Database Info

[Q] Root access removed after installing busybox

After receiving my asus transformer i wanted to share my files to it via hadhoc so i decided to root the device to change my wpa_supplicant file to achive this, so after finally rooting my transformer which was running updated Andriod 3.2 using rebound821 one click live cd v4, everything worked perfectly. Now i moved on to my next step for but had a change of heart after seeing a app that was to supposedly give me the same feature but it needed a busybox command to run the app properly.
And this is when all hell broke loose, i installed a busybox app by stephen, which in-fact installed busybox but removed my root access and i have been trying to get it back ever since. I have rooted, unrooted, update and restore the factory setting and rerooted the device and still cant get root access plus the busybox is still there.
I really need some help, i just feel so incomplete so you guys are my last resort.

superuser 3.0.7 doesnt work

I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.

try flashing su in recovery http://androidsu.com/superuser/

yeah thats exactly what i did...
I rooted my phone long ago and just got the new update so had to reroot it after installation... which seemed to work fine (with the older su-2.6.3.1) but sadly now that i got this nonworking superuser 3.0.7 (elf).zip in my phone none of my apps that need root access work
At this point im trying to figure how to go back to the older version (unless i can get this one working). Was just hoping i dont have to start all over as i cant even seem to reflash the older version - as it now gives me errors. Might just have to wipe the phone and start all over with the update.
But yeah so I updated the latest htc update and had to reroot my phone, I was able to flash the su-2.6.3.1 via CMR and this worked fine. It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.

Did you make regular Nandroid backups?
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1. I take it this isn't the case, because that backup would mean you could perform a factory restore, reflash CWM, and restore the backup. Any time you are making changes to your phone, backup before and along the way, just in case something like this happens. Titanium has its uses, but if your phone environment gets borked and you can't use it, it kind of defeats the purpose. Nandroid backups are more reliable in my book, and aren't app-dependent.
Sounds like you will have to start from scratch, although I'm unsure as to why Superuser 3.0.7 didn't work as expected. Possibly there was a conflict in moving from 2.6.3.1 to the newer version. I don't know of any specific problems 3.0.7 has with the MT4GS, and I'm running it on my phone with the latest binary without any problems. I do get an error message for one app, Quick Boot, when I use it to boot into recovery, but that doesn't stop the app from functioning as expected. I think that difficulty is related to the app itself and not Superuser.
Hopefully someone with a little more Superuser experience will chime in here. I'm afraid I don't have any ideas beyond the above.
Good luck --
--
KingCheetah

steve_77 said:
It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Click to expand...
Click to collapse
I had a similar problem before with SU after switching ROMs. Don't know if it might help but with Titanium Backup it showed that I had no busybox so I dl'ed busybox then SU wouldn't allow the apps to gain root access. Couldn't figure out what the problem was at all. Then I went to the SU app then saw that under the apps that were allowed or disallowed root access, the SU app itself was there. Once I deleted it from the list all the other apps that needed access worked fine. Hope that helps...

KingCheetah said:
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1.
Click to expand...
Click to collapse
Yeah i know - as fate would have it this is the one time i did not make a backup yet as i was hoping to gut out all the crap apps before doing a backup. Guess ill need to get more religious with the backups.
manimmal
Yeah i had Titanium Backup running with busy box before i had the "bright" idea to upgrade to 3.0.7 - but i guess i could try that but likely i might have to start-over from scratch (and forget about the 3.0.7 version) - unless anyone has any other ideas.
The only thing I can think of is perhaps the first su was flashed using one version of CMR and the second another version of CMR (updated after i installed rom manager perhaps)?
Even more interesting is the "su-2.3.6.1-ef-signed" with su having a datestamp of 8/17/2010; while the "Superuser-3.0.7-efghi-signed2" su version has a datestamp of 2/29/2008 - which seems a bit weird....

steve_77 said:
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
Click to expand...
Click to collapse
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.

Fuzi0719 said:
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Click to expand...
Click to collapse
do you still have the exact same zip file you used to install 3.0.7 ? (perhaps you have a slightly different one then whats available on the website)
I have no doubt that it works on some peoples devices, but i just dont know why it doesn't work on my device. I am pretty much running stock rom with the latest htc update, CMR 5.0.2.7 , rom manager 5.0.0.6 , superuser 2.3.6.1, su binary 2.3.1-ef - this works ( i have root) but if i boot into recovery and install the latest su for froyo 3.0.7 I loose root. (made nandroid backup this time)
I was thinking of trying to use chainsdd "su update fixer" in the market - but dont know how to use this app.. if it helps in debug i am also having a hard time installing busybox. i use "partitions info lite" to check status of my partitions, root access, and that i have busybox installed... i tried installing it via "busybox" [Stephen (Stericson)], which didnt seem to be recognized so uninstalled and tried "busybox installer" [JRummy16] - they are probably separate issues but who knows...

steve_77 said:
... and install the latest su for froyo 3.0.7 I loose root. ...
Click to expand...
Click to collapse
You answered your own question.
Froyo was the version of Android that predates Gingerbread.
The only official release of software for this device is on Gingerbread.
We are moving forward into Ice Cream Sandwich, but not officially.
You are basically trying to install a Windows 7 Program on Windows 95, to craft an analogy.
Stick with the gingerbread release of superuser.
The reason why the version is higher is because for the Froyo version of Android it went through more iterations.
Shame I didn't see this thread sooner, someone else had this same issue a while ago and I gave the same answer, should be around here somewhere. Would have saved you some trouble.

