The Android Debug Bridge, aka adb, has been an indispensable tool while unlocking and rooting my new Moto G5 Plus. I’ve used it dozens of times this week to push and pull files, run shells, and reboot my phone. Today, as is my habit, I ran the command adb devices after plugging my phone into my laptop, but the response I received made it obvious that I had some troubleshooting ahead of me.
tpodlaski@Alabama:~ ls -la ~/.android total 44 drwxr-x--- 5 tpodlaski tpodlaski 4096 May 9 10:31 . drwxr-xr-x 46 tpodlaski tpodlaski 4096 May 14 11:58 .. -rw------- 1 tpodlaski tpodlaski 1704 May 9 10:31 adbkey -rw-r--r-- 1 tpodlaski tpodlaski 719 May 9 10:31 adbkey.pub -rw-r--r-- 1 tpodlaski tpodlaski 185 Dec 19 21:21 analytics.settings drwxr-xr-x 2 tpodlaski tpodlaski 4096 Dec 19 21:24 avd drwxr-xr-x 2 tpodlaski tpodlaski 4096 Dec 19 19:31 cache -rw-r--r-- 1 tpodlaski tpodlaski 140 Dec 19 22:21 ddms.cfg -rw-r--r-- 1 tpodlaski tpodlaski 1258 Dec 19 21:20 debug.keystore drwxr-xr-x 3 tpodlaski tpodlaski 4096 Dec 19 21:31 monitor-workspace -rw-r--r-- 1 tpodlaski tpodlaski 36 Dec 19 19:31 uid.txt tpodlaski@Alabama:~ adb devices List of devices attached * daemon not running. starting it now at tcp:5037 * * daemon started successfully * ZY2243PNMF recovery
tpodlaski@Alabama:~ touch ~/adb_keys
tpodlaski@Alabama:~ adb push ~/adb_keys /data/misc/adb/adb_keys adb_keys: 1 file pushed. 0.3 MB/s (719 bytes in 0.003s)
tpodlaski@Alabama:~$ adb devices List of devices attached ZY2243PNMF device
And success! Success for me anyway. Your mileage, as always, may vary. While I am pleased to be authorized again and able to continue on my way, I am still wary of the fact that I don’t know what caused this issue in the first place and why I don’t have a Revoke USB Debugging Authorizations option in my settings. If you have any insight, I kindly ask that you clue me in by leaving a comment below. Thanks!