Android Studio - ADB Error - ...device unauthorized. Please check the confirmation dialog on your device.
you have missed the Fingerprint Certificate Authorization dialog in your phone when you connected it, try to change the USB mode to Media, or another different than the one you have in and then reconnect your device, or go to Developer Options -> Revoke USB Debugging and reconnect, watch for the dialog and click on accept, that should solve your problems.
If that doesn't work, set your ANDROID_SDK_HOME again, and then:
- Unplug device
Run:
adb kill-server
adb start-serverPlug in device
Android ADB devices unauthorized
Thankgod xda developers exist : http://forum.xda-developers.com/verizon-lg-g3/help/unable-to-access-adb-t2830087
Just had to delete adbkey file in C:Users/$Name/.android adbkey.pub was missing.
Restart after this and both files are there.
If this does not work :
- Try Revoke USB DEBUGGING Authorization.
- Enable USB debugging again.
ADB Android Device Unauthorized
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
ADB Android Device Unauthorized
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
Android studio Emulator ( device unauthorized)
Issue Resolved.
Step 1- Made a new emulator(Any).
Step 2- then fixed another problem the black screen by changing the settings to use hardware graphics.(Dunno if this problem was related to the bug)
And Bam every thing worked.
running adb devices showing unauthorized device?
This seems to be an issue with ADB version.
You may need to update your ADB.
Check using the follow, If older version, update to the latest.
$ adb version
Android Debug Bridge version 1.0.31
When you type:
$ adb devices
List of devices attached
TA93300ZP0 unauthorized
and you should get below notification on your phone
Select Ok
, and then when you issue
$ adb devices
List of devices attached
TA93300ZP0 device
You should be able to connect to your device.
If you select Always allow from this computer
.
This should fix your problem permanently.
Tested on Moto G (Android 4.4.4)
on Ubuntu 12.04
.
Android 8.0 adb device keeps unauthorized after authorisation
If you're using Windows follow these steps, after i tried every solution and almost gave up i found the following and it worked.
- First things first:
- Phone: Check if you have a file called adb_keys located at: /data/misc/adb/adb_keys. If you have it, i would recommend you to backup the file. (I didn't have it.)
Windows: You'll need to have a file called adbkey.pub located at C:/users/UserAccount/.android/
Boot into recovery mode.
- Plug your phone into PC.
Open cmd and run
adb devices
. It would show "recovery" instead "unauthorized".Create a new file called adb_keys file on your PC:
type NUL > adb_keys
Now you need to copy the contents from the adbkey.pub to adb_keys, the new file you just created:
adbkey.pub is located at C:/users/UserAccount/.android/
(Needless to say you need to replace "UserAccount" when running the command)type c:\users\UserAccount\.android\adbkey.pub > adb_keys
Upload the adb_keys file to your phone:
adb push adb_keys /data/misc/adb/adb_keys
Reboot and run adb devices. It should be working now.
Thank mnoguti from this post on XDA-Developers for this answer.
If you have Linux that's the same solution with Unix commands.
Related Topics
Gradle Duplicate Entry: Java.Util.Zip.Zipexception
How to Find the Android Version Name Programmatically
How to Configure Launcher Activity Programmatically in Android
Disable Home Button in Android Ics (4.0)
Checking My App Version Programmatically in Android Market
How to Detect If Any of My Activity Is Front-Most and Visible to User
Failure [Install_Failed_Older_Sdk] Android-L
Should Use "Sp" Instead of "Dp" for Text Sizes
How to Detect Android CPU Speed
Broadcast Receiver Not Working in Android Oreo
Can Not Set Debuggable Flag in Androidmanifest.Xml
Android: How to Get Current Opened Application Name on Screen
Gradle 0.9.+/0.9.2 Error: Unable to Load Class 'Com.Android.Builder.Testing.Api.Deviceprovider'
Cli on Dalvikvm Fails on Jni Lib
Android - What Is the Meaning of Stableids
Transfer Data from One Activity to Another Activity Using Intents