Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

failed to authenticate to <ip> | adb wifi

Tags:

When connecting a device with ADB Wireless, got failed to authenticate to <ip>

adb devices gives the device shows up as unauthorized.

like image 918
sivag1 Avatar asked Oct 21 '13 02:10

sivag1


People also ask

Why adb connect not working?

Failed ADB connections usually have one root cause: bad Android USB drivers that load in place of the right ones. Windows doesn't make it easy to remove the wrong drivers, unfortunately. But before attempting to troubleshoot an ADB connection, first enable USB debugging on your phone if it's not on already.

How do I authorize a device on adb?

Open a command window and enter "adb devices". Watch the device's screen for any Authorization message and allow the connection.


2 Answers

From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB.

So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work.

like image 87
sivag1 Avatar answered Sep 20 '22 21:09

sivag1


Solution

1 Connect device(over USB) to computer (WINDOWS).

2 Authorize adb device, so it can communicate(handshake over USB) with computer

3 Check that the device is connected

$adb devices  List of devices attached  SC8SDQWGKBT4JVS4        device 

4 Change to tcpip mode

$adb tcpip 5555  restarting in TCP mode port: 5555 

5 Connect device(over WIFI) to computer, make sure both are on the same network

$adb connect 192.168.1.100  connected to 192.168.1.100:5555 

6 Authorize adb device, so it can communicate(handshake over WIFI) with computer

7 Check that the device is connected

$adb devices  List of devices attached  SC8SDQWGKBT4JVS4        device  192.168.1.100:5555      unauthorized 

Although I authorized the device, adb is seeing things differently.

To get things working correctly, unplug device from USB because there is a connection over WIFI.

8 Kill the adb server

$adb kill-server 

9 Connect again over WIFI

$adb connect 192.168.1.100  * daemon not running. starting it now on port 5037 *  * daemon started successfully *  connected to 192.168.1.100:5555 

10 Finally, Check that the device is connect

$adb devices  List of devices attached  192.168.1.100:5555      device 

Device is now authorized, you can start debugging over WIFI.

like image 43
Philip Herbert Avatar answered Sep 21 '22 21:09

Philip Herbert