Dev Stack Source

Answer : It's likely that the device is no longer authorized on ADB for whatever reason. 1. Check if authorized: <ANDROID_SDK_HOME>\platform-tools>adb devices List of devices attached 4df798d76f98cf6d unauthorized 2. Revoke USB Debugging on phone If the device is shown as unauthorized , go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII). 3. Restart ADB Server: Then restarted adb server adb kill-server adb start-server 4. Reconnect the device The device will ask if you are agree to connect the computer id. You need to confirm it. 5. Now Check the device It is now authorized! adb devices <ANDROID_SDK_HOME>\platform-tools>adb devices List of devices attached 4df798d76f98cf6d device Ohhh finally I figured it out! After removing Eclipse directory I installed it into another directory. echo %ANDROID_SDK_HOME% has displayed wrong p...

Answer : Try Revoke USB DEBUGGING Authorization. Enable USB debugging again. It worked. Thankgod xda developers exist : http://forum.xda-developers.com/verizon-lg-g3/help/unable-to-access-adb-t2830087 Just had to delete adbkey file in C:Users/$Name/.android adbkey.pub was missing. Restart after this and both files are there. If this does not work : - Try Revoke USB DEBUGGING Authorization. - Enable USB debugging again. In sequence: adb kill-server in your DEVICE SETUP, go to developer-options end disable usb-debugging press REVOKE USB debugging authorizations, click OK enable usb-debugging adb start-server