Titanium backup can't get root permissions - Nexus 7 Q&A, Help & Troubleshooting

I have the 16 gig Nexus 7 which I have rooted but having tried to backup my ROM I find I am unable to reboot into Recovery to perform a ROM backup. I also cannot flash to the latest version of Clockworkmod, I have version 6.1.0 when I am told that 6.2.3 is available. When I try to flash the download reaches 100% and says flashing before telling me an error has occurred. Also Titanium backup can't get root. Is it possible I am not fully rooted and is there a way to check? Thanks in advance.
Sent from my Nexus 7 using xda app-developers app

There is an app called "Root Checker" ... Do you have SuperUser installed and does it open?
Sent from my Nexus 7 using xda app-developers app

Yes I have superuser installed and it does open OK and does list some apps as having root permissions. I will try the checking root app and thanks.
Sent from my Nexus 7 using xda app-developers app

Just tried Root Checker and sure enough it says my device is not rooted correctly. Now to find out why with the pro version!
Sent from my Nexus 7 using xda app-developers app

Just run root checker pro and got the following output:
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.99 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 380532 2008-08-01 13:00 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.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-07-18 20:47 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
Results provided on your Nexus 7 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
Can somebody please tell me how to fix this

Have you tried wugfresh's root toolkit? It's easy to use. I've rooted, and reset and rerooted several Nexus 7s with it and never had a problem.
Sent from my Nexus 7 using xda premium

Why do you have 2 SU apps installed? That's probably what is messing you up.
Remove super user and re flash supersu from fastboot. The supersu flash will make it work.

Related

Cant acquire root privileges

Im having trouble with root privileges, I rooted my phone for the first time the ohter day using the user guild for noobs and had a froend help who knew what he was doing. Everything went well and the phones running a treat. Only issue I got is I dont have root privileges and I dont know why? Any suggestions?
Not sure what info you may require.
Explain how you rooted and your software (os) version so we can help you better.
Sent from my GT-I9000M using Tapatalk
xxbeanxx said:
Explain how you rooted and your software (os) version so we can help you better.
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
I used the noob guide on this site
http://forum.xda-developers.com/showthread.php?t=1139050
and these files
GT_I9000_XXJVQ_XXJVQ_OXAJVQ_Sbl.exe
CSC_OXAJVQ.tar.md5
PDA_XXJVQ_Sbl.tar.md5
PHONE_XXJVQ.tar.md5
using
Odin_v1.82_and_512.pit_513.pit_803.pit_files.exe
So you flashed the CF rooted kernel?
Try putting your phone in debug mode and open a shell to it using adb. Once inside check to see if the su binary is in /system/xbin.
ie:
Code:
adb shell
$ ls -l /system/xbin/su
if you see something like this, you're golden:
Code:
-rwsr-sr-x root root 26264 2011-08-16 15:49 su
(also notice the permissions, it needs to be setuid, although I would guess if it is there it is unlikely it is not setuid)
if you see this, something's wrong:
Code:
/system/xbin/su: No such file or directory
if you have su, have you installed the superuser app from the market?
if not, you have to figure out why..for example, do you have space on your /system filesystem?
Code:
$ df /system
Filesystem Size Used Free Blksize
/system 275M 256M 19M 4096

Problem in Rooting DDJP6(after Indian official update)

Need Help for rooting my G3,
Baseband I5801 DDJP2
Kernel: 2.6.32.9
[email protected]#2
Build FROYO.DDJP6
I've rooted earlier, but since official update in India of DDJP6 all the applications which need root access have stopped working, now I'm unable to root or unroot again with superclick(2.1 and 1.7) as it doesn't detects my cell.
Help please, here a snapshot of root checker, it might help.
Superuser.apk -com.noshufou.android.su -version 3.0.6 is installed! System Environment PATH: /sbin /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: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su: /sbin/su: No such file or directory 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 Results provided on your GT-I5801 device by Root Checker version 3.9 from joeykrim in the
Sent from my GT-I5801 using XDA App
Flash cf-root kernel and you get root instantly, no hassles
Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App
Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"
ashutoshbpl said:
Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
No, its just a kernel, it wont wipe anything
umangsagar said:
Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"
Click to expand...
Click to collapse
z4root wont work on froyo, it uses an old exploit
Since we are talking about it, anyone has link for I5801DDJP6?
And anyone knows the changes between DDJP5 and DDJP6?

