On my Pixel 7 (Android 13) I just tried doing "adb connect {IP-addr}:5555 and get connection refused. I can do adb with a USB cable connected, and adb connect over the network does work with some firesticks.
I do have USB debugging, and Wireless Debugging enabled in Developer options.
I'm running ADB on Linux.
What am I missing?
Enable wireless debugging then tap it > pair device with paring code.
Code:
adb pair (IP:PORT) shown in pairing box
after pairing
Code:
adb connect (IP:PORT) shown above pairing options
Still a problem
$ adb pair 192.168.10.114:40479
Enter pairing code: 665364
Successfully paired to 192.168.10.114:40479 [guid=adb-2C190DLH2000SS-IXWUPg]
$ adb connect 192.168.10.114:40479
failed to connect to '192.168.10.114:40479': Connection refused
obitest11 said:
Still a problem
$ adb pair 192.168.10.114:40479
Enter pairing code: 665364
Successfully paired to 192.168.10.114:40479 [guid=adb-2C190DLH2000SS-IXWUPg]
$ adb connect 192.168.10.114:40479
failed to connect to '192.168.10.114:40479': Connection refused
Click to expand...
Click to collapse
I think the pairing and connecting port numbers should be different, one for client and the other for server; and one is static and the other is dynamic. It's been a while since I tried wireless debugging but that's how I remember doing it. Either that or adb daemon isn't running on both sides.
I tried doing the connect with the normal 5555 port, after the pairing succeeded, but that didn't work either
obitest11 said:
I tried doing the connect with the normal 5555 port, after the pairing succeeded, but that didn't work either
Click to expand...
Click to collapse
No VPN right? Same network I presume. Did you get the message to always allow adb on this device? I have a Galaxy watch and couldn't connect until I turned off the adb debugging, wifi connections rebooted and tried again. Then the alert came up I clicked always allow and that did it.
The ports are different when pairing and connecting. Looks like you used the same port.
Related
I'm using Windows 7 x64 work computer. The only device ADB can recognize is my HTC Desire S phone. However, when I tried to get ADB to detect my Asus Transformer Pad, it fails to do so.
The Asus Transformer Pad TF701T is not rooted. I have no plans to root/unlock the tablet, other than to try and get the Chrome for Android to always "request Desktop site." I'm just trying to do this: http://droidnerds.com/content/how-to-permanently-have-desktop-mode-on-chrome-mobile-for-android/
I have USB Debugging checked and turned on.
I already have Android SDK installed with all components updated to the latest.
I have tried using MTP to see if ADB detects it. Fails.
I have tried using PTP to see if ADB detects it. Fails also.
Plugged the USB cord into MobileDock keyboard, that fails too.
I went ahead and update/reinstall Google USB drivers. That failed.
I uninstall the drivers, reboot, reinstall Google USB drivers. Failed.
Tried to find TF300 series universal USB drivers, nothing works from that thread.
Also tried the Asus PC sync, but notices those are for TF300 Eee PC, therefore I ignored it.
Is there something I amiss?
Yes, there is something amiss.
Replugging the device, with USB debugging off, then USB debugging on, the tablet displays a prompt asking me about USB debugging and its risks. Completing the prompt is what gets the device to be detected by ADB!
Well, so much time wasted on this simple task.
tom_mai78101 said:
Yes, there is something amiss.
Replugging the device, with USB debugging off, then USB debugging on, the tablet displays a prompt asking me about USB debugging and its risks. Completing the prompt is what gets the device to be detected by ADB!
Well, so much time wasted on this simple task.
Click to expand...
Click to collapse
Glad you got it sorted out. There is one more thing that could help under those circumstances: Change the USB connection type to camera and back to MTP while connecting / disconnecting the USB cable in each state. That got me going, because somehow the USB driver wasn't able to kick in accordingly (both Win7 and Win8 64bit).
There should be a troubleshooting manual included with the tablet, as far as I'm concerned. Thanks for the tips.
So I'm following the instructions exactly how they're written on Google's documentation and my Gear Live keeps showing up as offline. I've rebooted both the phone and watch multiple times and reconnected bluetooth but it still shows offline.
Here's what I'm typing in:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb devices
shows locahost:4444 as offline.
Nevermind, I'm an idiot. If you go into the setting within Google Now on the device, there's an option enable USB debugging and debugging over bluetooth.
S4 mini, Cyanogenmod 12.1-20******, Android 5.1.1, KV 3.4.0.
I have USB mobile dongle on PC(good signal) and trying to get phone to use it's internet via USB cable and Android tool
Downloaded the Androidtool zip with all the relevant files.
Phone is rooted(CM) and is set to accept root access in dev options.
USB debugging is enabled.
I have also installed Xposed 22 and the hack connectivity module is installed. All looks good.
As far as I know I must have right USB drivers for PC as all connects with USB cable and looks good.
I have tried DNS both 8.8.4.4 and 8.8.8.8 (changed them manually in ini in AT folder)
USB tunnel service is running and connected.
So AndroidTool connects fine, first time Android asks for root access etc.
I get a # symbol in status bar on phone and all looks good. However no app will connect to internet. Tried chrome, Android browser, ClashofClans and a couple of others.
Any ideas why not.?
Good evening everyone.
I have an AT&T Galaxy S6 that is under warranty. My left (recent) capacitive button has stopped working, so I'd like to replace my phone. Kick in the nuts number 1: I recently rooted my phone via PingPongRoot. No problem, I thought. I downloaded the stock firmware for the AT&T Samsung G920A, and prepared to flash the custom firmware. Kick in the nuts number 2: My data connection pins on the microUSB port are fried. I've tried 5 different USB cables, three different computers, and nothing. I've disabled and re-enabled the ADB debugging option from the developer menu. But everytime I start an ADB shell from the computer, I get nothing from the phone. Usually, the phone will say "phone is connected as a media device" or somesuch, but it only displays "charger connected". Also, normally, when I use the adb start-server command, my phone will ask me if I want to allow the computer to connect, but I do not get that prompt. adb devices returns nothing. I've tried factory resetting my phone 3 or 4 times to see if maybe it was an S6 end driver problem. No dice. So, I googled around, and it doesn't look like the firmware is possible to flash via the recovery menu? It looks like it must be flashed via Odin/Heimdall. Is this correct? And if so, does anyone have any ideas as to how I could fix this?
Thanks guys.
Your USB port is not fried, you just don't have proper ADB drivers. Lol. Google "Samsung ADB drivers" - install and reboot your computer. You also have to allow the RSA fingerprint of your computer, if you miss that prompt, you have to trigger it again. Do what I said and watch your screen when you plug it in.
Maybe I should have mentioned in my first post, only one of the PCS I used was running Windows, the rest were running Ubuntu. I will try one more windows machine with the drivers installed and report back. It's also worth noting that I tried 4 different USB OTG cables with all different kinds of devices (Flash drive, mouse, Keyboard), and none of them have been recognized either.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Bump. I really want to know if I can maybe flash the recovery firmware from the recovery menu?
Are you running a launcher that might be interfering with the device-connection detection? Launcher-Pro on my old GSII would prevent detection of the USB cable / ADB connection. Just a thought, AoN.
Hi All,
As per title, my Asus ROG Phone II is not recognized by my PC when I connect it through USB.
It's not even that ADB commands aren't working or such: even just connecting "normally" (e.g. without USB debugging activated), the phone will charge but won't show up in the PC, and vice-versa it won't appear as connected to USB in the phone settings.
I've tried with two different PCs and the problem persists.
Am I missing something?
Thanks,
TG