a wacky workaround to get Nexus One usb driver installed on windows 7

by monkey.jsun » Thu, 19 May 2011 12:18:20 GMT

Sponsored Links
 I have wasted almost a day trying to get my nexus one connected to my
Acer laptop running windows 7 professional 64bit. The basic symptom is
that even if I point windows driver update to where the driver
software is (SDK/extras/google/usb_driver), windows still says there
is no driver found.

I finally looked at the properties of "Nexus One" device and saw its
hardware id's are


So I add the following line to SDK/extras/google/usb_driver/
android_winusb.inf file (the one ends with <<<<<)

;Google NexusOne
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E12
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E22&MI_01

Include = winusb.inf
Needs   = WINUSB.NT

That does the trick! I think somehow window's usb driver is not
working properly on my laptop (probably due to VMWare) and did not get
the device id correctly. Or google's usb inf has a bug. I just want to
post it so that someone else may save time in the future.




Re: a wacky workaround to get Nexus One usb driver installed on windows 7

by Eamonn Dunne » Thu, 19 May 2011 21:32:53 GMT

 I'm pretty sure thats an issue with the VM, as I installed the drivers 
without issue on the same setup.


Sponsored Links

Other Threads

1. WST 3.1 does not allow editing of Android manifest

Hi all,

I am putting this up in the hopes that someone more knowledgeable will
know what to do with it.

If you have eclipse installed, and you have WST XML Core at 3.1, then
double clicking an android manifest file will result in

An error has occurred. See error log for more details.

Reverting back to WST 3.0.4 fixes the issue.


2. crt0.o


I've been trying to compile the Voidroid project (PJSIP client for
Android). I can't copy with one problem that constantly occurs while
building the PJSIP part: After running the command: ./configure --
host=arm-eabi in my PJPROJECT directory, I get the following error:

aconfigure: WARNING: If you wanted to set the --build type, don't use
If a cross compiler is detected then cross compile mode will be used.
checking build system type... i686-pc-linux-gnu
checking host system type... arm-unknown-eabi
checking target system type... arm-unknown-eabi
checking for arm-eabi-gcc... arm-eabi-gcc
checking for C compiler default output file name... aconfigure: error:
C compiler cannot create executables
See `config.log' for more details.

The config.log file says:
aconfigure:1822: checking for C compiler default output file name
aconfigure:1825: arm-eabi-gcc -O2   conftest.c  >&5
eabi-ld: crt0.o: No such file: No such file or directory
collect2: ld returned 1 exit status

What should I do to get this file? The Android source code has built
without problems...
I will really appreciate your help!
Thanks in advance,


3. Serious dx error. Desperately need expert advice.

4. apps to sd card

5. Serious dx error. Desperately need expert advice.

6. Serious dx error. Desperately need expert advice.

7. what's wrong in this code