Update 03/14/2012: The below process works for the Windows 8 Consumer Preview. If you need to modify the driver .INF to support your device, please read this post for instructions on disabling Driver Signature Enforcement in Windows 8.
It isn’t actually that difficult to get ADB (Android Debug Bridge) working correctly under Windows x64 (Windows XP 64bit, 7 and Windows 8 x64 are supported) – you just need to perform a few steps in the right order.
- Download the latest 32-bit and 64-bit Java JDK from here: http://www.oracle.com/technetwork/java/javase/downloads/index.html (click the JDK link).
- Install the 32-bit JDK first, then the 64-bit. Note — Technically you can just use the 64-bit version, but you will occasionally get errors about the 32-bit version (x86) being missing. Best bet is to install both. Both Java 6 and Java 7 are supported.
- Once Java is installed, download the Android development kit for Windows from here: http://developer.android.com/sdk/index.html – you can now opt to download the SDK install in .exe format, which is recommend (and will be used by this guide).
- After the installer has finished downloading, run it. If you haven’t yet installed the JDK packages, the installer will remind you that they are required and won’t let you proceed.
- The installer will automatically launch the Android SDK Manager and prompt you to install a number of default packages. Of those listed, only the first two options (Android SDK Tools and Android SDK Platform Tools) and the Google USB Driver package (located in the Extras tree, near the bottom of the list) are needed. After you have selected the packages you want, click Install (x) Packages. A new window will appear – any items without a green checkmark require that you select them, then click Approve before you can proceed.
- After the process has finished, allow the Manager to restart the ADB process, then close the dialog box.
- When it’s finished downloading and installing, enable debugging mode on your Android phone and plug it in. Windows should now automagically detect the correct ADB driver. Once Windows has completed the driver installation, open Device Manager and ensure that the “Android Phone” category at the top has an entry called ‘Android Composite ADB Interface’ (pictured below). If the driver wasn’t installed automagically and appears in Device Manager as a Nexus One (or whatever your model of phone is), you can find the driver downloaded by the SDK Setup in the folder you extracted the SDK to (by default, C:\Program Files (x86)\Android\android-sdk-windows\google-usb_driver).
- Finally, open a command prompt, navigate to the platform-tools directory in the SDK folder and type ‘adb devices’ — ADB should now list your device (note: adb used to reside in the tools directory, but was moved to platform-tools with Gingerbread. As of r16 (the ICS update to the SDK), fastboot is also now located in platform-tools).
Device Manager showing the ADB Driver is correctly installed
Note that some devices aren’t supported by the official ADB driver. Check the comments below for instructions on how to modify the driver INF to support your device.
[...] This post was mentioned on Twitter by laslow. laslow said: New Blog Post – Android: ADB on Windows 7 x64 – http://is.gd/cdh6i (as promised to @rikupw) [...]
[...] written a few articles about Android, and my opinion of the platform should be pretty apparent. So, I'm just [...]
Had huge problems installing this driver in 64-bit Windows 7. The problem proved to be that Google had removed the lines for HTC Hero from the inf file from revision 3. Added this to the inf file in the [Google.NTamd64] section:
; HTC Hero
%CompositeAdbInterface% = USB_Install, USBVID_0BB4&PID_0C98&MI_01
Just a tip to other Hero owner out there.
I’m running Windows XP Professional x64.
My Nexus One driver appears to install correctly (I pointed it to the SDK driver folder) and I get the “Android Composite ADB Interface” properly installed under “Android Phone” in Windows’ Device Manager.
But ‘adb devices’ does not list the target – despite the fact that another 32-bit machine happily shows it (running XP Professional x86).
The phone’s running Froyo (2.2).
Only difference is the x64 machine is running ‘Eclipse SDK v.3.6′ (the x86 box is on ‘Eclipse IDE for Java Developers v.3.5′).
I don’t think that should be the problem as (from my current understanding) the ADB is not dependent on Eclipse (it’s the other way round).
This might be something I’m doing wrong somewhere. Quite likely.
But thought I would mention my problems (in progress) as you referenced x64 XP.
I’m going to try Windows 7 x64 next as I am keen to get this up and running 64-bit… grumble, grumble…
There are a number of general compatibility issues with XP x64 for many different programs, and it’s entirely possible that ADB isn’t able to work correctly under the OS (like I said, I haven’t had time to test it). If I get a chance, I’ll make an XP x64 VM and try ADB to see what’s up, but it’s most likely that it just won’t work.
I think that’s definitely the case.
Late last night I finished the process of installing the Android SDK, Eclipse (this time 32-bit v.3.5.2 ‘Java EE IDE for Web Developers’) and the Android Plugin on my Win 7 x64 machine – all working well and debugging against my Nexus One.
Hooray!
Your article definitely helped. Thanks.
(oh yeah – I tried installing the 32-bit JDK on the XP x64 box as I had previously just installed the 64-bit JDK… still ‘adb devices’ showed me nothing at all)
[...] win xp 32bit machine haha. If anyone encounters the same problem with win 7 64 bit, follow this: Android: ADB on Windows 7 x64 LaslowNET Thanks a bunch… my phone is useful [...]
correct solution for HTC Hero:
I had the same problem. It seems that the device ID has changed for some reason.
For me it became “VID_0BB4&PID_0C99″
1. So, go to the folder which has the driver (it should be %somewhere%android-sdk-windowsusb_driver).
2. Make a backup of android_winusb.inf and open the original using a text editor (notepad, notepad++, etc).
3. Right at the end of the [Google.NTx86] or the [Google.NTamd64] section (depending on whether you are 32bit or 64bit), paste the following:
CODE
; HTC HERO 2.1 (Chungwa)
%SingleAdbInterface% = USB_Install, USBVID_0BB4&PID_0C99
%CompositeAdbInterface% = USB_Install, USBVID_0BB4&PID_0C99&MI_01
%SingleBootLoaderInterface% = USB_Install, USBVID_0BB4&PID_0FFF
4. Then try to install the driver normally when it asks you to.
If it still does not work, it means that you have a different device ID.
1. Go to the device manager (Control Panel -> System -> Hardware -> Device Manager in XP.)
2. Double-click on ADB (which should have an question mark next to it).
3. Select details.
4. From the dropbox select “Device Instance ID)” and copy the change the VID and PID in android_winusb.inf (just in the section you copied from above!) accordingly.
source: http://android.modaco.com/content-page/310369/04-jun-official-htc-2-1-3-31-751-1-chungwa-taiwan-multiple-repacks-online-kitchen/page/240/ (Post #255)
greetings
Here’s what I added for 2.2 in the usb driver file for my rooted Hero (Windows 7 x64)
; HTC HERO 2.2
%SingleAdbInterface% = USB_Install, USBVID_0BB4&PID_0C9A
%CompositeAdbInterface% = USB_Install, USBVID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USBVID_0BB4&PID_0C9A
successfully installed the driver by following this:
”
If it still does not work, it means that you have a different device ID.
1. Go to the device manager (Control Panel -> System -> Hardware -> Device Manager in XP.)
2. Double-click on ADB (which should have an question mark next to it).
3. Select details.
4. From the dropbox select “Device Instance ID)” and copy the change the VID and PID in android_winusb.inf (just in the section you copied from above!) accordingly.”
[...] I had to get the adb working on Windows 7 x64. I followed these clear instructions, together with a bit of .inf file editing as in the comments and it worked (summary: install x32 [...]
The INF line for the Desire is:
; HTC Desire
%CompositeAdbInterface% = USB_Install, USBVID_0BB4&PID_0C87&MI_01
Hi please can somebody write me a INF line fort Wildfire 2.2??
Thanks.
@Jerdan
;HTC Wildfire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C8B
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C8B&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
@Jerdan: Follow the steps in this article to get the VEN and DEV numbers, and then copy one of the lines above and change the numbers as appropriate (you need to have your phone connected to do this): http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Once you’ve got it, post it here to give others a hand.
Been having absolute masses of problems getting the ADB drivers to work with the HTC Desire on WIndows 7 64-bit, until I did the following.
Followed the above process to get the SDK installed, then added the following lines to the android_winusb.inf file:-
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&REV_0226&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01
Those are for my Desire (On Vodafone if that makes a difference). After adding those lines, the drivers installed straight away, and I can now use DDMS to capture screens. I added them to [Google.NTamd64] section, but I presume they would work in the [Google.NTx86] section too.
In Windows 7 64-bit, the “Device Instance IDs” mentioned above, is listed as “Hardware IDs”.
@LeeC22
My Hero!
I tried all the mentioned and unfortunately doesn’t work on windows 8 cons. prev. build 8250
Thanks for (your) everybody’s time
What part wasn’t working?
Awesome! Thanks!
[...] Java SE Downloads Select the JDK See also – http://laslow.net/2010/05/17/android-adb-on-windows-7-x64/ [...]
my pc is detecting my device but whrn i use apk manager it shows adb not found………pls help
What does ‘adb devices’ show for output?
Disire HD – windows 7 x86
;Google DHD
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0CA2
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0CA2&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
So I followed the instructions with one issue- I forgot to read the part about installing the JRE 32bit before the 64bit. now I can’t install ADB on my HTC Inspire 4G. Any help?
So when you check Device Manager, it doesn’t appears as in the screenshot? Does it have an icon with an ‘!’ in it for the ADB device?
Great
These lines worked for me finally on Windows x64 Pro
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&REV_0226&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01
Thanks LeeC22
Thanks Thomas/LeeC22 I can also confirm that the new entries you supplied for the HTC Desire worked for me also (UK T-Mobile).
well… this sucks… have to unistall the 64 bit java sdk and then reinstall the 32 bit sdk and then the 64 bit sdk!?! that is bs… I had the beta version of XP 64 when it first came out and this was the kind of problems I had – but that was 2006 or something… no progress? no thanks, I just wont debug on my phone. maybe when I have a couple days to make no progress I’ll do it. I am betting it is no where as difficult as the problems I had with beta xp 64 and finding drivers but just the thought of driver problems due to 64 vs 32 bit brings back a week of hell and I’ll just pass for now.
If you already have the 64-bit version of Java installed, just install the 32-bit and then the SDK. It should still work fine. The steps are in that specific order above to mitigate as many issues around install order as possible, but it will typically still work.
“If you already have the 64-bit version of Java installed, just install the 32-bit and then the SDK”
I got Windows7 Home Edition,Eclipse Indigo(2011 v-3.7)’Android ADT v-15(last one)
I did all the steps with the android_winusb.inf and AdbInterface ,I had that bad experience before (tablet Xoom)
Now my problem is trying the original motorola Droid with this laptop running
windows 7 64 bit.(adb devices:not devices attached)
I also installed the J2EE SDK 64 bits.
What means:just install the 32-bit and then the SDK(I only installed de 64 bits)
I was saying that, if you have the 64bit version of Java JDK installed, don’t worry about uninstalling it and going in order, just go ahead and install the 32bit version of Java JDK, then run the Android SDK and download the usb driver.
;Samsung Galaxy Nexus
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
After you’ve made the changes to the INF file, then what do you do? How do you get the changes applied to the driver?
You need to open Device Manager and manually update the device, pointing it at the directory containing the modified .inf. Lots of instructions available out there for installing drivers manually.
To modify inf file, you need to get correct hardware id of your android device. It’s in devmgmt.msc-> right click on ‘ADB’ (the unknown device since driver is not properly installed) -> property -> detail -> select hardware id in property list, the id is shown in the textbox below.
They you may edit your own version of CompositeAdbInterface define, remember to modify both [Google.NTx86] and [Google.NTamd64] sections.
Thank you so much, it work on Windows 7 x64 Ultimate