When a smartphone on Android stops booting or installation of custom firmware is required, users are faced with the term Boot —a key stage in launching the system. This mode, often confused with Fastboot or Recovery, is actually the initial boot stage, where the hardware is initialized before transferring control to the operating system. Without understanding the operating principles Boot it is impossible to unlock the bootloader, flash the device or fix critical failures.

In this article we will look at what it is Boot Android at a technical level, how it differs from other service modes, and how to use it correctly. You will learn what commands developers use to interact with the bootloader, what risks are associated with incorrect work with boot.img, and why on some devices (for example, Samsung or Xiaomi) the login process may be different. The material will be useful to both beginners and experienced users who want to better understand the architecture Boot may vary. The material will be useful to both beginners and experienced users who want to gain a deeper understanding of architecture Android.

What is Boot on Android: technical explanation

Term Boot (from English bootstrap —“lace”) denotes the process of device initialization, which begins immediately after turning on the power. On Androiddevices this process is divided into several stages, where Bootloader (bootloader) plays a central role. Its main tasks:

  • 🔧 Checking hardware — testing the processor, memory, controllers before loading the OS.
  • 📦 Loading the kernel — transferring control to the file boot.imgwhich contains the kernel Linux and the initial file system (initramfs).
  • 🔑 Integrity control — checking the digital signatures of the firmware (on devices with a locked bootloader).
  • 🛠️ Transition to service modes —the ability to choose Fastboot, Recovery or normal loading.

File boot.img is an archive that includes:

  • Kernel Linux (zImage or Image.gz) - the basis of the system.
  • Initramfs — temporary file system used to mount the main partition.
  • Command line parameters (cmdline) - boot settings (for example, androidboot.hardware=qcom).
  • DTB image (Device Tree Blob) - description of the hardware configuration for processors ARM.

On devices with an unlocked bootloader (for example, Google Pixel or OnePlus) the user can modify boot.img to install custom kernels or Magiskon devices. c locked bootloader (for example, Samsung or Huawei) such actions lead to the activation of protection Knox or DM-Verity, which may make the device unusable.

📊 How often do you use Boot/Fastboot modes?
Never heard of them
Only with firmware
Regularly for debugging
I don’t know what it is

Differences between Boot, Fastboot and Recovery: when to use which mode

Users often confuse Boot with other service modes. Let's look at the key differences:

Mode Purpose How to enter Limitations
Boot (Bootloader) Basic bootloader that controls system startup. Allows you to select the boot mode. Button combination (for example, Power + Vol Down) or command adb reboot bootloader. On locked devices, limits the flashing of unsigned images.
Fastboot Protocol for flashing partitions (boot, recovery, system) from a PC. From the menu Bootloader or command adb reboot fastboot. Requires unlocking the bootloader on most devices.
Recovery Recovery mode for resetting, updating or backing up. Button combination (for example, Power + Vol Up) or command adb reboot recovery. Stock Recovery is limited in functions (for example, you cannot flash custom firmware).

Critical difference: Bootloader is software software built into the device's memory chip, while Fastboot and Recovery are modes that are loaded by Bootloaderth. For example, on Xiaomi entrance to Fastboot is carried out through Bootloader, but for firmware via fastboot flash preliminary unlocking is required.

⚠️ Attention: On devices Samsung mode Download Mode (analogue Fastboot) uses a protocol Odin, which is incompatible with standard commands fastboot. An attempt to flash Samsung via fastboot will lead to an error.

How to enter Boot mode on different devices

How to enter Bootloader Depends on the manufacturer and model of the device. Below is a list of popular combinations:

  • 📱 Google Pixel, OnePlus, Motorola: Power + Vol Down (hold for 5-10 seconds).
  • 📱 Xiaomi, Redmi, POCO: Power + Vol Down (with the device turned off). To unlock, you need to link your account. device by holding Mi.
  • 📱 Samsung: Power + Vol Down + Bixby (mode Download Mode, analog Fastboot).
  • 📱 Huawei, Honor: Power + Vol Down (on some models you need to disable Fastboot in developer settings).
  • 📱 Sony Xperia: Connect the USB cable to the switched off device while holding Vol Up.

If the device is turned on, you can use the command ADB:

adb reboot bootloader

