Database Develop

[Q] Why is superuser not granting anything permissions?

So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?

furlessxp said:
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
Click to expand...
Click to collapse
Have you tried updating the superuser app itself? not only the su binary

[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.

Understanding root loss, samsung security updates, and SuperSU 2.65 vs 2.74

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.

Losing root after 2 or 3 reboots

Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.

same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again

fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.

JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.

Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.

Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.

elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.

galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.