Hi all,
The cable/Internet went down for some time last, week so I thought I would try the USB tether... But I got a driver not found... (Wifi hotspot worked fine without any problems)
The computer is Windows 7 64-bit.
After some searching I found this thread:
http://forum.xda-developers.com/showthread.php?t=793102
And I fixed it that way, as in the instructions there. Thought I would make a note of it here, to save people the problem of searching.
Basically - I downloaded the USB driver from the Android SDK, then went into the inf-file and updated the vid/pid from what the device manager presented (under the amd64 section): VID_0BB4 PID_0FFE
I had to set this up on another computer, and I thought I would just package up the stuff, so that anyone else that needs this won't have to go through the same hassle (install Java SDK, set up Android SDK, download driver, edit install file...)
Attached here is the google-usb ADB driver from the SDK, as downloaded December 26th. The INF file is edited to support the HTC Vision (or at least the Desire Z).
Use Linux. :3
Related
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!
Hi guys
I did own a Sapphire/Magic back in the days and came back to Android after some skipping done during the last year. Back then installing usb drivers and adb was easy: plug in the Sapphire, point Windows to the drivers folder, done.
With the Vision/Desire Z it was much more complicated. I did use the old drivers from back then and ran into problems. Device manager had an ADB device listed, ADB couldn't find it though. Once I got it working in Android, it wouldn't interface with the recovery adb though. Once I got that working, it wouldn't show/mount the SD card anymore. Short: a huge mess.
Right now I have everything more or less working (still using the old drivers I used with the Sapphire) but it's not really right, I tried an RUU the other day and it would fail because my ADB/RUU ADB/Driver combination wouldn't match.
Long story short: where did you guys get your drivers from to interface the Vision with ADB/Fastboot?
Update the SDK ...this time its in platform tools. run the sdk update and download the usb drivers. Refresh your SDK.
If you don't want to do that...then install pdanet just to grab the drivers
Or go to cyanogenmod the drivers may be avail in a post from ciwrl in vision.dz download section.
All right, I'm d/ling the Java JDK as prompted by the latest SDK installer
Thanks!
I did this too (SDK + Platform tools) to get ADB/shell. However, I never got fastboot to work (even tried fastboot-mac). Not sure what I was missing, but flashing via SD (including radio) has been working thus far for me. Any recommendations on where to get more info on "fastboot" process, specifically on a Mac?
Hmm... you did notice that the fastboot binary is - at least on Windows - in a different folder than ADB, right?
On Windows its two different paths pointing to either ADB or Fastboot.
[posted on the go]
I am unable to get USB connection working with my phone for development purposes. I have turned on the USB debugging and connected the device with USB cable and it does detect file transfer capabilities, but I am unable to get the ADB connection working.
I am running Windows XP SP3
It says it has found a device 'Galaxy' but is unable to install drivers for it.
What I have tried:
sdk/extras/google/usb_driver directory
I tried installing PdaNetA302.exe
I tried installing Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I selected 'install from specific location' -> choose a driver -> 'Android Phone' but it had none listed and the aforementioned driver directories did not work either when I selected them as 'Have Disk' options.
I also tried uninstalling all related devices and do the whole connecting thing again, but without success.
Help please?
SOLUTION
Apparently HTC drivers got in the way. After I removed all HTC drivers from my Windows XP, restarted and connected the device, the Samsung drivers kicked in and made it work.
To remove unused drivers from Windows XP you can follow this guide.
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
PdaNet
waylo said:
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
Click to expand...
Click to collapse
I had no end of problems getting adb and fastboot working for GN due to the usb driver problems.
After much Google-ing...
I installed PdaNet on my laptop and this installed all required drivers in the process of installing, you can then un-install PdaNet and the required drivers are still on your system.
I now have adb and fastboot working for both my Nexus One and Galaxy Nexus phones on my Windows 7 x64 laptop.
Hope this helps!
Thanks to XDA member el3ctrik for this tip!
Thanks, figured it out just after you posted. The PDANet drivers were the trick, in #3 below (don't need to actually run the installation in this case).
You'd think after 1.5 years of playing/hacking/unhacking/fixing and refixing the N1 I'd know how this is supposed to work.
A couple of comments, since some tutorials are based on older installations.
1. Installing android sdk. I went through a crapload of unnecessary trouble in trying to reinstall these, thinking that the usb drivers, adb, and fastboot needed to be updated. NO.
1a. In fact, in trying to reinstall the android sdk, you have to install the Java SDK. THEN, with the latest revision, R15, FASTBOOT IS MISSING! Need to pull that from a r13 zip.
2. You need the CORRECT samsung drivers. The ones mentioned above are the correct ones. I installed some limited half-ass versions which did not do the job.
3. You need FASTBOOT drivers. These were found from this post http://forum.xda-developers.com/showpost.php?p=9919944&postcount=1
which states:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
The #2 drivers let ADB see it when ICS is running, #3 (and probably #2 too) are needed while in fastboot. To get #3 installed, I had to go to device manager in Win7, hit update driver (next to the error exclamation mark device), and direct to these files.
That is all <whew!>
Glad you got it sorted out buddy, I was in exact same boat, years of Nexus One fastboot and adb use, but still had problems!
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Windows 7N USB driver issues
First post on this forum, so please bear with me.
I struggled for a few weeks trying to connect my new Samsung Galaxy Nexus (Rogers) to a 32-bit Windows 7 Ultimate N machine. The system wouldn't accept the drivers from Samsung - failed to recognize, driver software not successfully installed, etc. Tried all variety of proposed fixes, manually selecting the driver (have disk), downloading SDKs and ADB drivers.
Finally fixed it based on a very old suggestion from several years ago from an HTC user. The USB driver wasn't recognized in the absence of Windows Media Player being installed on the machine (a quirk of Ultimate N). Found the Patch from MS for WMP for 7 Ultimate N and the system immediately recognized and installed the Samsung driver and thus the Nexus is now connected.
Download my toolkit (ROM-Less), it will assist you in that manner!
It has easy instructions, and it will do most of the work itselff!
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
AMoosa said:
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Click to expand...
Click to collapse
Check this, it has all neccesary info/drivers for your device, including fastboot drivers!
Beatsleigher root helper (My toolkit) check it out
I'm trying to root my HTC Desire but falling at one of the first hurdles: I'm not able to install the driver software, I see the following error:
hxxp://i.imgur.com/5n720Wi.png
I'm running Windows 8 64-bit, and I'm trying to follow the steps to root as described here: androidforums.com/desire-all-things-root/300866-guide-rooting-htc-android-2-2-1-lower-unrevoked-windows-updated-20th-december-2012-a.html
I've installed HTC Sync and uninstalled HTC manager, and uninstalled Dropbox. I can connect to the Desire via USB both in HBOOT (with a successful USB connection message) and in regular Android OS.
I experimented with a couple other drivers - "Universal_Naked_Driver_0.72.zip" and "Acer_A1.win8.usb_drivers.x86_x64.rar" I found mentioned elsewhere.
Are there other drivers available? Any other advice for me to root this for the first time?
I have posted sometime earlier workaround to get it working on Win8, search.
Edit:
http://forum.xda-developers.com/showthread.php?t=1961823&highlight=windows+8+drivers
outofbandii said:
I can connect to the Desire via USB both in HBOOT (with a successful USB connection message) and in regular Android OS.
Click to expand...
Click to collapse
That's not right. Because your screenshot shows an Android 1.0 Device and this means the Desire isn't connected correctly.
Uninstall ALL about HTC and Desire. start the device manager and there activate in the options show disabled Device. Than you look in EVERY directory for Android, Desire, HTC. And remove the Drivers. right klick, remove and than yes and make sure if there is a option that says complete delet the driver say yes.
For Fastboot drivers:
Start Desire in Fastboot, and than you connect to the PC. Normaly Win 8 searches for Drivers. Than it says nothing found. Try in the Device Manager right Klick on Android 1.0 - If there is something about HTC Bootloader with an ! than you have an diferent problem - and research for drivers -> Internet. Than it normaly should work. If not download these drivers directly from unrevoke.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install directly from unrevoked.
and go to device manager, install drivers from PC. Also here make sure the unknown device is an Android 1.0 if the name is different pls tell us.
For Normal use:
after Fastboot works, you download the newest HTC Sync for Desire: http://www.htc.com/de/support/news.aspx?p_id=312&p_name=htc-desire
Ok run the installation BUT After you startet setup it says something like there are a few things missing befor installing. These are HTC Driver, something about Adobe, install these. After that the installer ask for some agreements for HTC Sync now you cancle the install, because all you need are the drivers and they are now installed. It should work now.
If there are some more problems let me know. I had some trouble with the ADB and fastboot drivers a week ago, too but now it works
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..