![]() ![]() ![]() ![]() (Note: there's a similar answer on SO that goes into further details for this method.) The other method is to simply copy your machine's adbkey.pub from the ~/.android/ directory, and put it into the problematic Android device's sdcard (using Web or MTP) named as adb_keys, then copy the file into the correct path: # On the problematic deviceĬp /sdcard/adbkey.pub /data/misc/adb/adb_keys Then put the working adb_keys file into the problematic Android device's sdcard (using Web or MTP) named as adb_keys, then copy the file into the correct path: # On the problematic deviceĬp /sdcard/adb_keys /data/misc/adb/adb_keys In the end, I found a very useful post here that suggested to manually put the contents of ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys file.įrom another working device, copy the adb_keys file into your computer: # On the other Android device Otherwise check for a confirmation dialog on your device. Try 'adb kill-server' if that seems wrong. This adb server's $ADB_VENDOR_KEYS is not set I was not getting any confirmation dialogĪdb: error: failed to get feature set: device unauthorized.I had root access from the local terminal. ![]() Removing my local ~/.android/adbkey did not help either.The /data/misc/adb contained no adb_keys file.I had an issue where the Settings app would crash when selecting Revoke USB debugging authorizations.None of the methods listed on this page worked for me specifically: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |