Develop Bugs

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.

Just Rooted My S3 But SU Is Missing A Binary

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

[HELP] Root Failed on Sprint LS980

Hello Everyone,
I have a Sprint LS980. I am using this phone in India.
I followed the root procedure as per the XDA posts:
IOROOT: http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
Framaroot: http://forum.xda-developers.com/showthread.php?t=2130276
Framaroot just fails with this message at the time of selecting an :
"Failed ... Try another exploit if available"
I even tried the Kingo Root application, but none of them actually seem to work.
Root Check Pro result:
Superuser Application Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
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 shell 113036 2013-11-06 21:33 su
Analysis: Setuid attribute 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:
SU binary not found or not operating properly
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 LG-LS980 device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
I dont know if this would make any difference, but there already was a SuperSU app installed. But everytime I open it, i get this message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
Any information or help will be most appreciated.

hey there man, what version of ioroot did you use? The tutorial you linked to is not for the sprint model G2 ( I believe you got ioroot12 from there), use IORoot24 or higher. I used IO24 for my Sprint G2, rooted no problem!
Here is the IORoot25 page, you can get all the needed drivers from here too
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Best of Luck!

Cronic2009 said:
hey there man, what version of ioroot did you use? The tutorial you linked to is not for the sprint model G2 ( I believe you got ioroot12 from there), use IORoot24 or higher. I used IO24 for my Sprint G2, rooted no problem!
Here is the IORoot25 page, you can get all the needed drivers from here too
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Best of Luck!
Click to expand...
Click to collapse
Thanks man.
I will try this using the newer version.

Cronic2009 said:
hey there man, what version of ioroot did you use? The tutorial you linked to is not for the sprint model G2 ( I believe you got ioroot12 from there), use IORoot24 or higher. I used IO24 for my Sprint G2, rooted no problem!
Here is the IORoot25 page, you can get all the needed drivers from here too
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Best of Luck!
Click to expand...
Click to collapse
This worked and I am rooted. WOOHOO!! Thanks again man!

No problem man, glad I could help you out and that fixed your issue! Also didnt you mean to say ROOHOOT!! :good:

Not work on my lg ls980
Cronic2009 said:
hey there man, what version of ioroot did you use? The tutorial you linked to is not for the sprint model G2 ( I believe you got ioroot12 from there), use IORoot24 or higher. I used IO24 for my Sprint G2, rooted no problem!
Here is the IORoot25 page, you can get all the needed drivers from here too
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Best of Luck!
Click to expand...
Click to collapse
I get this message after trying the process given.
We don't have an unlock for this Sprint OTA version yet.
Your phone is running LS980ZVI .
Please try the manual root method or
post your full device info in the thread
This program will now exit.
Press any key to continue . . .

i was having the same problem with zvi. i revert back to 4.4.2 (zv8) and then root it successfully.
here is the link to revert back to 4.4.2:
http://forum.xda-developers.com/showthread.php?t=2432476

thanks man it work
cfli1688c1 said:
i was having the same problem with zvi. i revert back to 4.4.2 (zv8) and then root it successfully.
here is the link to revert back to 4.4.2:
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
thanks man it work

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