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.
Download Magisk to Root Android 6.0 (Marshmallow)
Use the links below to download the versions of Magisk that work with Android 6.0 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.