I am using stock rom, i installed busybox properly but in terminal emulator it showing 'applet not found' whts the problem.
Are you rooted? If so, download SuperSU and update the su binary. Reinstall busybox after that (just to be sure). Then see if you get the same error.
yes it is rooted, and how to update su binary?
Related
I am fairly new with using android phones, and I am encountering that error when I am attempting to update Superuser. I'm using a Samsung Admire SCH-R720 Android 2.3.4 and I rooted it with the One Click root. I've downloaded titanium backup, Root Checker, and terminal emulator to make sure I am really rooted. I've tried uninstall/reinstalling superuser, installing the superuser update fixer(which said signatures matched), and clicking on automatic update. Current version of SU Binary is 2.3.1-ef and everything in the update is fine until it gets to "Copying su to /system... fail!". Superuser does request for rights when it asks to gain root access which I click on Allow. I am also not sure if busybox installed correctly or not, but the Root Checker program I installed said busybox was installed.
Code:
Downloading manifest... okay!
Parsing manifest... okay!
Latest Version = 3.0
Checking installed version = 2.3.1-ef
Fixing Database... okay!
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... fail!
I got the same problem with my Galaxy S. Then I opened BusyBox Installer and it said that I have multiple busybox installed. I found busybox in /system/xbin and /sbin but the file size of the one in /sbin seemed abnormal, just 402 bytes. So I reinstalled busybox to /sbin. And rerun the superuser update after that. The fail has gone.
What program did you use to explore your system files?
Astro file manager
I only have busybox in system/xbin. I tried reinstalling busybox and i still get the same error when trying to update Super user. How can I uninstall Busybox? Please give a step by step if possible since I have no clue what the hell I am doing lol.
Edit 2: Er... I tried installing it also in system/bin, and it SEEMS like its working. Seems it's installed in 3 places, on my sd, bin, and xbin. It works now, so I won't touch it lol. Thanks for the help.
Hi everyone,
Same problem for me too.
after installed busybox in system/xbin using busybox installer downloaded from android market, the problem with superuser update was fixed.
I used in samsung galaxy s2..
Thank u
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
goister said:
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
Click to expand...
Click to collapse
Same problem, I am using a polaroid tablet, I installed busybox by doing the following
busybox --install /system/bin
I believe it overwrote some files and cant find the fix
Where does supersu search for the su binary. I am stuck with the cannot find su manually reroot message. This was after updating a working rooted system to the latest supersu after it asked me to. The only su on the system is in /system/xbin/su there is no su in /system/bin and /system/sbin does not exist.
Can I manually reroot by using adb to create a link from xbin/su to bin/su?
I cannot find any info on "manually rerouting" that says anything but reinstall the latest zip. Which is what I did.
Help!
Roger
Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?
Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.
I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.
new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...
Hi today I tell you how to fix super su problem
To fix we need to install the latest version of busybox
Next we need to install vroot and root the device..
Notice: we have to open busybox befor root the device
And your device now rooted!