Related
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
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!
I used hide my root to hide mu root and when I hid my su binary and tride to restore it will not restore at all. Is there any way I can restore it without factory reset. I still have root as xbmc launcher works perfect.I am on latest build and used custom rom via clockworkmod.
Any body that can help me with this please
Boot into recovery and adb push the su binary back into its location
{ParanoiA} said:
Boot into recovery and adb push the su binary back into its location
Click to expand...
Click to collapse
do you know where I can get the su binary from as tried google but no joy and thanks for your help
alba1978 said:
do you know where I can get the su binary from as tried google but no joy and thanks for your help
Click to expand...
Click to collapse
I am using supersu pro by chainfire and need to install binary for it and wondered if any one can upload a zip of it please.
Here you go....
I also lost su binary using Hide my root app, can you please check if I am going to perform the correct steps to recover it:
download su apk from the post above
reboot in recovery mode: adb reboot recovery
push SuperSU_v2.01.apk to /system/app: adb push SuperSU_v2.01.apk /system/app
reboot
Thanks a lot,
6MHz
I have a rooted T-Mobile 925T S6 Edge running stock 5.1.1 with SimplKernel_5.1.1_R5U2. I'm using SuperSU 2.49 and all rooting features work fine on the phone.
When I use ADB shell from a linux box, I get a root prompt on/from the phone, but cannot use root features such as remount / rw. I've tried Chainfire's adb insecure v2.00 but that doesn't solve the problem.
Previously with the stock 5.1.1 kernel I got the message "adb cannot run as root in production builds", which is why I installed SimplKernel_5.1.1_R5U2, but the problem persists.
Appreciate ideas how to fix. Thx, Gus
I've got some strange problems when trying to use an app which requires superuser.
I've unlocked my bootloader, flashed TWRP and (tried to) flashed SU. But now, when I try to get SU in any app it tells me, that this is not possible.
Unlocking was done with [ToolKit] OnePlus 3 ToolKit, Unlock Bootloader, Flash TWRP, Root, and More! [v2.0]
SecureSettings tells me: Root access was not detected. The System+ module...
ES Explorer tells me: Sorry, test failed. This feature cannot run on your device
There is no overlay from SuperSU, asking if SU should be granted, and the only entries inside the SuperSU app is the ADB shell and Thermux. In this two cases the window popped up and asked if I grant SU, when calling su.
Where should the SU binaries be located? I've got a folder located directly in
Code:
/
but nothing in
Code:
/system/bin
or
Code:
/system/xbin
It uses systemless root, you won't find any supersu files in /system.
If you have twrp installed I would just grab the latest supersu beta and flash it, those toolkits always seem to cause issues that can be bypassed by learning how to do the basics yourself
Already flashed it by myself. The toolkit just pushed the zip with fastboot into storage. Then I flashed it using twrp. Also download latest version, copied it onto phone and flashed that zip. Same result...