Magisk v20.4 release! 🎉🎊
This release is mainly focused on stability and bug squashing, and is released to the public beta channel.https://t.co/xiamjRai17
— John Wu (@topjohnwu) March 23, 2020
Here in this guide, we will share the full instructions to download and install Magisk zip on your Android Phone. This guide is also for the newbies/noobs who never installed root on their phones.
Magisk, the well-known tool for acquiring root permissions on Android devices, has received a new update that fixes some unexpected bugs and introduces the obfuscation feature. If you already have magisk root on your phone, then you can simply upgrade your phone to Magisk Zip 18.1 and Magisk Manager apk to 7.0.0. If you are installing Magisk root on your phone for the first time, then you can simply follow our instructions to install it on your phone.
Customizing an Android smartphone and performing advanced tweaks like flashing custom kernels, custom ROMs, overclocking, and changing system settings is fun, but you need root access to your device to be able to do these. Some time ago, SuperSU was the popular way of gaining root access on an Android smartphone, but since its release, Magisk has become the go-to way of rooting a smartphone. You can easily manage root access with Magisk Manager apk, and implement many functionalities with the various modules available.
There are many root apps available out there that you can use to gain root access on your Android device, but perhaps the simplest and easiest to use is Magisk. Magisk is an Android utility that grants you a systemless root on your Android device and managed with an application called Magisk Manager.
What is Magisk?
Among the plethora of options that an unlocked Android device provides, the most important one is the ability to gain administrative privileges or system-level access. In simpler terms, this is known as rooting your device. Earlier, people used to root their devices via SuperSu. However, the thing was that it directly modified the system partition. This was fine until Google released the SafetyNet mechanism. With this mechanism in place, if there was any tweak made to your device’s system partition, the SafetyNet check will fail and this will result in your inability to use most of the apps.
This is where Magisk came into the picture. Developed by topjohnwu, Magisk is a flashable ZIP file that is able to root your device “systemlessly”. That is, it makes no changes to your system partition. Whatever changes took place, it was stored in the boot partition. As a result, when Google checks for the SafetyNet trip, your device will successfully pass this test. This is one major reason why Magisk is the preferred method to root an Android device.
What is Magisk Manager?
While Magisk is a flashable ZIP, Magisk Manager is an APK file that could be installed on any Android device, whether rooted or not. There are quite a few reasons that you need to use this tool. To begin, if your device doesn’t have a working TWRP Recovery, then you cannot use the Magisk ZIP, and the Magisk Manager becomes the sole way of rooting your device.
Furthermore, it provides a rooted device an interface to interact with apps that ask for root permissions. Likewise, there are tons of Magisk Modules that you could install from this app itself. And if you need to unroot your device for some reason, that could easily be done via the app as well. So whether or not your device has Magisk ZIP Installer, Magisk Manager is the absolute necessity for a rooted device.
Advantages of Magisk
There exists quite a lot of benefits associated with rooting your device via Magisk. The first and foremost is the fact that it doesn’t tweak your device’s /system partition. As a result, SafetyNet wouldn’t be tripped and apps like Google Pay and Pokemon GO will work without any issue. Apart from that. there are some apps that just refuse to work in a rooted device. In that case, you could use the Magisk Hide functionality. This hides root from your selected apps and it will then function as it does in a non-rooted device.
Well, rooting does bring in a lot of goodies with itself as well. These include the ability to try out Magisk modules, Xposed Framework, or give your device a complete overhaul via Substratum Themes. Likewise, you could also remove unnecessary apps (bloatware) that comes pre-installed on your device. Taking a complete device backup via Titanium backup or flashing a custom Kernel to overclock the device’s CPU are some of the other benefits. Well, to be fair, there is no end to the benefits that a rooted Android device brings with itself. And Magisk plays an extremely crucial role in all this.
- Main Advantage is their systemless root: You can carry out any system or vendor modification on your Android smartphone without tampering with the system partitions.
- MagiskSU: You have the option to Grant or Deny the permission of any application
- Magisk Manager: You have the ability to install new updates and add or delete the modules on your phone. With Manager, you can also hide the root to bypass the SafetyNet check, download modules, and you have the option to Grant or Deny the permission of any application
- ByPass SafetyNet Check: Google’s SafetyNet detects when the system has been tampered with and blocks certain apps from working properly.
- OTA Updates: With Magisk, you can also enjoy seamless OTA updates without any problem.
- Install Systemless Xposed: You can install the Magisk modules to tweak, enhance, and add functionality to your device. You can use them for everything from improving battery life to installing iOS emojis on your Android phone.
Why is Magisk so important?
Google SafetyNet is the main reason why a lot of people use this tool over other methods like SuperSU, Kingoroot, etc. Google’s SafetyNet detects when the system has been tampered with and blocks certain apps from working properly such as Google Pay, Netflix, and Pokemon GO are a few examples. Unlike SuperSU which only grants or denies root permissions for specific apps, Magisk can hide root from an app completely. By hiding the root from an app, banking app or Pokemon GO on your rooted device can work if you’re rooted.
Similar to the Xposed Installer, the Magisk has its own Modules which the users can install and take benefit from. You would find a lot of modules like Busy Box Installer, AdBlock, Action Launcher and much more. Installing a module is not at all difficult, all you need to do is just select the module and tap on install.
You may further download various modules from the official repository or from here.
Magisk v20.4 Stable:
- [MagiskInit] Fix potential bootloop in A-only 2SI devices
- [MagiskInit] Properly support Tegra partition naming
- [General] Load libsqlite.so dynamically, which removes the need to use wrapper scripts on Android 10+
- [General] Workaround possible bug in x86 kernel readlinkat system call
- [BusyBox] Enable SELinux features. Add chcon/runcon etc., and ‘-Z’ option to many applets
- [BusyBox] Introduce standalone mode. More details in release notes
- [MagiskHide] Disable MagiskHide by default
- [MagiskBoot] Support patching special Motorolla DTB format
- [General] Detect API level with a fallback method on some devices
- [MagiskHide] Add workaround for Xiaomi devices bootloop when MagiskHide is enabled on cross region ROMs
- [MagiskPolicy] Support ‘genfscon’ sepolicy rules
- [Scripts] Support Lineage Recovery for Android 10+
- [MagiskHide] Add more potential detectable system properties
- [Scripts] Better addon.d (both v1 and v2) support
- [Scripts] Support NAND based boot images (character nodes in /dev/block)
Magisk v20.3 Stable:
- Fix lz4_legacy decompression
Magisk v20.2 Stable:
- [MagiskSU] Properly handle communication between daemon and application (root request prompt)
- [MagiskInit] Fix logging in kmsg
- [MagiskBoot] Support patching dtb/dtbo partition formats
- [General] Support pre-init sepolicy patch in modules
- [Scripts] Update magisk stock image backup format
Magisk v20.1 Stable:
– [MagiskSU] Support component name agnostic communication (for stub APK)
– [MagiskBoot] Set proper header_size in boot image headers (fix vbmeta error on Samsung devices)
– [MagiskHide] Scan zygote multiple times
– [MagiskInit] Support recovery images without /sbin/recovery binary. This will fix some A/B devices unable to boot to recovery after flashing Magisk
– [General] Move acct to prevent daemon being killed
– [General] Make sure “–remove-modules” will execute uninstall.sh after removal
Magisk v20 Stable:
– [MagiskBoot] Support inject/modify mnt_point value in DTB fstab
– [MagiskBoot] Support patching QCDT
– [MagiskBoot] Support patching DTBH
– [MagiskBoot] Support patching PXA-DT
– [MagiskInit] [2SI] Support non A/B setup (Android 10)
– [MagiskHide] Fix bug that reject process names with “:”
– [MagicMount] Fix a bug that cause /product mirror not created
Magisk 19.4 Stable:
– [MagiskInit] [SAR] Boot system-as-root devices with system mounted as /
– [MagiskInit] [2SI] Support 2-stage-init for A/B devices (Pixel 3 Android 10)
– [MagiskInit] [initramfs] Delay sbin overlay creation to post-fs-data
– [MagiskInit] [SARCompat] Old system-as-root implementation is deprecated, no more future changes
– [MagiskInit] Add overlay.d support for root directory overlay for new system-as-root implementation
– [MagiskSU] Unblock all signals in root shells (fix bash on Android)
– [MagicMount] Support replacing files in /product
– [MagiskHide] Support Android 10’s Zygote blastula pool
– [MagiskHide] All random strings now also have random length
– [MagiskBoot] Allow no recompression for ramdisk.cpio
– [MagiskBoot] Support some weird Huawei boot images
– [General] Add new “–remove-modules” command to remove modules without root in ADB shell
– [General] Support Android 10 new APEX libraries (Project Mainline)
– [MagiskHide] Hugely improve process monitor implementation, hopefully should no longer cause 100% CPU and daemon crashes
– [MagiskInit] Wait for partitions to be ready for early mount, should fix bootloops on a handful of devices
– [MagiskInit] Support EROFS used in EMUI 9.1
– [MagiskSU] Properly implement mount namespace isolation
– [MagiskBoot] Proper checksum calculation for header v2
Magisk 19.2 Stable:
– [General] Fix uninstaller
– [General] Fix bootloops on some devices with tmpfs mounting to /data
– [MagiskInit] Add Kirin hi6250 support
– [MagiskSU] Stop claiming device focus for su logging/notify if feasible
This fix issues with users locking Magisk Manager with app lock, and prevent
video apps get messed up when an app is requesting root in the background.
Magisk 19.1 Beta:
– [General] Support recovery based Magisk
– [General] Support Android Q Beta 2
– [MagiskInit] New sbin overlay setup process for better compatibility
– [MagiskInit] Allow long pressing volume up to boot to recovery in recovery mode
– [MagicMount] Use proper system_root mirror
– [MagicMount] Use self created device nodes for mirrors
– [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)
Magisk 19.0 Beta:
– [General] Remove usage of magisk.img
– [General] Add 64 bit magisk binary for native 64 bit support
– [General] Support A only system-as-root devices that released with Android 9.0
– [General] Support non EXT4 system and vendor partitions
– [MagiskHide] Use Zygote ptracing for monitoring new processes
– [MagiskHide] Targets are now per-application component
– [MagiskInit] Support Android Q (no logical partition support yet!)
– [MagiskPolicy] Support Android Q new split sepolicy setup
– [MagiskInit] Move sbin overlay creation from main daemon post-fs-data to early-init
– [General] Service scripts now run in parallel
– [MagiskInit] Directly inject magisk services to init.rc
– [General] Use lzma2 compressed ramdisk in extreme conditions
– [MagicMount] Clone attributes from original file if exists
– [MagiskSU] Use ACTION_REBOOT intent to workaround some OEM broadcast restrictions
– [General] Use skip_mount instead of auto_mount: from opt-in to opt-out
Magisk 18.1 Stable:
– [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
Magisk 18.0 Beta:
- Migrate all code base to C++
- Modify database natively instead of going through Magisk Manager
- Deprecate path /sbin/.core, please start using /sbin/.magisk
- Boot scripts are moved from <magisk_img>/.core/<stage>.d to /data/adb/<stage>.d
- Remove native systemless hosts (Magisk Manager is updated with a built-in systemless hosts module)
- Allow module post-fs-data.sh scripts to disable/remove modules
- Use component names instead of process names as targets
- Add procfs protection on SDK 24+ (Nougat)
- Remove the folder /.backup to prevent detection
- Hide list is now stored in database instead of raw textfile in images
- Add “–status” option to CLI
- Stop unmounting non-custom related mount points
- Add FLAG_INCLUDE_STOPPED_PACKAGES in broadcasts to force wake Magisk Manager
- Fix a bug causing SIGWINCH not properly detected
- Support new av rules: type_change, type_member
- Remove all AUDITDENY rules after patching sepolicy to log all denies for debugging
- Properly support extra_cmdline in boot headers
- Try to repair broken v1 boot image headers
- Add new CPIO command: “exists”
Magisk Manager Changelog:
Magisk Manager v7.5.1
– Fix toggling app components in MagiskHide screen
– Update translations
Magisk Manager v7.5.0
– Support new MagiskSU communication method (ContentProvider)
– Fix several issues with hidden stub APK
– Support using BiometricPrompt (face unlock)
Magisk Manager v7.4.0
– Hide Magisk Manager with stub APKs on Android 9.0+
– Allow customizing app name when hiding Magisk Manager
– Generate random keys to sign the hidden Magisk Manager to prevent signature detections
– Fix fingerprint UI infinite loop
Magisk Manager v7.3.5
– Sort installed modules by name
– Better pre-5.0 support
– Fix potential issues when patching tar files
Magisk Manager v7.3.4
– App is now fully written in Kotlin!
– New downloading system
– Add new “Recovery Mode” to Advanced Settings
Magisk Manager v7.3.0/1/2
- HUGE code base modernization, thanks @diareuse!
- More sweet changes coming in the future!
- Reboot device using proper API (no more abrupt reboot)
- New floating button in Magisk logs to go to the bottom
Magisk Manager v7.1.1
- Support the new module format
- Support per-application component granularity MagiskHide targets (only on v19+)
- Ask for fingerprint before deleting rules if enabled
- Fix the bug that causes repackaging to lose settings
- Several UI fixes
Magisk Manager v7.0.0
- 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
Download Magisk Zip and Magisk Manager
Latest version Magisk 20.1 and Magisk Manager 7.4.0
Steps to Install Magisk Zip on your phone:
There are two methods to install this on your device. If you have TWRP Recovery, then you can now flash the flashable zip without any hassle. All you have to do is just download the latest version from the link given below to enjoy systemless root and their benefit on your device. Also, make sure to download the latest Magisk Manager apk file.
There are several ways to install Magisk on your Android smartphone, and the one you go for depends on the current state of your device. If your phone is not rooted at all, you can install Magisk and gain systemless root access on your device in one pass by using TWRP Recovery. If you don’t have TWRP Recovery, then you can either install the TWRP recovery or you can simply follow the second method by patching the stock boot image (kernel) and flash the modified boot on your device.
In case your phone is already rooted and you want to use Magisk, you can unroot your phone and remove all existing root software on your phone, and then install Magisk using TWRP. Here is the complete guide on how you can switch over from SuperSU to Magisk. I’ll be covering all of these methods in this guide.
Method 1: Install using TWRP RecoveryWatch The Video on How to Download & Install Magisk Manager and Root your phone Using TWRP
First things first, let’s see how to install TWRP Recovery on your Android smartphone
TWRP Recovery is a custom recovery that offers far more features and functionalities than the default Android recovery. With the default Android Recovery, you can only perform a factory reset, wipe data and cache and carry out some other minor functions. but with TWRP Recovery, you can install custom modules, flash custom ROMs, install custom firmware, root your Android smartphone, perform a full Nandroid backup and carry out a host of other functions.
TWRP is short for TeamWin Recovery Project, and it’s an open-source custom recovery image for Android smartphones developed by, (you guessed right) TeamWin. In this guide, we’ll be using TWRP Recovery to install Magisk and root your Android device.
The fastest way to install TWRP is via Fastboot (pun unintended), and as most Android smartphones have fastboot, I’ll be covering only this method in this article. If you already have TWRP installed, you can skip this step.
Note: If you own a Samsung smartphone, follow this guide to install TWRP using Odin.
Steps to Install TWRP Recovery:
We already covered many guides on how to install TWRP Recovery on each device. In case if you are here for the first time, then let’s make things more clear. Make sure to download and keep the required drivers and files on your PC.Watch The Video on How to Download & Install Magisk Manager and Root your phone
- Download the latest Android USB drivers [Here is the guide on how to install Android USB drivers]
- Download TWRP Recovery for your device from the here
- Download ADB drivers on your PC and extract it to C:/ drive.
- You need to Unlock the bootloader on your device.
- First of all, Install ADB and Fastboot on your PC.
- Enable Developer Mode on your Android device by tapping continuously on Build Number on your phone About Phone settings.
- Open up the Developer Settings, find the OEM Unlocking settings and toggle it on.
- Next, you need to unlock your bootloader. If you’ve performed an advanced tweak on your device before, you’ve probably done this, and you can skip this step. Note that unlocking the bootloader will wipe your device data.
- Run adb on your PC with your device connected via USB cable.
- If your smartphone is running on Lollipop (Android 5.1) or lower, run the following commands
fastboot oem unlock
if it’s running on Marshmallow (Android 6.0) or higher, run
fastboot flashing unlock
- Use your Volume buttons to move up and down and highlight Yes, then press your power button to confirm the process and your bootloader will be unlocked.
- Download the latest TWRP image file here and extract it into the same folder in which you installed ADB and Fastboot.
- Power off your device.
- Boot the device into the bootloader. To do this, press the Volume up and Power buttons together until the bootloader menu comes up.
- Connect the device to your PC via USB.
- On your PC, navigate to your ADB installation folder. Right-click on any space within the folder while holding the shift key on your keyboard, and click Open command window here.
- Run the following command in the open command prompt.
fastboot flash recovery [filename.img][su_note note_color=”#fefdef” text_color=”#000000″]Please replace [filename.img] with the name of the TWRP Recovery img file you downloaded followed by the .img extension.[/su_note]
- The flashing process will begin. Once done, run
to reboot the device. You now have TWRP installed on your Android smartphone.
Install Magisk using TWRP Recovery
- If you already moved the latest Magisk zip to your root of internal storage, then you can simply boot into TWRP Recovery.
- In TWRP Recovery Interface, Tap on Install Button.
- Navigate to internal storage where you transferred or downloaded the Magisk zip file and proceed. Tap on the file and proceed.
- Once selected, Now you have to Swipe to confirm the flash.
- When the flashing process completes, you can tap on the reboot button to reboot your phone.
That’s it! You can now download and install the Magisk Manager apk to enjoy systemless root on your device.
How to Verify if your phone has a systemless root?
- Download and install the APK above, and launch the Magisk Manager app.
- To verify that you have a systemless root, check the top of the screen and if you see all options with Green Tick which means you have successfully rooted and bypassed SafetyNet.
Method 2: Install Magisk using Patched Stock Boot Image
To do this, you need to patch the stock boot image. You can follow this method by installing the Magisk Manager on your device.
- First of all, you need to grab the stock boot image for your current firmware installed on your phone. You can always get this file from the stock firmware or extract (Read) it using tools like CM2, Miracle Box, NCK, etc.
- Download and Install the latest Magisk Manager APK from above
- Download ADB drivers on your PC and extract in C:/Drive
- If you have the Stock Boot image, then moe the boot image to your phone’s internal storage.
- Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
- Tap on “Patch Boot Image File”.
- Navigate to internal storage and select your phone’s boot image that you transferred earlier.
- Wait for a couple of seconds. Magisk will start patching the boot image.
- Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and move it to the C:\ drive adb folder on your PC.
- In the same folder, hold the SHIFT key and right-click on an empty space.
- Select “Open PowerShell window here”.
- Now you need to boot your device into Bootloader/Fastboot mode.
- Connect your phone to the PC using USB Cable
- In your command window shell, you need to type the below command to install Magisk and root your Android device.
fastboot flash boot patched_boot.img
- Once done, reboot your phone using:
Once your phone reboots, open the Magisk Manager and confirm that the installation was successful.
Now, if you wish to uninstall Magisk for any reason, the steps below will assist you in doing so. The most certain way to do this is via the Magisk Manager app itself. Before you uninstall Magisk, make sure to disable and remove all the modules.
How to Uninstall Magisk and Unroot Android
You can now follow our separate guide to uninstall Magisk on your device.Uninstall Magisk very easily
- Open the “Magisk Manager” app on your phone.
- Now Tap on the “Uninstall” button
- Now confirm uninstallation by taping the “COMPLETE UNINSTALL”
- Once the uninstallation process is done, you can reboot your device.
Note: You can also flash the Magisk Uninstaller zip using TWRP Recovery to uninstall.