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.

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

[Q] 'Damaged/Messed' Up Root

Hi, I accidentally installed busybox v1.20.1 from Rom Manager. Now Root Explorer/ES File Explorer can not mount RW. Neither does Play Store work, just crashes. I managed to uninstalled busybox using a busybox uninstaller but still same issue. Can someone who knows please help. Thank you!
Root Checker Log:
Congratulations! You have root access!
Super User Applications Status:
Superuser application - version 3.0.4 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: reloc_library[1318]: 6501 cannot locate 'android_reboot'... CANNOT LINK EXECUTABLE

Superuser binary files not installed (root)

Ok so Ive been trying to complete root on this Pixel 3 XL.
I rooted with Magisk.
Now, some root checker apps say my phone is rooted, and some don't.
Also, one of the root checker apps tells me the "Superuser App is installed" and "Root User Account: Success". However the same app gives me an error on stage 2 - "Superuser Binary Files: Not Installed"
Lastly, when I open up a terminal emulator on my Pixel 3 XL, it shows a "$" as the directory instead of "#". I can run the "su" command and the terminal will go to the root directory, but when I close the terminal and open another one, I'm right back at "$".
Will gettting the superuser binary files installed fix the above?
How do I get the Superuser binary files installed?

When have you ever automatically had superuser rights in a terminal? You have to run su in each session to gain that right. It sounds like you are rooted. What is not working?

Sorry, I was uneducated on the terminal issue. Just made sense to me that if I had root then I wouldn't need to type a cmd in terminal to get to it.
One thing that isn't working is stage 2 of Root Checker Basic Verify Root function. It tells me that the superuser binary files aren't installed. Not exactly sure what that means or if it even means anything, tbh.

Also when I try to run ROM Manager it tells me I still need to root my phone because Superuser was not found at system/bin/su or system/xbin/su.

But what are you trying to do, that requires root, that doesn't work? If you are getting superuser request and able to respond you should be fine. Now I could be wrong here, BUT... The way the partition table is set up now, on top of all the other different things for Android 10, may mess with certain 'root checkers' I mean it sounds like you HAVE root, but certain apps fail to recognize it. But if it's just checking it what's the problem?
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
Like I tried to install busy box and was unable to for the pretty much the same reason as your rom manager. It said their was no room in that directory for it.

OK so I installed an updated version of Root Checker and also SuperSU validator and they are both testing fine now.
I think the older version of Root Checker that I was using was programmed to search for the binary associated with the superuser app I used to use for root management a few years ago?

Same problem