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.........
Related
Hi everyone, maybe this is a silly question but I don't want to screw my phone without asking first, so is there any tutorial or app about installing busybox on the P500? Or is it the "standard" procedure that involves adb, remounting r/w, copy ro /xbin etc?
Thank you!
I used a app called BusyBox Installer from Market.
I couldn't confirm if it worked, but you can try.
I installed it from the market
Android.Nis said:
I installed it fronte tue market
Click to expand...
Click to collapse
Ok but was it BusyBox Installer? I'd like to use a confirmed working app.
BTW I rooted my phone with z4root.
I downloaded BusyBox by Stephen (Stericson) =) This is the name
So I tried installing xRecovery (I think it was .3) on my new mini pro U20i which i rooted with z4root 1.3.0. HOWEVER, the busybox that came with it didn't work so I attempted to install another busybox... and I somehow bricked my phone lol.
The phone is fixed and rooted again but I would really like to get xRecovery working so I can flash roms.
Any help would be really appreciated
P.S. If you have any guides for backing up/flashing roms and partitioning sd cards that would be great!
johnpharrell said:
So I tried installing xRecovery (I think it was .3) on my new mini pro U20i which i rooted with z4root 1.3.0. HOWEVER, the busybox that came with it didn't work so I attempted to install another busybox... and I somehow bricked my phone lol.
The phone is fixed and rooted again but I would really like to get xRecovery working so I can flash roms.
Any help would be really appreciated
P.S. If you have any guides for backing up/flashing roms and partitioning sd cards that would be great!
Click to expand...
Click to collapse
Did you root with SOC?
No... should I have? Does it include xRecovery? Do you think it would be ok to unroot with z4root and the use SOC. I'm a noob to all this kinda thing Is SOC working with x10 mini pro 2.1 build 2.0.A.0.504?
1. root you device
2. install busybox from market only
3. try automatic installation(the safer way)
4. reboot
5. tap the back button several times
6. enjoy xRecovery
Tehouster said:
1. root you device
2. install busybox from market only
3. try automatic installation(the safer way)
4. reboot
5. tap the back button several times
6. enjoy xRecovery
Click to expand...
Click to collapse
Thanks Tehouster, but busybox isn't available on the market anymore...I've searched and I can't find it. That's why I ended up using an offmarket one before, ultimately bricking my phone lol.
Strange...I found busybox on the pc android market site, but not of my phone's market app?? I tried to install it via the pc site but
it said that my phone was incompatible? Now what?!
The market checks your phone to see there're compatible Apps available for your particular phone/ROM before showing you up the results, and that's why some may not find those particular Apps they're looking for, I sometime make use of Morelocale to search further outside my home region, hope this may help.
johnpharrell said:
Thanks Tehouster, but busybox isn't available on the market anymore...I've searched and I can't find it. That's why I ended up using an offmarket one before, ultimately bricking my phone lol.
Click to expand...
Click to collapse
Busybox is in my market.. strange.
Hi ive rooted my device and installed root explorer, also installed xrecovery, but i cant get it to work,
on a tut it says i need to install busybox, how do i install it? i cant find it on the store.
someone there who can help me
i tried to install it manually, but adb says exec:cp not found - the same error message from xrecovery what can i do?
Install Titanium backup, and click problems, then it will help you install busybox.
PressEsc said:
Install Titanium backup, and click problems, then it will help you install busybox.
Click to expand...
Click to collapse
I tried this method already, but to no avail. And BusyBox isn't available with my carrier/country it seems... Oh well!
Market don't show me busybox
Sorry for my poor english, i can't found the busybox installer on the market.
using my x10i i'm search "busybox" and show it in the 1st result, but
using a mini pro (U20i) don't show anithing from stericson
using 2.0.2.A.0.24 nordic
Lo bueno es que voy a aprender ingles antes de vuestra respuesta...
Sent from my froyo X10 using XDA App
me too.i also cant find the busy box and xrecovery installer.it strange.why oh why.i really want the x recovery in my phone
here you have a pretty good working guide
http://forum.xda-developers.com/showpost.php?p=9818553&postcount=535
he mentions chmodding with adb, but doesnt now the command - it's pretty straight forward
write following in adb shell
Code:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system 3 /system
# chmod 777 system/bin
# exit
$ exit
afterwards push the files downloadet from his post with
Code:
adb push %filepath%\busybox %filepath%\chargemon %filepath%\xrecovery.tar /system/bin
where %filepath% is the path to the folder where you extracted the 3 files
If you have problems with ddms, just write
You can find both on Google. Just be patient an look very well ... I found it.
for busybox, intall titanium backup, and xrecovery you will need to install zhidu's xRecovery mini... i have the same problem before..
http://forum.xda-developers.com/showthread.php?t=932194
Thank youuu.ive installed it.
Sent from my U20i using XDA App
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
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
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.