Some confusion here, I think...
Here's what is at ChainsDD's official site, http://androidsu.com/superuser/
Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)
md5: fc462fa0630379edbe10006b1d19d9b1
Superuser-3.0.7-efghi-signed.zip | mirror | RM Web Connect
binary only
md5: 26d08a253f1883c13561d173094d70b9
su-bin-3.0.3.2-efghi-signed.zip | mirror | RM Web Connect​
The lines after the md5 codes are links for the zip files. Superuser 3.0.7, according to the dev, is applicable to all flavors of Android as listed. This is also the exact file that I flashed and am using on my phone. There is a separate file for Donut 1.6, and it also is designated 3.0.7, but with a slightly different filename: Superuser-3.0.7-d-signed.zip.
I still think updating from 2.3.6.1 is part of the problem. If you go straight to 3.0.7 after your reformatting, it should work properly.
Also, Manimal's suggestion to check that Superuser isn't disallowed within the app itself is a great idea. It's weird, but an easy fix if this is the case.
I believe the update fixer Chains has available is to correct problems with the Superuser app updating new binaries. I don't think this would be of benefit to your situation.
Chains would be the best source for help, I think; an e-mail couldn't hurt --
--
KingCheetah

2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply

So why not install the working version, and then just update the binary from within the app?
That would be one way.
Sent from a digital distance.

steve_77 said:
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
Click to expand...
Click to collapse
Android 2.3.X is Gingerbread. Froyo is 2.2.X. Anyway, the SU you have SHOULD work, it is the same as I used. Have you tried flashing it via fastboot? I simply flashed the 3.0.7 version via recovery when I installed my ROM (stock 1.63.531.2).

[Q] Root not working as expected.

I got my HTC One X about a week ago now for AT&T. Almost immediately, I tried rooting but ran into an odd issue.
Before rooting I had installed Apex launcher. There is an option in the settings to enable Root Helper, which previously would give an error message of something like, "This device does not have root access"
I went through the rooting procedure as detailed here on my mac. The script didn't work at first until I realized I had to switch it to Unix from DOS (Didn't look at the script before running) after I fixed it, it ran and rebooted twice and everything looked normal. Now I tried using the apex root abilities and it just froze and crashed.
So I booted up windows and tried using that to root, but the exact same thing happened. It seems to recognize my root, but not actually give any permissions.
I've tried using other root apps such as uninstallers,titanium backup, etc and all of them just freeze when trying to get elevated permissions.
Is there something wrong with my phone or the way I did the root?

Have you tried clicking on the su app? I had to upgrade mine.
Sent from my HTC One XL using XDA

Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.

You could also try running paulobrien's root method. That's what I used, and my phone's good.

jason.hamilton said:
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
Click to expand...
Click to collapse
I've also had a situation where the Busybox version installed on a custom ROM on my HTC Flyer tablet interfered with some apps (like Titanium). Make sure Busybox is up to date. I even had to install a different Busybox installer in order to get it to work right on my Flyer in that particular instance. I had to use the JRUMMY16 version in the market, and not the Stericson installer (which seem the most popular).

No packages were installed with the root.
I'll try using paulobrien's method later and hopefully that will work.

Help with wiping and/or reinstalling busybox

Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.

I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...

Try this fix.

To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.

Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium

Already answered, see post above.

Deleted
Sent from my GT-P6800 using xda premium

Too late for me to try it, but thanks the same

ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!

Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.

Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted

I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.

ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way

regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.

Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though

No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.

I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.

Rooting the TF700 unsuccessfully

I'm having an issue hopefully someone can help me out with. I am trying to root my tf700 without success. I have ADB and java already installed on my x64 pc. My tablet is up to version 9.4.5.22. After running the DebugFS Root Tool the end result says that I should be rooted after the last reboot. Superuser logs say otherwise. Busybox will of course not install, saying denied. Terminal on the tablet shows $ after the issued su, so it seems to not taking effect. Has anyone run into this or have any suggestions?
Thanx
Chris

kristufer said:
I'm having an issue hopefully someone can help me out with. I am trying to root my tf700 without success. I have ADB and java already installed on my x64 pc. My tablet is up to version 9.4.5.22. After running the DebugFS Root Tool the end result says that I should be rooted after the last reboot. Superuser logs say otherwise. Busybox will of course not install, saying denied. Terminal on the tablet shows $ after the issued su, so it seems to not taking effect. Has anyone run into this or have any suggestions?
Thanx
Chris
Click to expand...
Click to collapse
Had same problem, quick search showed you need to uninstall and reinstall superuser from play store, then all is well.

gottahavit said:
Had same problem, quick search showed you need to uninstall and reinstall superuser from play store, then all is well.
Click to expand...
Click to collapse
Thanks for the response. That helped. I also had superuser set to auto allow apps, but it must be broken as it was denying everything. Setting it to prompt once again seems to have worked.
Chris