Hi all,
not sure if this is the right section to post this...
I already have root access through adb shell and I've installed superuser. However, my apps don't seem to be able to gain root access. This is what they have available:
$ su
# ls -l /system/xbin/su
lrwxrwxrwx root root 2012-03-29 17:27 su -> /system/bin/su
# ls -l /system/bin/su
-rwsr-sr-x root shell 64196 2012-03-29 14:10 su
I also compiled busybox 1.19.4 and it's on the device in /system/bin and xbin. I can use it with the busybox prefix (didn't manage to install it, the --install option doesn't work here... applet not found).
What am I missing for my root apps to work? Is it because of the missing --install on busybox? If so, does anyone know where to find a version that works?
Thanks!
Related
PLEASE HELP!!! First off I am a noob. Superuser keeps force closing on my htc evo 4g. Im running mikg 2.45 and have been for a few weeks which is great by the way. A few days ago I was deleting files in my phone and I'm not sure if I removed something that I wasnt supposed to but I think thats what happened. How can I correct this because I want the flash mikg 2.51 but the app root checker is saying I DO NOT have root access and this is what its saying
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 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 root
Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx root root 2011-08-09 13:34 su -> /system/xbin/su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root root 26324 2008-08-01 08:00 su
Alternate su binary location:
/sbin/su: No such file or directory
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your PC36100 device by Root Checker version 3.7 from joeykrim in the Android Market
PLEASE HELP IF YOU CAN I DONT WANT TO BRICK MY PHONE.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi! I have lost root access after recently updating my HTC Evo 4G. I checked with 'root checker' with the following response. I have looked at previous posts but none of them fit. Can someone help?
Thanks in advance.
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 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:
-rwxr-xr-x root shell 26324 2011-10-13 22:39 su
Standard su binary location: ls -l /system/xbin/su:
lrwxrwxrwx root root 2011-10-13 22:39 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
Try re-rooting .
Sent from my GT-S5830 using XDA App
Thanks a bunch!
Here is what ROOT CHK PRO SAYS AFTER I RUN IT. WHAT NEEDS TO BE DONE TO FIX THE ISSUE? ANY HELP I WOULD APPRECIATE. IM LEARNING SO ALL INFO IS NEEDED AND I WILL BE GREATFUL. CUZCARTER --- 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. 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: -rwxr-xr-x root shell 380532 2008-08-01 07:00 su Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location Check Command: ls -l /system/xbin/su: Result: lrwxrwxrwx root root 2012-08-17 20:51 su -> /system/bin/su Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location Check Command: ls -l /sbin/su: Result: /sbin/su: No such file or directory Analysis: File /sbin/su does not exist.
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 SPH-D710 device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market
Sent from my SPH-D710 using xda app-developers app
[originally posted in galaxy tab 1 forum by mistake...]
I used clockworkmod recovery and the cwm-root-gtab2.zip package to root my Tab 2. su appears to be installed ok, and I can get root permissions by running it from an adb shell:
~ $ adb shell
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),1015(sdcard_rw),1028(sdcard_r),300 1(net_bt_admin),3002(net_bt),3003(inet),3006(net_b w_stats)
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),1015(sdcard_rw),1028(sdcard_r),300 1(net_bt_admin),3002(net_bt),3003(inet),3006(net_b w_stats)
[email protected]:/ # ls -la /system/bin/su
-rwsr-sr-x root shell 22364 2008-08-01 12:00 su
[email protected]:/ #
So the su binary is present and has setuid bit set on its permissions. But if I run it from a SSH session, or via a terminal emulator on the Tab itself, I get permission error:
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $
Various root checking apps report similar problems. What am I doing wrong? Other threads suggest steps to recreate the su binary with the correct 6755 permissions, but as far as I can see, everything is already as it should be permissions-wise.
Thanks.
First off ran in to the same problem as you I could not get that root to work through cwm method so i did some more research and found my answers here http://androidjinn.com/how-to-root-galaxy-tab-2-p3113-on-ueclk7-android-4-1-1-firmware.html assuming that you are on the gtp3113 model and on stock jb like i am and not looking to flash other roms lol i havent been able to find a way to load cwm without loosing my root again
aj9507 said:
First off ran in to the same problem as you I could not get that root to work through cwm method so i did some more research and found my answers here xxxxxxx assuming that you are on the gtp3113 model and on stock jb like i am and not looking to flash other roms lol i havent been able to find a way to load cwm without loosing my root again
Click to expand...
Click to collapse
Thanks, but unfortunately my model is P3110.
On 4.1.1 completely stock. I used OTA Root Keeper to retain root successfully.
TiBu and Root Explorer were already running as root and still get root access.
Any new apps never prompt for superuser authority??
Root Checker Pro says I'm rooted,
OTA Root Keeper says:
x Superuser app installed
x Device rooted
Root permission granted
x /system supports root protection
x Protected su copy available
I tried to install SuperSU but that also failed, it doesn't
prompt for superuser rights so it can't write the su
binary.
I'm confused, what changed? how do I fix it?
I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app
su binary issues?
Reilly1812 said:
I can't go into details now but your su binary is the problem. Do not uninstall anything that still has root as you will lose it. I can go into more details when I get to the office later this morning.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I do have root access from adb I should be able to push a new binary
then set its perms, from adb shell.
Where would I find the binary I need?
I was using Superuser.apk and its binary.
Shouldn't OTA rootkeeper have saved a copy?
it says I have root, and it has copy somewhere.
--> Root Checker output
Congratulations! You have root access!
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 2013-01-29 02:14 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 ASUS Transformer Pad TF300T device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
I had exactly the same problem when I first upgraded from ICS to JB. Thought I had root until I decided to try AdAway. I uninstalled AdFree and attempted to install AdAway. The install failed stating that I did not have root. Of course I did since AdFree worked, ES File Explorer worked, Terminal Emulator worked, etc. Searched and searched and found discussion which highlighted the su binary to be the issue. Attempted to use the app to update the binary and it failed. I believe (and watch how fast I get corrected!) that the implementation of multiuser support in android is what requires the new versions of superuser and the binary. I documented the permissions of the existing su in /system/bin/ and ensured that I did not have another in /system/xbin/. Using ES File Explorer I copied and pasted on top of the existing su in /system/bin, checking to ensure permissions were good. You should then be able to download the latest and greatest binary using the app. This was all done with superuser. I have not worked with SuperSU. I crossed my fingers and restarted the tablet. I was good to go and have full root.
Please note that others have come back and stated that it did not work for them. I can tell you what worked for me and why I believe it did. I will add the link to the post discussing this problem as soon as I find it again.
Check out this thread which worked using adb.
http://forum.xda-developers.com/showthread.php?t=2183105
[Solved] that seems to have worked
downloaded updated su binary
adb pushed to /sdcard
adb shell
Code:
/system/bin/su
mount -o remount,rw /system
mv /system/su /system/su.bak
cat /sdcard/su > /system/bin/su
chmod 6755 /system/bin/su
exit
adb reboot