Magisk has received a new update that brings new features and a bunch of Android 12 support. The new version is Magisk v24.0 which is currently released on the public beta channel. It will be released on a stable channel soon. The new version is long overdue, but the new features make it worth the wait. You can download Magisk 24.0 from here.
What is Magisk?
Whenever anyone talks about Magisk, the word ‘systemless root’ is bound to appear. This is due to the fact that Magisk connects your device without a system. Simply put, this means that it is able to modify the system without notifying the device that a change has occurred. Also, Magisk cleverly makes all changes to the boot partition instead of actually modifying the system partition. As a result, neither Google nor your device has any idea that the system has been tampered with.
What is SafetyNet
To tighten security, Google has introduced a tool called ‘SafetyNet’. Its role was simple – to check if the system partition has been modified. And if it is found that the system has been tampered with, it will identify the app and stop its functionality.
Magisk vs SuperSu
Before Magsky came to the fore, it was all super sleepy. It was the only app that almost everyone used to root their device. But when Google implemented SafetyNet, it began to lose its luster. As a result, people started looking for alternatives and that is why Magisk was born. But what was the real problem with SuperSu? That was the way it worked.
SuperSu always makes changes to the system partition directly instead of editing the boot partition. Working in a ‘system’ way instead of ‘without a system’ – everything was fine and fine until Google introduced the SafetyNet feature.
As mentioned earlier, the SafetyNet system checks for changes to the partition and blocks any app that takes advantage of such changes. Because all rooted apps used root permission from SuperSu (which was responsible for tampering with the system), this app can no longer work on all devices. The most common apps include Google Pay, Pokemon Go, and every banking app.
Magisk Hide
The biggest problem with SuperSu is that it modified the system partition. So SafetyNet will block all apps that had root permission from SuperSu. This is where Magsky managed to score big. With the introduction of the ‘Magisk Hide’ feature, apps can easily evade Google. So all these apps were able to properly access the root and work as expected.
The last Magisk build was released in May last year. As this is a long hiatus, consumer expectations have also increased. Thanks to developer John Wu for adding so many new features and bug fixes and making it a great update that meets customer expectations. Zygisk debuted with Magisk 24.0, which was first available to testers on the Magisk Canary Blood. And now it is officially available to the public. You can see more about Zygisk here.
Another big change in Magisk 24.0 is that it now supports Android 12. Unfortunately, MagiskHide is no longer part of Magisk, which is one of the key features most users use to run apps even at the root. In case you didn’t know, Magic developer John Woo is now part of Google’s Android security team. And it is unethical to give features like Magisk Hide, so the reason is that Magisk Hide has been removed. You can find all changes to Magisk 24.0 below.
Magisk v24.0 Changelog
- [General] MagiskHide is removed from Magisk
- [General] Support Android 12
- [General] Support devices that do not support 32-bit and only runs 64-bit code
- [General] Update BusyBox to 1.34.1
- [Zygisk] Introduce new feature: Zygisk
- [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
- [MagiskBoot] Support patching 32-bit kernel zImages
- [MagiskBoot] Support boot image header v4
- [MagiskBoot] Support patching out skip_initramfs from dtb bootargs
- [MagiskBoot] Add new env variable PATCHVBMETAFLAG to configure whether vbmeta flags should be patched
- [MagiskInit] Support loading fstab from /system/etc (required for Pixel 6)
- [MagiskInit] Support /proc/bootconfig for loading boot configurations
- [MagiskInit] Better support for some Meizu devices
- [MagiskInit] Better support for some OnePlus/Oppo/Realme devices
- [MagiskInit] Support init.real on some Sony devices
- [MagiskInit] Skip loading Magisk when detecting DSU
- [MagiskPolicy] Load *_compat_cil_file from system_ext
- [MagiskSU] Use isolated devpts if the kernel supports it
- [MagiskSU] Fix root shell if isolated mount namespace is set
- [resetprop] Deleted properties are now wiped from memory instead of just unlinking
- [App] Build a single APK for all ABIs
- [App] Switch to use standard bottom navigation bar
- [App] Downloading modules from the centralized Magisk-Modules-Repo is removed
- [App] Support user configuration of boot image vbmeta patching
- [App] Restore the ability to install Magisk on the other slot on some A/B devices
- [App] Allow modules to specify an update URL for in-app update + install
Download Magisk 24.0
If you use magisk on your phone and want to try a new version of magisk then you can easily download it from here. It is mainly used for rooting and other advanced tasks. Magic makes everything from basic customization to advanced customization easy. The credit for the download link goes to its developer, John Wu. Now let’s move on to the download link.
How to install
- Make sure your phone’s Bootloader
- Make sure Custom Recovery is installed on your phone
- Download the latest Magisk manager 24 from the link above
- Install downlaoded Magisk 24 apk like normal apk file
- Open the installed Magisk app and follow the on screen instuctions
- Reboot and enjoy
[su_button url=”https://t.me/getdroidroms” target=”blank” style=”flat” background=”#0064c9″ size=”7″]Join us on telegram[/su_button]