Database Develop

[Q] Fastboot Windows 8.1 64bit

So I've trying for 2 days straight now to get anything work in fastboot on Windows 8.1 x64 and really am out of ideas...
Fastboot devices does nothing, fastboot oem get_identifier_token just waits for devices to show up.
I connect my HTC One on my USB 3.0 port and when it is in fastboot it shows up as My HTC in device manager.
I tried many drivers but nothing seems to work. Tried installing other usb 3.0 drivers, but no luck at all...
USB 2.0 gives device enumeration failed...
Here is some more info on my device:
S-OFF
HBOOT 1.54
RADIO 4A.17.3250.14
OpenDSP v31.120.274.0617
OS 2.24.401.8
Anybody can help me?

petemt said:
So I've trying for 2 days straight now to get anything work in fastboot on Windows 8.1 x64 and really am out of ideas...
Fastboot devices does nothing, fastboot oem get_identifier_token just waits for devices to show up.
I connect my HTC One on my USB 3.0 port and when it is in fastboot it shows up as My HTC in device manager.
I tried many drivers but nothing seems to work. Tried installing other usb 3.0 drivers, but no luck at all...
USB 2.0 gives device enumeration failed...
Here is some more info on my device:
S-OFF
HBOOT 1.54
RADIO 4A.17.3250.14
OpenDSP v31.120.274.0617
OS 2.24.401.8
Anybody can help me?
Click to expand...
Click to collapse
I have the same problem. Searchng for a solution since 2 month now.

same Problem here @ Win 8.1 64-bit
S-ON
HBOOT-1.44.0000
RADIO 4.A.14.3250.13
OpenDSP-v26.120.274.0202
Anyone has news?

Need HBOOT 1.55 so update to 4.3 and you'll be good to go

I got sinless 4.3. So Can you name a rom wich you are Sure that does?
Sent from my HTC One using Tapatalk

Also had the same problem, had to use the spare laptop.... Which unfortunately now been upgraded to 8.1 as well lol...
I've installed many 4.3 ROMs and I still have hboot 1.44, could you be more specific?
Sent from my HTC One using xda app-developers app

Found a Solution:
Change USB3.0 Driver from Microsoft to Intel's Driver following this instruction: http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
NOTE: If you've an PC with Intel Processor 4th Gen, you've to read the first comment of the Instruction and do what it's said.
after this, you'll get fastboot cmds run in bootloader.
kind regards

