I have search XDA, and the net as a whole, and I have found many people with this same problem, and a few that were able to fix it -- however none of the fixes have helped me.
The problem is that once the boot loader is unlocked, I am no longer prompted to allow a connection from ADB so the RSA key doesn't get installed. If I do an adb devices, it shows as unauthorized.
This isn't a huge issue since I can still use any terminal program and execute the same commands on the phone itself, however, that is not ideal. I would really like to be able to use adb and fastboot to pull images, dump files, etc to my PC. As it stands now, I have to use a wireless KB / mouse, execute the commands in a terminal, and then transfer the files to my laptop.
I have tried taking the key that gets generated in %appdata%\.android and copying it to /data/misc/adb/adb_keys, and /adb_keys and /data/adb/adb_keys. I have also tried setting the build.prob variable ro.adb.secure to 0 -- no luck.
If anyone has any other ideas, it would be greatly appreciated. Again, this only happens once I unlock the boot loader (which is needed to root MM). Stock MM gives the prompt on the phone, and I can communicate just fine with adb and fastboot (obviously, need fastboot to unlock the bootloader :) ).
EDIT: I have an MS631 -- not sure if H631 has this same problem.
-- Brian
The problem is that once the boot loader is unlocked, I am no longer prompted to allow a connection from ADB so the RSA key doesn't get installed. If I do an adb devices, it shows as unauthorized.
This isn't a huge issue since I can still use any terminal program and execute the same commands on the phone itself, however, that is not ideal. I would really like to be able to use adb and fastboot to pull images, dump files, etc to my PC. As it stands now, I have to use a wireless KB / mouse, execute the commands in a terminal, and then transfer the files to my laptop.
I have tried taking the key that gets generated in %appdata%\.android and copying it to /data/misc/adb/adb_keys, and /adb_keys and /data/adb/adb_keys. I have also tried setting the build.prob variable ro.adb.secure to 0 -- no luck.
If anyone has any other ideas, it would be greatly appreciated. Again, this only happens once I unlock the boot loader (which is needed to root MM). Stock MM gives the prompt on the phone, and I can communicate just fine with adb and fastboot (obviously, need fastboot to unlock the bootloader :) ).
EDIT: I have an MS631 -- not sure if H631 has this same problem.
-- Brian
from xda-developers http://ift.tt/1Z3AG8R
via IFTTT
Aucun commentaire:
Enregistrer un commentaire