Flashing a smartphone to Android is a process that can either bring an outdated device back to life or turn it into a โ€œbrickโ€ if done incorrectly. In 2026, when manufacturers are actively closing support for even flagship 2020-2022 models, the ability to independently update firmware becomes a critical skill. But how to do this safely, without losing data or disrupting the operation of camera modules or network chips?

This article is not just instructions, but a practical guide taking into account current trends: from unlocking the bootloader on new chips Qualcomm Snapdragon 8 Gen 3 to bypassing restrictions Google on installing unofficial firmware. We will analyze all the stages: from preparing a backup to choosing between stock ROM (official firmware), GSI (Generic System Image) and custom builds like LineageOS or Pixel Experience. We will pay special attention to the โ€œpitfallsโ€ that even experienced users are silent about - for example, why after updating the firmware it may disappear 5G or stop working NFC.

1. Why reflash Android: real reasons and myths

Many people believe that flashing is only needed to โ€œoverclockโ€ a smartphone or install the latest version Android. In fact, there are many more reasons - and not all of them are obvious:

  • ๐Ÿ”„ Restoring performance after a failure (for example, if the device is stuck on the logo or constantly reboots).
  • ๐Ÿ“ฑ Extension of support for models that the manufacturer abandoned (for example, Samsung Galaxy S20 officially not will receive Android 15, but custom firmware will fix this).
  • ๐Ÿ›ก๏ธ Removing bloodware โ€”pre-installed applications that cannot be disabled (especially relevant for Xiaomi, Realme i Oppo).
  • ๐Ÿ”’ Increasing security: some custom firmwares (for example GrapheneOS) offer better protection against surveillance than stock Android.
  • ๐ŸŽฎ Optimization for games: firmwares like DerpFest or ArrowOS can improve performance in Genshin Impact or Call of Duty Mobile.

However, there are also mythsthat are worth dispelling:

  • โŒ โ€œReflashing always speeds up smartphone" - incorrect. On weak devices (for example, Redmi 9A), heavy custom firmware can, on the contrary, slow down operation.
  • โŒ โ€œAfter the firmware, the warranty expiresโ€ - partially true, but some manufacturers (for example, Google for Pixel) allow you to return the stock firmware before contacting the service.
  • โŒ โ€œCustom firmware breaks the cameraโ€ - depends on the model. On Samsung Exynos this is a common problem, but on Qualcomm cameras usually work fine.
โš ๏ธ Attention: Firmware based on Android 14+ may require mandatory certification Google for the operation of services (for example, Google Pay or Netflix in HD). Check this before installation!

2. Preparing for flashing: backup, drivers and tools

First step - save all data. Even if you plan to flash the device without resetting (dirty flash), the risk of losing information remains. Here's what you need to do:

  • ๐Ÿ“ฑ Backup applications and data: use Swift Backup (requires root) or Titanium Backup (outdated, but works on older versions of Android).
  • ๐Ÿ“‚ Copy of internal memory: connect your smartphone to the PC and copy the folders DCIM, Downloads, WhatsApp (if any).
  • ๐Ÿ”‘ Saving IMEI and serial numbers: write them down or take a photo (located in Settings โ†’ About phone or under the battery).
  • ๐Ÿ“‹ Export settings: if you use Nova Launcher, Tasker or other customized applications, save their configurations.

Next - Installing the necessary software on a PC:

Tool Purpose Link (official)
Platform Tools (ADB & Fastboot) Basic commands for unlocking the bootloader and firmware Section for developers on the site Google
Minimal ADB and Fastboot Simplified version for Windows GitHub or XDA Developers
TWRP Manager (or OrangeFox) Custom recovery for installing firmware Official website TWRP.me
Frija (for Samsung) Downloading official firmware Forum XDA

Don't forget check driver version for your device. On Windows, this can be done through Device Manager (section Portable devices or Other devices). For Mac/Linux standard drivers are usually sufficient, but you may need to install libusb.

