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).
Related
anyone have a 64-bit adb driver for the slide
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
fermunky said:
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
Click to expand...
Click to collapse
it took a few days after nexus release to get a proper driver so im thinking we will be waiting a day or 2.
I used the 64bit driver for the Dream and my Vista64 had no trouble connecting to my Slide in ADB.
Thanks Fordude on Android Fourums!!!
1. Used USBDeview to uninstall all of the HTC drivers/ports
2. Unplugged HTC from PC
3. Installed PDANet software for Android (free).
4. When prompted, plugged in slide
5. After successful report of drivers being installed and program, accessed adb just fine!
Click to expand...
Click to collapse
Worked great for me on win7/64. SDK and Android Browser both work, still need root though
Also tried to use Apps2sd update zip, needs to be signed for this phone if anyone would be willing.
apps2sd--http://paulw.hardmilk.com/downloads/r1-a2sd-desire-dalvik-fresh-signed.zip
and the instructions for ADB were found here
http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
I'll have to give this a try. I remember using PDANet a while back and it worked, so probably will work again. Thanks
awesome i got it working now thanks
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
chrisinaz said:
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
Click to expand...
Click to collapse
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
the HTC Sync update for the phone was released for the phone. it should contain the necessary and appropriate drivers.
fermunky said:
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
Click to expand...
Click to collapse
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
poetik517 said:
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
Click to expand...
Click to collapse
Got it. For some reason Chrome had me Cached outside of the US, so it wasn't showing up for me.
For everyone's reference, make sure your selected country is US or just go here:
http://www.htc.com/us/support
chrisinaz said:
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
Click to expand...
Click to collapse
You'll want to remove the driver again via USBDeview. THEN make sure Charge only is selected, reinstall PDANet, and then plug in phone. If it still doesn't work, you are doing something wrong, trust me.
I am rooting my friends phone using the proper thread, following all the directions, did this on my previous Fascinate, however I get into download mode, but Odin does not recognize it and does nothing....?
make sure you have the samsung drivers installed...
Everything is installed including the drivers, its saying the device is not being recognized even though the drivers are on my computer..
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
droidstyle said:
are u using the stock usb cable? Maybe try a different one. Also might want to try a different computer. Another thing go into device manager and make sure the drivers are indeed installed for your device.
Click to expand...
Click to collapse
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
CC268 said:
Yes I am using the stock cable, and I have tried it on 3 different computers each one isn't working and a pop up comes up stating the usb device cannot be recognized or something close to that. Under disk drives on device manager it does show SAMSUNG HM500JJ but I dunno...this is weird maybe I just can't get this thing rooted..
Click to expand...
Click to collapse
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
droidstyle said:
I would try redownloading and installing the samsung drivers...try the drivers from section 1 of my guide in general section. If that still dont work then try another usb cable. The cables can be touchy with odin, especially if you coil it up all the time. Don;t ask me why, all I know is in the past 6mo this issue has been posted 50times or better. Usually its one of the things I mentioned causing the problem.
Click to expand...
Click to collapse
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
CC268 said:
Yea that is the driver I have been using and I have uninstalled it and installed it probably a good 5 times. I just dont understand why it would be the cable if I plug it in and its giving the message "The USB Device cannot be detected" or something along the lines of that. I will try the cable for my HTC Thunderbolt tomorrow and see if it works. If that doesn't work then it looks like the phone won't be getting rooted because I don't have anymore cables to try and I am running out of patience
It has to be the driver...my htc thunderbolt works perfect and is always recognized and adb works too and recognizes my device
Click to expand...
Click to collapse
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
droidstyle said:
try installing the google nexus driver and see if that works.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I will try this tonight when I get over to my buddies apartment, thanks
I couldn't get it installed...the directions on actually getting the driver installed are not good...there are a lot of steps that I can't do on my computer such as go to manage in computer and then devices tab...there is no devices tab?!?!
CC268 said:
I couldn't get it installed. It just said windows has already found the appropriate driver. I dont understand how it could be so hard to find a dang driver for this phone...
Click to expand...
Click to collapse
it wont automatically install...you have to click on the device in device manager and go to update driver, then manually push the google driver. After successful install it should say android device in DM.
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
CC268 said:
I couldn't find the device in device manager...I mean the computer isn't going to recognize it anyways if there isn't any drivers installed?
Click to expand...
Click to collapse
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
droidstyle said:
If you have usb debugging turned on, usb cable plugged in, installed either the samsung driver or nexus driver and still get a "cant recognize device error" then either the usb port is bad on the phone or the cable is jacked. The problem is not the drivers...Lots of people use the drivers I suggested with no problems. I thinks its the usb cable personally because from what you describe, windows can tell something is plugged into the usb port, but cant tell what it is. Windows has to be able to recognize the device before you can install the drivers for it.
Click to expand...
Click to collapse
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
CC268 said:
Yea...hmm well I know its not the computers and certainly not my laptop as I never have any trouble with it...I have used several different cables though so it could be the phone...
Click to expand...
Click to collapse
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
droidstyle said:
That could be...try cleaning the usb port on the phone...power of device, pull battery, then put some contact cleaner on a q-tip. If still nothing, then a replacement might be in order.
Click to expand...
Click to collapse
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
CC268 said:
I will try these steps...I mean windows is recognizing that something is plugged into the computer so I dont know if its really a phone issue still seems like its more of a driver issue...but I dunno I wish I could find the old adb way of rooting the fascinate...it was way more problem free...anyways I dont know when I will have time to try this on my friends phone again it may not be for another month but I will try again at some point
Click to expand...
Click to collapse
here is adb root method if it helps:
To Root
(credit p3droid/Mines_01 from ec09)
***Requires ADB***
1. Download this: http://www.multiupload.com/HXKQY717LY
md5: 113a9158535ddefa802eb2dc187f236d
2. unpack to wherever adb folder is
(if adb is universal unpack wherever)
3. cd folder with unpackaged files
4. adb push su /data/local
5. adb push Superuser.apk /data/local
6. adb shell
7. mount -o remount,rw -t rfs /dev/block/stl19/system
8. cat /data/local/su > /system/xbin/su
9. chmod 6755 /system/xbin/su
10. cat /data/local/Superuser.apk > /system/app/Superuser.apk
11. chmod 755 /system/app/Superuser.apk
12. reboot
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
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
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!!!