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?
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
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.
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.
Hello, all!
I've searched the web, and haven't been able to find any reports of this.
I recently downgraded from CM12 to Kitkat 4.4.4, and was going through the steps of re-setting up my phone. I rooted it/installed SuperSU, installed busybox, installed greenify, as well as a bunch of non-root apps. I finally decided to install Xposed Framework to get the experimental features in Greenify (I did this fine in 4.4.3 a year ago), but this is where I ran into trouble.
I downloaded the newest Xposed Installer (2.7 experimental1: http://repo.xposed.info/module/de.robv.android.xposed.installer), opened it, clicked on "Framework," and clicked "Install/Update." I was shown a message for a fraction of a second that looked like it said something about it being successfully installed, and the screen went black. I didn't think much of it, figuring it was rebooting, and left it for a couple of minutes. Nothing happened, so started pushing the power button, then holding it, and absolutely nothing happened. No backlight, no bootloader, no nothing. I plugged it into my computer, and it showed up as "qhsusb_bulk."
Long story short, it was hard bricked. Fortunately, I was able to revive the thing using this guide (http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798), and re-flashed 4.4.4 on it. I have just successfully installed Xposed Framework going through the same process I did previously (in fact, all my apps were still installed, since I didn't wipe them when re-flashing), so am unsure what happened, so everything was either the same, or at least very similar to how it was set up when I tried previously). I'm figuring it could be any one of three gazillion things that could have caused it...
Anyway, figured I'd mention it here for any future Googlers who may run into this issue.
Thanks for reading!
ElectroPulse
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