Howto: Enable Adb over wireless

[defconoi]

Hey guys just a heads up and quick howto:
Here is how to get adb wireless working so you dont need to use a cable any longer to easily push/pull files and logcats/debugging
(its beyond me why google doesnt have a ui option to turn this on)

Open up a terminal emulator (I use rom toolbox pro) with droidmote and do this:

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

From pc do this:

adb tcpip 5555
adb connect 192.168.0.101:5555

adb shell
adb push blah etc

To automate this on boot, add this as a script to rom toolbox/pro to execute on boot

 

[IBNobody]

Hey guys just a heads up and quick howto:
Here is how to get adb wireless working so you dont need to use a cable any longer to easily push/pull files and logcats/debugging
(its beyond me why google doesnt have a ui option to turn this on)

To automate this on boot, add this as a script to rom toolbox/pro to execute on boot

I'm not seeing ADB-over-wifi stay on all the time. I have the script set up to run at boot. Is Android stopping/starting the ADB service?

 

[defconoi]

I'm not seeing ADB-over-wifi stay on all the time. I have the script set up to run at boot. Is Android stopping/starting the ADB service?

the adb service stays on for me, I also have selinux set as permissive on boot with setenforce 0, that could be it, selinux likes to control stuff on its own

 

[IBNobody]

the adb service stays on for me, I also have selinux set as permissive on boot with setenforce 0, that could be it, selinux likes to control stuff on its own

I can try that. What are the commands I need to do to set selinux to be permissive?

 

[defconoi]

I can try that. What are the commands I need to do to set selinux to be permissive?

Su then setenforce 0

 

[IBNobody]

Su then setenforce 0

Thanks. I've tried this using Script Manager. It worked, and I am 24h without losing access.

https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en

Here is the contents of the script.

#!/system/bin/sh
setenforce 0&&setprop service.adb.tcp.port 5555&&stop adbd&&start adbd&&echo Done

The script is set to run on boot and after a network change.

I chained the commands together for convenience. (If I don't see "done", I know a command failed.)

 

[pacman366]

This is a pretty useful find! Thanks! I'd like to add a startup script for this, where can the init script directory be found for startup script placement on the nexus player? I can't seem to find it anyplace browsing the root filesystem using adb shell. I'm already rooted and what not.

Sent from my Nexus 6 using Tapatalk

 

[dandaddy]

Thank you all!

Works fantastically. Using the script provided by IBNobody, the Scripter tool in ROM Toolbox Pro, and the PC commands from the OP, wireless USB Debugging is recognized.
Cheers!

 

[billydroid]

The adb over WiFi app works as well.

 

[trevd]

Just an FYI Folks

you don't need to do all the su business on the device .. just connecting the device up the a pc with usb and doing

adb tcpip 5555
adb connect  .....

As the adb usage helpfully points out

"adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port"

Thanks
trevd

 

[rellik1000]

no script needed to autostart wireless adb

FYI peeps
No script needed to auto start wireless adb.
Obvious security concern though
Just add the line
service.adb.tcp.port=5555
to build.prop
It will auto start wireless adb at boot.
So far it has worked on all 15 android devices I've owned up to 4.4.2 not sure about lollipop.
I pretty much do everything on my TV sticks from my couch.
BTW android commander is a great free adb gui to perform basic tasks.
Very slow on my network though.

DON'T BLAME ME!!
Good luck

 

[pacman366]

FYI peeps
No script needed to auto start wireless adb.
Obvious security concern though
Just add the line
service.adb.tcp.port=5555
to build.prop
It will auto start wireless adb at boot.
So far it has worked on all 15 android devices I've owned up to 4.4.2 not sure about lollipop.
I pretty much do everything on my TV sticks from my couch.
BTW android commander is a great free adb gui to perform basic tasks.
Very slow on my network though.

DON'T BLAME ME!!
Good luck

This did the trick for me. Thank you.

Sent from my Nexus 6 using Tapatalk

 

[D-FUSE]

Nice man I'm gonna try this on my game stick after work

Sent from my SM-G386T using Tapatalk

 

[Raybasto]

FYI peeps
No script needed to auto start wireless adb.
Obvious security concern though
Just add the line
service.adb.tcp.port=5555
to build.prop
It will auto start wireless adb at boot.
So far it has worked on all 15 android devices I've owned up to 4.4.2 not sure about lollipop.
I pretty much do everything on my TV sticks from my couch.
BTW android commander is a great free adb gui to perform basic tasks.
Very slow on my network though.

DON'T BLAME ME!!
Good luck

Thanks for the info ! Question though I'm on Nougat if I downgrade to marshmallow for root and change build.prop will I lose this in build.prop if i reupgrade to Nougat?

 

[bigtimejdub]

This works for me on wireless, but from my wired (ethernet) desktop I get "device offline". Any ideas? Thanks.