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.
Related
So i was Rooted on NB4 and after being unable to do the KK update OTA I manually installed it through recovery and it worked. After rebooting after the KK update was installed I still have the "Custom" padlock on the boot-animation and to my surprise the SuperUser app is still on my phone. I have tried to go into Application Manager to attempt to uninstall it but there is no uninstall option: Only the option to "force stop" and "turn off." If i try and open the SU app it just says "there's no SU binary installed. I've checked in Odin Mode and Knox is still 0x0, Binary say "Offiial" and Status is "Custom."
Anyone have any idea how to remove the "Custom" status and SU App?
Try doing a factory reset in recovery, and wiping the cache in recovery.
Tried that 2 times already. Also just went to set up ISIS wallet and I get an error message saying that "This phone has been rooted, ISIS is not supported"
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I am same situation and also want to know.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
It's almost acting as if the phone is rooted but there is no Root access or binary. I'm gonna attempt to install the update again and see what happens.
Reinstalled update and still SU is installed. I just want to get this thing back to stock
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Well when you root it installs certain files. When you update without unrooting, those files never get erased completely. Traces are left behind. Now that you've updated and don't have root access to remove them, you're stuck with them. You can try reverting back to mj5 (if it's possible because I don't know anyone tried yet) and updating again. Or you can patiently wait for root access to come along for the latest release.
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Rukbat said:
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Click to expand...
Click to collapse
lehighkid said:
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Click to expand...
Click to collapse
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
If you un-root with superuser, you can't un-root with kingo too. Because you already un-rooted.
why are you giving up root?
I see so many people trying to go to stock KK but they will lose root forever - no? Why not use Knoxraid and have both (unless you are selling / taking it back)? Sorry - I'm a bit confused by this mass exodus from root ...
I am referring to the fix posted here: http://forum.xda-developers.com/showthread.php?t=2699321
It contains some system files to replace and a script.
I did not use SafeStrap at all.
rawb123456 said:
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Dont use the mj5 restore if you're on official 4.4.2 im pretty sure it wont work ( you may brick)
Sent from my GT-I9300 using xda app-developers app
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,
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
I just picked up a used T817T yesterday. I was able to root it with Kingroot. I then found out that I lose root after a reboot. Even worse, without enabling the developer options and enabling the OEM unlock, it would no longer boot. I had to reflash the stock ROM with ODIN to recover.
I purchased and installed SuperSu Me-Pro and that replaced the Kingroot SU with SuperSu. Now I can reboot without losing root.
I'm being prompted to install an update T817TUVS2APB1/T817TTMB2APB1/T817TUVS2APB1. If I install this update, will I lose root? If I install it, can I still root with other methods?
I still have the stock recovery.
I'm currently on T817TUVS2AOL1.
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
DonS said:
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
Click to expand...
Click to collapse
Install it with Flashfire.
I recently used the "New Root Method For 5.1.1 w/o custom kernel" to root my otherwise stock Note4 SM-N910T.
Everything was fine, but after a few weeks I lost root. I was able to get it back by re-flashing SuperSU 2.65 from recovery.
After further research, I found the blog post by Chainfire on SuperSU 2.74, and understand that 2.74 addresses the Samsung security update.
I've been using "SuperSU 2.65 Stable" because of root access compatibility issues with some programs.
How do I know if the Security Policy update was the cause of losing root? My phone's About Device has "Android Security Patch level" as 2015-11-01. So it doesn't look like something that was updated in the last week.
If it was not the security policy, then what caused the loss of root?
I have automatic updates off, and did not update anything at the time I lost root. Is there any other way that an update or change can be pushed? My /data/security/spota folder is empty. Should I delete the empty folder just to be sure?
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Supersuer said:
I guess because you upgraded the system root cause failure，you need to flash supersu.zip again ，can retrieve root
Click to expand...
Click to collapse
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
timg11 said:
Here's a summary of the problem:
1) FlashSuperSU from recovery.
2) Enjoy Root
3) 1 to 3 weeks later - something disables SuperSU, and root is lost
4) Go to 1)
I want to understand what is happening in 3) so I can exit this annoying loop.
Click to expand...
Click to collapse
This has only happened once? Interestingly, I had the same exact issue happen to me on my S5 with MM, I rooted using chainfire and just out of the blue, all root privelages were dismissed. So I flashed SuperSU v2.65. It happened multiple occasions until I was able to switch to an AOSP ROM. After going completely custom it seemed to have stop doing this. Maybe because of a contrast of coding that differ in security.
Sent from my SM-G900P using XDA-Developers mobile app
It has happened twice. I'm working on a Tasker recipe that will check for root regularly and report when it is lost.
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
timg11 said:
Now it has happened three times. Still trying to figure out what causes it. I have not found a tasker function that checks for root.
Unless I can find a solution, I guess I'll have to go back to the traditional root with beastmode kernel.
Click to expand...
Click to collapse
Nobody seems to have any idea what's going on. I'm guessing the loss of root was specific to SuperSU 2.65.
Here what I've tried today:
1) Recovery / Flash with SuperSU 2.65 to get root back.
2) Update SuperSU Pro to 2.76 from Google Store. Download and copy ZIP to phone storage just in case.
3) reboot and verify root still available from Titanium Backup
4) Uninstall ES File Explorer Pro. Install Solid Explorer
5) Test root access of Solid Explorer. It works. Buy Solid Explorer.
6) reboot again just to be sure root remains
7) Backup with TB.
So far, everything is working. Hopefully it will remain rooted.
Almost 3 weeks, and no loss of root. Super SU 2.76 seems to fix the problem.
J500G lost root minutes after connected to internet. I have to root every single day.