Database Develop

[Q] HTC One fastboot devices returns blank

Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.

zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.

syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx

are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems

Is your phone actually in fastboot mode?

Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"

BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.

skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?

zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window

hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!

zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else

As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now

zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC

try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?

MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.

zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first

zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info

MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks

MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?

Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.

Phone won't connect to HTC Sync or adb

Got my phone about a week ago & got pretty bored of it so I wanted to root it and get a different ROM going. For some reason, I can't get the phone to connect to HTC Sync Manager though I updated the drivers. Any time the phone is switched into USB debugging, My HTC drivers fail to install. I have no idea how to solve this problem. Also when trying to get the Token ID using the command prompt, the device doesn't show up after using the command adb devices either. Need help please.

In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC

bigdaddy619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.

HurtMeSole said:
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
Click to expand...
Click to collapse
Windows 8.1?

bigdaddy619 said:
Windows 8.1?
Click to expand...
Click to collapse
No, Windows 7, 64-bit.

HurtMeSole said:
No, Windows 7, 64-bit.
Click to expand...
Click to collapse
Check PM

i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again

trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.

HurtMeSole said:
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
Click to expand...
Click to collapse
Same problem here with an HTC One Mini. Its driving me mad!:silly:

trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
Strangely enough, I literally just tried it on a different computer and everything worked exactly as it was supposed to. I had 3 computers in my home, none of which worked but got to work and the laptop they gave me worked just fine. Then I got on my gf's Mac and it went mostly smooth (even though it was difficult not being as familiar with the OS). My advice is do everything you're doing on a different computer until you see it without the ! in the device manager.

Boblud said:
Same problem here with an HTC One Mini. Its driving me mad!:silly:
Click to expand...
Click to collapse
Should try using a different computer. Worked for me after trying several computers.

BD619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
My experience may be helpful. I had no ADB driver, but Composite USB seemed to work. However, the driver install crashed. I needed to open my phone and answer the dialogs on my phone while the driver was installing. After that, everything is hunky-dorry (I know, showing my age).

I was having the same problem until I UNCHECKED the USB debugging mode and reconnected the phone to the computer. Drivers reinstalled and HTC Sync Manager (not HTC Sync--different program) recognized the phone. I had to answer dialogue on phone and then the USB debugging mode status changed itself to enabled. It's all working now, after hours of fiddling.

Unknown USB Device (Device Descriptor Request Failed)

I am having issues with my Nexus 6. I am unable to get it to connect to any computer. Windows says the device is malfunctioning, but it charges okay. Windows gives the error "Device descriptor request has failed." It doesn't matter if I'm booted, in fastboot, or have the phone off, it gives that error.
What I have tried:
Toggled USB debugging, MTP, and PTP.
Nexus Root Toolkit to try to install the drivers
15 Second ADB Installer by Snoop05
Alternate drivers (Naked, Generic, PDA).
Each time I have tried new drivers, I have checked to uninstall anything using USBDeview.
Tried "Updating drivers"
Tried three different Windows machines.
Tried different USB cables
USB 2.0 and USB 3.0 ports
Cleared cache partition
I think I am down to two things: Factory reset or draining my battery all the way and letting the hardware reset itself. I am not confident that factory resetting it will work since this same message pops up in the bootloader.
I have researched the hell out of this and one person in this section was having similar issues but got it working when plugging it into their USB 3.0 port. If those last two things do not work, then I don't know how the hell I'm going to lock the bootloader to get it worked on--that's the only thing I have done to it as far as modification wise (/system is stock, no root).
Any help is greatly appreciated. This is so frustrating since using USB is our way of working on these damn things. If I could get root without having to use USB, then I could easily lock the bootloader back.

Does anyone know how to re-lock the bootloader without root or using USB? At least I could have it locked so I can RMA it.

In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.

bluh5d said:
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
Click to expand...
Click to collapse
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.

dijit4l said:
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
Click to expand...
Click to collapse
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...

right click the file then go to update driver than select browse my computer then at bottom select let me pick.

Tiptonian said:
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
Click to expand...
Click to collapse
Thanks for your reply. However, I have a hard time thinking that three Windows machines are experiencing the same thing. I have successfully gotten it connected before the 5.0.1 update to transfer ringtones. I even booted into Linux Mint and couldn't get it to connect either. It's like the controller is bad but it can still charge.
Also, I have followed every direction on your link at least twice already.
bluh5d said:
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Click to expand...
Click to collapse
Thanks for your suggestion. I have tried this and Windows refuses to use the proper drivers. It argues they aren't for 64-bit OS, but they have worked in the past. I almost got it to use some Samsung drivers, but after it installed, no change. The device is not reporting the details it needs to convey to the computer to start a proper driver setup.

I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.

HotInEER said:
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
Click to expand...
Click to collapse
To me, it sounds like you have a glimmer of hope. Have you tried a different computer? If you don't have a different computer handy, boot Linux from a flash drive and install fastboot and adb.

Device not found in adb sideload or recovery trying to install 5.1 otc

So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......

Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.

A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app

Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.

tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.

z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....

Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.

I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!

Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app

I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....

I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.

Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this

got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked

Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.

This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!

A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.

Fastboot "waiting for device"

I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app

Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.

This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.

Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.

wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?

MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.

For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!

chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.

Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!

wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?

okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?