Develop Bugs

SuperUserInstall Issues?( SOLVED)

Did the EVO 4G recent root instructions for 2.3.3
Downloaded Superuser from the link in the instructions and extracted to root of SD card and then installed. All programs requiring root say I have none (I do have S-OFF).
So, deleted the superuser stuff and tried to install it from the market. Says it installed fine but still I have no full root according to titianium,Rom Manager,etc.
Installed ROOT CHECK and ran advanced mode.
Says Superuser apk is installed.
The adb binary is set to default shell user access as a standard non root user
Standard su binary location:Is-I/ system/bin/su:
/system/bin/su: No such file or directory
Standard SU binary location: Is-I/system/xbin/su
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
SU binary not found or not operating properly.
Any assistance out there?
Thanks in advance....

Flash the zip from recovery and it works just fine.
DUH

Having same issue I've tried several times to no avail and the duh comment was a bit juvenile and not at all helping
Sent from my PC36100 using XDA App

Disregard the end of my post wasn't paying attention
Sent from my PC36100 using XDA App

[Q] Superuser after OTA

Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks

So you can't use boot unlocker so on play store?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Maybe you need to fix permissions.
Did you have ROM Manager by any chance with root access granted? If so you could flash CWM from there, and then apply the latest SuperSU zip from CWM.

skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.

efrant said:
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
Click to expand...
Click to collapse
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.

skyes113 said:
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
Click to expand...
Click to collapse
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.

skyes113 said:
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
Click to expand...
Click to collapse
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?

skyes113 said:
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
Click to expand...
Click to collapse
Strange. I have no idea what the problem would be then.
What I would do is boot up CWM, and re-flash an su package.
The permissions are fine: -rwsr-xr-x = 04755 and -rwsr-sr-x = 06755. Both will do the same thing.

Also I see nothing in the OTA package that would relock your bootloader. You're sure that's exactly what happened? If it did, maybe someone here could pinpoint the component of the OTA package responsible for this?
Sent from my Galaxy Nexus using Tapatalk 2

Looks to be a problem on su.
I download the latest binary and replace it using adb + busybox and now it works fine.
Thanks!

Proper Root Access Missing - Lenovo A830

Hi,
I just bought Lenovo A830 dual sim model and seems like the phone is rooted. I have tried SuperOneClick and it says the phone is rooted already but SuperUser is not able to gain root access while updating binary. Root Checker says "Sorry This device does not have proper root access.
---------------------------------------------------------------------------------------------
Super User existing Binary says below.
Su Binary V2.03:Kinguser_su
-rwsr-sr-x root root /system/bin/su
-----------------------------------------------------------------------------------------------
Tried Poot Method also but it gives below error
2012 gaintpune
[-] can't get handle on it:- 1 No Such File or Directory
A Demon Materalized while Pooting. Error Code: 18
su binary was not written
Built-In RootCheck - Poot
Path is: "/sbin:/vendor/bin:/system/bin:/system/xbin"
Found "/system/bin/su"
-rwsr-sr-x root root 18968 2013-09-01 16:54 su
Found "/system/xbin/su"
lrwxrwxrwx root root 2013-09-01 16:54 su -> /system.bin.su
"/system/bin" is the first su found
The su that is being used is not /system/xbin as expected.
-----------------------------------------------------------------------------------------
I have tried searching online but seems like I am not able to figure out whats wrong.
This Lenovo A830 is Chinese Model an have lot of unwanted apps in chinese which I would like to remove and my be install custom rom but due to missing Root access I am not able to do anything about it.
Any help in this would be appreciated.
Regards
Gaurav

I understand the phone is not so popular but if anyone can give some insight on the issue would be appreciated. I have Mac and most of the utilities to flash the CWM are for windows. I am stuck here and I just noticed that GPS is also not working, it keeps on waiting for the location.
regards
Gaurav
graswant said:
Hi,
I just bought Lenovo A830 dual sim model and seems like the phone is rooted. I have tried SuperOneClick and it says the phone is rooted already but SuperUser is not able to gain root access while updating binary. Root Checker says "Sorry This device does not have proper root access.
---------------------------------------------------------------------------------------------
Super User existing Binary says below.
Su Binary V2.03:Kinguser_su
-rwsr-sr-x root root /system/bin/su
-----------------------------------------------------------------------------------------------
Tried Poot Method also but it gives below error
2012 gaintpune
[-] can't get handle on it:- 1 No Such File or Directory
A Demon Materalized while Pooting. Error Code: 18
su binary was not written
Built-In RootCheck - Poot
Path is: "/sbin:/vendor/bin:/system/bin:/system/xbin"
Found "/system/bin/su"
-rwsr-sr-x root root 18968 2013-09-01 16:54 su
Found "/system/xbin/su"
lrwxrwxrwx root root 2013-09-01 16:54 su -> /system.bin.su
"/system/bin" is the first su found
The su that is being used is not /system/xbin as expected.
-----------------------------------------------------------------------------------------
I have tried searching online but seems like I am not able to figure out whats wrong.
This Lenovo A830 is Chinese Model an have lot of unwanted apps in chinese which I would like to remove and my be install custom rom but due to missing Root access I am not able to do anything about it.
Any help in this would be appreciated.
Regards
Gaurav
Click to expand...
Click to collapse

Hello,
maybe that helps:
http://chinamobiles.org/showthread.php?33248-Root-für-MT(k)-65xx-Handys&highlight=CWM-SuperSU-v0.99
I have done on my A830 Methode 1.1
Then I installed this Rom by CWM: A830-ROMV2_jack44 (from needrom) needrom is down at the moment

Needrom is up
http://www.needrom.com/mobile/lenovo-a830-5/comment-page-3/#comments

[Q] SU Binary error upon Execution: No root access

Info: For those of you who need more info on my SU Binary (/system/bin/su), it's NOT out of date. Its the newest version for galaxy s4 m919.
My problem: /system/bin/su (SU binary files) will not execute.
Why?...: Because, access to execute binary files on system is denied (I don't have root access/permission). EEEK.
here's the Logs from root checker Pro: (In no particular order)-
SuperSU application - is NOT installed.
SuperUser - Installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 2008-08-01 08:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2013-10-11 02:57 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
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
Root User ID and Group ID Status:
SU binary not found or not operating properly.
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

more details
Extra info that I didn't include: I originally WAS rooted, running stock Samsung ROM (factory ROM) and I rooted using ODIN. So after rooting, I installed CyanogenMod 10.1.3.1, which does not come with root installed by default.
*SIGH* So... I want to know how to root CyanogenMod... So supposedly following the instructions by Root checker pro Logs,
I need to execute /system/bin/su. (Which won't work, unless a magical "S-Off" appears so I can execute it. But, then executing would be pointless because I would be already rooted with S-Off.
Help please, anyone? Could I root cyanogenmod from the computer terminal? Is there a way to override system permissions and execute su binary?

As per all your other post. Have you enable Root in Developer Options? CM ROM now has root disable by default.

Root options...
Root options in CyanogenMod Developer Options are not displayed in my settings...
What exactly does the toggle panel say for it? I can take a screenie of my settings..?
sorry for my ignorance with CyanogenMod... The last time I flashed CyanogenMod
was with CyanogenMod version 5, lol. And that was 3 years ago (I had an HTC Inspire 4G)

System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]

In reply...
dynospectrum said:
System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]
Click to expand...
Click to collapse
Well then. That was not so loving and friendly. Lol. And I have done so, btw.. My developer options are enabled, but the root access panel is not
In there. infact, there was a new section called "SuperUser", and I had set the root access panel to "Allow ADB and Apps" like you said.
But in return, no cigar. No root rights, even still. :/

Same here I'm using beanstalk 4.3 and most of the root apps work but some don't for example gamekiller, the few times I installed it it denied it before the prompt window popped out then after a few tries it finally granted it but before I pressed grant it said WARNING GAMEKILLER HAS A COMMAND (not sure about that part) android.permission.ACCESS_SUPERUSER not declared so I went into super user settings and I checked that option so I tried searching a value number and as soon as I press search it doesn't do anything then I press help and it tells me it needs root access which has been give
Sent from my SGH-M919 using XDA Premium 4 mobile app

