Mobile Developer: adb devices can not find equipment to solve.

Very depressed, recently decided to require an entire Android phone directly to the functionality of the software installed inside the project which studied the two days, found that the use adb you can easily practice, the key issue 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 conducted the operation, but do not open 360 mobile guards can not. First rule, driving the problem, the drive has been properly installed, and then exclude the phone debug mode, has been opened, or 360 useless ah. Then the exclusion of any hardware failure. Because the 360 phone assistant opened after I can use the ADB. Members seeking master teach me. . . .

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: quote 1 floor Aries_zz reply:

Oh, first of all I do not have Eclipse, the second I was not Andrews development, I simply wanted to own the software inside (VC) plus to plug in the computer's Android phones which installed software (even identify the phone has been installed what software ) 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 find, I can find ADB), the driver is definitely a fitted. . kill-server, start-server is 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 pea pods and the like)
3, closed process Some adb
4, to ensure that only one android device

Reply:

quote 3rd 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 pea pods and the like)
3, closed process Some adb
4, to ensure that only one android device

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

quote 4th floor woshisange03 reply:

Quote: 3rd floor shen332401890 quote reply:

First of all these points you first try

1. Open your phone inside the debug
2, close some phones supporting software (like pea pods and the like)
3, closed process Some adb
4, to ensure that only one android device

Is critical, open the phone inside DEBUG is referring to? It is to set the phone to USB debugging mode? ?

Yes
Reply:

quote 5th floor shen332401890 reply:

Quote: quote, 4th Floor woshisange03 reply:

Quote: 3rd floor shen332401890 quote reply:

First of all these points you first try

1. Open your phone inside the debug
2, close some phones supporting software (like pea pods and the like)
3, closed process Some adb
4, to ensure that only one android device

Is critical, open the phone inside DEBUG is referring to? It is to set the phone to USB debugging mode? ?

Yes

This certainly is open, otherwise it is impossible to even 360 phone 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 version 1.0.31?
Reply:

quote 8th floor sgzy001 reply:

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

Cross rub, right, indeed the adb version of the problem. Changed 1.0.31 on OK
Reply:
I used 1.0.31, why not ah, the landlord must be changed to say where the next ah. . . .
Reply:
I also met, life and death can not find the phone, solving ah:
Prior has been good, I do not know how is it so suddenly. . .

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

Demand cattle Weapon, thank

C: \ Users \ cc & gt; adb devices
List of devices attached

C: \ Users \ cc & gt; adb kill-server

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

C: \ Users \ cchen122 & gt; adb devices
List of devices attached

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

C: \ Users \ cc & gt; adb kill-server

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

C: \ Users \ cc & gt; adb devices
List of devices attached

C: \ Users \ cc & gt; adb version
Android Debug Bridge version 1.0.31

C: \ Users \ cc & gt;
Reply:

quote the 11th floor cc1949 reply:

I have met, life and death can not find the phone, solving ah:
Prior has been good, I do not know how is it so suddenly. . .

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

Demand cattle Weapon, thank

C: \ Users \ cc & gt; adb devices
List of devices attached

C: \ Users \ cc & gt; adb kill-server

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

C: \ Users \ cchen122 & gt; adb devices
List of devices attached

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

C: \ Users \ cc & gt; adb kill-server

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

C: \ Users \ cc & gt; adb devices
List of devices attached

C: \ Users \ cc & gt; adb version
Android Debug Bridge version 1.0.31

C: \ Users \ cc & gt;

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

Found C: \ Documents and Settings \ Administrator \ .android folder
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!
Reply:
usb debugging horse of God are open, and then put forward a 360 phone assistant horse of God, connect the phone while the phone out the window what RSA authentication check pc always trust that then OK, then off, then you can use adb I find, and I was like millet phone.
Reply:
# 14-floor method is effective
Reply: