FORUMS
Remove All Ads from XDA

Installing ADB USB driver for HTC Hero on Windows 7

35 posts
Thanks Meter: 1
 
By mpavey, Member on 25th July 2010, 06:56 PM
Post Reply Email Thread
Hi,

I recently bought my first Android phone, an HTC Hero, from a helpful eBayer here in the UK. When I got the phone, it had already been rooted and had a custom ROM, v4 RC1 of EzHero, installed.

I want to update this custom ROM to v5.1, because there are some problems with the current version that's installed. (For example, the phone doesn't ring because there are no ringtones installed! Also, the camera doesn't work, and the phone crashed and rebooted whilst I was in the middle of a call last night.)

So, after some reading around on these forums, I tried following the instructions on this thread: https://forum.xda-developers.com/showthread.php?t=709220. The basic first step is to download the SDK from Google and instruct it to download the USB driver. So far so good. (I am using Windows 7 BTW.)

However, I have been unable to get the USB driver installed correctly, such that when I run the command:
Code:
adb devices
I get nothing back. (Not strictly true -- the first time I ran it it said it was starting a daemon, then said something like "devices list", but listed no devices. The second time I ran it, it didn't mention the daemon, but still didn't list my device.)

When I connect the phone to my computer (via USB, and with USB debugging enabled), I basically get a balloon at the bottom right of the screen to say that it is installing drivers, and then it says it had some problems. It lists out several devices, each with a green tick or a red cross against them. Invariably, one of the devices listed is called simply "ADB", and it always has a red cross against it. I am not specifically prompted to point the system towards any drivers for the device.

If I go into Device Manager, I currently see, under "Other devices", three devices:
- ADB
- Multimedia Controller
- Multimedia Video Controller.
The icon for each of these has a little yellow exclamation mark. If I double-click on ADB, I am given the chance to Update driver. Doing this gives me two options, and I choose "Browse my computer for driver software". This prompts me to "search for driver in this location" and I choose "C:\android-sdk-windows\usb_driver". (I have also tried pointing it to the subfolder "i386", but this gives the same result. I am on a 32-bit Intel system.) There is also a checkbox "Include subfolders", again I have tried both options, and both lead to the same outcome.

I then click Next and receive this error message:

Quote:

Windows was unable to install your ADB

Windows could not find driver software for your device.

[...]

If, instead of clicking Next, I click "Let me pick from a list of device drivers on my computer" and then select "Mobile devices" and click Next, I am presented with a blank list and a button reading "Have Disk". Clicking on this lets me browse, this time, for an .inf file. But selecting the android_winusb.inf file gives the following error message:

Quote:

---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a

driver, make sure it is designed to work with Windows for 32-bit systems.


---------------------------
OK
---------------------------

This is about as far as I have got! I have tried experimenting with a couple of things, but with ultimately the same result:
  1. Running (as administrator) USBDEview and uninstalling anything that starts with HTC, or ADB, or Android, or USB Mass Storage device
  2. Editing the .inf file using the modifications described below:

The first modification I tried is described in comment 44 of issue 1039 on the Android Google Code forum (link removed because I don't have permission to post external links!):

Code:
;HTC Hero
%USB\VID_0BB4&PID_0FFE.DeviceDescRelease%=androidusb.Dev, USB\Vid_0bb4&Pid_0ffe&Rev_0100
You can find / adapt those description with your material manager (look in advanced tabs)
To have a nice name of device, add at the end of file something like
USB\VID_0BB4&PID_0FFE.DeviceDescRelease="HTC Hero rev 0100"
The second modification I tried is described in comment 99:
Code:
[Google.NTx86]
; HTC Hero
%SingleAdbInterface%        = USB_Install, USB\VID_0BB4&PID_0C9A
%CompositeAdbInterface%     = USB_Install, USB\VID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
And the third is described in post 2 of a recent Android Developers Google

Groups thread entitled "cannot install USB drivers for HTC Slide, Android 2.1, Windows Vista 32 bit" (link removed because I am not allowed to post external links!). For this one, I consulted the information displayed when I go into Device Manager > ADB > Properties > Details > Hardware Ids, so the actual lines I added to the .inf file are as follows:
Code:
;HTC Hero 2.1 
%SingleAdbInterface%        = USB_Install, USB\VID_0BB4&PID_0C98&REV_0100&MI_01
%CompositeAdbInterface%     = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
I also tried a slight twist on this:
Code:
;HTC Hero 2.1 
%SingleAdbInterface%        = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface%     = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
since all the other devices in the .inf file didn't include the &REV_0100&MI_01 parameters for the %SingleAdbInterface% line.

Finally, I also tried various times to uninstall devices from Device Manager, e.g. ADB, the two multimedia controllers with exclamation marks against them, and USB Mass Storage Device (which does indeed have three lines on the Properties > Details > Compatible Ids screen, as advised by a blog post I found on the Android Simplicity blog entitled "How-To #0: How to Install Usb Driver on Your Computer" (link removed because I do not have permission to post external links!).)

I really can't think of much more to try, so would really appreciate any pointers, however small, from the experts!

Another option might be to give up on Windows and try doing the whole process under Ubuntu Linux, which I have installed under dual-boot. However, the instructions for updating ROMs/making backups/recovery/etc. appeared to rely on some Windows executables so I figured that could be a risky approach (especially given I know very little about how to work Linux...!).

Thanks for reading

Michael
 
 
25th July 2010, 07:07 PM |#2  
Senior Member
Flag Bournemouth
Thanks Meter: 19
 
More
Don't need them. Get the latest HTC Sync and install the My HTC driver and adb will work.
25th July 2010, 07:21 PM |#3  
OP Member
Thanks Meter: 1
 
More
Thanks for such a quick reply btdag!

Really? That would certainly make things a lot easier, however dreamersipaq does make a point of reinforcing how important it is not to have HTC Sync installed in his instructions:

Quote:

At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done)

