• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ADB over WiFi being stubborn.

McNerdius

McNerdius

Well-Known Member
I'm trying to troubleshoot a set of issues i'm having by using ADB. In order to keep my usage patterns normal, i figured i'd do ADB over WiFi. However, both the popular widget, and the wifi adb app, are being stubborn. I will after starting them up, the popup indicating superuser permissions being granted is displayed, and then nothing. Nothing gets done, no errors are displayed, just nothing. I feel like i'm missing something obvious. Both debugging and ADB over network are enabled in Settings>Apps>Development. Beyond that, i'm either in over my head or just ignorant... one way or the other. As usual, any tips at all = gold ! Thanky panky in advance. :)
 
You don't need to use an app. Once you turn on wifi, and then set adb over network in settings, you simply connect via your phone's ip address + port 5555:

adb connect 192.168.1.123:5555

To find out your phone's ip address while connected via wifi:
Settings>>Wireless & network settings>>Wi-Fi settings>>Press menu key>>Advanced>>IP address
 
JerryScript said:
You don't need to use an app. Once you turn on wifi, and then set adb over network in settings, you simply connect via your phone's ip address + port 5555:

adb connect 192.168.1.123:5555

To find out your phone's ip address while connected via wifi:
Settings>>Wireless & network settings>>Wi-Fi settings>>Press menu key>>Advanced>>IP address
Click to expand...

*uninstalls pointless app*

i suppose that narrows the issue down a bit. i'm getting "unable to connect to 192.168.###.##:5555" ADB via USB has been working flawlessly, and i use WiFi all the time. Some behind-the-scenes stuff is messin' me up here.

*bows to JerryScript for his mere presence*
 
"adb connect 192.168.xxx.xxx:5555" command does not work for me, getting can't connect to 192.168.xxx.xxx:5555:5555 (doubles port#).
But "adb connect 192.168.xxx.xxx" (no port #) does work. Try that.
 
Try ADB Wireless. Once you have downloaded the app open it up and push the green buuton. It should turn red and display your IP address and port #. Open up a command prompt and type in: adb connect (your IP and port number. Example, 192.168.2.4:555)
 
JerryScript said:
You may have to allow the port in your router settings. ;)
Click to expand...

methinks this is the issue. i've had it in my router from step one, yet double checking with nmap/similar shows no open ports for the ip. i've never had this problem before, with any other port opening/forwarding type stuff... very frustrating. no firewall btw.

i'm off to do some other stuff for a while so i stay sane :) after all, insanity could well be what's causing this.

*trips over cat on way to kitchen, hits head on corner of counter, passes out*
 
Just to be sure, I just did a bunch of testing with the latest build of BACKside (0313), all the following commands executed without issue:
Code: 
adb connect 192.168.1.xxx:55555
adb remount
adb shell
cd sdcard
ls
mv bootanimation.zip /system/media/bootanimation.zip
cd /system/media
exit
exit
 
I'm a little slow I'm thinking. JerryScript did you add an ADB wireless connect capability and I missed it, don't need an app to do it? That would be more room freed up on my system.
 
You must log in or register to reply here.
Back
Top Bottom