How can I connect to Android with ADB over TCP?

I am attempting to debug an application on a Motorola Droid, but I am having some difficulty connecting to the device via USB. My development server is a Windows 7 64-bit VM running in Hyper-V, and so I cannot connect directly via USB in the guest or from the host.

I installed a couple of different USB-over-TCP solutions, but the connection appears to have issues since the ADB monitor reports "devicemonitor failed to start monitoring" repeatedly. Is there a way to connect directly from the client on the development machine to the daemon on the device using the network instead of the USB connection or possibly another viable options?

adb tcpip 5555

Settings > About Phone > Status

adb connect 192.168.x.x

31 Answers
31

According to a post on xda-developers, you can enable ADB over Wi-Fi from the device with the commands:

su
setprop service.adb.tcp.port 5555
stop adbd
start adbd


And you can disable it and return ADB to listening on USB with

setprop service.adb.tcp.port -1
stop adbd
start adbd


It is even easier to switch to using Wi-Fi, if you already have USB. From a command line on the computer that has the device connected via USB, issue the commands

adb tcpip 5555
adb connect 192.168.0.101:5555


Be sure to replace 192.168.0.101 with the IP address that is actually assigned to your device.

192.168.0.101

You can find the IP address of a tablet in two ways:

Manual IP Discovery:

Go into Android's WiFi settings, click the menu button in the action bar (the vertical ellipsis), hit Advanced and see the IP address at the bottom of the screen.

Use ADB to discover IP:

Execute the following command via adb:

adb shell ip -f inet addr show wlan0


To tell the ADB daemon return to listening over USB

adb usb


There are also several apps on Google Play that automate this process. A quick search suggests adbWireless, WiFi ADB and ADB WiFi. All of these require root access, but adbWireless requires fewer permissions.

adb tcipip 5555

adb connect ...

adb tcpip <port>

ro.kernel.qemu

ro.secure

ro.debuggable

service.adb.root

adbd

adb_main

secure

adbd

This is really simple if your phone is rooted.

Download a terminal emulator from Google Play (there are lots that are free). Make sure that your Android device is connected to your Wi-Fi and get the Wi-Fi IP address. Open the terminal program and type:

su
setprop service.adb.tcp.port 5555
stop adbd
start adbd


Now go to your computer (assuming that you are using Windows) and create a shortcut on the desktop for "cmd.exe" (without the quotations).

Right click on the cmd shortcut and choose "Run as Administrator"

"Run as Administrator"

Change to your android-sdk-windowstools folder

android-sdk-windowstools

Type:

adb connect ***wifi.ip.address***:5555

(example: adb connect 192.168.0.105:5555)


adb should now say that you are connected.

Note: if you are too fast to give the connect command it may fail. So try at least two times five seconds apart before you say this doesn't work.

Connect device via USB and make sure debugging is working, then run:

adb tcpip 5555
adb connect <DEVICE_IP_ADDRESS>:5555


Disconnect USB and proceed with wireless debugging.

When you're done and want to switch back to USB debugging, run:

adb -s <DEVICE_IP_ADDRESS>:5555


To find the IP address of your device, go to Settings > Wi-Fi > Advanced > IP Address on your device or run adb shell netcfg.

Settings > Wi-Fi > Advanced > IP Address

adb shell netcfg

No root required. Only one device can be debugged at a time.

See this XDA post.

The adb command is located in the platform-tools folder of the Android SDK.

adb

platform-tools

From adb --help:

adb --help

connect <host>:<port> - Connect to a device via TCP/IP


That's a command-line option by the way.

You should try connecting the phone to your Wi-Fi, and then get its IP address from your router. It's not going to work on the cell network.

The port is 5554.

adb tcpip port

connect host:port

For PC users:

Step 1:
You have to enable Developer options in your Android phone.
You can enable Developer options using this way.
• Open Settings> About> Software Information> More.
• Then tap “Build number” seven times to enable Developer options.
• Go back to Settings menu and now you'll be able to see “Developer options” there.

• Tap it and turn on USB Debugging from the menu on the next screen.

Step 2:

Open cmd and type adb.
if you find that adb is not valid command then you have to add a path to the environment variable.

