Tutorial How to use Magisk-Delta instead of initrd-Magisk(Android-11 and up only)

mozixun

Member
VC
84
The initrd Magisk's biggest problem is that gearlock couldn't mount system properly,it couldn't install kernel package and so on.
Why I cannot package it to my modified PrimeOS?Because the Magisk-delta will broken after you factory reset your data.img,I have tried it,so after your factory reset,you should download my Modified PrimeOS and do this again!
The Screenshot is below:
1665039802062.jpeg


So I have a scheme to fix it through Magisk-Delta

1.install the initrd-Magisk through HuskyDG's Official Website.
*How to install:https://github.com/HuskyDG/initrd-magisk/wiki/How-to-install-initrd-magisk
1665040326434.jpeg




2.install the newest Magisk Manager and repair the environment in it(Choose the direct install!)
IMG_20221006_122403.jpg


3.Install the Magisk-delta app and open:https://huskydg.github.io/download/magisk/25.2-delta.apk

WARNING:please grant the root premission of magisk-delta and force stop it and then open the app again!Screenshot it below:
IMG_20221006_122558.jpg
IMG_20221006_122608.jpg
IMG_20221006_122638.jpg

4.After open it,DON'T LET IT FIX THE ENVIRONMENT BUTTON!

IMG_20221006_122650.jpg

5.Press install and directly press next,and choose the direct install to system partition!
IMG_20221006_122704.jpg

6.directly press next,and you will fail for the first time.And do STEP 4-5 again!

IMG_20221006_122715.jpg
>
IMG_20221006_122704.jpg

7.After STEP 6,you will success install it to /system
IMG_20221006_122726.jpg

8.
And DON'T REBOOT TO Android RIGHT ROW!
9.reboot to custom system like Windows/Linux,open the system folder and remove the boot-magisk.img and initrd.img

10.Then rename the initrd_real.img to initrd.img


11.In the end,boot into your Android-x86,you'll have a nice experience with your OS!
 

supertc

New member
VC
22
android x86 9.0 r2 can also use Magisk Delta,replace boot-magisk.img with the repaired IMG The img can be upgraded. my problem without mount system is that ntfs-3g: device or resource busy is displayed when other windows partitions are mounted. I don't want to delete the su that comes with Android x86 itself, so I can restore initrd.img can return no magisk status. I don't know what the problem is. A warm-hearted friend told me that using the command line mount is troublesome. Every time you enter a command, there is a random string. The partition can only be displayed on the terminal, but cannot be seen by other filers!
 

mozixun

Member
VC
84
android x86 9.0 r2 can also use Magisk Delta,replace boot-magisk.img with the repaired IMG The img can be upgraded. my problem without mount system is that ntfs-3g: device or resource busy is displayed when other windows partitions are mounted. I don't want to delete the su that comes with Android x86 itself, so I can restore initrd.img can return no magisk status. I don't know what the problem is. A warm-hearted friend told me that using the command line mount is troublesome. Every time you enter a command, there is a random string. The partition can only be displayed on the terminal, but cannot be seen by other filers!
Yes,it is.So this guide only for Android11+ because after A11,ramdisk has been merged into initrd.img
 

Similar threads

Similar threads

Get Connected

Discord Server

New Threads

Top