Guys my phone took a nose dive. I flashed back to global 2.1 from Eternity 2.1. I rooted via superoneclick. Installed busybox so I can reinstall xrecovery. Now when I try to install busybox it is telling me I am rooted but will not install due not being nand unlocked or unable to remount. Please help fast.
Update: I tried rooting with z4 still unsuccessful. busybox is in system/bin so I do not know. First time I have ran into this type of problem. do not know if is on my end or busybox's
1. remove busybox
- use rootexpoler mount r/w in /system/bin/busybox delete it
- download busybox in market and install busybox
2. xRecovery
copy 3 file /sdcard/android/data/com.zoz33.xRecoveryInstall/Xrecovery.rar/system/bin/
- chargemon
- busybox
- xrecovery.tar
to /system/bin/ mount r/w and past 3 file in filder
thanks I figured out that it was a bad flash file I used. It wouldn't save the information I was putting into it.
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
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?
K, I'm rooted, with hasoon's toolkit, have Titanium Backup, I can delete system apps, back them up,..., no problem.
BUT, installing BusyBox is a no go
edit -> still having problems reinstalling busybox - i wrote a script to flash it to the system/xbin folder through cwm, which works, but i can't make the permission for busybox to execute stick after a reboot - whenever i reboot, i have to manually set it to execute in root explorer or it's useless.
Can someone help me write a cwm script to flash busybox to /system/xbin through cwm and make it permanently executable ?
bumping this - need help - anyone ?
edit -> still having problems reinstalling busybox - i wrote a script to flash it to the system/xbin folder through cwm, which works, but i can't make the permission for busybox to execute stick after a reboot - whenever i reboot, i have to manually set it to execute in root explorer or it's useless.
Can someone help me write a cwm script to flash busybox to /system/xbin through cwm and make it permanently executable ?
give this a shot
http://forum.xda-developers.com/showthread.php?t=1772338