huskydg / initrd-magisk Goto Github PK

Hi, I have used your initrd-magisk. It is wonderful.
However, I have found the initrd unable to mount f2fs partition.
There is a mount.ntfs-3g into initrd.img/sbin, so it could mount ntfs partition.
If f2fs-tools were put into initrd.img/sbin, I wonder, could it have mounted f2fs partition?
Here is f2fs-tools into sbin that I copy from manjaro.
Could you try to see if it would make initrd to mount f2fs partition?
Or if you have a better way, in order to support both magisk and f2fs, could release a initrd-magisk-f2fs?

I install it using method 2 it works fine magisk app good and all I used unsu to remove su binary of rom then I enable zygisk it work good then install a module lsposed but it got installed and work fine but installed module lists not show in magisk app it empty but module work fine

TLDR
Magisk app isn't showing installed modules list but the modules work fine.

Hello I'm using initrd-magisk v1.15 with cm14.1-r5 kernel default
initrd-magisk loop in "Initialize system environment....."

EXT4-fs (sda4) couldn't mount as ext3 due to feature incompatibilities

Default initrd from iso work and initrd-magisk work with other os I'm testing.
For now I'm only get problem with initrd-magisk+cm14.1-r5 (previous version not tested)

grub code

kernel /cm14/kernel  quiet root=/dev/ram0 androidboot.selinux=permissive buildvariant=userdebug ROOT=/dev/sda4 SRC=/cm14
initrd /cm14/initrd.img

I can send you initrd_real.img and ramdisk.img if you want.
and I already verify if iso not corrupt

Hello. I've been using the LineageOS 14 r5 since early 2021 but only recently I wanted to get Magisk installed in hopes I can hide root from other apps, however, where is this directory you speak of? The / folder? I don't have an initrd file or directory there whatsoever, and I'm overall new to Linux so please bare with me, I can't find info anywhere on this.

Please add initrd-magisk whith supports Gearlock Recovery

on manualy install Gearlock Recovery I have error

         Developed by @AXON | supreme-gamers.com | Version: 7.3.3

------- Partition Table -------

 1]. /dev/block/sda1: LABEL="Android-x86" TYPE="ext4"

• Enter the partition number where you got this Android-x86 OS installed >> 1

• Trying to mount it ...

• Getting ramdisks : Done

• Extracting ramdisks : Done

• Patching Initial Ramdisk : ~ Error [gslr:1], could not find any line containing mount_sdcard
  Done

• Generating new ramdisks : Done

• Installing fx File-Manager : Success

++ Your system is now GearLocked!

+++ Press [Enter] to reboot ...

I'm trying to root an android-x86 installation running with qemu and virt-manager but I can't seem to make it work. No idea what Android-X84 directory means so I've decompiled the bootable iso and replaced initrd from there but upon booting Magisk wasn't yet installed.

I've tried using official Android-x86, Bliss OS v14.10.1, PrimeOS-2.1.3-64 bit. they all doesnt detect it

I followed the instructions (create folder "boot", putting the stock initrd.img to the folder, putting initrd-magisk.img as initrd.img in android-x86 folder, putting boot-magisk.img in boot folder) but after installing magisk apk, it doesnt detect magisk (Installed: N/A, Zygisk: NO)

I may be just tired and so i miss a step or it's really doesnt work. please help

I'm so sorry to post here, but that section is read-only and can't post, and I don't know how to contact the author. I need version 10024 of MagiskOnEmu, or any other version with a fix for bluestacks not loading magisk modules, thanks a lot.

the gui design in the os in homepage is very beautiful what os is?

Hello ! First, I just want to say that I love the project and I've been using it before and was able to setup Magisk as root manager with no problems, but starting with 1.20 I'm no longer able to setup Magisk as root manager on A7. I try to flash the latest .zip file in gearlock, zip file not flashing, I tried to do a direct install, doesn't install. Tried to unsu from gearlock, gearlock tells me unsu is not a recognised command.

I tried this on the latest 1.20 version on Android 7, both Lineage OS and Vanilla versions, both exhibit the same behavior.

Hi,

how is possible have magisk in a VM with Proxmox?

I have tried all tutorial without any success.

