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
Related
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.
Hello,
I'm having a headache since I upgraded to 8.1. I can see my htc phone without any problem in windows and communicate with ADB. But once I get to recovery or fastboot, the USB will make an error saying it failed enumeration. Because of that, it don't even try to install drivers. What can I do to fix that?
This is using USB 2.0 ports since my board don't have 3.0.
Thanks
nodiaque said:
Hello,
I'm having a headache since I upgraded to 8.1. I can see my htc phone without any problem in windows and communicate with ADB. But once I get to recovery or fastboot, the USB will make an error saying it failed enumeration. Because of that, it don't even try to install drivers. What can I do to fix that?
This is using USB 2.0 ports since my board don't have 3.0.
Thanks
Click to expand...
Click to collapse
try upgrading ur hboot to 1.55
your problem will be solved!
Harish_Kumar said:
try upgrading ur hboot to 1.55
your problem will be solved!
Click to expand...
Click to collapse
nop, already on hboot 1.55 with 3.62 firmware I too though it would fix it, but it didn't
nodiaque said:
nop, already on hboot 1.55 with 3.62 firmware I too though it would fix it, but it didn't
Click to expand...
Click to collapse
It fixed for me
why dont you try uninstalling everything regarding HTC Sync and drivers and reinstall the new HTC Sync
Harish_Kumar said:
It fixed for me
why dont you try uninstalling everything regarding HTC Sync and drivers and reinstall the new HTC Sync
Click to expand...
Click to collapse
Tried, even tried multiple version of HTC Sync (with and without sync installed). I even used own google ADB driver. Problem is, it's not HTC driver problem since the USB Port is having a "Device enumeration failed", which is a USB failure, not a driver failure. Meaning the device cannot be identified, thus can't know what driver should be used. I tried to force it but windows won't let me.
I searched extensively for a fix for this problem and I honestly don't think there is one yet. Eventually I gave up and installed the generic drivers on my old laptop that's still running Windows 7 and was able to adb and fastboot on it just fine. I've found several driver related issues with both Windows 8 and 8.1 so I think I'll be keeping the laptop as a legacy device for awhile just for situations like this!
I had the same problem, ended up using my phone on a Windows 7 PC.
Enviado desde mi HTC One mediante Tapatalk
nodiaque said:
Tried, even tried multiple version of HTC Sync (with and without sync installed). I even used own google ADB driver. Problem is, it's not HTC driver problem since the USB Port is having a "Device enumeration failed", which is a USB failure, not a driver failure. Meaning the device cannot be identified, thus can't know what driver should be used. I tried to force it but windows won't let me.
Click to expand...
Click to collapse
I don't know if this will help, but I'll leave this for you to read through: http://forum.xda-developers.com/showthread.php?t=2256359
Maybe there's a solution there for you. (I'm on Win 7 so never tried any of it)
I had this at first but as soon as I updated my firmware, the problem went away. Though I have ubuntu on my old laptop which I will keep now for situations like these because when I tried to install an old ruu through rebootRUU, my phone wasn't found anymore after the first flash, but saved it with my laptop.
Burn yourself a Linux (Ubuntu) live CD or install it side by side with windows 8.1.
Sent from my HTC One using Tapatalk
same problem
hboot 1.54
firmare 2.24.111.3
But did not work in windows 8.0, too.
MICH_** said:
same problem
hboot 1.54
firmare 2.24.111.3
But did not work in windows 8.0, too.
Click to expand...
Click to collapse
For fastboot in windows 8.1 you need the 3.62 firmware without a modified hboot. If you have firmware with red text removal or the dark bootloader version then fastboot will not see the device.
You should also download the latest HTC drivers then everything should work.
ah that's why, I have the modified hboot.
As for install linux in side by side or live linux, no thanks, this is not what I'm looking for. I won't install another OS just for that, thus why I'm looking for how to make it work in Windows 8.1, not how to make it work on my computer with any OS.
I have latest HTC drivers, but modified hboot. I hope someone came up with a fix for that because it's very annoying. Good thing I still have one pc on windows 7 and it will stay this way for now since it's the only computer that can see my phone.
I was having the same issues neither the usb 2.0/3.0 worked. But after I installed the latest HTC sync from their website everything works on W8.1
If some one else doesn't I'll post the drivers when my work day is over. So not anytime soon.
Sent from my HTC One using XDA Premium 4 mobile app
Here is the missing USB driver that was not loading correctly before I updated firmware to hboot 1.55. Had to flash that firmware on my old Samsung netbook under Windows 7, after that Windows 8.1 loaded the driver and fastboot works ever since:
https://www.dropbox.com/s/1fvlo16jn81dpf3/HTCDriver_4.8.0.002.exe
You need to download Intel drivers and scrap the windows ones...
Link with instructions in post... : http://forum.xda-developers.com/showthread.php?t=2510682
this is for usb 3.0, not for usb 2.0. I already checked anyway and intel didn't make any usb driver for my board, they only made 3.0 ones, which my board doesn't have.
Had the same issue, in the end I had to partition my drive and dual boot Windows 7. It's a ***** but I couldn't find a single fix on 8.1 after dicking around with it for 3 days straight.
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.
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.
OK guys, I'm getting desperate here...
My problem is, I can't flash RUU on my M7 UL unlocked european. All adb and fastboot commands work fine, but when I boot to RUU mode and issue "fastboot flash zip RUU.zip" my laptop restarts... I had some good help from @alray, but it didn't work so any help is apreciated.
My laptop info
HP 4730s with Windows 10 professionall
Minimal fastboot and adb 1.31 with htc fasboot.exe patched
Any insight will be highly appreciated
donkeykong1 said:
OK guys, I'm getting desperate here...
My problem is, I can't flash RUU on my M7 UL unlocked european. All adb and fastboot commands work fine, but when I boot to RUU mode and issue "fastboot flash zip RUU.zip" my laptop restarts... I had some good help from @alray, but it didn't work so any help is apreciated.
My laptop info
HP 4730s with Windows 10 professionall
Minimal fastboot and adb 1.31 with htc fasboot.exe patched
Any insight will be highly appreciated
Click to expand...
Click to collapse
Were you able to try with another computer? I'm curious to know if it's only with your laptop...
Might want to try fastboot on the same laptop with a Ubuntu live usb.... I wouldn't be surprised that Win10 is causing all this, I have a lot of problems with others things that worked fine before the update,
alray said:
Were you able to try with another computer? I'm curious to know if it's only with your laptop...
Might want to try fastboot on the same laptop with a Ubuntu live usb.... I wouldn't be surprised that Win10 is causing all this, I have a lot of problems with others things that worked fine before the update,
Click to expand...
Click to collapse
I'm waiting for a friend to bring me his W7 laptop to try. I have a W7 computer, but I was never able to get fastboot running on it. It showa something like "daemon out of time" or something. I tried few fixes for that, but it didn't work
..the thread seems to be abandoned, but i stambled on to it
..and thought: for the sake of the ones that look for answers..
in Windows 10, we have been introduced to a new feature:
,by default- it refuses to load unknown or unsigned drivers,
in many cases that is why- we all - have to struggle to set up and reliably
run fastboot on win 10
Digital signature verification can be disabled:
-temporarily - through windows settings
-permanently- via terminal ( it'd be worth searching for a bit )
Edit: this way,or another, this:
https://answers.microsoft.com/en-us...n/a53ec7ca-bdd3-4f39-a3af-3bd92336d248?auth=1
may be a part of the story- as we know it...
,and one day it surely will be compromised but
till then..
I have two driives on my pc, still keep my Win 7 on one of them
..Regards
asgardr said:
..the thread seems to be abandoned, but i stambled on to it
..and thought: for the sake of the ones that look for answers..
in Windows 10, we have been introduced to a new feature:
,by default- it refuses to load unknown or unsigned drivers,
in many cases that is why- we all - have to struggle to set up and reliably
run fastboot on win 10
Digital signature verification can be disabled:
-temporarily - through windows settings
-permanently- via terminal
Click to expand...
Click to collapse
Well, I have official HTC drivers, but I'm gonna try this. Thank you very much for the tip mate!
You mind if i ask why arent you running the exe RUU?
Luis_D1 said:
You mind if i ask why arent you running the exe RUU?
Click to expand...
Click to collapse
I don't mind at all. I never even looked at exe RUUs, I'm used to zip files, and I need fastboot to work because I want to unlock my HTC 10's bootloader [emoji6]