High-Level Overview & Boot Lifecycle Stages
Both ADB and Fastboot are official Google command-line tools included in the Android SDK Platform-Tools package. However, they operate at completely different stages of the Android boot lifecycle and serve fundamentally different architectural purposes.
• **ADB** communicates with the user-space `adbd` daemon while the Android Linux kernel and Android runtime (ART) are fully booted.
• **Fastboot** communicates directly with the low-level hardware bootloader (ABL/XBL) firmware before any kernel or operating system is loaded into memory.
Architectural Comparison Matrix
• **Operating Environment**:
- ADB: Android OS (UID 2000 / shell user) or Recovery Mode (UID 0 / root).
- Fastboot: Bootloader Stage (Qualcomm PBL/SBL/XBL, MediaTek Preloader, Google Tensor BootROM).
• **Storage Level Access**:
- ADB: Filesystem level (POSIX directories, `/sdcard`, `/system`, `/data`).
- Fastboot: Raw block partition level (e.g., `/dev/block/bootdevice/by-name/boot`, `init_boot`, `vendor_boot`, `super`).
• **Security & Authentication**:
- ADB: RSA-2048 user-authorized key verification prompt.
- Fastboot: Hardware Bootloader Lock state (`oem unlock` / `flashing unlock`) verified by hardware root-of-trust fuses.
When to Use ADB vs Fastboot
• **Use ADB for**:
1. Real-time application debugging and crash logcat analysis.
2. Live screen mirroring and automated touch input injection.
3. Sideloading APKs and debloating OEM manufacturer bloatware.
4. Querying hardware fuel gauges and sysfs battery cycle counters.
• **Use Fastboot for**:
1. Unlocking the hardware bootloader to allow custom firmware.
2. Flashing custom recoveries (TWRP, OrangeFox) or patched Magisk/KernelSU `boot.img`.
3. Unbricking soft-bricked devices trapped in bootloops.
4. Restoring stock factory firmware images across A/B partition slots.
Understanding Fastbootd (Dynamic Partitions in Android 10+)
Starting in Android 10, Google introduced dynamic partitions within a single physical `super` partition. Because the hardware bootloader cannot understand dynamic sub-partitions, Google introduced **`fastbootd`** — a userspace fastboot daemon running inside Android recovery. Commands like `fastboot reboot fastboot` enter fastbootd mode to flash `system`, `vendor`, and `product` partitions.