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.
Download Magisk to Root Android 6.0.1 (Marshmallow)
Use the links below to download the versions of Magisk that work with Android 6.0.1 Marshmallow:
Note: Use the latest version possible. And if that does not work, downgrade to the one previous until one works for your device.
How to Install Magisk
There are two general methods for installing Magisk. Most people install it via the TWRP custom recovery image. However, there is also a method to install Magisk without TWRP.