Android SDK: how to install and launch from scratch - a step-by-step guide

Developing applications for Android begins with settings Android SDK —a set of tools, without which it is impossible to build, test or launch a project. Even if you don't plan to become a professional developer, the ability to work with an SDK will be useful for debugging applications, modifying firmware, or automating tasks on a smartphone. However, the process of installation and first launch often causes difficulties: from choosing the right version to setting up environment variables.

In this article we will analyze current ways to launch the Android SDK in 2026including installation via Android Studio and standalone command-line tools, and also look at typical errors that beginners encounter. We will pay special attention to setting up Windows 11, macOS Ventura i Ubuntu 22.04+, since the algorithms differ due to the characteristics of the operating systems. If you have already tried to launch the SDK and received an error like "Failed to install Android SDK" or "Java not found" , you will find solutions here.

What is the Android SDK and why do you need it

Android SDK (Software Development Kit) is a set of tools from Google, which includes:

• 📦 Compilers and assemblers (for example, d8 for bytecode conversion)
• 🔧 Command line utilities (adb, fastboot, sdkmanager)
• 📱 Device emulators for testing without a physical device
• 📚 Libraries and APIs for interaction with Android functions (camera, GPS, sensors)

Without SDK you will not be able to:

• ❌ Build APK file from source code
• ❌ Launch the emulator Android Virtual Device (AVD)
• ❌ Debug the application via Android Debug Bridge (ADB)
• ❌ Update the smartphone firmware via fastboot

At the same time, the SDK is not an independent application - it is a set of console utilities that are integrated into development environments (Android Studio, Visual Studio Code) or used separately through the terminal. For example, the command adb devices will show all Android devices connected to the PC, and sdkmanager --list will display packages available for installation.

⚠️ Attention: Versions of the SDK and its components are updated regularly. If you are working with outdated instructions (for example, for Android SDK Tools 25.2.5 dated 2017), some commands may not work. Always check official documentation for the latest flags and syntax.

System requirements to run the Android SDK

Before installation, check if your PC meets the minimum requirements. The table below shows current data for Android SDK Command-Line Tools 11.0+ (2026):

It is critically important to install the correct version Java. For example, Android Studio Giraffe (2022.3.1) requires OpenJDK 17, and older versions of the SDK may work with JDK 8. You can check the current version with the command:

java -version

If Java is not installed, download it from OpenJDK official website or through a package manager (for example, sudo apt install openjdk-17-jdk for Ubuntu).

Ways to install the Android SDK

There are two main ways to install the SDK:

1. Via Android Studio —an automated process with a graphical interface.
2. Standalone command-line tools — for experienced users who do not want to install a full-fledged IDE.

Let's consider both options in detail.

Method 1: Installation via Android Studio (recommended for beginners)

This is the simplest method, because it automatically downloads and configures the SDK. Follow the steps: Download the official one site Android Studio automatically downloads and configures the SDK. Follow the steps:

1. Download Android Studio With official website (choose the version for your OS).
2. Run the installer. On Windows leave all the default settings, including Android SDK and Android Virtual Device.
3. After installation, open Android Studio and wait for the initial setup to complete.
4. In the start window, select More Actions → SDK Manager.

In SDK Manager you will see three tabs:

• 📌 SDK Platforms — Android versions (for example, Android 14.0 "Upside Down Cake").
• 🔧 SDK Tools — utilities like Android Emulator or NDK.
• 📁 SDK Update Sites — sources for downloading packages.

Tick the following boxes:

• Latest version Android (for example, Android 14)
• Android SDK Command-line Tools
• Google USB Driver (only for Windows)
• Android Emulator (if you plan to test on emulator)

Click Apply, confirm the license agreements and wait for the download. Default SDK installation path:

• Windows: C:\Users\\AppData\Local\Android\Sdk
• macOS/Linux: ~/Android/Sdk

Download the latest version of Android Studio|

Check for 10+ GB of free space|

Install OpenJDK 11 or 17|

Disable antivirus (may block file downloads)-->

