[Q] Spontaneously losing root - Moto X Q&A

I rooted my Moto X using Jcase's Pwnmymoto. Then I used this method to restore root after taking the OTA: http://forum.xda-developers.com/showthread.php?t=2466191
The problem that I'm having is that, after some time, I lose root. If I restart the phone, I will get root back and everything is back to normal, but then it will happen again after an undetermined period of time. When this happens, Superuser is unable to update the binaries and Adaway stops blocking ads.
I followed the instructions on the "keep root" thread to the letter, so I'm not sure what would be causing this, but it's annoying. Anyone have an idea of what the cause might be?
Thanks.

Related

[Q] Losing Root

Has anyone had problems with their Moto X losing root? Maybe like every 2 or 3 days my phone loses its root access. There doesn't seem to be any rhyme or reason on why it does. If i reboot my phone, my root access is back and works fine for the next few days and then its gone again until another reboot. Its so weird. It doesn't matter which app that I run. I'm running kitkat now. I had no problems rooting it. I don't recall having the problem when I was running on 4.2
No issues here, I've been rooted and stable for a few months now.
The only time I ever lost root on a phone was when I installed Airwatch for corporate email and apps and stuff. I didn't -know- I was losing root or I never would have done it. Strangely everything that was previously granted SU access worked, but any new requests were not processed.
Have you installed any apps or changed anything else in your system? What method did you use to root?
Is SuperSU just being removed, or it stops working? Sounds strange for sure.
It sounds like you're having the same problem I had, I could be wrong though. Here's the thread I created, give it a shot.
http://forum.xda-developers.com/showthread.php?t=2558916
Turbocom said:
It sounds like you're having the same problem I had, I could be wrong though. Here's the thread I created, give it a shot.
http://forum.xda-developers.com/showthread.php?t=2558916
Click to expand...
Click to collapse
This seems to make sense. I would bet that most people that root are also running MotoWPNoMo (or whatever it is..) as well because things like Xposed and other apps that install as system apps won't work without this, or booting through recovery as described.
I ran it right away because Xposed wouldn't work, and haven't had any issues.
You're not losing root... The issue is that JCase's rooting method uses an exploit to disable write protection, and sometimes the write protection comes back.
If you're on 4.2.2, just run MotoWpNoMo from this thread - > http://forum.xda-developers.com/showthread.php?t=2551113
I don't have any crazy apps or new frameworks installed. That motowpnomo is that for KitKat or 4.2.2?
Sent from my Nexus 7 using xda app-developers app

[Q] Xposed not surviving hard boot.

I've seen this topic mentioned in the forum but I have yet to find an answer that works. Maybe there isn't one, but here goes...
I have a Droid Maxx that shipped with 4.4.2. I rooted it with the PIE Exploit and everything went as expected. I set SuperSU to survival mode, and took the 4.4.4 OTA. This did not seem to kill root access, so again, all was well. Then, I installed Xposed and rebooted...fine. Installed some modules, configured them, rebooted..."Xposed is not active." So, I updated the framework and soft rebooted...everything works. However, if I hard reboot at any time, I get the "latest version is not active" error in Xposed. The only thing that fixes it is to update and soft reboot.
Mind you, root access is surviving these hard reboots. I check with SuperSU, Terminal and Root Checker each time just to be sure, and root is not failing. So what the heck is the issue with Xposed? Every time I see this topic brought up, the only advice is to update Xposed or to make sure you have root. Check and Check. Unless I'm missing something, it seems like root is permanent since it survives reboot. I've tried uninstalling/reinstalling everything one at a time, denying/granting root access to Xposed, etc. but nothing fixes the problem.
Is there a solution to this that I'm not seeing, or is this actually an unfixable bug?

[Q] SuperSU reinstalls itself after reboot (after full unroot).

When I purchased my Droid Maxx it was running 4.2.2 and I used the PIE exploit to root it. At the time, I didn't realize that allowing the 4.4.4 OTA update would completely frag the root so I took it. Now, on 4.4.4 I of course have very buggy and inconsistent root access. So, I decided to just unroot and forget about it for this phone. To that end, I ran a full unroot from SuperSU and the app disappeared. Great...until I rebooted and it came back. I went back into the app, disabled it via the app settings, full unroot again, and again the app reappears on reboot. I can't delete the apk from the System folder because even with SuperSU enabled it won't grant me write access (see above: root fragged). So what the hell am I supposed to do? The phone is essentially unrooted, but on every reboot, regardless of unroot attempts, SuperSU reinstalls itself.
Any ideas on how to get rid of it?
Either root it properly and use that to remove it, or reflash your full stock firmware.

Randomly Lost Root? - No Updates/OTAs applied

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.

Having Some Trouble. Lost my Root Access, Can't Seem to get it back

Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Disable OTA
Dmriskus said:
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Click to expand...
Click to collapse
1. Disable updates, link one post up
2. Root in TWRP
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Categories

Resources