adb identification equipment

            
Use adb devices command prompt the following error:
* Daemon not running. Starting it now on port 5037 *
CreateProcess failure, error 2
* Failed to start daemon *
error: cannot connect to daemon
This is what causes? ?

Reply:
You should first use lsusb, to see if there is a corresponding device, keeping in mind a number:
As follows: Device 004: ID 04f2:. B221 Chicony Electronics Co, Ltd, to remember 04f2
Then, add the configuration udev rules files, adjust the device file permissions
Create a rules file 50-android.rules
in / etc / udev / rules.dsudo gedit 50-android.rules

# Add something as:

SUBSYSTEMS == "usb", ATTRS {idVendor} == "04f2", SYMLINK + = "android_adb", OWNER = "lemon"
# Save & close window

ATTRS {idVendor} idVendor parameters obtained in the previous step
SYMLINK parameter enables the device file directory to add a connection point to the original device file
Users
OWNER of your current user, but also you run adb service
Reply:
Do not forget to turn on debug device
Reply:
Look no driver installed, there may be a driver problem.
Reply:
Is under WIN7.

cited a floor reply:

you should use lsusb, to see if there is a corresponding device, but keep in mind a number:
As follows: Device 004: ID 04f2:. B221 Chicony Electronics Co, Ltd, to remember 04f2
Then, add the configuration udev rules files, adjust the device file permissions
Create a rules file 50-android.rules
in / etc / udev / rules.dsudo gedit 50-android.rules

# ......

Reply:
Has opened a reference to the second floor

reply:

not forget to turn on debugging equipment

Reply:
Have been installed over the

referenced third floor reply:

look no driver installed, there may be a driver issue.

Reply:
Pea pod? 91? Is there a similar software conflicts
Reply:

reference to the 7th floor of replies:

peas in a pod? 91? Is there a similar software conflicts

never used pea / 91
Reply:
Task management, the closed adb
Then open eclipse
Reply:
Tried it again today, has been good. Do not know why. Thank you for the reply ......
Reply:
Investigate its source is the adb server did not start

After analysis are summarized as follows:

[Html] view plaincopy
C: \ Users \ xxxx> adb nodaemon server
cannot bind 'tcp: 5037'
The original adb server port bind failure

Continue to see in the end is which port to take up
[Html] view plaincopy
C: \ Users \ xxxxxx> netstat-ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 4236
TCP 127.0.0.1:5037 127.0.0.1:49422 ESTABLISHED 4236
TCP 127.0.0.1:49422 127.0.0.1:5037 ESTABLISHED 3840
Open Task Manager to kill off 4236 this process. ok

cmd execution

tasklist | findstr "4236"
Open Task Manager,
Find the process name,
Then the end of the process tree.

Done