Download and flash in recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

Yay.
I've flashed that in CM10 ROM several times, and no root. But no worries, I'm running an awesome, fast, great battery life AOSP Based ROM (Completely AOSP, actually) and it comes rooted
The ROM is actually solely based off of googles open source code from android 4.3, with a few of the major components hand-picked from other Dev sources. The ROM is called-
Google Edition s4
For all who wish to download this as well as I did, here's the link to this epic ROM:
http://forum.xda-developers.com/showthread.php?t=2341026

Thanks
Thank you, this method worked for me. So much misinformation out there, I tried like 20 other bogus remedies before this. I could hug you.

same problem
I rooted my phone before,then I unroot it. But now when I am trying to root it again I'm facing same problem with superuser, it's saying that su binary is outdated and its not updating also, and I don't have root permission so that I can fix it with several methods which I found by google it.

ES File Explorer "test failed" trying to turn on root explorer

I have an SGH-T999. I did an OTA of 4.3 UENC2 version, then rooted the phone with Root66 and SuperSU. I installed TWRP recovery. Both ES File Explorer and File Manager by Rhythm do not see the phone is rooted. All other apps I have tried work with root. It seems to be a permission issue from debug logs. ES File Explorer is a 4.1.3 debug version (since getting this I can't get a reply from them) Here are the logs:
ES File Explorer (ES custom log from debug build)
connect failed:java.io.IOException: Connection refused
try to create su proc
successfully get the SU shell proc
chmod estool succ
start root server succ, try connect
connect failed:java.io.IOException: Permission denied
SU Check result:false
connect failed:java.io.IOException: Permission denied
try to create su proc
successfully get the SU shell proc
chmod estool succ
start root server succ, try connect
connect failed:java.io.IOException: Permission denied
SU Check result:false
connect failed:java.io.IOException: Permission denied
File Manager (Rhythm Software) (from an android "bug report" log dump)
04-14 15:04:21.618 5070 5070 E com.rhmsoft.fm: Error when executing commands: [mount -o remount,ro rootfs
/, mount -o remount,ro /dev/block/platform/msm_sdcc.1/by-name/system /system] result: mount: Permission
denied
04-14 15:04:21.618 5070 5070 E com.rhmsoft.fm: Error when mounting system folders: mount: Permission denied

Have you tried the released, non debug version? Did you factory reset after root66 and run clean (no restoring of backups)? Open supersu and itll check if the binary needs updating. Have you installed busybox?
Sent from my SGH-T999 using Tapatalk

Please Open SuperSu and see if it prompts to update the SU Bianry. Do so if it does. Second, try Root Checker app from Play Store. See what it has to say.

I tried the release version first which is what led me to email their support and get the debug version. I have the latest 1.94 version of SuperSU. I did NOT do a factory reset, just an in place upgrade and root. I did uninstall and re-install both apps and delete them out of SuperSU so it would ask for approval again.
Root checker is one of the apps that does work, along with FX Explorer. Root checker sees I am rooted and sees Super SU 1.93. This is interesting since it doesn't match the 1.94 that SuperSU thinks it is. Root checker is looking at /system/xbin. How do I see where my shortcut for SuperSU is pointing? It of course doesn't show up in my applications.
Unix Utils shows toolbox installed. It doesn't see busybox. I thought that busybox was installed with FX. But I guess that is internal? I remember one of my apps like FX or Titanium Backup or TWRP recovery saying it had to download busybox to finish the install. Is it ok to install it myself? I was afraid of a version conflict.
I just got a reply back from Rhythm who thinks the problem with them is an issue in Android 4.3.

Did you check within the SuperSU to see if it prompts to update SU binaries ?

Reflash the supersu pkg. Download in my sig.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
If thst doesnt work backup and factory reset.
Sent from my SGH-T999 using Tapatalk