[Q] How to tell if rooted correctly?

I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
crimsontide said:
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
Click to expand...
Click to collapse
If you used BurritoRoot and you were able to successfully install the Market, then you likely have root.
Easiest and simplest way to 100% know is connect your KF to your PC. Run the following:
Code:
adb shell
su
If it says "su: Permission Denied" you don't have root (or at least it is not currently enabled). If it just gives you a prompt run:
Code:
id
If it comes back and says "uid=0(root) gid=0(root)" then you are good.
Make sure you use the superuser posted in the burritoroot post. There was one posted originally that was no good with the kindle fire but they updated to a working one.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
http://www.mediafire.com/?jj8sx4ojvq9i198
litotamez said:
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
I tried that app and it reports, "Sorry, you don't have root access."
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac devices
List of devices attached
7766000600000001 device
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell
$ su
su: permission denied
$
Looks like I have some more work to do, and I am not sure where to start.
I have installed on the KF:
BurritoRoot: Kindel Fire Edition 1.0.0
version 1.0.0
SuperUser version 3.0.6
Click to expand...
Click to collapse
Ok I went back and re-ran everything. Had to uninstall SuperUser in the middle, but things seem to be working better now!!!
HTML:
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac root
adbd is already running as root
Traveler:KindleFireRootMacLinux crimsontide$ adb push su /system/xbin/su
-bash: adb: command not found
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac push su /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chown 0.0 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chmod 06755 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
4426 KB/s (785801 bytes in 0.173s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
2858 KB/s (785801 bytes in 0.268s)
pkg: /data/local/tmp/Superuser.apk
Success
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac reboot

[Q] After JB update, have partial root; only for existing approved apps [SOLVED]

So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!
You did a good job of explaining the situation. I am in the same position.
Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 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:
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 XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market
I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2
FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?
Not sure....I don't think so. Good luck!
RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.
I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!

Lost Root Access

Hi all
After SuperSu requires me to update the binary and installed DeviceFaker it asked to me reboot but after rebooting Root Access gone. I checked it via Root Checker Pro and below are the findings.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 2.16 - 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 71532 2014-10-29 17:38 su
Analysis: Setuid attribute is not present BUT 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: shell (non root) user - ro.secure=1
Results provided on your GT-I9505 - Android 4.4.2 device by Root Checker Pro
Can someone please direct me to a thread on how to properly fix my issue.
Also, if i root my phone again via towelroot will this fix the problem??
TYIA for those who'll reply.
trancerziloth said:
Hi all
After SuperSu requires me to update the binary and installed DeviceFaker it asked to me reboot but after rebooting Root Access gone. I checked it via Root Checker Pro and below are the findings.
Root Access is not properly configured or was not granted.
Can someone please direct me to a thread on how to properly fix my issue.
Also, if i root my phone again via towelroot will this fix the problem??
TYIA for those who'll reply.
Click to expand...
Click to collapse
Hi mate
Seem like you lost root ...yes re root again , it should solve your problem
Up.. any ideas pls?
Any ideas on how to solve this? I'm having the same problem on my Galaxy Note 2 (SPH-L900) running 4.4.2. Re-rooting with Odin and the latest CF file doesn't help; it still reports the same problem. I've tried un/reinstalling SuperSU, but that doesn't make any difference, either. Any help would be wonderful.
Obi-Wan-YJ said:
Any ideas on how to solve this? I'm having the same problem on my Galaxy Note 2 (SPH-L900) running 4.4.2. Re-rooting with Odin and the latest CF file doesn't help; it still reports the same problem. I've tried un/reinstalling SuperSU, but that doesn't make any difference, either. Any help would be wonderful.
Click to expand...
Click to collapse
Delete everything Knox related.
Lennyz1988 said:
Delete everything Knox related.
Click to expand...
Click to collapse
I'm already running a custom Community ROM that already has all the Knox stuff removed. It came rooted, and worked fine for several months, until it magically lost root access a month ago.
I *REALLY* don't want to wipe the phone and flash a new ROM, because my lack of root access means I haven't gotten a complete backup in over a month.

Categories

Resources