I was rooted on my Verizon non-DE 4.4 Moto X, and kept delaying the 4.4.2 OTA. I had rooted with slapmymoto and MotoWPNoMo. Last night, drunk, I guess I accepted it at some point. It looks like MotoWPNoMo worked as advertised, and I still have root access (at least verified with the Root Checker app). But Xposed is not working (it was with 4.4). It says "The latest version of Xposed is currently not active. Did you install the framework and reboot?" I've done that many times, I've uninstalled and reinstalled rebooting multiple times through out the process. I'm not entirely sure if the problem is with root, or Xposed, or what. I've tried installing the Xposed 2.5 b1 apk with no success.
Has anyone had this problem or know how to fix it?
Thanks
Edit: Changes to /system stick after a soft reboot. So a workaround for now, is "Installing/Updating" the Xposed framework, then canceling the alert asking to reboot and insteading choosing a soft reboot. This keeps Xposed loaded up and Gravity Box works upon the reboot. A little annoying, but not to bad to have to do each time I rarely, if ever, let my phone die/restart...
You have root, but Write protection is enabled. Anytime you reboot, root is broken. You can do rooted stuff, and when you reboot its all wiped again.
So you have root, but its near useless.
Any more info you need can be found with a search. Tonnes of discussion about this already in the threads.
Sent from my N5 cell phone telephone....
kj2112 said:
You have root, but Write protection is enabled. Anytime you reboot, root is broken. You can do rooted stuff, and when you reboot its all wiped again.
So you have root, but its near useless.
Any more info you need can be found with a search. Tonnes of discussion about this already in the threads.
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
Ok thanks for the reply, but I though MotoWpNoMo killed write protection permanently?
EvanVanVan said:
Ok thanks for the reply, but I though MotoWpNoMo killed write protection permanently?
Click to expand...
Click to collapse
The 4.4.2 update puts write protection firmly back in place. So far, unless your device is unlocked, I haven't seen any way to remove write protection.
Thanks, reading the Xposed thread I was able to find a workaround. The changes to /system stick during a soft reboot... so "Installing/Updating" the Xposed framework, then canceling the alert asking if I'd like to reboot and insteading choosing a soft reboot, keeps Xposed loaded up and Gravity Box works upon reboot. A little annoying, but not to bad to have to do each time I rarely, if ever, let my phone die/restart...
EvanVanVan said:
Thanks, reading the Xposed thread I was able to find a workaround. The changes to /system stick during a soft reboot... so "Installing/Updating" the Xposed framework, then canceling the alert asking if I'd like to reboot and insteading choosing a soft reboot, keeps Xposed loaded up and Gravity Box works upon reboot. A little bit of a pain, but not to bad to have to do each time I rarely, if ever, let my phone die/restart...
Click to expand...
Click to collapse
You're welcome.
Of course, you could always unlock your phone and not have to worry about write protection anymore.
Related
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
So, I am using PIE from jcase and everything seems to go smoothly until I install XPosed.
Once I soft-reboot in the xposed installer, the device comes back to life but then after the screen is turned off for about 1 minute or more, I lose all root privileges. Funny thing is, any root checkers I run say that my phone still has root.
I really have no idea what could be causing this.
any ideas?
Why not ask in the PIE thread?
http://forum.xda-developers.com/showthread.php?t=2771623
Already talked to him. He doesn't have any clue either..
I got my B/L unlocked today and have full time root. This is no longer needed.
KJ said:
Why not ask in the PIE thread?
http://forum.xda-developers.com/showthread.php?t=2771623
Click to expand...
Click to collapse
Jcase posted he didn't want talk about Xposed, tethering, safestrap, etc... ( HERE ) in that thread... He wanted to keep it just about Pie itself.
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
Pretty sure you can't encrypt once you root. Or maybe it's once you put a custom recovery. I've never been able to use encryption after rooting my phones.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Hey be careful if your looking to install Safe Strap. Word for word what hashcode said
"THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW."
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
STraver said:
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Click to expand...
Click to collapse
I'm experiencing the same issue and changing the flash/encrypt/root sequence doesn't seem to change the results (encryption will not work, phone reboots). I'm attempting to root using CF's auto-root tools.
Wondering if there may be another root technique that wouldn't trip up the encryption process?
Disclaimers...
1. I know that encryption on a rooted device doesn't make much sense, but encryption is being forced down via the Exchange sync policies
2. I also know that the company might take a dim view of my attempt to root the device, but... they didn't explicitly tell me not to either
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?
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Sorry I don't have a solution but I just wanted to bump this thread because I'm having the same issues as you. Wakelock detector also gets stuck on loading screen and supersu fails to open.
vahx129 said:
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I also had the same issue. I am using the image with busy box and Xposed framework installed. After a an hour or so super user said that the binary was not installed, and most of my root apps stopped working. Root checker said my Turbo was not rooted, though gravity box and a few other Xposed modules continued to work. I rebooted the phone, but had the same problem. I turned notifications for the supersu app back on, and after about a minute it said the binary had to be updated, and I had root again. I'm not sure what is going on, but I will come back if I find anything
I'm not having any issues. I would reboot the phone into recovery and wipe the cache there. Hope that helps.
Glad I saw this thread...I'm having the exact same issue!
A hard reboot will solve the problem every time...but its quite annoying...
I'm going to try a factory reset and see if that helps
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Seems to have resolved itself
I just wanted to mention that between clearing the cache and flashing a different rooted image this issue appears to have resolved itself.
I will update after some time to see if this fix maintains or if anything else pops up. Thanks for the suggestions!
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
What cache did you clear? I tried to clear the cache from the recovery, but my phone freezes and I have to reboot. Then I loose root a while later.
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
I cleared cache in recovery...didn't help...gonna have to try a factory reset