Hi all. I had rooted my A100 about a week ago and then last night BusyBox had an update notification and stupid me press the Update button. It said I needed the Pro version for it to install and that it supposedly had "uninstalled" itself because whenever I try and hit the BusyBox icon, it tries to install again.
This got me worried that my A100 wasn't rooted anymore. How can I tell if it is or not? There's a install thread where someone says open up SuperUser and make sure it says that you have root access. I opened SU up but I don't see any sort of message. Then I opened up Titanium Backup and there is a line there "Root Access" and it says "OK (BusyBox 1.18.4-Titanium from app)". Does this mean that my device is still rooted?
Yes, you are still rooted.
Busybox and Superuser don't give you root, they are more like controllers that let you take advantage of the root access. These do need to be installed though in order for root access apps to work. Most apps that require root will tell you if you dont have access.
I actually did a factory reset the other day, and didnt lose root. Just had to re-install Busybox and Superuser.
You can always try Root Checker https://market.android.com/details?id=com.joeykrim.rootcheck&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..
Ive never used it, but it should confirm your concerns.
to see if you still have root, in terminal emulator simply type: su
and press enter.
If your rooted you'll get a # prompt rather then $ and you should get a message stating super permissions granted.
Sent from my MB860 using XDA App
sikesjb said:
Yes, you are still rooted.
Busybox and Superuser don't give you root, they are more like controllers that let you take advantage of the root access. These do need to be installed though in order for root access apps to work. Most apps that require root will tell you if you dont have access.
I actually did a factory reset the other day, and didnt lose root. Just had to re-install Busybox and Superuser.
Click to expand...
Click to collapse
crossix said:
to see if you still have root, in terminal emulator simply type: su
and press enter.
If your rooted you'll get a # prompt rather then $ and you should get a message stating super permissions granted.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for your replies. Crossix, I did what you said and it came back with # prompt so thank you so much for putting my mind at ease!
Related
May seem wierd but i seem to have this. I rooted my phone with a package THE-E (thnx for the root package) posted. I thought "get supersu" so i did but then i pressed clear binary as i saw no point in it but then su dissapeared but it was still in my system. So i used the unroot package (again THE-E thnx) but didnt delete supersu because i forgot. I pressed root explorer (as i wanted to delete it) but supersu was givin me that notification. I thought id check if everything from the root package got deleted and it did but supersu acts like su even though the packages required are gone. I was thinking of going back to root just in case my phone went haywire and it succeded but still...rooted while unrooted...anyone know what might of went wrong? Im using stock btw. This is not an everyday thing even for...idk...google them selves.
Sent From The Phone Of Gamers
why did you have to clear binary? that is needed for Root access.
are your applications that needs root still working fine?
you can download busybox installer, and it will update your SU app and binaries just in case. if it wont work, you have to root your phone again (to install the binaries again).
Supersu (created by someone else) has its own binary. I dowloaded that binary but thought super su is nothing but a space taker so i deleted the binary. I did get a message before saying you can update the binary again via superuser (normal version) but before i know it the binary is gone, superuser is gone and all packages required for root are gone but supersu still works even though superuser is gone. Superuser gives supersu root permisions but now every root file is gone im rooted while unrooted. Is this ok? Could i brick it without an app or anything (reboot maybe?)
Sent From The Phone Of Gamers
Seems like there are fragments of SU that you can't see in a folder. I had the same problem, just experimenting what happed if i deleted files that i don't need. Since that time the system runs stable (Bionic Cow) and also SU-rights are given to me without having these SU-files in the folder...
so im not the only one...
Sent From The Phone Of Gamers
I've used KFU .95 and it seemed to have run fine. I have TWRP and have made a full backup.
When I use the option to install the Google Apps, I get all kind of permission denied errors. Then I tried to copy the apps.zip directly to the apps folder on the Kindle and get a "must have root privileges" error.
Now I'm wondering do I really have root? If so, did the superuser privileges not stick?
Any ideas appreciated. Thank you!
Well first its pretty obvious to tell if you have root and superuser. Just look for the superuser app. Or use root checker from the market if you have to
Sent from my Desire HD using Tapatalk
I side loaded superuser.apk and that worked. For whatever reason, the KFU utility didn't install it.
I'm now trying to get Market working but when I started it, it displays a never ending "loading" message.
jwhistler said:
I side loaded superuser.apk and that worked. For whatever reason, the KFU utility didn't install it.
I'm now trying to get Market working but when I started it, it displays a never ending "loading" message.
Click to expand...
Click to collapse
You shouldnt side load superuser. It needs to be a system app to work
Sent from my Desire HD using Tapatalk
Removed.
Hi all..
I Rooted my Fire using KFU..
Then I installed OTA-RootKeeper
But I dont get the option to do a Temp Un-Root...
Any suggestions? It lets me Protect root but that is all it lets me do..
I did notice on the check boxes for "Root Permission has been granted" is not checked.. Could this be the cause??? And if so how do I fix? I thought KFU gave me root permission?
Thanks!
I think you did not install superuser.apk on your kindle. Without it having root is pretty useless for apps. Superuser gives you an option to allow root access to the app. If you already have superuser you may have it disabled for OTA. Otherwise a problem may have occurred with the rooting process. Tell me if this works.
That was it.. Thank you VERY much...
Wonder why KFU don't include superuser..
Glad it worked for you Not sure though why it is not included in kfu though I know in the past when you manually rooted the kindle super user would automatically get installed therefore it remain on the kindle unless you wipe. Though I guess you could recommend it to the developer to add.
Sent from my Galaxy Nexus using xda premium
UPDATE: Problem Already Solved
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
phonic said:
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
Click to expand...
Click to collapse
I ran the command as you said and got the identical permissions. Still that one app I'm trying to use says that the system denied root even though I granted it. Thanks for the help. I don't get the binary error anymore.
PS: Why don't I see the new SuperSU icon on my tablet, but I do in Google Play?
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
I experienced the same issue yesterday.
To resolve the issue I went to the app management screen , uninstalled updates, force stop and then disabled and re-enabled super user
I then proceeded back to flash the su zip via TWRP recovery
Upon rebooting device, there was an update available in the play store, I went ahead and installed this update
After installation, I opened the super user app and it prompted me to update the binary. I did that and root has been fine for me since then.
Hi -
I'm a new T700 user. Got it home and immediately rooted it via instructions here:
http://forum.xda-developers.com/galaxy-tab-s/development/official-chainfire-cf-auto-root-sm-t700-t2960171
That seemed to have worked fine. I booted to recovery, and the only issue then was it was erroring when trying to load 2 different ROMs I was trying. See here for my post showing the error message if that matters:
http://forum.xda-developers.com/galaxy-tab-s/help/8-5-to-recovery-error-installing-image-t3010758
Someone recommended using TWRP, so I installed that, and my ROM load worked like a charm.
So now I have the Cyanogenmod 11 for SM-T700 ROM loaded, and everything appeared to work fine until I went to install an app that needed root. It would prompt Deny/Grant, but would not let me press the Grant button, only the Deny. I then looked for SU in my app drawer, and I found none. I tried installing one of them from the playstore (not sure exactly which, but it was the blue "#"), but that didn't do the trick. I then figured I'd try rerooting (took nandroid backup first) this ROM. It took, but when I rebooted there was still no SU. I tried an app that triggers the SU prompt, and found a dialog box in the background telling me to update SU. I did, and finally I could see SU in my app drawer. I loaded the app that triggers the SU prompt and got a different looking SU prompt, but still would not let me hit the grant button.
I'm not sure what my next step should be here, but I don't know if I've lost root or if something else is going on, anyone have any advice?
Thanks in advance!!!
I couldn't figure out how to delete this post, but I think I'm all set. I flashed back to stock, rerooted, and reflashed ROM and all is working well.