Introduction: The Journey Back to Stock Android

For many Android enthusiasts, the journey into custom ROMs, kernels, and recoveries begins with unlocking the bootloader. This gateway provides unparalleled freedom to modify and optimize your device. However, there often comes a time when reverting to a completely stock, locked bootloader state becomes necessary. Whether it’s for warranty purposes, enhancing device security, preparing to sell your phone, or ensuring seamless Over-The-Air (OTA) updates, understanding the bootloader re-lock protocol is crucial.

Re-locking your bootloader is not merely the reverse of unlocking it. It’s a precise process that requires meticulous attention to detail. Attempting to re-lock without the proper stock firmware can lead to a soft-brick, boot loops, or even a hard-brick in severe cases. This guide will walk you through the comprehensive steps, primarily focusing on fastboot-compatible devices like Google Pixel and OnePlus, while briefly touching on platform-specific considerations for others.

Why Re-lock Your Bootloader?

• Warranty Restoration: While often debated and device-dependent, a locked bootloader generally presents a device in its original factory condition, which may be a prerequisite for warranty claims.
• Enhanced Security: A locked bootloader, coupled with Verified Boot, ensures that every component of your Android operating system, from the bootloader itself to the system partition, is cryptographically verified against OEM signatures. This prevents tampering and protects against malware.
• Receiving Official OTA Updates: Custom ROMs often mean foregoing official manufacturer updates. A fully stock, locked device can receive seamless OTA updates directly from the OEM.
• Selling or Gifting Your Device: For potential buyers or recipients, a stock, locked device offers peace of mind regarding security and official support.

Risks Associated with Re-locking

The primary risk is bricking your device. If the firmware flashed does not match the OEM’s cryptographic signatures, or if critical partitions are missing or corrupted, the bootloader will refuse to boot the system, leading to a non-functional device. Data loss is also inevitable, as the re-lock process typically performs a factory reset.

Prerequisites: Preparing for the Reversion

Before you begin, ensure you have the following:

• ADB and Fastboot Tools: Latest version installed on your computer and configured in your system’s PATH.
• OEM USB Drivers: Installed for your specific device model.
• Stock Firmware Package: The exact, official factory image for your device’s model and region. This is paramount. Source it directly from the OEM’s website (e.g., Google’s factory images page) or trusted community resources like XDA Developers.
• USB-C/A Cable: A high-quality cable for a stable connection between your device and computer.
• Charged Device: Your phone should be charged to at least 80% to prevent power loss during the process.
• Complete Data Backup: All data on your device will be wiped. Back up everything important!

Understanding Verified Boot and Re-locking

Modern Android devices leverage a security feature called Verified Boot. This mechanism ensures the integrity of the software on the device, starting from the bootloader and extending through the kernel and system partitions. When you unlock your bootloader, Verified Boot is disabled, allowing custom, unsigned images to boot. When you re-lock it, the bootloader expects all loaded components to be cryptographically signed by the OEM. If any component is not signed correctly (i.e., you’re trying to re-lock with a custom ROM or a mismatched stock firmware), Verified Boot will trigger a warning or outright refuse to boot, leading to a brick or a permanent