I'm having issues with Busybox versions. I currently have v1.19.2-Stericson installed in /system/xbin. When I try to ping with terminal emulator, it says it's using "busybox v1.16.2androidminimal".
I've removed all traces of busybox from system files using root explorer, verified with the busybox installer app that busybox is uninstalled, and reinstalled v1.19.2, but terinal server still says it's using v1.16.2. What am I doing wrong?
Thank you!
EnervinE said:
I'm having issues with Busybox versions. I currently have v1.19.2-Stericson installed in /system/xbin. When I try to ping with terminal emulator, it says it's using "busybox v1.16.2androidminimal".
I've removed all traces of busybox from system files using root explorer, verified with the busybox installer app that busybox is uninstalled, and reinstalled v1.19.2, but terinal server still says it's using v1.16.2. What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
I think it depends on the kernel you are using. I think 1.16.2 is baked directly into some of the kernels and wont allow you to update them. I ran into some this a while back (I cant remember which kernel) when i was trying to use the memory script from zeplinrox. I think the kernel code may be dependent on that certain version of Busybox. I could be wrong, but its my best guess based on my experience.
Related
I updated busybox in /system/xbin but still see the old busybox revision when I type busy box at the ADB shell prompt, I found:
/sbin # ls -l busybox
lrwxrwxrwx 1 root root 8 Aug 17 01:35 busybox -> recovery
looks to be a link to busybox in recovery, I cannot get to recovery..
Any ideas if that actually belongs there?
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
adrynalyne said:
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
Click to expand...
Click to collapse
Now that our NAND is (relatively) unprotected, can I use Stericson's busybox installer to place a copy that will be accessible anytime I use ash via adb or terminal, or do I (can I) simply push busybox to /system/bin to make it a native part of android's command path? OR, do I have to use ~/xbin like the OP? It seems until we got S-OFF, busybox commands rarely pointed back to busybox automatically, I always had to spell-out "busybox" as a prefix, unlike my G1, where all ROMs after a while had busybox installed natively, from /system/bin, I assume.
thanks for advice in advance
Yep, you can use his installer on the market just fine.
adrynalyne said:
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
Click to expand...
Click to collapse
Thank you, everything is working busybox 1.15.3 is loaded, for an added measure I ran permissions.
I have installed Busybox installer from Marketplace. I also managed to install Busybox 1.17.1 Now if I try to update Busybox from installler first I will get empty box with OK button and the status says: Looking for BusyBox. If I then press install the whole program crashes. I also tried to update Busybox from Titanium Backup but it carshes also. I have a stock rom 2.51.1 which is of course rooted and OC'd. So nothing special. What is wrong? What can I do?
logcat pls.
The crash for Titanium Backup was caused by Droidwall. I uninstalled then the Busybox installer which is now only Busybox(?) in Marketplace and then installed different Busybox installer and I was able to update my Busybox. So no problems anymore.
Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.
Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).
Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse
goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse
Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.
Does busy box come with supersu? Can I hurt my phone installing busy box?
SuperSU is way to ROOT cell...it adds "Superuser.apk" in system\app folder.
also it adds "su" file to system\xbin (and sometimes in system\bin)
busybox is a tools app (usually found in system/xbin or system/bin)
current version is v1.20.2
-you won't ever see it in the App drawer
- you can download busybox installer from market, that is a app that has 5 busybox files inside and will install to your cell phone,
then you can delete the app after you install busybox.
-all DEV's inject SuperUser, busybox, and more into all ROM's
-when u run Titanium Backup, it uses it's own busybox tools (currently it uses v1.18.4) it shows that on startup page , when u run app.
I would say, no, It doesn't harm ur device. I've been using it for many yrs and i always make sure i have most current version on all my rom's.
Just installed 4.4.3 using WugFresh's excellent NRT keeping my data.
All went OK. At the end I told NRT to Root and install TWRP. Again OK.
Except that I don't have BusyBox installed. The app isn't present. SU is OK. A root checker app shows I am rooted and that BusyBox isn't installed.
There are no BusyBox files in \system\xbin or \system\bin.
Tried Google Play for Stericson's BusyBox and when the app tries to install it gives "Incompatible update" error and stops.
Found the apk file in \data\app and it comes up with "Not installed" error.
Found the zip file that NRT stored for TWRP to install and tried re-flashing that in TWRP. It says it was successful but BusyBox Installer app not available.
It was previously installed and OK under 4.4.2 this morning.
Everything else is as it was as far as I can see.
Any ideas what's going on?
Thanks
I installed another BusyBox Installer instead and that went OK.
Don't know what the problem is with Stericson's version.