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
I am running FR007 on my aria. I am getting a su binary outdated message when launching titanium backup. The message says my su binary installed version is 2.3-ef and that the latest version is 3.0.3. When I try to update the su binary it fails and my aria reboots. My currently installed superuser version is 3.0.7.
I would appreciate instructions on how to fix this issue.
That is outdated. Just flash the attached file via CWM Recovery.
I appreciate your help Theonew. That seems to have fixed the problem.
Ok, so this is the problem:
I have a TF101, rooted since 3.2. I have been able to do OTA updates without problems so far, keeping my root with OTA Rootkeeper.
Last week, I tried figuring out how to automatically mount cifs-shares through Tasker. Whatever I tried, the share would not mount through Tasker. It mounted without problems through command line in Terminal Emulator.
Eventually, i narrowed it down to a root acces problem in Tasker, or the Locale Execute plugin, or the secure settings plugin. I noticed that neither of those had ever asked for SU-acces and there were no logs of it in the Superuser app. When downloading other root-needing apps (e.g. rootchecker), I had the same problem: whenever a new app would normally ask for root acces, instead of the usual Superuser-prompt, the app stalled for a few seconds and then gave an error message or just plain nothing. There was no log of this in the superuser app.
When setting the superuser app to 'always grant root', the situation stayed the same: new apps didn't get root, older apps still had root without problems.
While searching for similar occurences on the internet, I saw a suggestion somewhere to clear the cache and data for the superuser app, so I did.
Now superuser still doesn't prompt and NONE of my apps have root. Apparently even the superuser app itself has no root acces anymore, since it fails to get root acces when updating the su-binary.
My guess was that completely removing su and the superuser app and subsequently re-rooting the whole thing would fix this.
I tried unrooting/rerooting through various methods (Brk, Vipermod, this one, and the new Wolf's thingy), but to no avail.
Brk tells me eveything worked fine, but changes nothing, except it gave me an even older version of the su-binary.
Vipermod hangs on "daemon started succesfully" but apparently does nothing even after 10 minutes.
The Asus Backup Utility method changed absolutely nothing
The Wolf's method looked promising, but installing the "Superuser-3.0.7-efghi-signed.zip" failed. (maybe because I did this from CWM recovery instead of his recoveryblob recovery? Dunno.)
So far I can't seem to remove root, as OTA Rootkeeper assures me the superuser app is installed and the device is rooted, even if the root acces is not granted to it (or any other app).
Any ideas?
Update: tried installing SuperSU from CWM recovery to replace Superuser app, but it gave the same 'installation aborted' message. Is this because CWM has no root acces also?
update2: I have root acces through adb shell apparently. I looked here and here for a way to replace the superuser app. I managed to remount /system, delete Superuser.apk and push the Superuser.apk and su from "Superuser-3.0.7-efghi-signed.zip" onto the device.
No apparent change, not even in the su binary version number reported by Superuser app.
I downloaded the standalone su-binary from here too, and replaced /system/bin/su with that one, too, but after reboot the Superuser app still indicated su binary version 2.3.2-efgh.
I don't know exactly when this problem started, but it could have been caused by the recent update from 9.2.1.17 to 9.2.1.21? Is it possible to revert to the previous version? If so, how? Would I lose data/apps?
Type the following in terminal:
ls -l /system/*/su
My guess is that you have two binaries and one or both of them is not superuser with permission rwsr.xr.x
Ensuring CWM working properly, you just try do backup using CWM then, if it worked then it's has nothing to do with being root access problem. And flashing wolf's root zip via CWM is all it takes to regain root after the 9.2.1.21 update.
Mine was similar root access messed after flashing the 9.2.1.21 update. Tried rectified this by copying su from system/bin to system/xbin but still nothing, but my CWM work though and use it to flash wolf's root zip to correct the su missing in the system. Now it work great..
Sent from my awesome rooted Defy: 2.3.6
@gee one
ls -l /system/*/su gives me this:
-rw-rw-rw- root root 22364 2008-02-29 02:33 su
-rwsr-sr-x root shell 26324 2008-02-29 03:33 su
So you're on to sth. Top one is located in /system/bin, lower one is in /system/xbin.
Now what do I do with this? Copy one over the other? chmod? chown?
@farsight73
As said in the OP, I tried flashing wolf's root zip in CWM, but got an error and it aborted. I did the following:
put zip on removable sd
reboot to CWM
choose update from zip
select the right zip
confirm
I also tried this with /system mounted, but same result.
I don't have acces to pc now, I will try more tonight.a
[SOLVED]
Thanks for the replies, you got me in the right direction in that I was replacing the wrong su in the wrong way.
Since Brk Toolkit managed to get me an older su, I thought it could as well give me the right one second time.
I replaced the su and superuser.apk in the /adb folder of the Brk rootkit with the one from wolf's root zip, and then used Brk Toolkit to install su and superuser.
Upon reboot, the problem was solved.
Thanks a bunch!
For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer
gee one said:
For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer
Click to expand...
Click to collapse
HEY MY FRIED I HAVE EXACTLY THE SAME PROBLEM
chmod 06775 /system/bin/su results"unable to chmod /system/bin/su: readonly filesystem "
echo $PATH RESULTS /system/bin/su: /system/Xbin/su
COULD U HELP ME WITH ZIS MY FRIEND
10Q
From adb or the terminal, type in "/system/xbin/su" to elevate to the superuser. Then mount system to read-write and delete the /system/bin/su version. Remount system as read only.
This will work if you have two versions of su and one of them is not really super.
sent while running with scissors
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?
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