OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
SpongeR0b said:
OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
Click to expand...
Click to collapse
UPDATE : After running Root Checker Pro it told me that SuperSU wasn't installed.. I downloaded that from the play store and re ran Root Checker Pro, it now tells me..
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.91 - 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: -rwsr-sr-x root root 22364 2014-01-27 21:08 su
Analysis: Setuid attribute is present and root user ownership is 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:
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: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
I still have Root Explorer on the phone and seem to be able to navigate through the normally hidden directories.
Suggestions please!
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - version 3.0.2 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is 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: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is 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:
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: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
SpongeR0b said:
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Click to expand...
Click to collapse
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
joeykrim said:
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
Click to expand...
Click to collapse
Thanks for your reply JoeyKrim, unfortunately I don't think a custom recovery is available for this phone at present? I've had SuperSu on my device and to be honest not a great deal worked using it. I've also had both CWM / TWRP installed on the phone and both of them cannot find a suitable ROM to implement. I guess because of the phone being fairly new and a knock off doesn't exactly help me! :cyclops:
I will re-root my device and if that isn't successful manually try to match both superuser.apk and su binary with yet another version of superuser!
EDIT :
Here's what I've tried this morning (unfortunately now I have ran out of time and must get ready for college)
adb remount
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
adb shell
[email protected]:/ # CHMOD 644 /system/app/Superuser.apk
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
Superuser available to download from http://hosted.androidsu.com/superuser/
Using: su-3.0.1-d-signed.rar I get Superuser v3.0.1 (36), Su binary vnull (legacy)
su-3.0.1-efgh-signed.zip I get Superuser v3.0.1 (36), Su binary vnull (legacy)
Unsure of differences between d & efgh versions? Moved onto next version..
su-3.0.2-efgh-signed.zip I get Superuser v3.0.2 (37), Su binary vnull (legacy)
Renamed ([email protected]:/ # mv Superuser.apk root_Superuser.apk) seemingly no difference?
I was wondering if root allowed apps were renamed as root_appName.apk - I've left the file
name as this (i.e. Superuser.apk is NOT in my system/app/ directory and yet Superuser still
runs fine???)
Superuser-3.0.6-efgh-signed (Only binary updated) v3.0.2 (37), Su binary vnull (legacy)
su-bin-3.0.3.2-efghi-signed.zip Superuser v3.0.2 (37), Su binary vnull (legacy)
Isn't Su binary 3.0.3.2 the more up to date binary??? According my my Superuser's self update
it is?
Trying this release? - Also copied Superuser.apk to root_Superuser.apk as well this time..
Superuser-3.1-arm-signed Unable to check the versions.. different menu
Additionally myt Root Explorer (root_Root explorer.apk) now cannot gain root access which
is the first time this has EVERY occured
Superuser-3.1.1-x86-signed Unable to check the versions.. different menu
OK, so I know for sure that 3.1 is a more recent version of Superuser than I have ever had on
my phone, and of course root explorer doesn't now work, so trying an older version..
Superuser-3.0.7-efghi-signed.zip Superuser v3.0.7(41), Su binary v3.1
Again.. Root explorer no longer working.. tried deleting root_Superuser.apk
(adb shell rm -f /system/app/root_Superuser.apk)
Hasn't seemed to do anything different.. Removing all SuperUser files, ran out of time to
experiment with. Annoyed that now even my Root Explorer isn't working, I seem to be going
backwards and not forwards!!
After un-rooting (using SRSRoot) I once again have access to my Root Explorer??? Weird.
Click to expand...
Click to collapse
O.K, I'm ready for step by step instructions, anybody know how to help me please?
EDIT :
Thanks to tijsh111 for providing a working root solution to my problem..
http://forum.xda-developers.com/showthread.php?t=2219062&nocache=1
Related
Whenever I type any command in the command line that requires root (e.g. adb remount) or run script as root in script manager, I get a 'permission denied' immediately. The superuser app just doesn't pop up.
I bought the tab in China and rooted it according to the instructions in the forum. I don't know why some apps (e.g. root explorer) will pop up the su window but others won't.
It seems that my tab is partially rooted. Here is the result of Root Checker:
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root root 26336 2008-08-01 20:00 su
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Is it safe to reapply the root.zip?
Forgot to tell you that my tab was bought in China with HC 3.1 preinstalled.
After some trials. I think I'm closer to the cause of this problem.
I've flashed the latest oc kernel and after that adb remount worked without a glitch.
But after I flash a zip other than root.zip in recovery, be it kernel.zip, su_busybox_tools.zip or google_servicepack.zip (Samsung China has deprived google service off the system), the superuser icon in app drawer is becomes 4 times smaller (2 time for both height and length) than the superuser app installed by root.zip.
There seems to be something wrong with this version of superuser app. Whenever I open an app that requires root access, the superuser window is unable to pop out. As a result, I cannot use that app.
But if I reflash the root.zip. The big-icon superuser app is back. And other apps can revoke it most of time. However, it is not perfectly stable. Somethimes, it still failed to be revoked.
Any thought on this?
su from the busybox pack installs a new su app which only monitors /system/xbin/su executable, not the /system/bin/su executable the root.zip provides.
You can either remove the /system/bin/su executable (and optionally create a link to the /system/xbin/su executable in it's place) or re-install the su app from the root.zip file.
Thanks, I've flashed latest starburst rom and all is set.
i Rooted my phone a few months ago and installed a few roms but didnt like any of my options so i kept the phone rooted with the stock look. now i want to try a new rom and my phone is telling me my phone isnt rooted any more...
any suggestions??
What is telling you that you are not rooted? Like trying to run certain root apps? How did you root? Which bootloader? Does is say s-on or s-off?
Sent from the MIUI powered 3d
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
ramseyattar said:
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
ramseyattar said:
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
Click to expand...
Click to collapse
looks like your bootloader is still unlocked, which is a very good sign.
more than likely the permissions on your root access where changed at some point in time. either from loading a ROM or removing/adding superuser.apk incorrectly.
my application, root checker pro, will show all the necessary information in order to troubleshoot.
my guess would be, you'll probably need to install the superuser.zip file from recovery mode and that should add the /system/bin/su binary for Superuser.apk back and set the permissions as 4755 on the su binary. this is the most common and simplist method of properly restoring root access for Superuser.apk users.
if you want, feel free to post up the root checker pro results and we can specifically troubleshoot. hope that helps!
joeykrim said:
looks like your bootloader is still unlocked, which is a very good sign.
more than likely the permissions on your root access where changed at some point in time. either from loading a ROM or removing/adding superuser.apk incorrectly.
my application, root checker pro, will show all the necessary information in order to troubleshoot.
my guess would be, you'll probably need to install the superuser.zip file from recovery mode and that should add the /system/bin/su binary for Superuser.apk back and set the permissions as 4755 on the su binary. this is the most common and simplist method of properly restoring root access for Superuser.apk users.
if you want, feel free to post up the root checker pro results and we can specifically troubleshoot. hope that helps!
Click to expand...
Click to collapse
my results were:
Root Access is not properly configured or was not granted.
The following link is a suggested Guide for obtaining root access on your device. No guarantee the guide will work. Please use the guide with CAUTION!! Suggested guide for your device:
http://www.revolutionary.io/
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
---xr---wt root root 26324 2011-08-12 15:27 su
Standard su binary location: ls -l /system/xbin/su:
lrwxrwxrwx root root 2011-09-07 20:28 su -> /system/bin/su
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
ramseyattar said:
my results were:
Root Access is not properly configured or was not granted.
The following link is a suggested Guide for obtaining root access on your device. No guarantee the guide will work. Please use the guide with CAUTION!! Suggested guide for your device:
http://www.revolutionary.io/
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
---xr---wt root root 26324 2011-08-12 15:27 su
Standard su binary location: ls -l /system/xbin/su:
lrwxrwxrwx root root 2011-09-07 20:28 su -> /system/bin/su
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Click to expand...
Click to collapse
Those results are perfect in that they show exactly what the issue is!
If you are familar with ADB, the process is very simple to fix your root access. I've done this many times! A basic but important process to learn, in my opinion.
Reboot to recovery, from a computer type, adb shell and issue two commands as follows:
mount /system /system
chmod 4755 /system/bin/su
go ahead and reboot.
Alternatively, if you're not familar with adb, the next simpliest approach, in my opinion would be to load the Superuser-3.0.6-efgh-signed.zip file onto your sdcard. reboot into recovery and "flash"/install the .zip file. The superuser.zip file will execute the above commands for you.
Run Root Checker Pro again and it should trigger superuser prompting whether or not to grant root checker access. go ahead and grant it root access.
Root Checker Pro should confirm you have root access and for the /system/bin/su line it should show an "s" in the middle of the permissions, example: rwxsr-xr-x root root 26324 2011-08-12 15:27 su . the "s" being in the middle is important as this is the setuid bit essentially granting the su binary superuser permission/access.
Reasons the permissions were changed on the /system/bin/su binary ... really hard to say but we can narrow down the causes. In order to change the permission, the process/device/application would need root access. Everything executed in recovery mode usually runs as root and many users don't inspect the updater-script file of the ROM .zip before they load.
Sometimes flashing ROMs, which aren't setup properly, will remove or set incorrect permissions removing the setuid bit on the su binary.
Also, flashing an OTA file would definitely remove the setuid bit on the su binary.
Hope that helps!
I hope somebody can help me.
Since yesterday all of a sudden I could not download anything anymore from the market.
I rebooted and some programs were not working anymore (android market & quickpic don't launch).
Also my go launcher ex dissapeared everywhere ... without any reason.
When trying to use my titanium backup it said that no rooting privilages got granted.
I checked and I could not find my superuser / rom manager anymore ..
Searching the internet brought me to this topic.
I downloaded the RootcheckPro APK and ran it on my HTC Desire with below result.
Is there anybody who can help me :-(
I am desperate ...
Thanks in advance.
(Busybox - All was fine)
Below is the error messages I get when running "ROOT"
Root Access is not properly configured or was not granted.
The following link is a suggested Guide for obtaining root access on your device. No guarantee the guide will work. Please use the guide with CAUTION!! Suggested guide for your device:
Unrevoked
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:
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: ls: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x 1 root root 22240 Aug 1 2008 /system/xbin/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/bin/su:
Result: ls: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: ls: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
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: root user - ro.secure=0
Results provided on your HTC Desire device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Click to expand...
Click to collapse
What rom are you on?Did you move any apps to the sd (apps2sd) card instead of the system to save space?If something like this happens to me and i can't figure it out,i just reinstall the rom over the top without wiping anything,it will usually fixes my problem,but its good to do some research first.
Hello all-
I am having an issue with my rooted rezound (s-on).
A few days ago randonly i looked down (was at work and phone was in silent mode) and the phone seemed ot be in boot loader mode and then resart.
I was in the middle of work and couldnt investigate further and honestly forgot about it as nothing seemed to be odd on the phone.
well last night i went to turn on the "wifi tether" and no dice....it seems my su binary is gone and superSU is acting all screwed up.
Root checker Pro info below.....keep in mind i have tried to un-installing recent updates for superSU and it seemed to not allow me to do anything...even tried to un-install the entire app itself with no luck.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.94 - 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 shell 91980 2012-09-18 22:11 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
Can't tell you what happenned but a quick flash of this
http://download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
Should correct it. If not reflash your rom after wiping system.
Snuzzo said:
Can't tell you what happenned but a quick flash of this
http://download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
Should correct it. If not reflash your rom after wiping system.
Click to expand...
Click to collapse
AH ok, i will try that and see....im concerned because my titanium backup no longer works because my root acess was lost. I have a lot on my phone that i havent had a chance to backup and am worried about losing it.
jesternsb said:
AH ok, i will try that and see....im concerned because my titanium backup no longer works because my root acess was lost. I have a lot on my phone that i havent had a chance to backup and am worried about losing it.
Click to expand...
Click to collapse
Do an adb backup. That works only on your current rom though, but would work in this case if you do need to wipe.
Snuzzo said:
Do an adb backup. That works only on your current rom though, but would work in this case if you do need to wipe.
Click to expand...
Click to collapse
Ended up re-flashing the supersu zip and was GTG.
Thanks as always
i have been trying this for awhile now and so far i only have it unlocked and running cwrm touch. i have super su and superuser on my phone but both fail to gain root access when i try and update the binary. i have a log that may help you guys understand the problem.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied 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-02-17 00:54 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
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
any idea on how to get it to root? ive tried to install a custom rom and it would work but it wouldnt get past the loading screen. so i had to flash back to the stock rom. i also cant get su because its not rooted. id appreciate any help you guys can offer. thanks!
kodi.roberts said:
i have been trying this for awhile now and so far i only have it unlocked and running cwrm touch. i have super su and superuser on my phone but both fail to gain root access when i try and update the binary. i have a log that may help you guys understand the problem.
Click to expand...
Click to collapse
For the initial rooting you have to flash a superuser app from recovery rather than installing it from the Play Store or an apk. After the initial rooting is done and the app itself can get root permission, you can update using using the app.
The current flashable SuperSU zip file can be downloaded from this post.
ramjet73