I have followed about every damn fastboot on Windows 8 post I can find on XDA and none of them seems to be working with this phone. adb drivers work just fine but no go on fastboot. Anyone out there have any luck getting fastboot working on Windows 8 with the DNA?
I successfully used fastboot and adb on Windows 8(64 bit). When i first plugged in the phone, and it wanted to install htc sync, i allowed it to. Then i uninstalled htc sync, but i believe it left the drivers. Adb and fastboot worked fine.
You might also check that you are using a usb2 port (not usb3) and not using a usb hub. Both have been known to cause problems with fast boot/adb
Sent from my Nexus 7 using Tapatalk 2
jasoraso said:
I successfully used fastboot and adb on Windows 8(64 bit). When i first plugged in the phone, and it wanted to install htc sync, i allowed it to. Then i uninstalled htc sync, but i believe it left the drivers. Adb and fastboot worked fine.
You might also check that you are using a usb2 port (not usb3) and not using a usb hub. Both have been known to cause problems with fast boot/adb
Click to expand...
Click to collapse
Reinstalled latest HTC Sync from their support site and switched to USB 2.0 port. Seems to be working ok now. Thanks! Can stop using the backup machine with this phone now :highfive:
mikeschuld said:
I have followed about every damn fastboot on Windows 8 post I can find on XDA and none of them seems to be working with this phone. adb drivers work just fine but no go on fastboot. Anyone out there have any luck getting fastboot working on Windows 8 with the DNA?
Click to expand...
Click to collapse
i was in the exact same position. My system runs Win8 x64 and I had my phone plugged into a USB3 port, but even when I plugged it into the only USB2 Port, it still had issues so I used my Win7 x64 Rig and it worked flawlessly.
Also make sure you don't have an app like easytether installed on the computer this if very often overlooked just disable it for the system tray in windows
Sent from my HTC6435LVW using XDA Premium App
I was able to select and install the driver directly using device manager in Windows 8. The driver file can be obtained from the drive that the DNA mounts when you plug it in USB. I used the windows 7 driver:
i.e. <MountedDrive> HTC Sync Manager:\Win7_64\androidusb.INF​
Hate to revive a old dead thread, but I guess it is better than posting a new one, so anyways on to my question, my only computer is a Microsoft Surface Pro, and it only had one USB port which is USB 3.0. In the last few months since this thread has been dead has there been any progress on a USB 3.0 driver from HTC, or here on XDA. ADB works perfectly but I can't get fastboot to install. I have the SDK installed correctly but I just can't seem to get the drivers for for fastboot to install.
androidoholic said:
Hate to revive a old dead thread, but I guess it is better than posting a new one, so anyways on to my question, my only computer is a Microsoft Surface Pro, and it only had one USB port which is USB 3.0. In the last few months since this thread has been dead has there been any progress on a USB 3.0 driver from HTC, or here on XDA. ADB works perfectly but I can't get fastboot to install. I have the SDK installed correctly but I just can't seem to get the drivers for for fastboot to install.
Click to expand...
Click to collapse
I don't have surface so i'm speculating but, just like everything else. Install htc sync to make sure that all the drivers take cleanly. Plug in your USB and
adb reboot bootloader
when your phone reboots it should say
fastboot usb.
If it does then you are good to go, just run the fastboot commands from the same folder that your platform-tools are in. fastboot flash boot boot.img
it will say sending, then working. and you should be good.
If it does not say fastboot usb, then please post back and we will do more research to figure this out.
dragonstalker said:
I don't have surface so i'm speculating but, just like everything else. Install htc sync to make sure that all the drivers take cleanly. Plug in your USB and
adb reboot bootloader
when your phone reboots it should say
fastboot usb.
If it does then you are good to go, just run the fastboot commands from the same folder that your platform-tools are in. fastboot flash boot boot.img
it will say sending, then working. and you should be good.
If it does not say fastboot usb, then please post back and we will do more research to figure this out.
Click to expand...
Click to collapse
It does say fastboot usb but none of the commands will work, no matter what I try it will always say <Waiting for device>
And I have tried it with HTC Sync installed and after uninstalling it. I seem to remember it did not play nice with some older phones but when you uninstalled it they drivers stay there, not sure if that is still the case but thought that I would try just to see.
androidoholic said:
It does say fastboot usb but none of the commands will work, no matter what I try it will always say <Waiting for device>
And I have tried it with HTC Sync installed and after uninstalling it. I seem to remember it did not play nice with some older phones but when you uninstalled it they drivers stay there, not sure if that is still the case but thought that I would try just to see.
Click to expand...
Click to collapse
I've never heard of anyone with a usb 3 succesfully doing it and i've searched the forums like crazy. The only way i was able to get it to work is cuz i have two ports and the other was a 2.0.
I mean maybe im crazy but is there some sort of an adapter than could change 3.0 to output 2.0? idk....
On a side note I loved Windows 8 for about 10 minutes then dumped it and went back to Windows 7. Just saying.. I know that's not always an option.
zone23 said:
On a side note I loved Windows 8 for about 10 minutes then dumped it and went back to Windows 7. Just saying.. I know that's not always an option.
Click to expand...
Click to collapse
Lol , I'm with you on that one. I had dual boot and windows 8 took over my whole computer and locked me out of my Ubuntu partition. Plus hate the fact that windows 8 integration is dependent on having a windows account for EVERYTHING.
dragonstalker said:
Lol , I'm with you on that one. I had dual boot and windows 8 took over my whole computer and locked me out of my Ubuntu partition. Plus hate the fact that windows 8 integration is dependent on having a windows account for EVERYTHING.
Click to expand...
Click to collapse
Well aside we are off topic anyways Windows 8 on a desktop or laptop is a piece of sh#t, but on the surface this is amazing I could not imagine anything better on a tablet. The only problems are the price and only one usb, other than that this thing is the best computer by far that I have ever owned. And I would venture to say that it's the best tablet EVER! The only thing that would make it better is if the DNA would play nice with it.
Sent from my HTC6435LVW using Tapatalk 2
Related
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
ADB seems to work, but in fastboot I get a pop up says that the device couldn't be recognized by Windows and Device Manager gives
Windows has stopped this device because it has reported problems. (Code 43)
Click to expand...
Click to collapse
Now, I don't know how the underlying hardware works but I'm fairly sure that if ADB and other USB functions work, fastboot should work as well. Any ideas?
scy1192 said:
ADB seems to work, but in fastboot I get a pop up says that the device couldn't be recognized by Windows and Device Manager gives
Now, I don't know how the underlying hardware works but I'm fairly sure that if ADB and other USB functions work, fastboot should work as well. Any ideas?
Click to expand...
Click to collapse
ahhh...the famous code 43. The problem with this code is its pretty generic. It could be hardware or could be drivers. Basically what happens is Winblows is having an issue with the device that is connect, in this case your phone. Seen this one to many times. Try rebooting your computer first of all and try again. If you are still getting the try updating the HTC drivers for your phone. If you do this make sure to remove old drivers and then reinstall the new drivers. That should take care of the issue
clmowers said:
ahhh...the famous code 43. The problem with this code is its pretty generic. It could be hardware or could be drivers. Basically what happens is Winblows is having an issue with the device that is connect, in this case your phone. Seen this one to many times. Try rebooting your computer first of all and try again. If you are still getting the try updating the HTC drivers for your phone. If you do this make sure to remove old drivers and then reinstall the new drivers. That should take care of the issue
Click to expand...
Click to collapse
It does seem to be my computer and not the phone thankfully (works on another PC). I am using Koush's universal drivers and they've previously worked. On the USB 2.0 ports I get the device enumeration failed thing, and in the USB 3.0 ports (different board, uses a Renesas controller) it appears but gives me
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
I've tried reinstalling the drivers and no dice. I can't use the HTC drivers since I'm on Windows 8.1
I guess worst case I'll just patch it through to an XP virtual machine or something.
Yea win 8 has issues. I use Linux personally. That should resolve your issue using xp.
Sent from my Rezound using xda app-developers app
tburns said:
Yea win 8 has issues. I use Linux personally. That should resolve your issue using xp.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Same here Debian and DSL all the way but yeah a xp VM should do the trick then. Haven't played with 8 or 8.1 at all so I can even point you in a direction for that. Easy solution as well....use Linux
Sent from my ANDROFLY REZOUND using xda app-developers app
scy1192 said:
It does seem to be my computer and not the phone thankfully (works on another PC). I am using Koush's universal drivers and they've previously worked. On the USB 2.0 ports I get the device enumeration failed thing, and in the USB 3.0 ports (different board, uses a Renesas controller) it appears but gives me
I've tried reinstalling the drivers and no dice. I can't use the HTC drivers since I'm on Windows 8.1
I guess worst case I'll just patch it through to an XP virtual machine or something.
Click to expand...
Click to collapse
i know this is an old post, but the driver posted here got me back in business!!! Its a phone for the kiddos, and it was missing rh boot.img and all but 1 of my computers runs 10. This got the win 7 adb driver working just fine!!!
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hey friends, having a hard time here for some reason...
Both my N7 (v2) and HTC One m7vzw will NOT show up in "adb devices" when in bootloader mode. They do however, show up when they are powered on. Its been a while since I've tinkered with either one in adb so I can't remember the last time it worked, but couldn't have been longer than 2 months ago.
I've tried on two Win 7 x64 machines, my Dell Optiplex at work and my HP laptop at home. I've tried switching USB ports, I've tried different USB cables including the factory cables, I've tried uninstalling and reinstalling the drivers including HTC Sync Manager, I mean, I've tried it all as far as I know... Including updating everything is the Android sdk manager, I tried installing the drivers using WugFresh's Nexus Tool Kit as well (all with appropriate reboots as well...)...
So, I don't know what the eff is going on, but if anyone could maybe she some light or share some past similar experiences that would be sweet! :good:
You guys rock, thanks all.
Bump. Anyone?
however, "fastboot devices" does show the device, which is weird, so I should be good since fastboot is working and all I need to do is flash back to stock? I won't need adb commands?
If you have a windows 8 computer laying around, watch the video in that thread I linked you, it has drivers for 8.1.
GrayTheWolf said:
If you have a windows 8 computer laying around, watch the video in that thread I linked you, it has drivers for 8.1.
Click to expand...
Click to collapse
Thanks, I don't, but I did figure it out, fasboot worked just fine, just no adb, luckily I only needed fastboot commands.
adb will only work in recovery and os, fastboot will only work in bootloader
So yes this completely normal
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
adb will only work in recovery and os, fastboot will only work in bootloader
So yes this completely normal
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
^This.
hello.
i think i have already tried everything to get fastboot on my pc find my device, but no luck.
I've got an old laptop with usb 2.0 + windows 8.1 x64 Pro and the same OS on my PC with usb 3.0 (according to some of threads, my CPU is i7 4770k and my MOBO is MSI Z87-G45).
I use my HTC Desire X every day and it is simply slow. I cannot try every ROM cause of need to flash boot.img. And i Dont have any idea how to get the fastboot recognize my device....
Maybe someone have some time to help mi wlak through this 'issue' idiot friendly? I'm really confused and i dont have any idea what to do.
my hboot is 1.25.** JB. S-ON. I have installed TWRP recovery.
:crying: halp
EDIT:
SOLVED. Windows 7 FTW.
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Will_Xda said:
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Click to expand...
Click to collapse
So,what did you do ?:d
evnee said:
So,what did you do ?:d
Click to expand...
Click to collapse
Installed a HTC sync like program named PDAnet, and updated the drivers from that program, once in fastboot mode device is recognized in pdanet and in a command prompt (adb). this only worked on a usb2.0 port though.
(didn't bother replacing usb3.0 drivers as suggested elsewhere as this has caused big issues for me before.)