Does anyone have any problems with the busybox installed by wugfresh's utility? I switched out the SuperSU app with Koush's SuperUser app and I noticed that busybox is 0 bytes and none of the commands work. I would like to know if it is an issue with that busybox installer or because I am using a different su. I got it working by using the JRummy busybox installer, but I rather use the Stephen installer.
Additional info: stock rooted 4.4
brianf21 said:
Does anyone have any problems with the busybox installed by wugfresh's utility? I switched out the SuperSU app with Koush's SuperUser app and I noticed that busybox is 0 bytes and none of the commands work. I would like to know if it is an issue with that busybox installer or because I am using a different su. I got it working by using the JRummy busybox installer, but I rather use the Stephen installer.
Additional info: stock rooted 4.4
Click to expand...
Click to collapse
If it doesn't work using the Stephen installer, and you got it working using the JRummy installer, why do you want to use the one that wouldn't work?
JRummy installer uses an older version of busybox, which might be why it's working for you. I believe versions past 1.20 aren't compatible with Android 4.3+
Sent from my Nexus 6 using Tapatalk 4
I was wondering if others were having the same issue with the Stephen installer. If so, we could pass this information to Wugfresh. He might be able to give us an option as to which busybox installer his utility will install on the device. Also, it is just strange that everything installs properly, but the busybox binary is 0 bytes.
Can confirm the issue on a N4 also
Stock 4.4.2 ROM on Nexus 4. With koush's latest superuser, problem is exactly as you describe when busybox is installed via Stephen's utility. Using latest supersu by chainfire, everything is fine. Haven't tried any other installation methods. Someone know what's wrong?
Related
My note was/is rooted. SuperSU used to work and now it doesnt (along with busybox) it says there is no su binary installed, superSU cannot install it. There is a problem!
I have tried uninstalling busybox and supersu, rebooting, reinstalling, rebooting (about 5 times) with no success. I have no recovery installed and am running the stock os. The device status says custom. Ran root check pro (see attached). Any advice or insight into whats going on?
Looks like you lost root. Just root it again using CF Autoroot.
Sent from my GT-N5120 using Tapatalk 4
I root my phone using vroot and got a chinese kinguser, the problem is that I used a method to replace the kinguser and push
a new su-binary and busybox i think and after reboot the kinguser is gone and no supersu was replaced, I have tried installing a new
Supersu kinguser supersu but nothing works just got a message that D su-binary must be updated. Also tried flashing zips for rooting in stock
Recovery and tried many methods for unrooting but nothing works. I just want a suggestion how to delete the su in /system/xbin. TIA
Benamin0318 said:
I root my phone using vroot and got a chinese kinguser, the problem is that I used a method to replace the kinguser and push
a new su-binary and busybox i think and after reboot the kinguser is gone and no supersu was replaced, I have tried installing a new
Supersu kinguser supersu but nothing works just got a message that D su-binary must be updated. Also tried flashing zips for rooting in stock
Recovery and tried many methods for unrooting but nothing works. I just want a suggestion how to delete the su in /system/xbin. TIA
Click to expand...
Click to collapse
you dont need to push superSU just install and update the SU binary and uninstall the king user
Ive tried that constantly and it fails to update the su binaries. Almost like I'm stuck with KingUser. Not that I mind since it seems to work, but it would be nice to be able to switch to superSU if I wanted.
2
Same Problem
Still searching ?
If yes:
http://forum.xda-developers.com/showthread.php?p=61203253
Sent from my GT-I8160P using XDA Free mobile app
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods
I just got the phone today and the store updated it to 8.1. I have it unlocked and rooted but it crashes when i hit install for busybox. It says free space unavailable for /system/xbin
Delete unused keyboards. Not the Latin one tho...
equlizer said:
I just got the phone today and the store updated it to 8.1. I have it unlocked and rooted but it crashes when i hit install for busybox. It says free space unavailable for /system/xbin
Click to expand...
Click to collapse
If you're using Magisk, just use the Osm0sis BB module. If not try Meefik which supports custom install locations.
Hello everyone,
So I have a question regarding Busybox and Viper4. I'm rooted via magisk and I*'ve attempted to get viper4 via magisk app but have been unsuccessful due to drivers. I've installed busybox via magisk, but I never get the app in the app drawer. So I tried the playstore version but when I downloaded viper4 on magisk then try to download the driver, I get a message telling me to root or install busybox. I I have installed BB in sbin, and xbin, bin but no luck. I keep receiving the same message. Any ideas? I have elementalX kernel.
mzeigler1 said:
Hello everyone,
So I have a question regarding Busybox and Viper4. I'm rooted via magisk and I*'ve attempted to get viper4 via magisk app but have been unsuccessful due to drivers. I've installed busybox via magisk, but I never get the app in the app drawer. So I tried the playstore version but when I downloaded viper4 on magisk then try to download the driver, I get a message telling me to root or install busybox. I I have installed BB in sbin, and xbin, bin but no luck. I keep receiving the same message. Any ideas? I have elementalX kernel.
Click to expand...
Click to collapse
Wrong section mate
Sent from my Pixel 3 using Tapatalk
mzeigler1 said:
Hello everyone,
So I have a question regarding Busybox and Viper4. I'm rooted via magisk and I*'ve attempted to get viper4 via magisk app but have been unsuccessful due to drivers. I've installed busybox via magisk, but I never get the app in the app drawer. So I tried the playstore version but when I downloaded viper4 on magisk then try to download the driver, I get a message telling me to root or install busybox. I I have installed BB in sbin, and xbin, bin but no luck. I keep receiving the same message. Any ideas? I have elementalX kernel.
Click to expand...
Click to collapse
The module doesn't create an application. I install BusyBox for Android NDK and Viper FX with Dolby and Audio Mod Library and I have absolutely no issues
I was missing the audio mod. Thank you for the assistance.