Hi guys
How can I add BusyBox to my (custom) ROM?
My ROM is based on the rootedupdate.zip version 1.21.405.2 with superuser 2.1.
I hope anybody can help me.
Well, this kitchen - http://forum.xda-developers.com/showthread.php?t=633246 has an option to add busybox to a ROM. You could either look at the 'add_busybox' script and figure out how it works or just use the kitchen.
I use this kitchen in the version 0.51.
I don't see a option to add BusyBox in the menu..
At the folder "scripts" is a script called add_busybox.
But how can I add it to my ROM?
Thank you for your help.
EDIT: It's a Desire ROM.
nickiberli said:
I use this kitchen in the version 0.51.
I don't see a option to add BusyBox in the menu..
At the folder "scripts" is a script called add_busybox.
But how can I add it to my ROM?
Thank you for your help.
EDIT: It's a Desire ROM.
Click to expand...
Click to collapse
I stand corrected. You are right. There is no option in the menu for that. However, if you select #2 (add root permissions), it will optionally add busybox. If that doesn't work for you, you can try different things...
1) look through the 'add_busybox' script and see what it does
2) find a ROM that has busybox installed, and see if you can tell how they added it
After looking at the script myself, it looks like it just copies the busybox binary to /system/xbin and then does some needed mods to the update-script.
yeah, busybox is just a binary
$ busybox
BusyBox v1.16.2 android full (2010-03-28 22:34:45 EDT) multi-call binary.
It simply contains many basic binaris in it.
wget, for example, is busybox wget
Related
iam new but always read a lot of threads here i want some help
i am trying to setup openvpn installer and settings in my coderom v2x2b
i tried to to install it without reading any guide first and installed it in
system/bin/openvpn
but now i read a guide somewhere like this
install openvpn installer and the binaries..
to install:
-run openvpn installer using file explorer
step:
- click install >choose /system/xbin/ > choose /system/xbin/bb
-check this directory if installation successfull: /system/xbin/openvpn
instal busybox
-open the application and click install.
-wait and check directory: /system/xbin/busybox or /system/bin/busybox <-- it(busybox) should be there.
now my problem is i dont knw about busybox but i searched it and its installed in
sbin/busybox <<< their is the file name busybox nowhere else
where it is required in system/xbin
and other i already installed openvpn in
system/bin/openvpn which also needs to be in system/xbin
i tried uninstalling openvpn but binary still remains their
can someone help me how should i fix all this paths and make openvpn working
no one has any idea to make openvpn work ?
noone had this prob ? can someone give me a guide to make openvpn work ? some places says linking the directory can work something like that but i dont have a clue how to do that ...........someone reply atleast lol
bumppppppppppppppppppppp
Hi, I just installed NottachTrix on my Atrix.
Now all I need to know is which installation option of V6 Supercharger script is best for this device. Ideally, a small explanation with each option to help me learn.
Thanks.
BPinard said:
Hi, I just installed NottachTrix on my Atrix.
Now all I need to know is which installation option of V6 Supercharger script is best for this device. Ideally, a small explanation with each option to help me learn.
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1334834.
Busybox/Supercharger V6 Advice for Nottachtrix v.1.3.1
I would like to try the V6 Supercharger script. I'm running Nottachtrix v1.3.1. Having read through the main Supercharger thread, it appears Nottachtrix contains a version of busybox that is known to cause problems, 1.18.4. It seems prudent to update busybox before attempting to run the script. But I need to know which busybox to install and how to do that.
I have downloaded the CWM-flashable version recommended in the Supercharger thread, which is by wraithdu and installs version 1.19.4. Having looked inside the zip it appears it only install to system/xbin and exploring Nottachtrix file tree shows busybox is in both system/xbin and system/bin.
Does anyone know the best way to "properly" (i.e. both locations) update busybox in Nottachtrix? And which version I should install for full busybox implementation and trouble-free Supercharger scripting?
Also, is there a particular version of the script I should be using for my Atrix?
gandalf_grey91 said:
I would like to try the V6 Supercharger script. I'm running Nottachtrix v1.3.1. Having read through the main Supercharger thread, it appears Nottachtrix contains a version of busybox that is known to cause problems, 1.18.4. It seems prudent to update busybox before attempting to run the script. But I need to know which busybox to install and how to do that.
I have downloaded the CWM-flashable version recommended in the Supercharger thread, which is by wraithdu and installs version 1.19.4. Having looked inside the zip it appears it only install to system/xbin and exploring Nottachtrix file tree shows busybox is in both system/xbin and system/bin.
Does anyone know the best way to "properly" (i.e. both locations) update busybox in Nottachtrix? And which version I should install for full busybox implementation and trouble-free Supercharger scripting?
Also, is there a particular version of the script I should be using for my Atrix?
Click to expand...
Click to collapse
The BusyBox installer available on the V6 Supercharger thread is the one you want to use.
upndwn4par said:
The BusyBox installer available on the V6 Supercharger thread is the one you want to use.
Click to expand...
Click to collapse
Do you mean the installer script? Will it update both locations in Nottachtrix? Because it appears to be the same as the CWM-flashable one just with a script to install it?
gandalf_grey91 said:
Do you mean the installer script? Will it update both locations in Nottachtrix? Because it appears to be the same as the CWM-flashable one just with a script to install it?
Click to expand...
Click to collapse
At the bottom of the post there is a CWM flashable busybox installer zip. It will install a fully compatible version of busybox in the place it needs to be.
Stop fretting over install locations and just do it.
upndwn4par said:
At the bottom of the post there is a CWM flashable busybox installer zip. It will install a fully compatible version of busybox in the place it needs to be.
Stop fretting over install locations and just do it.
Click to expand...
Click to collapse
It is amazing how a small piece of "advice" can cause a crisis. Thanks for the response. The CWM version will not install, CWM aborts install and says zip file is corrupt (downloaded multiple times). Tried script install and it installed to system/bin and not system/xbin and now I have lost root!!!
Tried the 2 "big name" busybox installers and neither will install any version of busybox because I no longer have root.
This is exactly why I asked for advice.
Edit: Restored from nandroid backup (many times!) and tried 4 different version of busybox installed to both locations via JRummy and Stericson busybox installers, none will install on Nottachtrix with or without root. WTF?
Is there an Atrix-specific CWM-flashable version of Busybox newer than version 1.18.4?
Is busyBox built into CWM recovery kernals? is this common practice?
if so, and "I believe it is" How can I update my busyBox Version?
The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again.
So I geuse what Im asking for is verification basicly.
Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab?
By the way to all comers who would like to bash my noobness Bring it!
I say this because I can learn more from the bashing than from no response/answer at all.
That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Pirateghost said:
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
Click to expand...
Click to collapse
Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed.
I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot)
I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings.
However on the skyRocket I do not seem to have this problem I believe this is why.
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
While Great for My "I727" that doesnt help me on my "I777"
rdannar said:
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks but not at all what I was talking about.
Phatboyj420 said:
Thanks but not at all what I was talking about.
Click to expand...
Click to collapse
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
rdannar said:
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks again but your still off please re-read O.P.
Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot.
The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to
"/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread.
Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin).
Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot).
To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.
Im running ICS SlimROM 1.6 and (was) loving it. But:
Titanium Backup Pro prompted for an update, which I ran, then it barfed and told me to install BusyBox from the market
Installed BusyBox, which got TB to run
uninstalled WiFi tether ( not working, another issue.....)
Next full reboot of phone, its stuck at the Google Gears
Then:
I went into recovery, wiped cache, Dalvik and ran fix permissions
Reboot, stuck at Google Gears
Mounted SD in Recovery, copied my PH98img file to SD, fastboot and ran update
Still stuck at Google Gears
I need to get the file off of SD to get into Recovery again, but when I do, what next ? Full wipe ? Reflash ROM ?
Only thing I can think of is BusyBox broke the ROM......am I wrong ?
I was stuck doing a full reflash of the rom, fixes, updates etc.......only thing I can figure is that the supersu was gorked...... Superuser (chainsdd) from the market ended up on my phone after the busy box install and didn't want to work or be removed until reflash.
Sent from my ADR6425LVW using xda app-developers app
archalon said:
Im running ICS SlimROM 1.6 and (was) loving it. But:
Titanium Backup Pro prompted for an update, which I ran, then it barfed and told me to install BusyBox from the market
Installed BusyBox, which got TB to run
uninstalled WiFi tether ( not working, another issue.....)
Next full reboot of phone, its stuck at the Google Gears
Then:
I went into recovery, wiped cache, Dalvik and ran fix permissions
Reboot, stuck at Google Gears
Mounted SD in Recovery, copied my PH98img file to SD, fastboot and ran update
Still stuck at Google Gears
I need to get the file off of SD to get into Recovery again, but when I do, what next ? Full wipe ? Reflash ROM ?
Only thing I can think of is BusyBox broke the ROM......am I wrong ?
Click to expand...
Click to collapse
Most likely, you installed busybox to the /system/bin/ directory.
Uninstall it, restart your phone, then re-run the busybox installer, except this time make sure you select /system/xbin/ as the install path.
a.mcdear said:
Most likely, you installed busybox to the /system/bin/ directory.
Uninstall it, restart your phone, then re-run the busybox installer, except this time make sure you select /system/xbin/ as the install path.
Click to expand...
Click to collapse
I'm on CleanRom 4.4 and it runs fine. I have the BusyBox install app from the market. I currently have BusyBox 1.20.2 installed and it's installed in /system/bin. That's where it wanted to install it, so i let it. I have had no problems with it being there. Should I move it? What is the pros and cons of it being in /system/bin vs /system/xbin??
Thanks.
derek4484 said:
I'm on CleanRom 4.4 and it runs fine. I have the BusyBox install app from the market. I currently have BusyBox 1.20.2 installed and it's installed in /system/bin. That's where it wanted to install it, so i let it. I have had no problems with it being there. Should I move it? What is the pros and cons of it being in /system/bin vs /system/xbin??
Thanks.
Click to expand...
Click to collapse
If its working at /system/bin/ then its probably not an issue for you.
I have init.d scripts, and my init.rc calls for busybox to be located at /system/xbin/. If I accidentally installed busybox to /system/bin/, busybox and thus also my init.d scripts fail to load because the init.rc file still tries to load it all from /system/xbin/.
but, since its likely you didn't build your ROM yourself, you may not know exactly where its supposed to be installed. You could look at the original update script in the zip file that installed your ROM, because usually there will be an install path and associated symlinks in that script which you can then use to determine where busybox is supposed to be installed on your particular device. Or, if your ROM has init.d support, you can look in the /init.rc file for the lines where busybox is called to enable init.d support. Your install path for busybox should mimic whatever path is called in this file, meaning if its attempting to load busybox from /system/xbin/, then that is where you need to have busybox installed, and not /system/bin/.
a.mcdear said:
If its working at /system/bin/ then its probably not an issue for you.
I have init.d scripts, and my init.rc calls for busybox to be located at /system/xbin/. If I accidentally installed busybox to /system/bin/, busybox and thus also my init.d scripts fail to load because the init.rc file still tries to load it all from /system/xbin/.
but, since its likely you didn't build your ROM yourself, you may not know exactly where its supposed to be installed. You could look at the original update script in the zip file that installed your ROM, because usually there will be an install path and associated symlinks in that script which you can then use to determine where busybox is supposed to be installed on your particular device. Or, if your ROM has init.d support, you can look in the /init.rc file for the lines where busybox is called to enable init.d support. Your install path for busybox should mimic whatever path is called in this file, meaning if its attempting to load busybox from /system/xbin/, then that is where you need to have busybox installed, and not /system/bin/.
Click to expand...
Click to collapse
I'm running Scott's CleanRom 4.4. I've looked in the updater-script file inside the zip.
I see the line: symlink("/system/xbin/busybox","/system/bin/busybox");
So, I am assuming that it can be installed in either location. When I installed busybox using the busybox install app from the market, it has "Smart Install", it scans system memory and then recommends where to install everything so I just let it do that.
derek4484 said:
I'm running Scott's CleanRom 4.4. I've looked in the updater-script file inside the zip.
I see the line: symlink("/system/xbin/busybox","/system/bin/busybox");
So, I am assuming that it can be installed in either location. When I installed busybox using the busybox install app from the market, it has "Smart Install", it scans system memory and then recommends where to install everything so I just let it do that.
Click to expand...
Click to collapse
So, according to that symlink, the actual location of busybox should be in /system/xbin/, but has created a symbolic link to /system/bin/ because some applications look for it in that location as well.
on a linux system, the physical location is the first listed path, the symbolic link is created by the second path, which essentially allows you to run busybox from either location even though it is actually located in /system/xbin/ and not /system/bin/
make sense?
Hello!
I use ROM toolbox pro. Today I enabled its zipalign script, but it warn me there's no zipalgn binary installed on my system. When I search on XDA, I found this thread. But it for Drod X2. So I it OK if I push that binary into /system/xbin directory? If it's not good, then how do I find a suitable binary?
Thanks!
probably will work, just don't forget set chmod 755 after pushed to xbin folder
android addicts said:
Hello!
I use ROM toolbox pro. Today I enabled its zipalign script, but it warn me there's no zipalgn binary installed on my system. When I search on XDA, I found this thread. But it for Drod X2. So I it OK if I push that binary into /system/xbin directory? If it's not good, then how do I find a suitable binary?
Thanks!
Click to expand...
Click to collapse
Don't forget to do a cwm backup.....
Sent from my ST18i
init.d zipalign Scripts are pretty much universal I've found.