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 Via USB

Wireless Connection Via Wi-fi

Random guess, but what if you delete all debug authorizations in settings on the phone. — Chris Stratton, Apr 15 '14 at 13:19
1. unplug, 2. goto the developer menu, 3. remove all allowed devices, 4. replug the usb to your pc, 5. on the pop-up on your phone select remember, click allow, done! 6. ? 7. profit! — , Dec 04 '15 at 18:49
If you followed all this steps and still don't get a prompt to authorize the RSA fingerprint try deleting $HOME/.android/adbkey as suggested here: http://stackoverflow.com/questions/31638582/android-adb-devices-unauthorized — Romina Liuzzi, Aug 03 '16 at 11:19
I can't get the "pop-up on your phone requesting permission" to pop up. Yes I did everything in the newb suggestions, like revoke all authorizations, bounce the "USB debugging" button, reseat the cable, etc... — Phlip, Apr 02 '22 at 17:19

score 1394 · Accepted Answer · edited Oct 24 '14 at 08:13

1394

It's likely that the device is no longer authorized on ADB for whatever reason.

1. Check if authorized:

<ANDROID_SDK_HOME>\platform-tools>adb devices
List of devices attached
4df798d76f98cf6d        unauthorized

2. Revoke USB Debugging on phone

If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII).

3. Restart ADB Server:

Then restarted adb server

adb kill-server
adb start-server

4. Reconnect the device

The device will ask if you are agree to connect the computer id. You need to confirm it.

5. Now Check the device

It is now authorized!

adb devices
<ANDROID_SDK_HOME>\platform-tools>adb devices
List of devices attached
4df798d76f98cf6d        device

edited Oct 24 '14 at 08:13

Michael G

129
10

answered Aug 28 '14 at 10:15

Martin

13,980
2
12
3

7

Step two was not necessary here, but couldn't find that menu either. – Simon Forsberg Feb 06 '15 at 14:02
93

