Magisk Changelog

v26.4

• [MagiskBoot] Don’t pad zeros if signed boot image is larger
• [MagiskPolicy] Fix genfscon and filename_trans
• [MagiskPolicy] Fix bug in libsepol
• [Zygisk] Fix and simplify file descriptor sanitization logic
• [App] Prevent OOM when patching AP tarfiles
• [App] Fix bug in device configuration detection
• [Daemon] Fix certificate parsing of APKs
• [General] Fix logging errors from C++ code being ignored

Installation

This installation method is deprecated and is maintained with minimum effort. YOU HAVE BEEN WARNED!

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method.

• Download the Magisk APK
• Rename the .apk file extension to .zip, for example: Magisk-v24.0.apk → Magisk-v24.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in the custom recovery to rename the file.
• Flash the zip just like any other ordinary flashable zip.
• Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
• Launch the Magisk app; it will show a dialog asking for reinstallation. Do the reinstallation directly within the app and reboot (if you are using MTK devices that lock the boot partition after boot, please patch the boot image and flash it by custom recovery or fastboot).

Warning: the sepolicy.rule file of modules may be stored in the cache partition. DO NOT WIPE THE CACHE PARTITION.

Uninstallation

The easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.

Download