Set adb vendor keys

Question

EDIT: I figured out the problem, i think. ADB found out I wasn't on the latest updates (at&t released a stagefright udpate and i didnt know) so ADB didn't let me debug. Everything is fine now.

I have been debugging my app on an AT&T HTC One M8 for about a month. Suddenly today when I plugged in my phone, I didn't get the authorization popup. After an hour of troubleshooting, I found the problem, but not a solution.

This is the error i get in Android Studio 1.3.1:

device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I googled $ADB_VENDOR_KEYS but to no avail.

Information:

Phone: AT&T HTC One M8 running 5.0.1 (API 21)
Android Studio version 1.3.1 build 141.2135290
JDK Version: 1.8.0_60

How can I get the popup again? I need to debug my app

Try going into dev options on your device and clearing the access list. — JohanShogun, Aug 21 '15 at 05:51
Orthogonal to the issue, albeit, perhaps the following documentation resource may serve to be of any help, as to explain a meaning of the `ADB_VENDOR_KEYS` environment variable for its applications: _[Secure USB debugging in Android 4.2.2](http://nelenkov.blogspot.com/2013/02/secure-usb-debugging-in-android-422.html)_, by Nikolay Elenkov — Sean Champ, Apr 02 '16 at 03:30

score 69 · Answer 1 · edited Jul 09 '21 at 11:20

69

In this case what you can do is : Go in developer options on the device Uncheck "USB Debugging" then check it again A confirmation box should then appear

edited Jul 09 '21 at 11:20

Sam Joshua

310
6
17

answered Nov 17 '15 at 22:36

DvxWifiScan

691
5
3

1

In my case I had just forgotten to check this box in the first place, immediately fixed it. – JakeStrang Nov 08 '18 at 21:46
This IS the answer, no commands to execute, no complex keys generation... just disable and enable again the option – Mariano Ruiz Aug 07 '20 at 13:22

ColCh · Answer 2 · 2023-01-22T11:30:19.117

33

I tried almost anything but no help...

Every time was just this

➜  ~ adb devices    
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
aeef5e4e    unauthorized

However, I've managed to connect my device!

This is the step-by-step tutorial.

Remove existing adb keys on PC:

$ rm -v .android/adbkey .android/adbkey.pub

Remove existing authorized adb keys on device, the path is /data/misc/adb/adb_keys
Now create a new adb keypair

    adb I 47453 711886 adb_auth_host.cpp:220] generate_key '.android/adbkey'
    adb I 47453 711886 adb_auth_host.cpp:173] Writing public key to '.android/adbkey.pub'

Manually copy from PC .android/adbkey.pub (public key) to Device on path /data/misc/adb/adb_keys
Reboot the device and check adb devices :

➜  ~ adb devices
List of devices attached
aeef5e4e    device

Permissions of /data/misc/adb/adb_keys are (766/-rwxrw-rw-) on my device

edited Jan 22 '23 at 11:30

answered Feb 05 '17 at 13:43

ColCh

3,016
3
20
20

4

how can i "Remove existing authorized adb keys on device" on device which is still unauthorized by adb ? – Bourdier Jonathan Jun 19 '17 at 11:28
@BourdierJonathan using terminal app on device, or using "Revoke USB debugging authorization" menu entry under Developer Options – ColCh Jun 20 '17 at 12:51
2

@ColCh My screen is broken ! – Bourdier Jonathan Jun 21 '17 at 08:13
@BourdierJonathan try to reboot in recovery and make those manipulations with phone being in recovery mode – ColCh Jun 22 '17 at 12:01
using `scp`/`ssh` is also an option for copying `chmod`ing files (in case you can install SSHelper or anything similar) – frans Aug 04 '18 at 09:25
3

This is the most reliable solution, you might have to run 'adb shell' as root. – Mr. Fish Nov 15 '18 at 10:21
1

Just a note, if you want to add multiple PC as authorized to a single device, just append the public keys to `/data/misc/adb/adb_keys` – Santosh Kale Oct 18 '20 at 07:47
[Harald](https://stackoverflow.com/users/7761292) posted an [Answer](https://stackoverflow.com/a/66080503) saying "...After this procedure it didn't work at first. But an additional `adb kill-server` helped.Thanks ColCh...you saved my day and possible more in the future." – Scratte Feb 08 '21 at 05:18
You're welcome :D Sometimes I google this pesky adb problem, and find my own answer, so it saved also my day – ColCh Feb 08 '21 at 08:48

score 6 · Answer 3 · edited May 23 '17 at 12:18

6

look at this url Android adb devices unauthorized else briefly do the following:

look for adbkey with not extension in the platform-tools/.android and delete this file
look at C:\Users\*username*\.android) and delete adbkey
C:\Windows\System32\config\systemprofile\.android and delete adbkey

You may find it in one of the directories above. Or just search adbkey in the Parent folders above then locate and delete.

edited May 23 '17 at 12:18

Community

1
1

answered Aug 27 '15 at 12:17

Mlu

61
1

1

I figured out the problem. ADB found out that I wasn't on the latest updates ( I didn't know AT&T released the stagefright update) so it didn't let me debug – LonelyIdiot Aug 28 '15 at 03:48

score 6 · Answer 4 · edited Feb 09 '19 at 20:30

6

If you have an AVD, this might help.

Open the AVD Manager from Android Studio. Choose the dropdown in the right most of your device row. Then do Wipe Data. Restart your virtual device, and ADB will work.

edited Feb 09 '19 at 20:30

Narek Torosyan

99
2
10

answered Oct 13 '17 at 16:48

subash

3,116
3
18
22

The best answer ever!!! It worked for me. – nosequeweaponer Aug 10 '23 at 02:11

score 4 · Answer 5 · edited May 23 '17 at 11:54

4

I tried every method listed here and in Android adb devices unauthorized

What eventually worked for me was the option just below USB Debugging 'Revoke auths'

edited May 23 '17 at 11:54

Community

1
1

answered Jan 30 '16 at 15:31

killjoy

940
1
11
16

score 4 · Answer 6 · answered Apr 15 '19 at 20:29

I had the same problem running Ubuntu 18.04. I tried multiple solutions but my device (OnePlus 5T) was always unauthorized.

Solution

Configure udev rules on Ubuntu. To do this, just follow the official documentation: https://developer.android.com/studio/run/device

The idVendor of my device (OnePlus) is not listed. To get it, just connect your device and use lsusb:

Bus 003 Device 008: ID 2a70:4ee7

In this example, 2a70 is the idVendor.
Remove existing adb keys on Ubuntu:

rm -v ~/.android/adbkey* ~/.android/adbkey ~/.android/adbkey.pub
'Revoke USB debugging authorizations' on your device configuration (developer options).
Finally, restart the adb server to create a new key:

sudo adb kill-server sudo adb devices

After that, I got the authorization prompt on my device and I authorized it.

score 3 · Answer 7 · answered Aug 14 '17 at 03:47

3

Sometimes you just need to recreate new device

answered Aug 14 '17 at 03:47

IvanM

2,913
2
30
30

Set adb vendor keys

7 Answers7

Linked