Does busy box come with supersu? Can I hurt my phone installing busy box?
SuperSU is way to ROOT cell...it adds "Superuser.apk" in system\app folder.
also it adds "su" file to system\xbin (and sometimes in system\bin)
busybox is a tools app (usually found in system/xbin or system/bin)
current version is v1.20.2
-you won't ever see it in the App drawer
- you can download busybox installer from market, that is a app that has 5 busybox files inside and will install to your cell phone,
then you can delete the app after you install busybox.
-all DEV's inject SuperUser, busybox, and more into all ROM's
-when u run Titanium Backup, it uses it's own busybox tools (currently it uses v1.18.4) it shows that on startup page , when u run app.
I would say, no, It doesn't harm ur device. I've been using it for many yrs and i always make sure i have most current version on all my rom's.
Related
I have installed Busybox installer from Marketplace. I also managed to install Busybox 1.17.1 Now if I try to update Busybox from installler first I will get empty box with OK button and the status says: Looking for BusyBox. If I then press install the whole program crashes. I also tried to update Busybox from Titanium Backup but it carshes also. I have a stock rom 2.51.1 which is of course rooted and OC'd. So nothing special. What is wrong? What can I do?
logcat pls.
The crash for Titanium Backup was caused by Droidwall. I uninstalled then the Busybox installer which is now only Busybox(?) in Marketplace and then installed different Busybox installer and I was able to update my Busybox. So no problems anymore.
It took me 4 hours to get unrevoked root my phone (turned out that the actual version is buggy) but somehow it seems not "really" rooted.
I want to install titanium backup, so when I start it I get this popup to grant root access but titanium still says it is not ok.
I can do a "su" in the shell but not a whoami. - I don't understand why.
If I go into the recovery menu it says ClockworkMod Recovery v.3.0.0.5
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp-031d
Radio-5.10.05.23
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
EddyOS said:
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
Click to expand...
Click to collapse
It even says on first Titanium Backup launch!
Yep...pops up a message. Click "Problems?" at the bottom for a reliable busybox.
Believe me I bothered a lot to look around and I tried for hours and hours.
Titanium complained about not having root privileges not about busybox. And in the help on their homepage there was this guide "how to check if your phone is rooted properly" by issuing the su command followed by whoami which is obviously misleading.
However, thank you for pointing me in the right direction. It seems to work now.
OK. Now I am convinced - this was completely not my fault. Not only is the documentation missleading, the software is buggy as well.
Going to the Problems? Menu suggests it would fix your issues with busybox by installing it and such...
Well, it does download it to your device but it is not usable until you install it manually via the android sdk in recovery mode. Until then you will not get an app listing. I wonder where to find this little detail in the docu (talking about laziness)
No one else seems to have this issue so not sure what you're doing differently
I just went to running a custom ROM so once rooted didn't have any issues
When you flash your phone with unrEVOked, try using Clockwork 2.5.0.7 as I used this version and it worked 1st time.
SOLVED
Thanks guys. I already solved all problems. It was horribly difficult to get over all these pit falls but finally I reached my goal (a Titanium Backup).
What caused me most trouble was the unclear description of Titanium Backup, especially the part in which they state "if whoami does not respond so and so you are not root"... BULL****!!!
"Short" list of how I got my Desire with HBOOT 0.98 rooted and installed Titanium Backup:
Unrevoked root, but not the latest version 3.32. This one will stop with an Error: Cannot get root. Is your firmware too new? or something similar. Instead use version 3.2
Install Titanium and start it. Superuser will popup and ask for permissions - grant.
Make the changes in the application settings that Titanium asks for (I think usb debugging and allow applications that are not from market) and forget about the message telling you you have no sufficient root privileges, that is not true - I guess what they really mean is that busybox is not installed on your system (would be nice if they'd said what they mean).
Go to the "Problems?" button and let Titanium install Busybox.
... not over yet!
Titanium will now not complain about root privileges any longer but you will still not see any application listings in the software. So maybe there is still something wrong. But what could that be? The root priviliges? WRONG!. Titanium downloaded busybox but did not bother to also install it, although it said it did ;-)
Get the android SDK from Google and install it. (you will also need the Java JDK). You can uncheck most of the packages during installation, probably all. We are only interested in the adb tool that is included in the base installation (I think it is, I also installed the Android SDK Platform tools, SDK Tools and SDK Platform Android 2.2 - just because I was not sure about it).
Boot phone into recovery and connect with the adb shell. (this is a little tool that you will find in the tools subdirectory in the android sdk. You need to start it from the command prompt)
Once connected you need to install busybox manually. Titanium did download the data but did not install! How to do this is described by Loccy here:
Code:
Actually, what I did was use Titanium's busybox:
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Instead of using the mount commands, listed above I mounted the mentioned directories with the mount option in the ClockworkMod recovery menu, that comes with the unrevoked rooting, because the mount commands did not work properly for me. Also, I had to cd into the /data/data/com.keramidas.TitaniumBackup/files/busybox directory and copy busybox to /system/bin/. from there.
Code:
cd /data/data/com.keramidas.TitaniumBackup/files
cp busybox /system/bin/.
cd /system/bin
./busybox --install -s .
But I might have had a typo.
reboot the device and enjoy.
I should mention, if you NOW issue the suggested "su" and "whoami" commands in a shell that according to Titaniums super HOWTO should tell you if you have root privileges, THEN you will get the right response.
In Conclusion:
Forget about the Titanium howto. If Unrevoked finished with no error you HAVE root privileges, no matter what Titanium tells you. Another indicator: If the superuser popup appears, you should be rooted as well.
Install Busybox either completely manually or with the above described method via Titanium. The busybox setup has worked if you can issue the "su" and "whoami" command in a shell.
@EddyOS: "Noone" might not be entirely true - If Titanium was so clear you would not find tons of "how do I install it" questions in the forum. If it works on some *or most* devices but on others not, this is just an indication for sloppy coding. And a user should not have to spend hours over hours to surf some forums for solutions that should have been provided by the developers in the first place. Some people have a life...
I'm having issues with Busybox versions. I currently have v1.19.2-Stericson installed in /system/xbin. When I try to ping with terminal emulator, it says it's using "busybox v1.16.2androidminimal".
I've removed all traces of busybox from system files using root explorer, verified with the busybox installer app that busybox is uninstalled, and reinstalled v1.19.2, but terinal server still says it's using v1.16.2. What am I doing wrong?
Thank you!
EnervinE said:
I'm having issues with Busybox versions. I currently have v1.19.2-Stericson installed in /system/xbin. When I try to ping with terminal emulator, it says it's using "busybox v1.16.2androidminimal".
I've removed all traces of busybox from system files using root explorer, verified with the busybox installer app that busybox is uninstalled, and reinstalled v1.19.2, but terinal server still says it's using v1.16.2. What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
I think it depends on the kernel you are using. I think 1.16.2 is baked directly into some of the kernels and wont allow you to update them. I ran into some this a while back (I cant remember which kernel) when i was trying to use the memory script from zeplinrox. I think the kernel code may be dependent on that certain version of Busybox. I could be wrong, but its my best guess based on my experience.
A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.
NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.
I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.
Nice work!
gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.
Added to bump it back up so people can find it.
Is there a kernel that allows overclocking yet
Sent from my A100 using XDA
I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.
Up!
Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.
Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).
Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse
goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse
Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.