The device didn't ask (or I didn't see it ask) if to agree to reconnect, but after following the above steps, then turn off and turn back on usb-debugging, it worked. – Jack BeNimble Apr 03 '15 at 20:32
When the `List of devices attached` was empty, mysteriously for my 4.3 device, doing these steps actually helped it to show the device. (I also had to turn off the mtp and ptp usb modes I'd enabled when trouble shooting earlier as they would oscillate between debugging and media device modes). – dlamblin Aug 05 '15 at 05:21
3

Didn't work for me; Android 6.0 Marshmallow has no option "Revoke USB debugging authorization." Note: after killing ADB, I get "This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong"; as well as "error: device unauthorized" etc. – Aaron Campbell Oct 30 '15 at 22:34
I did have to plug int it and unplug it a few times to get the authorize dialog on the device. Also toggled usb debugging a few times too – Dave Pile Feb 29 '16 at 23:18
2

I can't find option "Revoke USB debugging authorization" on Android 4.4.4. Where is it? – JohnyTex Apr 13 '16 at 09:18
1

Worked great, though I had to make sure 'Stay awake' is selected since if it's not, it ends up killing the connection and going back to 'unauthorized' when the screen goes dark. – Water Jan 09 '17 at 01:00
10

If your device doesn't prompt for authorization it might be because the account you're running `adb` from doesn't have permission to handle keys. If this happens to you, try it elevated permissions (e.g. `sudo`). – MatrixManAtYrService Aug 27 '17 at 20:54
Revoke USB debugging authorization was deprecated and is no longer available. – Aero Wang Sep 07 '17 at 07:45
For those who didn't get a prompt on your devices, please run the command with sudo. It works for me. – hellojoshhhy Oct 12 '17 at 02:22
I got Settings has stopped on Emulator – Hitesh Sahu Oct 24 '17 at 05:40
1

helped: adb kill-server, adb start-server – Sergii Dec 12 '18 at 14:02
Sometimes this variant is not work. In that case I do all steps and then connect device into another USB-port on my PC – Vladimir Eremeev Feb 12 '19 at 07:35
If you don't want to mess with command line actions, open the task manager and kill the background process adb.exe. It's the only step I needed. – Androidcoder May 05 '19 at 13:37
Eventually my mobile asked for the permissions (pop up message that I need to approve), this was the key to get 'device' instead of 'unauthorized'. – Melroy van den Berg Aug 31 '21 at 23:43
5

Turn USB debugging off and On again. Only way it worked for me... – Akintunde May 08 '22 at 05:42
I had to turn off and on Developer options instead of "Revoke USB debugging authorization", just as @khamidjon-khamidov pointed out in his answer. (Android 10, Redmi 7A) – Felix Jan 31 '23 at 14:01
Depends on your device/Android, BUT the device has to allow the computer connecting FIRST, only then it can enter the "allow debugging layer". On Linux, this means: have your device attached, then go to Nautilus and click the device on the left bar. It will prompt "Allow connecting to the computer." ONLY after that, and with the adb server running, it will prompt for the debugging connection. – isync Aug 13 '23 at 18:11

score 125 · Answer 2 · edited Mar 30 '23 at 12:53

125

Try forcing ADB to create new keys.

On Linux/OSX:

  $ mv ~/.android/adbkey ~/.android/adbkey.old
  $ mv ~/.android/adbkey.pub ~/.android/adbkey.pub.old
  $ adb kill-server
  $ adb start-server

On Windows 10 (thank you, Pau Coma Ramirez, Naveen and d4c0d312!):
- Go to %HOMEPATH%\Android\.android\
- Look for files called adbkey or adbkey.pub.
- Delete these files. Or, if you want to be on the safe side, move them to another directory.
- Repeat the above steps in %USERPROFILE%\.android\
- Try again

After this I didn't even need to unplug my phone: the authorization prompt was already there.

edited Mar 30 '23 at 12:53

raveren

17,799
12
70
83

answered Mar 19 '19 at 14:42

e18r

7,578
4
45
40

4

For Windows check the keys in `%HOMEPATH%\.android\ ` or `%USERPROFILE%\.android\ ` . Thank you, This one worked for me! – Pau Coma Ramirez Jul 11 '19 at 17:47
What keys I have to check here "%USERPROFILE%\.android\".Please eloborate.I didn't get it. – Naveen Sep 03 '19 at 16:30
@Naveen go to that directory and remove or rename the files called adbkey and adbkey.pub – e18r Sep 05 '19 at 01:32
@e18r I only have adbkey file, I dont have adbkey.pub file.Will this be any problem ?? – Naveen Sep 05 '19 at 08:52
1

@Naveen that's probably the issue. Delete adbkey.pub and try again to see if both keys get regenerated. – e18r Sep 06 '19 at 12:25
1

Thank you! On Windows 10, this is what got it working for me. – BlueSilver Oct 05 '19 at 08:53
1

On Windows 10 you need to delete both %HOMEPATH%\Android\.android\ and %USERPROFILE%\.android\ – d4c0d312 Apr 17 '20 at 16:09
I don't have those two files in `%HOMEPATH%\Android\.android\` – IOviSpot Aug 30 '22 at 13:23
And none of the answers worked for me, not even this one. – IOviSpot Aug 30 '22 at 13:27

score 98 · Answer 3 · edited May 13 '19 at 18:33

98

Ohhh finally I figured it out! After removing Eclipse directory I installed it into another directory.

echo %ANDROID_SDK_HOME%

has displayed wrong path to sdk directory.

set ANDROID_SDK_HOME "E:\adt-bundle-windows-x86_64-20140321\sdk"
unplug device
adb kill-server
adb start-server
plug device

After these steps, I was able to see confirmation dialog with RSA fingerprint on my phone :)

edited May 13 '19 at 18:33

Reaz Murshed

23,691
13
78
98

answered Apr 15 '14 at 14:20

Quak

6,923
4
18
22

it's not showing debug enabling dialog...any suggestion here! – CoDe Sep 22 '14 at 06:59
1

