Develop Bugs

[Q] Downgrade busybox from 1.18.4?

How do you downgrade your busybox? I tried using the app called busybox installer and its not working. I install the version I want and then it gives me tow options for install location:
system/xbin/
or
system/bin/
does it matter where you install it? Once I install the version I want it says to reboot and when I do in titanium backup still says I am using version 1.18.4...Help please!!!
I am doing this so that I can use the V6 supercharger script.
EDIT: The first couple of times I tried it didnt change, now it just brings me to my splash screen and sits there.

Sorry to bump this but I need help!

I know there are a couple different busybox installer apps on the Market, I have used THIS one in the past
My busybox is located in system/xbin
Using Viruses 7/23 Kingdom port

Need Help - Problem with SU and other issues with my Desire

Hi everyone,
I have some problems with my Desire and need your help, which is highly appreciated
I rooted my Desire (PVT4) a while ago and flashed AmonRa Recovery 2.0.1 in order to install CustomRoms. I used DeFrost 6.1 for quite some time before i flashed GingerVillain 2.7 and recognized the following issues:
If i open ConnectBot or TerminalEmulator, i always get "not found" or "permission denied". I.e. i wanted to ship the Dalvik Cache to my SD when i had GingerVillain installed and tried to get some more internal space. So I entered "su" in ConnectBot but it said "su not found". If i enter cat/proc/mtd to determine if it is S-off or on (i don't remember if i changed it) i get the same result..."not found"...
I have root access and i can flash ROM's etc. but i can't use any terminal commands... Furthermore, the Superuser-App told me that there is an update available but i can't install it. I can't flash the zip in the recovery ("Can't open su-2-3-1-bin-signed.zip") . So i tried updating using the app itself but now it says: Su binary voutdated...
Something's wrong in here...What can I do to fix this?
Current Settings:
Android 2.3.3
LeeDroid GB 3.0.8.2 (With HTC Sense, App2SD+ working fine)
Baseband: 32.49.00.32U_5.11.05.27
Kernel: 2.6.35.10-g308ba26
Superuser: 2.3.6.3

Not every Rom is loaded with commands for Terminal emulator...
Regarding Superuser, there is application in android market called "superuser update fixer"..download and install it...update issue will be solved...

You should install busybox.
Swyped from Oxygen with Transparent XDA App

First of all thx for your replies
jjdoctor said:
Not every Rom is loaded with commands for Terminal emulator...
Regarding Superuser, there is application in android market called "superuser update fixer"..download and install it...update issue will be solved...
Click to expand...
Click to collapse
I had this problem since i switched to GingerVillain ROM and also now on LeeDroid GB. It should definitely work with GV, not sure bout LeeDroid though.
I installed SU Update Fixer, it says that there is no problem. I tried forcing a fix but the app is shut down... Superuser details: v2.3.6.3, Su binary v.2.3.1-ef
MatDrOiD said:
You should install busybox.
Swyped from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
If i open Titanium Backup, it says busybox and root access ok. Busybox 1.18.4

Any other suggestions on how to fix this?
Sometimes the superuser app/process just shuts down, too. After reboot it works again...something's just not totally right i guess.

I switched to Leedroid and the problem basically disappeared... Strange though
Sent from my HTC Desire using XDA App

Busybox Error after Updating via Odin

I was running stock rom, rooted with bloat removed. I flashed the update through Odin, flashed CWM, and reinstalled Superuser through CWM, and when I went to update the binary in Superuser, I noticed that it said that Busybox was not found. So I installed Busybox Installer and tried to run, but got an error saying that there are problems with some core utilities necessary to load Busybox.
I then reflashed the update, CWM and Superuser, hoping that would fix the problem, but it hasn't.
My question is if there is anyway to load Busybox internally through CWM? Even if it is an older version of Busybox, once the core utilities are there, I can always update through the Busybox Installer.
Worst case scenario, I just back up through Titanium, flash back to complete stock, update, and then load CWM...but I always hate starting from the beginning if I don't have to.
The only apps I use that require root are SetCPU, and Titanium Backup. Would I even notice anything without Busybox working? I know Titanium used to be able to update Busybox right through the app, but then they updated and don't anymore...but I'm not sure if Titanium still requires Busybox to properly work.
I posted screen shots of the error messages I see in both Busybox Installer and when updating the binaries through Superuser. Any help would be greatly appreciated. Thanks!

Nevermind, I fixed it. For some reason, the Busybox app from Stephen (Stericson) was the one that kept giving me the error. So I downloaded the Busybox Installer app from JRummy16, and it worked flawlessly the first time. I went back in to Superuser to see if it recognizes it, and it does. So all seems to be good.
Moderator, please feel free to delete the thread. Thanks!

You solved my problem thanks man!!

s-off, but not rooted?

I rooted my first Evo and had no problems until I had a screen issue. I re-rooted it and returned it for a replacement. They gave me a refurb, which they swore they didn't, but it was obvious that the phone had been used before. Didn't root because it had issues with the screen again. I now have a new one again and have tried rooting using Revolutionary.io and the tutorial like I did the first time. It's giving me an hboot version of 6.16 with s-off (I started with hboot 2.16) but it's still not rooted. I have the clockwork mod installed and can run a full backup but ROM Manager nor Titanium backup can attain root. What did I do wrong? What do I do next? I've been searching all over and can't quite figure out what went wrong. Thanks in advance.

Wipe cache and dalvik cache in recovery and flash this http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
It's the super user app and binaries. Which is what grants root access.
Edited with correct link.

With the phone booted up, go into the superuser app and force it to check for updates. You should be on 3.0.3.2 if not have a look here and download the binaries! Then try again.

I checked before I got started and it said that SU was v3.0.6 (40). When I tried to have SU update itself, it said it was a legacy version, couldn't find Busybox and failed to give root. When I tried to flash the .zip file you linked to it said every thing went fine but it's still at v3.0.6 (40). I'm kind of confused. Still no root.

The superuser app and su binaries are two different things. So you most likely are up to date. It also sounds like you need busy box. Look up busy box installer on market.
You will also likely have to refresh the two apps, simply clear their data, after you have busy box. Then restart them and allow root access.
Sent from my PC36100 using xda premium

I have the busybox installer in my app tray but when I run it to install busybox it says I don't have root and can't install.

You need to wipe data on all of your apps that require root. And refresh all of them. Also look into your superuser app and check if any settings are denying root.
Sent from my PC36100 using xda premium

Well, SU has nothing in it. Nothing in the logs or apps list, I open it and it's empty. I went in to the applications menu setting, selected each app that would need root and cleared their data. Only one app had any data, that was ROM Manager, I think. I even booted into recovery and had it fix permissions. Still the same thing. ROM manager can't fix permissions (no root), SU has nothing in any lists, TI Backup won't run because of no root and BusyBox won't install because of no root.

This is also weird. You guys AND the SU Update built into the program are saying that I should be running SU version 3.0.3.2, but I'm running version 3.0.6 (40) and that it's legacy. When I try to run an update from the SU in my programs tray it does this.
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3.2
Checking installed version = legacy (in red)
Fixing database... okay!
Checking for busybox... not found (in red)
Downloading custom busybox... okay!
checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... fail! (in red)

Are you using a custom ROM?
You have the custom hboot, so revolutionary worked... You can access recovery and use the commands, so you have to have root, it's just something in the ROM...
Tell me what ROM version you are on, in settings > about phone > software
Did you get the "efghi" version or the "d?" sounds like you flashed the donut version....
Again su binaries: 3.0.3.2 and Superuser: 3.0.6 are two different things the binaries are the actual code to allow "switch user" access and Superuser is the app that controls the permisions.
Your version should not be "legacy" it should be 3.0.3.2 efghi

I have run custom ROM's in the past on my other rooted Evo, but this one is the bone stock ROM. I haven't really had the chance to use any custom ROM's yet. I wasn't sure if it would work until I got this problem resolved. My version is:
Android Version
2.3.3
Kernel
2.6.3510-g13578ee
[email protected] #1
Build Number
4.54.651.1 CL134969 release-keys
PRI
2.15_003
PRL
61086

Ok, so you were correct in that I had installed the "d" version instead of the "efghi" version. I flashed the correct version and everything is able to get root access now! The only other problem I have now is trying to install busybox, it gets root but fails to install "failed to copy over busybox to /system/xbin/". I cleared all data and tried again. And of course, Titanium backup can't get root because of no busybox. The main thing I'm wanting to do is remove Sprint's bloat and wait for Deck's ICS build to get WiMax support.

imheroldman said:
Are you using a custom ROM?
You have the custom hboot, so revolutionary worked... You can access recovery and use the commands, so you have to have root, it's just something in the ROM...
Tell me what ROM version you are on, in settings > about phone > software
Did you get the "efghi" version or the "d?" sounds like you flashed the donut version....
Again su binaries: 3.0.3.2 and Superuser: 3.0.6 are two different things the binaries are the actual code to allow "switch user" access and Superuser is the app that controls the permisions.
Your version should not be "legacy" it should be 3.0.3.2 efghi
Click to expand...
Click to collapse
Whoa that was my bad, browser must of skipped when I was copying....sorry

Finally, success! Apparently since I hqd installed the busybox installer before I fully had root it didn't install properly. I uninstalled and re-installed it and everything is working great. Thanks for your help, guys!
Sent from my PC36100 using XDA

Glad to hear it! Superuser and su should now update auto-magically!
Sent from my PC36100 using xda premium

Having similar S Off Issue
Ok, I have an EVO 4G (Supersonic) with HBoot 2.16.0001 and used the following "Guide" to root: http://forum.xda-developers.com/showthread.php?t=1218386
(Showing S OFF)
(Android Version
2.3.3
Kernel Version
2.6.35.10-gc0a661b
[email protected] #1
Build Number
4.24.651.1 CL61076 release-keys
Software Number
4.24.651.1
PRL Version
60690)
After reading this(and having basically the same problem... showed S OFF/SU saying not rooted... almost word for word what "toothles" put) ... I went into ASTRO File Manager to see if I indeed had "d" or "efgh".... Shock... "d". Hooked my phone to the PC and removed the .zip and other files it created.... Replaced it with the efgh(3.0.6-efgh-signed.zip) file from Superuser Site: http://hosted.androidsu.com/superuser/
Then back to HBooter... Recovery (Revolutionary)... File from .zip... Then loaded the efgh.... So now this is what my Superuser shows:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.03 (in red)
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... fail! (in red)
Then "Try again" at bottom.
I've looked for answers, and had hope when I found this..... Any suggestions would be well received.... I know this is the place to go when one has Android issues... Have found solutions here for other issues and have sent many a person here when they have had issues. Thanks for your time; and if I should have posted it somewhere else... Sorry.

Can't uninstall Busybox

Hey everyone,
This is my first post, so sorry it's a question. I'll try my best to help out in the future.
I've just rooted my Note 2 running 4.1.1 using CF-Auto Root. I installed Sterricsons Busybox installer from the Play Store and installed Busybox to system / bin.
Now the app is saying it can't uninstall Busybox. Is this something I should be worried about?
Thanks

Or another thought... would a factory reset clear the installation?

Factory reset won't do it. Leaving it installed isn't gonna hurt. Just leave it.
this is XXXDDDAAA

Ok, I'll leave it installed.
I must admit though I'm curious why this happened. This is my 5th Android phone, all of them have been rooted and had Busybox installed, but this is the first time I've not been able to uninstall.

This is common issue when you install busybox from market. You should flash busybox installer flashable zip whenever you need busybox (very few app needs busybox installed separately)and same way you can flash busybox uninstaller flashable zip to uninstall it.
Try flashing busybox uninstaller zip. As you said you have rooted with CF root, you may not have CWM so use mobile odin OR flash CWM to use busybox uninstaller flahable zip

Thanks dr.ketan, at least I know the problem wasn't due to me or my phone.