![]() ![]() That means having the system partition back the same way it was when you first started using the ROM. 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. Note: There are some things that you need to do before getting started with the guide. 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. That said, you don’t need to have SuperSU on your device before using Magisk. That’s the most important part of understanding. 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. When you make the switch from Chainfire’s SuperSU to Magisk SuperSU, you aren’t leaving behind SuperSU altogether. 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. Thus, the number of people rooting heir phones dropped. 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. Android was now coming up with features like Android Pay that would not work if you had root access - even with the systemless version. 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.Ĭhainfire 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. The result was the way Chainfire used to make SuperSU go through the system partition couldn’t happen anymore. The change was forced by Android who decided to step up security more in comparison to what it was in the past. The only thing was whether or not a custom recovery image was available for your device or not.Įven 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. It was basically just the one version of SuperSU that you needed to flash from a custom recovery for each Android version. There are no tools out there that can root as many devices as the SuperSU could. Even if you include the one-click rooting tools, my guess would be that SuperSU was still rooting more devices. ![]() ![]() 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. For about as long as I can remember, SuperSU was always the most popular way for people to get root access. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |