mirror of
https://github.com/topjohnwu/Magisk.git
synced 2024-12-25 10:47:38 +00:00
34 lines
2.5 KiB
Markdown
34 lines
2.5 KiB
Markdown
|
## 2023.4.11 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](https://github.com/topjohnwu/zygisk-module-sample) repository to check out the new API and documentation!
|
||
|
|
|
||
|
|
### Full Changelog: [here](https://topjohnwu.github.io/Magisk/changes.html)
|