Magisk v20.2 lets modules include custom sepolicy patches and introduces a new module installer format
Magisk is one of the best tools for Android users looking to unlock the full potential of their device. It’s a systemless interface developed by XDA Recognized Developer topjohnwu that can be used for everything from rooting your device to adding unique features to it. The best part about using it is that it allows users to tinker with system settings without actually making changes to system files. Another reason behind its popularity is its ability to bypass Google’s SafetyNet which prevents certain apps from running on rooted devices. Late last year, topjohnwu rolled out Magisk v20.1 along with Magisk Manager v7.4.0 featuring a couple of interesting updates to the interface. And now, they’ve released v20.2 which includes even more changes and bug fixes for both Magisk and Magisk Manager.
As per the release notes posted on our forums, the update brings improvements to the root request prompt, support for patching dtb/dtbo partition formats, support for pre-init sepolicy patch in modules, and a new module installer format which aims to make creating new modules easier.
Here’s the official changelog for Magisk v20.2:
- [MagiskSU] Properly handle communication between daemon and application (root request prompt)
- [MagiskInit] Fix logging in kmsg
- [MagiskBoot] Support patching dtb/dtbo partition formats
- [General] Support pre-init sepolicy patch in modules
- [Scripts] Update magisk stock image backup format
- Magisk Manager v7.5.0:
- Support new MagiskSU communication method (ContentProvider)
- Fix several issues with hidden stub APK
- Support using BiometricPrompt (face unlock)
For more information on the pre-init sepolicy patches for modules and the new module installer format, you can visit the GitHub source linked below. If you’re interested in creating new Magisk modules with the updated installer format, you can follow topjohnwu’s guide on how to use the new module template.