So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
AMTrombley0924 said:
So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
Click to expand...
Click to collapse
Stupid question but after you updated did you restore root with the Root Keeper app?
Sent from my DROID4 using XDA
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
Glad it was something easy!
Sent from my DROID4 using XDA
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
---------- Post added at 04:39 AM ---------- Previous post was at 04:29 AM ----------
jnc8651 said:
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
Click to expand...
Click to collapse
Well it turns out a backup was dropped in /system and it was called su-backup. I was able to obtain root that way then I remounted system and copied it over to /system/bin
So, as it turns out, I did not think to backup my root with Rootkeeper, and now after the update, I still have Superuser but I'm unable to grant any apps superuser permissions. I got the Droid 4 utility .3 and tried to reroot. Unroot, then reroot, and basically everything I could think of, and still, no luck.
PS - Isn't unrooting supposed to remove superuser? It did not.
I had the same problem. Basically what has happened is you have lost root access, but the apps that use root are still there, and without root access, the unroot function is unable to remove them.
What I did, was manually push the files using adb :
adb push motofail /data/local/motofail
adb shell chmod 755 /data/local/motofail
Then I tried the running the exploit to get root:
adb shell "/data/local/motofail exploit"
but it failed... I also tried remounting the system folder as rw and it failed so I couldn't get root.
After this, I booted into fastboot/recovery and wiped my data/cache. Then, I tried the rooting process again, got read/write permission errors (did not originally), wiped data/cache again, and finally tried the unroot process.
This got rid of my superuser.apk and su binary somehow.
After all of this, the rooting utility worked. So, once you manage to get rid of those files, you should be good to go. I apologize I cannot narrow it down any better.
Well, I appreciate your response, but I'm still not having any luck.
Here is what I did:
Rooted phone few weeks back, left it alone.
Installed update
Did a factory reset, superuser still intact, but not granting permissions
Came to these forums
Booted into recovery and wiped (Holding volume buttons at boot, pressing down then up, formatting cache and data/factory reset)
Tried to root using Droid 4 Utility .3 - Did not get many errors
Waited for that process, then again, booted into recovery and wiped
Ran Droid 4 Utility .3 UNROOT option.
Recieved errors in removing superuser.apk due to read-only file system. Permission was denied to remove the app data, system/bin, etc....
Please, I know there's a lot of topics/posts around here and other sites, but I feel like I've tried everything to the best of my knowledge and refuse to give up!
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
can you give me some details about your uninstalled the superuser ?i use the peter's roottool and can't find how to do it...
jsnweitzel said:
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
Click to expand...
Click to collapse
I used the automatic method to install root on my Fire HD 7. The issue is that SuperUser has not shown up even after multiple reboots. I've read that I could use ADB to install it manually but I have no idea what commands are needed to push an .APK. I've also ready that ES File Explorer could be used to install .APK's but whenever I click root settings it force closes then says unable to mount upon reopening.
I'm running 7.2.1 if that helps. Can anyone help?
Thanks!
NVM I've figured it out guys! Thanks!
I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
shobuddy said:
I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
Click to expand...
Click to collapse
Install latest version of SuperSU (2.23) and latest version of ES (3.2.3).
Srandista said:
Install latest version of SuperSU (2.23) and latest version of ES (3.2.3).
Click to expand...
Click to collapse
Thanks for the response. I was already on ES 3.2.3. I update SuperSU to 2.23 but still having the same issue where ES does not go thru SuperSU.
shobuddy said:
I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
Click to expand...
Click to collapse
I had this issue so deleted and reinstalled ES File Explorer, but now I just get "ES File Explorer isn't responding".
I've Googled this error but no one else seems to be getting it.
So, I have switched to FX for the moment, till ES fix the problem (or I discover what is causing it)
Did you go under the tools tab and turn on root browser? I don't have lollipop so i can't try it out myself.
jhuebert95 said:
Did you go under the tools tab and turn on root browser? I don't have lollipop so i can't try it out myself.
Click to expand...
Click to collapse
This worked for me, thanks!
Yeah no prob! Make sure to turn on show hidden files. It really comes in handy. Ive actually had some issues with ES lately where it corupts apk files when you manually push them to /system/app. So be careful its been a real pain in the butt...
As we're loosing the root/safetynet battle with Google I have been wondering about how to live without root. If I place an app in the priv-app folder I suddenly give the app permission to the system, how is this different from just giving it root privileges? If they are the same, what would I lose if I move all of my root required apps to priv-app folder and then un-root?
just tried moving Sixaxis Controller as system app, then unroot, it failed to load driver
So, yeah. it's totally different ball game
ZzzzzxXxzzzzZ said:
just tried moving Sixaxis Controller as system app, then unroot, it failed to load driver
So, yeah. it's totally different ball game
Click to expand...
Click to collapse
Yeah, IDK why though. Some apps like adaway and FlyGPS are perfectly fine with it and even tell you to put them there for root privileges, but titanium backup and root explorer won't work without su.
Would love to get rid of root on my phone as Ive managed to get away from xposed.
EDIT:Spoke with Colin from Speed Software (Root Explorer) and he linked me to this permission breakdown: https://developer.android.com/reference/android/Manifest.permission.html
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.