โš ๏ธ Attention: If you are using a laptop, make sure it is connected to the network. Interrupting the firmware process due to a low PC battery can lead to hard brick (irreparable damage).
๐Ÿ“Š What firmware are you planning to install?
Official (stock) ROM)
Custom (LineageOS, Pixel Experience)
GSI (Generic System Image)
I donโ€™t know, Iโ€™m still choosing

3. Unlocking the bootloader: step-by-step guide

Without an unlocked bootloader (bootloader), it is impossible to install custom firmware. The process differs depending on the manufacturer:

  • ๐Ÿ“ฑ Google Pixel: unlocking is officially supported through the command fastboot flashing unlock.
  • ๐Ÿ“ฑ Xiaomi/Redmi/Poco: account linking is required Mi and waiting 7โ€“168 hours (depending on the model).
  • ๐Ÿ“ฑ Samsung: unlocking is only possible on models with Exynos-processors (for Snapdragon options in the USA - not possible).
  • ๐Ÿ“ฑ OnePlus: unlocking is available, but may reset data (even if you selected fastboot flashing unlock_critical).

General algorithm for most devices:

  1. Enable Developer mode (click on Build number 7 times in Settings โ†’ About phone).
  2. Activate USB debugging and OEM unlocking in the developer menu.
  3. Connect the device to the PC and do:
    adb reboot bootloader
  4. Check the status of the bootloader:
    fastboot oem device-info

    (look for the line Device unlocked: false).

  5. Unlock:
    fastboot flashing unlock

    (on some devices - fastboot oem unlock).

On devices with a chip MediaTek (for example Realme 9 Pro) unlocking the bootloader can lead to loss of IMEI. You can restore it only through the engineering menu or specialized utilities like MTK Meta Utility.

Make a backup of all data|

Charge the phone at least 70%|

Install drivers and Platform Tools|

Enable USB debugging and OEM unlocking|

Prepare a USB cable (better original)-->

4. Select firmware: stock ROM vs custom builds

The type of firmware determines what functions will be available, how stable the device will work and whether you will receive updates in the future. Let's consider the main options:

Official firmware (Stock ROM)

Suitable for:

  • โœ… Restoring the device after failure.
  • โœ… Refund of the warranty (if it is still valid).
  • โœ… Obtaining maximum stability (especially on Samsung or Google Pixel).

Where to download:

  • ๐Ÿ”— Samsung: Frija, SamMobile, Sammobile Firmware.
  • ๐Ÿ”— Xiaomi: Xiaomi Firmware Updater or Mi Flash Tool.
  • ๐Ÿ”— Google Pixel: official website Google (section Factory Images).

Custom firmware

Popular options in 2026:

  • ๐Ÿ“ฑ LineageOS โ€”the most stable and closest to stock Android.
  • ๐Ÿ“ฑ Pixel Experience โ€”firmware with proprietary features Google Pixel (for example, Now Playing or Call Screen).
  • ๐Ÿ“ฑ ArrowOS โ€”a balance between performance and customization.
  • ๐Ÿ“ฑ DerpFest โ€”optimized for games and multimedia.
  • ๐Ÿ“ฑ GrapheneOS โ€” for security paranoids (without services Google).

Where to look:

  • ๐Ÿ”— XDA Developers โ€” forum with discussions and links to firmware.
  • ๐Ÿ”— Telegram channels developers (for example, @LineageOSupdates).
  • ๐Ÿ”— Official firmware sites (for example, lineageos.org).