Setting the environment variable worked for me, but I had to perform a reboot for it to take effect. – Tim S. Van Haren Dec 10 '14 at 14:54
In my case an environment variable of ANDROID_HOME_SDK point to 'E:\android-sdk\SDK Manager.exe' which wrong. so, after I change to 'E:\android-sdk' I try to echo like him said but enviroment seem not to update. so, I restart pc -> unplug usb -> adb kill-server -> adb start-server -> plug usb -> work ! – Jongz Puangput Oct 21 '15 at 09:45
I was using adb kill-server and adb start-server that doesn't work but when when unplug device and use these the command it worked thanks! – Yirga Dec 21 '16 at 18:19
Steps 2-5 helped me. The only weird thing - step 4 did not work without sudo. I mean, it did start the server, no errors. But authorization popup did not appear on the phone. (And after step 2 I've cleared all stored authorizations on the device, not sure if it was important) – Евгений Савичев Oct 05 '18 at 17:38

score 57 · Answer 4 · edited Jun 29 '14 at 06:50

57

I run into the same issues with nexus7.

Following worked for fixing this.

Open Developer option in the Settings menu on your device.
Switch off the button on the upper right of the screen.
Delete all debug permission from the list of the menu.
Switch on the button on the upper right of the screen.

now reconnect your device to your PC and everything should be fine.

Sorry for my poor english and some name of the menus(buttons) can be incorrect in your language because mine is Japanese.

edited Jun 29 '14 at 06:50

Harpreet Singh

2,651
21
31

answered Jun 29 '14 at 06:10

user3787209

571
4
3

5

This worked for me. step 3 seemed vague, but for that I "revoked usb debugging authorization." When I connected the device back up (after enabling debugging options and usb debugging again) it prompted me to save the computer's RSA key. Thanks :) – SgtPooki Sep 11 '14 at 18:38
This worked for me on a Wiko Lenny. Disconnect device, switch ``Developer`` mode off, revoke debug permissions, turn ``Developer`` options back on, reconnect device, re-enable ``USB debugging``. – user1438038 Jan 02 '15 at 15:50
After trying to fix this for a while, `Revoke USB Debugging Authorization` now makes my emulator hard-reset. Quality. – Timmmm Mar 25 '19 at 22:45

Tim Boland · Answer 5 · 2017-05-19T00:50:36.500

47

I had the same problem. It was resolved by setting "USB computer connection" to "Camera (PTP)" instead of "Media Device (MTP)

edited May 19 '17 at 00:50

answered Oct 31 '14 at 00:06

Tim Boland

1,872
4
23
37

1

Only way is working for my `ID 1004:631d LG Electronics, Inc. Optimus Android Phone (Camera/PTP Mode)` Thank you! – josejuan Jul 21 '15 at 20:53
1

this worked for me too.. on redmi note 3 NitrogeOS 7.1.2 – ashishsony Apr 16 '17 at 17:02
Did it for me on OnePlus One Lineage 14.1. – Alex Bergsland May 18 '17 at 19:19
Worked for me on a Samsung Galaxy S4 Active. – Étienne Nov 06 '18 at 09:46
Tried everything, only this solution worked (setting a different USB mode - Transferring Images - in "default USB configuration"). The machine has a rather old motherboard (with an old chipset) and an AMD CPU, so this seem to a driver-related issue. – Javad May 15 '19 at 14:56
1

Worked on S20+ with Android 11. Set the para to "image transfer". Then I had the prompt on my device in order to authorize it. Thanks ! – toto_tata Jan 05 '21 at 07:57
4

I connected my Samsung Galaxy S21 5G running Android 11 to my Mac Mini (2018) running macOS 11.6, but my phone wasn't prompting for authorization. I changed "Use USB for" from "Transferring files / Android Auto" to "Transferring images" and that worked – Adam Taylor Oct 13 '21 at 21:50
Good answer and often overlooked. It was on share files by default, I put it on only charge and the auth request popped up on the phone. – ThaJay Apr 12 '22 at 11:16
where to change this options (Android emulator Pixel4, API30) ? – CodeBy Aug 24 '22 at 09:25

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

I wasted hours on this stupid issue. None of the above solutions worked for me on their own.

I'm running Windows 10. I had an old manual install of the Android SDK as well as Android Studio's SDK. I deleted my manually installed SDK and all my devices stopped working. These were the symptoms:

$ adb usb
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.

as well as

$ adb devices
List of devices attached
id1        unauthorized
id2        unauthorized
id3        unauthorized

To be honest I'm not sure which of these steps got me my Allow USB debugging? prompts back so I listed EVERYTHING for completeness. Goes in order from easiest to hardest. Most people seem to be back on their feet after the first two sections.

Restart ADB

I would perform this after each of the sections below.

adb kill-server
adb usb

Go crazy with developer options

Turn Developer options off and back on
Turn USB debugging off and back on
Revoke USB debugging authorizations. Try this while USB debugging is on and if possible try also when USB debugging is off.

Replug devices

Unplug and replug USB cable into phone.
Switch physical ports on your PC that your USB cable is connected into
Switch physical USB cables you're using to connect your devices

Start rebooting everything

Reboot all your devices and connect again
Reboot your PC
Toggle WIFI on and off

Start deleting things

CAUTION Delete your ~/.android folder. Sometimes this folder can have the wrong permissions which can cause issues. You might want to back this folder up first.
Uninstall all manufacturer specific drivers from add/remove programs. I uninstalled the following (names are not exact)
- LG United USB Driver
- HTC Mobile USB Driver
- OnePlus USB Drivers 1.00
- Samsung USB Driver
I also uninstalled all emulators and their respective drivers (optional)
- Nox & related drivers
- Bluestacks
- Genymotion

Erase all Android related environment variables.

Delete %ANDROID_HOME% if you have it set
Delete %ANDROID_SDK_HOME% if you have it set

At this point all my devices magically came to life and started displaying the Allow USB debugging? prompts and connecting properly through ADB. If you've made it this far and haven't found a solution, I am truly sorry you're in this predicament. Make sure you've restarted all devices and your dev machine at the end of all of these steps and connect to a fresh USB port using a new cable.

If that still doesn't work try some of these other SO posts on the subject:

None of the other suggestions here worked, but this one got me on the right tracks. The ~/.android directory part is almost right. After a recent Android Studio update for SDK adb stopped working, with exectly these symptoms. In the end I found out that ~/.android/adbkey and ~/.android/adbkey.pub were both 0-sized files, so I've deleted them, restarted adb server, et voila! Got my auth prompt immediatelly. — mkilmanas, May 11 '17 at 07:26
Thanks. Deleting ~/.android solved it for me after having done everything else and staying there for long as well! — Sheila, Oct 07 '18 at 06:37
Deleting the adbkey file did it for me. After I reset device, pc etc and deleting this; — Kevin Cloet, Sep 03 '19 at 12:15
Replacing the USB cable did it for me. My symptoms were that "adb devices" lists the status of any device as "authorizing". I have a USB hub with 4 USB-A ports connected to one of the MacBook's USB-C ports. I connect the phone thru that with a USB-A-to-USB-C cable (as well as an external keyboard and mouse). Connecting the phone directly with a USB-C-to-C cable fixed the issue. (Note that the previous setup was fine from macOS Mavericks thru Mojave on past MacBooks, and on High Sierra and Mojave on this one.) — Andy Marchewka, Jul 30 '20 at 13:02

Khamidjon Khamidov · Answer 7 · 2022-01-06T05:33:43.383

30

For me, I firstly unauthorized my device accidentally which I found out later. To revert it back to reauthorise:

Disconnect USB device from laptop/computer
Click 'Revoke USB debugging authorisations' in Developer options.
Disable developer options on top.
re-enable it again.
enable USB debugging
run command 'adb kill-server' on terminal
run command 'adb start-server' on terminal
connect your mobile device to laptop/computer
reauthorize
press like)

