[Download] Magisk v21.0 - Support for Android 11, Magisk Manager redesigned

Who I am
Aina Martin

After months of the latest stable release, developer John Wu has now announced the Magisk v21.0 update. This new and latest version of Magisk offers full support for Android 11, safe mode detection to fix boot loops caused by modules, new SELinux policy for devices running Android 8.0+, a completely redesigned user interface of the Magisk Manager app and much more.

Now you can download Magisk v21.0 with Magisk Manager v8.0.2 and install it on your Android device. Users running an older version of Magisk can easily upgrade to the latest version of Magisk v21.0 by following the instructions provided on this page.

Update n. 3: just one day after the previous release, John Wu has now released Magisk Manager v8.0.2. This solves the permission request on devices running Android 10 and earlier. Plus, move more files to the new CDN for faster and more reliable downloads.

Update n. 2: Magisk Manager v8.0.1 has been released. This new version fixes the vbmeta.imgpatch for the Samsung AP.tarfile. This fixes boot loops on Samsung Galaxy devices after flashing updated AP firmware files.

Update n. 1: According to developer John Wu, recent reports indicate that Magisk 21.0 does not work on Android MediaTek devices.

What's new in Magisk v21.0?

To recap, the previous version (Magisk 20.4) disabled Magisk Hide by default in light of the new hardware-backed SafetyNet claim, BusyBox's standalone mode, and introduced several other minor changes. Before we go to the download links or instructions, let's take a look at some of the key changes made by Magisk v21.0.

1. Support for Android 11

Let's start with the first big change. As you know, after months of testing, Google has finally announced the stable update of Android 11. Several device manufacturers are already releasing beta versions of Android 11 for their devices, such as the OnePlus 8 series. This definitely means that many users are running Android 11 on their phones. For rooting enthusiasts, Magisk has already supported Android 11 on the Canary channel. With v21.0, Magisk now fully supports Android 11 on stable channel. The developer worked very hard to rewrite a lot of Magisk code from scratch.

Also, Magisk generally mounts and uses the / tmpfsdirectory to store temporary data. According to the developer, the / sbinsubdirectory may no longer be available in Android 11. So, on devices running Android 11, Magisk will automatically create a random folder inside / and use it as the PATH. Developers could find everything about this change in the official documentation here.

  • The complete guide to rooting Android 11 using Magisk v21.0

2. Redesigned Magisk Manager user interface

In early January, developer John Wu showed a preview of a completely new design of the Magisk Manager application, courtesy of Viktor De Pasquale (@diareuse). For months, users running Magisk Canary have been privileged to enjoy this new user interface. With Magisk Manager v8.0.2, the newly redesigned user interface is now also available for users on the stable channel.

Starting with the design itself, the old hamburger slide menu has been completely removed. It has been replaced with a minimal navigation bar towards the lower end of the app. Elements in the app interface are now displayed in the form of cards.

The individual sections of the app have been rearranged for faster access. For example, Magisk Hide (when enabled) is now shown in the “Superuser” section instead of having its own dedicated section. Even in the old user interface, downloading and managing modules was done from their individual sections. With the new UI in Magisk Manager v8.0.2, you now have a unified “Modules” section that allows you to manage (install, uninstall and disable) and download Magisk modules from the same screen.

The new Magisk Manager also incorporates eight different color accent schemes and the ability to force light or dark theme modes.

Personally, we're not a huge fan of card-based design in general, but Magisk Manager adapts it so well that we have no choice but to love it. Overall, this new user interface makes a big leap over the previous one, both in terms of design and usability.

3. Safe Mode Detection

A common problem that many users face is boot cycles caused by modules due to incompatibility. Until now, users could use TWRP or ADB to remove unauthorized Magisk modules to fix the problem.

Developer John Wu was certainly well aware of the problem and gave us a simple solution. From Magisk 21.0 onwards, you could just boot your Android device in safe mode. Magisk will detect Safe Mode and automatically disable all Magisk modules. After that, you could just reboot into normal OS mode and the boot loop will be fixed.

4. New configuration of SELinux policies on Android 8.0+

For devices running Android 8.0 and later, SELinux security has been strengthened with an entirely new policy configuration. This new policy now keeps the Android sandbox less compromised, separates the Magisk policy rules from the original rules, thus providing better security on rooted devices with Magisk.

So these were the main changes in the Magisk 20.1 update. For end users, not much has changed except the first two, which are support for Android 11 and the redesigned Magisk Manager. For developers, some key changes have been made to how Magisk works. You would like to refer to the new changes in the official documentation here.


Magisk v21.0 change log

