Can someone help me get my HTC One to be recognized by Windows. I can get it recognized when the phone is booted into the system but once it hits the bootloader it shows this error:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
sapplegater said:
Can someone help me get my HTC One to be recognized by Windows. I can get it recognized when the phone is booted into the system but once it hits the bootloader it shows this error:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
are you possibly using a USB 3.0 port? if so use a 2.0
I've tried using both and no luck either way.
Sent from my HTC One using Tapatalk 2
sapplegater said:
I've tried using both and no luck either way.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
You could always do what I ended up doing; get an Ubuntu Live CD and run it without installing, download the sdk, and run adb/fastboot commands that way.
Strike9172 said:
You could always do what I ended up doing; get an Ubuntu Live CD and run it without installing, download the sdk, and run adb/fastboot commands that way.
Click to expand...
Click to collapse
This is a very good suggestion and Ubuntu 13.04 installs beside Windows 8 pretty easily. As long as you get into the bios and turn secure boot off and then change the boot order to put your CD image or sd drive first.
It is probably the easiest way if to don't have a Windows 7 machine laying around. That's what I had to do myself. I didn't feel like installing the sdk on my Fedora partition right then so I hijacked my wife's computer.
Sent from my HTC One using xda app-developers app
see this thread... it helped me solve my Win8, 64-bit, USB issues, including fastboot.
I have problem with HTC One flashed Stock RUU with Google edition and can't see mass storage. In device manager Android device: My HTC -this is ok, but MTP driver is not found, i had tried everything.
Windows 8 x64. I tried 2 different win8 x64 machines and same problem. Few weeks ago I ran's win7 and ARHD 12.1 then working well. All started in win8.
In Windows 7 x64 no problems at all. Windows find automatically driver or update new driver both working.
Can anyone recommend something?
Cheers !
Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
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
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!!!
I just got a new laptop with Windows 8.1 64 bit. When I plug in my Evo LTE, nothing happens. It does not show up as new hardware and there is no trace of it in the device manager. The charge light is on, but that's it.
I've tried installing HTC sync & drivers only but I get the same results. I've dug around on this site and on the web for a couple of days before starting this thread just in case I could find something. No luck.
My phone:
Evo LTE S-Off
CM 10.2
My laptop:
Acer V5 122P
1 USB 3.0, 1 USB 2.0
I've tried plugging it into both ports with the same above results. I'm stuck.
Seems to be a common issue with 8.1. The consensus seems to be either downgrade to 8 or find a Windows 7 machine to use.
Nice avatar
Sent from my HTC EVO 4G LTE
oops. Double post.
Thanks. She's my baby.
I was afraid of that.. My Windows 7 machine has been retired. I've been reading about downgrading to 8.0 and it looks like it's a PITA as far as having to completely reset the machine.
So far everything but my phone works through the USB ports. I guess I'll just have to wait for a fix.
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Try a different USB cable - some will do charge only, others will give full access to communicate with phone.
If using an Intel chipset, go to Intel's webpage and download their USB 3.0 drivers and use those instead of Microsoft's - these are a must if trying to flash/root phone when using windows 8/USB3 drivers.
CapedCrusader said:
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Click to expand...
Click to collapse
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
aarsyl said:
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
How did you do this? I can't use 8.1 with fastboot. Would love to use one of my old thumb drives and try.
Download Ubuntu here:
http://www.ubuntu.com/download/desktop
Download the Live USB creator here (instructions included):
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
Some might find my method to be a bit cumbersome, but it got the job done. I experienced a lot of problems trying to dual-boot Windows 7 & Ubuntu, so I used 2 flash drives. I used the 2gb drive as the Live USB install, rebooted using my new Ubuntu Live USB, then I installed Ubuntu onto my 32gb drive. In Windows, you might be able to run the installer, and install Ubuntu to the flash drive that way, but for some reason that I don't know, it would force me to try or install Ubuntu as my only option.
I will continue to edit this post as I find more tips, and clearer instructions.
If your win8 system only has USB 3.0 ports, try installing the intel usb3.0 drivers instead of the Microsoft ones. This is what I did to get around adb and htc sync connection issues - I have no problem connecting my win8.1 system w/intel usb3.0 drivers to communicate and flash rom's to my evo since I made the switch over. do a search and you will find all the information about intel vs. Microsoft usb drivers on this and other sites.
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.