Note: if above doesn't work, trying restarting your laptop before connecting again

edited Jan 06 '22 at 05:33

answered Jul 26 '21 at 07:39

Khamidjon Khamidov

6,783
6
31
62

In my case This WORKED!!! – Khamidjon Khamidov May 03 '22 at 07:46
Validated steps in Sep-2022 on Android-11. – Shiraz Sep 29 '22 at 20:03
Thanks, disabling developer options was the missing step in my case! – Felix Jan 31 '23 at 14:02
this worked for me – Canh Nguyen Aug 18 '23 at 03:48

score 18 · Answer 8 · answered May 22 '16 at 20:17

18

Steps that worked for me:
1. Disconnect phone from usb cable
2. Revoke USB Debugging on phone
3. Restart the device
4. Reconnect the device
The most important part was rebooting the device. Didn't work without it .

answered May 22 '16 at 20:17

vovahost

34,185
17
113
116

1

From my experience working with AndroidTV devices I remember them behaving the same as a normal phone so you should try it out. – vovahost Mar 05 '19 at 13:13

Shimmy Weitzhandler · Answer 9 · 2021-04-28T14:28:55.257

17

After having spent over an hour going in rounds swearing at Samsung (mostly), Google, and who not, here are my findings, that finally helped me get the device recognized:

