ADB / Fastboot Builder
Search commands, fill in parameters, copy the exact line. Destructive ops are flagged.
- Runs locally
- Works offline
- No sign-up
ADB / Fastboot builder
About this tool
Search the cheatsheet, fill in the parameters for a command, and copy the exact line to run in your terminal. Destructive commands are tagged so you know what wipes data before you run it.
Tags: info safe to run, caution changes state, destructive wipes data or can brick the device.
What are ADB & Fastboot?
ADB (Android Debug Bridge) talks to a booted Android device or its recovery, so you can install apps, copy files, read logs, and run shell commands.
Fastboot talks to the bootloader (the low-level mode before Android loads). You use it to unlock the bootloader and flash partitions like boot or recovery.
Both are part of Google's platform-tools. Enable USB debugging in Developer Options to use ADB.
Tips
- Run
adb devicesfirst. If nothing lists, fix the driver or cable before anything else. - Unlocking the bootloader (
fastboot flashing unlock) erases all data. Back up first. - Flash the correct image to the correct partition. A wrong
flashcan soft-brick your device. - Prefer
fastboot boot recovery.imgto test a recovery before permanently flashing it. - Quote file paths that contain spaces.
About the ADB & Fastboot Builder
ADB and Fastboot are the two command-line tools you reach for whenever you work on an Android device, but their syntax is easy to get wrong, and a wrong flash can soft-brick a phone. This builder gives you a searchable catalog of 40+ common commands, lets you fill in the parameters through simple form fields, and renders the exact command to copy into your terminal. Anything that wipes data or can brick a device is clearly tagged.
ADB vs Fastboot
ADB (Android Debug Bridge) communicates with a device that is fully booted into Android or its recovery. You use it to install apps, push and pull files, read logcat, and run shell commands.
Fastboot communicates with the bootloader, the low-level mode that runs before Android starts. You use it to unlock the bootloader and flash partitions such as boot, recovery, and vbmeta. Both ship in Google's official platform-tools package.
Getting started
- Install Google's platform-tools and add them to your PATH.
- On the phone, enable Developer Options (tap Build number seven times) and turn on USB debugging.
- Run
adb devicesand your device should appear. If not, fix the driver or cable first. - For Fastboot commands, reboot to the bootloader with
adb reboot bootloader.
Frequently asked questions
What's the difference between ADB and Fastboot?
ADB controls a booted device or recovery; Fastboot controls the bootloader before Android loads. You flash partitions with Fastboot and manage apps/files/logs with ADB.
Why doesn't my device show in adb devices?
Usually a driver or cable issue, or USB debugging is off. Check the cable supports data, accept the "Allow USB debugging" prompt on the phone, and reinstall the platform-tools/driver.
Is unlocking the bootloader safe?
It is reversible but erases all data and voids the warranty on most phones. Some carriers disable OEM unlocking entirely. Back up first and make sure you have the correct factory images.
Can a wrong flash brick my phone?
Yes. Flashing the wrong image to a partition can soft-brick or hard-brick your device. Always match the image to the exact partition and model, and prefer fastboot boot to test a recovery before flashing it permanently.