Method 2: Installing stand-alone command-line tools

If you do not need Android Studio, you can install only the SDK through the terminal This method is suitable for:

• 🖥️ Servers without GUI
• 🐧 Linuxsystems. minimalistic environments
• 🔧 Automated scripts (CI/CD)

Steps for Windows/macOS/Linux:

1. Download commandlinetools--_latest.zip from download pages (section "Command line tools" only").
2. Extract the archive into a folder, for example:
   • Windows: C:\Android\cmdline-tools
   • macOS/Linux: ~/Android/cmdline-tools

Now you can install the necessary packages via the terminal. For example, to install Android 14 i platform-tools:

./cmdline-tools/latest/bin/sdkmanager "platforms;android-34" "platform-tools"

⚠️ Attention: It may be necessary to first make the files executable: Linux You may need to make the files executable first:

chmod +x -R ~/Android/cmdline-tools/latest/bin/

Setting environment variables

To run SDK commands (for example, adb or fastboot) from any directory, you need to add the path to the SDK to the variable PATH. The instructions differ for each OS.

Windows 10/11

1. Open Control Panel → System → Advanced system settings → Environment variables.
2. In the section User Variables find Path and click Edit.
3. Add two paths (replace to your real path to the SDK):
   • \cmdline-tools\latest\bin
   • \platform-tools

macOS

Open the terminal and add lines to ~/.zshrc (or ~/.bashrcif you use Bash):

export ANDROID_HOME=~/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools

Apply changes:

source ~/.zshrc

Linux (Ubuntu/Debian)

Similar to macOS, but edit ~/.bashrc or ~/.profile:

export ANDROID_HOME=~/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools

Update the configuration:

source ~/.bashrc

Check the settings are correct with the command:

adb --version

If you see the version (for example, Android Debug Bridge version 1.0.41) - everything is configured correctly.

Checking the SDK and the first commands

Make sure that the SDK is working by running the basic commands:

1. Checking the version sdkmanager:

   sdkmanager --version

   Should output something like 11.0.

2. List of installed packages:

   sdkmanager --list

   Here you will see available and installed components, for example:

   Installed packages:
   Path                        | Version | Description
   ----                        | ------- | -----------
   platform-tools              | 34.0.4  | Android SDK Platform-Tools
   platforms;android-34       | 3       | Android SDK Platform 34

3. Checking connected devices:

   adb devices

   If you connect a smartphone with USB debuggingenabled, you will see its serial number.

If the commands do not work, check:

• 🔹 Correct paths in the environment variables
• 🔹 Availability of permissions to execute files (on Linux/macOS)
• 🔹 Correct installation Java

Common errors and their solutions

Even with correct installation, errors may occur. Let's consider the most common ones:

export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64

sdkmanager --uninstall emulator
sdkmanager "emulator"

If the error is not listed in the table, study the log with the command:

sdkmanager --verbose

Or look for a solution on Stack Overflow, indicating the full text of the error.

Running an Android emulator

The emulator allows you to test applications without a physical device. run:

1. Create a virtual device (AVD):

   avdmanager create avd -n Pixel_6_API_34 -k "system-images;android-34;google_apis;x86_64" -d pixel_6

   Here:

   • -n — device name
   • -k — system image (Android 14 c Google APIs)
   • -d — model (pixel_6, nexus_5 etc.)

emulator -avd Pixel_6_API_34

To speed up the emulator:

• 🖥️ On Windows enable Hyper-V (Control Panel → apps → Turn Windows components on or off).
• 🐧 On Linux install KVM:

  sudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils

• 🍎 On macOS use Hypervisor.Framework (enabled by default).

If the emulator is slow, try:

• Reduce the resolution of the emulated device
• Disable animation in the emulator settings
• Use image from x86_64 instead arm64

FAQ: Frequently asked questions about launching the Android SDK

sdkmanager --update

sdkmanager --update --channel=0

sdkmanager "platform-tools"

sdkmanager --list

sdkmanager --uninstall "platforms;android-30"