On Device:
- Set developer mode
- Allow USB debugging
- Default USB configuration > Select USB tethering
- Connect device to PC USB
On PC:
- Elevated cmd/ps prompt (maybe not mandatory, but that was my drill)
- adb kill-server (precede with .\ in ps)
- adb start-server (while device connected) > watch for prompt on device
On device:
- Always allow connections from this computer > Yes
On PC:
- adb devices gets the following output:

List of devices attached
278c250cce217ece        device

edited Apr 28 '21 at 14:28

answered Aug 02 '20 at 13:27

Shimmy Weitzhandler

101,809
122
424
632

1

Omg you are my HERO <3! I tried everything else for hours and it didn't work! – novas1r1 Apr 14 '23 at 12:22
Default USB Configuration -> Select USB Tethering worked for me. – Abdul Basit Rishi May 12 '23 at 08:07

score 15 · Answer 10 · answered Nov 18 '14 at 11:55

For reference, I just encountered much the same issue on Linux and had a hell of a time figuring it out. I eventually determined that I had a ~/.android directory that was root owned (thanks to running adb as root, while flailing around trying to figure out other connection problems). Deleting that root owned ~/.android directory resolved the missing authorisation dialog next time I reconnected the device.

It's possible that simply changing the ownership would also have fixed the problem - I'm guessing it was a simple lack of access to the adb key file stored inside that was the root of the problem. I didn't verify that, though, and I'm not going to deliberately break my hard-won connectivity just so I can check ;-)

To me, the issue was the `~/.android` folder lacked the `adbkey.pub` file. — That Brazilian Guy, Jun 12 '19 at 19:25

score 13 · Answer 11 · answered Apr 18 '22 at 21:14

13

Recheck 'USB Debug' option in developer options helped me

answered Apr 18 '22 at 21:14

Alexmelyon

1,168
11
18

score 12 · Answer 12 · edited May 23 '17 at 12:34

12

Had similar issue on osx and Nexus 5 (A6.0.1). I did get the authorization pop-up and confirmed it, despite that Android Studio nor any other IDE could connect to device.

Turned out my Nexus (rooted) was missing key files.

Rebooted Android device into recovery
Ran code pasted below
Rebooted Android device, adb now identifies device

Push key from computer to Android device:

 cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys

Solution came from here

edited May 23 '17 at 12:34

Community

1
1

answered Sep 30 '16 at 06:22

Deko

1,028
2
15
24

1

THIS is the answer for a device which can't show an ADB authorization dialog (like when having a custom kernel installed) – BamsBamx Feb 04 '20 at 00:50

score 9 · Answer 13 · answered Nov 14 '14 at 02:57

I was getting this error with my Nexus 10. I tried all of the answers I could find, and then I realized I was using a different USB port than usual. I switched to using the port I usually use, which is on the other side of my laptop, and the authorization popped up on my tablet!

