could not connect to tcp:5037: cannot connect to 1

Question

Hi I am new to android I am not able to run adb.exe it gives me below error:

==>adb start-server
adb I  6108  5748 adb.cpp:219] Android Debug Bridge version 1.0.32
adb I  6108  5748 adb.cpp:219] Revision 09a0d98bebce-android
adb I  6108  5748 adb.cpp:219]
adb I  6108  5748 adb_client.cpp:126] _adb_connect: host:version
adb I  6108  5748 sysdeps_win32.cpp:742] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: No connection could be made because the target machine actively refused it. (10061)
adb I  6108  5748 adb_client.cpp:175] adb_connect: service host:start-server
* daemon not running. starting it now on port 5037 *
Cannot open 'nul': The system cannot find the file specified. (2)
* failed to start daemon *
error: cannot connect to daemon

What does this error exactly mean..?

Cannot open 'nul': The system cannot find the file specified. (2)  

What is this error..?

Answer 1

Check this answer which helped me. The issue might be with the latest unstable version of platform-tools.

adb cannot connect to daemon at tcp:5037

Answer 2

make sure you have installing your device driver and adb service and is activated USB debugging in android device -> setting -> developer options and must be could to see your device when you connected by USB port ( by this command : adb devices)

so when you connected by USB follow this Commands :

1-stay connect via USB
2-connect to your WIFI network (computer and mobile device both)
3-ping DeviceIP (must be have ping to your device)
4- adb kill-server
5-adb usb
6-adb tcpip 5556
7-adb connect "yourDeviceIP:5556"
8-adb devices (must be see two device names , one of them is by deviceIP:5556)
9-unplug USB cable

then it's Done! and you could to test your app

Answer 3

adb.exe might be corrupted , try to replace these files

ADB.exe
AdbWinApi.dll
AdbWinUsbApi.dll

from the latest SDK Platform-Tools for Windows

Answer 4

it seems your adb is listening in tcpip mode for connecting over wifi..kill the server using adb kill-server..start it again using adb usb

Else also try l-> Go to task manager and kill adb process. ..