Hey guys,
I was following this instruction here:
http://nexusonehacks.net/android-hacks/droid-hack-how-to-install-thai-font-on-droid/
hoping to install Thai fonts to my X10i, but having trouble installing Busybox. I was told to put the busybox file into the root folder of my SDcard...is that /sdcard/...?
I did the following commands on Terminal Emulator:
Type each line and press the enter key.
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# mkdir /data/busybox
# cat /sdcard/busybox > /data/busybox/busybox
# chmod 755 /data/busybox/busybox
# mkdir /data/local
# cd /data/busybox
# ./busybox –-install
# cp /sdcard/fonts/* /system/fonts
And when I got to the busybox install, it says something like directory not found.....So I'm wondering whether I put the Busybox file in the right location in the first place...
Can somebody help me out? Greatly appreciate it!!
Search the marketplace for the busybox installer, it does it automatically.
Oh really? I did download Titanium Backup and use it to install Busybox. Is it the same thing?
Once I get it installed, can I just use "cp" in Terminal Emulator? How do I use it?
Yeah, if you can use Titanium Backup, then you have busybox installed.
I'm not sure about that, maybe someone else can jump in and assist.
Yes, once you've installed Titanium Backup, and used it to install busybox, you are ready to go. I didn't have to separately install busybox when I loaded Thai fonts into my phone.
if you installed titanum backup just press menu >problems >download busybox and it will be installed for you
Related
Hi,
since a few days I have my first andriod mobile the HTC Hero. I have rooted it and everything works fine.
However, I found several interesting images for the G1 (JesusFreke or CyanogenMOD and so on). I suppose that they will not run on the HTC Hero :-( (yet). Sombody know if there is someone working on it? A google search is not that easy because the most roms are based on the HTC Hero sence and so you can easy find 100 hits with hero but all roms are not for the hero itself.
Does somebody have busybox running on the hero? I searched for a while but found nothing Hero specific. My first try to use a exiting manual for G1 did not work without problems. The most manuals are old and suggest to use a custom rom which include busybox.
Maybe someone has a hint for me
I want to test debian but the istaller use cp and so on. So busybox is a good starting point.
Cheers
Visios
download the attachment (busybox taken from cyanogen's rom), extract busybox and copy it to sdcard, then (if you have root):
Code:
adb shell
su
mount -o remount,rw /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mount -o remount,ro /dev/block/mtdblock3 /system
enlightener said:
download the attachment (busybox taken from cyanogen's rom), extract busybox and copy it to sdcard, then (if you have root):
Code:
adb shell
su
mount -o remount,rw /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
tx for your info and the extracted busybox bin. It worked without any problem.
Do you have tried to use busybox install and export the path ?
enlightener said:
download the attachment (busybox taken from cyanogen's rom), extract busybox and copy it to sdcard, then (if you have root):
Code:
adb shell
su
mount -o remount,rw /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
when i type adb shell it says
adb permission denied..
Help please
Yeah, I could google it but I'll just ask here instead, busybox - what's it good for?
It provides a lot of the standard Linux/Unix utilities - such as cp, rm, df, ls, ps, grep, etc. The toolbox program provided in the HTC ROM is a "crippled" replacement for busybox and doesn't have some of the functionality. For example, Market Enabler doesn't work with the stock ROM because toolbox doesn't provide the grep utility.
BlueHawk said:
It provides a lot of the standard Linux/Unix utilities - such as cp, rm, df, ls, ps, grep, etc. The toolbox program provided in the HTC ROM is a "crippled" replacement for busybox and doesn't have some of the functionality. For example, Market Enabler doesn't work with the stock ROM because toolbox doesn't provide the grep utility.
Click to expand...
Click to collapse
Oh, I see. Well explained, sir!
Busybox 1.15.3 for android for anyone interrested:
Code:
[URL="http://www.mediafire.com/?wcknmnhtin0"]http://www.mediafire.com/?wcknmnhtin0[/URL]
Does anybody know what version of Busybox is in the original post?
And if I want to upgrade, should I just follow the instructions over again with the newer version?
enlightener said:
download the attachment (busybox taken from cyanogen's rom), extract busybox and copy it to sdcard, then (if you have root):
Code:
adb shell
su
mount -o remount,rw /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Sorry for the newb question but... where do I type this stuff?
jpmi23 said:
Sorry for the newb question but... where do I type this stuff?
Click to expand...
Click to collapse
on a command line on your pc. this is not the right place to start for you, get a guide on how to setup adb on your pc first.
Wow. "abd". That's a new term now isn't it.
Ok. I'll skip it. Just looking to control my Samsung Moment on my PC like I was able to with my WM phones.
I'll keep looking around. Thanks for the help.
ok..so ive recently flash my X10i stock 2.1 eclair to Wolfbreak CM 6.1.3 v5
and im having problems regarding my Openvpn settings.
**cant check my config files
so what i did is to follow the old thread regarding the old openvpn settings for eclair and issue this following command on terminal emulator
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
busybox insmod /sdcard/openvpn/tun.ko
busybox cp /sdcard/openvpn/openvpn /system/xbin/openvpn
busybox cp /sdcard/openvpn/openvpn /system/xbin/tun.ko
chmod 700 /system/xbin/openvpn
mkdir /system/xbin/bb
busybox ln -s /system/bin/busybox /system/xbin/bb/ifconfig
busybox ln -s /system/bin/busybox /system/xbin/bb/route
busybox mount -o remount,rw /dev/block/mtdblock2 /system
busybox cp /sdcard/openvpn/chargemon /system/bin/chargemon
busybox cp /sdcard/openvpn/busybox /system/bin/busybox
reboot
Click to expand...
Click to collapse
then my X10i will reboot and will start acting up. Force close keeps on popping and the device will automatically restart.
ive used those command when i used 2.1 eclair before and everything is working fine.
if anyone could enlighten me about this will be a great help.
also if you need other info, you can pm me or reply to my post.
this is my old working settings when i used eclair.
1.rooting my phone
2.install busy box
3.install terminal emulator
4.install openvpn application
5.install openvpn settings
6. issue this command in terminal
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
busybox insmod /sdcard/openvpn/tun.ko
busybox cp /sdcard/openvpn/openvpn /system/xbin/openvpn
busybox cp /sdcard/openvpn/openvpn /system/xbin/tun.ko
chmod 700 /system/xbin/openvpn
mkdir /system/xbin/bb
busybox ln -s /system/bin/busybox /system/xbin/bb/ifconfig
busybox ln -s /system/bin/busybox /system/xbin/bb/route
busybox mount -o remount,rw /dev/block/mtdblock2 /system
busybox cp /sdcard/openvpn/chargemon /system/bin/chargemon
busybox cp /sdcard/openvpn/busybox /system/bin/busybox
reboot
Click to expand...
Click to collapse
7.open the config file and wait for it to connect.
but those above mention steps doesnt work anymore in 2.2 froyo cm 6.1.3 of wolfbreak
tried it and my phone starts acting up.
reflash again, this time openvpn settings is the only application i installed because as far as i know, wolfbreak custom rom is already been rooted and includes busy box and openvpn application but no luck..
help please.
Hi There!
I think you've followed my old thread so i've made this very same codes work on every Froyo Modded ROM... Wolfbreak already have the openvpn binary installed in /system/xbin so you'll have to do 1 extra step.
1.- Open Terminal Emulator and issue this comand
Code:
rm -r /system/xbin/openvpn
mkdir /system/xbin/bb
ln -s /system/bin/busybox /system/xbin/bb/ifconfig
ln -s /system/bin/busybox /system/xbin/bb/route
cp /sdcard/openvpn/tun.ko /system/lib/modules/tun.ko
chmod 644 /system/lib/modules/tun.ko
2.- Download OpenVPN installer from Market (Free)
3.- Click on Install and choose the following options and you'll see two screens:
3.1 - In the first one choose "/system/xbin"
3.2 - In the Second one choose "System/xbin/bb"
4.- Go to OpenVPN settings and go to Advanced>TUN module Settings>Path to tun module> This should be /system/lib/modules/tun.ko
5.- Choose your OpenVPN configuration and you'll be done.
Report back if this helps... At least i've test it in the following ROMS:
* Trip's MIUI Roms
* Wolf's CM Roms (all Variants)
* Zdizihu's Free X10
* Jerpelea's CM 7 GB Roms
thanks mate for the reply,
anyway, i somehow manage to fix the above mention problem and somehow got my config file to get connected using the above post.
but everytime it get connected, a lot of errors occur.
1.force closed.... .....
2.linux....error....... .....fork error...
i cant remember the whole error message because it only pops up for a bit.
tried to reflash twice but to no avail, same results hapen.
so i gave up and flash back to 2.1 kx10 aosp and everything is working again..
>>>>>>>> REQUIRES working adb shell <<<<<<<<<<<
1. Download this zip, and extract its contents to /sdcard/extracted/rootED01/ (Root Explorer, which is not required, will do this by default when you click Extract All)
2. For each of the two STEP.txt files (in the zip and copied below), open an 'adb shell' and paste its contents into your shell.
Includes:
+ instructions, with pasteable root and unroot
+ Superuser.apk
+ su
+ busybox
+ rage.bin
CREDITS:
* adrynalyne for his version of busybox.
* 743C for rageagainsthecage exploit binary.
* ChainsDD for Superuser.apk
* Eousphoros on droidforums for his very similar guide.
********
Most people will prefer to use Super OneClick root. I only wrote this guide in response to finding this, and hoping that I could indeed get terminal emulator to root.
Unfortunately, I could find no way to change the permissions of the copied rage.bin without using adb. If anyone can find a way around this for froyo, I would love to hear about it!
I decided to post this guide anyway. At least it's a manual root that works with the official ED01 froyo update. If there is interest, I will go into detail about installing ADB, etc.
rootED01.zip
MD5: e97913f3bed5283c89d5b755a66f28e5
SHA-1: ab87ad372d0f9ba9d1d5043175953e91bdef77f3
# >>>>>>>>>> STEP ONE <<<<<<<<<<<<<
# Note: This path must match the files you extracted!
export ROOT_TOOLS=/sdcard/extracted/rootED01
cd $ROOT_TOOLS
cat rage.bin >/data/local/tmp/rage.bin
cd /data/local/tmp
chmod 777 rage.bin
./rage.bin
echo "Rage.bin will be done applying root. Reopen shell in 10 seconds."
# >>>>>>>>> STEP TWO <<<<<<<<<<<
# Do not procede with this step until you see a # in newly opened shell.
# Note: This path must match the files you extracted!
export ROOT_TOOLS=/sdcard/extracted/rootED01
# mount /system for writing & copy su & busybox
mount -o rw,remount /dev/block/stl9 /system
cd $ROOT_TOOLS/xbin
cat su >/system/xbin/su
cat busybox >/system/xbin/busybox
cd /system/xbin
chmod 4755 su
chmod 4755 busybox
#install Superuser
cd $ROOT_TOOLS/app/
cat ./Superuser.apk >/system/app/Superuser.apk
reboot now
# >>>>>>>>>> UNROOT <<<<<<<<<<<<
# get root
su
# mount /system for writing
mount -o rw,remount /dev/block/stl9 /system
#delete su & busybox
rm /system/xbin/su
rm /system/xbin/busybox
# delete Superuser.apk
rm /system/app/Superuser.apk
# delete other clutter
rm /data/local/tmp/rage.bin
# Once you reboot, the last of your root will be gone
mount -o ro,remount /dev/block/stl9 /system
Hey everyone,
I am a new member and I haven't ever developed anything for Android, even though I am a CS major, thus I am not very familiar with kernels , bootloaders and recoveries.
Anyway, I decided that I wanted BlueStacks on my computer. I have been going through a variety of Android emulators and this is the one interface I like the most.
I have downloaded the pre-rooted version of BlueStacks 2.0.0 (from here: http://forum.xda-developers.com/wiki/BlueStacks_App_Player) and I have downloaded some apps to check if it was rooted, in fact. And yes, it is, but it doesn't have SuperSU installed.
I have then tried to install SuperSU. But once I click on SuperSU icon I get an error message "There is no binary SU installed and SuperSU cannot install it .... " and it suggests to install SuperSU manually.
Since then I have been reading a little about how Android boots and I have tried some apps like RecoveryReboot, QuickBoot, etc. None of them work. I have tried to find ways to see if the BootLoader is locked or to discover if the system has or doesn't have a recovery but no luck. I believe there's no recovery mode available.
Instead of going through the kernel and bootloader (which I am not familiar with and would take me ages to figure out) I decided to look for alternative ways.
I have found this apk: http://forum.xda-developers.com/showthread.php?t=2250555 which looked promising because it would allow me to install SuperSU without going through recovery mode. But, unfortunately, after selecting the zip file with SuperSU, I receive an error saying that this package is not a flashable zip.
Anyway, instead of keep looking, I was wondering if anyone has an idea of a way to install SuperSU in this version of BlueStacks.
I know that some previous versions have SuperSU installed by default, but I like BlueStacks 2 interface and some functionalities better.
Thank you!
How to install SuperSU and root BlueStacks 2.0.x.x manually
I'm a total noob when it comes to android but somehow I've managed to root latest 2.0.8.5638 with trial and error method Here is what I've done. I'm not sure if its the right way tho
1. Download SuperSU 2.46 from their site or download this: https://dl.dropboxusercontent.com/s/v5kje7gsb9q3pp8/tmp.7z?dl=1 I've only added necessary files in the zip.
Open cmd and push this files to BlueStacks. If you've downloaded complete supersu package then you'll need "libsupol.so, su, supolicy" from "x86" folder and "Superuser.apk" from "common" folder. You'll also need adb installed and added to your environment variable path or you can use "C:\Program Files (x86)\BlueStacks\HD-Adb.exe" instead of adb...
Code:
adb push xbin\su /data/local/tmp
adb push xbin\supolicy /data/local/tmp
adb push lib\libsupol.so /data/local/tmp
adb push app\Superuser.apk /data/local/tmp
2. Run adb shell in cmd
Code:
adb shell
And type this in shell, it will grant you root permission. They left this and also busybox in latest versions.
Code:
/system/xbin/bstk/su
3. Remount with rw rights. Not sure about first and last though, /dev/sda1 /system is necessary.
Code:
mount -o rw,remount /dev/block/sdb1 /data
mount -o rw,remount /dev/sda1 /system
mount -o rw,remount / /
4. cd to /data/local/tmp and give these permissions below to files.
Code:
cd /data/local/tmp
chmod 0775 su
chmod 0775 supolicy
chmod 0664 libsupol.so
chmod 0664 Superuser.apk
5. Move/copy this files.
Code:
cp su /system/xbin/su
cp su /system/xbin/daemonsu
cp supolicy /system/xbin/supolicy
cp libsupol.so /system/lib/libsupol.so
cp Superuser.apk /system/app/Superuser.apk
6. You have to edit init.sh file. You can do it with vi
Code:
busybox vi /system/etc/init.sh
Scroll down to end of script.
You'll see something like this.
Code:
init|"")
do_init
;;
esac
change it to
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
then exit with ":wq!"
or alternatively you can copy that file to bluestacks shared folder and edit it with your text editor then copy it back. Its easier this way.
Code:
cp /system/etc/init.sh /storage/sdcard/windows/BstSharedFolder/init.sh
edit init.sh file in "C:\ProgramData\BlueStacks\UserData\SharedFolder" then copy it back to BlueStacks.
Code:
rm /system/etc/init.sh
cp /storage/sdcard/windows/BstSharedFolder/init.sh /system/etc/init.sh
P.S. if you use "cp -f" you may not need to write "rm" command, haven't tried it myself. Like I said, noob here
Ok, now you should have root access.
You may want to install apps like apex launcher, root explorer etc. Then you can uninstall BlueStacks' bloatware if you want.
::bluestacks things
Code:
rm /mnt/prebundledapps/com.google.android.apps.photos-1.apk
rm /mnt/prebundledapps/downloads/BstFakeGps.apk
rm /mnt/prebundledapps/downloads/MyBluestacks.apk
rm /mnt/prebundledapps/downloads/bluestacksHome.apk
rm /mnt/prebundledapps/downloads/bluestacksServices.apk
rm /mnt/prebundledapps/downloads/newAppFinder.apk
rm /mnt/prebundledapps/downloads/setupWizard.apk
rm /data/downloads/AppGuidance.apk
rm /data/downloads/AppSettings.apk
rm /data/downloads/BstFakeGps.apk
rm /data/downloads/MyBluestacks.apk
rm /data/downloads/S2P.apk
rm /data/downloads/bluestacksHome.apk
rm /data/downloads/bluestacksServices.apk
rm /data/downloads/newAppFinder.apk
rm /data/downloads/setupWizard.apk
7. Remount with readonly again.
Code:
mount -o ro,remount /dev/sda1 /system
mount -o ro,remount / /
8. Don't know what it does but I've seen it on some instructions
Code:
sync
9. Open a cmd with admin rights and kill BS2 completely then open it again.
Code:
taskkill /f /t /im "BlueStacks.exe" /im "HD-Agent.exe" /im "HD-Adb.exe" /im "HD-BlockDevice.exe" /im "HD-FrontEnd.exe" /im "HD-Network.exe" /im "HD-Service.exe" /im "HD-SharedFolder.exe" /im "HD-UpdaterService.exe" /im "HD-LogRotatorService.exe"
10. Open SuperSu app in BS2, it may want you to update su binaries. Update it with normal option and restart it. Use taskkill way to completely kill it again.
11. Run adb shell again. You may need to run "adb kill-server" command first.
12. Run "adb shell" command then type "su". SuperSu will want grant permission approval for shell. Give it and now you should have a rooted BS2
Hi,
I've got a Probox2 AndroidTV box on Marshmallow.
I would like to mount a remote NFS share into it's filesystem, so that the share is accessible to all apps (I've disabled mountspace in SuperSU).
I can do this via terminal or SSH using the following 3 lines
Code:
su busybox mkdir -p /mnt/nfs/roms
su busybox chmod 777 /mnt/nfs
su --mount-master -c busybox mount -o rw,nolock,hard,intr,vers=3 -t nfs x.x.x.x:/mnt/Roms /mnt/nfs/roms
This works well and my Apps can find the network shares.
However I would like this be mounted automatically at every boot...
I've tried ScriptManager with this as the script
Code:
#!/system//bin/sh
su busybox mkdir -p /mnt/nfs/roms
su busybox chmod 777 /mnt/nfs
su --mount-master -c busybox mount -o rw,nolock,hard,intr,vers=3 -t nfs x.x.x.x:/mnt/Roms /mnt/nfs/roms
The script doesn't work from script manager or cli. (I know nothing about scripting).
I'm unsure how to go about getting it run/work....
Please could someone explain to me how to get those lines to run after boot or how to fix the script...
Thanks