score 8 · Answer 14 · answered Apr 15 '14 at 12:55

8

As the message have stated, you need to allow the adb access on your phone.

You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.

IF your device doesnt shows any messages when connected to the PC.Just do this.

Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.

answered Apr 15 '14 at 12:55

ShihabSoft

835
6
15

3

Still no message. I don't know what to do now :( I don't want debug on emulator... – Quak Apr 15 '14 at 13:15
Unplug and replug works! This scenario occurs when enabling USB debugging for the first time. – David Douglas Aug 12 '14 at 08:47

score 7 · Answer 15 · answered Aug 24 '17 at 06:59

The solution is to copy your file ~/.android/adbkey.pub (on GNU/Linux, or %USERPROFILE%\.android\adbkey.pub on Windows) to Android, and place it as /data/misc/adb/adb_keys. You need root privileges to do that.

You can transfer the file any way you like (or are able to), be it USB, e-mail or a temporary file upload service. In my case, as it was a new Android-x86 installation in a Virtual Machine, no usable web browser, and with network/TCP adb not working, I had to actually type in the 715 characters.

At least it worked.

score 7 · Answer 16 · answered Mar 06 '19 at 09:12

7

If you are on ubuntu, try running the server as root:

sudo adb kill-server

sudo adb start-server

answered Mar 06 '19 at 09:12

Samson Maosa

472
5
11

1

this one helped me on Ubuntu 19.10 and Amazon Fire 7, thanks! – druss Mar 22 '20 at 21:05
I dunno why, but running with sudo works. Ubuntu 20.04.1 – Nakamoto Jan 09 '21 at 04:49

score 7 · Answer 17 · answered Oct 12 '21 at 10:30

7

Simply, turn off developer options from your device and again turn on, attach USB with the device and working system and turn on USB debugging.

answered Oct 12 '21 at 10:30

gaus

223
4
12

This has already been mentioned in other answers. *When answering older questions that already have answers, please make sure you provide either a novel solution or a significantly better explanation than existing answers.* – Eric Aya Oct 12 '21 at 10:34
1

In my case this worked for me. – Ranjit Vamadevan Nov 28 '21 at 12:52

Sakkeer Hussain · Answer 18 · 2016-03-12T07:31:51.643

6

I was tiered with this, I got that permission dialog by turning off wi-fi of my phone.

edited Mar 12 '16 at 07:31

answered Oct 23 '15 at 05:28

Sakkeer Hussain

459
6
19

score 5 · Answer 19 · edited Jun 19 '17 at 12:46

I was not getting the RSA fingerprint pop up on my phone.

I had to go into the

  C:\Users\<userName>\.android\adbkey and adbkey.pub

files, delete those and then do kill and restart of adb server. I had to stop and restart the debugger and connecting as USB in PTP mode.

Because the RSA authorisation key was getting stored in this path, killing and restarting the adb server didn't help.

score 5 · Answer 20 · answered May 21 '19 at 06:52

5

Disconnect your device from the computer.

Go into developer settings.

Turn off developer settings.

Turn on developer settings.

Enable USB Debugging (and whatever other settings you enabled beforehand)

Reconnect your device to the computer.

Try again.

Worked for me so hope it works for you!

answered May 21 '19 at 06:52

isXander

127
1
7

Worked immediately for me. Mush easier than most of these other methods. Thank you! – SeanMC Nov 29 '21 at 16:23

score 4 · Answer 21 · answered Jul 16 '17 at 12:36

4

This solved my issue!

run your android simulator
go to setting and enable developer mode
enable from the developer settings usb debugging

at this point you will get popup massage at you emulator to authorise the device and you are good to go :)

answered Jul 16 '17 at 12:36

Ofir Attal

1,136
10
10

score 4 · Answer 22 · edited Jul 01 '19 at 16:10

4

You should delete the file: c:\users\_user_name_\.android\adbkey

edited Jul 01 '19 at 16:10

Jared Forth

