Nsryjdtyk

For me the complete steps that worked were :

• Settings -> Developer options -> Revoke USB debugging authorizations (clear the list of authorized PCs).




• Set USB Debugging OFF.




• In Terminal write : adb kill-server




• Then : adb start-server




• Then : adb connect xx.xx.xx.xx:5555 (the devices ip), it should say unable to connect.



• 
  

  Now turn ON USB debugging again and type the adb connect xx.xx.xx.xx:5555 again.

  
  
  

  It should now ask for authorization and you are back online without
  needing to connect cable to USB, only wifi used.

  
  

run adb kill-server, then try to connect wirelessly again. It worked for me.

Disconnect adb over wifi, connect your phone with a USB-cable to your pc. It will ask you on your phone is you want to allow the connection. Tick always allow. You will only get this when you connect with USB and have to do this only once, you can use over wifi afterwards.
Don't get the pop-up? Try the answers on google over a cable, since you need to do this first.

I could not find exact solution for this problem too.
Best way worked for me was disconnecting device from wifi, then try to connect while device is not connected to Wifi like:

adb connect 192.168.55.3:5555

this causes adb waiting for connection. immediately connect device to wifi and adb will detect device and connect again.
hope this helps.

It seems you want authenticate adb over wifi.If you had your device rooted,you can try this way.

• Copy ~/.android/adb_key.pub to your android device,and rename it to adb_keys




• Move it to your /data/misc/adb/




• Reboot your android,then reconnect over wifi.

For the first time in debug mode, you need to Authorize your phone with the PC, and that requires the USB cable. After that you can use Debug over WIFI.

If you want to force your phone to show the Authorization message box, simply delete the below file.

/data/misc/adb/adb_key

1. In android studio go to Preferences->Plugins


2. Download and install this plugin
   ADB WIFI Connect
   , restart Android Studio


3. Connect phone via USB


4. In android terminal use command: adb devicesyou should get visible device connected via USB:

List of devices attached



988a57334e57365058      device

5. Click on plugin icon in android studio AndroidWiFiADB


6. If phone get connected properly via WiFI, you see in event log:

12:41 Android WiFi ADB: Device 'ModelOfYourPhone' connected.

7. In android terminal use command: adb devices use should get

List of devices attached

988a57334e57365058      device

192.168.60.101:5555     device

8. Disconnect USB cable and re-check again adb devices, should remain only device connected via wifi:

List of devices attached

192.168.60.101:5555     device

Try disconnecting your device with:

abd disconnect <IP/TCP>:<port>

Then restart the WiFi connection of your device, and reconnect your device with:

abd connect <IP/TCP>:<port>

That may fix it; it worked for me.

My solution steps:

1. Turn Off WiFi and Turn it back On again.


2. Settings -> Developer options -> Revoke USB debugging authorizations.


3. Settings -> Developer options -> Turn Off ADB over network and turn it back On again.


4. adb kill-server


5. adb start-server


6. adb connect xx.xx.xx.xx:5555

Note: Step 3 was the key for me. don't forget it.

Note that wireless adb connectivity in Android 6.0.0 is broken. Updating to 6.0.1 fixes the issue.

https://stackoverflow.com/a/34530543/1123355

In Windows, if you are using system-wide proxy software like Proxifier, you need to add adb.exe to the ingore list or direct-mode list. In my case, using Proxifier will make adb able to connect to any IP address even when the phone is not connected to the WiFi, and this leads to device offline.

I know its late to answer but I believe this is the exact answer:

go to WIFI setting on your device and "set a new IP" in your network IP range an reconnect.

Conflicting ADB connections can cause this issue as well:

Windows Host with Docker to Hyper-V Android x86 emulator

I didn't see this answer here yet so for those attempting something similar, the issue I had was that the local Windows Host ADB process had already acquired the adb connection during start up (adb server start).

By simply running: adb disconnect <Device/Android x86 Hyper-V ip>:5555
on host machine

Running adb connect <Device/Android x86 Hyper-V ip>:5555 on the Docker container was able to successfully acquire the remote device (aka Android x86 Hyper-V)

IMPORTANT!!! Until you disconnect Docker (or whatever), your host machine (or any others) will not be able to connect, apparently only one ADB connection at a time is allowed.

I didn't need to do anything else listed above. Hope this helps others.

Just turn off your Proxifier or something else like this.

Socks5 works fine

I have this problem just now. Note that my case is special, the usb has been disabled for security concerns. Reboot not working. This is not ip problem since ping is working and nmap shows 5555 port is open. Also since I will not able to connect if port is wrong, so nothing to do with port.

There are 3 reasons:

1. Because another pc in the local network already connected, so the other guy have to adb disconnect first, then I can do adb disconnect and adb connect <ip>, since only one person can connect at the same time.




2. A hotspot ssid name might consists of multiple bssids in (especially you're in office) local network, so you need to ensure your pc try all the hotspot bssids which match the android connected hotspot bssid. Note that I noticed it's not always the case (Now I tried different bssids still success), but it did solved before.




3. Ensure the port 5555 is open correctly. Even though there are many ways, but you can download this app to open port 5555.

For me, the important part turned out to be the following line adb tcpip 5555 together with using the port in the IP of my phone like so: adb connect 192.168.1.87:5555 (only using one of them, did not work, i.e: writing the second alone didn't work, writing the first and then excluding the port in the IP also didn't work). The adb tcpip 5555 line is not mentioned anywhere here. So, for me, the PORT needed to be both manually set and used in the connect line!

These are the events of my command line in Windows PowerShell Admin to demonstrate (Wifi on and debug mode on and confirmed permission when the popup came):

notice that the connection first failed, then it said it was connected which is weird behavior to begin with (no matter what, it always failed once and "succeeded" once), and in both instances, the device showed as offline. The disconnect commands also confirm that its 110% offline

PS C:WINDOWSsystem32> adb kill-server

PS C:WINDOWSsystem32> adb start-server

error: protocol fault (couldn't read status): Connection reset by peer

PS C:WINDOWSsystem32> adb start-server

* daemon not running; starting now at tcp:5037

* daemon started successfully

PS C:WINDOWSsystem32> adb connect 192.168.1.87:5555

failed to connect to 192.168.1.87:5555

PS C:WINDOWSsystem32> adb devices

List of devices attached

220947272e047ece        device

192.168.1.87:5555       offline



PS C:WINDOWSsystem32> adb connect 192.168.1.87:5555

already connected to 192.168.1.87:5555

PS C:WINDOWSsystem32> adb devices

List of devices attached

220947272e047ece        device

192.168.1.87:5555       offline



PS C:WINDOWSsystem32> adb disconnect 192.168.1.87:5555

error: no such device '192.168.1.87:5555'

PS C:WINDOWSsystem32> adb disconnect 192.168.1.87:5555

error: no such device '192.168.1.87:5555'

PS C:WINDOWSsystem32> adb tcpip 5555

restarting in TCP mode port: 5555

PS C:WINDOWSsystem32> adb disconnect 192.168.1.87:5555

error: no such device '192.168.1.87:5555'

PS C:WINDOWSsystem32> adb connect 192.168.1.87:5555

connected to 192.168.1.87:5555

PS C:WINDOWSsystem32> adb devices

List of devices attached

220947272e047ece        device

192.168.1.87:5555       device

As soon as I added the adb tcpip 5555 command and it restarted in TCP mode port: 5555 the adb connect 192.168.1.87:5555 command worked!