Related
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Install HTC Sync, then reboot your computer
JvIo55iBl3r said:
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Click to expand...
Click to collapse
I did, actually. As a matter of fact, i do have that sync icon in my task bar
I am not sure, but i was wondering if the adb driver is necessary to be installed?
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
adseguy said:
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
Click to expand...
Click to collapse
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
JvIo55iBl3r said:
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
Click to expand...
Click to collapse
this should definitely be in the Q&A board, not the developers board.
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Exit HTC sync first on your computer so it is not running or just uninstall it. It should find it after that.
joeykrim said:
this should definitely be in the Q&A board, not the developers board.
Click to expand...
Click to collapse
Sorry about that, will do next time
joeykrim said:
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Click to expand...
Click to collapse
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
JvIo55iBl3r said:
Sorry about that, will do next time
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
Click to expand...
Click to collapse
any help? anyone?
I'm having a problem that is affecting two different computers, both of them gives me a 'adb device not found' message and it won't list my G2 when I typed in 'adb devices', the only difference between them is that in my laptop it gives me a message that it couldn't successfully install 'ADB'(Windows 7 Home 64 Bit) while my older Windows XP SP3 desktop gives me no such message.
Before replying, please note that I have Checked USB debugging and have done everything in the ADB for dummies thread, which includes the adding the tools part to Path and I have reinstalled my drivers more than five times (with and without USBDeview), each time with a different method. I am not mounting my SD card. I have also tried the PDAnet method. I have modified the android_winusb.inf file and reinstalled it. Tried uninstalling my USB Root Hub's as suggested by another. I have updated my USB Driver in SDK to rev 4. There aren't any yellow checkmarks in my Device Manager, however I have noticed that I only have 'Android Phone' and the subcategory 'Android Composite ADB Interface', I've heard that I should see another category like 'ADB Device Driver'. I have tried to fix this problem for five hours to root my G2, any help would be appreciated very much.
Where did you get your drivers from ? In the guide at http://forum.xda-developers.com/showthread.php?t=865685 I suggest getting them from the HTC Sync software, not the SDK.
I walked a guy with Win 7 through this the other day, and it worked fine for him.
I know it sounds like a stupid question but is the adb.exe file in your tools folder? If not, try running an advance search and only in the titles search for "drivers". You should only get about 10 returns. The top one should have some files attached named tools. Download them and extract the files to your tools folder. Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
I second getting the drivers from HTC Sync and remember the desire z is the same a G2 so run the seach for desire z for htc sync.
Sent from my HTC Vision using XDA App
ddgarcia05 said:
Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
Click to expand...
Click to collapse
adb has been taken out of the latest version of the SDK "Starter" package (the 2.3 one). It used to be there in the 2.2 version. So now you have to run SDK Manager to install the platform-tools add-on, then you get adb. This is all in my updated adb guide
ddgarcia05 - I didn't have adb in my tools folder, however I don't believe that you need adb.exe in that folder, just in the 'platform-tools' folder or in the system-32 fodler. Thanks for trying.
steviewevie - Thank you so much! I found your adb for noobs thread and it seems that installing HTC Sync after uninstalling my previous drivers via USBDeview worked like a charm. I also didn't see that you had to add 'platform-tools' in the Path in the various other threads, so I did that too. +1 Thanks to your helpful thread!
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..
I was able to install the ADB and fastboot drivers for my Galaxy Nexus no problem (using both manually installed INF files and device manager, an the wugfresh toolkit), but when I do the same thing with the N72013, it just never recognizes my device in CMD or with the wugfresh ADB/fastboot test
Any idea what's happening here? I've tried in both Windows 7 and Windows 8
I've used the Google USB driver from the Android SDK, open SDK Manager and scroll to the bottom, check it to install.
- Sent from my Galaxy S3
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Let windows download the fastboot drivers from the network.
boot into fastboot, connect to pc
open up
win-r
devmgmt.msc
right click the 5x device and search network for drivers (or wherever that option is)
It'll come it with something like marshall london bootloader interface. That is fine, it works, it is for different phone that is also android based. The bootloader interface is the same.
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the very same problem when I first received my 5X. I tried every damn think on to get Windows 10 to see the device, including all listed here and manually installing the drivers downloaded from Google and various other sites. Installed various Windows 10 packages. Even LG driver packages. I believe the issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer. I'm willing to bet it would work just fine on 7 (did on every machine I tried). Eventually adb and fastboot magically started working but I still could not use MTP. The ONLY thing that got it working was, strangely enough, a reinstall of Windows 10 (chose to kept files/documents) and then updating with the Anniversary Update). I know that is like the LEAST desirable option.
Windows 10 is really just not great for this sort of thing.
stmims1124 said:
The issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer.
Click to expand...
Click to collapse
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
sfhub said:
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
Click to expand...
Click to collapse
Yeah, that's exactly how it's worked every other android device I've owned too-only had issues with this device and this particular Windows 10 machine. This machine is configured to get drivers automatically, but for whatever reason I just couldn't get this to work. Of course, this was just my experience but there have defintiely been other folks out there with similar (maybe not exactly the same) problems. It was infuriating!
I can't really comment intelligently regarding what Google may have done to fix this. I'm shaking my head to hear that their drivers for Nexus devices is missing the fastboot USB ID's for a Nexus phone lol
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
---------- Post added at 10:45 PM ---------- Previous post was at 10:34 PM ----------
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
Thanks to all, I've solved with Google -> Android Bootloader Interface and it seems it works.