• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stuck on "Waiting for device" with Kingo Root (HTC One V)

P

patrio

Newbie
The phone is an HTC One V. I'm using Windows 10 (via Parallels on my Macbook Pro).

It's been stuck on "Waiting for device" for 2 hours. Screenshot below.

Nothing has happened on the phone itself. It's plugged in of course but it hasn't initiated any sort of thing related to rooting.

I don't know what to do. I've seen threads online where had similar problems and were told to make sure fastboot is disabled in settings (already did that) and to make sure USB debugging is checked (already did that).

I'm also using its original USB cable.

Could the fact my Macbook has USB 3.0 ports instead of 2.0 really be the issue? I saw someone claim this is another thread.


mc5a8cA.png
 
patrio said:
The phone is an HTC One V. I'm using Windows 10 (via Parallels on my Macbook Pro).

It's been stuck on "Waiting for device" for 2 hours. Screenshot below.

Nothing has happened on the phone itself. It's plugged in of course but it hasn't initiated any sort of thing related to rooting.

I don't know what to do. I've seen threads online where had similar problems and were told to make sure fastboot is disabled in settings (already did that) and to make sure USB debugging is checked (already did that).

I'm also using its original USB cable.

Could the fact my Macbook has USB 3.0 ports instead of 2.0 really be the issue? I saw someone claim this is another thread.

If i was you i would just switch back to the Mac side. Then unlock the bootloader, flash a custom recovery and flash SuperSU.

3.0 ports might be a problem but in fastboot on the Mac side, you should get a response. If not well then it maybe the ports. Sorry i've never used Parallels i imagine it's like Bootcamp which i have used.


mc5a8cA.png
Click to expand...
 
James L said:
If i was you i would just switch back to the Mac side. Then unlock the bootloader, flash a custom recovery and flash SuperSU.
Click to expand...

I ended up unplugging the phone and ending the attempt at rooting it. Phone seems fine but not rooted yet.

I tried it previously on Mac following this guide here: https://theunlockr.com/2012/04/24/how-to-root-htc-one-v/

But near the end when I had to enter those two commands into Terminal on my Mac, I also got 'Waiting for device'. Nothing else prior to it though. At least with my attempt on Windows with Kingo Root, it seemed like it was working and doing stuff for 15-20 mins before getting stuck on 'Waiting for device'...
I figured the issue on Mac was that it wasn't even recognizing my Android when I plugged it in (but Windows did)
 
You could unlock the bootloader, flash the recovery. Then boot twrp and sideload the file you mentioned above.
 
patrio said:
Also, I came across this guide which is for Windows: https://androidforums.com/threads/guide-how-to-root-the-htc-one-v.543850/

However in step 5b it mentions "Copy CWM-SuperSU-v0.9x.zip to your SD card." --- I don't have an SD/Micro SD card though.
Click to expand...

I decided to go with that guide. I figure I'll just copy it to the internal storage once I get to that step.

Anyway, I began following the instructions there (already did a certain portion of them)

Now I'm at part 4:

"
3) Open a command prompt and navigate to the folder where you saved the recovery image in step 1 above. Type the following command:
Code (Text):
fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img
"
Click to expand...

When it says to "navigate to the folder where you saved the recovery image in step 1", I entered:

"cd C:\Users\myusername\Downloads" since I saved it in my Downloads. Is that what I needed to do? I'm not very tech savvy when it comes to some of this stuff.

Anyway, after that, I copy & pasted what it told me to: "fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img" but I got this message:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
 
Last edited:
Are you using terminal or cmd? You can put the recovery.img wherever you want. You need to cd into the folder you have your fastboot file in.
 
James L said:
Are you using terminal or cmd? You can put the recovery.img wherever you want. You need to cd into the folder you have your fastboot file in.
Click to expand...
Command Prompt.

Ok, I cd into the folder where the fastboot file was. Then entered the first command "fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img" ---- now it says <waiting for device>... I should note that my device is in bootloader mode and with Fastboot selected.

I'm assuming something else is supposed to happen rather than <waiting for device> before I go ahead with the next step in that guide? Which is:

4) Reboot the phone back into bootloader using the following command:
Code (Text):
fastboot reboot recovery

You should see the new Recovery.
Click to expand...
 
patrio said:
Command Prompt.
D
Ok, I cd into the folder where the fastboot file was. Then entered the first command "fastboot flash recovery recovery-clockwork-5.8.4.5-primou.img" ---- now it says <waiting for device>... I should note that my device is in bootloader mode and with Fastboot selected.

I'm assuming something else is supposed to happen rather than <waiting for device> before I go ahead with the next step in that guide? Which is:
Click to expand...
Usb drivers are not installed or change cables. Just type fastboot flash recovery then drag the .img into cmd and press enter. Less typing and no errors.
 
This "waiting for device" issue has happened on my attempt to root via my Mac... and with the Kingo Root method on Windows... and now once again on Windows with the method I've been referencing above.

