Adb ошибка device unauthorized

asked Apr 15, 2014 at 10:39

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

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.

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.

1. set ANDROID_SDK_HOME "E:\adt-bundle-windows-x86_64-20140321\sdk"
2. unplug device
3. adb kill-server
4. adb start-server
5. plug device

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

I run into the same issues with nexus7.

Following worked for fixing this.

1. Open Developer option in the Settings menu on your device.

2. Switch off the button on the upper right of the screen.

3. Delete all debug permission from the list of the menu.

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

answered Oct 31, 2014 at 0:06

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

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

Replug devices

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

Start rebooting everything

1. Reboot all your devices and connect again
2. Reboot your PC
3. Toggle WIFI on and off

Start deleting things

1. 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.
2. 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
3. I also uninstalled all emulators and their respective drivers (optional)
   • Nox & related drivers
   • Bluestacks
   • Genymotion

Erase all Android related environment variables.

1. Delete %ANDROID_HOME% if you have it set
2. 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:

• Android ADB device offline, can’t issue commands
• Can’t connect Nexus 4 to adb: unauthorized
• How to solve ADB device unauthorized in Android ADB host device?

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

1. Disconnect USB device from laptop/computer
2. Click ‘Revoke USB debugging authorisations’ in Developer options.
3. Disable developer options on top.
4. re-enable it again.
5. enable USB debugging
6. run command ‘adb kill-server‘ on terminal
7. run command ‘adb start-server‘ on terminal
8. connect your mobile device to laptop/computer
9. reauthorize
10. press like)

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

answered Jul 26, 2021 at 7:39

answered May 22, 2016 at 20: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:

1. On Device:
   • Set developer mode
   • Allow USB debugging
   • Default USB configuration > Select USB tethering
   • Connect device to PC USB
2. 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
3. On device:
   • Always allow connections from this computer > Yes
4. On PC:
   • adb devices gets the following output:

List of devices attached
278c250cce217ece        device

answered Aug 2, 2020 at 13:27

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

answered Nov 18, 2014 at 11:55

AlexmelyonAlexmelyon

1,16811 silver badges18 bronze badges

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

answered Nov 14, 2014 at 2:57

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, 2014 at 12:55

Marc.2377Marc.2377

7,8577 gold badges51 silver badges95 bronze badges

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

sudo adb kill-server

sudo adb start-server

answered Mar 6, 2019 at 9:12

answered Oct 12, 2021 at 10:30

answered Oct 23, 2015 at 5:28

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.

answered Apr 27, 2016 at 7:52

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, 2019 at 6:52

Ofir AttalOfir Attal

1,13610 silver badges10 bronze badges

answered Sep 12, 2015 at 16:08

Reaz MurshedReaz Murshed

23.7k13 gold badges78 silver badges98 bronze badges

Hasan A YousefHasan A Yousef

22.8k24 gold badges132 silver badges205 bronze badges

Bilal SaeedBilal Saeed

2,1128 silver badges31 bronze badges

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.

answered Oct 2, 2014 at 14:29

Pazel1374Pazel1374

2183 silver badges14 bronze badges

LanguoguangLanguoguang

2,1862 gold badges10 silver badges15 bronze badges

answered May 28, 2020 at 15:28