Reputation: 71
I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet. (I have Windows XP) Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site: http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears. On the Eclipse console, I get the following message: [2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great. I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.
Upvotes: 7
Views: 6192
Reputation: 17
I had this same problem. Do the following:
Plug your phone into your computer and:
- Run the command prompt.
- Go to the tools location of the android sdk.
- run 'adb kill-server'
- then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module
Upvotes: 1
Reputation: 1
Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe
and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.
Upvotes: 0
Reputation: 13154
Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.
Upvotes: 2
Reputation: 577
I had this same problem. To get it working, do the following:
adb.exe
program.Run adb devices
from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.
Upvotes: 13
Reputation: 20036
I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.
Upvotes: 0
Reputation: 10669
Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem.. link text
Upvotes: 1
Reputation: 17781
It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices
again. You can also check your system logs for errors - run compmgmt.msc
and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe
? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.
Upvotes: 2