Hi,
Today I've unlocked, flashed Paul's CWM recovery, and then rooted my HTC One S.
I've installed SU and Busybox but Titanium Backup still says it couldn't get root privileges. What am I doing wrong?
reupugi
try to update the binarys in SU
if that fails re flash the root.zip file
happened to me yesterday
Thanx for the quick answer.
When I try to update the su binarys it fails saying it "failed to find currently installed su binery...
What does that mean?
uninstall and reinstall the SU app
or reflash the root file as this is supposed to install SU on your device
Well, last night I spent hours trying to uninstall and reinstall su. I've also flashed Paul's root twice but still no luck.. I've tried to install busybox with two different apps but still no luck... Is there any way to roll back everything and start over?
you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1
So I encountered a similar problem (https://github.com/ChainsDD/Superuser/issues/46).
Edit: Of-course it'd make more sense to confirm if this could be the problem first...
Code:
$ adb pull /system/framework/framework.odex
$ strings framework.odex | grep HtcIntentFlag
@test_code: getHtcIntentFlag:
@test_code: setHtcIntentFlag:
addHtcIntentFlag
getHtcIntentFlag
setHtcIntentFlag
I patched the su binary in accordance with the change I observed in the framework and that works for me.
Could the OP please try the following su binary:-
* http://revolutionary.io/one-s/su (md5sum: 83fdeaef210225d7361e6c8eb63bae96)
This will need to pushed from recovery, something like (after ensuring /system is mounted):-
Code:
$ adb push su /system/bin/su
$ adb shell chown root /system/bin/su
$ adb shell chgrp root /system/bin/su
$ adb shell chmod 6755 /system/bin/su
(You can obviously push to xbin/ if you have the appropriate symlink set-up in bin/, etc...etc...)
zylith said:
you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1
Click to expand...
Click to collapse
I've flashed su through Paul's cwm, following steps 1,2 and 3. I did have a problem entering bootloader through shutting sown - power+vol down. For some reason that didn't work, numerous times, so I got into the bootloader through terminal (mac) and command prompt (win 7).
Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards
reikanou said:
Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards
Click to expand...
Click to collapse
Hi, i am a new tf300t user. It seems that nobody can root latest stock 4.2 with motochopper and i read that all failed with rootkeeper as well. I bought my tf a week ago and it was with the latest update, so i coundt root it. I downloaded from asus website the previous stock firmware (V10.6.1.15.3 for WW SKU which is my tablet), extracted it to internal and i got a notification for downgrade. I did it and 10 min later i rooted with motochopper. Then i opened su and updated binaries. Installed voodoo ota rootkeeper, backed up root and temporarly unrooted. I then updated again via OTA notification (only 50mb) to latest fw and i ota rootkeeper managed to restore root successfully. So im on latest with root access.
H,
Thanks for you reply i will try this and if it doesn't work i forgot root it was just to recover a file and application to recover need to be root.
Thanks again.
Bregards
Where does supersu search for the su binary. I am stuck with the cannot find su manually reroot message. This was after updating a working rooted system to the latest supersu after it asked me to. The only su on the system is in /system/xbin/su there is no su in /system/bin and /system/sbin does not exist.
Can I manually reroot by using adb to create a link from xbin/su to bin/su?
I cannot find any info on "manually rerouting" that says anything but reinstall the latest zip. Which is what I did.
Help!
Roger
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4
shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2
buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:
i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
I just updated my Super Su and it prompted me afterwards to update my SU bianry which i tried to do but the feed back was SU binary update failed. Kindly help me out.
[email protected] said:
I just updated my Super Su and it prompted me afterwards to update my SU bianry which i tried to do but the feed back was SU binary update failed. Kindly help me out.
Click to expand...
Click to collapse
you can try to reinstall from scratch, directly from SuperSU if you can enter into the apps.
Otherwise better to flash .zip package under recovery.
Hope it helps.