Below is the complete change log for Magisk v21.0 published by the developer on Github.

  • [General] Supports Android 11
  • [General] Add Safe Mode Detection. Disable all modules when the device boots in safe mode.
  • [General] Increase the post-fs-datatimeout of the mode from 10 seconds to 40 seconds
  • [MagiskInit] 2SI support rewritten from scratch
  • [MagiskInit] Support when no folder exists (Android 11)
  • [MagiskInit] Download fstab from device tree to rootfs and force inita use it for 2SI devices
  • [MagiskInit] Eliminate AVB for 2SI as it may cause boot loop
  • [Modules] Module mounting logic rewritten from scratch
  • [MagiskSU] For Android 8.0+, a completely new policy configuration is used. This reduces trade-offs in the Android sandbox, providing greater policy isolation and better security for root users.
  • [MagiskSU] Isolated mount namespace will now inherit from parent process first, then isolate itself from the world
  • [MagiskSU] Updates the communication protocol with Magisk Manager to work with the enhanced SELinux configuration
  • [MagiskPolicy] Optimize matches all rules. This will significantly reduce the size of the policy binary, save memory, and improve overall kernel performance.
  • [MagiskPolicy] Supports the declaration of new types and attributes
  • [MagiskPolicy] Make the policy statement closer to the *. Action format. Please check the updated documentation or magiskpolicy --helpper for more details.
  • [MagiskBoot] Extrablob compressed support
  • [MagiskBoot] Fill boot images to original size with zeros
  • [MagiskHide] Manipulates the properties of the additional provider

Magisk Manager v8.0.2 change log

Below is the complete change log for Magisk Manager v8.0.2 published by the developer on Github. The change log for V8.0.0 and V8.0.1 has been combined into this.

  • Resolves an issue with requesting permission on devices older than Android 10
  • Download multiple files via CDN
  • Fixed the vbmeta.img issue with patches for the Samsung AP.tarfile. This fixes boot loops on devices like Galaxy S10 after flashing updated AP files.
  • Properly truncate existing files before writing to avoid damaged files
  • Prevent a possible UI loop when the device has had very low memory
  • Switch to using JSDelivr CDN for several files 100% full app rewrite! It will highlight the functional changes below.
  • Add detailed device information on the home screen to assist user installation
  • Supports Magisk v21.0 communication protocol
  • Support modern Samsung AP.tar patching

Download Magic v21.0 and Magic Manager v8.0.2 from Github

Like every previous version, Magisk v21.0 is available for download as a flasable ZIP file for those who wish to install it via a custom recovery. Users who want to install Magisk by patching the boot image can download the latest Magisk Manager v8.0.2 APK from below.

File ZIP flashable di Magisk v21.0:

  • Installer: Magisk-v21.0.zip
  • Uninstaller: Magisk-uninstaller-20201003.zip
  • Magic Manager v8.0.2 APK: MagicManager-v8.0.2.apk

If you are looking for a specific version of Magisk, check the official Github release page for Magisk.

How to install Magisk v21.0

You can install the latest version of Magisk on your Android device:

  • By installing the Magisk installer ZIP file using a custom recovery, such as TWRP recovery.
  • Or, patching the boot / recovery image in Magisk Manager and then flashing the resulting patched boot image to your phone.

The first method is generally simpler and is the one you should use if you have installed a custom recovery. On the other hand, if a custom recovery like TWRP is not available for your device, or if you don't want to install a custom recovery at all, just follow the second method.

The second method also makes it much easier to install the OTA update device after rooting. All you will need is the stock boot / recovery image for the version / build number of the Android software currently installed on your device. You can extract these images from OEM factory image or OTA update package, try to download it from firmware.mobi, or search for device rooting guide on our website.

Before installation, it is highly recommended to make a full backup of all data before starting the installation of Magisk. This will prevent your data from being completely lost if a problem occurs during installation.

Instructions for both methods can be found in the following tutorial. We suggest that you follow the instructions and familiarize yourself with the procedure before starting to perform it.

- The complete step by step guide to install Magisk on Android

How to upgrade to Magisk v21.0 Stable

If you have an older version of Magisk installed on your device, you don't need to reinstall it at all. You can simply upgrade to the stable version of Magisk v21.0 using Magisk Manager. To do it:

  1. First, download the Magisk Manager v8.0.2 APK file and install it on your device.
  2. Now launch the Magisk Manager application on your device.
  3. Press the cogwheel icon at the top right to access the “Settings” menu.
  4. Tap “Update Channel” and select “Stable”.
  5. Go back to the main Magisk Manager screen and wait for it to check for the latest version.
  6. Select "Update" and choose "Direct Installation" as the installation method.
  7. Finally, select “LET'S GO” to confirm and install the Magisk v21.0 update on your device.
  8. Press the "Restart" button after installation is complete.

That's all! So you were able to download Magisk 21.0 Stable and install / update it on your phone. Don't forget to browse the redesigned Magisk Manager app to familiarize yourself with the new user interface.

The developer has certainly made some major improvements in this latest Magisk update, making it safer for end users and easier for the module / kernel developers out there. We really appreciate his hard work and the time he has devoted to the Android community. If you have any questions about Magisk or its installation, please do not hesitate to contact us.

Fonte: Magisk su Github

add a comment of [Download] Magisk v21.0 - Support for Android 11, Magisk Manager redesigned
Comment sent successfully! We will review it in the next few hours.