Magisk v27.0

• [Zygisk] Introduce new code injection mechanism
• [Zygisk] Support new signature introduced in U QPR2
• [SEPolicy] Update libsepol to properly set some policy config bits
• [MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions
• [ResetProp] Add new wait for property feature resetprop -w

Full Changelog: here

Magisk 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

Full Changelog: here

Magisk v26.3

• [General] Fix device information detection script
• [General] Update BusyBox to 1.36.1
• [General] Update toolchain that produces broken arm32 executables
• [App] Fix root service unable to bind on OnePlus devices

Full Changelog: here

Magisk v26.2

• [MagiskBoot] Support extracting boot image from payload.bin
• [MagiskBoot] Support cpio files containing character files
• [MagiskBoot] Support listing cpio content
• [MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation
• [Daemon] Make daemon socket a fixed path in MAGISKTMP
• [resetprop] Support printing property context
• [resetprop] Support only printing persistent properties from storage
• [resetprop] Properly support setting persistent properties bypassing property_service
• [MagiskSU] Support -g and -G options
• [MagiskSU] Support switching mount namespace to PID with -t
• [MagiskPolicy] Fix patching extended permissions
• [MagiskPolicy] Support more syntax for extended permissions
• [MagiskPolicy] Support printing out the loaded sepolicy rules
• [App] Support patching boot image from ROM zips
• [App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

Full Changelog: here

Magisk v26.1

Changes from v26.0

• [App] Fix crashing when revoking root permissions
• [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition
• [General] Restore module files' context/owner/group from mirror. This is a regression introduced in v26.0

(The following is the same as v26.0 release notes)

Hey! Long time no see!

Bumping Minimum Android Version to 6.0

Magisk's support for Android Lollipop has been pretty broken for a while without it being noticed. Also, none of the active developers of Magisk have actual hardware to run Android Lollipop. We rely on using the official Android emulator for regression testing on older platforms, however Google never shipped a Lollipop emulator image with SELinux support, leaving us with no option but to drop Lollipop support since we don't feel comfortable supporting Android Lollipop without adequate testing.

New Magic Mount Implementation

Magic Mount, the feature that make modules modify partitions, has gone through a major rewrite. The existing implementation doesn't work well with OEMs injecting overlays into their system using overlayfs. The new implementation fundamentally changes how filesystem mirrors are created, giving us a more accurate clone of the unmodified filesystem.

New sepolicy.rule Implementation

Magisk allows modules to provide custom SELinux patches by including the file sepolicy.rule. Due to the complicated nature of SELinux patching, the compatibility of this functionality has been pretty spotty; many devices are not supported. In this release, a brand new pre-init partition detection mechanism has been designed to support even more devices. Due to complicated reasons, this detection mechanism cannot be performed in a custom recovery environment.

This means that any installation of Magisk v26+ using custom recovery will be incomplete; a subsequent re-installation through the Magisk app after booting up is required.

Zygisk Updates

The new Zygisk API v4 is now live! It comes with new features and a refined PLT function hook API. The implementaton of Zygisk has also gone through some major refactoring, including new code loading/unloading mechanisms and a new PLT function hook implementation.

Head over to the Zygisk Module Sample repository to check out the new API and documentation!

Full Changelog: here

Magisk v26.0

Hey! Long time no see!

Bumping Minimum Android Version to 6.0

Magisk's support for Android Lollipop has been pretty broken for a while without it being noticed. Also, none of the active developers of Magisk have actual hardware to run Android Lollipop. We rely on using the official Android emulator for regression testing on older platforms, however Google never shipped a Lollipop emulator image with SELinux support, leaving us with no option but to drop Lollipop support since we don't feel comfortable supporting Android Lollipop without adequate testing.

New Magic Mount Implementation

Magic Mount, the feature that make modules modify partitions, has gone through a major rewrite. The existing implementation doesn't work well with OEMs injecting overlays into their system using overlayfs. The new implementation fundamentally changes how filesystem mirrors are created, giving us a more accurate clone of the unmodified filesystem.

New sepolicy.rule Implementation

Magisk allows modules to provide custom SELinux patches by including the file sepolicy.rule. Due to the complicated nature of SELinux patching, the compatibility of this functionality has been pretty spotty; many devices are not supported. In this release, a brand new pre-init partition detection mechanism has been designed to support even more devices. Due to complicated reasons, this detection mechanism cannot be performed in a custom recovery environment.

This means that any installation of Magisk v26+ using custom recovery will be incomplete; a subsequent re-installation through the Magisk app after booting up is required.

Zygisk Updates

The new Zygisk API v4 is now live! It comes with new features and a refined PLT function hook API. The implementaton of Zygisk has also gone through some major refactoring, including new code loading/unloading mechanisms and a new PLT function hook implementation.

Head over to the Zygisk Module Sample repository to check out the new API and documentation!

Full Changelog: here

Magisk v25.2

Maintenance release fixing various issues.

• [MagiskInit] Fix a potential issue when stub cpio is used
• [MagiskInit] Fix reboot to recovery when stub cpio is used
• [MagiskInit] Fix sepolicy.rules symlink for rootfs devices
• [General] Better data encryption detection
• [General] Move the whole logging infrastructure into Rust

Full Changelog: here

Magisk v25.1

v25.1 fixes some minor bugs over v25.0. The following are the same as v25.0 release notes.

Another major release! A lot of the changes aren't visible at the surface, but v25 is actually a really substantial upgrade!

MagiskInit Rewrite

A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the "SELinux Problem" once and for all.

Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.

MagiskSU Security Enhancements

The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:

• Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
• Properly support and implement the UX in the Magisk app for packages using sharedUserId
• Enforce root manager APK signature verification to combat the rampant unofficial Magisk app "mods"

Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk's root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.

And in case some of you are about to put on your tin foil hats, this is not designed to "vendor lock-in"; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk's build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.

Full Changelog: here

Magisk v25.0

Another major release! A lot of the changes aren't visible at the surface, but v25 is actually a really substantial upgrade!

MagiskInit Rewrite

A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the "SELinux Problem" once and for all.

Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.

MagiskSU Security Enhancements

The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:

• Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
• Properly support and implement the UX in the Magisk app for packages using sharedUserId
• Enforce root manager APK signature verification to combat the rampant unofficial Magisk app "mods"

Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk's root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.

And in case some of you are about to put on your tin foil hats, this is not designed to "vendor lock-in"; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk's build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.

Full Changelog: here

Magisk v24.3

For those coming from v24.1, check the full changelog for changes introduced in v24.2.

• [General] Stop using getrandom syscall
• [Zygisk] Update API to v3, adding new fields to AppSpecializeArgs
• [App] Improve app repackaging installation workflow

Full Changelog: here