Root Stuck at the OneClickRoot step, please help!

B

budmonster

Guest
I unlocked my bootloader following all the directions form HTC. I them followed these to get perm root:

Permanently Rooting Your HTC Rezound With One Click
Now that the hard part's over, here's how you go about getting permanent root for your Rezound.

Again, make sure you have USB debugging enabled (Settings -> Applications -> Development)
Connect your phone to your computer
Double-click the OneClickRoot.bat file extracted from the 1-Click Root archive downloaded earlier.
Press any key to start the rooting process when prompted



The first time nothing happend and it just sat there and hanged. I exited and tried again now I get this:

Press any key to continue . . .
--- WAITING FOR DEVICE ---
The system cannot find the path specified.
--- Device Connected ---
Checking for previous attempts...
The system cannot find the path specified.
Pushing Zergrush...
The system cannot find the path specified.
Setting Permissions...
The system cannot find the path specified.
Gaining Perm Root (Aka running zergrush)...
The system cannot find the path specified.
--- WAITING FOR DEVICE ---
The system cannot find the path specified.
--- Device Connected ---
Pushing Busybox
The system cannot find the path specified.
Setting Permissions...
The system cannot find the path specified.
Remounting System...
The system cannot find the path specified.
Coping Busybox to /system/xbin/...
The system cannot find the path specified.
Installing Busybox...
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Installing Superuser...
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Removing tools That Was Pushed To Data...
The system cannot find the path specified.
Congrats You Are Now Perm Rooted...
Press any key to continue . . .

Whats going on? Am I rooted now?

I then tried this again after, I doubled clicked the .bat file and got this, just sits here:
Press any key to continue . . .
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *

I made sure HTC Sync is not on, phone is in charge mode. oneclickroot is here: C:\Android\OneClickRoot_1.1
 

Padron26

Well-Known Member
I'm getting the same thing, but I'm not unlocked.

Windows7 64 bit

edit it works with windows 7 32 bit until i reboot then i am no longer rooted
 

MrSmith317

Android Enthusiast
bud...make sure your phone has USB debugging turned on. The first set of errors were due to it not being able to find the script(usually when you run the script from inside the zip file instead of uncompressing it). So Checklist...
PC:
HTC USB Drivers installed
HTC Sync not running/uninstalled
OneClick Package uncompressed(not zipped)

Phone:
USB Charge mode only
USB Debugging on
 

droid24

Lurker
bud...make sure your phone has USB debugging turned on. The first set of errors were due to it not being able to find the script(usually when you run the script from inside the zip file instead of uncompressing it). So Checklist...
PC:
HTC USB Drivers installed
HTC Sync not running/uninstalled
OneClick Package uncompressed(not zipped)

Phone:
USB Charge mode only
USB Debugging on

*I was also having the exact problem as mentioned. To fix this, while device is connected exactly as described above, *Toggle USB debugging (on to OFF and back on) then run script. Worked for me perfectly.
 

Bob Cat

Careful, They're sharp!!
So Checklist...
PC:
HTC USB Drivers installed
HTC Sync not running/uninstalled
OneClick Package uncompressed(not zipped)

Phone:
USB Charge mode only
USB Debugging on

I followed your check list, it starts, gets to *daemon started successfully* and that's as far as she goes. What am I missing?


Edit: Just tried again and it only gets to --- Waiting for Device ---

Edit Edit: Droid24 up there had the answer. Toggling debugging fixed it.
 
Top