问题
I am finding ADB extremely fuckle for my Droid 2. My computer is Windows 7 64bit and my Droid2 version is 2.3.4.
I have googled and searched Stack Overflow and found many people have a similar problem. But mine is a weird twist on it.
I can in fact connect my phone to my computer after a fresh install of ADB, however after I connect and run an app on it, the ADB connection dies and I cannot get it back.
I have tried the following:
- Reinstalling the Android USB driver, editing the .INI file to match my hardware ID
- Updating AVD to the latest addition. Same with SDK on Eclipse
- This did work at first, but the connection died after running 1 app
- Restarted my computer
adb kill-serverand tried to cycle through it that way- Forced shut down ADB through the task manager
- put ADB on my system variables path
- Switched all my USB ports and used 3 different USB cables, including the stock one and my Kindle one.
- Installing the Motorola Drivers (which I think does nothing. After I install it, my phone doesn't appear on my device manager.)
- I relied on the ones from
android-sdk\extras\google\usb_driver
- I relied on the ones from
- Restarted my phone (which worked once, but not the second, third, or fourth time)
- Made sure USB Dev mode was on (cycled that a few times too)
I am stumped. Here is the output of my logcat before ADB pooped on me:
09-13 17:34:39.709: D/UsbService(1469): WaitDevNodeClosedTimeout() 09-13 17:34:39.709: D/UsbService(1469): UsbEventHandler(), Received event: usb_devnode_closed 09-13 17:34:39.709: D/UsbService(1469): Current Usb State:USB In-Switch Wait DevNod Close State 09-13 17:34:39.709: D/UsbService(1469): ReadCurrentUsbMode() 09-13 17:34:39.709: D/UsbService(1469): Current Usb Mode: Motorola Phone Tools : E/(): Device disconnected
After this, it went completely dark, even after many reinstalling of the drivers, restarts, etc.
I have also tried to set up my ADB to connect to my phone over wifi, but it appears you need root access on your phone (as su or sudo does not work on the terminal emulator) and it also appears you have to go through a very risky flash to get that done. At least, that is what I read.
But, if there is a way to do this ADB connection over wifi without having to do a risky super-user hack, that would circumvent this fiasco too!
I suppose this is a 2.5 part question -- How to make the ADB connection stable or how to get ADB to work over wifi without needing Super user/root (or how to get Super user access without risking your phones life!)
回答1:
Okay I think I solved it. Basically, when you plug the phone into the computer, make sure it is in USB Mass Storage mode! Now, its been working consistently all night. So I think I got it.
来源：https://stackoverflow.com/questions/12417148/android-adb-not-connecting-to-droid-2