The system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path. Which installed Android Debug Bridge version 1.0.29 in /usr/bin On deleting the symlink or recreating the folder it should work. In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)Īnd the symlink pointed to a nonexisting path which prevented saving any sdk settings. Stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both. (I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.ĭelete the computers adb key: rm /data/misc/adb/adb_key on device Now, the computers adb key was gone with the userdata folder of the sdk (the. It said: "error: device offline" when trying to access it. Then I wanted to pull some files from my CM10.1 nightly device per adb. I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it. (I was transferring data to a new harddrive and in the process
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |