Database Info

[Q] Copying su to /system... fail! help?

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

10.1 Root Problem

I am trying to root my samsung galaxy tab 2. I tried Weltwon's guide here:
http://forum.xda-developers.com/show....php?t=1657056
But it didn't work. I redownloaded each file and attempted the process 4 times. After that, I figured maybe I was doing something wrong. I don't understand how it isn't working for me yet it works for everyone else it seems.
Using odin "passes" (goes green as if it worked) And i'm able to boot into the recovery. I chose the file on the sd card and it runs through a quick install. It then says it has completed and enjoy. I reboot my tablet and try accessing 3 different root apps. (root checker, SuperSU, and GameCih- which requires root) and I get errors telling me im not rooted.
Here is what my install looks like:
-- Installing: /sdcard/cwm-root-gtab2.zip
Finding update package...
Opening update package...
Installing update...
************************
Galaxian-Soup is Proud to present
#######################
CWM root for your galaxy tab 2 7.0
#######################
Root brough to you by Brett Richter - nycbjr - itweakit.com
######################
*************************
Mounting SYSTEM...
Deleting System:bin/su...
Deleting SYSTEM:xbin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755
Creating SYSTEM:xbin/su symbolic link...
Installing busybox
Unmounting SYSTEM...
Install complete. Enjoy!

What model tab do you have?
P p.
Delivered to you via microwave technology .

Did you download and install super user from the market? It is not included with rooting procedure (although Super su is) .

!0.1
I have the 10.1 model. there were 2 other zip files i tried. They said 10.1. The one i tried last i found on a forum for 7.1 that said was fully operable on 10.1

SU
Yes. I didn't read to do that anywhere, but I tried it on my own. SuperSU says that it cannot find SU bin. SuperUser is blank when I open it. I try to update and it says canot find su binary. :S
I am so confused. Lol. It doesn't make sense! The instructions were not difficult to follow, and others are finding success.
For what it's worth, Model # = GT-P5113
Android version = 4.0.3
Kernal version = 3.0.8-396106-user [email protected] #1
Build number: IML74K.P5113UEALD7

Why are you trying to install the galaxian soup zip, I don't think this is compatible with the 10.1, your description says Tab 2 7 inch, this may be your problem. Just follow the op instructions and work with the zip file provided by welton.
Pp.
Delivered to you via microwave technology .

re
I have tried both of the ones on weltons guide. Plus a few others. All have same results. No root.

download the app superuser from play store, then run supersu, it will request root access, give it to it, then it will update. Might need to download busybox from playstore before hand if u dont see it in your app list

Check out this thread for recovery /root on the 10.1" tab: http://forum.xda-developers.com/showthread.php?t=1686514
Do not flash the stock ROM though, it's for the 3g model.
Cheers,
C.

Ok let's see. Superuser never asks for permission. I open it and the log is empty. The whole app stays empty. I check the installed version and it says legacy. It asks if i want to update and i say yes, then it fails. Super.su opens up saying it cannot find any .su binaries and that it's a problem. Busybox installer is the only app I've ran that gave me any belief that the root worked. It tells me I'm rooted and my current Busybox version is 1.19.3 when i try to install any new versions it fails. I also downs0loaded an app called busybox. When i click install there, it says it may be unable to find the binaries and it closes.
Sent from my GT-P5113 using XDA

Oh, here's something I'd like to add. I read a different guide an in its description the rooting process took a couple minutes after selecting the zip. Mine only lasts about 3 seconds. Could my probem have been the odin process?
Sent from my GT-P5113 using XDA

re
I'm probably stacking too many responses, but here's word for word issues:
I JUST WHIPED ALL DATA on my tablet, deleted all the files on my PC, and started over. I redownloaded, reflashed (ODIN), used only the versions in the guide by weltwon - and ran the root again.
Superuser, Busybox, SuperSU - NONE of these were installed on their own. NOTHIGN was installed by the root process.
Superuser:
Opens to a grey background and a white column. On the left (in grey) "No apps in list". On the right (in white) No log information Showing 0 entries. The start icon takes me to the app store. The button that looks like a piece of paper with a list and an (X) does nothing.The wrench icon takes me to the settins.
---In settings AutoResponse is set to Prompt. no settings have been touched, all are default. Under general there is a lane saying "Superuser v3.0.7 (41)" I press it but nothing happens. next i press "Su binary vnull (tap to check for updates)".
------In su binary vnull:
{
Downloading Manifest... Okay![GREEN]
Parsing manifest... Okay![GREEN]
Latest version = 3.0.3.2[GREEN]
Checking installed version = legacy[RED].
}
At the top, "New version of su binary found. Update now?" So i click update.
{
Fixing databse... Okay![GREEN]
Checking for busybox... Okay![GREEN]
Checking current install path... fail![RED]
Failed to find currently installed su binary. Update cannot continue.
}
So I try to run busybox free.
Under the install busybox tab the first thing i notice is; "Location of Busybox could not be determined.
I try to install BusyBox 1.20.1 to /system/bin and I get a pop up that says the following; "I am unable to verify whether or not certain utilities needed for this application to run are present and functional on your device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured."
My only option is to press the X on this message box, which closes the application.
I reopen and try other versions, same message. I reopen and try the other two installation choices (/system/xbin and Custom Path) I instantly cancel the Custom Path because it says it's an advanced option and I do not want to mess up anything.
I install SuperSU and open it. I'm brought immediately to a pop up saying, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" MY only choice is to press OK which closes the app.
Next i try "Jrummy16" 's BusyBox Installer. I install it and open it. Under the installer tab:
Select busybox version [Set to: BusyBox v1.20.1]
Select install location [Set to: /system/xbin/]
Your devise is rooted
Busybox Location: /system/xbin
Busybox version: v1.19.3
System storage 200 MB
Phone Model: GT-P5113
ROM version: IML74K.P5113UEALD7
I press install and get, "Installing BusyBox v1.20.1 failed. Please try installing a different version." I press the X and am taken back to the original screen. I try the next 5 versions, plus sqlite3, zip, zipalign, and a few versions of BusyBox and I get the same failure message. I change the location to ~/bin instead of ~/xbin and try again. SAME error.
It is VERY frustrating because I have the correct model, and am following instructions that (to my knowledge) not a single person has had trouble with. And now that I whiped the data, I'm completely out of ideas. It is completely beyond me how I end up stuck in this situation where nothing seems to be doing what it should.

Need help with Root on TF700 Tw edition.

I tried Debugfs method
http://forum.xda-developers.com/showthread.php?t=1706588
It state it is rooted, but if I check with Rootchecker, it state it isn't, and I can't use Titanium Backup or Market Unlocker.
I have the driver installed, I can see my TF700 on my PC.
I have set USB debugging, and unknown source, and also turned off Asus sync.
I have also used the SU Update fixer, which states.
Checking signature - OK
Extracting tiny busybox - OK
Extracting Super.apk - OK
Gaining Root Access - Fail
And gives the message, Fix failed. try download and flashing an update.zip from androidsu.com
My TF700 is on build IM74K TW_epad-9.4.5.30-20120907
Kernel version 2.6.39.4

bluewr said:
I tried Debugfs method
http://forum.xda-developers.com/showthread.php?t=1706588
It state it is rooted, but if I check with Rootchecker, it state it isn't, and I can't use Titanium Backup or Market Unlocker.
I have the driver installed, I can see my TF700 on my PC.
I have set USB debugging, and unknown source, and also turned off Asus sync.
I have also used the SU Update fixer, which states.
Checking signature - OK
Extracting tiny busybox - OK
Extracting Super.apk - OK
Gaining Root Access - Fail
And gives the message, Fix failed. try download and flashing an update.zip from androidsu.com
My TF700 is on build IM74K TW_epad-9.4.5.30-20120907
Kernel version 2.6.39.4
Click to expand...
Click to collapse
After you finished and your device bootup, make sure you launch the superuser app (open up), then do update, once done, check root again.

buhohitr said:
After you finished and your device bootup, make sure you launch the superuser app (open up), then do update, once done, check root again.
Click to expand...
Click to collapse
Tried that, still no root.
Same as the SU update
Downloading manifest - OK
Parsing Manifest.. okay
Latest version 3.1.1
Unpacking sutools okay
Checking current installl path /system/xbin/su
downloading new binary
gaining root access.. fail.

Urgent: I cannot unroot!

The SU Binary file is corrupted on my device, from trying to replace it with another. Shortly after replacing the SU file, I was unable to open SuperUser.apk. I reset my phone, hoping this would unroot my device. I was WRONG. My device is now currently rooted, with a corrupted SU file, so i can't even unroot via SuperSU Application. I've also tried terminal commands to remove the SU file, but it needs root access, which i cannot access due to the SU file! HOW CAN I UNROOT MY PHONE , THUS GETTING RID OF /SYSTEM/BIN/SU , SO I CAN SUCCESSFULLY RE-ROOT MY PHONE?
PLEASE LEAVE A SUGGESTION, OR LINK ME TO SOME UNROOTING SOFTWARE, I'M IN DESPERATE NEED OF HELP
Device: Kyocera Rise
Model: C5155
OS: 4.0.4 (ICS)
Kernel: 3.0.8-perf
Build: IML77

[Q] Loaded Clockworkmod Superuser Update - Lost Root - Note N7000

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 ...