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.
Related
My htc one is plugged in, in fastboot, and says fastboot usb but fastboot on my computer is saying waiting for devices. What can i do to fix this issue?
I just had this problem and fixed it on my Windows 8 machine.
The culprit seems to be a Microsoft USB driver; fix is to replace the Microsoft with the Intel version.
Follow this guide here and you should be all set.
Good luck!
michaelalias said:
I just had this problem and fixed it on my Windows 8 machine.
The culprit seems to be a Microsoft USB driver; fix is to replace the Microsoft with the Intel version.
Follow this guide here and you should be all set.
Good luck!
Click to expand...
Click to collapse
But im on windows 7, but i'll still try it if it can be done on win7 but thank you though
GhostSoldier_US said:
But im on windows 7, but i'll still try it if it can be done on win7 but thank you though
Click to expand...
Click to collapse
Are you trying to get the device token via Hasoon's kit? I might be able to help given more details
michaelalias said:
Are you trying to get the device token via Hasoon's kit? I might be able to help given more details
Click to expand...
Click to collapse
no im trying to put another recovery on my one via fastboot
GhostSoldier_US said:
no im trying to put another recovery on my one via fastboot
Click to expand...
Click to collapse
Via command line or via Hasoon's kit?
If I were you, I'd reboot to the OS and then see if you can ADB a command to get to the bootloader. If that doesn't work, then maybe you don't have ADB installed properly?
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
whitetiger_0603 said:
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
Click to expand...
Click to collapse
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Ardmanz said:
I use windows 8 and it has mostly been trouble free for me. However I did have problems with my laptop recognising my phone when in recovery. It eventually worked on it's own but I found this after:
http://forum.xda-developers.com/showthread.php?t=2232799
Maybe try installing the windows 8 drivers above.
Click to expand...
Click to collapse
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
whitetiger_0603 said:
Yeah i saw that thread, but my phone was already showing up in devices. It just won't be recognized in bootloader or fastboot.
Click to expand...
Click to collapse
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Ardmanz said:
Mine was recognised everywhere (including recovery). I'd get the beep from windows 8 and the driver would initialise but it wasn't recognised by adb.
If you haven't tried installing the above drivers yet it certainly wouldn't hurt to try.
Click to expand...
Click to collapse
I gave it a shot while in bootloader. Thanks tons. Just a question though, my cope recognizes my phone however when i input "adb devices" in CMD, nothing shows up. Just wondering if that is an issue before i continue.
Rayskull said:
if your problem is adb have you tried to add it in the "Environment Variables" ?
have you enabled USB debugging in your phone ?
i have windows 8 too and i don't have this kind of problem
Click to expand...
Click to collapse
I glanced at something about the environmental variables but i can't find it again. Yeah i have all the correct settings marked to do this
Hey Folks, anyone here using windows 8.1? I have no problem running adb, but when I boot the m7 into fastboot, windows says there is a problem with my usb device. I've tried uninstalling htc sync and reinstalling, no dice.
Any thoughts?
shadoslayer said:
Hey Folks, anyone here using windows 8.1? I have no problem running adb, but when I boot the m7 into fastboot, windows says there is a problem with my usb device. I've tried uninstalling htc sync and reinstalling, no dice.
Any thoughts?
Click to expand...
Click to collapse
Yep. It's a known issue. ADB doesn't work with 8.1. Only solutions right now are to either downgrade back to 8, or wait for the final version of 8.1.
Freaking annoying.
Kinda sucks I have to use a really low end laptop running 7 to use adb commands. At least I rarely use them though...
Sent from my HTC One running CM 10.1
blackroseMD1 said:
Yep. It's a known issue. ADB doesn't work with 8.1. Only solutions right now are to either downgrade back to 8, or wait for the final version of 8.1.
Freaking annoying.
Click to expand...
Click to collapse
ADB works fine for me in 8.1, its the HTC drivers for fastboot that are the problem. Anyway, I gave up and just used my Linux box, so I think we'll just have to wait for HTC to update their drivers.
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
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.