Hi,
I tried to root a 7" Galaxy Tab (device MID7 with Marvell CPU) runing Android 2.3.5 by using z4root ver.1.3.0 but I haven't managed. I got the following response from Root Check Pro V1.2.7 (I have Superuser 3.0.7 installed).
Verifying BusyBox:
BysyBox has been installed correctly!
Verifying Root:
Root Access is not properly configured or was not granted.
Detailed results:
Superuser application - version 3.0.7 - is installed
System file properties for root access:
Standard location
Check command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 64196 2008-08-01 20: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!
Question: which file and how do I execute it??
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
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: Nosuch file or directory.
Analysis: File /ststem/xbin/sudo does not exist.
Root user ID and group ID status:
SU binary not found or not operating properly
System environement path: /sbin/vendor/bin /system/sbin/system/bin /system/xbin data/bin/ marvell/tel/busybox/bin
ADB shell default user:
ADB shell setting for standard access, stored in default.prop is configured as rootuser -ro.secure=0
Using the Root Browser I noticed that:
- there is no /system/bin/su file (as correctly indicated by Root Checker)
- folder /sbin is empty, although the Checker says there is a su flile there, but permission is denied. It the file hidden?
- there is a /system/xbin/su file,
- there is no /system/xbin/sudo file (as correctly indicated by Root Checker)
- there is a /marvell/tel/busybox file, but not a folder
I also have Terminal Emulator 1.0.41 installed, however it seems I cannot do anything with it now.
I would appreciate explanations and suggestions about how to gain root, taking into considerations all of the above.
Thank you.
Try using SuperOneClick. It worked for me:
http://forum.xda-developers.com/showthread.php?t=803682
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09: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!
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.
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 DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
clyde1914 said:
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09: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!
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.
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 DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
Click to expand...
Click to collapse
Try rebooting.
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link Here. If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
nobe1976 said:
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
Click to expand...
Click to collapse
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
clyde1914 said:
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
Click to expand...
Click to collapse
I would stick with the HOB just to keep the data. The only route I have found that will successfully re root it is done with Linux. It can be done running Linux on a thumb drive as long as there was space created for updates.
Sent from my XT875 using Xparent Red Tapatalk 2
If that doesn't work and you need restore it to JB, here are the relevant links:
FXZ files for Bionic:
http://forum.xda-developers.com/showthread.php?t=2240725
RSD Lite Example (not for bionic, but gets you some of the links you'll need):
http://forum.xda-developers.com/showthread.php?t=2231249
If you want to try it from linux, fastboot from linux:
http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz
And if you need to root once you flash your JB stock image, you'll need something like this:
Easy root:
http://forum.xda-developers.com/showthread.php?t=2256439
I've successfully unlocked my bootloader, but having trouble getting root. I've flashed SuperSU-v1.65 using TWRP and Root Checker Pro gives the result below. USB debugging is on. Any thoughts? Apologies in advance if wrong thread or Q has been answered in a prior thread.
Thanks!
+++++Root Checker Pro output:
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.80 - 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 104496 2008-08-01 07:00 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 /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
Hi! I'm a newbie here and i need help with my CM 11.0 M9 from novafusion. I put M9 today (i was M8) and my root don't ser to work anymore! When i try to use lucky patcher it says i have a su java-code running and i don't know what's going on. I Tried root checker pro and it says i have root but there's some weird stuff at the description.
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 2.01 - 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 125420 2014-09-18 18:18 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:
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 GT-I8190 - Android 4.4.4 device by Root Checker Pro version 1.3.7
And yeah. When I installed SuperSU it said i need to upgrade binary and when i tried it told me that it couldnt install it and after rebooting i couldnt see the SuperSU binary upgrade offer anymore.
Also when i installed the new ROM i made a full wipe at twrp recovery including system.
Please somebody help me! If you need any more information just ask me. Sorry my horrible english. And thanks.
Have you tried flashing SuperSU through TWRP? You can find the flashable zip in the SuperSU XDA thread.
Sent from my GT-I8190 running tenshi_xp's PAC ROM 4.4.4.
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix. Any help will be appreciated this is the first time I have rooted.
PS. If this post is in the wrong place please advise where itshould be.
Thanks