I just got the same problem today after my Nexus 7 and Galaxy Nexus were updated to Android 4.2.2. The thing that fixed it for me was to upgrade the SDK platform-tools to r16.0.1. For me, this version was not displayed in my SDK Manager, so I pulled it down from http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip directly. You then need to rename the platform-tools directory and unzip … Read more
By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to one of the following files: If you want adb shell to start as root by default – then add ro.secure=0 as well. Alternatively you could use modified adbd binary (which does not check for ro.debuggable) From https://android.googlesource.com/platform/system/core/+/master/adb/daemon/main.cpp
Connect Android phone and host machine to same WiFi network Connect Android phone to host machine using USB cable (to start with) Run adb tcpip 5555 from a command prompt Run adb shell “ip addr show wlan0 | grep -e wlan0$ | cut -d\” \” -f 6 | cut -d/ -f 1″ to obtain the phone’s IP address Disconnect USB cable … Read more
Edit: In newer Android Studio versions you can re-sync the project using this button: For older versions: Open Gradle window (on the right side in Android Studio) and click on the refresh button. However it is not a 100% sure fix. Solutions for other cases: Open terminal window and type “adb kill-server”, then type “adb … Read more
It’s likely that the device is no longer authorized on ADB for whatever reason. 1. Check if authorized: 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 4. … Read more
In this case what you can do is : Go in developer options on the device Uncheck “USB Debugging” then check it again A confirmation box should then appear
By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to one of the following files: If you want adb shell to start as root by default – then add ro.secure=0 as well. Alternatively you could use modified adbd binary (which does not check for ro.debuggable) From https://android.googlesource.com/platform/system/core/+/master/adb/daemon/main.cpp
Looks like the installed driver was in bad state. Here is what I did to make it work: Delete the device from Device Manager. Rescan for hardware changes. List item “Slate 21” will show up with “Unknown driver” status. Click on “Update Driver” and select /extras/google/usb_driver Device Manager will find the driver and warn you … Read more
I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed “Android SDK Tools”, “Android SDK Platform-tools”, and Google USB Driver. I have checked the setting on my Nexus 10 for “Unknown Sources”. When I run “adb devices” from the command terminal, it … Read more
Use a fully-qualified path to the desktop (e.g., /home/mmurphy/Desktop). Example: adb pull sdcard/log.txt /home/mmurphy/Desktop