I just went through a similar experience. In my case, I was using a computer that had reliably attached to several different Nexus One's previously, but two different Droids failed to be seen by ADB -- even though the devices enumerated properly (showed up in the device manager as Android devices) and even though the N1's were still able to be seen. I got past this by attaching a Droid, using the windows device manager to delete (not just uninstall, that didn't work) the driver, then the device moved to the "unknown devices" category. From there I told windows to install the driver; I pointed it at the same usb_driver directory that was previously installed, and things worked after that. No difference in the driver that I can see, but clearly something was different since it works now (and still works for N1).
On Mar 7, 1:14 am, Arun <[email protected]> wrote: > A call to Verizon helped. I had to reinstall the driver from: > > http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0... > > After reinstalling the drivers, adb devices started displaying the > device!. > > On Mar 6, 6:11 pm, Arun <[email protected]> wrote: > > > I got a new Droid. I connect it to the USB port of my Windows 7 > > laptop. One (Motorola A855) out of 4 installations failed. If I mount > > the SD card, i can access it from the file explorer. However, if I run > > "adb devices" the list is empty. > > I rebooted both the device and the laptop. > > > It is the same behavior both on XP and Windows 7. > > > I can see my HTC Hero with out any problem on both. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