Well, the title says it all. I use BlissOS 15.8.5 (Android 12L) and I need to install Magisk there. The issue is that no matter how I install Magisk and modules, they always disappear after a reboot: they are available straight after installation, they are active after the first reboot and they are gone on the next reboot.

What I've tried so far:

• initrd-magisk 1.19 + Magisk Delta stable/canary/debug + unpacked system from sfs to img + switched versions here and there
• Magisk Delta debug + KernelSu root + Direct install into system
• Putting unpacked modules in /data/adb/modules in DEBUG mode
• Different modules, Zygisk on/off

I also have a strong suspicion that it's a rom-specific issue but I'm unable to find any info about it in any discussion there.

These logs are from the version that directly installs into system, I can get logs from initrd version if required. I can also provide access to the VM if needed.

magisk_log_module_active.log
magisk_log_module_gone.log

Thanks!

Hi, man.
I have seen you adapt initrd.img to mount a fake boot.img.

I wonder whether vmlinux could be adapted to mount a fake boot.img.

What I want is to achieve this picture,

The advantage of this is

• to avoid editing android.cfg over and over again, if Android x86 updates;
• to avoid copying initrd.img (initrd-magisk.img renamed first) to cover initrd.img (the real not having been made a backup, yet), by mistake;
• to avoid .img files into $SRC are too many to be recognized immediately rightly, only to be deleted or covered by mistake;
• to avoid hesitating for a long time to tangle which .img file should be renamed at first.

And then I create a fork to edit,

After building, I download to try.
It can boot, but seems not to mount boot-magisk.img.
It must be something I haven't edited yet.

Could you tell me what else I should edit?

I will appreciate it if you would help me about that.

Due to comprehension issues, I wasn't able to install initrd-magisk, well, sorted it out, but now I can't get root access.

Followed the steps on the Wiki, and installed latest Magisk Delta. When opening the App, Superuser and Modules appear grayed out.

Installed: N/A
Zygdisk: No
Ramdisk: Yes

Any hints?
Thanks in advance.

initrd-magisk v1.19 & Official Magisk v26.1

If using Magisk 26.1, there is some bug.
The Official Magisk App v26.1 is disapearing, with apk lost or not found.
If downloading its apk and trying to install it again, it cannot be opened after installation.

the Log

I catch the log by using Magisk Alpha.
magisk_log_2023-07-16T11.43.47.log

initrd-magisk v1.19 & Magisk Alpha the newest

If using Magisk Alpha the newest, there is some bug.
https://github.com/vvb2060/magisk_files
It seems that the boot-magisk.img patched by Alpha cannot be mounted.
Sorry I forget saving its log.

something saved

something.zip

• alpha.apk - the apk file of Magisk Alpha the newest;
• boot-magisk.img - patched by Magisk v26.1;
• Magisk-v26.1.apk - the apk file of Magisk v26.1;
• magisk_log_2023-07-16T11.43.47.log - the log of the boot-magisk.img above;

Last

However, your Magisk Delta the newest works fine.
Don't worry, take your time.
If you are busy, please ignore this issue.

I have installed Bliss OS 14.3 on the internal emmc of my windows 10 tablet and trying to get root to work.. came across this and when I try to follow the how to doc at https://github.com/HuskyDG/initrd-magisk/wiki/How-to-install-initrd-magisk

said:

In Android-x86 directory, rename initrd.img to initrd_real...

where is this "Android-x86 directory" please?

How can I edit the files in Android x86 directory?
My environment is running in a VM in synology virtual machine manager. I could of sworn I had installed it read/write with ext4. I can see that directory with and android file manager but cannot edit it. There is a boot directory in that main directory already. Can you toss me a bone please

- Flashing new boot image
! /dev/block/loop2 is read only
! Installation failed

My system:
Bliss-v14.10-x86_64-OFFICIAL-foss-20230201.iso + qemu

I followed this tutorial, but I can't find the initrd.img in the directories of the system
https://github.com/HuskyDG/initrd-magisk/wiki/How-to-install-initrd-magisk

I tried initrd magisk on primeos 2.1.3 before, worked perfectly fine but I had to reinstall it (irrelevant) and now when I try this it just says Initialization failed!

What is wrong or what did I do wrong
files in my androidx86 dir:
data (folder)
boot-magisk.img
initrd.img
initrd.img.old
kernel
system.img

and this is my parameters on grub2win