For about as long as I can remember, SuperSU was always the most popular way for people to get root access. Sure, plenty of individuals preferred doing it the easier way with a one-click rooting method, but outside of the one-click root tools, it was SuperSU — and by a long margin. Even if you include the one-click rooting tools, my guess would be that SuperSU was still rooting more devices. There are no tools out there that can root as many devices as the SuperSU could. It was basically just the one version of SuperSU that you needed to flash from a custom recovery for each Android version. The only thing was whether or not a custom recovery image was available for your device or not.

Even though there was still only one version of SuperSU that you needed per Android version, there was a significant change in recent years with the way that SuperSU had to go about getting root access. The change was forced by Android who decided to step up security more in comparison to what it was in the past. The result was the way Chainfire used to make SuperSU go through the system partition couldn’t happen anymore. The change first came about during Android 5.1.1 Lollipop, and it was official news to the world by the time Android 6.0 Marshmallow had a SuperSU version made available.

Chainfire eventually made a version of SuperSU called “systemless root.” The systemless root that no longer went through the system partition did manage to grant people root access still, but there wee still some things that couldn’t work with Chainfre’s systemless root version of SuperSU. Android was now coming up with features like Android Pay that would not work if you had root access — even with the systemless version. Netflix is another. It went on like this for a very long time (all the way until now) that people couldn’t use a smartphone that had root and Android Pay or Netflix at the same time. Thus, the number of people rooting heir phones dropped.

Well, it now looks like Chainfire’s SuperSU’s time at the top is coming to an end as a new tool has become available that manages to solve all the problems that people were facing with Chainfire’s SuperSU.

When you make the switch from Chainfire’s SuperSU to Magisk SuperSU, you aren’t leaving behind SuperSU altogether. You then run Magisk over the top of the SuperSU to go from SuperSU’s systemless root to Magisk’s full systemless root that is a better version of the systemless root than what SuperSU had — because Magisk completely bypasses SafetyNet which allows for things like Android Pay. That’s the most important part of understanding. That said, you don’t need to have SuperSU on your device before using Magisk. Magisk is a root method in itself, and you can install it directly from Team Win’s TWRP Recovery without needing to install Chainfire’s SuperSU first.

Note: There are some things that you need to do before getting started with the guide. One of the key things about getting Magisk to work is to make sure you start by having all system files back how they were when you started using the stock ROM before you try using the tool. That means having the system partition back the same way it was when you first started using the ROM. For example, if you are using an app like Ad Away that changes the host files from the system partition, you’ll need to remove that application from your device. Also, if you have installed Titanium Backup in the past and removed any of the stock apps, you’ll need to flash a new stock ROM and put those back, because the stock apps are always from the system partition also. On the other hand, if you have only frozen application with Titanium Backup (with the paid version of Titanium) then you can just unfreeze them without having to do anything else. They’ll still be on the system partition.

How to Install Magisk Root Tool on Android 6.0.1 Marshmallow

Download the Magisk SuperSU from the Downloads section of the XDA-Developers thread.

If you already have rooted your device, you’ll need to unroot it now before going ahead with the installation of Magisk. If you have used TWRP and then flashed Chainfire’s SuperSU, you can just remove the SuperSU by opening it up and then choosing to uninstall it from the menu. For everyone else, you might be interested in installing the unSU script instead.

You can only use Magisk if there is a custom recovery image available for you to install. You can look for a custom recovery image made for your device from the TWRP website. Remember that before you can install a custom recovery image, you need to have the bootloader unlocked first. The way you unlock the bootloader changes depending on your smartphone manufacturer. If you find a guide made for your manufacturer, then chances are you can follow it because it’s the same for all devices from the one manufacturer.

Find out the steps required to boot your smartphone into the custom recovery. The way manufacturers choose to enter recovery mode changes depending on who it is, but the good news is that booting into custom recovery is always the same steps as booting into the stock recovery for your phone because it just replaces it. So, all you really need to do is find out what steps you need to boot your device into the standard recovery mode that all devices come with and then you’ll be able to boot to the custom recovery as well.

Once you are in the custom recovery, tap on the “Install” button and then tap on the Magisk SuperSU zip file. Then to install the zip file you have selected, tap on the “Install Image” button (if you are using TWRP Recovery.) You’ll also need to swipe at the bottom of the phone’s display to confirm the installation of the zip file if it is TWRP Recovery.

After the Magisk SuperSU is installed, you then need to reboot the phone from the TWRP Recovery menu. Once your phone boots back up again, it’s time to install the Magisk Manager application directly on the phone. Before you can install it, though, you first need to enable the Unknown Sources option from the Android Settings. To do that, swipe down from the top of the Android homecreen to pull down the notification shade, and then tap on the “Settings gear icon” at the top.

Tap on the “Security” link from the Settings.

Inside the settings is the “Unknown Sources” option that you now need to tap on.

You’ll get a message letting you know about the risks of enabling the Unknown Sources before it turns on for you. Tap on the “OK” button to continue.

The Unknown Sources toggle is now turned on.

Next, you need to get the Magisk Manager application from the XDA-Developers thread under the same Downloads section that you got the Magisk SuperSU earlier. Download it like you would any other app and then tap on the ‘Install” button to install it on your device.

The Magisk Manager sends a superuser request to your device. Tap on the “Grant” button to continue.

You’ll need to allow Magisk Manager permissions to access your files from the device if you want to get the best experience. Tap on the “Allow” button here.

It lets you know that Magisk Manager is not yet installed. Tap on the “Go to Install” section” to continue.

At the bottom of the next screen is the “Download and Install” button that you need to tap on now.

You can choose to view the release notes if you want before installing. When you are done, just tap on the “Install” button, and then the Magisk manager is finally installed.

Wait until you get the “Installation succeeded!” message on the phone’s display and then tap on the “Reboot” button.

Once the reboot is complete and the phone starts up again, you can start using Magik on your device to have root access as well as Android Pay and Netflix working again.

Enter your email address:

Delivered by FeedBurner