#!/bin/bash
#*Disclaimer*
echo "I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS"
Click to expand...
Click to collapse
This installs the latest busybox onto your gear 2.
God bless Skin1980 and gav83collins for inspiring me! ))
How to install?
1) Download the zip file
2) Extract it to a folder
3) Run installbusybox.bat
4) Done ))
Benefits:-
1) Able to use over 20 new commands!!
2) Better scripts can be made, and better functionally.
Usage:-
sdb root on
sdb shell
busybox "anycommand"
For ex:-
busybox kill
busybox date
busybox bzip2
busybox fstrim
Will this help at all with failed to install issue many are having.
Hey man,
Thanks very much for your work. Would you mind explaining to us the potential of busybox on Gear 2 ?
Cheers
You are most welcome, I did not build these binaries. I took them and make a batch script to install them onto the gear 2. Experienced users and developers can make use of busybox to improve the watch. For example by utilising the sysctl command. I don't know all of busybox applets, but this is an example of what u can do
Sent from my SM-N910C using Tapatalk
diamantericos said:
Will this help at all with failed to install issue many are having.
Click to expand...
Click to collapse
No sir it can not
Sent from my SM-N910C using Tapatalk
Related
Hello guys!
I am not new in the Android and Nexus world but at this time I need some help.
I am used to root any Nexus phone in this way:
1. Put su, daemonsu, busybox on /system/xbin/ path;
2. Create the init.d folder in /system/etc/ path;
3. Add a script file to start the superuser daemon at the boot;
4. Edit the kernel ramdisk adding the sysinit script to add the init.d support at the boot;
5. Edit the updated-script for the right permissions to the new init.d folder (and its content) and to the su binary file.
I never had problems with Galaxy Nexus and LG Nexus 4 but today I am having troubles with the Nexus 5.
Is this a common issue?
I hope to get answers,
regards,
kalo86
kalo86 said:
Hello guys!
I am not new in the Android and Nexus world but at this time I need some help.
I am used to root any Nexus phone in this way:
1. Put su, daemonsu, busybox on /system/xbin/ path;
2. Create the init.d folder in /system/etc/ path;
3. Add a script file to start the superuser daemon at the boot;
4. Edit the kernel ramdisk adding the sysinit script to add the init.d support at the boot;
5. Edit the updated-script for the right permissions to the new init.d folder (and its content) and to the su binary file.
I never had problems with Galaxy Nexus and LG Nexus 4 but today I am having troubles with the Nexus 5.
Is this a common issue?
I hope to get answers,
regards,
kalo86
Click to expand...
Click to collapse
fastboot oem unlock
flash custom recovery
flash SuperSU in recovery
Of course I have unlocked the bootloder but the init.d script does not work.
Neither a test script works...
This is the test script that I am using to verify if the init.d support is working. The file 00test is placed in /system/etc/init.d/.
Code:
#!/system/bin/sh
#Init.d Test
busybox mount -o remount,rw -t auto /system
if [ -e /system/Test.log ]; then
rm /system/Test.log
fi
echo "kalo86 @ XDA 2014" > /system/Test.log
echo "Init.d is working !!!" >> /system/Test.log
kalo86 said:
Of course I have unlocked the bootloder but the init.d script does not work.
Neither a test script works...
This is the test script that I am using to verify if the init.d support is working. The file 00test is placed in /system/etc/init.d/.
Code:
#!/system/bin/sh
#Init.d Test
busybox mount -o remount,rw -t auto /system
if [ -e /system/Test.log ]; then
rm /system/Test.log
fi
echo "kalo86 @ XDA 2014" > /system/Test.log
echo "Init.d is working !!!" >> /system/Test.log
Click to expand...
Click to collapse
You're making it way too difficult. Just flash supersu in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
You could install an application such as Universal init.d from the playstore. It works for me on both my Nexus 5 and 10. Initially works without issue.
Sent from my Nexus 10 using XDA Premium HD app
jd1639 said:
You're making it way too difficult. Just flash supersu in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Why difficult? This is the same identical mechanism that Chainfire uses to root your phone but I like to share a rooted-ROM ready to use.
The init.d folder is not supported at the moment. This is the truth.
And I don't want a workaround since the init.d support is very useful also for other stuff which is not only root access.
To install busybox on a rooted gear 2, turn root on (sdb root on) and then push this package (download.tizen.org/snapshots/2.3-wearable/common/tizen-2.3-wearable_20140605.1/repos/tizen/armv7l/packages/armv7l/busybox-1.17.1-2.3.armv7l.rpm) to the device. Install the package (from a sdb shell on the watch) by typing "rpm -i busybox-1.17.1-2.3.armv7l.rpm".
This gets you VI (a CLI text editor) on the device. Very useful when editing xml and config files.
kylgore said:
To install busybox on a rooted gear 2, turn root on (sdb root on) and then push this package (download.tizen.org/snapshots/2.3-wearable/common/tizen-2.3-wearable_20140605.1/repos/tizen/armv7l/packages/armv7l/busybox-1.17.1-2.3.armv7l.rpm) to the device. Install the package (from a sdb shell on the watch) by typing "rpm -i busybox-1.17.1-2.3.armv7l.rpm".
This gets you VI (a CLI text editor) on the device. Very useful when editing xml and config files.
Click to expand...
Click to collapse
Awesome. Thanks jumping straight on it
This is very good. Thanks.
But I wonder; do we have a use for Busybox on the Gear 2 yet ?
Thx.
Hi, when I try any install, I get "installing package busybox-1.17.1-2.3.armv71 needs 188KB on the / filesystem"
I've tried putting the package on the "SD card" (storage for music, pictures etc.) but still nothing
You guys know any solutions?
Make sure root is on and that you mount the filesystem r/w (then be sure to mount r/o after)
sdb root on
sdb shell mount -o remount,rw /
for read-only------>
sdb shell mount -o remount,ro /
mrmrmrmr said:
This is very good. Thanks.
But I wonder; do we have a use for Busybox on the Gear 2 yet ?
Thx.
Click to expand...
Click to collapse
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.
mrmrmrmr said:
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.
Click to expand...
Click to collapse
I am just tinkering and exploring at this point. Other than that... no not really.
mrmrmrmr said:
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.
Click to expand...
Click to collapse
I said this in my initial post. It provides VI. Without VI (or another text editor), there's no way to edit files on the device without a push/pull. Maybe you don't need that, but it's very helpful to me, and I assume to others.
Sorry for the question that many of you will be trivial but would like to know how I can successfully install the Busybox for Lollipop 5.0.1 on my Moto G xt 1032 with Firmware GPE?
Like to know how to install or FASTBOOT or through ADB.
I look forward to your suggestions.
Thank you very much
One way is to download a CM12 ROM, extract it, find the busybox executable (probabbly in /system/xbin/busybox) and copy it to your phone to /system/xbin. Then run this command as root (on the phone using ethier adb or a terminal emulator):
Code:
chmod 755 /system/xbin/busybox
and
Code:
cd /system/xbin/; ./busybox --install .
Hi, u can download BusyBox by Stephen (Stericson) from playstore.. Its just an installer.. Launch it, give Root access, then click install busybox.. I am using it in my XT1033 now..!
Sent from my XT1033 using XDA Free mobile app
dvdkon said:
One way is to download a CM12 ROM, extract it, find the busybox executable (probabbly in /system/xbin/busybox) and copy it to your phone to /system/xbin. Then run this command as root (on the phone using ethier adb or a terminal emulator):
Code:
chmod 755 /system/xbin/busybox
and
Code:
cd /system/xbin/; ./busybox --install .
Click to expand...
Click to collapse
If still there is only this way I prefer to leave everything as !!!!!!
As soon as there will be something more concrete for my version of Lollipop 5.0.1 GPE'll both Root that busybox.
For the moment still leave everything as is normal.
Thanks for the answer.: Buono:
claudiodelf said:
If still there is only this way I prefer to leave everything as !!!!!!
As soon as there will be something more concrete for my version of Lollipop 5.0.1 GPE'll both Root that busybox.
For the moment still leave everything as is normal.
Thanks for the answer.: Buono:
Click to expand...
Click to collapse
There are installer apps available just as @3abr86 mentioned, I'm just a CLI person
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Hey k02a,
thanks! I was looking for that, and installed it over the custom install feature and works flawless.
But there is one more thing, and maybe you can help me. I am looking for a tar version for android
that supports the --H ustar option like the linux one. To create odin packages within the phone.
I cannot find anything usefull for this. Any Idea? Maybe cross compile?
Cheers
NewBit
Good to hear that the binary worked on your device too!
Regarding the lack of flags and options in BuxyBox, I assume the developers have made a trade-off between functionality and binary size. - and in your case, the need for supporting the -H ustar format (e.g. for making Samsung/Odin images) have obviously not been considered.
Anyway, to get around this problem, I looked at my LG G3:s tar binary and discovered that it obviously supports the ustar format. I have included this file and hopefully you are able to use it as well. I hope this will help you a bit.
Kind regards,
k02a
Code:
[email protected]:/ $ /system/bin/tar --version
/system/bin/tar --version
tar (GNU tar) 1.16
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
...and this:
Code:
[email protected]:/ $ /system/bin/tar --help
...
Archive format selection:
-H, --format=FORMAT create archive of the given format
FORMAT is one of the following:
gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
...
Here is the MD5 hash sum:
Code:
[email protected]:/ $ busybox md5sum /system/bin/tar
busybox md5sum /system/bin/tar
d19775629f7f966e65bf1de7e2f695cf /system/bin/tar
Some kind of integrity verification in Linux (Slackware 14.1).
Code:
bash-4.3$ file tar; md5sum tar tar.zip
tar: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
d19775629f7f966e65bf1de7e2f695cf tar
e72aefb1060bc70725a1e2e0d432c9e0 tar.zip
Bamn, it's done! Thank you so much. It works great, this is exactly i was heading for! I own you a favour!
Btw: I have a Samsung Rugby Pro I547C with Android 4.1.2 and CWR.
Cheers
NewBit
I'm just glad to be of some help.
Take care
k02a
k02a said:
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Click to expand...
Click to collapse
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
HAYLCION said:
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
Click to expand...
Click to collapse
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
newbit said:
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
Click to expand...
Click to collapse
Thnks , sorry what should i send you? You mean a busybox installer pakage?
HAYLCION said:
Thnks , sorry what should i send you? You mean a busybox installer pakage?
Click to expand...
Click to collapse
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
newbit said:
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Seems goot , thanks
Great, you already seemed to solve it even before I logged in! :good:
newbit said:
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Via Terminal Emulator or on ADB, you can type "busybox" after you got superuser's permissions and check the version.
@k02a Does this busybox support x86 intel device?
@k02a i rooted my lenovo a7000 today. busybox installer shows busybox 1.21.1-jb installed in /sbin. so do i need to install busybox 1.23.2 and where to install? /system/xbin? and if yes then do i need to uninstall older one from /sbin?
Hi all,
since I am on CM13 some of my scripts did not work as expected any more. I discovered this was because my new rom uses toybox instead of busybox. >> read more
Maybe someone else has the same problems. So here my solution.
I wrote a small (flashable) script that combines best of both and makes sure that there are no conflicts between.
Disclaimer:
As usual, you use it on your own risk and I am not responsible for any damage that may happen to your device!
Make a Nandroid backup of your system before you flash/execute this script!!!
Prerequisit:
Busybox and toybox are already installed on your device!
(At least busybox + toybox binary have to be located in /system/bin and/or /system/xbin.)
Note: if your rom already comes with busybox instead of toybox, you do not need this script and should not use it!
What does it do? How does it work?
First, it makes sure that toybox is completely installed.
Then it will install all applets from busybox that are not already installed by toybox.
Finally it will make sure to use most compatible commands from bb/tb
Installation:
Copy ZIP to your device and flash it with TWRP recovery or compatible.
- or -
Extract install.sh from ZIP, copy it to your device and execute it as root.
Download:
BB-TB-Merger.zip
Busybox 1.24.1 ARM or use any other suitable version.
Changelog:
Code:
## 11.02.2016 v1.0 Initial version
## 12.02.2016 v1.1 + Keep original executables, replace only if forced
## + Use gzip from BB!
## + Code cleanup
Have fun,
Enkidu
Why this merger?
When I switched to CM13 I noticed that some of my shell scripts were broken. The reason was, some commands did not work as expected or were just missing. This seems to be because toybox is not as complete as busybox and also has some differences. Just flashing BB over TB also resulted in various problems, so this was also not the solution!
So I thought why not using best from both!? And a short while later, BB-TB-Merger was born!
Currently I found the following differences:
Toybox offers around 170 applets/command, busybox around 390!
TB version of head & tail do not really work. BB version does!
BB whoami does returns "whoami: unknown uid 0" instead of "root"
BB "mount -o rw,remount" does not work on my devcie. TB ones does...
BB gzip seems to be smoother..
And I am sure some more. So if you know further differences, please report them here! Tnx!
Have fun,
Enkidu
reserved
Important update!
Changelog:
Code:
## 12.02.2016 v1.1 + Keep original executables, replace only if forced
## + Use gzip from BB!
## + Code cleanup
Download: BB-TB-Merger_v1.1_2016-02-12.zip
great work,runs good on my A5.Thanx.
--SIGNATURE--
Excuse me sir @enkidu70,could you adapt the zip to make it work with busybox installed /su/xbin please?
Micky99 said:
Excuse me sir @enkidu70,could you adapt the zip to make it work with busybox installed /su/xbin please?
Click to expand...
Click to collapse
This should be no big deal...
Please give me full path to toybox and full path to busybox (/su/xbin/busybox ?) on your system.
enkidu70 said:
This should be no big deal...
Please give me full path to toybox and full path to busybox (/su/xbin/busybox ?) on your system.
Click to expand...
Click to collapse
I'm using systemless root with SuperSU by chainfire so busybox is in /su/xbin/busybox and toybox in /system/bin/toybox,thanks in advance sir.
Links not working
merger didn't work with busybox 1.25 installed in system/xbin.
kessaras said:
merger didn't work with busybox 1.25 installed in system/xbin.
Click to expand...
Click to collapse
What are the steps you're taking when you flash this?
evertking said:
Links not working
Click to expand...
Click to collapse
Here you go.
Enjoy!
Ibuprophen said:
What are the steps you're taking when you flash this?
Click to expand...
Click to collapse
boot to twrp -> adb sideload path/to/busybox.zip -> reboot.
Anyway , it worked fine. it was my mistake that it didn't work at first, i just didn't confim it, because nobody answered almost since a month, so i thought that its ok.
@enkidu70, it looks as though BusyBox is currently locating ToyBox and Symlink's to it.
I believe that this may be something new, post the November 2016 security updates.
Just wondering what your thoughts are...