[Nexus One Q&A, Help & Troubleshooting] Psychopoddy:
Win XP x64 works with latest android driver (2013) wo problems

Hi all.

I registered to leave this info here, cause spent a full day for searching this and for expirements, and to say that latest android usb drivers WORK UNDER XPx64 EVEN WITH NOOK and without any difficulty.

See instructions below.

Most devices that I've checked work with usb adb + Xp x64 - without problems (HTC one V, Tablet Freetab 9702) except Nook simple touch - but it also works here via USB.

MAIN THING:

A.) adb interface usually ends on &MI_01 .

like USB\VID_2080&PID_0003&MI_01 or USB\VID_18D1&PID_4EE2&MI_01 etc

NOT USB\VID_2080&PID_0003 or USB\VID_2080&PID_0003&MI_00

B.) adb interface Windows usually detects in "Other Devices" section of dev manager, not in USB controllers. And with a yellow question mark.

---------------------------------

So

* Enable USB debug in dev, connect usb.

* Sytem > Hardware > device manager - look at Other devices.

Click on unknown device > Details> look at string. adb interface usually ends on &MI_01 .

For example for htc one V : USB\VID_0BB4&PID_0CE5&MI_01

REMEMBER these chars, you need it later.

if you have such evidences A. and B. - do next (if not, skip this block) :

1. Download Android SDK for Win 32bit (developer.android.com/sdk/index.html#ExistingIDE)

Yes for WinXPx64 - download 32bit - cause it most common and therefore more stable and tested

2. All as usual when installing ASDK - unpack, set paths thats all

(addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android).

3. Download latest android driver (developer.android.com/sdk/win-usb.html)

Unpack to any folder. (I tested driver from June 2013 - works ok on XPx64)

4. Double click on android_winusb.inf. Search for "[Google.NTamd64]" string and afterthat

add device id chars that u see in device manager, like that:

[Google.NTamd64]

%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0CE5&MI_01

5. Save android_winusb.inf file. Go to Hardware Wizard (automatically launched, if no, go to dev.manager > your device > "update driver" button) > Install from a list > Browse > show path to our android_winusb.inf .

If windows asks some files - browse files in "androiddriver > amd64" folder.

If driver NOT installed - check VID and PID in inf file and device manager - must be the same.

6. If driver intalled, press "win + R" on keyboard, type: cmd , than type: adb devices

If adb works > it shows:

"List of devices attached"

"xxxxxxx device "

If adb not work - it doesn show "xxxxxxx device" string.

-------------------------------

OK, now if YOU do not see "&MI_01" at the end of dev id. or you do not see yellow exclamation in "Other devices" for example for Nook .

1. In Nook (or another device) go to applications and start adbwireless app.

then exit from this app. U do not need to start wifi, or to enable adbwireless button just start this app and then exit.

If u do not have adbwireless app - you can download it from market (nookdevs.com/NookColor:adb_wireless).

It is for any devices, NOT for nook only,

2. Connect usb to PC. Now you will see that Windows Xp x64 detected new device in other devices section in device manager with "&MI_01" id.

So go to 1.

Oh, Nook only (nookdevs.com/NookColor_USB_ADB - read "II. Patch the USB Driver files" - title sounds so majestically in this case :) simply u have to create a txt-ini file with value 0x2080 in user folder, but smbdy call it "Patch the USB Driver". lol

---------------------------------

By the way adbwireless - another easy way to adb, not depended on OS. Easiest way imho.

But not all have wifi at the right time.

([oftop]:Why XP x64? It's a fastest OS among latest Windows.

I use it cause XP GDI (95% of all programs interface) render is hardware based (via videocard ) and Vista\Win 7\win 8 GDI is based on software render (cpu).

XP GDI is 4.5 times faster than Win 7\8 GDI. d2d is also slower than XP GDI.

If interesting - youtube.com/watch?v=ay-gqx18UTM and google "Tom2D: Text Output", - it visually noticeable in browsers (slow scrolling), in notepad (blinking text in all std Memo ctrls), while resizing and moving windows etc.

Imho indians programmers "have tried" :),

I play a lot of games, mostly shooters, for dx11 - I have Win 7 as second OS only for Batlefield and Crysis, but most games work on xpx64 wo any problem. Of course all programs work on Xpx64 both x32 (x86) and x64.

Work, Films (mostly 1080, use Potplayer (DXVA)). Internet, Games 98% of time on fast XP x64. + additional 15-20min battery on XP x64 on notebook (less services? )

And I see no reason to change it to a slower platform on CPU render, that need more resources but in fact functionality will remain the same. (cause I have same apps, same games, same browsers, same photoshops etc)

Its a marketing guys!

[end oftop]) .