Hye, after i have succes root my xperia ion, busybox keep tell me that more than one copies of busybox found, i have read a thread about this and they said just delete it, ok i delete busybox that was installed to /sbin and open busybox again and it said busybox installed to /system/bin, ok that was fine. After i reboot, the busybox detected that more than one copy of busybox installed again. This thing happen after everytime i reboot, how to solve this?? your help is appreciated
Sent from my LT28h using xda premium
Related
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.
Hi Guys!! I've got a problem installing BusyBox here!!
I searched for the problem on google, but didn't find anything helpful, so thought someone can help here.............
The point was to get V6 Supercharger script running, which requires BusyBox. I already had BusyBox V. 1.19.2 installed, but as Zeppellin has described, versions above 1.18.2 could've caused problems, so I decided to install V1.18.2, via BusyBox app(by stericson) on market. It was unsuccessful to do the job, so i tried it with another app- BusyBox installer(by JRummy), but now this one is unable to detect root access!!!
PLUS, now root apps such as SetCPU, script manager are all getting FCs
I've already confirmed with the root access-- I am getting # sign with SU command.........
Please help someone.......Its all getting really weird!!!!
*EDIT*:- Now Wi-Fi not working too !!!!!---WTF????
You really make all things confusing better to clear data of superuser from settings and then flash older version of superuser and then use jrummy app to install busybox
Edit:Flash kernel again
Update su binary.
aspee
aspee said:
You really make all things confusing better to clear data of superuser from settings and then flash older version of superuser and then use jrummy app to install busybox
Edit:Flash kernel again
Update su binary.
aspee
Click to expand...
Click to collapse
Gosh!! Nothing above worked :\
Finally, had to restore \system through recovery and then reflash kernel and everything is back now
However, thanks for you reply!!!!
Sent from my LG-P500 using XDA App
maybe u should try it this way:-
1.install root explorer
2.at the top of root explorer u will see "mount r/w" (select it) such that it show u "mount r/o"
3.open busybox and try again to install it
i am not sure that it will work for u or not but works fr me
pm me if u want root explorer
kssood said:
maybe u should try it this way:-
1.install root explorer
2.at the top of root explorer u will see "mount r/w" (select it) such that it show u "mount r/o"
3.open busybox and try again to install it
i am not sure that it will work for u or not but works fr me
pm me if u want root explorer
Click to expand...
Click to collapse
Problem already solved bro!!
Thanks for reply though.........
Is busyBox built into CWM recovery kernals? is this common practice?
if so, and "I believe it is" How can I update my busyBox Version?
The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again.
So I geuse what Im asking for is verification basicly.
Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab?
By the way to all comers who would like to bash my noobness Bring it!
I say this because I can learn more from the bashing than from no response/answer at all.
That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Pirateghost said:
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
Click to expand...
Click to collapse
Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed.
I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot)
I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings.
However on the skyRocket I do not seem to have this problem I believe this is why.
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
While Great for My "I727" that doesnt help me on my "I777"
rdannar said:
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks but not at all what I was talking about.
Phatboyj420 said:
Thanks but not at all what I was talking about.
Click to expand...
Click to collapse
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
rdannar said:
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks again but your still off please re-read O.P.
Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot.
The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to
"/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread.
Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin).
Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot).
To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.
I have BB 1.18.4 still from the old doomlord kit, installed into system/xbin, and I noticed that some mods/tweaks/apps require it installed in /xbin, while others need it into /bin. So my question is, if I use Busybox Installer to install the 1.20.2 to both folders, will it harm my device having two busyboxes installed at the same time?
You could install it in xbin and then symlink it to bin.
Sent from my Nexus 7
Err, how to symlink it? I find something like console commands searching around, but i don't know where to put them =(
I think you have some learning to do.
You can install busybox in both directories. The order of directories in $PATH will prevent issues with having it installed twice.
Sent from my Nexus 7
Thanks, I'll go directly with the double install then.
Just one more thing that just happened, I usually use Busybox Installer for that, but when I select the installation for the right version, before dowloading the install files, it stops and says I have a bad internet connection, even tho my 3G works perfectly. Did anyone else experience this?
BillGoss said:
I think you have some learning to do.
You can install busybox in both directories. The order of directories in $PATH will prevent issues with having it installed twice.
Sent from my Nexus 7
Click to expand...
Click to collapse
Yeah, I know this is old thread, but I have some related questions: if busybox is already installed in system/bin by kingroot, why should I install a binary update in system/xbin as busybox installer wants to do by default? If it is in both paths, which one is going to do the job? or... Why do I actually want to have two busybox copies in two separate directories if I "can" have just one? And last: most people suggest to install busybox in system/xbin, so why kingroot choose to do it in system/bin?...
Man quetion.. I'm curious what the answers are to these please!..
Hello i have some problems while updating Busybox on my phone
i'v tried with theese two applications.
https://play.google.com/store/apps/details?id=stericson.busybox&feature=search_result
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&feature=search_result
but after reboot busybox fall back to the old version "1.16.2" (more details on the attachment)
sorry for my bad english, and thanks for help
ps: i tried to install on bin, and xbin
Busybox is embedded in ne kernels, so every reboot you reload the old version.
To fix permanently, decompile the kernel IMG and update busybox in the ramdisk
Sent from my MT11i using xda app-developers app