[Solved] Problems with adb.exe – AdbHostServer.cpp:93: Unable to connect to adb daemon on port: 5037

I have a problem with adb.exe of Android Studio 3.4.

When I run the emulator, I get this error:

Emulator: emulator: ERROR: AdbHostServer.cpp:93: Unable to connect to adb
daemon on port: 5037

I opened a terminal with the rute of the adb.exe: C:UsersChristianAppDataLocalAndroidSdkplatform-tools

And here I tried with adb kill-server and then adb start-server and I get this:

*daemon not running; starting now at tcp:5037
*daemon started successfully

When i run again the same error appears, i get this in terminal with the command adb devices:

List of devices attached
emulator-5554   offline

I emulate Nexus 5X API 28 with System Image: Pie 28 x86 Android 9.0.

I download the last version of abd.exe in for Windows

I also reinstalled the Android Studio and the emulator, but the error still appears.

How can I solve that?

Solution #1:

You need to first run adb start-server and then run emulator -avd <avd_name>

Respondent: Uddhav Gautam

Solution #2:

I had this happen with the following Event Log entry:

Emulator: emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037

So I opened command prompt as administrator and ran netstat -a -b >c:connections.txt and found the following:

 [Amazon Music Helper.exe]
  TCP         jbiss-PC:0             LISTENING
  TCP         jbiss-PC:54858         ESTABLISHED
  TCP        jbiss-PC:5037          CLOSE_WAIT
  TCP        jbiss-PC:5037          ESTABLISHED

So I shut down Amazon Music Helper, shut down and restarted Android Studio and then launched the emulator. It works now. I’m not sure why I started having this problem today, I assume that Amazon Music Helper was involved previously and the status indicated ESTABLISHED for adb.exe, but I did, and this process cleared it up for now at least.

Respondent: Jeff

Solution #3:

If you have any port utilizing software like Xampp, Vmware workstation, or virtual box
they normally utilize the port through which the Android Studio can access the devices.

  1. On your Android Studio interface click on Assistant
  2. It will show you Troubleshoot your connection
  3. click on next until you see Restart ADB Server
  4. do that until it restarts.
Respondent: kis Aar

Solution #4:

I had this with flutter. I updated Flutter and Dart to latest version and it resolved.

Respondent: Abhi R

Solution #5:

Close emulator and then Cold Boot that virtual device. And then try again.
Here is the link to catchup how to Cold Boot emulator.

Solution #6:

  1. Check JAVA_HOME, NODE_HOME and ANDROID_HOME paths in environment variables. If they are not available, set them.

  2. Cold Boot your emulator.

  3. Kill appium server session if it is running. Then re-run the appium server

  4. Run your program through IDE

Respondent: shiva kumar

Solution #7:

I did add this AMD VM installation. Some how I feel that its working how. But few errors still exists. Few Port error has gone.

This error still there while the port access error has vanished.

Emulator: socketTcpLoopbackClientFor: error: fd 60640 above FD_SETSIZE (32768)

Surprise thing is that the same was working in Similar Laptop HP with Ryzon processor few days back. My old laptop crashed and its a new one. Different between the LT is just 8/16 GB ram. Older LT has McAfee while this has Windows defender. I added the adb.exe process in the Exclution list in Windows Defender now.

Respondent: Arindam

Solution #8:

I had this with react native. This worked for me.
1 – Open Android Studio
2 – Click AVD Manager
3 – Click On Icon right to the emulator(that you want to run)
4 – Click cold boot

once emulator restart run your app it will works.

Respondent: Shakeel Haider

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Most Popular

To Top
India and Pakistan’s steroid-soaked rhetoric over Kashmir will come back to haunt them both clenbuterol australia bossier man pleads guilty for leadership role in anabolic steriod distribution conspiracy