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.

[Q] ADB device not found

Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...

Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app

Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.

Hi,
You're on Windows? If yes which version?

Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.

Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4

Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.

I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.

[Q] HTC One Half Bricked?

So, pretty much the title. I'm pretty noobish when it comes to phones, and think i messed it up. I'm currently with Rogers, and what i did i unlocked it, and put the Google Play edition onto my phone, because i personally did not like the Blink Feed. So me being awful with phones, after the update came out for the Google Play 4.4 KitKat, I decided to update the firmware... Not realizing that it would mess my phone up... I have no rom to go back too, which would of probably saved this whole problem... Also another huge problem, my Phone does not want to be found by my computer... I would of just easily fixed it by flashing another rom, but i can't because it doesn't want to be recognized. Basically my phone right now boots up half way to the Google Logo, and then goes to a blue/green screen and stays there till i decide to turn it off.. I can get into bootloader, but that's as far much as i can do... Any help would be awesome, because i'm lost as far as it goes and decided to come here to post about it... Considering this is the best website for phones and whatnot... Thanks ahead of time guys!!

BUMP!

You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)

SaHiLzZ said:
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
Click to expand...
Click to collapse
The thing is, the only time it can recognize it is when it is in fastboot, it says it's connected but it on the phone but doesn't connect to the computer :/

Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?

SaHiLzZ said:
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
Click to expand...
Click to collapse
Sorry for super late reply, fell asleep. Also Windows 7, tried installing different drivers to no avail

Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..

SaHiLzZ said:
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
Click to expand...
Click to collapse
Says it's connected, [FastBoot USB] Also says it's connected via Device Manager, http://gyazo.com/f9dfe5d0ab3f184f3b085d776e765d2c But, does not appear in my computer. http://gyazo.com/b23dc0defe0d657a7a4aab8abcc2866e Wish i could get a picture of my phone as well, but you know

Fastboot not working on my HTC One

Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!

Which version of Win are you running?
And, if you open the device manager how is recognized the phone?

Fastboot usb is normal, try using win 7 instead of win 8, I had the same problem
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery

Arcellano said:
Hi all,
I can't get my phone recognised when it's in fastboot mode. I tried all the drivers i found (my PC runs W8.1), with or without HTC Sync installed, with different adb and fastboot aplications but still nothing. Also I noticed that when I connect my phone to the PC in fastboot mode it in the beginning shows "FASTBOOT" and then, if I go up/down, it starts showing "FASTBOOT USB".
I don't know how to fix this. Can someone help me please?
Thank you all very much!
Click to expand...
Click to collapse
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
The only for sure way to get fastboot working on windows 8.1 is to update your hboot to 1.55.000 and up or the hboot 1.54.000 from the GPE from the Android 4.4 update. Once your on these hboot fastboot and adb work fine in windows 8.1 x86 or x64.
the dark bootloader files here are all updated to the newer version hboot
http://www.htc1guru.com/downloads/firmware-downloads/
You need S-off for these to work
Click to expand...
Click to collapse

Guich said:
Which version of Win are you running?
And, if you open the device manager how is recognized the phone?
Click to expand...
Click to collapse
Hi, my PC runs Windows 8.1 32bit. If my phone is normally on, my PC recognizes it as "Android Devices", My HTC or something similar. If my phone is in the bootloader my device manager recognised it as unknown USB device, with error 43.

clsA said:
I guess I'll paste my answer from the last post asking the same question
You'll need another PC to make it work.
Click to expand...
Click to collapse
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.

Arcellano said:
So you're saying I need to upload my HBoot to 1.55 and then it will work? The problem is that I can't get my One S-Off if my PC doesn't recognize it when in fastboot mode, so I guess I can't upload the HBoot yet.
Click to expand...
Click to collapse
you can RUU to version 3.xx.xxx.x to get the new hboot
find your phones RUU here>> http://forum.xda-developers.com/showthread.php?t=2428276

ADB Works but Fastboot does not...
So tonight I decided to venture into the idea of pushing the GPE on to my HTC One. I unlocked the bootloader and got S-Off (The 2 prerequisites for the conversion). I loaded TWRP for the recovery mod and rooted it by installing SuperUser. Then came time to push the GPE RUU over to the phone using these instructions: http://forum.xda-developers.com/showthread.php?t=2358781
Before I pushed the ROM my bootloader screen looked like this: https://www.dropbox.com/s/r7jodkxh8gq7epy/2014-04-22 21.07.51.jpg
When I was pushing it, everything stalled, and it disconnected from the computer. I now no longer have any access to the Fastboot, my computer is saying that the usb device is not recognized by my computer and my bootloader screen now looks like this: https://www.dropbox.com/s/0zap1jiykeqrd9a/2014-04-23 00.00.06.jpg
If I boot into Android, it boots up in the stock AT&T version and I still have ADB control over USB. I run the prompt [ADB reboot bootloader] and it does what it is supposed to, boots it up to the bootloader, but again it is the broken version that I have no access to fastboot with.
I can still load up TWRP and run anything in there that I need. I have tried clearing all caches and doing factory resets with no success. I am at a loss and everything I am finding online is telling me that it is a driver issue or windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Any help here would be amazing. The phone still works as a phone which is a plus, but I would really like to be able to either successfully load the Google Play Edition on it or get everything back to stock for warranty reasons. Thanks so much for your help in advance!! I look forward to trying some new solutions soon!