1,577
6
17
32

answered Jul 01 '19 at 14:03

Nash

51
3

This helped me along with following the 5-step process by @Martin. This can go between steps 2 and 3. – Cat Perry May 30 '20 at 02:07

score 2 · Answer 23 · answered Sep 12 '15 at 16:08

2

On some Samsung devices the mode change that can be set by dialing *#0808# doesn't stick without direct reboot. Once rebooted, dial the same string and make sure that you have adb + mdp selected and USB set to AP. After this make sure to reconnect phone and restart ADB server. Also try to avoid USB hubs and virtual machines witch surely complicate matter further. The follow the previously mentioned instructions for clearing authorized devices etc.

answered Sep 12 '15 at 16:08

not2qubit

14,531
8
95
135

Great! Works for Samsung Galaxy S5 Android 5.0 (OTA updated from KitKat). I should also mention that the issue only appeared on Windows 7 desktop. At windows 7 laptop and mini-mac it never asks for authorization! – madlymad Oct 14 '15 at 20:55

score 2 · Answer 24 · answered May 13 '19 at 18:48

I had a similar problem. However, it was solved using a different solution. I thought I might share this here as well. Let me describe my problem first.

I had the Android SDK in my ubuntu. The path to the android SDK was not in the environment variable path. I installed adb using a apt-get command and it could not find the sdk home folder and hence, it was showing the unauthorized error and the device was not popping up anything as well. I got stuck here.

Then I uninstalled the adb using apt-get purge which I installed earlier. The Android SDK has the adb program in the platform-tools folder. I just add the path to the environment variable and it worked like a charm.

export PATH=${PATH}:/home/YOUR-USERNAME/path/to/adb
adb devices
List of devices attached
f7f716d56905    device

Hence the problem was not setting the Android SDK to the environment variable path.

score 2 · Answer 25 · answered Jun 22 '19 at 17:29

2

The same issue started appearing once I changed my development device, it was solved as:

$ mv ~/.android/adbkey ~/.android/adbkey.old
$ mv ~/.android/adbkey.pub ~/.android/adbkey.pub.old
$ adb kill-server
$ adb start-server

answered Jun 22 '19 at 17:29

Hasan A Yousef

22,789
24
132
203

score 2 · Answer 26 · answered Aug 26 '22 at 06:00

2

I just had to follow these simple steps:

Remove the wire from laptop and phone.
Again attached the wire to my phone and laptop
Allowed debugging on the device.

And every thing started to work fine.

answered Aug 26 '22 at 06:00

Bilal Saeed

2,092
8
31

score 1 · Answer 27 · edited Jun 22 '21 at 20:06

1

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

edited Jun 22 '21 at 20:06

Cristian Ciupitu

20,270
7
50
76

answered Apr 15 '14 at 11:14

lantonis

143
14

Yup , in my case I wasn't using an of the shelf Android device , so I had to delete any previous adbkey files , and ask the device manufacturer to send me : adbkey and adbkey.pub ....but for regular devices , "Revoke USB Debugging on phone" seems to do the trick – rugby2312 Feb 05 '21 at 07:15

score 1 · Answer 28 · answered Oct 02 '14 at 14:29

I had the same message in two phones:

- Sony Xperia E
- Samsung Galaxy Core 2

both Android 4.4.2, and i solved it with these two steps:

1.- Updating my adb to 1.0.31, downloading the latest version of Android SDK from SDK Manager

You can check your adb version by typing

adb version

2.- Once the phone is plugged in USB Debugging mode, A message appears asking you to authorize this computer for debugging. You have to mark "Always allow this computer", and click on Allow.

Hope it helps.

i update the android sdk plateform-tools and it's work thinks (y) — zakaria, Jul 02 '20 at 10:05

score 1 · Answer 29 · answered Jan 28 '15 at 20:09

1

it's not may work for all situations but because i used a long cable my device doesnt connect properly and the message wont pop up change the cable may solve the problem

answered Jan 28 '15 at 20:09

Pazel1374

218
3
14

