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
Related
Hi, I have an 101 G9 with rooted 3.2.78 firmware (thank you letama). Now I would like to install busybox. In the past, on other phones, updating pre installed version of busybox (of a custom rom) through market, the phone hangs on reboot and I was forced to restore a nandbackup. The authors of these custom roms told me that the latest versions of busybox had incompatibilities with certain phones. Do you can tell me if busybox version in the marke block our tablet? thank you and sorry for my poor english.
Hi hitman72,
Yes, you have to be careful with busybox installers. They have a tendency to try to update Archos busybox in /bin and it will break things around.
Check here for instructions for a manual install with adb, it's quite easy and safer. This busybox comes from a cm7 build and is quite complete.
Cheers,
LeTama
I know, a lot of you are shaking your head after seeing the title lol. But I am trying to use DSploit on my home network, I saw that I need busybox fully installed on my device. So I downloaded it, installed it by opening the app and hitting install. Nothing seems to be working still. I keep seeing something about using commands or something. I am more or an iOS guy so I'm not an expert on android. Can anyone help me get DSploit/Busybox working?
Thanks!
tpayne174 said:
I know, a lot of you are shaking your head after seeing the title lol. But I am trying to use DSploit on my home network, I saw that I need busybox fully installed on my device. So I downloaded it, installed it by opening the app and hitting install. Nothing seems to be working still. I keep seeing something about using commands or something. I am more or an iOS guy so I'm not an expert on android. Can anyone help me get DSploit/Busybox working?
Thanks!
Click to expand...
Click to collapse
remove busybox then reinstall it, download a busybox checker app to verify this is working on your phone, if it is its the DSploit app thats encountering problems, if its not working on your phone download a different installer and install a ew different versions of busy box on your device
ricky310711 said:
remove busybox then reinstall it, download a busybox checker app to verify this is working on your phone, if it is its the DSploit app thats encountering problems, if its not working on your phone download a different installer and install a ew different versions of busy box on your device
Click to expand...
Click to collapse
Okay, I did that and all seems good. Ran a root checker that checks for SuperUser, busybox and SU and here are the results:
Status Rooted
Id Uid=0(root) gid=0(root
SuperUser Not found (which is weird because I so have SuperUser installed)
Busybox /system/Xbin/busybox
SU /system/Xbin/SU
What now? DSploit still seems to not be working
tpayne174 said:
Okay, I did that and all seems good. Ran a root checker that checks for SuperUser, busybox and SU and here are the results:
Status Rooted
Id Uid=0(root) gid=0(root
SuperUser Not found (which is weird because I so have SuperUser installed)
Busybox /system/Xbin/busybox
SU /system/Xbin/SU
What now? DSploit still seems to not be working
Click to expand...
Click to collapse
your phone isnt properly rooted, update su binaries or install supersu! if that doesnt fix the problem i am sorry i cannot assist you any further
Hello everyone! I've recently rooted my Galaxy S6 Edge rom version: G925FXXU1AOCV using the PingPong Root.
Now im trying to install Viper4Android. But it needs BusyBox to be installed in order to work.
So I tried downloading and installing Busybox. But installation fails and shows the following error:
Install BusyBox v1.20.2 failed.
We have detected your system cannot function with this version of busybox.
Please try installing a different Rom or fixing your system.
Error: Cannot Link Executable: cannot locate symbol "_res_get_state" reference by "busybox"...
I have no idea what I need to do in order to install BusyBox. I tried playing around with ADB shell but for the life of me can't figure it out.
Any help will be greatly appreciated!
Same here I've tried everything and I can't get some apps to grant full root without busybox....
Just an update, I was able to install BusyBox by downloading another version. Even looks different. Allowed me to install no problem and no I enjoy the benefits of Viper4Anroid! yahooooo!
I use TricksterMod for speed tweaking, and it's built-in Busybox on Rails would not install at all, just said not supported. I used another installer to get v1.20, which installed fine and works with TricksterMod
Hello community,
I'm new in the forum, It's 2 days I'm fighting with this problem: I want to root my BlackPhone 2 using TWRP and SuperSU (I think that this is the only method that works with BP2, since KingoRoot and others are patched for security)
I flashed the recovery TWRP, then I tried the following SuperSU versions:
SR3-SuperSU-v2.79-2017...zip
BETA-SuperSU-v2.74-2.zip
SuperSU-v2.79-2016...zip
UPDATE-SuperSU-v2.79-2016...zip
None of them works, in TWRP all goes OK, no errors and no warnings, but then when I open SuperSU apk it says "There is no SU binary installed... ...If you just upgraded to Android 5.0".
This is really crazy because I'm running on Android 6.0.1 (Silent OS 3.0.7) and using Total Commander I can see /su directory.
Using a root checker app it says that my device is not rooted, but the SU binary is present and also the busybox one.
The Silent Circle's Security Center in their "Privacy Meter" app warns me "Security alert, active root access detected! ...."
For install TWRP I had to switch these things on in Developer Options: "OEM unlocking", "USB debugging", then I enabled installs from unknown sources by ADB and SD card.
Any help will be great, Thanks guys
EDIT: sorry for the Thread title, I can't modify it, it should be SuperSU not sudo su (too much linux)
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
RAZERZDAHACKER said:
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
Click to expand...
Click to collapse
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Unfortunately they are in the same situation. But I admit that I did not install the TWRP permanently due to a possible bootloop phone. Has anyone found a solution to the root?
i have same problem i want unlock bootloader .............need help plz!!!
Koskha said:
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Click to expand...
Click to collapse
After you flashed the su zip, did you get the superuser app?
Blackphone 2 bootloader
RAZERZDAHACKER said:
After you flashed the su zip, did you get the superuser app
phone not flash with any file.....devices lock ....need to bootloader unlock.
Click to expand...
Click to collapse
A litle guide to increase bp2 performance
https://forum.xda-developers.com/an...e-make-bp2-t3735815/post75218344#post75218344
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.