Database Info

Busybox for the EVO

Does anyone have a compiled busybox for the EVO yet. Preferably in update.zip format. I'd like to get Debian working on the phone and Busybox is a requirement.

Im confused, I got busybox installed from titanium backup. Is that the same one you need? If so install titanium backup, hit 'problems' and install busybox that way.

I made a custom rom I just posted with BusyBox preinstalled. I will see if I can post an update.zip with busybox in it soon.

ChrisDos said:
Does anyone have a compiled busybox for the EVO yet. Preferably in update.zip format. I'd like to get Debian working on the phone and Busybox is a requirement.
Click to expand...
Click to collapse
here is one of my busybox binaries which should get you going. you'll have to manually install it, adb push to sdcard and then using root, mv to /data and chmod 755. should be good to go. if you're using unrevoked root, you can put it in the shadow directory and it'll appear in /system/bin.
http://forum.sdx-developers.com/android-2-1-development/(source)-sdx-busybox-for-android-2-1/ - where we maintain our latest version of busybox thanks to LouZiffer. I use this binary in all my ROMs. Its our community trade off for features with size..
my personally hosted mirror isnt always as updated as the link above - http://www.joeyconway.com/sdx/busybox/busybox (its the recovery version from link above with more features)
i'm sure somebody will throw up an update.zip which might be easier for most users.

joeykrim said:
here is one of my busybox binaries which should get you going
http://www.joeyconway.com/sdx/busybox/busybox
Click to expand...
Click to collapse
Even better Will installing it out of recovery work since it needs to add symlinks? You will probably need to go into recovery, and then adb shell busybox --install.

chuckhriczko said:
Even better Will installing it out of recovery work since it needs to add symlinks? You will probably need to go into recovery, and then adb shell busybox --install.
Click to expand...
Click to collapse
yea, so depends. if you're as root in normal android mode, unrevoked or one of toast/maejrep's rooted ROMs you can manually install w/o rebooting to recovery. if you dont have root in normal android mode, no custom ROM and no unrevoked root, you'll need to go into the recovery mode with root access.
i think the command to put sym links into /sbin which would be in the default PATH is:
busybox --install -s /sbin
i havent really experimented to see what people are using as their default install locations ... sorry for the rough guide!

I installed busybox entirely from my phone using the directions laid out in the troubleshooting section on the TitaniumBackup webpage (sorry, new user cannot post link, but you can link to it from the app in the market). I have toast's root and radio and flipz's .6 ROM, and I was able to do it all using a terminal on the phone, so, no recovery.

Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.

ChrisDos said:
Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.
Click to expand...
Click to collapse
can you post the files and directions to so i can get it installed? thanks

ChrisDos said:
Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.
Click to expand...
Click to collapse
if you use toast's kernel source released here, you can compile a working kernel with ext4 support ... just throwing out ideas cuz i'd hate to see you stop with your progress!

Busybox Installation Instructions
I use Linux, well, for all my computers, including my phone
So these instructions are biased for Linux...
Boot into torch's recovery.
Download busybox from joeykrim:
http://www.joeyconway.com/sdx/busybox/busybox
Place it in a directory and create this script:
Install_Busybox.sh:
#!/bin/bash
echo "Mounting /system"
adb shell mount -v /system
echo "Mounting /data"
adb shell mount -v /data
sleep 3
adb push busybox /data
adb shell chmod 755 /data/busybox
adb shell /data/busybox --install -s /system/xbin
echo "Waiting for system to stabilize before unmounting"
sleep 3
adb shell umount -v /system
adb shell umount -v /data
chmod 755 Install_Busybox.sh
./Install_Busybox.sh
Windows/Mac users can just manually run the adb commands and it should work fine.

joeykrim said:
if you use toast's kernel source released here, you can compile a working kernel with ext4 support ... just throwing out ideas cuz i'd hate to see you stop with your progress!
Click to expand...
Click to collapse
Well, I compile kernels all the time for my laptop and Myth boxes. Is there a bit of a how-to for compiling the kernel for ARM and install it/replace the current kernel. It's be nice to find out how-to on how to make an update.zip to provide the install for everyone else as well.

Busybox reinstallation causes su problems

Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.

