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

I think I messed up my root...

I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?

ayang02 said:
I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?
Click to expand...
Click to collapse
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.

yakalid said:
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.
Click to expand...
Click to collapse
I've figured out the solution to my problem: just re-push su & Superuser.apk to /system/su and /system/apps/Superuser.apk respectively.
Basically I referenced this thread: http://forum.xda-developers.com/showthread.php?t=1531865
Since I already have su and Superuser.apk in my /system (although I think I tainted both files), all I needed to do was grab clean versions of su and Superuser.apk and adb push em through and type "adb shell su" to make the # appear. I was even able to update su binary within Superuser, awesome :good:
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
Click to expand...
Click to collapse
Hope this helps with people who are having troubles with Superuser/su not gaining root access.

If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.

Matridom said:
If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.
Click to expand...
Click to collapse
I guess it makes sense, the only real issue was my su permissions.
I did this with a locked bootloader btw.

Problems with GBTweaked and R800x

Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.

Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app

otonieru said:
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Well, I don't even get the blue light on boot to indicate it is waiting for me to push the button...
Additionally, I keep finding a lot of chmod/rm/ls permission denies whenever I tried to reinstall superuser, or use the PC installer for CWM and Titanium keeps FC whenever I try to start it.

I just ran rootchecker and got this:
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
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
Results provided on your R800x device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Any thoughts?

edwinen said:
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Click to expand...
Click to collapse
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.

chery2k said:
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
Click to expand...
Click to collapse
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.

edwinen said:
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
Click to expand...
Click to collapse
Do not use an auto-installing app for CWM.
If you are on windows, use RecoveryX.
Sent from my Kindle Fire

Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.

lightningdude said:
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
Click to expand...
Click to collapse
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)

edwinen said:
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
Click to expand...
Click to collapse
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.

lightningdude said:
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
Click to expand...
Click to collapse
Yeah... well, whenever I try to do anything with adb shell, i get permission denied, I can't even ls!!!

how about re-flashing kernel? doom kernel should bring along CWM as well...

otonieru said:
how about re-flashing kernel? doom kernel should bring along CWM as well...
Click to expand...
Click to collapse
Hmm.. well looks like my only option is to wait for my bootloader unlock... but I have not heard back from them in about 5 days.

They r quite slow in replying email, contact them via gTalk directly.. or just pay 1st (like what i did), when they receive the money they will feel more responsible to finish the service, LoL
Sent from my R800x using xda app-developers app
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
For now i will suggest to falshback to original stock via flashtool..
Sent from my R800x using xda app-developers app

Well.. ended up unlocking the phone, and been messing with various options. Nothing seems to be working quite well, although it is because I am trying to use CM10 and CM9 which dont seem TOO stable.. but eh... Thanks for all the help everyone!

Proper root or not

When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps

brion1020 said:
When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps
Click to expand...
Click to collapse
I'm having the same issues with 4.0.4. It's getting me pissed and contemplating doing 4.0.3 where I had access to system files via root explorer. I've been going through different ROMs on 4.0.4 to see if that would alleviate the problem. So far, still issues saying something to the affect that I don't have superuser access even though I can run any rooted application.

Here is the results of using root checker pro
Code:
Congratulations! You have root access!
Super User Applications Status: Superuser application - version 3.0.5 - is installed! SuperSU application - is NOT installed.
System File Properties for Root Access: Standard Location Check Command: ls -l /system/xbin/su: Result: lrwxrwxrwx root root 2012-09-29 00:35 su -> /system/bin/su Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location Check Command: ls -l /system/bin/su: Result: -rwsr-sr-x root root 22228 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!
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: Root user id: uid=0(root)
Root group id: gid=0(root)
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
Results provided on your SGH-T989 device by

Su or superuser
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.

[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
I've tried updating superuser from the market, even bought the elite version. Tried SuperSu and thus far, no luck. Tried using titanium just now and it didn't work on superuser.
---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------
I've even reflashed the su signed efghi 3.0.7 apk.

[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?

brion1020 said:
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?
Click to expand...
Click to collapse
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.

Hype As Fruck said:
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.
Click to expand...
Click to collapse
Just Odin back to stock and then reroot. Its super simple. Maybe if you can get back to you recovery somehow you can just flash another rom and install it where you can have your supersu access back.
Sent from my SGH-T989 using xda app-developers 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!