•First go to you SDK installed folder
Follow this path and this path is just for an example.
D:softwaresDevelopmentAndoirdSDKsdkplatform-tools;
D:softwaresDevelopmentAndoirdSDKsdktools;
• Now search on windows system advanced setting

•

Open the Environment variable.

then open path and paste the following path
this is an example.
You SDK path is different from mine please use yours. D:softwaresDevelopmentAndoirdSDKsdkplatform-tools;
D:softwaresDevelopmentAndoirdSDKsdktools;

Step 3:

Open cmd and type adb. if you still see that adb is not valid command then your path has not set properly follow above steps.

Now you can connect your android phone to PC.

Open cmd and type adb devices and you can see your device.
Find you phone ip address.

Type:- adb tcpip 5555

Get the IP address of your phone

adb shell netcfg


Now,

adb connect "IP address of your phone"


Now run your android project and if not see you device then type again adb connect IP address of your phone

For Linux and MAC User:

Step 1: open terminal and install adb using

sudo apt-get install android-tools-adb android-tools-fastboot

Connect your phone via USB cable to PC.
Type following command in terminal

adb tcpip 5555


Using adb, connect your android phone ip address.

Remove your phone.

I needed to get both USB and TCPIP working for ADB (don't ask), so I did the following (using directions others have posted from xda-developers)

Using adb shell:

adb shell

su
#Set the port number for adbd
setprop service.adb.tcp.port 5555

#Run the adbd daemon *again* instead of doing stop/start, so there
#are two instances of adbd running.
adbd &

#Set the port back to USB, so the next time ADB is started it's
#on USB again.
setprop service.adb.tcp.port -1

exit


/sbin/adbd

To connect your tablet using TCP port.
Make sure your system and device is connected to same network.

adb tcpip 5555

adb connect 192.168.1.2

Connected using port forward
Try to do port forwarding,

adb forward tcp:<PC port> tcp:<device port>

<PC port>

<device port>

like:

adb forward tcp:5555 tcp:5555.

C:Usersabc>adb forward tcp:7612 tcp:7612

C:Usersabc>adb tcpip 7612 restarting in TCP mode port: 7612

C:Usersabc>adb connect 10.0.0.1:7612

connected to 10.0.0.1:7612

If you get message error: device not found connect a usb device to system then follow same procedure.
for a rooted device

setprop service.adb.tcp.port 5555
stop adbd
start adbd


su

Assume you saved adb path into your Windows environment path

Activate debug mode in Android

Connect to pc via usb

Open command prompt type: adb tcpip 5555

Disconnect your tablet or smartphone from pc

Open command prompt type: adb connect IPADDRESS (IPADDRESS is the DHCP/IP address of your tablet or smartphone, which you can find by Wi-Fi -> current connected network)

Now in command prompt you should see the result like: connected to xxx.xxx.xxx.xxx:5555

First you must connect your device via USB

Then connect your device to WIFI and get the IP address.
While still connect via usb type this in command line or via Android Studio Terminal

adb tcpip 5555
adb connect <device IP>:5555


You will see these messages:

restarting in TCP mode port: 5555
connected to 172.11.0.16:5555


Now remove the USB cable and you will still see your logcat as normal

Done. Enjoy

I do not know how to connect the device without any USB connection at all, but if you manage to connect it maybe at another computer you can switch the adbd to TCP mode by issuing

adb tcpip <port>


from a terminal and connect to your device over wifi from any PC on the network by:

adb connect <ip>:<port>


Maybe it is also possible to switch to TCP mode from a terminal on the device.

If you want to easily connect your device to run, debug or deploy your Android apps over WiFi you can use an open source IntelliJ Plugin I've developed. Here is the code and here the plugin ready to be used.

The usage is quite simple. Here you have a gif:

From a computer on a non-rooted device

(Note that this can be done using a rooted device as well, but you can use a shell on a rooted device which doesn't require a USB connection)

Firstly, open command prompt (CMD). If you use Android Studio or IntelliJ there is a console included in there you can use.

If possible, open the SDK location, right click, and press "start command prompt here". Not all have this option so you have to do this (/these) commands as well:

Change the drive (if applicable)

D:


And access the sdk and platform tools. Replace this path with your SDK location:

D:/sdk/path/here/platform-tools


Now you have access to the Android debug bridge.

Now, with the device connected to the computer, do:

adb tcpip <port>
adb connect <ip>:<port>


Where is the port you want to connect to (default is 5555) and is the IP of the device you want to connect to.

5555

Please note: 5555 is the default port and just writing the IP address connects it. If you use a custom port you can at least improve the security a bit. USB debugging over wifi can be abused, but only if the device is connected to the computer who wants to abuse the device. Using a non-default port at least makes it a bit harder to connect.

5555

If you use a custom port, make sure to add it after the IP. Writing no port connects to 5555 and if you didn't use that the connection will fail.

5555

You can find the IP address of a device in two ways:

Depending on your device, the exact names may vary. Open settings and go to About device -> Status -> IP address

Use ADB to get the IP

From the console, do:

adb shell ip -f inet addr show wlan0


And once you are finished with the connection, you can disconnect the device from your computer by doing:

adb disconnect <ip>:<port>


Or no IP to disconnect all devices. If you used a custom port, you must specify which port to disconnect from. The default is 5555 here as well.

To disable the port (if that is something you want to do) you do this command with the device connected:

adb usb


Or you can restart the device to remove the tcpip connection

From a computer on a rooted device

Firstly, you need access to the shell. You either connect the device using a usb cable and use adb shell or download an app from Google Play, FDroid, or some other source.

adb shell

Then you do:

su
setprop service.adb.tcp.port <port>
stop adbd
start adbd


And to connect the device, you do as in the non-rooted version by doing adb connect <ip>:<port>.

adb connect <ip>:<port>

And if you want to disable the port and go back to USB listening:

setprop service.adb.tcp.port -1
stop adbd
start adbd


You can also use an Android Studio plugin to do it for you (don't remember the name right now), and for rooted users there's also the option of downloading an Android app to set up the phone connection (adb connect is probably still required).

Some phones have a setting in developer options (this applies to some unrooted phones, though probably some rooted phones too) that allows for toggling ADB over wifi from the device itself without root or a computer connection to start it. Though there are few phones that have that

adb shell ip -f inet addr show wlan0

As Brian said:

According to a post on xda-developers, you can enable ADB over WiFi from the device with the commands

setprop service.adb.tcp.port 5555

stop adbd

start adbd

And you can disable it and return ADB to listening on USB with

setprop service.adb.tcp.port -1

stop adbd

start adbd

If you have USB access already, it is even easier to switch to using WiFi. From a command line on the computer that has the device connected via USB, issue the commands

adb tcpip 5555

adb connect 192.168.0.101:5555

To tell the ADB daemon return to listening over USB

adb usb

There are also several apps on the Android Market that automate this process.

It works.You just need to access the android shell and type those commands...

One other (easier) solution is on the Market: adbWireless, it will automatically set your phone.

Root is required! for both...

adb tcpip 5555


Weird, but this only works for me if I have the USB cable connected, then I can unplug the usb and go for it with everything else adb.

and the same when returning to usb,

adb usb


will only work if usb is connected.

It doesn't matter if I issue the

setprop service.adb.tcp.port 5555


or

setprop service.adb.tcp.port -1


then stop & start adbd, I still need the usb cable in or it doesn't work.

So, if my ADB over usb wasn't working, I bet I wouldn't be able to enable ADB over WiFi either.

To switch between TCP and USB modes with just one command, you can add this to /init.rc:

/init.rc

on property:service.adb.tcp.port=*
restart adbd

on property:service.adb.tcp.enable=1
setprop service.adb.tcp.port 5555

on property:service.adb.tcp.enable=0
setprop service.adb.tcp.port -1


And now you can use property service.adb.tcp.enable to enable or disable listening on port 5555. Run netstat to check whether it's listening. As you can see it will also trigger if you do wish to change service.adb.tcp.port manually.

service.adb.tcp.enable

netstat

service.adb.tcp.port

STEP 1.

Make sure both your adb host computer and Android device are on the same Wifi network.

STEP 2.

Connect the Android device with the computer using your USB cable. As soon as you do that, your host computer will detect your device and adb will start running in the USB mode on the computer. You can check the attached devices with adb devices whereas ensure that adb is running in the USB mode by executing adb usb.

adb devices

adb usb

$ adb usb
restarting in USB mode
$ adb devices
List of devices attached
ZX1D63HX9R device


STEP 3.

Restart adb in tcpip mode with this command:

$ adb tcpip 5556
restarting in TCP mode port: 5556


STEP 4.

Find out the IP address of the Android device. There are several ways to do that:

$ adb shell netcfg

Now that you know the IP address of your device, connect your adb host to it.

$ adb connect 192.168.0.102:5556
already connected to 192.168.0.102:5556
$ adb devices
List of devices attached
ZX1D63HX9R device
192.168.0.102:5556 device


STEP 5.

Remove the USB cable and you should be connected to your device. If you don’t see it in adb devices then just reconnect using the previous step’s command:

adb devices

$ adb connect 192.168.0.102:5556
connected to 192.168.0.102:5556
$ adb devices
List of devices attached
192.168.0.102:5556 device


Either you’re good to go now or you’ll need to kill your adb server by executing adb kill-server and go through all the steps again once more.

adb kill-server

Hope that helps!



Reference:

You can also use SSH local port forwarding. But it still involves a USB cable. Connect your phone using USB to a computer (host) with an sshd running. On a remote (guest) pc start an SSH client capable of portforwarding/tunneling. Example:

plink -L 5037:localhost:5037 <host_IP_address>


I use this construction to connect my device to a virtual machine. Eltima USB to Ethernet wasn't stable enough (timeouts during debug).

SSH tunneling works for free and is more reliable.

I find the other answers confusing. Far simpler to use adbWireless:

http://ppareit.github.com/AdbConnect/

Simply install an app on your phone to toggle debugging over wifi, install an eclipse plug-in and you're done.

I put together a batch file for automatic enabling and connecting ADB via TCP, to a device connected via USB. With it you don't have to put in the IP manually.

@echo off
setlocal

REM Use a default env variable to find adb if possible
if NOT "%AndroidSDK%" == "" set PATH=%PATH%;%AndroidSDK%platform-tools

REM If off is first parameter then we turn off the tcp connection.
if "%1%" == "off" goto off

REM Set vars
set port=%1
set int=%2
if "%port%" == "" set port=5557
if "%int%" == "" set int=wlan0

REM Enable TCP
adb -d wait-for-device tcpip %port%

REM Get IP Address from device
set shellCmd="ip addr show %int% | grep 'inet [0-9]{1,3}(.[0-9]{1,3}){3}' -oE | grep '[0-9]{1,3}(.[0-9]{1,3}){3}' -oE"
for /f %%i in ('adb wait-for-device shell %shellCmd%') do set IP=%%i

REM Connect ADB to device
adb connect %IP%:%port%

goto end

:fail
echo adbWifi [port] [interface]
echo adbWifi off
goto end

:off
adb wait-for-device usb

:end


Here's an extension to Brian's answer using Bluetooth:

On Linux, use Blueman to share PC internet with your device via Bluetooth:

$ sudo apt-get install blueman
$ blueman-manager
Pair them: Search devices after enabling Bluetooth
on your phone and making it visible
$ blueman-services
Network > [X] Network Access Point (NAP)
Your Phone > Settings > Bluetooth > Paired Device > [X] Internet access


Use the Bluetooth network for ADB commands:

$ adb tcpip 5555
$ adb connect $(adb shell ip -f inet addr show bt-pan | egrep -o '[0-9]+.[0-9]+.[0-9]+.[0-9]+' | head -n1):5555


Once done to return to USB mode:

$ adb disconnect
$ adb usb


Note: Bluetooth 3.0 and 4.0 can go up to 24 Mbit/s.

Steps :

su

setprop service.adb.tcp.port 5555

stop adbd

start adbd

this works perfectly with ssh from my windows PC

ssh

I try to do this on the boot on my cyanogen mobile or launch this with plink. With plink I can't launch shell with su right ... sudo or su command not works. On boot I don't know how it's works!
My shell program works from ssh with su -c "sh /storage/sdcard1/start_adb.sh" with the last 3 commands (without su --)

su -c "sh /storage/sdcard1/start_adb.sh"

Thanks

You Need to do following things:

Use the adbwireless app to enable the phone, then use adb connect from the Windows machine to talk to it. The adbwireless app on the phone tells you how to connect to it, giving the IP address and everything.

The much less fun alternative is to connect via USB, tell the phone to use TCPIP via adb tcpip 5555, then disconnect USB, then use adb connect. This is much harder because this way you have to figure out the IP address of the phone yourself (adbwireless tells you the IP), you have to connect via USB, and you have to run adb tcpip (adbwireless takes care of that too).

So: install adbwireless on your phone. Use it. It is possible, I do it routinely on Linux and on Windows.

On my system it went like this:

On my Android device in my Linux shell, a simple "ifconfig" did not give me my IP address. I had to type:

ifconfig eth0

-or-

netcfg

to get my IP address. (I knew eth0 was configured because I saw it in my dmesg.) Then I did the :

setprop service.adb.tcp.port -1

stop adbd

start adbd

Then on my Win7 box (the one running Eclipse 3.7.1). I opened a command prompt to

android-sdkplatform-tools>

without running as admin. Then I did a

adb connect 12.345.678.90

I never put a port. If I did a

adb tcpip 5555

it said it couldn't find the device then nothing appeared in my "adb devices" list. I.e. it only works if I DON'T do the tcpip command above.

I can do an "adb shell" and mess with my Android Device. But my Android Device does not appear in my Run->Run Configurations->Target tab right now. On the other hand, if I keep the Target Tab set to automatic. Then when I run my app via Run->Run it does run on my Android device even though my Android device is not even listed as one of my targets.

I did get this working. Didn't use any usb cable.

Run it. That will set ip and port; Then in dos

cd C:Program FilesAndroidandroid-sdkplatform-tools adb connect "192.168.2.22:8000 "enter"


Connected.

I just followed following steps and it started working, so that i can connect to my android device.

Step 1: Open the terminal Window in Android Devices and execute the following command.

Step 2: Through ADB, Execute the bellow command.(From the path where ADB is configured)

adb connect 10.10.10.50:5555 - Here 10.10.10.50 is the IP address of the android device and 5555 is the port number.

I've found a convenient method that i would like to share.

For Windows

Having USB Access Once

No root required

Connect your phone and pc to a hotspot or run portable hotspot from your phone and connect your pc to it.

Get the ip of your phone as prescribed by brian (Wont need if you're making hotspot from your phone)

adb shell ip -f inet addr show wlan0


Open Notepad

Write these

@echo off
cd C:androidandroid-sdkplatform-tools
adb tcpip 5555
adb connect 192.168.43.1:5555


Change the location given above to where your pc contains the abd.exe file

Change the ip to your phone ip.

Note : The IP given above is the basic IP of an android device when it makes a hotspot. If you are connecting to a wifi network and if your device's IP keeps on changing while connecting to a hotspot every time, you can make it static by configuring within the wifi settings. Google it.

Now save the file as ABD_Connect.bat (MS-DOS batch file).

Save it somewhere and refer a shortcut to Desktop or Start button.

Connect through USB once, and try running some application. After that whenever you want to connect wirelessly, double click the shortcut.

Note : Sometimes you need to open the shortcut each time you debug the application. So making a shortcut key for the shortcut in desktop will be more convenient. I've made a shortcut key like Ctrl+Alt+S. So whenever i wish to debug, i'll press Shift+F9 and Ctrl+Alt+S

Ctrl+Alt+S

Shift+F9

Ctrl+Alt+S

Note : If you find device=null error on cmd window, check your IP, it might have changed.

One additional note (learned the hard way): You should not have your company VPN-connection active at the same time...

adb can communicate with adb server over tcp socket.
you can verify this by telnet.

$ telnet 127.0.0.1 5037
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
000chost:version
OKAY00040020


generally, command has the format %04x%s with <message.length><msg>
the following is the ruby command witch sends adb command cmd against tcp socket socket

%04x%s with <message.length><msg>

cmd

socket

def send_to_adb(socket, cmd)
socket.printf("%04x%s", cmd.length, cmd)
end


the first example sends the command host:version which length is 12(000c in hex).
you can enjoy more exciting command like framebuffer: which takes screenshot from framebuffer as you can guess from its name.

host:version

000c

framebuffer:

If you want to be able to do it on a button click then:

Note: If it did not work:

Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).


Would you like to answer one of these unanswered questions instead?