Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

adb tcpip 5555 fails because no device is found

ErrorList of devices attached (nothing listed)

Short answer

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555. Run it over USB first, then unplug, then adb connect to the phone's IP address. Both machines must share a Wi-Fi network. If it stalls, run adb kill-server and start again.

  • Applies to Android platform-tools current, Android 10 and lower for tcpip, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    List what adb sees, with state and description. The next step depends on whether the phone shows as device, offline or not at all.

    adb devices -l
  2. 2Match what you see, then jump to its fix

    1. 1adb devices -l is empty, and adb tcpip 5555 has no device to talk toThe phone is not attached by USB when tcpip runsFix
    2. 2adb tcpip works over USB, but adb connect cannot reach the phoneThe phone and the computer are on different Wi-Fi networks, or the access point blocks adbFix
    3. 3adb devices shows the phone as offline, or a connection that worked earlier is goneA stale adb server or a dropped connectionFix
    4. 4adb: more than one device/emulatorMore than one device is attached and no target was namedFix

What does the error look like?

  • List of devices attached (nothing listed)
  • adb: more than one device/emulator
  • offline

Cause 1 of 4

The phone is not attached by USB when tcpip runs

1Check

Android's wireless steps start over USB: connect the device with a cable, then set it to listen on TCP/IP port 5555.

adb devices -l

2Fix

Attach the phone with a data cable, accept the debugging prompt on the phone, then run the tcpip command, unplug, and connect by IP.

adb tcpip 5555
adb connect 192.168.1.50:5555
adb devices

3Verify

The list shows the IP address and port with the state device.

adb devices

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 4

The phone and the computer are on different Wi-Fi networks, or the access point blocks adb

1Check

Android requires the device and host to be on one Wi-Fi network and warns that not every access point is suitable: its firewall must allow adb. Compare the phone's IP address with your computer's.

ip -4 addr show | grep inet

2Fix

Join both to the same network, or use another access point whose firewall allows adb, then run adb connect again with the phone's IP address.

adb connect 192.168.1.50:5555

3Verify

adb devices lists the phone with the state device.

adb devices

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 4

A stale adb server or a dropped connection

1Check

The offline state means the device is not connected to adb or not responding. Android says to reconnect with adb connect, and to reset the adb host with adb kill-server if that fails.

adb devices -l

2Fix

Restart the adb server and repeat the whole sequence from the USB step.

adb kill-server
adb start-server
adb tcpip 5555
adb connect 192.168.1.50:5555

3Verify

The phone shows as device.

adb devices

Confirmed by developer.android.com

Did this fix it?

Cause 4 of 4

More than one device is attached and no target was named

1Check

With several devices or emulators, each adb command needs a target.

adb devices

2Fix

Name the target with -s and its serial. Use -d for the only hardware device or -e for the only emulator, or export ANDROID_SERIAL (the -s option wins over it).

adb -s 192.168.1.50:5555 shell
# or, for many commands in a row
export ANDROID_SERIAL=192.168.1.50:5555

3Verify

The command runs on the device you named.

adb -s 192.168.1.50:5555 shell getprop ro.product.model

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • On Android 11 and later, use Wireless debugging with adb pair instead of the USB-first tcpip steps.
  • Check adb devices -l before every wireless step.
  • Keep the phone and computer on one network and note the phone's IP address before unplugging.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Android Studio cannot pair the phone over Wi-Fi

The Pair devices over Wi-Fi dialog lists no device

Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.