madejackson said:
Found a Solution:
Change USB3.0 Driver from Microsoft to Intel's Driver following this instruction: http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
NOTE: If you've an PC with Intel Processor 4th Gen, you've to read the first comment of the Instruction and do what it's said.
after this, you'll get fastboot cmds run in bootloader.
kind regards
Click to expand...
Click to collapse
While this potentially holds the solution, it's some serious-level ****. I tried this in an attempt to solve the exact same problem about a month ago, and I ended up reinstalling Windows. Because my USB drivers were all ****ed up, I was unable to pull files from the system, so it was a clean install, minus all my music and games and jazz. :/
I'm pretty sure I didn't do anything wrong, so I don't know what happened, but if you're going to follow the directions on the above thing, make sure you do exactly what the **** you're told. As a reminder: it never hurts to have a backup of your Windows install.
Also, it looks like the modified 4th-gen drivers (stock drivers won't install on > Win7) listed in the top comment are now out-of-date, with no replacement. You'll do exactly what I did if you try it on a Haswell CPU with the listed modified drivers. I'd currently consider it a dead end.
So, again, this is complicated. If you're here on XDA, it's assumed you know what you're doing, so maybe go ahead, but this was your warning.

I already gave that a shot, resulting in my USB port not working
Sent from my HTC One using Tapatalk

Zak Jones! said:
While this potentially holds the solution, it's some serious-level ****. I tried this in an attempt to solve the exact same problem about a month ago, and I ended up reinstalling Windows. Because my USB drivers were all ****ed up, I was unable to pull files from the system, so it was a clean install, minus all my music and games and jazz. :/
I'm pretty sure I didn't do anything wrong, so I don't know what happened, but if you're going to follow the directions on the above thing, make sure you do exactly what the **** you're told. As a reminder: it never hurts to have a backup of your Windows install.
Also, it looks like the modified 4th-gen drivers (stock drivers won't install on > Win7) listed in the top comment are now out-of-date, with no replacement. You'll do exactly what I did if you try it on a Haswell CPU with the listed modified drivers. I'd currently consider it a dead end.
So, again, this is complicated. If you're here on XDA, it's assumed you know what you're doing, so maybe go ahead, but this was your warning.
Click to expand...
Click to collapse
petemt said:
I already gave that a shot, resulting in my USB port not working
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I have a Lenovo Yoga 2 Pro --> 4th Gen Haswell i7-4500
Installing Driver following instruction went fine. I have access to my phone now.
Probably you've done something wrong.

I also can't flash any ROMS above 4.3... Still on HBoot 1.54

ADB does work though when the phone is booted so I really don't understand this.

PC and Mac does not recognize fastboot mode [PARTLY FIXED]

Hi all
At the moment I am trying to update my HTC One's recovery so I can install Android 4.4 ROM's, although it seems that this won't happen that easy for me.
As usual I wanted to flash the recovery.img in fastboot over adb, unfortunately, my PC doesn't seem to recognize the device when it's in fastboot mode, while it did worked before.
I've been looking around on the internet and the XDA forums for a possible solution, because it seems to be a common problem.
Unfortunarely, none of the possible solutions seem to work! Installing drivers, tried USBDeview, removing drivers, trying USB3.0 port, and I even tried a Mac system, with the same results.
adb works just fine when the device is booted in Android, but in fastboot mode, it's not recognizing the device anymore, this happens on my Windows 8.1 PC, and also on my Mac.
It worked before on Windows 8, but it seems it stopped working between the time when I upgraded to 8.1, but as I said, it doesn't work on Mac either, and I also tried a few possible solutions for this issue on Windows 8.1 (which is common), but it all didn't made any sense.
Right now, I have no idea what could solve this issue.
I hope anyone could help me.

windows 8.1 does break fastboot it will work on windows 8 but not 8.1!
the newer hboots, 1.55+ or the 1.54 that was included with the 4.4 GPE update do work on windows 8.1. but of course to update hboot you have to have working fastboot access.
you may have missed something when setting up fastboot on your mac. I haven't worked with adb or fastboot on mac so I can't offer much help there.
best bet is if you can get access to someone's windows 7 machine or just spin up a VM
joshoon said:
Hi all
At the moment I am trying to update my HTC One's recovery so I can install Android 4.4 ROM's, although it seems that this won't happen that easy for me.
As usual I wanted to flash the recovery.img in fastboot over adb, unfortunately, my PC doesn't seem to recognize the device when it's in fastboot mode, while it did worked before.
I've been looking around on the internet and the XDA forums for a possible solution, because it seems to be a common problem.
Unfortunarely, none of the possible solutions seem to work! Installing drivers, tried USBDeview, removing drivers, trying USB3.0 port, and I even tried a Mac system, with the same results.
adb works just fine when the device is booted in Android, but in fastboot mode, it's not recognizing the device anymore, this happens on my Windows 8.1 PC, and also on my Mac.
It worked before on Windows 8, but it seems it stopped working between the time when I upgraded to 8.1, but as I said, it doesn't work on Mac either, and I also tried a few possible solutions for this issue on Windows 8.1 (which is common), but it all didn't made any sense.
Right now, I have no idea what could solve this issue.
I hope anyone could help me.
Click to expand...
Click to collapse

ipfreelytech said:
windows 8.1 does break fastboot it will work on windows 8 but not 8.1!
the newer hboots, 1.55+ or the 1.54 that was included with the 4.4 GPE update do work on windows 8.1. but of course to update hboot you have to have working fastboot access.
you may have missed something when setting up fastboot on your mac. I haven't worked with adb or fastboot on mac so I can't offer much help there.
best bet is if you can get access to someone's windows 7 machine or just spin up a VM
Click to expand...
Click to collapse
Thank you for your reply.
So you are telling me it should work on Windows 8 but not on 8.1?
Because on my Macbook I also have Windows 8 running in a VM, and that doesn't work either.

why not try windows 7?

SaHiLzZ said:
why not try windows 7?
Click to expand...
Click to collapse
Well, I think I will be left with the same result, since it worked fine on Windows 8 before... And it should work on Mac too, right?
Isn't there any other way to flash the new recovery without going into fastboot?

I've been able to flash the recovery via TWRP Manager from the Playstore
The fastboot issue isn't fixed yet, but I can atleast enjoy Kitkat

Fastboot problem Windows 8.1

Hi,
I recently upgraded to Windows 8.1.
It does not recognize the fastboot mode in my Nexus One.
When the phone is connected in fastboot mode (bootloader), Windows gives the prompt 'The last USB device you connected to your computer malfunctioned and Windows does not recognize it.'
Is there a problem with my phone?
What can be done to rectify this?
What fastboot drivers would be required to be installed?
Thanks in advance.

viditbhargava said:
Hi,
I recently upgraded to Windows 8.1.
It does not recognize the fastboot mode in my Nexus One.
When the phone is connected in fastboot mode (bootloader), Windows gives the prompt 'The last USB device you connected to your computer malfunctioned and Windows does not recognize it.'
Is there a problem with my phone?
What can be done to rectify this?
What fastboot drivers would be required to be installed?
Thanks in advance.
Click to expand...
Click to collapse
Same to me. I have Windows 8.1 and when i connect my N1 in fastboot mode and it give me the same error. I don't think that your (our) phone is the problem.

Mirko Lona said:
Same to me. I have Windows 8.1 and when i connect my N1 in fastboot mode and it give me the same error. I don't think that your (our) phone is the problem.
Click to expand...
Click to collapse
Thanks, such a relief knowing that it is most probably nothing wrong with my phone. :cyclops:

No replies on this?
Please help guys.

There's anyone there?

I triend on Windows 7 and same message appears

I also have this issue. I keep trying to update/re-install the driver but it always reverts back to ADB Interface > HTC Bootloader (when looking at device manager). I have re-installed the Official Google Nexus Drivers, my Nexus 9, 10 and Galaxy Nexus all work fine.
And to be clear, it's only fastboot that is the issue. ADB works:
Code:
adb devices
yields the devices ID and
Code:
adb reboot bootloader
reboots into HBoot.
Also, to be clear, I just upgraded to Windows 10 and all of the devices listed above work still!
So any thoughts would be greatly appreciated. Otherwise I might try replacing the logicboard in this bad boy.

nisiwi
toonhead85 said:
I also have this issue. I keep trying to update/re-install the driver but it always reverts back to ADB Interface > HTC Bootloader (when looking at device manager). I have re-installed the Official Google Nexus Drivers, my Nexus 9, 10 and Galaxy Nexus all work fine.
And to be clear, it's only fastboot that is the issue. ADB works:
Code:
adb devices
yields the devices ID and
Code:
adb reboot bootloader
reboots into HBoot.
Also, to be clear, I just upgraded to Windows 10 and all of the devices listed above work still!
So any thoughts would be greatly appreciated. Otherwise I might try replacing the logicboard in this bad boy.
Click to expand...
Click to collapse
I'm experiencing the same problem on Windows 10 with a Google Nexus One Did you ever resolve it toonhead85 ?

I'm thinking about buying an old windows 7 laptop on ebay just to be able to keep working on the phone. I just can't let go.

anyone found the solution about this error message? I'm trying to give life to my old N1 and I can't see to find a fix for this error, and I really dont want to downgrade my notebook system just for that...

nisiwi said:
Did you ever resolve it toonhead85 ?
Click to expand...
Click to collapse
YES!!!
So, using VirtualBox I installed Windows 7 and this. No problems at all. I guess this means that there is some incompatibility with Windows 10 and Nexus One. I was able to remove BlackRose and install STOCK 2.3.6, which is what I wanted to do in the first place.
Best of Luck!

toonhead85 said:
YES!!!
So, using VirtualBox I installed Windows 7 and this. No problems at all. I guess this means that there is some incompatibility with Windows 10 and Nexus One. I was able to remove BlackRose and install STOCK 2.3.6, which is what I wanted to do in the first place.
Best of Luck!
Click to expand...
Click to collapse
Sorry to pull this thread up from the grave, but how did you get the virtual Windows 7 to see the device at all? I've only been able to get it to pick up devices with working drivers in my main Windows install.

[Q] fastboot failing - waiting for device

Hello,
Ive Google play edition installed and TWRP recovery, S-off - I bought the phone on ebay and was going to sell it again but the guy wanted stock rom. So I checked this guide htc1guru.com/guides/return-stock-guide/] and started following it, it worked till flash RUU.exe and after that I received waiting for device. Now when I try fastboot command I always get waiting for device. I tried everything from reinstalling drivers, another ports, another cable but without luck. Any advice how to proceed and get the stock ROM ?
Thank you

tslid said:
Hello,
Ive Google play edition installed and TWRP recovery, S-off - I bought the phone on ebay and was going to sell it again but the guy wanted stock rom. So I checked this guide htc1guru.com/guides/return-stock-guide/] and started following it, it worked till flash RUU.exe and after that I received waiting for device. Now when I try fastboot command I always get waiting for device. I tried everything from reinstalling drivers, another ports, another cable but without luck. Any advice how to proceed and get the stock ROM ?
Thank you
Click to expand...
Click to collapse
my first guess is that you are using windows 8.1 with hboot 1.44? If yes then find a windows 7 computer.

