Magisk: Patching boot.img on A/B devices via app

Created on 26 Aug 2018  路  3Comments  路  Source: topjohnwu/Magisk

The app should not allow, the users of A/B devices to patch the boot image file via the app.

The true kernel loaded initramfs resides in system.img. If you patch the boot.img, you actually accepting to patch the recovery ramdisk. Thus, flashing the boot.img via fastboot, will have no effect.

Most helpful comment

You obviously don't know how Magisk works, so I'll close this issue.

All 3 comments

You obviously don't know how Magisk works, so I'll close this issue.

Possibly you miss understood the issue text or my particular device is much more customized by the manufacturer, as the app confirms a successful patch of the boot.img, and the magisk never runs despite the correct boot.img flashed on the device by fastboot. And this was the reason I suspected the magiskinit could possibly called by kernel.

You can refer my root guide written for Nokia 7 plus:

https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-root-ab-partition-scheme-t3792509

You shouldn't flash patched boot image to the device with fastboot command, instead you should perform temporarily boot from patched boot image, then reinstall Magisk zip in Magisk Manager to make the root permanently.

Was this page helpful?
0 / 5 - 0 ratings