Hi,
I have a Chineese device without otg port, so I cannot connect to adb. I want to root the device. I just discovered the su binary exists in the /system/xbin. I would manually fix the root if it is possible, but I can't run the su.
The error I get while running the su binary:
uid 10076 not allowed to su
1. Is there any chance to manually fix the root, and if so what step shall I take?
2. What does is exactly mean when there is a su binary in the system/xbin folder if can't do anything whit that?
Related
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.
Hi, I'm using Samsung Note 3, i had never root my device. Usually, when i installed some official apps, i still be able to use it. However, when i updated those apps to the latest version recently, my device can no longer use the apps, those apps include some samsung official apps. I had checked those requirements for the apps to work, i had met those requirements like Minimum RAM, android version and etc..
So, i try to checked whether my phone is rooted or not using the "Root Checker" app. It shown as follow:
Root Access: No access
SU: su found [/system/xbin]
UID/GID: n/auid=10378(u0_a378)
gid=10378(u0_a378)
groups=3003(inet),50378(all_a378)
context=u:r:untrusted_app:s0
Unix Utils: n/a
PATH: /sbin
/vendor/bin
/system/sbin
/system/bin
/system/xbin
There is a su file found, but i never root my device.
1. Can i know is it possible for user accidentally rooted a phone when installing some unofficial app? or any other action that caused the existence of su file in my device?
2. I had installed "ES File Explorer", and tried to remove the su file by enabling the Root explorer, but it shown " the feature cannot run on your device", so i had tried to remove the su file by going to the "/", then "system", and "xbin", to remove the su file, but it shown that "su file cannot be deleted". Is there any possible way to remove the su file?
3. Lastly, does anyone know that my device can't run those apps is it whether caused by the "su" file or any other main problem?
Kindly need your help, please. Thank you in advance.
Note: Tested on Latest version of "pokemon go" app, same problem appears, unable to run the app as those official Samsung apps.
I have a nvidia shield tv with full android 6.
adb root and and adb remount is working, so I have root access on shell level.
Also I have /system/xbin/su which goes into root if I do not use "adb root".
But root for apps does not work. No app gets root access, RootChecker says "no".
I installed Superuser.apk but this did not help.
What is missing?
I see that this:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Caused by: java.io.IOException: Permission denied
I saw that RootChecker tells me "SELinux enforcing", is this the problem?
I do not want to download any ready-made root miracle and flash the whole device.
Since I have adb root, I can adb push everything.
Just flash su.zip and all will be fine.
I don't need SuperSU. I want to root my device i.e. that apps can execute su.
I have /system/xbin/su but it seems that apps cannot use it.
SuperSU is required to give root access to apps, even with full Android. You will need to flash the zip file from TWRP recovery.
How does SuperSU work?
As far as I understand, there is a /system/xbin/su which is called by apps wanting root access.
This su binary then starts the app to verify access. Right?
Not sure, but I think that su is just for adb and maybe system apps.
On my system I have "adb root" access. But apps do not have root access, I do not have supersu or su.
I have Samsung Intercept from Sprint with Android 2.1, locked. Tried to root it with SuperOneClick 2.3.3. It seems device is rooted (it is not failed during the rooting, and Root Checker shows phone is rooted). SuperUser was installed.
su in /system/xbin
remounting system with read only access
I used simple Root and not Shell Root. I installed Titanium Backup but was unable to start it. I've got the following error:
Could not acquire root privileges. This app will not work. Verify rom is rooted. Attempt was made using /system/xbin/su command.
In Titanium: Root access failed.
So, it seems I'm able to install non-market app but unable to run it, because SU failed to recognize it.
How to root this phone in a right way? Should I unroot it and make Shell Root? Will this unlocked the bootloader? Would this affect the wifi and other phone functions? If the system was mounted with read access only how to get write access rights?
Thank you for your suggestions
I was able to apply temporary root by InterceptRoot software. Unfortunately, permanent root on my device doesn't work.
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
pc_magas said:
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
Click to expand...
Click to collapse
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
keikari said:
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
Click to expand...
Click to collapse
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
pc_magas said:
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
Click to expand...
Click to collapse
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
keikari said:
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
Click to expand...
Click to collapse
Because SuperSu is a propriatery software.
pc_magas said:
Because SuperSu is a propriatery software.
Click to expand...
Click to collapse
I think magisk is open source https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 maybe you want to give it a try.
ps. Is open source opposite of propriatery? if not pls ignore this post
I love you you're awesome!!!!!