How to Use ADB and Fastboot on a Tablet

What are ADB and Fastboot?

ADB, short for Android Debug Bridge, is the Swiss Army knife for Android power users. It is a client-server program that lets your computer send commands to your tablet over a USB cable or Wi-Fi. With ADB you can install APK files, copy files in and out, run Linux shell commands, capture screenshots, and even record video of the screen without touching the tablet. It is included in Google's official Platform Tools, which are free to download.

Fastboot is a separate protocol that runs when the tablet is in bootloader mode, before Android boots. It is the tool you use to flash partitions, unlock the bootloader, or install a factory image. Fastboot is more powerful than ADB, but because of that it carries more risk: the wrong command can brick your device. Not every tablet supports Fastboot; some budget models disable it. Check your tablet's documentation before relying on it.

Both tools are part of the same platform-tools package, so you install them together. They are command-line utilities, which means you type text commands rather than clicking a graphical interface. If you are new to the terminal, do not worry: the commands you need for everyday tasks are few and easy to memorize. To get the most out of ADB, you will want a tablet that supports a wide range of commands; see our guide to the best Android tablets for models that are developer-friendly.

• ADB: runs while Android is on; used for app install, file copy, shell, backups, and log reading.
• Fastboot: runs in bootloader mode; used for flashing system images, unlocking bootloader, and recovery.
• Platform Tools: the official package containing both binaries, updated regularly by Google.

Setting Up ADB on Your Computer

Download the platform-tools package from Google's Android developer site. It is a small zip file that contains adb, fastboot, and related DLLs. Extract it to a folder you can remember, for example C:\adb on Windows or ~/platform-tools on macOS or Linux. There is no installer; you run the tools directly from that folder. On Windows, you may want to add that folder to your PATH so you can run adb from any directory. That is a one-time environment variable change.

On macOS and Linux, the platform-tools work out of the box once you extract them. On Windows, you might need to install the Google USB driver or your tablet maker's driver, which we cover in the next section. If you plan to use ADB wirelessly, you also need ADB over Wi-Fi, a feature built into Android 11 and later. It removes the cable requirement, but for first-time setup a USB cable is more reliable.

Before you connect, make sure your tablet's screen is unlocked and the cable is a data cable, not a charge-only one. Some budget cables carry power but no data, so if ADB cannot see the device, try another cable. You should also check the USB mode on your tablet; some models ask you to choose 'File Transfer' or 'Charge only' when plugged in. For ADB, the tablet should be in a mode that allows data. If you are unsure which tablet to buy for this level of control, our guide to 10 to 11.9 inch tablets highlights models with broad support.

• Download platform-tools from the Android developer site.
• Extract to a simple path without spaces, like C:\adb.
• Open a terminal or command prompt in that folder.
• Plug the tablet in, enable USB debugging, and check 'adb devices'.
• Authorize the RSA key fingerprint on the tablet screen.

Installing Drivers on Windows

Windows often does not recognize Android devices without a proper USB driver. The first sign is a message in Device Manager saying 'Unknown Device' or 'ADB Interface' with a yellow warning. To fix this, you need the USB driver for your specific tablet brand. Samsung, Lenovo, Xiaomi, and other makers publish OEM USB drivers, usually under their support or developer pages. Install that driver before connecting the tablet for the first time.

For most modern Android tablets, the generic Google USB Driver works, but it only supports Nexus and Pixel devices, so for brand-name tablets, use the OEM driver. For step-by-step driver installation on Windows, see our guide to installing tablet drivers on Windows. It covers Device Manager and driver updates.

If you still see an unknown device, try a different USB port. USB 2.0 ports work fine for ADB; USB 3.0 ports can sometimes cause issues. You should also disable USB power saving for the port. In Device Manager, right-click the USB root hub, go to Power Management, and uncheck 'Allow the computer to turn off this device to save power'.

Note that the USB-IF, the standards body behind USB, defines power and data specifications. A cable that is not compliant with USB standards may cause data transfer problems. Under the USB Power Delivery specification, a full-featured USB Type-C cable can carry both power and data, but a cheap charge-only cable lacks the data pins. If in doubt, use the cable that came with your tablet; it is usually compliant.

Enabling USB Debugging on Your Tablet

USB debugging is part of the Android Developer Options, which are hidden by default. To reveal them, open Settings, tap 'About tablet', and tap the 'Build number' seven times. You will see a toast message like 'You are now a developer!' Then go back to Settings, enter 'Developer options', and toggle 'USB debugging' on. Some tablets also require you to enable 'Install via USB' to allow ADB installs.

When you connect the tablet to your computer, a dialog appears on the tablet asking you to allow USB debugging. The dialog shows the computer's RSA key fingerprint. Tick 'Always allow from this computer' to avoid this prompt in the future, and tap OK. If you dismiss it by accident, unplug and replug the cable.

