Has anyone managed to get rootkeeper or supersu survival mode working? I wanted to try and use pingit like i have on previous phones but the supesu uninstall always fails
Related
How is temporary unroot supposed to work? I tried to temporarily unroot my Note 3 (rooted with towelroot) and I figured after I rebooted I could open the SuperSU app and reenable it. But it says there is no Su binary installed. When I click OK the app closes. I can't ever deactivate the temporary unroot.
I've looked EVERYWHERE to see if I'm missing something but there are ABSOLUTELY ZERO instructions on how to temporarily unroot then reactivate the reroot.
Hello? Is anybody there? No help for this problem?
This problem should be fixed in the latest SuperSU version. You will have to re-root and update to the latest.
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.
Has anyone unroot via SuperSU and managed to update via OTA ? Thanks
User @Mnemoch shared with me that he managed to do that. He did full unroot in SuperSU, rebooted a couple times, then tried sideloading and the OTA worked fine.
But do note that he rooted with chainfire autoroot, if your method was different you may have different results.
I tried turning off\disabling root to get Android Pay to work and now I can't get root back.
Whenever I open SuperSU it just says the binaries are missing. I've tried flashing the SuperSU zip in the recovery, but it still just says the binaries are missing.
I've also tried uninstalling SuperSU from the Play Store, and it just removes the latest update, doesn't actually uninstall it.
Ideas?
incarceration said:
I tried turning off\disabling root to get Android Pay to work and now I can't get root back.
Whenever I open SuperSU it just says the binaries are missing. I've tried flashing the SuperSU zip in the recovery, but it still just says the binaries are missing.
I've also tried uninstalling SuperSU from the Play Store, and it just removes the latest update, doesn't actually uninstall it.
Ideas?
Click to expand...
Click to collapse
There will be no root support for android pay. Explanation here
Yeah I know, that's why i was trying to temporarily get rid of root, but now i can't get root back. Any ideas how I can? SuperSU just keeps telling me there aren't any binaries, even when i try to flash the zip
The exact same thing happened to me when trying out android pay. Did you ever figure this out? Thanks!
Now that I want to update my Moto X Play via OTA from 6.0 to 6.0.1, I wanted to use my standard procedure: deactivate adaway, full unroot, do OTA.
Problem is that unroot fails. A simple message "deactivate root failed" (or similar, my message is German) with an ok button appears.
I rooted using SuperSU 2.62-3 and updated the app and binaries to official 2.65. Had a flashify backup with only 2.62-3, but there unroot also did not work. Is there an easy way to make unroot work? Can I do any logfiles to analyze the problem unroot has?