alray said:
my first guess is that you are using windows 8.1 with hboot 1.44? If yes then find a windows 7 computer.
Click to expand...
Click to collapse
Yes, Windows 8.1 and I searched whole day for possible solutions however Im still nowhere.
When I enter in fastboot mode I get Unknown USB device - device failed enumeration and so on.
Is there any fix to this or just to get rid of damn Windows 8.1 ?
Regards and thank you for answer

tslid said:
Yes, Windows 8.1 and I searched whole day for possible solutions however Im still nowhere.
When I enter in fastboot mode I get Unknown USB device - device failed enumeration and so on.
Is there any fix to this or just to get rid of damn Windows 8.1 ?
Regards and thank you for answer
Click to expand...
Click to collapse
Simplest solution is to use windows 7, linux or macOS. Windows 8.1 will not work with hboot 1.44. There is a fix somewhere but I dont know, never tried myself.

[Q] Trying to gain Root on M7 (AT&T) but wiped recovery and no fastboot!!

I've been looking for a while for a forum with someone who has my problem hoping to solve it on my own but i haven't found one so if this is a duplicate please post a link so i can do it! thank you!
As far as i know, this m7 has never had s-off because as long as i've had it i haven't been able to access fastboot. i bought it from swappa and it already had root and a custom rom. However a few months later i thought i was going to sell it so i flashed an RUU onto it and declined root. the sale fell through and i'm trying to put a custom rom on it again but i don't have a recovery anymore. it must have gotten wiped when i flashed the RUU? i declined root when i flashed it (because of the sale) and not having root OR a recovery OR access to fastboot i'm not sure what to do from here.
ADB works just fine, as far as i know. i DO have the fast boot option turned off within the os (which is the only thing that boots) i have Hboot 1.44 which should apparently be a BREEZE to get s-off and root with except neither I, or any of the apps, programs, one click root's i've tried have been able to access fastboot.
i HAVE tried multiple machines with multiple OS. (windows 8.1 and Ubuntu 14) i've tried multiple cables. i've tried usb 3.0 and usb 2.0. i've installed htc sync drivers on the windows machine. i've tried the 'naked' unsigned drivers that a few people have said made fastboot work for them but they never worked. although what confuses me most is i've never had a problem with ADB. adb reboot bootloader works for me no issue but as soon as i get into fastboot this device has never been recognized.
at this point i'm rrreeeaaalllyyy tempted to just trash it but i was hoping this phone would last me until the rest of the year so i could save up for the m9.
Thank you so much for your help!! I was as thorough as I could be with the details.. I hope it's enough.

I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.

shinji257 said:
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
Click to expand...
Click to collapse
i haven't had the option yet to try with windows 7 but i had hoped that Ubuntu would recognize it because all the problems i've heard from windows 8+ were with the usb drivers.. i will see if i can get my hands on a win 7 machine though.