Seems like a matter of not recognizing the device. Or perhaps more specifically, a matter of not recognizing the device when it's in fastboot mode. I think it recognizes it in Windows when it's just in "regular" mode.

I've installed every driver I've seen recommended. Also installed HTC Sync Manager (but kept it closed since I read having it open can use problems). Also have ADBD Driver installed.

This is driving me crazy.
 
James L said:
Usb drivers are not installed or change cables. Just type fastboot flash recovery then drag the .img into cmd and press enter. Less typing and no errors.
Click to expand...

Just posted an update above. As mentioned, I've installed every driver I've seen recommended. And I don't have another cable, just this one which is the original.

And I tried to type 'fastboot flash recovery' but I think that because it's it's still "waiting for device", it won't let me type anything in Command Prompt at all. So I can't type that.
 
James L said:
I would just go back to the Mac side. No usb drivers are needed that way.
Click to expand...

Ok, I'll try that. Just a couple minutes. Although I'm anticipating I'll end back up with <waiting for device> again, but in Terminal.

I'll retry and see what happens, and report back.
 
Also found another cable. Tried it. Made no difference. Still stuck on <waiting for device>

:(:(:mad:

This is driving me crazy.
 
You're trying to do this on a Mac with Windows running as a virtual machine in Parallels? Also Windows 10 as well, is it 64bit?. I wonder if it's the USB virtualization or Win 10 causing problems. Do you have a PC you could try using instead?

Although I'm a Mac user myself, any rooting type jobs I've done in the past, I've always used a PC laptop with Win 7 32bit. Although I no longer root my Android phones these days.
 
Last edited:
mikedt said:
You're trying to do this on a Mac with Windows running as a virtual machine in Parallels? Also Windows 10 as well, is it 64bit?. I wonder if it's the USB virtualization or Win 10 causing problems. Do you have a PC you could try using instead?

Although I'm a Mac user myself, any rooting type jobs I've done in the past, I've always used a PC laptop with Win 7 32bit. Although I no longer root my Android phones these days.
Click to expand...

Yes. I've tried 2 different methods on Windows (via Parallels) but also a method on Mac as wel.

It is 64 bit Windows 10.

I do have a PC laptop I can borrow easily. I think it's running something higher than Windows 7 though.
 
I just went on the PC laptop (Windows 10), followed that guide from here https://androidforums.com/threads/guide-how-to-root-the-htc-one-v.543850/ including installing what it mentioned at the very beginning (SDK Tools, Java, Sync Manager)

But once it came time to put my phone in fastboot mode, connect via USB, I got a notification on the computer that "USB Device not recognized: One of the devices attached to this computer has malfunctioned and windows does not recognize it." --- I got this message when using Windows via Parallels as well.

Seems like it can't recognize it when it's in that mode. If the phone is just in "regular" mode then it recognizes it just fine in Windows.
 
Oh my God, I think I finally got it rooted. (edit: never mind)

The main issue seemed to be my device not being recognized when it was in fastboot mode. So I googled some stuff and came across this suggestion. It was random but it worked: https://social.technet.microsoft.co...numeration-error-code-43?forum=win10itproapps (I followed the instructions of the 4th last post in that thread where it says to copy that bolded text and create a .reg file, etc....)

Anyway, I then used Kingo Root and it didn't get stuck on 'waiting for device', and wound up saying Root Successful. Also got this screenshot here below... Yet when I went on my phone (yes I restarted it) and installed Root Checker from the Play Store... it said 'Sorry! Root access is not properly installed on this device'.

DyRpOOy.png
 
Last edited:
patrio said:
Oh my God, I think I finally got it rooted.

The main issue seemed to be my device not being recognized when it was in fastboot mode. So I googled some stuff and came across this suggestion. It was random but it worked: https://social.technet.microsoft.co...numeration-error-code-43?forum=win10itproapps (I followed the instructions of the 4th last post in that thread where it says to copy that bolded text and create a .reg file, etc....)

Anyway, I then used Kingo Root and it didn't get stuck on 'waiting for device', and wound up saying Root Successful. Also got this screenshot here below... Yet when I went on my phone (yes I restarted it) and installed Root Checker from the Play Store... it said 'Sorry! Root access is not properly installed on this device'.

DyRpOOy.png
Click to expand...
If Fastboot is working then why not just backup anything that's important to you. Then unlock the bootloader and flash Twrp and SuperSU?

The Superboot in the unlocker post doesn't seem familiar and the easiest way is to do it the right way.
 
James L said:
If Fastboot is working then why not just backup anything that's important to you. Then unlock the bootloader and flash Twrp and SuperSU?

The Superboot in the unlocker post doesn't seem familiar and the easiest way is to do it the right way.
Click to expand...

I don't have anything important on this phone to backup.

And bootloader is unlocked already. But it looks like I need a microSD in order to save the SuperSU file to the phone. I'm on the phone's browser and when I try to download the SuperSu zip https://download.chainfire.eu/204/supersu/ it says 'An SD Card is required to download ____".

I'll have to go buy a micro SD.
 
You must log in or register to reply here.
Back
Top Bottom