Windows says it's malfunctioned and and Windows does not recognise it.
Running Windows 8.1 with HBOOT 1.44. Anyway I could get it to work? ADB works fine though.
Superwig said:
Windows says it's malfunctioned and and Windows does not recognise it.
Running Windows 8.1 with HBOOT 1.44. Anyway I could get it to work? ADB works fine though.
Click to expand...
Click to collapse
There is drivers issue with win8 and hboot 1.44. use windows 7, Linux or MacOS.
Windows8 will works fine when you'll update hboot
Same problem exactly on 8.1 but i find a way to update hboot via adb shell commands. But still even im s-off i cant flash ruu, reboots to ruu mode for flashing hboot pre update thing, and suddenly my fastboot drivers doesnt work and getting the same error.
Edit:
This errors started after flashing the 1.44 hboot just after s-offed. After this problem i pushed the 1.54 hboot via adb shell, but still same error
Sent from my Lollipop One using XDA Free mobile app
Related
Hello friends,
I tried reverting back from 4.3 Developer Edition back to my original phone's condition by restoring a 4.1.2 CWM backup (Rogers) that I had. This worked, except the touch drivers don't work. I tried to run a 4.2.2 update under RUU, which seemed to break after the first attempt, and the second attempt did not work.
HBOOT 1.55 flagged the OS version and from here on out my computer stopped recognizing my device over fastboot (but is fine in ADB).
I've reverted back to my HBOOT 1.44 and the OS version flag is gone, but I'm still getting Failed Device Enumeration. Is there a partition I may have broken during the failed RUU?
You using windows 8.1 by chance? If so, you're not alone...
Sent from my HTC One using XDA Premium 4 mobile app
Yeah! Welcome to this laaarge club! Win 8.1 hate our One.
There's a thread just for this here http://forum.xda-developers.com/showthread.php?p=46794667
Easiest fix is flashing through Linux... even a live CD works.
I fixed my issue by completely deleting my htc drivers (there is also an HTC folder under programfilesx86) and reinstalling.
Sent from my HTC One using Tapatalk
EddyOS said:
You using windows 8.1 by chance? If so, you're not alone...
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
aliud said:
Yeah! Welcome to this laaarge club! Win 8.1 hate our One.
There's a thread just for this here http://forum.xda-developers.com/showthread.php?p=46794667
Click to expand...
Click to collapse
Looks like it hates all the HBOOTS except 1.55 from 3.22 base. I put that HBOOT back onto my phone, and fastboot works fine with Windows 8.1 and HBOOT 1.55. This is letting me get back into RebootRUU to run the RUU for the 4.3 developer edition until I try this thing again later hahaha.
I've just got a new laptop and after installing 8.1 fastboot is working fine with the HTC Sync Manager drivers and FW 3.62 so yeah, assumed HTC fixed it!
EddyOS said:
I've just got a new laptop and after installing 8.1 fastboot is working fine with the HTC Sync Manager drivers and FW 3.62 so yeah, assumed HTC fixed it!
Click to expand...
Click to collapse
But it doesn't work with hboot 1.44 which I needed to return to stock by running the 1.27.401.7 RUU. I had to re-install windows 8 to run the RUU then upgrade back to windows 8.1 afterwards which is not such an ordeal for me as I store all of my data on an external hard drive.
If we could just get hold of a more recent .401 RUU I would be very happy then all my windows 8.1 issues will be resolved.
Please consider this post : http://forum.xda-developers.com/showpost.php?p=69234983&postcount=6
After a lot of reading and some trial and error I was finally able to get S-OFF on my Bell (Canada) unlocked HTC One using the universal 0.45 rumrunner. I wanted to change my phone into the Google Edition so I followed the guide and everything went well but I missed the part about flashing the RUU twice and once I got that failed error I assumed it hadn't worked and I manually rebooted the phone. When I booted back into bootloader my phone was on 1.54.0000 instead of 1.55.0000 which it had been on before. The problem is that my computer won't recognize the phone in 1.54 bootloader so i can run my adb commands. I know the drivers are installed properly because it recognizes it when the phone is booted up normally and my adb commands work and I can reboot the bootloader from there but once it goes into the bootloader I can't get it to recognize the device. For reference this is on a windows 8.1 laptop, I also tried on a windows 7 desktop and an older windows 7 laptop with the same results. Is the issue with the HTC drivers not compatible with newer versions of windows? Or do I need to try to find an older version of the drivers that are compatible with the 1.54 bootloader? Or is it something else? Any help to steer me in the right direction would be greatly appreciated. Once I can get the bootloader recognized I can flash the RUU again and everything should be good to go.
Just got my new laptop running windows 8.1. Now my ONE is not recognized when in fastboot, no fastboot drivers. Did a lot of research and found that everything works on the new hboot 1.55 which I don't run! Does anyone have the fastboot drivers available and can share? Or does anyone know of flashable for just the hboot upgrade?
I ran into the same issue on my home desktop computer with 8.1 after messing around with it I ended up grabbing out my old hard drive and booting back into Windows 7 however I would try flashing the Rumrunner H boot which should be compatible with Windows 8.1 as others have told me but I haven't tested it yet but that is my plan when I have to do my next round of flashing. Your going to have to use a Windows 7 (or xp) computer in order to do that but once you do then you can use your 8.1 computer from then on out
I wonder if I could get just the fastboot drivers if it would work without having to change my hboot. Does anyone have the fastboot drivers only available?
Go read the FAQ, @BD619 has the info you likely need in that thread (stickied).
letmeputdatipin said:
I wonder if I could get just the fastboot drivers if it would work without having to change my hboot. Does anyone have the fastboot drivers only available?
Click to expand...
Click to collapse
You will have to upgrade the hboot for it to work on 8.1 regardless of what drivers you get at least that is my understanding. I'm on an older hboot because I did a custom hboot with my name on top. The main reason I did a custom hboot was to get rid of the ugly red development text during boot which rumrunner will do. The bootloader customizer plugin hasn't been updated to the new hboot yet so I would just flash rumrunner hboot. It just says rumrunner at the top and most important red development text is gone.
I'm trying to avoid changing my hboot because I have modded just the way I like it and I've never had a problem with it. But I guess is lose one, gain one!
If we're soff, can we just fastboot flash this firmware
http://forum.xda-developers.com/showthread.php?p=46123838 (the full firmware) to obtain the hboot we need to use in windows 8.1? I've rooted my One since the beginning and soff'd with revone and have always flashed the newest firmware minus the hboot...
Sent from my HTCONE using xda app-developers app
I updated my hboot from 1.44 to 1.55 using rumrunner hboot and my fastboot works on windows 8.1.
pelon90005 said:
If we're soff, can we just fastboot flash this firmware
http://forum.xda-developers.com/showthread.php?p=46123838 (the full firmware) to obtain the hboot we need to use in windows 8.1? I've rooted my One since the beginning and soff'd with revone and have always flashed the newest firmware minus the hboot...
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
All u need is the rumrunner hboot and Ur good. U do not need to flash any firmware. I've always done the same as u, upgrade firmware without hboot but this time I had to flash just a new hboot. And everything is all good now with windows 8.1! :thumbup:
letmeputdatipin said:
All u need is the rumrunner hboot and Ur good. U do not need to flash any firmware. I've always done the same as u, upgrade firmware without hboot but this time I had to flash just a new hboot. And everything is all good now with windows 8.1! :thumbup:
Click to expand...
Click to collapse
I added this to my FAQ Guide Q26
BD619 said:
I added this to my FAQ Guide Q26
Click to expand...
Click to collapse
Nice add to the FAQ, I had 8.1 before it was released so I ran into this issue right away but as it rolls out even more it's going to come up more often. With s-off changing upgrading/downgrading hboots isn't a big deal at all. With s-on you gotta be careful but this is the 1st time I can recall ever that upgrading your hboot has a benefit.
letmeputdatipin said:
I updated my hboot from 1.44 to 1.55 using rumrunner hboot and my fastboot works on windows 8.1.
Click to expand...
Click to collapse
Glad you got it working
i'm trying to install a stock Europe ROM from a RUU.zip because the RUU.exe wont run on my laptop for some reason (Windows 8.1 64bit)
i am S-off and have changed my CID to Super-CID and MID to the required one.
I have the latest HTC drivers installed and have uninstalled HTC Sync. my HBOOT version was 1.57 before, but i used firewater to obtain s-off and it brought my HOBOOT back to 1.44 (i don't know how) *i couldn't get s-off with 1.57*
i'm trying to follow this guide to install the ruu.zip
but i can only get as far as adb reboot-bootloaderon htcguru site
after it boots to bootloader mode the USB device becomes unrecognized and i cant fastboot any commands (waiting for device) shows up.
i restart my phone and i can mount to my laptop just fine and everything but when i get into fastboot mode it becomes unrecognized (Code 43), i've been up all night trying to find a solution but nothing. im lost for ideas.
ive tried different ports and restarted my laptop several times
any ideas. only reason i wanted the European ROM was to get rid of the o2 UK bootanimation and now its become a much bigger problem
i cant even run the ruu.exe file now that im s-off so im pretty much stumped
Windows 8 and 8.1 has trouble recognizing hboot 1.44, Update hboot to 1.54 and Windows will now recognize fastboot.
Sent from my HTC One using XDA Premium HD app
bored_stupid said:
Windows 8 and 8.1 has trouble recognizing hboot 1.44, Update hboot to 1.54 and Windows will now recognize fastboot.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
but i cant do that without flashing can i? will 1.44 be fine on windows 7?
jewwiid said:
but i cant do that without flashing can i? will 1.44 be fine on windows 7?
Click to expand...
Click to collapse
Hboot 1.44 is fine with Windows 7
Take a look at FAQ 1, and 5, from here
http://forum.xda-developers.com/showthread.php?p=47794181
This should get fastboot working again
Sent from my Nexus 7 using XDA Premium HD app
I am having an issue with my phone in fastboot mode. After changing my CID to GOOGL001 from CWS_001, I was in the process of flashing the GPE RUU, but it got interrupted and it was stuck on the HTC logo for a while. I ended up rebooting the device and now it is unrecognized in fastboot, yet it still works in normal mode. In fastboot mode, it is a black screen instead of the normal white screen. I don't think anything is wrong with my drivers because everything was working alright before. Phone is still fully functional and I would like to either change my CID back to normal or continue with the GPE RUU. Any help would be much appreciated. Thanks!
I have tried using USBDeview to uninstall all drivers and reinstalled all HTC drivers, but I still cant get it to connect on fastboot. Has anyone had a similar issue with their phone or know what I can do?
jacky1017 said:
I have tried using USBDeview to uninstall all drivers and reinstalled all HTC drivers, but I still cant get it to connect on fastboot. Has anyone had a similar issue with their phone or know what I can do?
Click to expand...
Click to collapse
my guess is that you are using windows 8 or above and your phone is on hboot 1.44.
try with windows 7, linux or mac.
alray said:
my guess is that you are using windows 8 or above and your phone is on hboot 1.44.
try with windows 7, linux or mac.
Click to expand...
Click to collapse
Yeah I am on Windows 8.1, but my phone is on hboot 1.54 if that makes a difference. I will try to get on a computer with windows 7 next weekend when I get home. Really hoping that it works out because this has been stressing me out these past two days.