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!
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 need some help with Superuser. Currently running Mustaavalkosta 's CM11 BR4 and Superuser version 3.1.3 (46).
After clean installing the ROM, Superuser works and allows me to grant root permission to apps. Temp unroot works but updating the binary immediately results in 'downloading manifest... fail!' and if I click the 'try again' button, Superuser crashes. No big deal cause everything that I need it to do, works. A couple of days later however it just stops working and no longer grants permissions... I still have root. Temp unroot stops working and crashes Superuser when I try to use it. The file /system/bin/su still exists.
Things I tried:
- clear Superuser data
- uninstall Superuser and reinstall from Play Store
- install SuperSU
None of the above works.
Please somebody help me out here, I don't want to keep restoring my Nandroid cause it still is alot of work. Thanks
After doing some more research I think I fixed the problem by flashing the latest SuperSU.zip instead of installing it from the Play Story where it wouldn't let me update the binaries. I can now grant root access again to apps.
Still no idea what caused the Superuser issues but I 'm glad with this 'workaround'.
Hi guys,
My Z1C is rooted and currently running 4.4.4. I think I have rooted with towelroot; not sure of the name of the method.
The experience was quite bumpy. I had to run it a few times to get it to work, and when I finally did, I installed SuperSU, and it said that it needs to update the binary. After a fail, and a restart, the app stopped complaining, and I seem to have received a half-proper root. I'm not really sure, because some apps work fine, while others don't.
Basically, I can't mount /system as RW. Xposed has this problem, and ES File Explorer has this problem. I'd really like to install Xposed, but I don't know how to fix this. Also, I really don't want a custom recovery so that I can flash a more proper su binary. I just want to make root working on a stock ROM. No further tinkering than that.
I'm totally up for methods where you do something from the adb shell on your computer. I have nothing against that.
The error message I receive from Xposed is:
Mounting /system writable...
mount: permission denied (are you root?)
cp: can't create '/system/bin/app_process.orig': Read-only filesystem​
Hope someone can point me in the right direction. I've searched the forum, and tried with older versions of Xposed, but with no avail. The only thing that was different was that XposedBridge.jar got installed. app_process did still not make it. :/
Thanks!
You may need to redo it, have a read through the EasyRoot thread as this issue is addressed there.
Thanks! Will do!
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.
clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.