How to make a backup of Android firmware: 5 proven methods

Firmware backup Android is not just a recommendation, but a necessity for those who plan to update the system, install custom firmware or repair the device. Without a backup, you risk losing not only user data, but also critical system files that can turn your smartphone into a “brick.” However, not all methods are equally effective: standard tools Android often save only applications and settings, and not the firmware itself.

In this article we will examine 5 ways to create a full firmware backup - from built-in functions to advanced solutions using ADB, TWRP and specialized utilities. You will learn how to save not only user data, but also the boot partition (boot), the system partition (system), and the recovery partition (recovery). We will pay special attention to the nuances for devices with a locked bootloader and without root access.

Before you begin, check: you must have at least 30-50% battery chargean original USB cable and a computer (for most methods). If you are working with Samsung, Xiaomi or other brands with proprietary firmware, please note that some methods may require unlocking OEM Unlock in the developer settings.

1. What is firmware backup and why do you need it? data-i="59">System partition

Backup firmware is a complete copy of all device memory partitions, including:

• 📱 System partition (system) - OS kernel, drivers, standard applications.
• 🔧 Boot partition (boot) - files necessary to start the system.
• 🗄️ Recovery partition (recovery) - environment for recovery or installation of firmware.
• 📁 User data (data) - applications, settings, files (optional).
• 🔐 Modem section (modem- files responsible for communications (LTE, Wi-Fi, Bluetooth).

Without such a backup, you will not be able to roll back to the previous version Androidif the update fails, or restore the device after a failure. For example, when installing custom firmware (LineageOS, Pixel Experience), it is often necessary to clear the partition system, and without a backup it will be extremely difficult to return to the stock firmware.

In addition, backup firmware is useful in the following cases:

• 🔄 Rollback to the previous version of Android after a failed updates.
• 🛠️ Device repair (replacement of the motherboard, flashing via EDL).
• 🔓 Unlocking the bootloader (on some devices this erases all data).
• 🧪 Experiments with kernels or modifications (for example, installation Magisk).

⚠️ Attention: On devices with Samsung Knox (for example, Galaxy S23, Note 20) unlocking the bootloader or installing a custom recovery may trigger the flag Knox 0x1, which will deprive you of the warranty and access to some functions (for example, Samsung Pay or Secure Folder).

2. Preparing the device before creating a backup

Before starting a backup, you need to complete several critical steps. Skipping any of them can lead to an incomplete backup or even data corruption.

Step 1. Enable USB debugging

Go in Settings → About phone → Build number and tap on it 7 times to activate developer mode. Then return to the main settings, open System → For developers and enable:

• 🔌 USB debugging (USB Debugging).
• 🔓 OEM unlocking (OEM Unlocking) - if you plan to work with the bootloader.

Step 2. Install the necessary drivers

The following must be installed on the computer:

• 🖥️ Drivers ADB and Fastboot (for example, via Minimal ADB and Fastboot or Platform Tools from Google).
• 📱 Drivers for your device (for example, Samsung USB Drivers for Galaxy, Mi PC Suite for Xiaomi).

Step 3. Check the available space

A full backup of the firmware can occupy 2 to 10 GB depending on the model. Make sure you have enough space on your computer or external drive. For devices with partition super (dynamic partitions used in Android 10+) may require up to 15-20 GB.

Windows debugging is enabled USB|ADB/Fastboot drivers installed|OEM unlocked (if needed)|Battery charge > 50%|Free space on PC > 10 GB-->

⚠️ Attention: On some devices (for example Huawei or Honor s EMUI) To work with fastboot authorization through the manufacturer's account is required. Without it, commands may fail with an error FAILED (remote: 'Token Verify Failed').

3. Method 1: Backup via TWRP (the most reliable method)

TWRP (Team Win Recovery Project) is a custom recovery that allows you to create complete backups of all partitions of the device, including boot, system and data. This method is suitable for most devices with an unlocked bootloader.

Advantages:

• ✅ Saves all partitions, including EFS (IMEI, serial numbers).
• ✅ Supports encryption backups.
• ✅ You can restore individual partitions.

Disadvantages:

• ❌ Requires an unlocked bootloader and root (on some devices).
• ❌ Does not work on devices with A/B sections without additional settings.

Instructions:

1. Download the official version TWRP for your model from the site twrp.me (file format - .img).
2. Reboot the device into mode fastboot:

   adb reboot bootloader

3. Flash TWRP via fastboot:

   fastboot flash recovery twrp-3.7.0_9-0-lavender.img

   (replace the file name with yours).

4. Boot into TWRP:

   fastboot reboot recovery

5. In TWRP go to Backup, select partitions (Boot, System, Data, EFS) and start the process.
6. Save the backup to an external memory card or computer (via MTP or ADB pull).

Backup in TWRP is saved in the folder /TWRP/BACKUPS/[serial_number]. It can be copied to a PC using the command:

adb pull /sdcard/TWRP/BACKUPS

4. Method 2: Backup via ADB (without root)

If you do not have root access or custom recovery, you can create a backup of some partitions via ADB. This method is suitable for devices with a locked bootloader, but it does not save all partitions (for example, boot or recovery will not be available).

What can be saved:

• 📁 User data (/data) - only if the device is not encrypted.
• 📱 System applications (/system/app).
• 📄 Configuration files (/system/build.prop).

Restrictions:

• ❌ You cannot copy boot, recovery or modem.
• ❌ On Android 10+ many system files are protected dm-verity.

Instructions:

1. Connect the device to the PC and check connection:

   adb devices

   (your device should be displayed).

2. Create a backup partition /data (if it is not encrypted):

   adb backup -f backup.ab -apk -obb -shared -all

   (a confirmation request will appear on the device).

3. For backup system files, use:

   adb pull /system/system/build.prop ./backup/

   (repeat for the required files).

File backup.ab can be later restored via:

adb restore backup.ab

⚠️ Attention: On devices with MIUI (for example, Xiaomi Redmi Note 11) command adb backup may not work due to manufacturer restrictions. In this case, use Mi PC Suite for a partial backup or unlock the bootloader.

su
dd if=/dev/block/bootdevice/by-name/userdata of=/sdcard/userdata.img

5. Method 3: Backup via Fastboot (for devices with an unlocked bootloader)

Method via fastboot allows you to copy any section devices, including those that are not accessible via ADB. This is a universal method that works even without TWRP, but requires an unlocked bootloader.

Advantages:

• ✅ Works on any device with fastboot.
• ✅ You can back up individual partitions (for example, only modem).

Disadvantages:

• ❌ Requires an unlocked bootloader.
• ❌ Inconvenient for regular backup (you need to manually list partitions).

Instructions:

1. Reboot the device into fastboot:

   adb reboot bootloader

2. Look at the list of available partitions:

   fastboot getvar all

   (look for lines like partition-type:...).

3. Create a backup of the desired partition (for example, boot):

   fastboot flash boot boot.img
   fastboot flash boot backup_boot.img

   (or use dd via TWRP).

4. For partition backup system (can be large):

   fastboot pull system system.img

For devices with A/B partitions (for example, Pixel or OnePlus) you need to back up both slots:

fastboot --set-active=a
fastboot pull system system_a.img
fastboot --set-active=b
fastboot pull system system_b.img

6. Method 4: Using specialized utilities (SP Flash Tool, Odin)

For processor-based devices MediaTek (MTK) or Samsung Exynos you can use proprietary ones utilities for creating backups. These tools are often used in service centers and allow you to save complete firmware images, including boot files and calibration data.

For MediaTek (SP Flash Tool):

• 🔧 Supports devices on MT65xx, MT67xx, MT81xx.
• 💾 Can read and write preloader, secro, nvram.

For Samsung (Odin):

• 📱 Works only with official firmware (.tar.md5).
• 🔒 Requires an unlocked bootloader (on new models - only through EDL).

Instructions for SP Flash Tool:

1. Download SP Flash Tool and firmware for your model (for example, from firmwarefile.com).
2. B SP Flash Tool select Scatter-loading File (file MTxxxx_Android_scatter.txt from the firmware).
3. Click Readback, add a new region and specify the partition addresses (can be found in the scatterfile).
4. Connect turned off the device to the PC and wait until reading is completed.

Instructions for Odin (Samsung):

1. Download the official firmware (.tar.md5) for your model from the site samfw.com.
2. Open Odin, connect the device in Download Mode (Volume Down + Power + Bixby).
3. B Odin click BL, AP, CP, CSC and select the appropriate files from firmware.
4. Click Startto flash (this will also create a backup copy of the current firmware in the form of files).

⚠️ Attention: On new devices Samsung (for example, Galaxy S22 and newer) to work s Odin may be required authorization through a Samsung account (function RMM State). Without it, the firmware will block the bootloader.

7. Method 5: Backup through custom scripts (for advanced users)

To automate the process, you can use scripts based on ADB, Fastboot or Python. For example, the script Android Image Kitchen allows you to unpack and edit firmware images, and FlashFire (outdated, but still working application) - to create backups directly from the device.

Example script for backup via ADB (requires root):

#!/bin/bash
Backup of all partitions via ADB (root required)
DEVICE=your_device_serial
OUTPUT_DIR=./backup_$(date +%Y%m%d)

mkdir -p $OUTPUT_DIR
adb -s $DEVICE shell "su -c 'for partition in $(ls /dev/block/bootdevice/by-name/); do
dd if=/dev/block/bootdevice/by-name/$partition of=/sdcard/backup_$partition.img
done'" && adb -s $DEVICE pull /sdcard/backup_*.img $OUTPUT_DIR/

Popular tools:

• 🐍 Android Image Kitchen - for unpacking and editing boot.img i recovery.img.
• 📦 FlashFire (outdated, but works on Android 5-9) - backup and recovery without a PC.
• 🔧 Parted - to work with partitions via ADB Shell.

For devices with A/B partitions (for example, Google Pixel) you can use a script ab-backup:

git clone https://github.com/chenxiaolong/ab-backup
cd ab-backup
./ab-backup.sh -v

fastboot flash [partition] [file.img]

fastboot flash boot backup_boot.img

fastboot --set-active=a
fastboot flash boot backup_boot.img
fastboot --set-active=b
fastboot flash boot backup_boot.img

8. How to check the integrity of the backup and restore the firmware

Creating a backup is only half the battle. It is equally important check its integrity to make sure that the recovery takes place without errors. Here's what you need to do:

Step 1. Checking hash sums

Compare the checksums (MD5 or SHA-256) of the original partitions and the backup. For example, for boot.img:

md5sum boot.img
md5sum backup_boot.img

If the hashes match, the file is copied correctly.

Step 2. Test recovery

Try to restore the backup on a test device or in an emulator (for example, via VirtualBox s Android-x86). If the device boots, the backup is working.

Step 3. Restore via TWRP

1. Boot into TWRP.
2. Go to Restore and select the folder with the backup.
3. Check necessary partitions and start recovery.

Step 4. Recovery via Fastboot

If you have a backup in the form of .imgfiles, flash them back:

fastboot flash boot backup_boot.img
fastboot flash system backup_system.img
fastboot reboot

⚠️ Attention: On devices with AVB (Android Verified Boot) (for example, Pixel or OnePlus s OxygenOS 11+) after recovery boot or system You may need to disable signature verification:

fastboot flashing unlock_critical
fastboot disable-verity
fastboot disable-verification

1. Correctness of partition firmware (for example, vendor must correspond to the firmware version).

2. Availability of the file vbmeta.img —it also needs to be restored or disabled checking (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img).

3. Compatibility of the bootloader version (bootloader) and firmware.-->

FAQ: Frequently asked questions about Android firmware backup