zpeverman said:
windows 8.1 issue, but if that were the case, then why would I have had Fastbook access before attempting to push the GPE ROM?
Click to expand...
Click to collapse
It's because you're original hboot was 1.55 which works with Win 8.1, but after the first flash hboot got downgraded and therefore "broke" for Win8.1.
Use a Windows 7 PC to complete the conversion, or if you don't have access to one, you can make an Ubuntu Live USB (you can check in my guide under the FAQs how to do that).
and do not ever go S-On again!!!!

@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app

zpeverman said:
@nkk71 Is there any way to get the hboot back to 1.55? I did get it working last night by accident. I used my wife's Win7 computer just to try a different USB port, didn't know why it fixed it but just went with it hoping to understand it later. I would however love to get my phone back to a state that I don't feel like it is broken when I load the bootloader.
Thanks for the response though. Glad I at least understand what happened to it.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes their are newer black GPE firmware that work look for the firmware at htc1guru in my sig.
I was also able to get fastboot working on windows 8.1 with this fix
http://forum.xda-developers.com/showthread.php?p=49131915
use the old dirty method described

Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help

abedi75 said:
Hello,
My Htc One M7 when connected to PC with Windows 7 shows fastboot ac instead of fastboot usb, any idea what could be the problem
My M8 get connected properly & shows fastboot usb
can someone help
Click to expand...
Click to collapse
Probably a bad usb cabpe or usb port. fastboot ac = phone only get power, no data connection.

Strange Fastboot behaviour

Hello,
A long time stalker of these forums, but first time poster so apologies if this is in the wrong place.
I'm quite experienced with rooting and installing custom roms, my M7 is currently running CM and I've got the scars from bricking devices over the years! However this current problem has got me stumped and I wonder if anyone here has seen something similar.
I'm running the latest skinny Android fastboot / adb files. If I boot my phone into recovery > fastboot while connected to my pc everything is wonderful, fastboot devices can see the phone. However if I reboot the phone to desktop, fastboot on my PC doesn't do anything. I've tried different HTC drivers, USB cables and ports etc.
The strange thing is it was fine a few months ago!
Any thoughts?
Thanks,
Ben

B3ndy said:
Hello,
A long time stalker of these forums, but first time poster so apologies if this is in the wrong place.
I'm quite experienced with rooting and installing custom roms, my M7 is currently running CM and I've got the scars from bricking devices over the years! However this current problem has got me stumped and I wonder if anyone here has seen something similar.
I'm running the latest skinny Android fastboot / adb files. If I boot my phone into recovery > fastboot while connected to my pc everything is wonderful, fastboot devices can see the phone. However if I reboot the phone to desktop, fastboot on my PC doesn't do anything. I've tried different HTC drivers, USB cables and ports etc.
The strange thing is it was fine a few months ago!
Any thoughts?
Thanks,
Ben
Click to expand...
Click to collapse
You have enabled USB debugging on your Phone?

Justin2003 said:
You have enabled USB debugging on your Phone?
Click to expand...
Click to collapse
Hey Justin, thanks for the reply.
Yes, USB debugging is enabled.

B3ndy said:
Hey Justin, thanks for the reply.
Yes, USB debugging is enabled.
Click to expand...
Click to collapse
I should also add when the device is plugged into the PC, Windows recognises it ok.

B3ndy said:
I should also add when the device is plugged into the PC, Windows recognises it ok.
Click to expand...
Click to collapse
bootloader: you can use fastboot commands (no adb)
custom recovery: you can use adb commands (no fastboot)
booted up ROM + USB debugging: you can use adb commands (no fastboot)

Just a quick update, solved!
It was actually something up with the HTC drivers, I'd noticed that HTC Sync had updated (never use that thing anyway). Quickly nuked all mention from the machine, reinstalled drivers via the brilliant HTC One Toolbox and everything is good again.
Interestingly I also had some problems getting S-Off on this device but Firewater seems to have solved it as well.
Thanks for the replies!
Ben