Related
Most of us were talking about Towelroot over in Jcase's PIE thread or over in collinjames' thread, but I think it's time it deserves it's own thread.
UPDATE:
@iKrYpToNiTe made the awesome TowelPieRoot which makes this method easier to use. You can still use this thread to root your phone, but I will be using his method from now on. Happy rooting!
Important Links:
Geohot's original post.
Towelroot's Homepage
Mod Strings
What is Towelroot?
Towelroot is a rooting method for most android phones, and it uses an apk to obtain root (dead simple too, push one button, no need for other tools and workarounds). (source)
Why do we use Towelroot in conjunction with PIE?
PIE nor Towelroot disables write protection. Both of them offer a temporary root that has to be applied after a reboot. The advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then Towelroot allows you to continue rooting "on the go" in the future without needing a PC.
How does it work with the Moto X?
It works the same as PIE. It gives root access but the device is still write protected. It is also temporary and must be reapplied after a reboot. However, a soft/hot reboot can keep the root access, due to soft/hot reboots only rebooting the graphical Android shell.
What does it work on?
XT1049 - Republic Wireless, not confirmed, should work.
XT1052 - European
XT1053 -T-Mobile US, not confirmed, should work.
XT1055 - US Cellular, not confirmed, should work.
XT1056 - Sprint, not confirmed, should work.
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM
XT1060 - Verizon
How do I use this tool?
Remember to apply PIE first!
1. On your device, go to here.It will start to download the .apk
3. On your device, go to Settings>Security>Unknown Sources and tick the box.
4. Run the downloaded apk, tr3.apk
5. Press "welcome to towelroot" 3 times.
6. Replace the last 0 with a 1, due to modstrings.
7. make it ra1n
Your device should now be rooted and you should be able to use apps such as Greenify and Titanium Backup.
Some applications that should work with root, might not work with this method.
Some people have experimented with using Superuser apps, but I have not seen a consistent method to use one.
How are we keeping root after reboots?
We aren't rebooting! Seriously, we soft/hot reboot which allows us to keep root after a graphical reboot. And even if you do reboot, you can always reapply the root with Towelroot. You just need to make sure you have applied jcase's PIE before hand.
Xposed:
jpond83 posted up some instructions in the PIE thread about how to get Xposed to work:
Make sure you have installed PIE before you try to use Xposed or it will NOT work. View jcase's PIE thread for more details.
jpond83 said:
1) install towelroot. Xposed installer, Busybox installer, power menu
2)run towelroot, click "welcome to towelroot", replace 0 with 1, make it rain.
3) run xposed and click install
4) run busybox installer and click install
5) run power menu and click "hot reboot"
6) enjoy root without using a PC.
Click to expand...
Click to collapse
Current problems/bugs
Some users have problems with soft/hot rebooting. Reapply PIE.
Random reboots.
Warning about using this exploit
Myself or anyone that has helped develop this are not responsible for anything that occurs to your phone by using this method.
As for this thread, feel free to post your experiences with this tool or any supplements to add.
I'm glad this finally has a dedicated thread. Good job OP
I finally got it working. When I installed SuperSU it was lagging. But I kept it off. I even have hkthememanager running with KitKat all white settings from the nexus forum.
Sent from my XT1058 using XDA Free mobile app
The softboot/hot boot issue comes from not having busybox installed.
jpond83 said:
The softboot/hot boot issue comes from not having busybox installed.
Click to expand...
Click to collapse
I've installed 3 different Busybox installers:
Busybox by Stephen (Stericson)
Busybox Installer by JRummy Apps Inc.
Busybox X by Robert Nediyakalaparambil [root]
The first and the third one said they installed successfully, but the second one did not.
Even after 2 installations succeeding, I was still unable to soft/hot reboot.
Any ideas?
I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.
jpond83 said:
I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.
Click to expand...
Click to collapse
Guessing that is the Busybox Installer , I just get this when I try to install it. I have root access, but Busybox is not installing.
But when I use Busybox by Stephen, it says it installs correctly, and my Busybox checker says it does too, but Power Menu still won't Hot Reboot.
Have you ran pie root before? It needs to be ran on the device once before for it to work.
jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?
dier325 said:
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?
Click to expand...
Click to collapse
Yes, its a must. It should only need to be ran once. After that you should never need it again unless you factory reset.
jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.
KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Towelroot can work just by itself, but PIE adds some functionality that allows for easier softbooting.
jpond83 said:
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.
Click to expand...
Click to collapse
I'm sorry that it bothers you so much that I have a question I'm asking. But if you must know, YES I READ. I've read this thread, the PIE thread, and Does Towel Root have any potential in the Motorola field?
And if you can read, you would know that you didn't even answer my question of "why use both?". Instead you just sort of flaming me for asking something and said pie only needs to be run once which is already stated very clearly in what I quoted.
What I'm getting at with my question is something that is implied, but not stated.....
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
But it does beg a few more questions (at least by someone who is READING all of this, but not using either PIE or TowelRoot)...
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?
KidJoe said:
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
This is a great explanation of why we are using both. I will add a paragraph to the OP that paraphrases what you just said.
KidJoe said:
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Click to expand...
Click to collapse
Towelroot alone works, but we've found that some applications (i.e. Xposed, Busybox) don't work unless you have PIE. Using them together allows us to use them.
KidJoe said:
[*]Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
Click to expand...
Click to collapse
The method of each one must be done in order but it does not matter which one you apply first to the device. In fact I just had Towelroot running on my device and then applied PIE allowing for Xposed to work.
KidJoe said:
[*]What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
Click to expand...
Click to collapse
PIE allows us to keep Busybox installed on the device which allows us to Soft/hot reboot.
KidJoe said:
[*]If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?
Click to expand...
Click to collapse
I want to remind everyone that there are very few of us who are using both of these methods together currently. It is fine for these questions to be brought up for the uninitiated. As for them working together, I think Jcase stated that he wants to move away from the X, as well as I think he is on holiday due to his current signature. I don't know about Geohot but some people have created a thread over in the Moto G forum raising some money to buy the device for him after he said he would try to work on it if he had one.
I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary
KidJoe said:
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
I have added another section to the OP explaining the situation.
cell2011 said:
I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary
Click to expand...
Click to collapse
Adding them together allows you to root without having to use a PC if you do reboot your device, say it dies.
Thanks guys for clearing this up. I think Towel root should be renamed to something less middle east reference and it would be welcomed more.
So basically if we want more functionality with our root, we should do PIE first? I clicked over onto the PIE page but didn't really how it's done. I have towelroot down, but it seems PIE is a good idea to use in combo with towel root. I could be missing something though cause I'm in the XDA app at work.
I do understand though that PIE is a one time thing and we should just use towel root thereafter when we reboot and need to reroot again.
Sent from my XT1060 using XDA Free mobile app
Using PIE in conjunction with Towelroot allows you to use apps such as Xposed.
Sent from my XT1060 using XDA-FORUM, powered by appyet.com
I'm wondering why you root your phone or choose not to. My reasoning for both is below.
On the root side:
*I'm coming from a rooted 5x. With the introduction of Nougat, I lost any way to a power menu (via Xposed) screenshot. So my preferred method without that option was using a home button remapping app (Homebot https://play.google.com/store/apps/details?id=com.abast.homebot ) that opened up my screencap app ( Screencap https://play.google.com/store/apps/details?id=com.symcoding.app.screenshots ) but there screencap app requires root. It's clunky, but it works. I've tried every other screencapping app I can find and nothing works as easy as power menu>screenshot. I could use power+power down, but my case makes that difficult. It's not worth downgrading the OS to use Xposed for this. But I'm on the fence if it's worth rooting my 6p.
* I like Xposed mods that allow me to modify things like going to text only battery percentage. Still not worth downgrading to Marshmallow though.
On the no rooting side:
*I won't be forever chasing a way to use or being without the ability to use Android pay.
Your thoughts/reasoning?
Sent from my Nexus 6P using Tapatalk
I mean, you don't have to root.
You can unlock the bootloader and flash a custom ROM (such as Pure Nexus). With Pure Nexus, you don't have to flash SuperSU, which gives you root access, or you can flash SuperSU, up to you.
Either way, there is an option in the ROM to add screenshot to the power button menu, and there is no need for Xposed (which doesn't have support for N yet anyways).
Going between root access and no root only takes 30 seconds, and you can switch between the two anytime you want. To add root, simply flash the SuperSU. To unroot, go into SuperSU menu and click the unroot button.
The only benefit I see without root is the ability to use Android Pay. Android Pay will still work on the Pure Nexus ROM, as long as you don't flash SuperSU.
Sent from my Nexus 6P using XDA-Developers mobile app
Because even factory images are bugged to no end. That's why I root...
Sent from my Pixel using Tapatalk
I root so I can use Adaway and High Brightness Mode Widget
Well, if you're not sure, don't root. It is a security risk. Also if you ever want to pay with your phone, then you don't root.
Me, I always had rooted phones, because
- I like to be in total control of all my computers, no matter if stationary or mobile.
- Also when I develop my rom, it helps if I can remove all traces of a system app from the phone itself.
- Also, because I develop my rom, I regularly make TitaniumBackups when trying out a bigger change in the os.
- Makes me all powerful and grownup
I just rooted my 6P yesterday. My main driver was to be able to edit the build.prop file to get the Google Assistant on my 6P, which is supposed to be a Google Pixel exclusive feature. That worked for me, and I'm enjoying the Google Assistant, although I'd say it's still very much in its infancy. However, I did lose the ability to use Android Pay though , but I've been trying to find a workaround for using Android Pay on my rooted 6P. I believe it can be done on a systemless root (like SuperSU 2.76+ IIRC). I've seen some data points on that on another 6P thread. My Android Pay is still being very finicky though.
---------- Post added at 07:00 PM ---------- Previous post was at 06:51 PM ----------
vikramjatt11 said:
I mean, you don't have to root.
You can unlock the bootloader and flash a custom ROM (such as Pure Nexus). With Pure Nexus, you don't have to flash SuperSU, which gives you root access, or you can flash SuperSU, up to you.
Either way, there is an option in the ROM to add screenshot to the power button menu, and there is no need for Xposed (which doesn't have support for N yet anyways).
Going between root access and no root only takes 30 seconds, and you can switch between the two anytime you want. To add root, simply flash the SuperSU. To unroot, go into SuperSU menu and click the unroot button.
The only benefit I see without root is the ability to use Android Pay. Android Pay will still work on the Pure Nexus ROM, as long as you don't flash SuperSU.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Are you sure that the custom TWRP recovery will remain if you unroot using the button within SuperSU? In the Nexus 6P rooting guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), step 2, dealing with installation of custom recovery TWRP, says that TWRP "won't stick" if you don't immediately flash SuperSU after booting into TWRP recovery the very first time. I can attest to that, because it happened to me. I had to reflash the TWRP img file, reboot into TWRP recovery, and immediately flash the SuperSU on the phone to make TWRP stick. Do you think unrooting thru SuperSU will allow the TWRP to remain, so that you can use Android Pay? Otherwise, you need to do another step of flashing the TWRP before rerooting.
Secondly, do you know if you just need to be unrooted to add cards to Android Pay? Or do you need to be unrooted for even regularly paying with your app? I've not had success adding cards (except for one) to my Android Pay app after rooting. I haven't yet had a chance to test whether I am able to pay while rooted.
One does not need to root.
If it works for you stock, go for it.
I would say though that unlocking the bootloader is a must.
It allows freedom if anything ever gets corrupt.
Do it ASAP because it wipes the device..
istperson said:
Well, if you're not sure, don't root. It is a security risk. Also if you ever want to pay with your phone, then you don't root.
Me, I always had rooted phones, because
- I like to be in total control of all my computers, no matter if stationary or mobile.
- Also when I develop my rom, it helps if I can remove all traces of a system app from the phone itself.
- Also, because I develop my rom, I regularly make TitaniumBackups when trying out a bigger change in the os.
- Makes me all powerful and grownup
Click to expand...
Click to collapse
Magisk takes care of the rooting non rooting Android Pay fiasco.
Sent from my Nexus 6P using Tapatalk
inprince said:
I just rooted my 6P yesterday. My main driver was to be able to edit the build.prop file to get the Google Assistant on my 6P, which is supposed to be a Google Pixel exclusive feature. That worked for me, and I'm enjoying the Google Assistant, although I'd say it's still very much in its infancy. However, I did lose the ability to use Android Pay though , but I've been trying to find a workaround for using Android Pay on my rooted 6P. I believe it can be done on a systemless root (like SuperSU 2.76+ IIRC). I've seen some data points on that on another 6P thread. My Android Pay is still being very finicky though.
---------- Post added at 07:00 PM ---------- Previous post was at 06:51 PM ----------
Are you sure that the custom TWRP recovery will remain if you unroot using the button within SuperSU? In the Nexus 6P rooting guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), step 2, dealing with installation of custom recovery TWRP, says that TWRP "won't stick" if you don't immediately flash SuperSU after booting into TWRP recovery the very first time. I can attest to that, because it happened to me. I had to reflash the TWRP img file, reboot into TWRP recovery, and immediately flash the SuperSU on the phone to make TWRP stick. Do you think unrooting thru SuperSU will allow the TWRP to remain, so that you can use Android Pay? Otherwise, you need to do another step of flashing the TWRP before rerooting.
Secondly, do you know if you just need to be unrooted to add cards to Android Pay? Or do you need to be unrooted for even regularly paying with your app? I've not had success adding cards (except for one) to my Android Pay app after rooting. I haven't yet had a chance to test whether I am able to pay while rooted.
Click to expand...
Click to collapse
Yes, when you flash the Pure Nexus ROM, it will not have root by default. So if you flash the ROM, google apps, and vendor image and then reboot, the ROM will work as needed, but will not have root. In order to get root, you have to flash the SuperSU file in TWRP.
In Android Pay, you will need to be on the Pure Nexus ROM with no SuperSU flashed in order to add cards or use Android Pay regularly when paying. But you can simply flash the SuperSU file when you need root, and then remove root by going to the SuperSU app.
Hi everyone,
I just got my Huawei Nova and i wonder if there is any easy rooting-guide or app like KingRoot.
I used this app for Honor 7 and others and it's a great one, but i don't know if it's working for the Nova.
If possible, i don't want to change recovery/rom, only small root that allows me to really control my phone.
Thanks yall
At the moment, there are no automated tool or any application on XDA unfortunately...
The easiest way is unfortunately the ADB/Fastboot way.
It's not that hard, but you have to be a bit careful going through each step:
- Install ADB/Fastboot tools, and the drivers
- Unlock bootloader (you'll need an unlock code)
- Flash TWRP recovery
- Flash Root.
You'll find pretty much all the info needed in the Nova forums, but it is a bit of research. Nothing that is worth having is easy to get!
Yes, all info is in the TWRP post under development forum. Weird issue with data partition in TWRP.
Thank you for your replies. I've seen the TWRP post with all the instructions, i just don't want to take any risks with my brand new phone for now.
That's why i used King Root app before, one tap and it does everything, without flashing anything.
Anyway, i'll wait for some time then.
Again, thank you very much.
Is re-locking the boot loader after rooting possible without losing root again?
Found the tool?
Hi
I want to know is there any way to root without using pc. My bootloader is unlocked. Need to flash twrp.
mapbond said:
Hi
I want to know is there any way to root without using pc. My bootloader is unlocked. Need to flash twrp.
Click to expand...
Click to collapse
Don't think so, no. Not without root anyway.
Kingroot might work but it's a horrible app that isn't worth the trouble it creates. If Kingroot works on this phone then you can probably install a custom recovery via something like Flashify or the TWRP app. The problem with Kingroot is that it's basically malware. It installs adware on your phone and won't give root access to anything that interferes with its functioning like Adaway or an alternate root app. It also sends God only knows what data from your phone to China. You are honestly better off not being rooted at all than using Kingroot. There are instructions for rooting with Kingroot and then switching root to SU but unless the instructions are extremely up to date they will not work. Kingroot is updated with the specific purpose of preventing you from being able to do anything that reduces the power Kingroot has over your phone. It can be uninstalled but the app makes certain you completely lose root functions before that happens.
no support
jhs39 said:
Kingroot might work but it's a horrible app that isn't worth the trouble it creates. If Kingroot works on this phone then you can probably install a custom recovery via something like Flashify or the TWRP app. The problem with Kingroot is that it's basically malware. It installs adware on your phone and won't give root access to anything that interferes with its functioning like Adaway or an alternate root app. It also sends God only knows what data from your phone to China. You are honestly better off not being rooted at all than using Kingroot. There are instructions for rooting with Kingroot and then switching root to SU but unless the instructions are extremely up to date they will not work. Kingroot is updated with the specific purpose of preventing you from being able to do anything that reduces the power Kingroot has over your phone. It can be uninstalled but the app makes certain you completely lose root functions before that happens.
Click to expand...
Click to collapse
i tried kingroot there is no support from there end. so i uninstalled it.
You can't. You need to unlock the bootloader if this phone and this requires a PC
Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.
You have to re run the root file on your pc.
helllmonkey said:
Is there any easy way to get root back? Do I just flash a previous version of SuperSU with flash fire? Thanks.
Click to expand...
Click to collapse
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.
nyr2k2 said:
Just need to run the root.bat file from your PC and you'll be good to go. That can be found in the thread on how to root your phone, install Xposed, etc.
Then make sure not to to update SU. There are a few workarounds to simply avoiding the update, but in general you don't want to take it. It will make you lose root every time you update.
Click to expand...
Click to collapse
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.
cn2661 said:
Actually is there a way to stop it from popping up, asking me to Update SuperSU or not everytime when I press auto update for my other apps in the Google Play?
There were once or twice I mistakenly pressed yes when updating other apps (obviously when I was daydreaming or sleepwalking) and I will have to root it again.
Click to expand...
Click to collapse
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.
nyr2k2 said:
If you long press the notification in the notification pull down, you can then turn off app notifications for it. That would stop the reminder and the constant # symbol from sitting in your tray. That's what I did. If you open the app itself it will still tell you the binary needs to be updated, but you can just ignore it. Basically you're running the 2.78 or whatever SU app and binary that installs when you run the root.bat but you have installed the latest version so you don't have to see it in the store. Supposedly the most recent version of the app itself "fixed" the problem of losing root just by installing the app but we can't install the binaries on our phone. So you can try updating it in the store--I'm on 2.82 with old binaries. There's still I suppose a chance you could lose root, but then again you just rerun the root.bat.
So all in all I'd recommend downloading the 2.82 update. Don't try to install the binaries. Hide the notifications. Then you're good to go. If you somehow lose root in the process then rerun the root.bat and look around here further. Someone had another workaround with a modified version of SuperSU, but I never tried that because my setup was fine and I was tired or screwing around, LOL.
This, again, is why I will not buy another phone unless I know it can have the BL unlocked. I want to use Magisk and have a custom recovery. Tinkering around on this thing and risking bricks when you then have to re-flash everything, it just sucks.
Click to expand...
Click to collapse
Cheers mate, perfectly works,
by Updating the SuperSU app, Not updating the SU Binary and long-press notification to shut the notification off.
Peace to the Earth again.:good: