My little gift to the community, who don't happen to have driver hacking experience
Here's the adb drivers modified with the new ADB device ID.
For both x86 and amd64
Let me know if it works, as I only tested on amd64
Regards,
P
EDIT: Oh, should mention how to use these.
You need to extract the ones you are after (x86/amd64) and point device manager to the folder when it shows the "Android Phone" with unknown drivers.
This is great, I've been looking for this the past 2 weeks.
But.....
I get an error message that WinUSBCoInstaller.dll is missing. When I add the file from the android 2.2 sdk, my machine is asking for WdfCoInstaller01007.dll. Your zip contains 01005.
I'm on Win XP 64.
Azkabor said:
This is great, I've been looking for this the past 2 weeks.
But.....
I get an error message that WinUSBCoInstaller.dll is missing. When I add the file from the android 2.2 sdk, my machine is asking for WdfCoInstaller01007.dll. Your zip contains 01005.
I'm on Win XP 64.
Click to expand...
Click to collapse
Hmm. I don't know about XP x64 (it's rarely supported btw), but try renaming the file to what it needs. I had no issues installing it straight in.
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
ltraddical said:
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
Click to expand...
Click to collapse
You're lucky then. They changed the device ID of the adb driver on this release today. Maybe newer drivers are better, but I don't know... I used SDK 1.5 drivers from November btw.
how would i go about using this? do i place them the in drivers folder in the sdk folder?
info5i2002 said:
how would i go about using this? do i place them the in drivers folder in the sdk folder?
Click to expand...
Click to collapse
Yeah, go to device manager and update the drivers of the unrecognised Android Phone. Use these.
anon2122 said:
Yeah, go to device manager and update the drivers of the unrecognised Android Phone. Use these.
Click to expand...
Click to collapse
alright, that's great! thanks.
ltraddical said:
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
Click to expand...
Click to collapse
Same here. Others probably didn't install the drivers right.
jaymac407 said:
Same here. Others probably didn't install the drivers right.
Click to expand...
Click to collapse
Nah. I think it's age of drivers. I installed them fine, but a long time ago. I guess they have been updated since then, but I'm not the only person to have had this issue. I think adwinp had the problem too, although he's been going for longer than me on the hero, so has likely got old drivers too...
I did the exact same thing, but it's nor working, when I selecht the map it says that it can't install it.
"There are no devices to be found"
Since I installed an 2.1 ROM i can not go into adb anymore.
anon2122 said:
You're lucky then. They changed the device ID of the adb driver on this release today. Maybe newer drivers are better, but I don't know... I used SDK 1.5 drivers from November btw.
Click to expand...
Click to collapse
My adb stopped working 4 days ago. So I reinstalled HTC Sync from HTC's website. This fixed it and still it works after flashing Pauls ROM. So I guess an easier fix is to just install the latest HTC Sync.
The latest offical Android SDK drivers do not work with 2.1 Hero so far (device is not recognized).
However, installing the (old) HTC Sync includes all the necessary drivers for our Hero, even with 2.1 installed!
So no need for anything else.
Does not work with Win7x64
any chance of you making the Linux version of adb compatible with 2.1 as well?
Umm. It's working fine here on 7 x64 (that's where I was having the issue).
Also, adb is running on my ubuntu x64 machine fine, although i downloaded the 2,2 SDK for it
anon2122 said:
Umm. It's working fine here on 7 x64 (that's where I was having the issue).
Also, adb is running on my ubuntu x64 machine fine, although i downloaded the 2,2 SDK for it
Click to expand...
Click to collapse
ahh, yes I used the old 1.5 adb. I forgot they had released the 2.2 sdk. the updated version works great. well thanks for reminding me
You don't need any new sdk.
This is the way to do it:
If you have a linux workstation, great. Otherwise, popin a bootable CD, boot into the system, open a terminal, plugin your HTC, and do a:
# dmesq | tail
You'll get a pcid in the format of 0bb4:xxxx where xxxx is the new pcid you need to replace in the adb usb driver inf.
That's it.
Here's a sample output:
[ 5144.934366] usb 2-1.3: Product: Android Phone
[ 5144.934367] usb 2-1.3: Manufacturer: HTC
[ 5144.934369] usb 2-1.3: SerialNumber: HT999L903279
[ 5145.681192] usb 2-1.3: USB disconnect, address 16
[ 5145.863757] usb 2-1.3: new high speed USB device using ehci_hcd and address 17
[ 5145.962591] usb 2-1.3: New USB device found, idVendor=0bb4, idProduct=0c98
[ 5145.962596] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5145.962599] usb 2-1.3: Product: Android Phone
[ 5145.962600] usb 2-1.3: Manufacturer: HTC
[ 5145.962602] usb 2-1.3: SerialNumber: HT999L903279
works on xp 64
Got this fully working on Windows XP x64 with HTC Hero running Android 2.1. Thanks alot, I've tried many ways to debug my device on XP 64 and all of them ended with "adb devices" showing nothing.
I had to expand "amd64\android_usb.inf" a little bit.
Following lines at the end of [Google.NTamd64] section:
Code:
; HTC Hero
%USB\VID_0BB4&PID_0C98.DeviceDescRelease% = androidusb.Dev, USB\VID_0BB4&PID_0C98
%USB\VID_0BB4&PID_0C98&MI_01.DeviceDescRelease% = androidusb.Dev, USB\VID_0BB4&PID_0C98&MI_01
Following lines at the end of [Strings] section:
Code:
USB\VID_0BB4&PID_0C98.DeviceDescRelease="HTC Hero"
USB\VID_0BB4&PID_0C98&MI_01.DeviceDescRelease= "HTC Hero Composite ADB Interface"
If you have something else than HTC Hero or HTC Dream — just replace "VID_0BB4&PID_0C98" with your device IDs.
Lendarel said:
Got this fully working on Windows XP x64 with HTC Hero running Android 2.1. Thanks alot, I've tried many ways to debug my device on XP 64 and all of them ended with "adb devices" showing nothing.
Click to expand...
Click to collapse
I hope you realise that if you download the latest HTC Sync it installs x64 drivers correctly and then you just have to start using adb for it to work. The guide linked in my signature also shows you how to set it up to run every time you start your computer so that you can run it from any command prompt without having to change location. This thread is more or less dead.
Related
I have been doing Android development for a while on my work laptop that runs Windows Server 2003 64bit. Previously I've used a HTC Magic (AT&T) and a Moto Droid (Verizon) for development. Now I also have a EVO that I am trying to use. The problem is that I cannot get ADB to work with it.
System: Windows Server 2003 64 bit (work laptop, no I cannot put Windows <whatever else> on here).
Phone: EVO
Since I have been doing development for some time I already have the SDK, along with the USB drivers.
Here are things I have tried:
1. Plug in EVO. It wants to install ADB drivers. I choose the USB drivers location. Fails.
2. Delete USB Drivers. Redownload them from the SDK. Plug in, choose drivers, fail.
3. Plug in, allow drivers to fail, I have the ! in device manager for ADB. Unistall the ADB driver. Scan for hardware changes. Install ADB drivers. Fail.
4. Uninstall the Motorola USB Driver package. Try all above steps, fail.
5. Try to install HTC Sycn, Server 2003 not supported, fail.
What else can I try to get ADB working? Seems funny that it would work perfectly with a HTC Magic and a Droid but not this EVO.
Eureka! I found an obscure post on some crappy forum to a link for what someone called HTC Evo 64 bit drivers, so I thought what the hay, lets try them.
http://depositfiles.com/en/files/yd61xorii
The folder of drivers in there was really called Vista x86 but, still worth a shot.
It worked perfectly. The phone doesnt say ADB in device manager now but "My HTC". ADB is working fine.
Hopefully someone in the same boat as me will happen across this and it will save them time.
Thank you! Saved me a BUNCH of time! You're the man!
The file appears to be unavailable on that site now, could someone please re-host this ASAP? I can't get anything else to work and I'd really appreciate it if this turned out to be my fix. Thanks.
weidong said:
The file appears to be unavailable on that site now, could someone please re-host this ASAP? I can't get anything else to work and I'd really appreciate it if this turned out to be my fix. Thanks.
Click to expand...
Click to collapse
just grab HTC Sync from the HTC www site. It will install the drivers you need.
frankenstein\ said:
just grab HTC Sync from the HTC www site. It will install the drivers you need.
Click to expand...
Click to collapse
not always. I had to search for drivers for mine too. HTC Sync (latest rev on website) wouldn't work. Android SDK wouldn't work.
Still neeeeed help!
frankenstein\ said:
just grab HTC Sync from the HTC www site. It will install the drivers you need.
Click to expand...
Click to collapse
twin001 said:
not always. I had to search for drivers for mine too. HTC Sync (latest rev on website) wouldn't work. Android SDK wouldn't work.
Click to expand...
Click to collapse
downloadin HTC Sync made it worst. i had some htc evo drivers just not the ADB driver. After downloading now i don't have any drivers with my htc evo.
since i cant connect my evo to pc it will not automatically install the drivers!!!!!!
is there any way i can manually download the htc evo drivers to windows 7!
im back to normal i can read my sd card and i can connect to pc thank you all
bboy_201 said:
downloadin HTC Sync made it worst. i had some htc evo drivers just not the ADB driver. After downloading now i don't have any drivers with my htc evo.
im back to normal i can read my sd card and i can connect to pc thank you all
Click to expand...
Click to collapse
I can't connect on VMWare Fusion and Windows 7. How did you fix your problem? Did you find drivers? Thanks.
wow. never had a problem on windows 7 or ubuntu getting the evo to be recognized. but, head to work, plug it in, and no go. install the sdk and update it, no go. i was baffled, because i've never had a problem before. but, this file did the trick! thanks!
Unfortunately for those of us who are behind a proxy and can't get at the SDK file, going through the stupid SDK to get the driver is very annoying.
pcm2a said:
The folder of drivers in there was really called Vista x86 but, still worth a shot.
Click to expand...
Click to collapse
Didn't work for me. I'm running Deck's 4.0.3 ROM and can't get my device recognized on my computer. I tried to install the driver pack above through device manager and got an "unable to install" message. Any advice?
I have been searching for several hours, and I am absolutely unable to get ADB to recognize my phone using Windows XP 64 bit. I have uninstalled and re-installed the Unrevoked modified drivers several times to no avail. All I get is "Error: Device Not Found". Does anyone know a trick to getting ADB working on XP 64? I appreciate any and all help.
Thanks!
EVO HW 0003
HBOOT 2.10
MIKFROYO 4.4
Make sure the rom your using has adb functionality included/enabled in the rom.
And make sure usb debugging is enabled under settings/applications
Swyped from a galaxy far far away......
I have connected to the same phone with another computer. All settings are confirmed correct on the phone itself.
I know a trick, but I haven't tried it with the Evo or XP! I bet it works though. I used it to get my hero working with win7 last march, and it worked great.
install PDAnet.
It is a tethering program and has the ADB drivers, should set them up for you.
Also installing HTC sync is supposed to get the drivers working.
Thanks I will give that a shot and report back.
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Windows sucks and 64 bit XP is a pain in the ass. You need a usb driver or linux.
sixspeeder said:
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Click to expand...
Click to collapse
can u post the driver.?
Here it is. Be sure to uninstall any other drivers. I used USBDeview to uninstall the old drivers. Extract this zip and use the driver inside for Android 1.0 when prompted. It will not show up as Android ADB in Device Manager (showed up as My HTC Phone or something on mine) but ADB connected immediately once I installed this driver.
I doubt that it will work
Works for me!
Been looking at this for two hours now...
Running 64-bit XP - Installed the drivers manually by connecting the device, then selecting not now.... navigated to the drivers, installed BOTH .ini files - not sure if was really two different drivers or not - restarted, reconnected and device showed up.
The name my device function says "Desire" but it seems to work so far (only one sync)
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
crazyg0od33 said:
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
Click to expand...
Click to collapse
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
andybones said:
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
Click to expand...
Click to collapse
So just install and plug my phone in and the drivers will be installed?
Sent from my HTC6500LVW using Tapatalk 4
EDIT - that didnt do anything
Looks like I need to try something else...
crazyg0od33 said:
EDIT - that didnt do anything
Looks like I need to try something else...
Click to expand...
Click to collapse
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
andybones said:
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
Click to expand...
Click to collapse
My BMP is the same but my HTC Driver Installer is 4.0.3.001
Maybe I can find that other one and it will work for me
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
eL_777 said:
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
-snip-
-eL
Click to expand...
Click to collapse
Yeah I'm going to try it out on my roommates laptop that only has samsung drivers and the ADB installed and see what happens. Can't reformat the PC cause it's my School desktop and I've got work on there.
Once my macbook pro comes back from repairs I'll use that though, since I've never had issues running adb commands on my mac
Found a soultion
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
gald said:
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
Click to expand...
Click to collapse
MPT USB Drive isnt one of my options
However I've found that it's microsofts USB3 drivers, which override the Intel ones.
I just got my macbook back from repairs and it has USB3 ports as well so I was worried it wouldnt work, but its working fine from there
I'm having this same problem and nothing I do is working. I even tried from another computer but had no luck. adb finds the phone fine but fastboot just won't work. This is keeping me from getting S-Off. Someone please help.
Edit: Nevermind I think the issue is that I'm using Windows 8.1
I'm having the same problem I'm windows 8 64bit...
I have a nagging feeling that it's pda net.. I need to look into it today sometime
Sent from my HTC6500LVW using xda app-developers app
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
kinglime said:
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
Click to expand...
Click to collapse
I just experienced the exact same issue following the same steps on my laptop also running 8.1
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
gzbrambila said:
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
megaorange1 said:
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
Click to expand...
Click to collapse
From all of my research, you're the first person I've heard of having it working. Any specific drivers used? I'm very curious (currently, I have to use a backup machine to push TWRP updates to my VZW One)
Same thing here. 8.1 broke fastboot. Is this a Microsoft problem specifically because if it is I seriously doubt they will be in a hurry to patch it.
Sent from my HTC One using Tapatalk
I have found out something based on the VMware experience. Can somebody try it out and report back???
I feel that the fastboot problem in windows 8.1 is related to the USB port.
For those people that having problem, are you guys using USB 2.0??? If yes do you have USB 3.0 port in your computer??? The real problem maybe is that fastboot only works with USB 3.0 but not USB 2.0 in windows 8.1...
I tried both USB types, and half a dozen drivers and workarounds, and nothing.
I don't believe the dude above got it working. He is probably thinking Win 8, not 8.1. I have it working on 8.
Flash Image GUI will probably do everything you need to do in fastboot without the need for a computer. I just threw 8.1 on one of my extra PC's, I'll see if I can get the drivers going. I feel like this was answered in another thread though, I think it is in the rumrunner thread...
Just another reason why 8 is bad
cgskook said:
Just another reason why 8 is bad
Click to expand...
Click to collapse
fastboot was working on windows 8 and adb !!!
so the update win 8.1 have change sometihng but the question is what
and i try different drivers (from google,intelandroiddrv) and noting work
why have micro change something with drivers pffffff
kaverorzi said:
yep,definitely not working on Win8.1x64
Rooted a couple weeks ago on Win8x64, no issues.
Only noticed this issue today after I couldn't flash a different splash screen for my NuSenseOne.
Click to expand...
Click to collapse
I don't have the link on hand but there is a driver update to support 8.1 I have it working fine.
Sent from my HTC6500LVW using Tapatalk
i just used http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ and fastboot works on a 3.0 port on 8.1
I've just had this problem last week, and now got a solution...
Hi guys,
For anyone interested, due to something DreamerTKM said - I tried both USB 2 & USB 3 sockets on my Dell L701X laptop and both failed:
ERROR: Unknown USB Device (Device Failed Enumeration)
I did a clean install of Win 8.1 Pro and it still failed...
Anyway, I was using Windows 8.1 Pro default drivers for my system when this issue came up last week - default as in Microsoft's own out of the box drivers (drivers on the install DVD and Windows Updates) for my CPU chipset, USB chipset, etc... - my entire system (except for my nVidia graphic card!)
My laptop is now a few years old and my official "Dell" CPU chipset drivers are not compatible with Win 8.1, so I need to rely on Microsoft for these, but my USB 3 originally had Dell supplied "Renesas USB 3" drivers which I hadn't installed or even thought about installing as my USB 3 socket worked - and worked well...
...anyway, after installing the original Renesas USB 3 drivers the fastboot commands work once plugged into a USB 3 socket! USB 2 still wouldn't work though, but now my Win 8.1 laptop can do fastboot commands through a USB 3 socket.
I understand not everyone will have a Dell L701X laptop but the moral here is before blaming Microsoft and their Windows 8.1 O/S (which is truly awesome), try installing the correct drivers first!
DreamerTKM - thank you for putting me on the correct path with this!
Hopefully this post may help some of you!
solution
guyz if u r working on win8.1 just plug it in ur usb 3.0 then it will wrk...if u put in usb 2.0 it wont!
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
wex28 said:
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
Click to expand...
Click to collapse
Full fastboot and ADB support is available in windows 8.
Watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
morrowa2 said:
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
Click to expand...
Click to collapse
Also, there is this: http://forum.xda-developers.com/showthread.php?t=2703585