Rencently, my phone update to the ICS4.0.4 ROM via official rom。
I tryed to root my device use a 4.0.3 root tool (which worked fine with official 4.0.3rom),but it doesnt work.(2.3.6 is doesnt work too).
BOOT:locked
Reproduce
1.Flash the signed su update pack.
2.run the root tool.
the problem seems su command cant run use "su -c"
after update su zip pack ,I try run su use "adb shell su" in bat file , the # is appeared ,but the terminal freezed,the cursor flash continued,i can't input anythiny anymore,so other commane can't be run too.
Any ideas?
I don't believe there is a way to 1 click root 4.0.4 yet. It's a brand new update so the tools may not work.
The only way I could think of to keeping your root would be to downgrade back and the download "Voodoo OTA" root keeper and "Root Check" from the android market.
Voodoo is an app that creates files in your phone that will store the su- binary and restore it when you update your phone.
Root Check will do just as it says: Check to see if your phone is rooted.
So you will either have to wait for the 1 click root to be updated. Or Downgrade an try again.
Hope this helps!
Related
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
Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?
Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.
I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.
new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...
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 have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time
se7encircles said:
I have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time
Click to expand...
Click to collapse
I've tried to root the ZTE Whirl also with the same results as you. It is my understanding that it cannot be permanently rooted unless the write protection is disabled. I read on other forums that this was done on the HTC One X and Motorola MOTOX with a recovery installed zip. I don't know if the file in the zip "wp_mod.ko" would work on the ZTE Whirl and without access to the RUU, I really don't know how an update zip could be made. I'm no developer but this is my understanding from my research.
se7encircles said:
I have tried to root this phone it does root but it is only temperorary it goes away after reboot.
I got busyinstalled in the /system/bin but no SU
The system is RO
I have tried this code to no avail
busybox mount-o remount,rw /dev/block/mmcblk0p18
cant be found in proc/mounts
busybox dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
permmsion denied
I used framaroot and it said sucess then it said binary cant be installed any help would be great a thnk you ahead of time
Click to expand...
Click to collapse
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:
Daniel Dunhill said:
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:
Click to expand...
Click to collapse
Vroot cannot root this device at all. Framaroot can root device. The problem is that the system is write protected. In other words, it is temporary until you reboot etc. I have found that if I already have Supersu.apk installed when I root that I will have super user permissions etc., however, when I open Supersu and attempt to update binaries, it fails and root is immediately lost. I have also rooted and used Total commander to remount r/w and could paste files to system directories etc. but SuperSU still failed to update and lost root. When I attempt to install SuperSU or any zip via stock recovery, it verifies etc but in the end aborts installation. I am beginning to thing that its not just write protected but active defense against any changes to system from stock. BTW, you don't have to drain the battery to root: When I loose root (after restart etc.) I uninstall Framaroot apk, shut down device (not restart), start device, install Framaroot and am able to root with Gandalf option.
Bottom line: This write protection or whatever it is needs to be removed or disabled for root to be permanent.
Daniel Dunhill said:
Download Vroot.. turn on USB Debugging..and tick on usb debugging to active it on your phone setting/developer option
connect your phone to pc..and wait untill it detect..click root...and it will reboot..done..only one click root..i use this already 2 year..work find..if this help..press thank button :laugh::good::laugh:
Click to expand...
Click to collapse
Try using pootdebug.apk
I originally rooted my LG Vortex (2.2.1) by flashing the su-bin-3.1.1-arm-signed.zip binary within the ArmonRA recovery. Somehow my root apps are no longer gaining root so I'm trying to use the Universal AIO Flasher Tool 1.4 beta to unroot before reflashing the root.
However, the AIO Flasher Tool's unroot process is stuck at ".../adb shell rm /system/xbin/su"
How do I safely get out of this process? Thanks.
OK, I took a chance and hit the Reboot button in AIO and was taken to RA recovery where I rebooted. Superuser app icon was still present and it pointed to superuser3b4.apk, and indicated that no superuser binary was present.
I flashed the SU binary zip, rebooted and gained root. Found that both superuser3b4.apk and superuser3.1.3 were installed in /system/app.
I used the Terminal Emulator to remove superuser3b4.apk. After I rebooted, the superuser3.1.3 icon displayed in the apps menu. All seems back to normal for now.