Languoguang · Answer 30 · 2018-06-29T01:44:10.697

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

score 1 · Answer 31 · edited May 28 '20 at 15:48

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

Enable developer mode and USB debugging on your device.
Revoke the USB debugging authorization
Plug your phone to computer via USB.
Drag notification panel and select "Software Installation" as shown in the image below
This will begin installing USB driver and the prompt for USB debugging authorization will show.

traktor · Answer 32 · 2022-03-29T02:48:24.760

"Device Unauthorized" when trying to screen mirror Huawei

I was redirected to this question from scrcpy's FAQ coverage of "Device Unauthorized" messages when trying to screen mirror an aging Huawei Elite S6 mobile phone to a Windows 10 PC.

With USB debugging enabled on the phone, no popup to authorize debugging appeared and strcpy output these errors on the terminal:

ERROR: Device is unauthorized:
ERROR:     -->   (usb)      AKTBBCB731702690      unauthorized
ERROR: A popup should open on the device to request authorization.
ERROR: Check the FAQ: <https://github.com/Genymobile/scrcpy/blob/master/FAQ.md>
ERROR: Server connection failed

The solution mostly relates to non-standard Huawei modifications to Android:

Connect the phone to the PC with a USB cable.
Drag down the notifications list from the top of the screen on the phone.
An icon titled "USB Connected" should appear in the list
Press "Photos" amongst the modes presented.

This answer suggested selecting "Camera" as the connection type. Although Huawei doesn't use the same wording or menu structure, choosing "Photos" solved issues that
- the "Files" option doesn't support adb authentication,
- the "USB drive" option (which appeared to work initially) prevents or stops phone apps accessing files on the sd card if this connection option is chosen.
Enable USB debugging if a popup appears.

Rerunning scrcpy at this stage worked as expected, with working mouse and PC keyboard input to apps on the phone. No reboots of the phone or PC should be needed during setup - check the tips below if things go wrong.

scrcpy Tips

Check "Stay Awake" under developer options in settings to prevent the screen being turned off while mirroring the phone, and turn it off again when done mirroring. Both can be performed from the PC.
Close the scrcpy GUI window to kill the adb process on Windows automatically: don't just close or abort the terminal window running scrcpy.exe.

score 1 · Answer 33 · answered Sep 13 '22 at 10:45

1

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.

answered Sep 13 '22 at 10:45

Ali Abbas

540
4
10

score 0 · Answer 34 · answered Oct 09 '14 at 10:47

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

score 0 · Answer 35 · answered Aug 06 '15 at 00:48

0

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

answered Aug 06 '15 at 00:48

Bobkatt

65
4

This just gives me "error: no devices/emulators found". – Jun 19 '17 at 12:48

score 0 · Answer 36 · answered Jan 16 '17 at 16:11

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.

score 0 · Answer 37 · answered Apr 22 '17 at 15:35

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).

score 0 · Answer 38 · answered Apr 25 '19 at 06:02

0

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.

answered Apr 25 '19 at 06:02

lbenedetto

2,022
1
21
39

score 0 · Answer 39 · answered May 23 '19 at 09:54

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

score 0 · Answer 40 · answered Sep 06 '21 at 03:15

0

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

answered Sep 06 '21 at 03:15

Sandeep Amarnath

5,463
3
33
43

score -1 · Answer 41 · answered Jan 13 '17 at 07:29

-1

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

answered Jan 13 '17 at 07:29

Bhavana Vadodariya

2,287
1
19
26

After giving -ve vote , people should add comment also, for a change ;) – Bhavana Vadodariya Jan 18 '17 at 13:08

Sanster · Answer 42 · 2015-03-03T02:25:47.927

-4

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.

edited Mar 03 '15 at 02:25

answered Mar 02 '15 at 06:51

Sanster

1
2

You should name your link like the software and you should explain what the software does. – Pablo Jomer Mar 02 '15 at 07:13
Sorry. It's a software like google play, you can download apps.@PabloKarlsson – Sanster Mar 03 '15 at 02:21