I am trying to connect adb device and it showing \"Please check the confirmation dialog on your device\" ..but there is no adb confirmation(rssi) dialog.
For me, selecting the Revoke USB debugging authorizations would crash the entire Settings app. Here's a simple method that worked for me (I had root access to the device):
The method is to simply copy your machine's
adbkey.pub
from the~/.android/
directory, and put it into the Android device's sdcard (using Web or MTP) named asadb_keys
, then copy the file into the correct path:# On the problematic device cp /sdcard/adbkey.pub /data/misc/adb/adb_keys
(Note: there's a similar answer on SO that goes into further details for this method.)
I have explained a bit more about this here, if anyone's interested.
I had the same problem. I have two different Linuxsystems on my computer. The installation on MX-Linux 19.3 xfce was very easy and working after a short time. The installation on Mint 19.3 Cinnamon would not work. All instructions i found in google didn't solve my problem. After deleting the files adbkey and adbkey.pub in my directory, i didn´t get these files, when i followed the instructions. I got always the status "device unauthorized" and did not get the "confirmation dialog on my device". Then i had a divine inspiration. In a console i gave me root permission via su and started there droidcam. I imediately got the confirmation dialog on my smartphone and the driodcam was working fine. The files adbkey and adbkey.pub are now in the directory /root/.android.
This usually happens when you miss accepting the RSA Key Notification at first.
Best would be to reset the setting.
Do as follows:
Switch OFF Developer's option
.
Under Developer Setting, Tap on Revoke USB Authorization
Switch ON Developer's option
Enable USB Debugging
, and you would see RSA Key Notification on device
You should immediately see the above notifiaction.
Select Always allow from this computer
and Ok.
To avoid further denial.
The link mentioned in your question should also work.
Might be some issue.
Update:
This might also be an Issue with your adb
binary version.
Check adb
version using:
$ adb version
Android Debug Bridge version 1.0.31
If you are using an older version please update.