When updating the su binary, the su in /system/xbin is corrupted, so I can't gain root access. Any ideas how to get it back?
EDIT: Apparently this is a known issue:
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/
DO NOT UPDATE THE SU BINARY TO 3.0.1!
Here's how to fix it temporarily:
1. Download this file: http://goo-inside.me/superuser/su-3.0-bin-efgh-signed.zip
2. Copy it to the root of your SD card.
3. Reboot to recovery.
4. Install that zip file.
EDIT #2: The latest binary 3.0.3 works fine. It should be safe again to update your version of su.
Related
Sorry to bother everyone.
In preparation for the 4.04 update, I flashed the stock 4.02 ROM and then was prompted to install the VZW OTA update. This flashed OK. I went ahead via adb and flashed cwm-recovery and then installed the su.zip file via the recovery console.
Once rebooting, I'm able to pop open an adb shell and type su and become the superuser, however none of the apps that require root no longer work -- root explorer, busybox installer, etc.
I'm guessing its a problem with my su file (possibly). Does anyone have any suggestions to troubleshoot? Thanks.
The problem I'm having specifically is gaining root access....fail (within su app).
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one
Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053
Yeh thanks its working now after reflashing the cwm superuser.
I just rooted my ATT S3 4.3. I did everything the tutorial said to do except when it got the part wherr odin reboots ur phone, i had to reboot it myself yo makr it go in cwm recovery. So once I was done rooting my phone and turned it on for the 1st time I instantly was greeted with superuser has stopped and security violations. So I tried random fixes from google and it keepa teling me there is no binary code. I can't figure out how to fix this, can anyone help me?
Which tutorial did you follow?
audit13 said:
Which tutorial did you follow?
Click to expand...
Click to collapse
I can't find it anymore. It was on this forum and it said it was for att S3 phones. Is there an area where all the ways to root are?
This is what root checker pro gave me as the results.
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 1970-08-25 22:58 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
laughingT said:
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did reboot into recovery. I remeber the files I downloaded were named clockword mod and another was called superboot with cwm. Don't k ow if that helps.
I'm having a big issue though, I had tried fixing it by flashing dif ways, now whe I try tk flash it. When it loads up in download mode, my phone turns off or of ot doesn't do that, after I flash my phone and it reboots, it shows a red screen.
EDIT:
I just tried that root method you suggested and I still have the same issues. I don't know what to do!
EDIT 2:
I fixed it by using this site http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html. Specifically, these instructions:
Download and install the latest APK for SuperSU like MrW0lf suggested.
I was having the same exact problem (unfortunately, SuperSU has stopped), so I downloaded the latest UPDATE-SuperSU file and extract it to have supersu APK, put it on my SD card in my phone and installed it from there.
It was strange because the version that was already on my phone was the same 1.89 version that I downloaded, but regardless, when I clicked on the APK, it saw it as an update, it asked to disabled knox, and worked like a charm.
- See more at: http://www.w0lfdroid.com/2013/12/Fi...y-S3-S4-Note2-Note3.html#sthash.0nlj3XHO.dpuf
PS: this is the root method I had 1st followed, http://forum.xda-developers.com/showthread.php?t=1726960
I used hide my root to hide mu root and when I hid my su binary and tride to restore it will not restore at all. Is there any way I can restore it without factory reset. I still have root as xbmc launcher works perfect.I am on latest build and used custom rom via clockworkmod.
Any body that can help me with this please
Boot into recovery and adb push the su binary back into its location
{ParanoiA} said:
Boot into recovery and adb push the su binary back into its location
Click to expand...
Click to collapse
do you know where I can get the su binary from as tried google but no joy and thanks for your help
alba1978 said:
do you know where I can get the su binary from as tried google but no joy and thanks for your help
Click to expand...
Click to collapse
I am using supersu pro by chainfire and need to install binary for it and wondered if any one can upload a zip of it please.
Here you go....
I also lost su binary using Hide my root app, can you please check if I am going to perform the correct steps to recover it:
download su apk from the post above
reboot in recovery mode: adb reboot recovery
push SuperSU_v2.01.apk to /system/app: adb push SuperSU_v2.01.apk /system/app
reboot
Thanks a lot,
6MHz
I've got some strange problems when trying to use an app which requires superuser.
I've unlocked my bootloader, flashed TWRP and (tried to) flashed SU. But now, when I try to get SU in any app it tells me, that this is not possible.
Unlocking was done with [ToolKit] OnePlus 3 ToolKit, Unlock Bootloader, Flash TWRP, Root, and More! [v2.0]
SecureSettings tells me: Root access was not detected. The System+ module...
ES Explorer tells me: Sorry, test failed. This feature cannot run on your device
There is no overlay from SuperSU, asking if SU should be granted, and the only entries inside the SuperSU app is the ADB shell and Thermux. In this two cases the window popped up and asked if I grant SU, when calling su.
Where should the SU binaries be located? I've got a folder located directly in
Code:
/
but nothing in
Code:
/system/bin
or
Code:
/system/xbin
It uses systemless root, you won't find any supersu files in /system.
If you have twrp installed I would just grab the latest supersu beta and flash it, those toolkits always seem to cause issues that can be bypassed by learning how to do the basics yourself
Already flashed it by myself. The toolkit just pushed the zip with fastboot into storage. Then I flashed it using twrp. Also download latest version, copied it onto phone and flashed that zip. Same result...