Sorry to bother everyone.
In preparation for the 4.04 update, I flashed the stock 4.02 ROM and then was prompted to install the VZW OTA update. This flashed OK. I went ahead via adb and flashed cwm-recovery and then installed the su.zip file via the recovery console.
Once rebooting, I'm able to pop open an adb shell and type su and become the superuser, however none of the apps that require root no longer work -- root explorer, busybox installer, etc.
I'm guessing its a problem with my su file (possibly). Does anyone have any suggestions to troubleshoot? Thanks.
The problem I'm having specifically is gaining root access....fail (within su app).
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
I've got an LG-510, model number VK810, software version VK81022B, Android version 4.4.2
I originally rooted using towelroot when the device was at 4.2.2.
Several months later, I did an OTA update to 4.4.2. Root appeared to be gone...I couldn't access directories using Root Explorer...but when I attempted to re-root using ioroot and again using Stump, I couldn't. With ioroot I kept getting the 'signature verification failed' error. Stump notified me that my device had already been rooted.
Dug through my device to find that system/bin/su, system/xbin/su, and system/xbin/daemonsu were still installed. They were still there after doing a factory data reset (from settings).
Running ps | grep su from Terminal IDE shows that the following commands are running
daemonsu:mount:master
daemonsu:master
If I want to successfully re-root my device, how should I proceed?
Additionally...would it be possible to remove daemonsu and su from adb after mounting system as rw?
EDIT: More info...system/bin/su is linked to system/xbin/su. Immediately after posting this I ran ps | grep su from adb shell, and in addition to the commands posted previously, the following was also running:
daemonsu:10213
UPDATE: Even stranger, running daemonsu from adb shell pops up the SuperSU Deny/Allow prompt.
UPDATE: Strangest of all...running daemonsu in TerminalIDE opens the root prompt. No notification from SuperSU so I still need to fix this.
Problem Solved
Basically, I followed the steps from the original post in this thread: http://forum.xda-developers.com/showthread.php?t=2590185. Once the process was complete, all su and daemonsu binaries were gone.
MonaLisaOverdrive said:
I've got an LG-510, model number VK810, software version VK81022B, Android version 4.4.2
I originally rooted using towelroot when the device was at 4.2.2.
Several months later, I did an OTA update to 4.4.2. Root appeared to be gone...I couldn't access directories using Root Explorer...but when I attempted to re-root using ioroot and again using Stump, I couldn't. With ioroot I kept getting the 'signature verification failed' error. Stump notified me that my device had already been rooted.
Dug through my device to find that system/bin/su, system/xbin/su, and system/xbin/daemonsu were still installed. They were still there after doing a factory data reset (from settings).
Running ps | grep su from Terminal IDE shows that the following commands are running
daemonsu:mount:master
daemonsu:master
If I want to successfully re-root my device, how should I proceed?
Additionally...would it be possible to remove daemonsu and su from adb after mounting system as rw?
EDIT: More info...system/bin/su is linked to system/xbin/su. Immediately after posting this I ran ps | grep su from adb shell, and in addition to the commands posted previously, the following was also running:
daemonsu:10213
UPDATE: Even stranger, running daemonsu from adb shell pops up the SuperSU Deny/Allow prompt.
UPDATE: Strangest of all...running daemonsu in TerminalIDE opens the root prompt. No notification from SuperSU so I still need to fix this.
Click to expand...
Click to collapse
if supersu is popping up, then you do have root. What is it that makes you think you don't have root?
also, do you have the google plantation? Or the verizon model?
sleekmason said:
if supersu is popping up, then you do have root. What is it that makes you think you don't have root?
also, do you have the google plantation? Or the verizon model?
Click to expand...
Click to collapse
SuperSU didn't pop up when running "root" programs from my device. Root Explorer didn't browse the entire filesystem, etc.
I did a half ass job in trying to unroot. I deleted the su binary and superuser.apk file but didn't restore the stock ROM or recovery or boot before deleted them. I didn't wipe disk and relock the bootloader either, I just stopped there.
After that, my ROM, Viperx 3.7.7 can still grant apps permission to access root, albeit a little buggy (can't grant for one time but must choose either 10min of access or forever). But after I update to Viper 4.1.1 or CM 12, that ability is lost completely and CWM start asking me if I wanted to fix root upon exit. Right now I can still access root and do things to its file (maybe) but I can't grant any permission, root checker told me my root is not properly installed and like I said above, CWM keep asking me and what I choose (Yes or No) makes no difference.
Anyone got a clue about what I should do? I've already tried to reflash the su binary from the onexroot zip file available on this forum, It didn't do anything.
Updated: I still have my su binary, but I don't have any superuser.apk in system/app
And I can't deleted or do anything to the files in root dir.
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...
Have a FTV rooted version 1 with old firmware (51.1.4.0) I updated TWRP to the latest version then used a pre-rooted rom to upgrade to 5.5.2.1.1
I now have some problems with a file (mbcache.db) increasing in size so I would get Memory full delet apps.
I wanted to use TWRP to change rom to a later one. Hoping the problem would go away.
When I booted into TWRP i found that it reverted to old version screen is huge can only see button to install and cant scroll around
So I tried to update TWRP again but when I use adb and just after I run adb shell I try to run su but I get this
/system/bin/sh: us: not found
So
I cant do anything because everything requires the su command
I also checked and my bootloader is locked but wasn't when I did the first rom but now its locked
Any idea whats going on
Rick
Ok I think I got it figured out was able to downgrade to 5.0.5.1
I am having a similar issue with SU permission. My rom is 5.2.1.1, and boot loader unlocked. I was wondering if you can help me out. I am able to access FireTv with Teamviewer Quicksupport and SU grants permission, but when I select remote control however it grants permission, and then quickly denies it. What exactly am I doing wrong?
Does the Xposed framework and Module have to be installed again? If so what version should I use or does that not make a difference with this working? I have busybox updated and working fine, but I can't get my head around this. I had it working before on OS 3, but on OS 5 no luck, I know it works, but something is changing the permissions quickly. If you can please help me with this it would be greatly appreciated.
Don't know if this helps but I found FACTORY RESET kills removes the SU functionality. I just reinstalled my routed rom and SU worked again