last time i rooted my phone using binary's method and im still using stock rom.now i want to unroot it but it gives me this error.
x) Unroot
Make a choice: x
Really (y/n) ?y
2642 KB/s (1085140 bytes in 0.401s)
rm failed for /system/bin/su, No such file or directory
rm failed for /system/app/Superuser.apk, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
i have superuser installed and it's enabled
dylan992 said:
last time i rooted my phone using binary's method and im still using stock rom.now i want to unroot it but it gives me this error.
x) Unroot
Make a choice: x
Really (y/n) ?y
2642 KB/s (1085140 bytes in 0.401s)
rm failed for /system/bin/su, No such file or directory
rm failed for /system/app/Superuser.apk, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
i have superuser installed and it's enabled
Click to expand...
Click to collapse
Theres an app called ota rootkeeper. Try it out
Related
Everytime I run the .bat for the my prompt reads Your device is a Nook Tablet meaning we can continue!
[/quote]Now, just making sure you WANT to root it!
[-] Cannot copy boomsh.: Permission denied
Installing superuser and su...
2313 KB/s (843503 bytes in 0.356s)
1819 KB/s (22364 bytes in 0.012s)
failed to copy 'root-files\su' to '/system/bin/su': Read-only file system
Installing and setting up busybox...
failed to copy 'root-files\busybox' to '/system/xbin//busybox': Read-only file s
ystem
1963 KB/s (12066 bytes in 0.006s)
[quote/]
I tried to root when in version 1.4.0 then downgraded back to 1.4.0 when the OTA hit and tried once more only to get the same error. Tried to cmod the entire system folder from both an adb shell and android terminal. any ideas guy?
Do you have USB Debugging enabled (in both boxes)?
Yea, its shows my device in the beginning of the script. =\
I think you need to run the runmefirst. bat then apply the other .bat to root
Sent from my LG GT540 Swift using XDA App
Did the runmefirst.bat.
logoguy said:
Did the runmefirst.bat.
Click to expand...
Click to collapse
ok then if that didn't work then its 100% drivers issue check this its the best step by step tutorial i have found , check step 3 or better the whole tut
Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running zergrush)...
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
I assume this is this the one click root NilsP posted? That one worked great for me. Make sure USB debugging is enabled and you have checked the box under applications to enable use of non-market apps.
If you continue to have issues, flash the AmonRa recovery via fastboot and under Developer Options you can choose to install superuser while in recovery.
You will have to flash Amon Ra recovery through fastboot. There is info about that in development thread. Read through first few pages of Amon Ra thread. Once you have recovery, boot it up from hboot, and then install su and superuser from development section in Amon Ra recovery. The only confusing part for me was preparing to flash Amon Ra thru Windows command prompt due to my inexperience. PM me for further assistance. Good luck. One click does not work for the OTA.
Thanks guys...wish me luck
Kbartley77 said:
Thanks guys...wish me luck
Click to expand...
Click to collapse
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Kbartley77 said:
Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running zergrush)...
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
Click to expand...
Click to collapse
if you can't root using oneclickroot,
flash AmonRA recovery using cleanflash
then install su and superuser under Developer menu under AmonRA recovery.
Amonra Recovery: http://forum.xda-developers.com/showthread.php?t=1339679
Cleanflash: http://forum.xda-developers.com/showthread.php?t=1416791
Same Issue
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
dnvm said:
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
Click to expand...
Click to collapse
go here
http://forum.xda-developers.com/showthread.php?t=1466474
Im in the same boat.. I took the ota update and now i cant root. I tried going into cmd to flash the recovery img, and it says "cannot load recovery img" I also tried using clean flash 1.0 and i get the same thing "cannot load" and than the phone just boots in fastboot.. What could be the problem?
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Kbartley77 said:
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Click to expand...
Click to collapse
c:/Android>fastboot flash recovery (name of recovery).img
Not recovery.img
Sent from my ADR6425LVW using xda premium
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Kbartley77 said:
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Click to expand...
Click to collapse
Developer menu if your trying to achieve root. Then there is an option to install su and superuser. Select that then after that is done immediately reboot. You may or may not still have to download the superuser off the market and update it. I didn't but alot of people reported having to do so.
I'm ROOTED!!!! Thank you everyone for your time and patience!!!
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You have to do this in Cmd, while the phone is in fastboot
Sent from my DROID RAZR using XDA App
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You run those commands on your PC in a command/DOS prompt.
Hi,
I went back to factory settings using CWM to try to root again and update ota to .62, but after I went back to factory I can't get it to root anymore
I am trying to use DooMLoRD_v4_ROOT-zergRush-busybox-su
This is what I get:
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir: permission denied
--- cleaning
rm: permission denied
--- pushing zergRush
461 KB/s (23060 bytes in 0.048s)
--- correcting permissions
chmod: permission denied
--- executing zergRush
./data/local/tmp/zergRush: permission denied
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2945 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
chmod: permission denied
--- remounting /system
/data/local/tmp/busybox: permission denied
--- checking free space on /system
87 KB/s (439 bytes in 0.004s)
chmod: permission denied
./data/local/tmp/makespace: permission denied
--- copying busybox to /system/xbin/
dd: permission denied
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
chmod: permission denied
--- installing busybox
/system/xbin/busybox: not found
rm: permission denied
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
chmod: permission denied
--- correcting symlinks
rm: permission denied
ln: permission denied
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm: permission denied
--- rebooting
ALL DONE!!!
Any ideas?
USB Debugging turned on? Unknown sources allowed? ADB drivers properly installed?
usb debugging was on, unknown sources allowed and I could adb shell... so I guess no problem there either.
For now I recovered the cwm backup I did before I tried going back to 'new'. 58 (to root and update to. 62)
I'll probably start trying again tomorrow.
Just to be clear I now reverted to a rooted .58
But I would like to be able to start over with. 58 (been messing around to much ), root it and update to. 62 (hoping to keep root).
I do have cwm installed, but no unlocked bootloader
All tips are welcome
Thanks
I tried to use a .58 firmware file and flashtool yesterday, but got problems with drivers.
Where can I get the correct driver for sk17i?
TIA
I got one step further using flashtool on my work pc, it rooted, but when trying to update ota, it gives 'could not install new software'...
It worked
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Time for a backup with cwm
Which got apparently uninstalled when using flashtool to go to .58 ... that's a lesson learned and probably logical,so I reinstalled it from the market ...
Strangely cwm installer had a force closed, but it didn't seem to affect anything.
Now for OTA update to .62 ... Done
Root still there? Yes
time for another CWM backup...
And I can go about messing with it again, freezing/uninstalling apps...
Thanks for the help
angelofhope said:
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Click to expand...
Click to collapse
Phone is restarted again to flashmode
That's why you have to disconnect and power up.
angelofhope said:
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Click to expand...
Click to collapse
Phone has to be turned on in order to root
Just turn it on, make sure USB debugging and Unknown Sources are allowed and leave it on home screen for example.
Today i saw Bin4ry's root method for ICS and JB devices, so i thought i give it a try.
Since i cant yet post on dev threads, i started this thread so people try it themselves, and maybe post findings here and on Bin4ry's original thread.
All i got was
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3532 KB/s (1085140 bytes in 0.300s)
2183 KB/s (22364 bytes in 0.010s)
3432 KB/s (843503 bytes in 0.240s)
^CTerminate batch job (Y/N)? n
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press any key to continue . . .
!^CTerminate batch job (Y/N)? n
At this point, first run i said yes, and batch just closed.
Second run, i said no, so the rest came up. Phone rebooted twice, never asked me to press anything, and no root.
AndStuff said:
Today i saw Bin4ry's root method for ICS and JB devices, so i thought i give it a try.
Since i cant yet post on dev threads, i started this thread so people try it themselves, and maybe post findings here and on Bin4ry's original thread.
All i got was
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3532 KB/s (1085140 bytes in 0.300s)
2183 KB/s (22364 bytes in 0.010s)
3432 KB/s (843503 bytes in 0.240s)
^CTerminate batch job (Y/N)? n
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press any key to continue . . .
!^CTerminate batch job (Y/N)? n
At this point, first run i said yes, and batch just closed.
Second run, i said no, so the rest came up. Phone rebooted twice, never asked me to press anything, and no root.
Click to expand...
Click to collapse
I think that method just works on some models.
Try this method: http://talk.sonymobile.com/thread/41119. Works for me
By the way: I have ICS 4.1.B.0.587 firmware
I know about this method, but i don't wanna flash roms etc.
(.587 on mini pro? if yes info!)
AndStuff said:
I know about this method, but i don't wanna flash roms etc.
(.587 on mini pro? if yes info!)
Click to expand...
Click to collapse
.587 isn't released yet for mini pro, you will have to wait. Not sure if/when we will get it!
You will have to downgrad the your firmware if you want to root ics or a gingerbread firmware like 4.0.2.A.0.62 or.69. Check out my signature, see your firmware version and decide if you want to root, if yes follow the steps
Bin4ry's himself said that it doesn't work for se xperias.
the suggested way to root from above works. I used the unlocked bootloader to directly flash cm.
Sent from my MK16i using xda premium
I can't unroot using bin4ry method
it shows like this
"x) Unroot
Make a choice: x
Really (y/n) ?y
4587 KB/s (1085140 bytes in 0.231s)
rm failed for /system/bin/su, No such file or directory
rm failed for /system/app/Superuser.apk, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry"
please help...
Is USB Debugging on, on the phone?
You're not running the executable on the computer with admin rights, right?