Creating a complete Android firmware image is like insurance for your smartphone. One wrong step when updating the firmware, an unsuccessful update or even a virus can turn the device into a “brick”, and with a backup copy (backup), you can restore functionality in a matter of minutes. But how to “remove” this image correctly so that it is functional? The methods differ depending on the phone model, version Android and even the type of bootloader unlocking.

In this article we will analyze all the current methods - from standard tools Google to advanced solutions like TWRP i adb. You will learn what data can be saved (and what cannot), how to avoid common mistakes when making a backup, and what to do if the image is not restored. We will pay special attention security: why some methods can lead to account blocking Google or loss of IMEI.

Important: the procedure requires technical training. If you have never worked with fastboot or custom recovery, start with the “Device Preparation” section - there we will explain the basic concepts. For experienced users, go straight to method c TWRP or dd.

1. Preparing the device: what needs to be done before creating the image

Before starting the backup, make sure that your smartphone is ready for the procedure. Skipping at least one of these steps can lead to an inoperable image or even data loss.

  • 🔋 Battery charge at least 70%. Interruption of the process due to discharge is one of the main reasons for devices becoming bricked.
  • 📋 Unlocked bootloader (bootloader). On most smartphones (Samsung, Xiaomi, Pixel) it is blocked by default. Unlocking erases all data!
  • 🔧 Enabled USB debugging. Find it in Settings → About phone → Build number (press 7 times), then return to Settings → System → For developers.
  • 💻 Installed drivers. For Windows download Google USB Driver or Mi Flash Tool (for Xiaomi). On Mac/Linux standard packages are usually sufficient.

If you plan to use TWRP or adb, check the compatibility of your model with these tools. For example, processors Samsung with processors Exynos often require special versions Odinerather than universal solutions. For Pixel and some OnePlus the standard fastboot.

⚠️ Attention: unlocking the bootloader on devices with Android 10+ can lead to resetting the keys DRM (for example, for Widevine L1). This means that after restoring from backup Netflix and Disney+ can only work in 480p.
📊 What smartphone do you have?
Samsung
Xiaomi
Google Pixel
OnePlus
Other

2. Method 1: Standard backup via ADB (without root)

This method is suitable for most devices and does not require superuser rights (root). It saves user data, applications and some settings, but not copies system partitions (for example boot or recovery). Ideal for backup before resetting or updating.

