can i manually update the SU ? i used AndRoot to root my g1 and i was able to "root" it but i noticed that i didn't get SuperUser along with it so i've tried googling several solutions to come up with one where i can download it from the market.
i downloaded from the market and there was an update for it. after pressing okay after a request to update the SU, a toast came up saying it had successfully update it but it didn't update because i could not get permission from my root apps. oddly, i can access root apps but there wasn't a pop up asking for permission..
So in other words everything works just fine? You just want to have the actual application for SuperUser?
You can always try to download the APK and use that instead of your current SU.
I'm unsure if the superuser application is universal, or specific to device, but it's worth a shot.
http://www.mediafire.com/?mmjmoiz5mkw
Here is a Dump from the System Apps for those who accidentally deleted some of them and can't update to OTA2. I deleted some apps, you won't need for OTA2 to make the package smaller.
Remember before updating to OTA2 to protect your superuser by downloading and applying OTA root keeper.
After the update you have to download Superuser then just reactivate root by using ota root keeper.
PW for the archive is:
tptsystemappsdump
When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
My TPT is rooted (Titanium Backup shows it as rooted and RomManager also) but when I try to reinstall the Browser App it says could not install the app. Also Insallation via adb didn't work.
Can I somehow copy the files manually and what files need to be copied?
Thank you for this, one of our tablets unistalled the lenovo app market while trying to update itself, only want this for the notesmobile update but your dump helped greatly and meant i didn't have to faf about pulling it from my tpt
@Atom2007:
you will have to put the Browser.apk and Browser.odex into /system/apps with i.e. Root Explorer.
delete post
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
So I have a rooted stock zv6 android 5.1 sprint lg g4. Root is working fine and so is xposed version 79 sdk 22. I get all su prompts and can grant of deny them. In titanium backup latest version from Google play I also get the root prompt and I grant it, but it still says it doesn't have root access even though I even see the toast message that it has been granted superuser. It says something about not obtaining root using system/bin/su. But using root explorer the su binaries are there I even copied the su from the xbin folder and pasted it into the bin folder tried changing install paths in busy box still didn't solve it. What has me stumped that the prompt to grant superuser permissions comes up with titanium backup, but even granting it does not see it/achieve superuser permissions for whatever reason. Do you guys have any idea on what to try?
Bump
Sent from my VS985 4G using XDA Free mobile app
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.