adb tcpip 5555 fails because no device is found
List 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.
Fix it fast
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 -l2Match what you see, then jump to its fix
- 1
adb devices -l is empty, and adb tcpip 5555 has no device to talk toThe phone is not attached by USB when tcpip runsFix - 2
adb 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
adb devices shows the phone as offline, or a connection that worked earlier is goneA stale adb server or a dropped connectionFix - 4
adb: more than one device/emulatorMore than one device is attached and no target was namedFix
- 1
What does the error look like?
List of devices attached (nothing listed)adb: more than one device/emulatoroffline
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 -l2Fix
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 devices3Verify
The list shows the IP address and port with the state device.
adb devicesConfirmed by developer.android.com
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 inet2Fix
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:55553Verify
adb devices lists the phone with the state device.
adb devicesConfirmed by developer.android.com
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 -l2Fix
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:55553Verify
The phone shows as device.
adb devicesConfirmed by developer.android.com
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 devices2Fix
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:55553Verify
The command runs on the device you named.
adb -s 192.168.1.50:5555 shell getprop ro.product.modelConfirmed by developer.android.com
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 fixMobile apps
adb pair or adb connect fails with error 10061 over Wi-Fi
Wireless debugging device not listed by adb devices
Error 10061 means the phone's address refused the TCP connection.
4 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix