Unable to connect to adb daeomon on port:5037

Question

I have just installed the android studio, But my "Hello world " App is not running in emulator, It's showing the Emulator error - Unable to connect to adb daemon on port 5037

Cummerbund

Answer 1

1.) You can restart adb manually from command prompt

  run->cmd->your_android_sdk_path->platform-tools>

Then write the below commands.

adb kill-server - To kill the server forcefully

adb start-server - To start the server

F:\android-sdk-windows latest\platform-tools>adb kill-server
F:\android-sdk-windows latest\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Hairworm

but got this one error - The program can't start because api-ms-win-crt-heap-|1-1-0.dll is missing from your computer. Try reinstallling the program to fix this problem. – Cummerbund

I have added new image of erroe, for fixing this I have added these files in system 32 and sysWOW64, but still am getting same error – Cummerbund

thewindowsclub.com/api-ms-win-crt-runtime-l1-1-0-dll-is-missing Follow instruction on this link may solve your issue – Hairworm

Answer 2

Go to platform-tools folder in appdata where adb.exe file resides.

Execute the following command:

adb reconnect offline

it worked for me.

Filbert

Answer 3

Sir , reinstall everything especially for Android Studio , reverse to older version if that's available , update to newest version if that's unavoidable

Aerophyte

Answer 4

I had two Android Studios running (Stable and alpha). Closed both of them and then re-opened one, and was good again.

Robillard

Answer 5

What worked for me was wiping the data of the emulator.

emulator -avd Your_Device_Name -wipe-data

Alphaalphabet

Answer 6

just do 2 things into your terminal below:

adb kill-server

adb start-server

write above 2 lines into your terminal problem will resolve. thanks

Pyrimidine

Answer 7

For me on time all adb commands were "stuck" and did not work at all. Not even adb kill-server did execute. It failed with the following error:

could not install *smartsocket* listener: Address already in use

* failed to start daemon
adb: failed to check server version: cannot connect to daemon

I noticed that I had several adb processes running in the background, all trying to listen to port :5037 of course, which was already busy. What helped for me was to kill the adb processes running in the background.

After killing all of them off everything worked fine and adb devices would discover my emulator again.

Come

Answer 8

I've got simmilar problem but in my case I had to run adb attached to all network interfaces.

To do it, simply run the adb with -a flag like below

adb -a start-server

Overlap