adb devices can not find the equipment to solve.

adb not found equipment driver Andrews

Very depressed, recently decided to require an entire Android phone directly to the functionality of the software installed inside the project which studied two days and found that you can easily use adb internship, the key question here. My phone is connected to a computer. Only by first opening 360 Mobile Assistant (PC version), so you can re-use my adb shell display device name and perform operations, but do not open 360 mobile guards can not. First rule, driver problem, the driver has been installed correctly, and then exclude the phone debug mode has been opened, or 360 useless ah. Further exclude any hardware failure. Because the 360 ​​mobile assistant opened the future I can use ADB. Seek expert teach me. . . . <-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
You try this:
Try below steps:

1, Close the Eclipse if running
2, Go to the Android SDK tools directory in Command Prompt
3, type adb kill-server
4, then type adb start-server
5, No error message is thrown while starting ADB server, then adb is started successfully.
6, Now you can start Eclipse again.

it worked for me this way, Eclipse should be closed before issuing these commands.
Reply:

Quote: references to a floor Aries_zz reply:

Oh, first of all I do not have Eclipse, I'm not a second Android development, I simply want to own the software inside (VC) coupled to plug in the computer software installed Android cell phones (mobile phones but also to identify what software has been installed ) function, my idea is to use ADB ADB inside the hair command line parameters. But I could not find the phone, (other mobile assistant can be found after they found my ADB can be found), the drive is definitely fitted. . kill-server, start-server are done, useless, before the start of the process but also the ADB closed. And there is no error.

Reply:
First of all these points you first try

1, open your phone inside the debug
2, close some phones supporting software (like peas in a pod and the like)
3, the shutdown process some adb
4, to ensure that only a single android device

Reply:

reference to the third floor shen332401890 reply:

first of these points that you first try

1, open your phone inside the debug
2, close some phones supporting software (like peas in a pod and the like)
3, the shutdown process some adb
4, to ensure that only a single android device

Is critical, open the phone inside the DEBUG is referring to? The phone is set to USB debug mode? ?
Reply:

references, 4th Floor woshisange03 reply:

Quote: references to the third floor shen332401890 reply:

First of all these points you first try

1, open your phone inside the debug
2, close some phones supporting software (like peas in a pod and the like)
3, the shutdown process some adb
4, to ensure that only a single android device

Is critical, open the phone inside the DEBUG is referring to? The phone is set to USB debug mode? ?

Yes
Reply:

references, 5th Floor shen332401890 reply:

Quote: references to the 4th floor woshisange03 reply:

Quote: references to the third floor shen332401890 reply:

First of all these points you first try

1, open your phone inside the debug
2, close some phones supporting software (like peas in a pod and the like)
3, the shutdown process some adb
4, to ensure that only a single android device

Is critical, open the phone inside the DEBUG is referring to? The phone is set to USB debug mode? ?

Yes

This is certainly open, otherwise it is impossible to even 360 mobile assistant on my phone ah. .
Reply:
The landlord does not solve the problem?
Reply:
Adb version is not too much of it. You are using a version 1.0.31?
Reply:

reference to the 8th floor sgzy001 reply:

adb version is not too much of it. You are using a version 1.0.31?

Cross-rub, right, and indeed the adb version of the problem. 1.0.31 changed to OK
Reply:
I use 1.0.31, why not ah, the landlord must be changed to say where the next ah. . . .
Reply:
I also ran into, life and death can not find the phone, solving ah:
Prior has been good, I do not know how could such a sudden. . .

1 Restart the computer, mobile phone
2 Set the "USB debugging mode"
3 reinstall the device USB drive

Seeking large cattle Weapon, thank

C: \ Users \ cc> adb devices
List of devices attached


C: \ Users \ cc> adb kill-server

C: \ Users \ cc> adb start-server
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *

C: \ Users \ cchen122> adb devices
List of devices attached


C: \ Users \ cc> adb devices
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
List of devices attached


C: \ Users \ cc> adb kill-server

C: \ Users \ cc> adb start-server
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *

C: \ Users \ cc> adb devices
List of devices attached


C: \ Users \ cc> adb version
Android Debug Bridge version 1.0.31

C: \ Users \ cc>
Reply:

reference to the 11th floor cc1949 reply:

I have met, and life and death can not find the phone, solving ah:
Prior has been good, I do not know how could such a sudden. . .

1 Restart the computer, mobile phone
2 Set the "USB debugging mode"
3 reinstall the device USB drive

Seeking large cattle Weapon, thank

C: \ Users \ cc> adb devices
List of devices attached


C: \ Users \ cc> adb kill-server

C: \ Users \ cc> adb start-server
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *

C: \ Users \ cchen122> adb devices
List of devices attached


C: \ Users \ cc> adb devices
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
List of devices attached


C: \ Users \ cc> adb kill-server

C: \ Users \ cc> adb start-server
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *

C: \ Users \ cc> adb devices
List of devices attached


C: \ Users \ cc> adb version
Android Debug Bridge version 1.0.31

C: \ Users \ cc>

I, too, do the Great God, how to solve
Reply:
Technical aspects have not been resolved, but the issue is resolved, the method in this announcement, and you shoes Sharing:
Mobile Assistant software download mobile assistant or pea pods and the like, and then find the device, and then uninstall them. . . Then OK. . . Ha ha ha
Reply:
Open the device driver details, find the device's VID, such as the landlord's view of the device VID is 0x12D1


\ Documents and Settings \ Administrator \ android folder: find C.adb_usb.ini information, open. Add a line inside 0x12D1, save the file

Restart adb

Reply:
Thank you very much 14th floor jxbicestare answer is very useful!