如下:

1. Unplug the usb and plug it back again.

2. Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it back again.

3. Restart the adb on your PC. adb kill-server and then adb start-server

4. <<>Restart>/strong> 您的装置并再次尝试。

为了完成先前的回答,另一个可能的解决办法是改变你电缆铺设的USB车面。

I had this problem (with the classical answer about using adb kill-server / start-server not working) and it solved it.

实际上,需要一些时间才能发现,因为Windows在我的第一卷中正确地承认了这一装置。 但非亚行。 由于Windows正在确认该装置,我实际上没有必要测试其他USB的体积。 我本应该这样做。

So you can try to plug the cable in all your USB physical sockets directly available on your computer. It did worked for me. Sometimes the USB sockets are not managed the same way by a computer.

从< Andersstrong>4.2.2开始,你必须在您的装置上确认,该装置正附属于一个可信赖的计算机。 它将使用1.0.31及以上版本。

 adb kill-server
 adb start-server

解决我的问题

I ve had a similar issue with one of my phones. I was unable to connect and use usb debugging on any of my computers. In the end, I had to restart the usb debugging on the phone manually [doing so using the Developer menu was not enough].

只有一个指挥员必须用你的电话接听[我用<条码>定期发送<>条码>。

这就是说。

希望有助于未来的人。

http://developer.android.com/tools/help/adb.html。

更换装置。 这总是将它保留在澳门特区,而adb death-server则不适用。

关于我的Galaxy Nexus with 4.2.2,我最初也存在同样的问题,用燃烧装置显示器具,但具有脱线状态(USB debugging最初在我的装置上活跃)。

这些是我为纠正这种情况而采取的步骤:

1. Disable USB debugging (Device not connected to PC)
2. Re enable USB debugging
3. Now connect to your PC, now a pop up on the device (not on PC) will ask you for authenticating the PC, Thats it...

adb devices now lists both device id and no offline.

I post here my question just in case is helpful for somebody else. My problem was that my colleague was connected to the same device and I was not able to connect to the same device.

注:我在Wifi上空接连的上有这个问题。

有两个解决办法:

Easy to "drop” his connection (sorry buddy :)

Restart the device
adb kill-server
adb start-server
adb connect device-ip

www.un.org/Depts/DGACM/index_spanish.htm 略微困难,但有两个客户可以使用同样的装置。 (使用不同的TCP港口)

请参看https://stackoverflow.com/a/30912863/2000162>answer。

For me with Android 4.1.1 only rebooting device works

操作SDk管理员和安装了Andan SDK工具和AndenSDK平台工具。 亚洲开发银行必须更新为4.2.x的新版本。

I had the same issue and none of the other answers worked. It seems to occur frequently when you connect to the device using the wifi mode (running command adb tcpip 5555 ). I found this solution, its sort of a workaround but it does work.

1. Disconnect the usb (or turn off devices wifi if your connected over wifi)
2. Close eclipse/other IDE
3. Check your running programs for adb.exe (Task manager in Windows). If its running, Terminate it.
4. Restart your android device
5. After your device restarts, connect it via USB and run adb devices . This should start the adb daemon. And you should see your device online again.

这一进程几乎是漫长的,但它是我每次工作的唯一进程。

如果在客户的机器上安装,他就会发现通过 时间：2014-10-22 08:34:14

~/local/opt/Android/Sdk/platform-tools/adb
Android Debug Bridge version 1.0.32

adb version   
Android Debug Bridge version 1.0.31

apt-cache show android-tools-adb  | grep Version
Version: 4.2.2+git20130218-3ubuntu23