Over the course of history, for as long as we’ve had the pleasure of knowing the Android operating system, gaining root access to it has always been possible. Up until lately, when a new feature called SafetyNet was first introduced, all root apps can always be run at the same time as the apps that didn’t require root access.
In more recent times, however, we have seen the development of apps such as Android Pay. While it’s not a huge deal now, one can only assume that Android Pay—at least for the people using the Android operating system—is going to be very common to use eventually.
The main reason for this likely being the case is it is simply going to be easier to do: battery technology will continue to advance, mobile phones will continue to be used, and it makes sense to have additional services tied to the mobile phone itself, so it is the one object you need to carry instead of a few.
We, somewhat surprisingly, have already seen places like New York City throw away the idea of metro cards for train tickets and now people who ride the public transport can flash their mobile device displays instead, presumably for the same reason of convenience.
Apps like Android Pay are not available to use with rooted device. Before Android Pay was around, when a device got root access it could always run all apps.
Now though, Android has brought out a new feature called Google SafetyNet, specifically designed to stop apps such s Android pay from running with a rooted device. Most of your other root apps will still run: Dumpster, Greenify, Link2SD, just to name a few. But Android Pay, plus other services like Netflix or games like Pokemon Go, are all now protected by SafetyNet and won’t work when it detects you have a rooted device.
You may have thought the answer to this problem would be to get a rooting tool that can go undetected by SafetyNet, but as it turns out, that wasn’t going to be possible due to the nature by which SafetyNet is designed. That left the rooting community stumped, at least for a little while, until something became available for this problem, that up until recently, was only solved by either choosing between having a rooted or device or having an unrooted device and using the apps that wouldn’t work with a rooted device.
Eventually, the solution came by way of Magisk: a new universal systemless root interface that allows for root access, and then offers a switch that can be toggled quickly to turn off the root access when apps like Android Pay need to be used. Once you’re done with the app that would have tripped SafetyNet, you just toggle root access back on again, and you’re using the device with root access again. It’s not a solution that’s as great as using root access all the time, but it’s also the best case scenario after it had become apparent that Google was not going to allow rooted device ever to use these services.
How to Root Android 6.0 (Marshmallow) with Magisk
Download the Magisk installer 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.