Firmware type Pros Cons
Stock ROM Maximum stability, support for all functions May contain blockware, slow updates
Custom (LineageOS, PE) Pure Android, regular updates, customization The camera, NFC or 5G may not work
GSI (Generic System Image) Suitable for devices without official support No optimization for hardware, lags are possible
โš ๏ธ Attention: Firmware based Android 14+ may require mandatory certification Google for banking applications (for example, SberBank Online or TinkoffCheck this before installation!
What is GSI and why do you need it?

GSI (Generic System Image) is a universal firmware that can work on any device with support Project Treble (all smartphones running Android 8.0+ It is not optimized for specific hardware, so some functions (for example, a camera) may work worse, than on custom firmware. However, GSI is the only option for devices for which there are no official builds (for example, for some models Motorola or Nokia).

5. Installing firmware via TWRP or Fastboot

There are two main ways to flash Android: via custom recovery (TWRP) or directly via Fastboot. The choice depends on the type of firmware and device.

Method 1: Installation via TWRP

Suitable for custom firmware (LineageOS, Pixel Experience etc.).

  1. Download the firmware (usually in the format .zip) and place it in the internal memory or SD card.
  2. Boot into TWRP:
    adb reboot recovery
  3. Do wipe (cleaning):
    • For clean installation: Wipe โ†’ Advanced Wipe (select Dalvik, Cache, System, Data).
    • For update (dirty flash): enough Cache and Dalvik.
  • Install the firmware: Install โ†’ select the zip file โ†’ Swipe to Confirm Flash.
  • After installing the firmware be sure to flash GApps (if you need services Google): download the appropriate package (for example, NikGApps) and install in the same way.
  • Reboot: Reboot โ†’ System.
  • Method 2: Installation via Fastboot

    Used for official firmware (for example, for Google Pixel or Xiaomi).

    1. Unpack the downloaded firmware (usually an archive with files .img).
    2. Connect the device in mode fastboot:
      adb reboot bootloader
    3. Run the firmware script:
      • For Google Pixel: flash-all.bat (Windows) or ./flash-all.sh (Mac/Linux).
      • For Xiaomi: use Mi Flash Tool (select Clean all and lock to completely clear).
  • Wait for completion (may take 5-15 minutes).
  • Reboot the device:
    fastboot reboot
  • Important nuance: On some devices (for example, OnePlus 11after flashing through Fastboot it may be necessary unlocking the bootloader againThis is normal - just repeat the command. fastboot flashing unlock.

    ๐Ÿ’ก

    If after flashing the device the device is stuck on the logo, try booting into TWRP and do Wipe โ†’ Format Data (this will delete all data, but often solves the problem).

    6. Solving problems after flashing

    Even if you did everything correctly, problems may arise after flashing. Here are the most common ones and how to fix them:

    Problem Possible cause Solution
    Does not turn on (black screen) Incorrect firmware or interrupted process Repeat the firmware, check model compatibility
    No network (IMEI lost) Partition damaged modem or EFS Restore IMEI through the engineering menu or MTK Meta Utility
    The camera does not work There are no drivers or libraries Halide Install a patch ANX Camera or flash another kernel
    Quick battery drain Unoptimized kernel or background processes Check Settings โ†’ Battery, flash another kernel
    Not working Google Pay No certification Google (SafetyNet) Install Magisk and module Universal SafetyNet Fix

    If after flashing the device not detected by PC, try:

    • ๐Ÿ”Œ Reconnect the cable (it is better to use the original one).
    • ๐Ÿ”„ Reinstall the drivers (for example, Samsung USB Driver or Qualcomm QDLoader).
    • ๐Ÿ“ฑ Reboot the device in fastboot manually (hold Volume down + Power).

    Critical error: If after flashing the device does not respond to any buttons (the so-called hard brick), you may need EDL mode (Emergency Download Mode). For this you need a special cable or box (for example, Qualcomm 9008). It is almost impossible to do this at home - contact the service.

    ๐Ÿ’ก

    If it disappeared after the firmware 5G or VoLTE, most likely the problem is incompatibility of modem files. Try flashing a separate file modem.img from the stock firmware.

    7. Optimization after flashing: settings, root and Magisk

    Successful flashing is only half the battle. To make the device work quickly and stably, follow a few additional steps:

    1. Initial setup

    • ๐Ÿ”ง Disable unnecessary services Google v Settings โ†’ Google โ†’ Google Services (saves battery).
    • ๐Ÿ”‹ Activate Adaptive battery and limit background activity for unnecessary applications.
    • ๐Ÿ“ถ If there are problems with the network, manually select the operator in Settings โ†’ Mobile network.

    2. Obtaining root access (optional)

    If you need root access (for example, for AdAway or Greenify), install Magisk:

    1. Download the latest Magisk (.zip) from GitHub.
    2. Reboot into TWRP and flash Magisk.zip.
    3. Reboot and check root through the app Magisk.

    Attention: On Android 14+ Magisk may not pass SafetyNet even with the module Universal SafetyNet Fix. In this case, try Magisk Delta or roll back to Android 13.

    3. Performance optimization

    For additional speedup:

    • ๐Ÿ”„ Install a kernel with support EAS (Energy Aware Scheduling) - for example, Kirin or FrancoKernel.
    • ๐ŸŽฎ For games, disable MIUI Optimization (on Xiaomi) or activate Force GPU Rendering in the developer settings.
    • ๐Ÿ—‘๏ธ Clear the cache once every 1-2 months. TWRP once every 1โ€“2 months.
    How to check if SafetyNet is working?

    Open the application Magisk, go to the section SafetyNet and click Check SafetyNet. If the status is FAIL, install the module Universal SafetyNet Fix and reboot the device. If it doesnโ€™t help, check whether your bank (for example SberBank) is blocking root access.

    8. Common mistakes and how to avoid them

    Even experienced users sometimes make mistakes that lead to brick (turning the phone into a โ€œbrickโ€). Here are the most dangerous of them:

    • ๐Ÿšซ Incompatible firmware version (for example, firmware Redmi Note 10 Pro on Redmi Note 10). Always check the model in Settings โ†’ About phone โ†’ Model.
    • ๐Ÿšซ Using unofficial versions of TWRP. Download recovery only from the official website twrp.me or verified sources on XDA.
    • ๐Ÿšซ Interrupting the firmware process. Even if the device seems to be frozen, wait 10-15 minutes before forcing a reboot.
    • ๐Ÿšซ Installing GApps over existing. This leads to conflicts and endless reboots. Always do clean flash (full cleaning).
    • ๐Ÿšซ Ignoring instructions for wipe. For example, for LineageOS it is not enough to clear only Cache โ€”you need to format Data.

    The most dangerous error: firmware boot.img or dtbo.img from another model. This is almost guaranteed to lead to hard brick, and the device can only be restored through EDL or Qualcomm Firehose.

    โš ๏ธ Attention: On devices with Dynamic Partition (all smartphones running Android 10+), you cannot manually resize sections via TWRP. This will lead to data loss and possible brick.
    ๐Ÿ’ก

    If you are flashing the device for the first time, select official firmware or a stable custom build (for example, LineageOS). Leave experiments with beta versions or unofficial ports for later.

    โ“ Is it possible to reflash Android without a computer?

    Yes, but with reservations. Some devices (for example, Samsung with Odine Mobile or Xiaomi via MIUI Updater) allow flashing directly from the phone. However, for custom firmware you will still need TWRP, and installing it without a PC is impossible.

    โ“ Why does the mobile network not work after flashing the firmware?

    This is a problem when flashing custom ROMs. Reasons:

    • The file is missing modem.img or it is incompatible with your model.
    • The partition EFS (where the IMEI is stored) is damaged.
    • Incorrect APN settings (check in Settings โ†’ Mobile network โ†’ Access points).

    Solution: flash modem.img i vendor.img from stock firmware or restore IMEI through the engineering menu (##4636##).

    โ“ How to return stock firmware if something went wrong?

    The process depends on the manufacturer:

    • Samsung: use Odin or Smart Switch (in emergency recovery mode).
    • Xiaomi: Mi Flash Tool with option Clean all and lock.
    • Google Pixel: script flash-all.bat from the official archive.
    • OnePlus: MSM Download Tool (requires authorization).

    After returning the stock firmware, the bootloader will be automatically locked, and the device can be returned under warranty (if it is still valid).

    โ“ Is it possible to flash Android if the bootloader is locked?

    No. Unlocking the bootloader is a mandatory step before flashing the firmware. The exception is official updates via OTA or proprietary utilities (for example, Samsung Smart Switch), but they do not allow you to install custom firmware.

    On some devices (for example, Huawei or Honor) unlocking bootloader is officially prohibited. In this case, firmware is only possible through exploits (for example, DC-Unlocker), but this is risky.

    โ“ Which firmware to choose for maximum performance?

    Depends on the goals: