I used the SAMSUNG Android ADB Interface driver. Once in Recovery, go to Device Manager on your PC, and change the driver for the phone. If you don’t have a recovery installed, you’ll have to boot into the bootloader (same buttons as above just use volume down instead), and then use Fastboot to install a custom recovery (like CWM or TWRP). Let go of the power button when the screen comes on. Power off the phone, plug it into your computer and power it up in Recovery mode with (this is for a Samsung Galaxy S3) holding down the power button, volume up and menu at the same time. Close the SDK Manager when done.Ĭlose Android Studio. Now, tick “Android SDK Platform-tools” under Tools, and “Google USB Driver” under Extras. Click “Deselect All” then ”Select Updates”. You’ll probably also have to create a JAVA_HOME environment variable. Since there’s a good chance you don’t have a 64-bit JDK installed too, go to this link and download the latest JDK for Windows 圆4. Go to this link and download the Android SDK and install it. This procedure illustrates why it’s a damned good idea to encrypt your phone. This of course requires physical access to the phone. I’ve recently changed over to encryption on my smartphone, because it came to my attention that it’s possible to use the Android debugger to get access to an Android device’s flash even if you don’t have the unlock pin.

I don’t have a specific use case for this, but I thought I’d experiment and see just how this can be done.

Start adb in android studio