goister said:
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
Click to expand...
Click to collapse
Same problem, I am using a polaroid tablet, I installed busybox by doing the following
busybox --install /system/bin
I believe it overwrote some files and cant find the fix

[Q] Re: "Busybox Uninstaller v1.0 - Removes busybox and its +600 symlink files"

[Q] Re: "Busybox Uninstaller v1.0 - Removes busybox and its +600 symlink files"
I'm trying to use the script provided in the thread Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]. Would've asked this question there, but not allowed, being new to the forum. (Hello. First post.)
New to android in general, actually, but familiar with linux.
Anyhow, I tried using the script both using Flash from recovery method and running the script from terminal, but both fail.
Flash from recovery method fails with an error regarding package verification.
Not running CWM but the stock-thingy. Hardware is Samsung n8010 tablet. Factory-ROM (4.1.2) loaded through ODIN. Rooted.
Run script in terminal fails with a long row of "readling: applet not found".
Script was run in terminal, having su:ed and permitting root-rights. Also remounted system as RW.
Looking at bb-uninstall.log, I see a lot of
/system/bin/COMMAND is not linked to busybox but to ---> file not deleted
Click to expand...
Click to collapse

[Q][Solved][XT897] cifs module for CM 11 (3.0.101 Kernel)?

Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx

Fr4nz84 said:
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Click to expand...
Click to collapse
Why the quotes around "official"?
Cifs and nfs support is built-in, there's no need for additional loadable kernel modules (you can check https://github.com/CyanogenMod/andr.../arch/arm/configs/msm8960_mmi_defconfig#L3091 )
If mount fails for you, try busybox mount.
Btw., after CM11 M2, Motorola msm8960 2012 devices were unified under moto_msm8960 moniker in CM11.
Later, after the release of the official KitKat update for only a subset of the devices being part of the moto 2012 family, xt897 builds went under moto_msm8960_jbbl (jellybean bootloader) unified builds.
So the latest CM11 builds for xt897 can be found here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
For CM12, the builds were separated again, so CM12 builds for xt897 can be found again under http://download.cyanogenmod.org/?device=xt897

A other problem?
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.

I've always accessed CIFS shares thru an app like ES File Explorer. Works fine.

Fr4nz84 said:
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
Click to expand...
Click to collapse
CM11 M2 is quite old, so I can't be 100% sure it worked there, but I'm convinced that it worked fine even on such old build.
I mount cifs shares quite regularly on my xt897, so I guess I would have noticed if it was not working anymore in any milestone build.
Regarding SuperSU and BusyBox Free - there's no need to install anything like that, CM has built-in su and also busybox.
I'm on CM12 and I don't plan to restore CM11 any time soon (and certainly not M2, if anything it would be moto_msm8960_jbbl M12 or a recent moto_msm8960_jbbl nightly), but something like this has always worked for me:
Code:
su
mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I've just tested it (indeed with my own server path and user credentials) and it works fine.
To use busybox for mount, just replace "mount -o..." with "busybox mount -o..."
The stock CM busybox resides in /system/xbin , btw.

@arrrghhh good tip! Compared to AndSMB I can at least look at pictures without downloading with hand.
@kabaldan
You are totally right with cat /proc/filesystems I can see the Kernel supports cifs.
I had to install SuperSu because there was no su in terminal available.
After playing around, I was able to mount with:
mount -o username=franz,password=XXX,rw,nodev,relatime,default_permissions,allow_other -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
But it’s only available to the terminal where I executed the command. Do I have multiple root users?
I don’t know something in my system feels wrong.
Could there some other security policy I am not aware of?

It works now. It seems it was a update problem.
I wipe/clean the system with Open Recovery
removed all Files and Folders in /system (To remove old apps especially SuperSu)
And installed cm-11-20140104-SNAPSHOT-M2-xt897.zip again with Open Recovery
Now su is there on start and root is managed by the System. And I can mount cifs normally.
Whatever, now the shell seams not proper configured so I get this ^[[A^[[D^[[C for arrow keys, in su.
Also I can't get Link2Sd to work because mount give me constantly "invalid argument"( not more) even when I try it on console. Fells like it don’t want me to mount my second partition.

OK is a problem with the SD Card mount works normally. I tested it with another sd card.

[TOOL][MOD]Flashable Busybox/Toybox Merger v1.1 (12.02.2016)

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...