On Samsung tablets, you may also need to 'Allow ADB debugging in charge only mode', which appears once you enable USB debugging. This setting lets ADB work even when the tablet is locked to charge. For other brands, check the developer options for similar entries.

After you enable debugging, run `adb devices` on your computer. If the output says 'the product is unauthorized', unlock the tablet and accept the prompt. A second run should show the serial number and 'device' status. If you want to start fresh with your tablet before going deep into ADB, consider a factory reset to avoid interference from previous settings.

Running Common ADB Commands

Once ADB is connected, you can do a lot without rooting. The table below lists some useful commands. You can pull backups of installed apps, push files to the tablet, take screenshots, record video, and even change settings, all from the command line.

Use `adb help` to see all available options. You can also use `adb -s SERIAL` to target a specific device when multiple are connected. For wireless connections, use `adb pair` and `adb connect`.

Note that some commands require the tablet to be unplugged or rebooted. For example, `adb reboot bootloader` reboots the tablet into the bootloader for Fastboot. Other commands are harmless; do not fear the terminal. For a full walkthrough of backing up and restoring your data, see our backup and restore guide which pairs well with ADB's backup features.

Using Fastboot

Fastboot is the mode you enter when the bootloader is unlocked. To get there, run `adb reboot bootloader`, or turn off the tablet and hold a key combination (Volume Down and Power on many models). In bootloader mode, the screen shows a menu. Use the volume keys to navigate, and confirm with the power key or just run `fastboot devices` from your computer.

To see if your tablet supports Fastboot, run `fastboot devices`. If it returns a serial number, you are good. If it returns nothing, the tablet might not support the fastboot protocol, or the drivers are wrong. Some brands use proprietary bootloader modes; check your tablet maker's docs.

Common Fastboot commands include `fastboot reboot` to exit bootloader, `fastboot flash recovery recovery.img` to install a custom recovery, and `fastboot oem unlock` to unlock the bootloader (on devices that allow it). Unlocking erases your data, so back up first.

Be careful with `fastboot erase` and `fastboot format`. These erase partitions and can render a device unbootable if you wipe the wrong one. Only flash images that are made for your exact tablet model. A wrong image can brick the device, and not all bricked devices can be recovered. If you get stuck in a boot loop or firmware issue, refer to our recovery mode troubleshooting and OS reinstall guide for help.

Troubleshooting Common Issues

If `adb devices` shows no device, check these in order: is USB debugging enabled? Is the cable data-capable? Is the driver installed? On Windows, open Device Manager and look for 'Android Composite ADB Interface'. If you see a yellow exclamation, the driver is wrong. Uninstall and reinstall the OEM driver.

If the device shows as 'offline' in `adb devices`, you usually need to revoke USB debugging authorizations on the tablet and reconnect. Go to Developer options, tap 'Revoke USB debugging authorizations', and replug the cable.

If `adb` reaches the device but commands hang, try restarting the ADB server: run `adb kill-server`, then `adb start-server`. On some networks, a firewall can block the ADB ports 5037 and 5555. Allow them in your firewall if you use wireless ADB.

For Fastboot, if `fastboot devices` is empty, the tablet may not be in the correct mode. On certain Samsung tablets, download mode replaces fastboot, and you need a different tool called Odin. Check your tablet's model-specific guides. For a broad look at tablets that are known to respond well to ADB and Fastboot, review our roundup of the best Android tablets.

• Check USB debugging is on and the screen is unlocked.
• Try a different USB port and cable.
• Install or reinstall the OEM USB driver.
• Revoke USB authorizations and reconnect.
• Run `adb kill-server` and `adb start-server`.

What to pick for your use

Questions

Is ADB safe to use on my tablet?

ADB commands that only read or copy data are safe. Commands that write to system partitions carry risk. Always back up before using Fastboot or any command that modifies the system.

Do I need root to use ADB?

No. ADB works on stock Android without root. Fastboot also works without root, though some bootloaders are locked by the manufacturer.

What if my tablet is not detected by ADB?

Check the USB cable, enable USB debugging, install the correct USB driver, and accept the RSA prompt on the tablet. If it still fails, restart the ADB server or try a different port. For step-by-step driver fixes, see our Windows driver guide.

Can I use ADB over Wi-Fi?

Yes, Android 11 and later include wireless debugging in Developer options. You pair with a code and then connect. It is convenient once the initial USB setup is done.

Is Fastboot the same on every Android tablet?

No. Some manufacturers disable fastboot or replace it with a proprietary mode such as Samsung's Odin download mode. Refer to your tablet's official documentation.

Can ADB commands fix a boot loop?

If the tablet boots to fastboot or recovery, you may be able to flash a working image or wipe data. If it does not, check our boot loop fix guide.

Do I need to install drivers on macOS or Linux?

Mostly no. The platform-tools include the necessary protocols. Linux often requires udev rules for certain media devices, but for ADB it usually works out of the box.