Install TWRP Custom Recovery on Android Using Fastboot (No Root)

Flashing a custom recovery such as TWRP gives you full control over backups, OTA management, and rooting. The process can look intimidating, but with a clear workflow you can do it safely using only Fastboot – no root, no third‑party flashing apps.

Before you start

• Backup your data. Flashing a recovery rarely wipes user data, but a failed flash can leave the device unbootable. Use adb backup or your preferred backup method.
• Charge the device to at least 60 % and keep it connected to power during the whole process.
• Install USB drivers for your phone on the PC (Windows) or ensure adb works on macOS/Linux.
• Download the correct TWRP image (.img) for your exact device model from the official TWRP site. Using the wrong image can brick the device.
• Enable Developer options and USB debugging on the phone:

1. Open Settings → About phone.
2. Tap Build number seven times until you see “You are now a developer”.
3. Return to Settings → System → Developer options.
4. Toggle USB debugging ON.

Some OEMs (e.g., Samsung, OnePlus) also require you to enable OEM unlocking in the same menu. This permission allows the bootloader to accept unsigned images.

Step 1 – Install the Android Platform Tools

If you already have adb and fastboot in your PATH you can skip this step. Otherwise:

1. Download the Android Platform‑Tools zip for your OS.
2. Extract the zip to a convenient folder (e.g., C:\platform-tools on Windows).
3. Add that folder to your system PATH so you can run adb and fastboot from any terminal.

Step 2 – Unlock the bootloader (if required)

Most devices ship with a locked bootloader, which prevents flashing unsigned images. Unlocking varies by manufacturer:

• Pixel / Nexus: Fastboot command fastboot flashing unlock (will wipe data).
• OnePlus: fastboot oem unlock (may require a code from the OnePlus website).
• Samsung: Uses Odin, not Fastboot; this tutorial does not cover Samsung devices.

If your device already has an unlocked bootloader, skip this sub‑step. Warning: Unlocking erases all user data on most phones.

Step 3 – Reboot into Fastboot mode

1. Connect the phone to the PC via a USB‑C cable.
2. Open a terminal (Command Prompt, PowerShell, or Terminal) and verify the connection:

   adb devices

   You should see a device ID with the word device.
3. Enter fastboot mode:

   adb reboot bootloader

   The screen will go black and show a fastboot prompt (often a simple text screen).
4. Confirm fastboot sees the device:

   fastboot devices

   You should see the same device ID.

Step 4 – Flash the TWRP image

If the device reboots into Android instead of TWRP, repeat the flash command and ensure you boot directly into recovery (see next step).

Step 5 – Verify TWRP is installed correctly

1. Power off the device completely.
2. Use the device‑specific key combo to enter recovery (commonly Power + Volume Down or Power + Volume Up). The exact combination varies; check your phone’s manual.
3. If TWRP appears, you have succeeded. You should see a touchscreen‑enabled UI with options like Install, Backup, and Wipe.

Step 6 – (Optional) Preserve TWRP after OTA updates

Many stock OTA packages overwrite the recovery partition. To keep TWRP:

1. In TWRP, go to Advanced → File Manager → navigate to /system (or /vendor on newer devices).
2. Create a folder named twrp and place a copy of the twrp-xxxx.img there.
3. After an OTA, re‑flash the saved image using the same fastboot command.

Troubleshooting

Fastboot does not recognize the device

• Make sure USB debugging is enabled and the phone is in fastboot mode.
• Try a different USB cable or port; some cables are charge‑only.
• Install or reinstall the OEM USB drivers (Google USB Driver for Pixel, etc.).
• On Linux, you may need to add a udev rule for your vendor ID.

Flash command returns “FAILED (remote: unknown failure)”.

• Double‑check you are using the exact image for your model (e.g., mido vs lavender for Pixel 3a).
• If the bootloader is still locked, the flash will be rejected. Verify the unlock status with:

  fastboot oem device-info

• Some devices require the fastboot flashing unlock_critical command for the recovery partition.

Device boots into Android instead of TWRP after flashing

• Immediately run fastboot boot twrp-xxxx.img after flashing, before the device boots normally.
• On some OEMs, the stock ROM restores the original recovery on first boot. To avoid this, flash a recovery image and then immediately boot into recovery.

TWRP boots but shows a black screen or freezes

• Check the device’s Android version. Newer Android releases may need a newer TWRP build that includes updated drivers.
• Try flashing the “latest nightly” version from the TWRP site.

Safety considerations

• Unlocking the bootloader usually voids the manufacturer warranty.
• Flashing an incompatible recovery will brick the device, requiring a full firmware reinstall via fastboot or Odin.
• Always keep a copy of the original stock recovery image (often available on the OEM’s firmware page) in case you need to revert.

What to do after installing TWRP

Now that TWRP is functional you can explore its core features:

• Full NANDroid backups: In TWRP, tap Backup, select the partitions you want (System, Data, Boot, etc.), and swipe to start. Store the backup on an external SD card or USB OTG for safety.
• Flashing custom ROMs: Download a compatible ROM zip, transfer it to the device, then use Install in TWRP.
• Rooting: Flash Magisk zip via TWRP to gain root access without modifying the system partition.

Each of those topics deserves its own tutorial, but the key point is that a solid TWRP install gives you a reliable foundation for further modifications.

By following the steps above you have turned a stock Android device into a flexible platform ready for advanced customization, all without needing a pre‑rooted state or third‑party flashing apps.