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 fin

Answer 1

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!

Answer 2

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.

Answer 3

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

Answer 4

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

Answer 5

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

Answer 6

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