I have rooted my Hero and have root acces on 2.73.405.5. (no custom rom)
How do i get busybox installed on it without installing custom rom?
Would this work or is there a newer build ?
http://benno.id.au/blog/2007/11/14/android-busybox
Ok, I installed busybox according tutorial mentioned before but everytime after a restart i need to re-enter "export PATH=/data/busybox:$PATH" to have busybox cmd set again.
Isn't there a method to have it permanent?
find out where the path is set for android system and alter it?
kendong2 said:
find out where the path is set for android system and alter it?
Click to expand...
Click to collapse
Isn't there some tutorial?
I doubt i'm the only one with this problem
probably not the only one, but one of a few. most people who want to have root access and gadgets like busybox & co install modacos custom rom, where it works. maybe google can help (lol in two ways: either as a search engine or as maintainer of the official android documentation...)
Hi! Sorry if this question was already asked, but I couldn't find something related..
I have SGS2 XXKG3, so I've downloaded Chainfires's rooted kernel XXKG3 and successfully flashed it. Then I tried to install SUFBS (root file manager and terminal) and it told me that I don't have busybox when I tried to mount /system as r/w. Also it offered to install free busybox from Market. I agreed.
Everything seemed to be OK until I found that droidwall cannot show me the log - it tells "dmesg: applet not found". Little research discovered that I have symlink /sbin/dmesg which refers to busybox. But my version of busybox doesn't support dmesg. Also I'd found normal dmesg (ELF-executable) under (probably, I don't remember) /system/bin. So I deleted the symlink (/sbin/dmesg) and everything worked OK again. But.. till reboot. After reboot the /sbin/dmesg was there again.
Little more research and I found that now I have two versions of busybox on my SGS2: one from Chainfire's kernel (dated 2009) and one that I've installed myself (dated 2011, sep). The latter (2011) has about 1.5 times more functions that Chainfire's. But 2009 has dmesg function whereas 2011 hasn't.
So here is the question: why /sbin/dmesg is automatically restored after boot? And what can I do to prevent it from restoring?
Also, do I need to do something to remove one copy of busybox or two of them will live OK with each other?
Guys, please help... I can't now write to developers' forums since I don't have enough posts, so my only hope is to write here
My DX2 has been rooted using the Motorola One Click Root. Superuser is installed. Is busybox also installed during the root process?
I was reading something or other the other day about some customization that I was thinking of doing, but it stated that I should have busybox installed. So I didn't move forward with whatever it was doing because I wasn't sure busybox was installed on my phone during the root process.
Related...
What does busybox do or what is it used for?
Busybox is basically a pared down version of a bunch of common *nix utilities in one download. It's used so that you can easily install the command line functionality you need for scripts and applications without needing to manage and maintain a bunch of different utilities that have extraneous capabilities.
It seems that after rooting ICS via the Bin4ry Many-root-methode (on Xperia U) busybox is not properly installed.
On first sight this seems to be fixed after updating busybox manually but it doesn't function completely.
All ASH scripting functionality isn't found.
In the correct situation when typing " ASH " in the shell it should return which busybox ASH version is installed.
But with this rooting methode it returns "not found".
I tested a few other busybox functions (awk/grep etc) and those do seem to work.
Does anyone have any idea how to fix this issue ?
try to install "bysobx installer" and update to the latest version of the binaries
waiflih said:
try to install "bysobx installer" and update to the latest version of the binaries
Click to expand...
Click to collapse
I'm guessing you made a typo and meant the busybox installer?
I used the BusyBox installer to update to the latest version of the binaries.
It makes no difference
Hi,
I need to root a Zebra TC56 to install some other apps that require rooted Android. There is very little information in the way of rooting the Zebra TC56. I 'm pretty set on using Chainfire's superSU, but I cannot find any information on whether it will work on this hardware. Does anyone know if the superSU works on this device with Android 6? If not, is there another Root Tool that will work.
Any advice appreciated.
THANK YOU!
VK
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
jwoegerbauer said:
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
Click to expand...
Click to collapse
BusyBox installed fine.
SuperSU will not install all the way. When I select to root, it says root not detected and then, "How to Root", which launches my browser to a site that no longer exists.
Now what?
Thank You!
edit: Still stuck at this point. I read about TWRP, KingoRoot and some other random apps. I cannot brick this touch computer; it is $1600; that would be a very expensive brick. :crying:
So, I have no idea if I am right, but maybe I need to open the terminal emulator and "su" install the SuperSU apk. But I have no idea and I don't want to experiment. Hopefully, someone can help me.
@vidarr_kerr
Don't confuse things:
SU is the super user who unrestrictedly can perform any operation on Android OS. As soon as SU got installed Android is rooted! Again: BusyBox you successfully installed contains the su applet.
SuperSU is merely a root-manager app: it maintains a database where is stored what app can act as super user. SuperSU app doesn't grant super user rights.
BTW:
TWRP has nothing to do with rooting device's Android, as this is also true with Magisk.
The device is still not rooted after the "BusyBox Installer (No Root)", from your link, was installed.
I installed BusyBox, I followed the directions to then copy a command, then open a terminal, paste the command in and hit enter, then nothing happened. SuperSU was not installed with it.
So, as you told me, I then installed the latest SuperSU APK from your link. It says it installed, but when I run it, it says root not detected and then has a link named, "How to Root", which launches my browser to a site that no longer exists.
I followed what you said. Where did I go wrong?
Thank You!
You didn't get it. Sorry to say this.
jwoegerbauer said:
You didn't get it. Sorry to say this.
Click to expand...
Click to collapse
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
(That should have tipped me off right away you had no clue, but I thought maybe you knew something.
So, you gave me the links for both of those files and it doesn't work.
I don't think you have any idea what you are doing; and shouldn't be explaining things you do not understand.
The "no root" BusyBox, does not include SuperSU.
If it did, why did you give me the link for the separate SuperSU file?
All the "no root" BB did was install a terminal emulator (with no su abilities).
The SuperSU didn't install, because the Android is NOT rooted.
If the Android WAS rooted, SuperSU would run and allow me to grant su privilges to the apps that require it to work.
You basically just wasted my time.
I would have just said "thank you" and moved on, but you are rude.
You don't know what you are talking about either.
Hopefully, this will help others, to not do what you say to do.
vidarr_kerr said:
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
Click to expand...
Click to collapse
You're right: BusyBox (No Root) doesn't come with SU-binary. Wasn't aware of this. I misinterpreted APK's title. Pitty.
ERRARE HUMANUM EST ( To err is human ).
Installing BusyBox containing SU-binary requires your device's bootloader got unlocked before, because Android's /system partition gets modified. Hence manage to unlock device's bootloader as 1st thing of all things. Good luck.
DL BusyBox latest: https://github.com/meefik/busybox/releases/download/1.31.1/busybox-1.31.1-46.apk
My last 2 cents here: SuperSU and SU binary are totally different things.