sodcalculator

10 Tech How-To

Install Android SDK & ADB on Windows: 3 Ways

Guide 10-29408 · Updated · Step by step

This guide shows you three different ways to install the Android SDK and ADB (Android Debug Bridge) on Windows. ADB is a command-line tool that lets you communicate with an Android device, install apps, run shell commands, and more. The Android SDK includes ADB plus other essential tools like Fastboot. By the end, you’ll have a working setup whether you prefer a full IDE, a standalone command-line package, or a lightweight minimal installer.

What You’ll Need

  • A Windows PC (Windows 10 or 11 recommended) with at least 500 MB of free disk space.
  • An internet connection to download the necessary files.
  • Java JDK (for Method 1 only, if you plan to use Android Studio).
  • Basic familiarity with using the Windows Command Prompt or PowerShell.
  • USB debugging enabled on your Android phone (if you want to connect a real device).

Step-by-Step

Method 1: Using Android Studio (Easiest for Beginners)

  1. Go to the official Android Studio download page and download the latest stable version for Windows.
  2. Run the downloaded .exe file and follow the installation wizard. Keep the default settings unless you have a preference for the installation location.
  3. Once installed, launch Android Studio. The first time it opens, it will ask if you want to import settings; choose “Do not import settings” and click OK.
  4. The Setup Wizard will appear. Click “Next” through the steps, and it will automatically install the Android SDK. Make sure the “Android SDK” component is checked.
  5. After the SDK is installed, you need to add the platform-tools to your PATH so you can use ADB from any command prompt. Open the SDK Manager (click the SDK Manager icon in the toolbar, or go to File > Settings > Appearance & Behavior > System Settings > Android SDK).
  6. Note the “Android SDK location” path (e.g., C:\Users\YourName\AppData\Local\Android\Sdk).
  7. Open the Start menu, search for “Edit the system environment variables”, and open it.
  8. Click “Environment Variables…”. Under “User variables”, select “Path” and click “Edit…”.
  9. Click “New” and add the path to the platform-tools folder: %LOCALAPPDATA%\Android\Sdk\platform-tools (or the full path you noted earlier).
  10. Click OK on all dialogs. Open a new Command Prompt and type adb version to verify ADB is accessible.

Method 2: Standalone Command-Line Tools (Lightweight)

  1. Visit the Android Studio download page and scroll down to the “Command line tools only” section.
  2. Download the Windows ZIP file (e.g., commandlinetools-win-11076708_latest.zip).
  3. Extract the ZIP to a folder like C:\Android\cmdline-tools. The extraction should create a folder named cmdline-tools inside it.
  4. Rename that inner folder to latest so the path becomes C:\Android\cmdline-tools\latest. This is required for the sdkmanager to work correctly.
  5. Open a Command Prompt in that directory (Shift+Right-click > “Open command window here” or type cmd in the address bar and press Enter).
  6. Run the following command to install the platform-tools (which includes ADB) and the basic SDK tools:
    sdkmanager "platform-tools" "platforms;android-33"

    (Replace android-33 with a newer API level if desired.)

  7. Accept the licenses when prompted by typing y and pressing Enter.
  8. After installation, the platform-tools folder will be at C:\Android\platform-tools. Add this to your PATH using the same steps as in Method 1 (steps 7-10).
  9. Verify by opening a new Command Prompt and typing adb version.

Method 3: Minimal ADB & Fastboot Installer (Quickest)

  1. Search online for “Minimal ADB and Fastboot” by a reputable developer (e.g., from XDA Developers). Download the installer from a trusted source.
  2. Run the downloaded .exe file. The installer is very small (around 1-2 MB).
  3. Follow the installation wizard. It will ask for an installation directory; the default is usually C:\Program Files (x86)\Minimal ADB and Fastboot.
  4. During installation, you may be asked if you want to add ADB to your PATH. Choose “Yes” if you want to use it from any command prompt.
  5. If you didn’t add to PATH, you can still use ADB by opening the installation folder and running adb.exe from there.
  6. To test, open Command Prompt and type adb version. If it says “command not found”, navigate to the installation folder and try again.

Common Mistakes

  • Not adding platform-tools to PATH: This is the most common issue. Without it, Windows won’t recognize the adb command.
  • Using the wrong folder structure for cmdline-tools: The sdkmanager will fail if the inner folder isn’t named latest.
  • Forgetting to enable USB debugging on your phone: ADB won’t detect your device otherwise. Go to Settings > About Phone > Tap “Build Number” 7 times, then enable Developer Options and USB Debugging.
  • Installing outdated or unofficial ADB versions: Always download from the official Android developer site or a well-known source.

Tips

  • After installing, run adb devices to see if your phone is connected. If it shows “unauthorized”, check your phone and accept the RSA fingerprint prompt.
  • Use adb help to see all available commands. Common ones include adb install app.apk, adb shell, and adb logcat.
  • If you use Android Studio often, you don’t need to manually add platform-tools to PATH; Studio uses its own bundled SDK.
  • Keep your SDK up to date by running sdkmanager --update from the cmdline-tools folder.

Troubleshooting

  • “adb is not recognized as an internal or external command”: This means the PATH isn’t set correctly. Double-check the path to platform-tools and ensure you opened a new Command Prompt after changing environment variables.
  • “sdkmanager” not found: Make sure you are running the command from the cmdline-tools\latest\bin directory, or that this directory is added to PATH.
  • Device not showing in adb devices: Ensure USB debugging is enabled, try a different USB port, and install the correct USB driver for your phone (usually from the manufacturer’s website).
  • Installation fails with “SDK location not found”: In Android Studio, go to File > Project Structure > SDK Location and set the correct path.
  • Java errors during Android Studio setup: Install the latest JDK (Java Development Kit) from Oracle or OpenJDK, and set the JAVA_HOME environment variable.

Frequently Asked Questions

  1. Do I need Android Studio to use ADB? No. You can install only the command-line tools (Method 2) or use a minimal installer (Method 3).
  2. What is the difference between ADB and Fastboot? ADB is used when the device is booted into Android; Fastboot is used when the device is in bootloader mode. Both are included in platform-tools.
  3. How do I uninstall ADB? Simply delete the platform-tools folder and remove the PATH entry. For Android Studio, use the Windows “Add or Remove Programs” feature.
  4. Can I use ADB over Wi-Fi? Yes, but you need to connect via USB first and run adb tcpip 5555, then adb connect <device-ip>:5555. This is not recommended for beginners.
  5. Why does my phone show “unauthorized”? You need to accept the RSA key fingerprint on your phone when prompted. If you missed it, disconnect and reconnect the USB cable.
  6. Is ADB safe to use? Yes, but be careful with commands like adb shell rm or adb reboot bootloader as they can affect your device. Stick to basic commands until you’re comfortable.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →