Introduction: The Journey Back to Stock

Returning your Android device from a custom ROM, like LineageOS, back to its original factory firmware can be a straightforward process, but it harbors critical risks, especially when it comes to relocking the bootloader. A custom ROM provides unparalleled flexibility and features, but there are many reasons to revert to stock: warranty claims, selling the device, receiving official OTA updates, or simply preferring the OEM experience. This guide will walk you through the precise steps to ensure a clean return to stock, emphasizing the critical precautions necessary before attempting to relock your device’s bootloader, a step that, if done improperly, can lead to a permanent brick.

Understanding the Perils of Bootloader Relocking

The Anti-Rollback Protection Mechanism

Modern Android devices incorporate anti-rollback protection, a security feature designed to prevent downgrading to older, potentially vulnerable firmware versions. This mechanism is crucial for device security but can be a significant hurdle when flashing stock ROMs. Each firmware component (bootloader, modem, system) has a version number. If you flash an older bootloader or modem version than what the anti-rollback fuses expect, your device might refuse to boot, displaying a “corrupt device” message, or worse, become permanently inoperable.

Mismatching Firmware Components

The primary danger arises from flashing incorrect or mismatched firmware components. When relocking the bootloader, the device’s security checks rigorously verify that all currently installed partitions (bootloader, radio, system, vendor, etc.) are official, un-tampered, and match the expected versions for the specific stock firmware being locked to. If there’s any discrepancy – a custom recovery, an outdated bootloader, or a modified kernel – the relock process will fail, often resulting in a hard brick. Always ensure you are flashing a complete, official factory image package appropriate for your device’s specific model and region.

Pre-Requisites and Preparations

• Full Data Backup: Before starting, back up all essential data. This process will wipe your device entirely.
• Identify Your Device Model: Precisely know your device’s model number (e.g., Pixel 7a, OnePlus 10 Pro) and region. This is crucial for downloading the correct firmware.
• Download Official Factory Images: Obtain the factory firmware package directly from your OEM’s official website. For Google Pixel devices, this is usually from the Google Developers site. Avoid third-party sources unless absolutely verified, as they may contain modified or outdated files.
• Install ADB and Fastboot Tools: Ensure you have the latest Android SDK Platform-Tools installed on your computer and added to your system’s PATH.
• Charge Your Device: Your device should be charged to at least 80% to prevent unexpected shutdowns during the flashing process.
• Disable Screen Lock & Find My Device: For some OEMs, removing all screen locks and disabling factory reset protection (FRP) by removing your Google account is a prerequisite.

Step-by-Step Guide to a Clean Return to Stock

Step 1: Download and Extract Official Factory Images

Navigate to your OEM’s factory image page. For Google Pixel devices, visit Google’s Factory Images for Nexus and Pixel Devices. Download the correct factory image for your device model and the desired Android version. Once downloaded, extract the contents of the ZIP archive into your ADB and Fastboot directory.

Step 2: Boot Your Device into Fastboot Mode

Connect your device to your computer via a high-quality USB cable. Open a command prompt or terminal in the directory where you extracted the factory images. To enter Fastboot mode:

adb reboot bootloader

Alternatively, power off your device completely and then hold specific button combinations (e.g., Volume Down + Power button for many devices) to enter Fastboot mode.

Step 3: Verify Device Connection

Once in Fastboot mode, verify that your computer recognizes your device:

fastboot devices

You should see your device’s serial number listed. If not, check your drivers and cable connection.

Step 4: Flash the Stock Firmware

Most factory image packages come with a script to automate the flashing process:

• For Windows: Double-click the flash-all.bat script.
• For Linux/macOS: Open a terminal in the extracted folder and run:

./flash-all.sh

This script will automatically flash all necessary partitions (bootloader, radio, system, vendor, etc.) and perform a factory reset. It’s crucial to let this process complete without interruption. If the script encounters an error or you prefer manual control, you can flash individual components:

fastboot flash bootloader <bootloader_filename>.imgfastboot reboot bootloaderfastboot flash radio <radio_filename>.imgfastboot reboot bootloaderfastboot update <image_filename>.zip

Replace placeholders with actual filenames from your extracted package. The update command handles the main system partitions (system, vendor, product, etc.).

Step 5: Wipe Userdata for a Pristine State

After flashing, it’s highly recommended to perform a clean wipe of the userdata partition to ensure no remnants of the custom ROM remain. The flash-all script usually does this, but for extra assurance or if flashing manually:

fastboot -w

This command wipes the userdata and cache partitions. This is crucial for a clean relock.

Step 6: Relocking the Bootloader (Proceed with Extreme Caution)

This is the most critical step. DO NOT proceed unless you are absolutely certain that the device is running a complete, official, and matching stock firmware. Attempting to relock with mismatched or unofficial software WILL BRICK your device.

Ensure your device is still in Fastboot mode. Execute the following command:

fastboot flashing lock

On older devices or some OEMs, the command might be:

fastboot oem lock

Your device’s screen will display a warning about relocking the bootloader and erasing data (which you’ve already done). Use the volume keys to navigate to the