I rooted my phone using GingerBreak, but can't install Busybox. Downloaded it from market but it never finishes installation, saying there's already another installation of busybox and immediately quits after. Any ideas how to install it properly?
I think it means Gingerbreak also installed busybox and installing another instance is not necessary. It could also mean that there is a special version for your device
after rooting some programs asked me to install busybox, so it rather wasn't installed... and they're still asking now, so nothing changed
install root explorer
create folder /system/xbin.change permissions to r/w
try again to install busybox
this work for me
Related
hi guys,
new to all this and have rooted my x10 mini mainly in order to remove excess apps that came with the phone (and i'm sure i'll start using root access for other things too!)
having a bit of a problem though...
what i've done so far:
updated from OEM 1.6 to 2.1 via sony webste
used SuperOneClick to gain root access
added SuperUser
added titanium backup and used that to download busybox
installed terminal emulator
in terminal emulator i enter su - and this gives me access fine.
however when i type in busybox it says not found. i've rebooted after every app installation etc.
i gathered (probably incorrectly) that this may be because busybox isn't in a path or something, so i would need to navigate to the busybox folder first? however i cant find anything called busybox on my SD card!!
help please!!
cheers, Adam
well i still cand find busybox, BUT.....
didn't realise I can browse root with ES File Explorer that I already had - gunna delete apps now
cheers!!
<edit>
scrap that, says i'm not allowed lol.
if i buy root explorer from the market i guess that'll work?
lincoln_dj said:
if i buy root explorer from the market i guess that'll work?
Click to expand...
Click to collapse
it does
lincoln_dj said:
hi guys,
new to all this and have rooted my x10 mini mainly in order to remove excess apps that came with the phone (and i'm sure i'll start using root access for other things too!)
having a bit of a problem though...
what i've done so far:
updated from OEM 1.6 to 2.1 via sony webste
used SuperOneClick to gain root access
added SuperUser
added titanium backup and used that to download busybox
installed terminal emulator
in terminal emulator i enter su - and this gives me access fine.
however when i type in busybox it says not found. i've rebooted after every app installation etc.
i gathered (probably incorrectly) that this may be because busybox isn't in a path or something, so i would need to navigate to the busybox folder first? however i cant find anything called busybox on my SD card!!
help please!!
cheers, Adam
Click to expand...
Click to collapse
Superoneclick does not install busybox
Gothic-4-Schiffer said:
Superoneclick does not install busybox
Click to expand...
Click to collapse
i know. that's why i said i used titanium backup to try to install it, as per instructions elsewhere on this site
lincoln_dj said:
i know. that's why i said i used titanium backup to try to install it, as per instructions elsewhere on this site
Click to expand...
Click to collapse
Look for it in the market. That one works, i had the same problem. Titanium seems to install an old version of this one, and sometimes it fails.
Sent from my X10mini using XDA App
thats the busybox version i use for x10 mini 2.1 update1 (rooted of course):
http://dl.dropbox.com/u/1229065/busybox
copy it to "/system/bin/"
even better check this http://www.omapedia.org/wiki/Android_Installing_Busybox_Command_Line_Tools
My Razr Maxx installed the OTA ICS update today. There were no error messages. Everything seemed to run fine. And on top of that I thought that my root was preserved.
Well, I have an old version (3.0.3.2) of SuperUser intalled that I cannnot uninstall. I cannot mount /system/ as read-write using ADB. I can't mount /system/ as rw using Terminal Emulator on the phone. I tried the one-click script EternityProject EasyRootICS to install root and it seemed to work (no errors reported), but when I edited the batch file to get rid of all of the CLS (clear screen) commands, I was able to see that when it tried to write the new superuser app to /system/bin/ it's failing (with no error reporting).
So what do I do now?
The bottom line is that I need root, but I don't know how I can get root without getting rid of my old SuperUser installation first.
I have the exact same problem..... I can't get rid of Superuser, but I can't get access too use any root applications. SU denies all of them...
Go to this link here and where it says "Note: If you don't get root by other method root attempt with su and Superuser.apk already installed." download from that link.
http://www.mod2xtreme.com/showthread.php?13332-TOOL-ROOT-Razr-EternityProject-EasyRootICS-Win-Linux
It helped with Superuser not working properly.....
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?
Hi all. As flashing SuperUser via CWM doesn't give an uninstall option, would it be better to install
it from the Play Store, or is flashing better for some reason.
Thanks.
I think flashing is better because:when you root your Tab,in addition to Superuser you inject a file named "su" in the folder "bin" of your OS,but if you install Superuser you must put that file there manually...but there is a way:in the flash able zip remove the Superuser APP,and after flashing install Superuser or SuperSU according to your OS.
arashtarafar said:
I think flashing is better because:when you root your Tab,in addition to Superuser you inject a file named "su" in the folder "bin" of your OS,but if you install Superuser you must put that file there manually...but there is a way:in the flash able zip remove the Superuser APP,and after flashing install Superuser or SuperSU according to your OS.
Click to expand...
Click to collapse
Thank you.
I flashed CWM, and then installed SuperUser via Play, but it didn't work. I didn't know about the "su" file.
So I uninstalled SuperUser, and flashed the file I had on hand, which is SuperSU.
Worked like a charm and everything is working.
Got an "update available" message this morning, which was for SuperSU. Updated, and all is well.
Thanks again!
Hi,
first of all thanks to everyone that works here, I have been visiting this forums for about 3 years.
I currently have a 5.0.2 with htc sense 6.0
Kernel version 3.4.10-gd7bdf6a [email protected] #1 SMP PREEMPT (this is what it read after attempting root)
To root it, I installed drivers (HTC Sync manager, mini-SDK tools, java), unlocked bootloader as instructed on htcdev.com/bootloader, went to fast boot, installed recovery-clockwork-touch-6.0.4.6-m7ul.img, moved UPDATE-SuperSU-v1.94.zip to my sdcard, and went on recovery to install this zip hoping it would be rooted. After all this I noticed Titanium Backup pro didn't have access to root, downloaded Root Checker Basic by joeykrim and in fact it said "Sorry! Root access is not properly installed on this device." Then I went on my apps drawer and noticed that strangely SuperSU is installed, but when I opened it it reads "There is no SU binary installed, and SuperSU cannot install it. This is a problem!".
After all that I tried downloading Superuser instead Superuser-3.1.3_superuserdownload.com.rar, but my device on recovery couldn't even see the RAR file, meaning on recovery that file didn't even show, so I tried extracting files to a folder of the same name and then compressing it again as a zip file. It could read fine and I attempted installing it again on recovery CWM but the installation started and aborted instantly. So I tried reinstalling SuperSU again, after deleting all cache/data/system/delvik, but again same problem. SuperSU is installed, but the same problem message pops up, and Root Checker still reads the device isn't rooted properly.
Strangely, Busybox installer says my device is rooted but after tapping install it said it failed. Root Check by JRummy Apps says device is rooted too.
Thanks in advance, let me know what other questions you have.
Additional info,
Root Check details reads
BINARY /system/xbin/su
PERMISSIONS rwsr-sr-x (6755)
VERSION 1.93:SUPERSU
ADB ROOT Enabled
Use this zip file. Flash it using whatever recovery you have currently. https://download.chainfire.eu/735/SuperSU