Develop Bugs

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.

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

I9195 Rooted device, but unable to get root access using adb shell su

Hi All,
I did root my device following this procedure by arco68: http://forum.xda-developers.com/showthread.php?t=2364980
Worked perfectly and naming few applications they are ok, like Terminal Emulator, BusyBox, ES File exploree, etc, and ran different root verifiers program which confirmed root status.
But when using adb shell su, I'm unable to get root access as you can see here
Code:
C:\Users\marco\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform
-tools>adb devices
List of devices attached
08985214 device
C:\Users\marco\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform
-tools>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $
1|[email protected]:/ $
1|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
It does generate a new prompt adding "1|", and as soon as you execute a comand it returns to the original prompt, but never you have root access
I've been researching across, but unable to find something similar.
All the procedures for permission denied that I have found point to rooting the device which is why I already did.
I have redone the procedure in case something was wrong, but no changes.
Hope somebody knows what is happening
Thanks in advance

Hi,
I had this problem on terminal emulator (same when typing su) on the s4 mini rooted the same way yours is.
It occurred after I installed some apps including some google updates I installed manually - I don't know which of them caused that. But after I had this problem I realised that all apps don't have the root access anymore - SuperSU, RootChecker... And SuperSU didn't gave apps like TerminalEmulator and RootExplorer anymore root access.
This problem has been solved itself after I restarted my phone (because of another reason). And I had my rooted phone again.
So after your problem occurred - did you try another app that needs root access again? Does it have still root access? If no, try restarting too (if you haven't done that already) - maybe it helps you too...

There's a SU binary on my phone but i didn't root it

Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.

bombastique said:
Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.
Click to expand...
Click to collapse
Since i believe, on all stock android firmware, since android 6 ( Marshmallow ) it comes with Toybox installed.
Toybox is similar Busybox. Except for the latest version ( i believe ) of toybox these versions don't have ' root ' like functionality, which is why ' su ' command will fail. This is why you will see the commands in directories like /bin etc.
As for apps, the detection methods have changed to more then looking for ' just if your phone is rooted ( SU Binaries )' or not. ie: unlocked bootloader etc, and maybe playstore certification/safetynet. Blame Google for that.
Toybox - Wikipedia
en.wikipedia.org