sodcalculator

10 Tech How-To

Install ADB on Chrome OS 67 Without Crouton

Guide 10-14970 · Updated · Step by step

This guide shows you how to install ADB (Android Debug Bridge) on a Chromebook running Chrome OS 67 or later, without using Crouton or Linux. You’ll enable Developer Mode, use the built-in Crostini (Linux) container, and install ADB from the command line. This gives you a working ADB tool for debugging Android apps, flashing devices, or managing your Chromebook’s Android container.

What You’ll Need

  • A Chromebook running Chrome OS 67 or newer (check in Settings > About Chrome OS).
  • At least 1 GB of free storage space.
  • An internet connection to download the Linux container and ADB package.
  • Basic comfort with the command line (you’ll type a few commands).

Step-by-Step

  1. Enable Developer Mode (if not already on). This wipes your local data, so back up anything important. Power off, then press and hold Esc + Refresh and tap the Power button. When the recovery screen appears, press Ctrl + D, then Enter to confirm. Wait for the device to reboot and show the “OS verification is OFF� screen. Press Ctrl + D each boot to skip the warning.
  2. Enable Linux (Crostini). Go to Settings > Linux (Beta) > Turn on. Follow the prompts to set up a Linux username and allocate disk space (default is fine). Wait for the terminal to open—this means the container is ready.
  3. Open the Linux terminal. Click the Terminal app in your app drawer. You’ll see a prompt like username@penguin:~$.
  4. Update the package list. Type sudo apt update and press Enter. Enter your Linux password when prompted. This refreshes the list of available software.
  5. Install ADB. Type sudo apt install adb -y and press Enter. The -y auto-confirms the installation. Wait for the download and install to finish (a few minutes).
  6. Verify ADB is installed. Type adb version and press Enter. You should see output like Android Debug Bridge version 1.0.41. If you see this, ADB is ready to use.
  7. Connect your Android device (optional). On your Android phone/tablet, enable Developer options and USB debugging (usually under Settings > About > Tap build number 7 times). Plug the device into your Chromebook. In the terminal, type adb devices. Authorize the RSA key prompt on your device, then run adb devices again—your device should appear as “device.�

Common Mistakes

  • Skipping Developer Mode: Crostini requires Developer Mode on many Chromebooks. If you skip this, Linux won’t work. Check by going to Settings > About Chrome OS > Additional details—if you see “Developer mode� under “Channel,� you’re good.
  • Not updating apt: If you skip sudo apt update, the install may fail with “Unable to locate package adb.� Always run it first.
  • Wrong password: The Linux password you set is separate from your Google account. If you forget it, you’ll need to reset the Linux container (Settings > Linux > Remove).
  • USB debugging not enabled: If adb devices shows nothing, check that your device’s USB debugging is on and that you’ve approved the RSA key prompt.

Tips

  • Use adb from any directory: The installation puts ADB in your PATH, so you can type adb anywhere in the terminal.
  • Update ADB regularly: Run sudo apt update && sudo apt upgrade adb to get the latest version.
  • For wireless debugging: Use adb connect : after enabling wireless debugging on your device (Android 11+).
  • Keep a backup: Developer Mode wipes your Chromebook’s local data. Use Google Drive or external storage for important files.
  • Use adb shell for a full command-line interface: Once connected, type adb shell to get a shell on your Android device.

Troubleshooting

  • “Linux is not available on this device� – Your Chromebook may not support Crostini. Check if your device is on the official list (search “Chrome OS devices supporting Linux�). If not, you’ll need to use Crouton or a different method.
  • “adb: command not found� – The install didn’t complete. Run sudo apt install adb again and watch for errors. If it says “Unable to locate package,� run sudo apt update first.
  • “No devices found� in adb devices – Try a different USB cable, enable USB debugging again, and check your device’s lock screen for an authorization prompt. Also, ensure the device is connected directly to the Chromebook, not a hub.
  • Developer Mode boot loop – If the Chromebook gets stuck on the “OS verification is OFF� screen, press Ctrl + D each time. If it still loops, do a hard reset by holding Refresh + Power for 10 seconds.
  • ADB works but slow – Try using a USB 3.0 port (blue interior) and a high-quality cable. Also, close other apps on the Chromebook to free resources.

Frequently Asked Questions

Do I need Developer Mode for ADB?

Yes, on most Chromebooks, enabling Linux (Crostini) requires Developer Mode. However, some newer models support Linux without Developer Mode (check your device’s settings). If you don’t want Developer Mode, you can try using the Android Debug Bridge from the Chrome browser via WebUSB, but that’s limited.

Will this wipe my Chromebook?

Enabling Developer Mode wipes your local data (downloads, settings, etc.). Cloud data (Google Drive, Gmail) is unaffected. Back up anything important before starting.

Can I use ADB to root my Android phone?

ADB alone doesn’t root a device. It’s a debugging tool. Rooting requires additional exploits and is not covered here. Use ADB for legitimate development and debugging.

How do I uninstall ADB?

If you no longer need it, remove the Linux container entirely (Settings > Linux > Remove) or just uninstall ADB with sudo apt remove adb.

Does ADB work with any Android device?

ADB works with any Android device that has USB debugging enabled. Some manufacturers require specific drivers on Windows, but on Chrome OS, it’s usually plug-and-play.

Can I use ADB wirelessly?

Yes, on Android 11+ you can enable wireless debugging and use adb connect :. For older versions, you can use adb tcpip 5555 after a USB connection.

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 →