Related
I know its been asked before, but how do I take screen shots? A quick google search left me confused and looking here was like a needle in a hay stack.
Phone is not rooted, and I won't be rooting it either, so err suggestions?
I know this really should be in the Q & A Section
Thanks in advance
see http://myhtcdesire.com/tutorials/how-to-take-screenshots
i hope htc give us this feature without rooting like is available out of the box on the samsung galaxy s.
Download the Android SDK for your platform. Connect your Desire to your computer and enable USB debugging. Navigate to the tools folder of the SDK, and run ddms. Highlight your device and go to Device > Screen Capture.
Back to trying this today, Can't seem to do it, Im guessing because there is no driver for the ADB part, Suggestions?
I can't even get ddms.bat to load!
Tried this earlier & it worked great. Using windows 7
Bouncer5 said:
Back to trying this today, Can't seem to do it, Im guessing because there is no driver for the ADB part, Suggestions?
Click to expand...
Click to collapse
Try installing HTC Sync. My Win 7 was also missing this driver before I installed Sync. If this doesn't help I have to look a bit through my browsing history because on my work computer I don't have Sync and i managed to find some ADB driver that work.
Hi,
I have an O2 retail Galaxy Nexus. Before I began to use the phone I thought I would root it now.
I've read through the instructions and tips but unfortunately my PC can't find the drivers...
I could still access the phone so I opened the .bat for Windows Superboot.
CMD read < Waiting for Device> so I closed the cmd after waiting.
The phone now seems to be stuck on Fastboot Mode. Holding buttons or using the screen do not do anything.
This is my first Android device.
Is there a way for me to get back to normal phone mode until I sort the drivers?
I would be tempted to remove the battery if this were any other circumstance.
Will the older threads about Fastboot being stuck also work?
Thanks in advance.
I hit this myself and yanked out the battery to overcome it. Sorry if that's not what you want to hear, but I do now have a rooted device.
In response to fastboot freezing at <waiting for device> you need to install the fastboot drivers (these are not included in the root zip). Google around to find the best way to install them, I ended up installing pdanet onto my PC - as this has them included - and then removed the application after the drivers were installed.
Thanks for the reassurance, el3ctrik. Battery pull allowed it to boot normally.
Think I'll wait til the morning before trying again... Read some more articles, and try the pdanet method.
Ta!
I remember struggling with the drivers when I rooted my NS - I also ended up installing PDA net to sort out the issue.
Sent from my Nexus S using XDA App
I'm looking at buying a GNex for next to nothing, but the seller says it's stuck in fastboot. Came across this thread after a search, is this a fixable issue?
You need to install two drivers. Actually, it is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode.
I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, NOT the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...
PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.
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