Instructions:

  1. Connect the phone to the PC via USB (select mode File transfer).
  2. Open command line (cmd on Windows or Terminal on Mac/Linux) and enter: 
    adb backup -apk -obb -shared -all -f backup.ab

    Where:

    • -apk — saves installed applications;
    • -obb — game data;
    • -shared — files on internal memory;
    • -all — all possible data.
  • A confirmation request will appear on the phone screen - enter the password (if you have one) and click Create backup.

    • The file backup.ab will be saved in the folder where the command was launched. To restore data, use: 

    adb restore backup.ab

    ⚠️ Attention: This method does not save SMS, call log and some system settings. They will require root or specialized applications like Swift Backup.

    Install ADB on the PC|Enable USB debugging|Connect the phone in file transfer mode|Check the free space on the PC (minimum 5-10 GB)|Disable screen lock (if there is a PIN/pattern)-->

    3. Method 2: Full image via TWRP (requires root or unlocked bootloader)

    TWRP (Team Win Recovery Project) is a custom recovery that allows you to create full images of all partitions of the phone, including system, boot and data. This method is suitable for a full backup before flashing the firmware or experimenting with the system.

    Steps:

    1. Install TWRP for your model (look for instructions on XDA Developers or 4PDA). To do this, the command is usually used: 
      fastboot flash recovery twrp.img
    2. Boot into TWRP: turn off the phone, then hold down Power + Volume up (the combination may vary).
    3. In the main menu select Backup.
    4. Tick the partitions for backup (we recommend all except cache and android_secure).
    5. Select a save location (preferably on microSD or an OTG flash drive).
    6. Swipe to get started process.

    Recovery occurs in the same way: in TWRP select Restore and specify the folder with the backup. The time to create the image depends on the amount of data - it takes ~20-30 minutes. 128 GB takes ~20-30 minutes.

    Section What it contains Do I need to backup?
    boot Kernel and system bootloader Yes (critical for recovery)
    system Android system files Yes (if you plan to return to the current firmware)
    data Applications, settings, user files Yes (the most important section)
    recovery Stock or custom recovery No (you can reflash it separately)
    What to do if TWRP does not see the internal memory?

    If TWRP does not display files on the internal drive, this may be due to encryption FBE (File-Based Encryption) in Android 10+. Solutions:

    1. Use OTG adapter and a flash drive.

    2. In settings TWRP enter the unlock password (if you have one).

    3. Format data to TWRP (erases all data!).

    4. Method 3: Manually copying partitions via ADB Shell (for advanced)

    This method is suitable for those who want to gain maximum control over the process. Here we will use the command dd to copy partitions byte byte. Danger: one error in the command can erase the partition beyond recovery!

    Example for backing up a partition boot:

    1. Connect your phone and open adb shell with rights root: 
      adb shell

      su

    2. Find the list of partitions: 
      ls /dev/block/by-name/
    3. Copy the partition to the PC (replace boot with the desired partition): 
      dd if=/dev/block/by-name/boot of=/sdcard/boot.img
    4. Transfer the file to the computer: 
      adb pull /sdcard/boot.img

    To restore, use the reverse command: 

    dd if=/sdcard/boot.img of=/dev/block/by-name/boot

    ⚠️ Warning: Commands dd irreversibly overwrites the target partition. If you make a mistake along the way (of=), the data will be lost. Always test commands before executing!
    💡

    Before using dd create a text file with the commands and test it manually. This will help avoid typos that could cost the phone's functionality.

    5. Method 4: Backup via Fastboot (for devices without root)

    If you have an unlocked bootloader, but not root, you can use fastboot to copy critical partitions. This method works on most devices Google Pixel, OnePlus and some Xiaomi.

    Instructions:

    1. Boot the phone into mode fastboot: 
      adb reboot bootloader
    2. Create a partition image (for example, boot): 
      fastboot getvar all

      (to see the list of available partitions)

      fastboot flash boot boot.img

      (replace boot with the desired partition)

    3. Save the image on your PC: 
      fastboot flash boot backup_boot.img

      4. Unfortunately, fastboot does not allow you to copy the partition data (where user files are stored) without root. This will still require TWRP or adb with superuser rights.

      6. Method 5: Backup applications (without a PC)

      If you don’t want to mess around with commands, you can use specialized applications. They are easier to use, but have limitations:

      • 📱 Swift Backup — backups applications and data (requires root). data-i="206">- open source software for backup without
      • 🔄 Titanium Backup - a classic of the genre, but becoming outdated. Works only on Android 9 and below.
      • ☁️ OAndBackupX - open source software for backup without root (saves only APK and data of some applications).

      Disadvantages of such applications:

      • Do not save system partitions (boot, recovery).
      • May not work on Android 12+ due to limitations Scoped Storage.
      • Recovery sometimes leads to failures (for example, Swift Backup may not restore data correctly WhatsApp).
    💡

    Backup applications are convenient, but do not replace the full system image. Use them only for backing up applications and user data, and not for restoring after serious failures.

    7. Typical mistakes and how to avoid them

    Even experienced users sometimes encounter problems when creating an image. Here are the most common errors and their solutions:

    Problem Cause Solution
    ADB does not see the device Drivers are not installed or debugging is disabled Check adb devices, reinstall the drivers, re-enable debugging
    TWRP asks for a password, but does not accept it Encryption FBE v Android 10+ Use adb pull /data in TWRP or format data (data loss!)
    Error dd: permission denied No rights root or the partition is protected Get root or use TWRP
    The restored backup does not load Mismatch of kernel or firmware versions Restore the image only for the same version of Android and phone model

    Another common problem is loss of IMEI after recovery. This happens if you backed up and restored the partition modem or nvram on another device. Solution:

    1. Do not backup partitions associated with the modem if you are not sure of their compatibility.
    2. To restore IMEI, use the engineering menu (##4636##) or tools like ChimeraTool.

    8. Where and how to store the Android image

    Creating a backup is half the battle. It is equally important to save it correctly so that at a critical moment the file is not damaged or lost. Here are the basic rules:

    • 💾 Store on several media: for example, on a PC and in the cloud (Google Drive, Mega).
    • 🔐 Encrypt sensitive data. For this you can use 7-Zip with a password or VeraCrypt.
    • 📝 Keep a version log. Indicate the date the backup was created, Android version and phone model (for example, backup_20260515_Xiaomi_RedmiNote12_Android13.ab).
    • ⏳ Check integrity. Once every 3-6 months, test the recovery on another device or in an emulator.

    For cloud storage suitable:

    • Google Drive — convenient, but the 15 GB limit may not be enough for a full image.
    • Mega — gives 20 GB for free and encrypts files on the client side.
    • OwnCloud/Nextcloud — for those who prefer their own cloud.
    ⚠️ Attention: Do not store backups on internal memory phone! If the system crashes or resets, you will lose access to the files. Always copy them to an external drive or PC.
    💡

    The optimal storage option is an external SSD drive + cloud. SSD is more reliable than flash drives, and the cloud protects against physical data loss (fire, theft, etc.).

    FAQ: Frequently asked questions about Android backup

    Is it possible to make a backup without unlocking the bootloader?

    Yes, but with serious limitations. Without an unlocked bootloader, you can only save user data (via adb backup or applications like Swift Backup), but not system partitions. For the full image (boot, system), unlocking is required.

    Why does TWRP not see the internal memory on Android 12?

    This is due to the new type of encryption FBE (File-Based Encryption), which has been used since Android 10. TWRP cannot decrypt data without a password, even if you enter it. Solutions:

    • Use OTG adapter and an external flash drive.
    • Format data to TWRP (all data will be erased!).
    • Copy the necessary files via adb pull /data manually.

    Is it possible to restore a backup to another phone?

    Technically it is possible, but highly not recommended. Even if the phone models are identical, restoring the image to another device can lead to:

    • Loss of IMEI and network;
    • Conflicts with drivers;
    • Account blocking Google (due to mismatch of device identifiers).

    The only exception is restoration to the same device after resetting or replacing the motherboard (if IMEI is saved separately).

    How to check that a backup has been created correct?

    A full scan can only be done by restoring, but there are ways to minimize the risks:

    • Compare the size of the backup file with the original partition (for example, data a 64 GB archive should give an archive of ~20-50 GB in compressed form).
    • Try restoring the backup on the emulator (Android Studio) or a second device (if you have one).
    • Use the command sha256sum to check the checksum (if you backed up via dd).

    What to do if the phone does not work when restoring turns on?

    This is one of the most unpleasant situations, but there is no need to panic. Try the following:

    1. Reflash the stock firmware via Fastboot or Odine (for Samsung).
    2. Check the section boot. Often the problem is there. Try flashing it separately:
      3. fastboot flash boot stock_boot.img
    3. Use EDL-mode (for QualcommYou will need boxing (QFil or MiFlash) and an authorized manufacturer account.
    4. Contact the service, if you are not sure of your actions. Sometimes it’s easier to pay for repairs than to risk completely losing your data.