Right im using the google ion ota update from the htc website
.
Im trying to root it (Done) add busybox (followed instructions to the t and no joy) and install superuser.apk
busybox
mkdir /data/busybox
cat /sdcard/busybox > /data/busybox/busybox
chmod 4755 /data/busybox/busybox
cd /data/busybox
./busybox --install
export PATH=/data/busybox:$PATH
Also tried all that but with /system/xbin instaed of /data
Im testing using louder volume hack.It isnt working, i have root i guess its this?
Superuser
after doing
cat sh>su
etc..etc..
and installing superuser i cant get it to work?doesnt pop up saying always allow etc?Any help would be frigging awesome thanks
--------------------------------------------------------------------------------
Busy-Behold V.1
This thread contains instructions (to lazy to post) and a script to successfully install and run busybox on your Behold 2. Please download the Script below. If you prefer not to use a automated script then I will also post instructions later.
MAKE SURE YOU HAVE PERSISTANT ROOT AND ADB ACCESS
Instructions:
Download Zip below and extract to your desktop in a folder called BusyBehold then once extracted plug in your phone and make sure you disable mass storage mode and Samsung Studio is selected. Then double click on BusyBehold2 and follow the instructions on the script. If you have any issues or trouble or you know how to clean this up a bit more let me know. Enjoy.
Click to expand...
Click to collapse
That's nice and all, but this is a HTC Dream dev forum...
Here is what i got???
Pushing Busybox to /sdcard
1363 KB/s (1745016 bytes in 1.250s)
Push Complete
Pushing BusyBehold Script to Phone
12 KB/s (407 bytes in 0.031s)
Push Complete
Don't forget to follow the instructions above , make sure you SU first
$ su
su
# sh /data/local/BB.sh
sh /data/local/BB.sh
: not found
/system mounted
: not found
3408+1 records in
3408+1 records out
1745016 bytes transferred in 0.496 secs (3518177 bytes/sec)
: not found
Now we CHMOD
: not found
: No such file or directory/busybox
CHMOD Complete
: not found
Operation Finished
: not found
BusyBox Installed Successfully
: not found
Now adb shell and type in busybox and/or download Super User File Browser from t
he market.
Now type exit to complete script.
# exit
exit
$ busybox
busybox
busybox: permission denied
$ su
su
# busybox
busybox
busybox: permission denied
#
As those of us who are rooted know, the unrEVOked process has us installing busybox (or, if using the final payload, installs it for us). As those of us using Titanium Backup know, Titanium wants to update that busybox to a later version.
Doing some internet research, I note that busybox is distributed here:
http://busybox.net/downloads/
And the lastest update, as of this posting, is v1.7 (7/6).
Does anyone know if it is safe to download updates from this site, uncompress, and push to the phone?
I know the old instructions were:
adb push busybox /sdcard/busybox
adb shell
$ su
# export PATH=$PATH:/system/bin
# cd /system/bin
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# rm /sdcard/busybox
But is this still the case?
These downloads are only snapshots of the source tree. no compiled binaries to push on your device.
So I rooted my vibrant and extracted busybox to the xbin folder so I could leave it out of commands, but now I can't remember what was in xbin originally. I need to know because I am writing myself an unrooter script. Now I seem to recall that it was empty, but I am not sure enough to go ahead and blithely rm -r * the contents of xbin.
went to terminal and typed:
$su
#ls system/xbin
ipctool
busybox
su
#
next time post questions in general
Hi,
I've just replaced the stock toolbox with busybox provided by netarchy kernel package. Maybe there is a better way to do this, but I'm just playing with my new phone
Anyway, this is what I did:
Info
nexus model: I9023
rom: stock 2.3.4 with root permission
kernel: 2.6.35.13-netarchy-nexus-1.3.7-bfs-2.3.4
busybox version: 1.16.0 (included in netarchy kernel package)
Entering adb shell
Code:
adb shell
Inside adb shell:
Replacing toolbox with busybox
Code:
mount -o rw,remount /dev/block/mmcblk0p1 /system
busybox mv /system/bin/toolbox /system/bin/toolbox.bak
busybox ln -s /system/xbin/busybox /system/bin/toolbox
mount -o ro,remount /dev/block/mmcblk0p1 /system
Add a new command
After remounting rw /system
Code:
ln -s /system/xbin/busybox /system/xbin/COMMAND
For example:
Code:
mount -o rw,remount /dev/block/mmcblk0p1 /system
ln -s /system/xbin/busybox /system/xbin/chroot
mount -o ro,remount /dev/block/mmcblk0p1 /system
If you know a better way, tell me! Anyway I hope this could be useful
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
snandlal said:
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
Click to expand...
Click to collapse
Or just download BusyBox from Titanium Backup.
Code:
# busybox --install /system/xbin
should do the trick -- be warned, you'll get *a whole lot* of symlinks to busybox
snandlal said:
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
Click to expand...
Click to collapse
Great, thanks. I've installed that busybox and it works great!
suksit said:
Code:
# busybox --install /system/xbin
should do the trick -- be warned, you'll get *a whole lot* of symlinks to busybox
Click to expand...
Click to collapse
Yes, I installed busybox in /system/xbin and it created a lot of symlinks, but it's ok because in this dir there is almost nothing.
Anyway, thanks for the tip
???
Weird! After running shell script, I can no longer stay connected on wireless for more than a couple of minutes. I think something was replaced and it shouldn't be replaced!
Any hint?
In most Android systems, the c binary stalk is installed in /system/bin and is handled by TOOLBOX.
If we install BUSYBOX with any of the apps mentioned above, it will most likely be installed in /system/xbin
So at the end we'll end up with 2 utilities handling some binaries that are clones as it show in both /system/bin and /system/xbin
and because the PATH includes both locations then wouldn't that create some complications and possible hanging/crashing of the android system ???