Tutorial initrd-magisk - Magisk for Android x86 project

huskydg

New member
VC
46
Another easy and convenient way to integrate Magisk, add support boot.img for Magisk into Android-x86 project (BlissOS, PrimeOS, ...).

68747470733a2f2f692e696d6775722e636f6d2f314262537254702e6a7067


Download initrd-magisk and boot-magisk from Release page

Check out Wiki page for how-to-install.
Post automatically merged:

If you want magisk modules to work properly, do not use rusty-magisk
 
Last edited:

wevelo

New member
VC
36
I ll try it later, thanks.

Although, I doubt that all modules will work and this is magisk 24.3, an outdated version.
 

huskydg

New member
VC
46
I ll try it later, thanks.

Although, I doubt that all modules will work and this is magisk 24.3, an outdated version.
Do you know you can update magisk through Magisk app
 

Attachments

  • IMG_20220601_124412_330.jpg
    IMG_20220601_124412_330.jpg
    42.4 KB · Views: 755

wevelo

New member
VC
36
This method doesn't seem to work following the guide in this wiki using GearLock. It returned "Invalid initrd image".

I tried to use initrd-magisk.img as initrd.img in gearlock/gearroot/android-x86 folder, as well as renaming it to ramdisk.img, both failed to boot.

How do I install it with gearlock installed in my system? Rusty isn't installed tough.
 

huskydg

New member
VC
46
This method doesn't seem to work following the guide in this wiki using GearLock. It returned "Invalid initrd image".

I tried to use initrd-magisk.img as initrd.img in gearlock/gearroot/android-x86 folder, as well as renaming it to ramdisk.img, both failed to boot.

How do I install it with gearlock installed in my system? Rusty isn't installed tough.
Seems like you don't read my instruction carefully. Moreover, please provide more information about it (screenshot, logcat, dmesg,...)

The proper instruction is renaming initrd.img to initrd_real.img, putting initrd-magisk as initrd.img and putting boot-magisk image as boot-magisk.img. Do not replace ramdisk.img
 
Last edited:

wevelo

New member
VC
36
An important part of the directory tree points a requirement which I wasn't following. Original initrd.img must be renamed to initrd_real.img, therefore, I actually can't see any usage for Magisk in Android-x86, GearLock does a better job.
 

huskydg

New member
VC
46
An important part of the directory tree points a requirement which I wasn't following. Original initrd.img must be renamed to initrd_real.img, therefore, I actually can't see any usage for Magisk in Android-x86, GearLock does a better job.
Magisk and GearLock, they serve different demand. Compare them are extremely wrong. Like you compare Magisk vs TWRP or Magisk vs Xposed.
 

wevelo

New member
VC
36
Magisk and GearLock, they serve different demand. Compare them are extremely wrong. Like you compare Magisk vs TWRP or Magisk vs Xposed.
GearLock, sorry, I don't think so. Nothing is extremely wrong about softwares, they're made for optimize your computer experience.
 

huskydg

New member
VC
46
GearLock, sorry, I don't think so. Nothing is extremely wrong about softwares, they're made for optimize your computer experience.
Magisk is framework, not all-in-one tool like GearLock. Compare Magisk with GearLock is wrong.
Post automatically merged:

Because they don't do the same so I cannot say who is the best.
 
Last edited:

wevelo

New member
VC
36
Magisk provides root access and modules in systemless way while GearLock doesn't have that thing. As i said compare them are such wrong.
A GearLock extension will do all these jobs, there is also a topic here from a superstar programmer which created something similar to the job done by a Magisk Module which optimize Android performance in ARM devices. While GearLock first, had intentions to be only a recovery, doesn't work directly in kernel, but things are changing and GearLock extensions are taking space in AMD64 development, ahead of Magisk which can't do much as most modules were compiled for ARM devices and not all are open source.
 

huskydg

New member
VC
46
A GearLock extension will do all these jobs, there is also a topic here from a superstar programmer which created something similar to the job done by a Magisk Module which optimize Android performance in ARM devices. While GearLock first, had intentions to be only a recovery, doesn't work directly in kernel, but things are changing and GearLock extensions are taking spaces in AMD development, ahead of Magisk which can't do much as most modules were compiled for ARM devices and not all are open source.
what do you mean when you say "most modules were compiled for ARM devices"?
Post automatically merged:

I am using Magisk modules Zygisk - Shamiko, Zygisk - LSPosed, Magic Flash, Enhanced mode for Hide My AppList, Thanox, ...
 

wevelo

New member
VC
36
what do you mean when you say "most modules were compiled for ARM devices"?
Whenever you install certain modules in Magisk using Android x86, the result will be like:
"This module is incompatible with x86_64 processors."
As Magisk works in Kernel Level, compatibility layer such as Houdini wont do anything.

edit: while a few other Magisk "modules" are just flashable applications.
 

huskydg

New member
VC
46
Whenever you install certain modules in Magisk using Android x86, the result will be like:
"This module is incompatible with x86_64 processors."
As Magisk works in Kernel Level, compatibility layer such as Houdini wont do anything.
i don't see any modules imcompatible with x86_64. Did you know almost Magisk/Zygisk module developers test their modules on AVD which is same as Android x86?
Post automatically merged:

Magisk works in userspace not kernel.
 
Last edited:

wevelo

New member
VC
36
i don't see any modules imcompatible with x86_64. Did you know almost Magisk/Zygisk module developers test their modules on AVD which is same as Android x86?

I tested this module before removing magisk, It was made to be used with ARM devices, therefore I also read many threads in XDA forums, the best answer I read was that Magisk has no utility for Android-x86. Anyway, Magisk has some shell applications which alters files in the system, like setting up a performance handler such as a battery life saver. I personally did the job with a shell script using pidof to check if a program is running, monkey to launch the application, find to search for scaling_governor and echo to switch between performance and powersave.
 

huskydg

New member
VC
46

I tested this module before removing magisk, It was made to be used with ARM devices, therefore I also read many threads in XDA forums, the best answer I read was that Magisk has no utility for Android-x86. Anyway, Magisk has some shell applications which alters files in the system, like setting up a performance handler such as a battery life saver. I personally did the job with a shell script using pidof to check if a program is running, monkey to launch the application, find to search for scaling_governor and echo to switch between performance and powersave.

This module uses very old Magisk modules template. That's why it fails to install.
If you know how to edit shell script, you can bypass some command check in installation script of module zip. Since you have libhoudini, you can execute arm binaries
 
Last edited:

zharevnarts

New member
VC
50
Please make video bro
Easy to apply bro just read wiki
How to mount ext4 on windows ? , use paragon Linux mounter then edit what u need in drive installed ext4 of Bliss, prime or phoenix.
I can share edited bliss & prime os initrd so you just need to replace only later
 

Similar threads

Similar threads

Get Connected

Discord Server

New Threads

Top