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.
Who has Android pay working on their unlocked bootloader?
What obstacles did you have to overcome?
I do, I installed and opened it before I flashed TWRP and super su.
Sent from my XT1254 using Tapatalk 2
Have you used it since?
I'm getting errors and I wonder if it's from unlocking the bootloader or xposed. I've read a bit about it it but short of going full stock nothing has worked
Sent from my SM-T330NU using XDA Free mobile app
Batttie said:
Have you used it since?
I'm getting errors and I wonder if it's from unlocking the bootloader or xposed. I've read a bit about it it but short of going full stock nothing has worked
Sent from my SM-T330NU using XDA Free mobile app
Click to expand...
Click to collapse
Root kills all the pay services. Disable root.
mrkhigh said:
Root kills all the pay services. Disable root.
Click to expand...
Click to collapse
Is that confirmed? There are lots of topics here that say that any root kills Android Pay but they are several months old.
I've rooted my phone using the latest Sunshine yesterday. I can live without Android Pay but if turning off root gets it back I'll take it.
nlinecomputers said:
Is that confirmed? There are lots of topics here that say that any root kills Android Pay but they are several months old.
I've rooted my phone using the latest Sunshine yesterday. I can live without Android Pay but if turning off root gets it back I'll take it.
Click to expand...
Click to collapse
I've never used it, so no I cannot confirm it. But, a while back somebody posted with stock cm12.1 root not enabled in dev options that it worked.
mrkhigh said:
I've never used it, so no I cannot confirm it. But, a while back somebody posted with stock cm12.1 root not enabled in dev options that it worked.
Click to expand...
Click to collapse
OK, I highly doubt that. Cyanogen as I understand it isn't CTS compliant. Therefore, it couldn't work rooted or not. When I turn off Root I can pass a safetynet check. That implies that it SHOULD work with root turned off but it's not guaranteed to function that way. I'll need to check it at a cash register.
nlinecomputers said:
OK, I highly doubt that. Cyanogen as I understand it isn't CTS compliant. Therefore, it couldn't work rooted or not. When I turn off Root I can pass a safetynet check. That implies that it SHOULD work with root turned off but it's not guaranteed to function that way. I'll need to check it at a cash register.
Click to expand...
Click to collapse
When you try it post back, I'm curious and then we'd both know.
Disabling root stopped working a few updates ago. Even on the stock rom. Unlike other companies, who might eventually get to the point where patching workarounds isn't worth it to them, Google seems pretty dedicated to the cat and mouse game.
Also, it is possible for you to add a card and then for you not to be able to use it when you try to pay for something. So for all those who think "I can add a card! Success!", you might want to hold off on the celebrations for a bit.
Will the Xposed module that hides root from apps work (root cloak or something)?
jlang11 said:
Will the Xposed module that hides root from apps work (root cloak or something)?
Click to expand...
Click to collapse
Nope
What's the best method to get Android pay working? There's still time to tap 10, and a free chromecast might be worth the trouble lol.
Here ya go:
Workaround to get Android Pay Working with SuperSU v2.67
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
Doesn't work with xposed, however.
ChazzMatt said:
Here ya go:
Workaround to get Android Pay Working with SuperSU v2.67
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
Doesn't work with xposed, however.
Click to expand...
Click to collapse
That workaround was done using systemless superSU on android 6.0.1. I'm hoping that it will work for us, but I'm not optimistic. Even if it does, I give it a month max before it stops working.
As the title says...I'm considering doing root in my V2. I just got my replacement note an hour ago. I immediately paused the update because I read somewhere on here that once you update, you won't be able to root. I was looking forward to root till I started thinking about what types of abilities I would actually lose by rooting?
What I can think of from the top of my head is:
1) No Samsung/Android pay
2) Some games won't let you play if you're rooted.
3) Some games won't let you play if you have xPosed installed (such as Marvel Future Fight)
4) Can't do software updates to make my phone faster/fix anything that is wrong (can't I just install the software updates after installing root? Or will that just remove the root?)
5) Voids warranty
Anything else I might lose?
I'm excited for xPosed cause I need me some modules such as snapprefs, and youtube playing in the background. I also like having the ability to change things around the device and such
Is there a way to get around the "xPosed detected" in those types of games by the way?
Luckily for you, the current root does not trip knox
1) Samsung pay will not work, but with right xpose set up Android pay will. The good news is if you ever go back to stock, Samsung pay will work again (knox not tripped)
2) Some games indeed will not work, but with the right xpose app you can fix this by hiding root from it.
3)I did not know that! They getting fancy now...but I can see reason why. I guess no Marvel Future Fight for you if you have xposed than. I know you can hide root from apps, not sure you can hide xposed from apps.
4)You cannot do software update, this is true. The run around for this is to wait for a developer, or even Jovy do a deodex of the new update and you can install that while keeping your old bootloader (for root to work). There is a possible downside to this...samsung is known to make their software run very funny if you are not on the corresponding bootloader. P.S. I never recommend taking a software update while you are rooted (assuming it will even install depending on what you have frozen or block). Just dont risk it.
5) TECHNICALLY your warranty will not be voided with current root method. Knox not tripped = Warranty in place.
As you can see, you are not really loosing much.
Root cloak fixes every problem with root.
Leelouster said:
As the title says...I'm considering doing root in my V2. I just got my replacement note an hour ago. I immediately paused the update because I read somewhere on here that once you update, you won't be able to root. I was looking forward to root till I started thinking about what types of abilities I would actually lose by rooting?
What I can think of from the top of my head is:
1) No Samsung/Android pay
2) Some games won't let you play if you're rooted.
3) Some games won't let you play if you have xPosed installed (such as Marvel Future Fight)
4) Can't do software updates to make my phone faster/fix anything that is wrong (can't I just install the software updates after installing root? Or will that just remove the root?)
5) Voids warranty
Anything else I might lose?
I'm excited for xPosed cause I need me some modules such as snapprefs, and youtube playing in the background. I also like having the ability to change things around the device and such
Is there a way to get around the "xPosed detected" in those types of games by the way?
Click to expand...
Click to collapse
You'll lose secure folder and if you update shealth after the root process it will no longer run.
louforgiveno said:
You'll lose secure folder and if you update shealth after the root process it will no longer run.
Click to expand...
Click to collapse
Oh yeah, I've heard about the shealth thing, just update it before you root and you'll be good It's a shame about the secure folder...:/ Anyway to go around it to be able to use it just like the shealth?
Seems like rooting will somehow cripple your device...wow times have changed.
Sent from my SM-N930T using Tapatalk
charlieb620 said:
Root cloak fixes every problem with root.
Click to expand...
Click to collapse
Will samsung pay continue working?
Sent from my SM-N930T using Tapatalk
leelouster said:
oh yeah, i've heard about the shealth thing, just update it before you root and you'll be good it's a shame about the secure folder...:/ anyway to go around it to be able to use it just like the shealth?
Click to expand...
Click to collapse
im rooted wit secured folder workin
mister_propa said:
im rooted wit secured folder workin
Click to expand...
Click to collapse
How did you get that working? Ive tried setting it up before rooting and it wont let me open the file. I also tried setting it up after rooting but it keeps giving me error making the folder.
---------- Post added at 01:36 PM ---------- Previous post was at 01:31 PM ----------
Leelouster said:
Oh yeah, I've heard about the shealth thing, just update it before you root and you'll be good It's a shame about the secure folder...:/ Anyway to go around it to be able to use it just like the shealth?
Click to expand...
Click to collapse
I had heard even if you update s health before rooting once your rooted it wont open due to root.
This is the first Android device I've own that I feel no need to root. Sure I'd love to have Viper4Android running but can't justify all I'd lose to run one app that requires root.
mgbotoe said:
Luckily for you, the current root does not trip knox
1) Samsung pay will not work, but with right xpose set up Android pay will. The good news is if you ever go back to stock, Samsung pay will work again (knox not tripped)
2) Some games indeed will not work, but with the right xpose app you can fix this by hiding root from it.
3)I did not know that! They getting fancy now...but I can see reason why. I guess no Marvel Future Fight for you if you have xposed than. I know you can hide root from apps, not sure you can hide xposed from apps.
4)You cannot do software update, this is true. The run around for this is to wait for a developer, or even Jovy do a deodex of the new update and you can install that while keeping your old bootloader (for root to work). There is a possible downside to this...samsung is known to make their software run very funny if you are not on the corresponding bootloader. P.S. I never recommend taking a software update while you are rooted (assuming it will even install depending on what you have frozen or block). Just dont risk it.
5) TECHNICALLY your warranty will not be voided with current root method. Knox not tripped = Warranty in place.
As you can see, you are not really loosing much.
Click to expand...
Click to collapse
THANK YOU for you detailed explanation, this is exactly what I was looking for! Thank you for your advice and everything Do you know what xpose app that is to hide root from games? I don't think you can hide xposed from apps though :/
charlieb620 said:
Root cloak fixes every problem with root.
Click to expand...
Click to collapse
I'm guessing that's an xposed module?
mister_propa said:
im rooted wit secured folder workin
Click to expand...
Click to collapse
How did you get it working? Can you please tell me what you did?
dkb218 said:
This is the first Android device I've own that I feel no need to root. Sure I'd love to have Viper4Android running but can't justify all I'd lose to run one app that requires root.
Click to expand...
Click to collapse
I feel ya, I'm on the same boat, but I'd really enjoy some xposed modules lol. I'm an audiophile and haven't had Viper4Android since the S5 and I miss it lol
Question:
Is Xposed or any of its modules suppose to give zygote root access? Doesnt Xposed already take care of that?
Yes. What's app extensions module must have zygote/sqlite3 base for work.
Robert342 said:
Yes. What's app extensions module must have zygote/sqlite3 base for work.
Click to expand...
Click to collapse
One module that is using it wrong.
Others? None?
riahc3 said:
Question:
Is Xposed or any of its modules suppose to give zygote root access? Doesnt Xposed already take care of that?
Click to expand...
Click to collapse
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Spott07 said:
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Click to expand...
Click to collapse
...wow...really?
Spott07 said:
No. You must have root access on your device before trying to install Xposed.
Please go read in the Zygote sub-forums to learn how to get root access, if it is possible.
Click to expand...
Click to collapse
I accidentally unrooted my phone multiple times yet Xposed still works. So I'd say you are wrong, Xposed only requires unlocked bootloader/recovery.
levizx said:
I accidentally unrooted my phone multiple times yet Xposed still works. So I'd say you are wrong, Xposed only requires unlocked bootloader/recovery.
Click to expand...
Click to collapse
Technically, you are correct.
However, you can't get root access without unlocking the bootloader/recovery, so it's easiest just to start with root as your goal. By the time you unlock bootloader/recovery you're already 90% of the way to root.
Spott07 said:
Technically, you are correct.
However, you can't get root access without unlocking the bootloader/recovery, so it's easiest just to start with root as your goal. By the time you unlock bootloader/recovery you're already 90% of the way to root.
Click to expand...
Click to collapse
90% of the way to root means EXACTLY that, not rooted. So saying Xposed REQUIRES root is not just "technically" wrong, there's nothing right about that statement, and that's a fact.
levizx said:
90% of the way to root means EXACTLY that, not rooted. So saying Xposed REQUIRES root is not just "technically" wrong, there's nothing right about that statement, and that's a fact.
Click to expand...
Click to collapse
To install Xposed requires permission or workarounds to edit system files at the root level. End of story.
However you go about it, whether the user account has ongoing root access or not, whether the device allows root/bootloader access out-of-the-box or if you have to use exploits, whether it continues to run after the *user account* has unrooted, is immaterial.
SuperSU or equivalents do not *provide* root access, and removing them is not the same as unrooting the entire device. They instead take existing root access and bring it to where it is convenient for the user.
Unlocking the bootloader/system partition IS rooting your device, even if you never install a root manager program, despite how the terminology has been distorted in popular use here on XDA.
Xposed requires root access. Xposed modules do not provide root access if your device does not already have it.
Ok, fine. But where did the "zygote" related discussion ended up? I've just had a zygote root permission request which I denied, and now SuperSU is not responding and crashing. Some other non root app nor Xposed module is also closing itself...
Sent from my Moto G4 Plus using XDA Labs
The Analog Kid said:
Ok, fine. But where did the "zygote" related discussion ended up? I've just had a zygote root permission request which I denied, and now SuperSU is not responding and crashing. Some other non root app nor Xposed module is also closing itself...
Click to expand...
Click to collapse
Zygote process is in the system, and should not request root permission (already has it).
You encountered a bug which you should have neither allowed/disallowed and just rebooted your device.
Search the supersu threads, the bug get's reported every now and then.
Chainfire said:
There is a case where an internal crash of zygote(64) will attempt to create log files as root. This is a left-over from Android development and really shouldn't be in production builds, but it often is. It is impossible to know if that is the cause, though.
Click to expand...
Click to collapse
corkiejp said:
Zygote process is in the system, and should not request root permission (already has it).
You encountered a bug which you should have neither allowed/disallowed and just rebooted your device.
Search the supersu threads, the bug get's reported every now and then.
Click to expand...
Click to collapse
Well, I've searched for that indeed; but there's no concluding answer that I can spot whatsoever. Anyway, just to see if granting zygote root permission (Chainfire's "suggestion" picked from one zygote related discussion) resulted in any help, I just did... And it positively doesn't. SuperSu has exactly the same bad behavior. I even updated it to 2.82 SR5, to no avail. Nevertheless, I agree this is something that just entered device since SuperSU was working as usual for one month a few days back; I can say it started right after I tried the SuperSU logs section. As of know, I have a nice collection of different "Cracker" logs regarding SuperSU crashes (though, sometimes it just stops). One of the most dramatic SuperSU related events, involved multiple apps and even system stopping in sequence following SuperSU's own. That is something I couldn't even find reports of in any SuperSu nor zygote threads. I think I'll keep trying some stuff before definitely going full restore and start from zero.
Sent from my Moto G4 Plus using XDA Labs