Note: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
I can connect to the M9Pro with any version of ADB if I connect via TCPIP instead of USB cable. If the Android 4.2.2 is running the adbd Daemon that supports RSA key whitelists, you cannot connect to it with a version of ADB.exe (1.0.26) that doesn't supply a RSA key (would sort of defeat the new added security). When I use ADB 1.0.31, I can't connect to the adbd Daemon running on the M9Pro. That is even true if I use its own copy of ADB (1.0.31) to connect to itself with the USB port looped into the Host port. If you can use 1.0.31 via USB, I'll be encouraged to keep trying. When it does connect to an RSA aware version of adbd on the device, it should produce a prompt requiring the user to OK the USB connection from the ADB.exe client machine. I've just been assuming Pipo is still using an old version of adbd in /sbin:
root@android:/ # ls -l /sbin/adbd
ls -l /sbin/adbd
-rwxr-x--- root root 161804 1969-12-31 23:00 adbd
Maybe it is something on my PC that can't handle generation of the RSA key, but I would expect the M9Pro to be able to and for it not to be a "driver issue".
SO, when you do connect with 1.0.31, is it TCPIP or via USB? What you are doing the CD adb ends with android-sdk\platform-tools\? There, I have ADB.exe, adb-mac, and adb-linux but NO directory named adb anywhere in the SDK directory structure to CD to.
Comment