Magisk v18.1 released with support for Kirin 960, EMUI 9, Android 4.2, and more
XDA Recognized Developer topjohnwu‘s Magisk started off as a systemless root method and has evolved over the years into a much more diverse and powerful tool beyond just plain root. But even today, if you need root, chances are that the recommended root method for your device mentions installing Magisk for root.
Magisk has now been updated to v18.1, bringing in support for Huawei’s EMUI 9 and Kirin 960, and also extending support all the way down to Android 4.2 (which was released in 2012, just to refresh your memory).
Magisk v18.1 Changelog
- [General] Support EMUI 9.0
- [General] Support Kirin 960 devices
- [General] Support down to Android 4.2
- [General] Major code base modernization under-the-hood
Even though Huawei has stopped providing official bootloader unlocking services, there are paid services that unlock the bootloader. This situation is similar to certain previous HTC devices that had to be bootloader unlocked through an unofficial paid service, with the difference being Huawei devices do sell like hot cakes. With v18.1, Magisk now supports EMUI 9 and the Kirin 960. However, since Huawei has done changes to partitions, special workarounds have been adopted to bring support. You can find more details and instructions on this instruction page.
Magisk now also supports Android versions all the way down to Android 4.2 Jellybean. Devices on Kitkat 4.4 and above will have all features enabled, while devices between Android 4.4 and Android 4.2 can utilize Magisk as a root solution currently as MagiskHide and resetprop features are not possible on Jellybean while Magic Mount/modules are temporarily disabled.
Magisk Manager has also been updated to v7.0.0, for which the changelog is as follows.
Magisk Manager v7.0.0 Changelog
- Major UI redesign!
- Render Markdown natively (no more buggy WebView!)
- Support down to Android 4.1 (native Magisk only support Android 4.2 though)
- Significantly improve Magisk log disply performance
- Fix post OTA scripts for A/B devices
- Reduce memory usages when verifying and signing boot image
- Drop support for Magisk lower than v18.0
As a side note, some users are reporting that Magisk Manager v7 is unable to directly upgrade Magisk from v18.0 to v18.1. If you face this issue, you should try unhiding Magisk Manager before updating. We would also like to stress the importance of backups (as most of us often take Magisk’s stability for granted), so be sure to make adequate backups before attempting an update.
Want more posts like this delivered to your inbox? Enter your email to be subscribed to our newsletter.