Android ADB Server failed to start

The following error was reported when launching Android Stdio:

12345

unable to create Debug Bridge:un Able to start ADB server:error:could not install *smartsocket* listener:cannot bind to  127.0 0.1 : 5037 : é Argon father jiao younger generation Kettle Lian Suite failed Ying 楀 ban 鍧? (Å corporate/network connection failed 鍦 board from/վ hani) Å è¡#̈亞 厑 optin pickaxe Jiao úã momma dress Rao °?? ( 10048 ) could not Read OK from ADB Server * failed to start daemon * error: Cannot connect to daemon D:\adt-bundle-windows-x86_64-20140624\sdk\platform-tools \adb.exe,start-server '  failed-run manually  if  necessary

Then the emulator list is empty and the emulator that was previously created cannot be found. Then Baidu inquires the next method, record.

The reason is that Port 5037 is occupied.

Workaround: Find out who is occupying a port and turn it off.

1. Open the cmd window and enter the folder directory where the Adb.exe is located.

such as CD D:\adt-bundle-windows-x86_64-20140624\sdk\platform-tools

2, netstat-aon|findstr "5037"

TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 5456

　　

Discovery 5456 takes up 5037 ports, continues to view 5456 of the task, and discovers that it is 360MobileLink.exe. as shown below

Tasklist|findstr "5456"

360MobileLink.exe 5456 Console 1 23,240 K

　　

The next problem is solved, in the task Manager kill 360MobileLink.exe, run the Android program, OK.

Android ADB Server failed to start