On some devices (for example, Realme or Oppo) to enter Bootloader you must first activate developer mode:

  1. Go to Settings → About phone.
  2. Click 7 times on Build number.
  3. Go back to Settings → System → For developers.
  4. Activate USB debugging and OEM unlocking (if available).

Activate developer mode|Enable USB debugging|Connect the device to PC|Install ADB/Fastboot drivers|Download official utilities (Odin, Mi Flash, etc.)

-->

⚠️ Attention: On devices with Android 10+ option OEM unlocking may disappear after a reboot. It must be enabled immediately before unlocking the bootloader.

Unlocking the bootloader: why do you need it and how to do it

Unlocking Bootloader is a mandatory step for:

  • 🔄 Installing custom firmware (LineageOS, Pixel Experience).
  • 🔧 Kernel modifications or boot.img (for example, for Magisk).
  • 📱 Restoring a device after a “brick” (if the stock firmware is damaged).

The unlocking process varies depending on the manufacturer:

Manufacturer Unlocking method Consequences
Google Pixel Command fastboot flashing unlock (requires confirmation on device). Reset to factory settings, data loss.
Xiaomi Account linking Mi + wait 7–15 days (on some models). Function blocking Mi Pay and Find Device.
Samsung Unlocking via OEM Unlock in the settings + use Odin. Triggering Knox (loss of warranty, restrictions Samsung Pay).
Huawei Obtaining an unlock code through the official website (impossible on new models). Loss of access to services HMS on some firmware.

Unlocking example on Google Pixel:

  1. Log in Bootloader (Power + Vol Down).
  2. Connect the device to the PC and do: 
    fastboot flashing unlock
  3. Confirm unlocking on the device screen (volume buttons to select Power to confirm).
  4. After rebooting, the device will be reset.
💡

If after unlocking the bootloader the device does not boot, try flashing the stock one boot.img via fastboot flash boot boot.img. This often solves the problem with the boot loop.

Firmware via Boot: step-by-step guide

Firmware via Bootloader (in Fastbootmode) is a standard method of installing or restoring software. Let's look at the process using firmware as an example boot.img:

  1. Preparing files:
    • Download the official firmware for your model (for example, from the website Xiaomi or Google).
    • Extract boot.img from the archive (usually it is located in the folder images).
  • Go to Fastboot: 
    adb reboot bootloader
  • Connection check: 
    fastboot devices

    (the serial number of the device should be displayed).

  • Firmware: 
    fastboot flash boot boot.img
  • Reboot: 
    fastboot reboot

    • For full firmware (for example, on Xiaomi), use the script flash_all.bat (Windows) or flash_all.sh (Linux/Mac) Example command for flashing all partitions:

    fastboot flashall -w
    ⚠️ Attention: Flag -w erases user data. Without it, the firmware can lead to errors in the system.
    What to do if the firmware is interrupted?

    If the firmware process was interrupted (for example, due to USB disconnection), the device may stop booting. case:

    1. Repeat the firmware from the very beginning.

    2. If the device is not detected in fastboot, try using EDL Mode (for Qualcomm-chips) or Download Mode (for Samsung).

    3. On some devices (for example, Xiaomi) account authorization is required to unlock after unsuccessful firmware.

    Typical errors when working with Boot and how to avoid them

    Errors during operation c Bootloader can lead to “brick” (inoperability) of the device. Let's consider the most common problems and their solutions:

    • 🚫 FAILED (remote: 'Flashing is not allowed in Lock State')

      Cause: The bootloader is locked. Solution: Unlock it (see section above).

    • 🚫 No such file or directory

      Cause: The firmware file was not found or the wrong path was specified. Solution: Check the file path or use the full path (for example, fastboot flash boot C:/boot.img).

    • 🚫 The device is not detected in fastboot

      Reason:

      • Not installed drivers ADB/Fastboot.
      • A non-original USB cable is used.
      • On devices MediaTek activation is required BROM Mode.
      Solution: Install the drivers manually via Device Manager (for Windows) or use the original cable.

    • 🚫 Cyclic reboot after firmware

      Reason: Incompatibility boot.img with the kernel version or modules. Solution: Flash the full stock image or check the compatibility of the custom kernel.

    If the device stops turning on after manipulating with Bootloader, try the following steps:

    1. Boot into Fastboot and flash the stock one boot.img.
    2. If Fastboot is not available, use EDL Mode (for Qualcomm) or Download Mode (for Samsung).
    3. On devices Xiaomi with locked The bootloader may require authorization via Mi Account.
    💡

    Always check the compatibility of the firmware with the device model. Installing boot.img from another model or version of Android will lead to system inoperability.

    Boot and security: risks of modifying the bootloader

    Operation s Bootloader is associated with risks that go beyond the normal use of a smartphone:

    • 🔒 Loss of warranty: Unlocking the bootloader on most devices will void the manufacturer's warranty.
    • 🛡️ Triggering of protections:
      • Samsung Knox —blocks Samsung Pay, Secure Folder and encryption.
      • DM-Verity —prevents loading the modified system.
      • Rollback Protection (on Pixel)—blocks rollback to the old version of Android.
    • 🕵️ Vulnerabilities: Unofficial firmware may contain backdoors or vulnerabilities (for example, in 2022, some custom kernels were discovered vulnerability Dirty Pipe).
    • 📵 Loss of functionality: On some devices, after unlocking, they stop working:
      • Banking applications (SBI, Tinkoff - due to lack of SafetyNet).
      • Functions Widevine L1 (downgrade to L3, deterioration in streaming quality in Netflix).
      • Official over-the-air (OTA) updates.

    To minimize risks:

    • Use only trusted sources of firmware (for example, XDA Developers, official manufacturer forums).
    • Before unlocking, create a backup copy of the partition persist (responsible for IMEI and sensor calibration).
    • For bypass SafetyNet use Magisk with the module Universal SafetyNet Fix.
    ⚠️ Attention: On devices with chips Exynos (for example, Samsung Galaxy S22) modification boot.img may lead to hardware damage memory controller. This cannot be fixed by software!

    FAQ: Frequently asked questions about Boot mode on Android

    Is it possible to enter Bootloader without buttons (for example, if Volume Down is broken)?

    Yes, if on the device USB debugging is enabled, you can use the command:

    adb reboot bootloader

    If debugging is not enabled and the buttons do not work, you will need to disassemble the device to close the contacts on the board (for example, test points to enter EDL Mode).

    What is boot.img and can it be modified?

    boot.img — this is a boot image containing the kernel Linux and the initial file system. It can be modified for:

    • Installation Magisk (root access without changing the partition system).
    • Replacing the kernel with a custom one (for example, FrancoKernel).
    • Disablements DM-Verity or forced encryption.

    To modify, use utilities like Magisk Manager or Android Image Kitchen.

    Why did banking applications stop working after unlocking Bootloader?

    Banking applications are checked status SafetyNet —mechanism for protecting against modified devices. Unlocking the bootloader triggers CTS Profile Match, which is why applications (for example, SberBank Online or Tinkoff) refuse to work.

    Solutions:

    • Install Magisk and activate modules Universal SafetyNet Fix + MagiskHide Props Config.
    • Use alternative versions of applications (for example, SberBank Online for Huawei without GMS).
    • Return the stock one boot.img and block the bootloader (but this will remove root access).
    How return stock Bootloader if the device does not boot?

    If the device is “bricked” after modifications, you can restore it in the following ways:

    1. Via Fastboot: Flash stock images boot.img, recovery.img and system.img from the official firmware.
    2. Via EDL Mode (for Qualcomm): Use utilities QFil or MiFlash for flashing the full image (rawprogram.xml).
    3. Through Download Mode (for Samsung): Flash the stock firmware via Odin with a checkmark BL (BootLoader).

    If the device is not detected in any mode, you will need soldering equipment to restore via test points.

    Is it possible to flash Boot on devices with Exynos or MediaTek?

    Yes, but the process differs:

    • Exynos (Samsung, some Meizu): Use Odin to flash the BLfile (BootLoader). Modification boot.img may cause damage eMMC!
    • MediaTek (Redmi Note, Realme, Tecno): Firmware is carried out via SP Flash Tool in Download Agentmode. An authorization file (auth.svg) for new chips is required.

    On devices MediaTek s Secure Boot (for example Helio G90) unsigned firmware boot.img will lead to an error SLA Auth Fail.