ADB Android Device Unauthorized

Question

Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.

Unplug/plug, Uncheck/check "Debug Enabled", adb kill-server/adb start-server, restart phone/computer doesn't work for me. On the device authorize dialog never appears (but I remember that dialog appeared before reinstallation). I have no idea how to force this authorize dialog to display. There is no abd_key.pub file in .android directory. When i try read cpu info DDMS says:

[2014-04-15 12:47:06 - DDMS] device unauthorized. Please check the confirmation dialog on your device.

Any ideas? Is it possible to generate keys manually without confirmation dialog?

USB Connection

Wireless Connection

Answer 1

I just try adb kill-server, it works for me:

PS C:\Users\languoguang> adb devices
List of devices attached
MKJ0117A19000186        unauthorized
PS C:\Users\languoguang> adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

kill and start adb server:

PS C:\Users\languoguang> adb kill-server
PS C:\Users\languoguang> adb start-server
* daemon not running; starting now at tcp:12345
* daemon started successfully
PS C:\Users\languoguang> adb devices
List of devices attached
MKJ0117A19000186        device

Answer 2

Here's what I did that that brought the authorization prompt and made my device appear. I used a Samsung Galaxy s7 edge.

1. Enable developer mode and USB debugging on your device.

2. Revoke the USB debugging authorization

3. Plug your phone to computer via USB.

4. Drag notification panel and select "Software Installation" as shown in the image below

   

5. This will begin installing USB driver and the prompt for USB debugging authorization will show.

Answer 3

Check if you have Samsung Kies installed. That is one possible solution

Answer 4

You need to enable USB Debugging from Settings

Then if still the issue persists then run the following command

adb kill-server adb reverse tcp:8081 tcp:8081

Also try removing the cable and plug it again.

Answer 5

This is error because your window version haven't driver for usb 3.0 to receiver authenticate permission from phone. I spent 5 day with this bug. Now, install 58964_Intel(R)_USB_3.0 driver. And continue with awesome code!

i use this link to download driver

Answer 6

adb usb worked for me This restarts the adb daemon listening on the USB port The command returned:

error: device unauthorized. Please check the confirmation dialog on your device

. But the prompt for the RSA key showed up on the phone straight away. Once I approved, everything started working as expected

Answer 7

After installing Android studio, I had incorrect permissions on the folder "~/.android"(access for reading and writing only for root). So I changed it and ran project from Android studio(device still was marked as "unauthorized").

Android studio showed an error "Error installing apk", but in the folder "~/.android" were created files "adbkey", "adbkey.pub", "debug.keystore".

After that I restarted adb (ran commands adb kill-server and adb start-server) and authorization dialog appeared on my device.

Hopefully someone will approach this solution.

Answer 8

What I've done to solve the issue was to disconnect and reconnect the usb cable to the USB port again (done with another port on my machine).

Then I have chose to charge and that's it. The mobile device asked me to grant access for the machine, I agreed and that's solved the issue.

When running adb devices, I saw the device in the list.

(Done in Windows 10 home).

Answer 9

I was stuck on this for quite some time, and I was able to side-step the issue completely by copying the adbkey from a computer that my phone would connect to.

Answer 10

I'm using an older Huawei phone. When I plug in to my Debian Stretch instance I get the USB computer connection popup. If this is set to MTP, PTP or "Connect to PC software" I found that "adb devices" will fail. However, if I set the connection option to:

Mount SD Card

I then could run "adb devices" and status changed from unauthorized to device.

Also I turned on:

USB debugging

Answer 11

Not sure if someone encountered the same situation like me where I had plugged my phone to my laptop and trying to run the emulator. That's the reason I was getting this error. If that is the case then unplug your phone and try

Answer 12

If the kill-server and start-server doesn't work, go into dev settings on the device and Cancel the authorization for the current computer.

Answer 13

Linux-Ubuntu-14.04
I read all the answer for this post, nothing worked for me :(
This may be because I am not using normal end User device, working on corporate device!

Thing worked for me is:
Get VID,PID for your device from lsusb and update 51-android.rules (https://source.android.com/source/initializing.html#configuring-usb-access)
Ensure adb_usb.ini is also updated with same VID, PID

Answer 14

I tried many ways to solve this problem, this one works for me.

Install SnapPea on your PC. SnapPea

Plug your phone in USB Debugging mode and open SnapPea， a authorization dialog will show on your phone. The Dialog shows on the phone

Hope it helps.