[...]
Quote:

HTC Sync does not like to play nice with the reflash tool

[...]
Quote:

Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it)

Does this not matter after all?
25th July 2010, 07:31 PM |#4  
Senior Member
Flag Bournemouth
Thanks Meter: 19
 
More
To get adb working I just installed the latest HTC Sync and drivers and then added ;C:\Path\To\SDK\Tools to my Windows Environment Variables as described in this guide:
http://www.villainrom.co.uk/viewtopi...c370bf1afa64d0

no problems with adb since
25th July 2010, 09:48 PM |#5  
Member
Thanks Meter: 10
 
More
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
26th July 2010, 01:55 PM |#6  
OP Member
Thanks Meter: 1
 
More
Smile
Thanks for all the help.

I'm pleased to say I've now managed to install the update, and my phone is now ringing!

In the end I worked out that I did not in fact need ADB at all. Since the phone had already been rooted and had a custom ROM installed, it dawned on me that it must already have the requisite recovery image installed. And indeed it did. So all I had to do was install Titanium Backup, back up my apps and settings, also take a nandroid backup just to be on the safe side, and then factory reset/wipe and install the update. (And then restore apps and settings using Titanium Backup.) Problem solved!

As an aside, I think there is certainly scope for more 'newbie' documentation. (Or would this be on the Wiki, currently down?) I'm certainly very grateful to those who have taken the trouble to set out what they have learnt already, for the benefit of others. For example though, even after spending several hours searching and reading up all the newbie guides I could find, I still had to read between the lines quite a lot to work out what a 'radio' was, what purpose the recovery image serves, how ADB fits into the whole picture, why there are multiple custom ROMs available for the same version of Android and how to choose one, etc. Perhaps one day I will be advanced enough to attempt that myself!
29th November 2010, 02:03 AM |#7  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by CyberWalrus

As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!

Thank you very much! I was reading this trying to get my G1 to work and it did. Windows 7 x64 won't allow me to install the android_winusb.inf driver but droid explorer did.
10th March 2011, 07:42 AM |#8  
Junior Member
Thanks Meter: 0
 
More
Phone nor computer will recognize adb/usb
First of all, my is rooted but somehow the superuser.apk file is missing. When trying to activate wifi tethering it asks if the device is rooted. The answer is, yes! I can boot into recovery mode but I do not have a way to get the superuser to open without adb. Can anyone help me?
20th August 2011, 11:25 PM |#9  
Junior Member
Thanks Meter: 0
 
More
Question Unable to Instal ADB Drivers
I'm having similar issues trying to root my MyTouch 4G. I've been following steps on the cyanogen wiki website for this device, which refers you to their site's instructions for setting up SDK & ADB drivers.

I've downloaded the SDK zip file, extracted to the C drive and made sure file paths are all the same as per the instructions. When following the instructions under Windows, I've added to variable values ;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools (and double checked these folders on C drive to be sure they're accurate).

When trying to manually update device drivers for ADB, I select the file android_winusb.inf and get error: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

My device has USB debugging enabled and is in mass storage mode (I've read on other forums that this can fix).

Not really sure what else to try? Any way I can change the .inf file to make Windows recognize it? Running Windows Vista 64.
Post Reply Subscribe to Thread

Tags
adb, htc hero, install, usb, windows 7

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes