I've got some strange problems when trying to use an app which requires superuser.
I've unlocked my bootloader, flashed TWRP and (tried to) flashed SU. But now, when I try to get SU in any app it tells me, that this is not possible.
Unlocking was done with [ToolKit] OnePlus 3 ToolKit, Unlock Bootloader, Flash TWRP, Root, and More! [v2.0]
SecureSettings tells me: Root access was not detected. The System+ module...
ES Explorer tells me: Sorry, test failed. This feature cannot run on your device
There is no overlay from SuperSU, asking if SU should be granted, and the only entries inside the SuperSU app is the ADB shell and Thermux. In this two cases the window popped up and asked if I grant SU, when calling su.
Where should the SU binaries be located? I've got a folder located directly in
Code:
/
but nothing in
Code:
/system/bin
or
Code:
/system/xbin
It uses systemless root, you won't find any supersu files in /system.
If you have twrp installed I would just grab the latest supersu beta and flash it, those toolkits always seem to cause issues that can be bypassed by learning how to do the basics yourself
Already flashed it by myself. The toolkit just pushed the zip with fastboot into storage. Then I flashed it using twrp. Also download latest version, copied it onto phone and flashed that zip. Same result...
Related
Sorry to bother everyone.
In preparation for the 4.04 update, I flashed the stock 4.02 ROM and then was prompted to install the VZW OTA update. This flashed OK. I went ahead via adb and flashed cwm-recovery and then installed the su.zip file via the recovery console.
Once rebooting, I'm able to pop open an adb shell and type su and become the superuser, however none of the apps that require root no longer work -- root explorer, busybox installer, etc.
I'm guessing its a problem with my su file (possibly). Does anyone have any suggestions to troubleshoot? Thanks.
The problem I'm having specifically is gaining root access....fail (within su app).
So I usually use the toolkit to root, in fact I have been for many versions now.
However with the installation of 4.2.1 I haven't been able to root at all. I use the toolkit in the same way but it simply doesn't root the phone.
So today I tried the manual way. I downloaded and installed SDK tools from google navigated to the adb folder and went through the commands. Everything seemed to go okay apart from when I typed adb shell chmod 06755 /system/bin/su. The command window did nothing.
I carried on and typed adb shell chmod 06755 /system/app/Superuser.apk, when it said "bad command" or something similar.
Rebooted the phone, no root... still.
However the Superuser app is there. So:
1) How do I delete the superuser app, bearing in mind it has system permissions. I'd like to simply start again.
2) I don't have CW recovery installed and would prefer not to bother with it if I can.
3) Just to confirm, when I root the phone, does that allow me to delete files in the /system/app folder?
4) Following this guide on rooting manually. Is that all alright?
5) In a couple of sentences, can someone explain rooting to me? From what I understood, rooting simply opens up the phone to allow access to everywhere, where you can copy and delete files, or apks.
6) If 5 is true, when following the rooting guide (4), which command am I actually telling the system to run as root? Is it simply the "root" command?
7) If 6 is true, how come when I re-boot, the phone won't let me delete things from the system/app folder?
Thanks for any help.
1) stop using a toolkit, and no you didnt root the manual way.
2) download this: http://forum.xda-developers.com/showthread.php?t=1538053 - its supersu, superuser is unreliable on 4.2+
3) fastboot flash a recovery
4) flash the supersu.zip
5) done.
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Don't these superuser apps just manage app permissions? They don't actually enable the root access do they?
Thanks
anotherxdauser said:
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Thanks
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
anotherxdauser said:
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
Click to expand...
Click to collapse
it replaces anything in /system... basically the OS.
I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...
ChrisG12 said:
I had previously rooted my phone and everything was fine... The OTA 4.2.2 update came automatically and took away root (but kept the bootloader unlocked). A few months passed and I decided to reroot using the same approach as before .... it fails. It looks like it works, but once the phone reboots I don't have root access.
Note I am using the following commands:
> adb push su.zip /sdcard/
> fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
> adb reboot bootloader
Then I select install from sdcard and selecting the su.zip file and back out / reboot.
Only odd thing I see is that I have two superuser apps installed (must have used different zip files). But neither app works...
Click to expand...
Click to collapse
adb reboot bootloader ?? or fastboot reboot-bootloader?? you are supposed to be in fastboot mode.
i dont know if this will make sense: flash latest CWM http://www.clockworkmod.com/rommanager and install latest supersu http://download.chainfire.eu/324/SuperSU/UPDATE-SuperSU-v1.30.zip
open supersu and update su binary
install busybox
2 in a row: OP, read the stickies on general and q&a by efrant before asking questions.
a maguro wrote this.
Actually - I did read the stickies before posting - thanks though. I know how to root - done it on a few devices in the past. Done it successfully on my Nexus in the past too...
For the record, those commands I listed are valid (they are from instructions on Droidlife.com and XDA) - I prefer not to use a "one-click" tool. So I use the Android SDK and run commands from a DOS window one at a time. Also - this way I don't have the custom ROM permanently installed on my phone...
That exact procedure worked in the past - but now it doesn't. I've tried the latest roms, etc. nothing - all the commands seem to run fine but after the phone reboots - I don't have root.
I did at one point try one of the one click tools ("Nexus Root Toolkit") - but it didn't seem to work either.
Has anyone seen this problem? I seem to have two copies of supeuser installed on my phone (one from the previous successful rooting and one from my current attempts) - is that a problem? I can't seem to get rid of them (chicken and egg - need root to remove APK)...
Huh? Superuser? Use SuperSU. Here, check this thread. http://forum.xda-developers.com/showthread.php?t=1538053 - the flashable zip is on the first post. Now, what you should do is, while on a custom recovery, 'adb shell', mount /system rw, delete traces of previous su zips, and then flash SuperSU zip.
a maguro wrote this.
Thanks man - that did it!
ChrisG12 said:
Thanks man - that did it!
Click to expand...
Click to collapse
Please edit thread title to include [SOLVED] after [Q]; reported to mod team for closing.
a manta wrote this.
I just rooted my ATT S3 4.3. I did everything the tutorial said to do except when it got the part wherr odin reboots ur phone, i had to reboot it myself yo makr it go in cwm recovery. So once I was done rooting my phone and turned it on for the 1st time I instantly was greeted with superuser has stopped and security violations. So I tried random fixes from google and it keepa teling me there is no binary code. I can't figure out how to fix this, can anyone help me?
Which tutorial did you follow?
audit13 said:
Which tutorial did you follow?
Click to expand...
Click to collapse
I can't find it anymore. It was on this forum and it said it was for att S3 phones. Is there an area where all the ways to root are?
This is what root checker pro gave me as the results.
Super User Application Status:
SuperSU application - version 1.93 - 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 113036 1970-08-25 22:58 su
Analysis: Setuid attribute is 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:
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
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
laughingT said:
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did reboot into recovery. I remeber the files I downloaded were named clockword mod and another was called superboot with cwm. Don't k ow if that helps.
I'm having a big issue though, I had tried fixing it by flashing dif ways, now whe I try tk flash it. When it loads up in download mode, my phone turns off or of ot doesn't do that, after I flash my phone and it reboots, it shows a red screen.
EDIT:
I just tried that root method you suggested and I still have the same issues. I don't know what to do!
EDIT 2:
I fixed it by using this site http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html. Specifically, these instructions:
Download and install the latest APK for SuperSU like MrW0lf suggested.
I was having the same exact problem (unfortunately, SuperSU has stopped), so I downloaded the latest UPDATE-SuperSU file and extract it to have supersu APK, put it on my SD card in my phone and installed it from there.
It was strange because the version that was already on my phone was the same 1.89 version that I downloaded, but regardless, when I clicked on the APK, it saw it as an update, it asked to disabled knox, and worked like a charm.
- See more at: http://www.w0lfdroid.com/2013/12/Fi...y-S3-S4-Note2-Note3.html#sthash.0nlj3XHO.dpuf
PS: this is the root method I had 1st followed, http://forum.xda-developers.com/showthread.php?t=1726960
I did a half ass job in trying to unroot. I deleted the su binary and superuser.apk file but didn't restore the stock ROM or recovery or boot before deleted them. I didn't wipe disk and relock the bootloader either, I just stopped there.
After that, my ROM, Viperx 3.7.7 can still grant apps permission to access root, albeit a little buggy (can't grant for one time but must choose either 10min of access or forever). But after I update to Viper 4.1.1 or CM 12, that ability is lost completely and CWM start asking me if I wanted to fix root upon exit. Right now I can still access root and do things to its file (maybe) but I can't grant any permission, root checker told me my root is not properly installed and like I said above, CWM keep asking me and what I choose (Yes or No) makes no difference.
Anyone got a clue about what I should do? I've already tried to reflash the su binary from the onexroot zip file available on this forum, It didn't do anything.
Updated: I still have my su binary, but I don't have any superuser.apk in system/app
And I can't deleted or do anything to the files in root dir.