The standard recovery menu, which is preinstalled on every Androidsmartphone, has extremely limited functionality. It only allows you to perform a factory reset or install an official update. However, this is not enough for advanced users. Installation custom recovery opens access to creating full system backups, installing unofficial firmware, obtaining root access and deep optimization of the device.
The process of replacing the stock bootloader with a modified one, for example TWRP or OrangeFox, requires care and understanding of the risks. An error at any stage can cause the phone to stop turning on. However, if you follow the sequence of steps and prepare the necessary files in advance, the procedure is successful in most cases. You get full control over your gadget, turning it from a simple content consumer into a flexible tool.
In this manual we will go through all the stages: from unlocking the bootloader to the first boot into the new menu. We won't use complicated terms without explanation, but rather focus on practical steps that apply to most modern devices. Remember that modification of system software is always carried out at your own peril and risk, so data is the first and most important step.
Preparing the device and necessary tools
Before you begin any manipulations with system partitions, you need to make sure that you have all the components for the job. You will need the smartphone itself, a USB cable (preferably an original one that provides stable data transfer) and a computer running Windows, macOS or Linux. Without a PC, installing via Fastboot in most cases is impossible.
Backup is a critical step. The installation process often requires a complete data wipe (wipe), so save contacts, photos and documents to the cloud or to an external storage device. Also make sure the battery is at least 60-70% charged. A sudden power outage while flashing the recovery partition can cause permanent damage to the boot sector.
You will also need drivers for your device. For smartphones based on processors Qualcomm usually you need Qualcomm USB Drivers, and for MediaTek -MTK VCOM Drivers. Users Samsung may require specific drivers, although standard ADB drivers are often sufficient. Check for drivers in Device Manager after connecting your phone in debug mode.
⚠️ Attention: Unlocking the bootloader and installing third-party software will void the manufacturer's warranty on the device. If your phone is still under warranty, think twice before starting the procedure.
☑️ Check before you start
Activating debugging and unlocking the bootloader
The first step in the chain of actions is to enable developer mode. Go to Settings → About phone and find the item Build number. Click on it 7 times in a row until a notification appears indicating that you have become a developer. After this, a new section will appear in the main settings menu For developers.
In the developer menu, you need to activate two key parameters: USB debugging and Unlocking the bootloader (OEM Unlocking). The second point may be missing on some devices, especially on models for the US market or on phones with a locked bootloader from the telecom operator. Without the ability to enable OEM Unlocking, further actions are impossible.
The process of unlocking the bootloader varies depending on the manufacturer. On devices Xiaomi a wait period of 7 to 168 hours is required after linking the account through a special Mi Unlock utility. On Pixel i Nexus unlocking occurs with a command in Fastboot mode. On Samsung you need to hold down the combination of buttons and confirm the action in a special menu, which also entails the activation of the Knox counter and the loss of Samsung Pay functions.
Why does unlocking erase data?
When unlocking the bootloader, the system forcibly performs a data reset (factory reset). This is a security measure designed to prevent an attacker who steals a phone from simply unlocking it and gaining access to the owner's encrypted data. Therefore, saving information is critical.
After executing the unlock command, the phone will reboot and clear all user memory. You'll have to go through the initial system setup again, connect to Wi-Fi, and sign in to your Google Account. Only after this can you proceed to the next stage.
Installing the Android SDK platform and drivers
To interact with a smartphone at a low level, you need a set of tools Android SDK Platform-Tools. This is an official package from Google containing utilities adb and fastboot. You should download it only from the official website of Android developers to avoid malicious modifications.
Unpack the archive with the tools into a convenient folder on drive C, for example C:\platform-tools. Work via the command line will be carried out from this directory. To avoid entering the full path every time, you can add this folder to the PATH environment variables of the Windows system, but for a one-time procedure it is easier to open the console directly in the folder.
Check that the connection is working. Connect your phone to the PC, making sure that debugging permission appears on the smartphone screen (click "Always Allow"). Open a command line in the tools folder and enter:
adb devicesIf the list displays the serial number of your device with status device, then the connection is established correctly. If the status is unauthorized, check the phone screen and confirm access. If the list is empty, check the cable or reinstall the drivers.
If the adb devices command does not see the phone, try changing the USB port on the motherboard (use the ports on the back of the system unit) or replacing the cable with a known good one that supports data transfer, and not just charging.
Search and download a custom recovery image
The most important file you will need is a recovery image with the extension .img. The most popular and stable solution is Team Win Recovery Project (TWRP). However, not all models have an official TWRP version. For some devices you have to use unofficial assemblies or alternatives, such as OrangeFox or PitchBlack.
You should look for files on specialized forums, for example, 4PDA or XDA Developers. Enter the exact codename of your device (codename), not the marketing name. For example, for Xiaomi Redmi Note 10 Pro the code name is sweet, and for Samsung Galaxy S21 — o1s. Using an image from another model is guaranteed to turn the phone into a “brick.”
Rename the downloaded file to recovery.img for convenience and place it in the folder platform-toolswhere the adb and fastboot utilities are located. This will make it easier to enter commands later. Make sure that the file does not have a double extension (for example, recovery.img.img) if you have hidden file extensions in Explorer.
Flashing recovery via Fastboot mode
Now put your smartphone into bootloader mode. Turn off your phone completely. Then hold down the button combination specific to your model. Most often this is Volume Down + Power. Some Pixel or OnePlus devices may require holding Volume up + Power. You should see a screen with an image of an Android robot or the word Fastboot.
Connect the phone to the computer and check the connection with the command:
fastboot devicesIf the device is detected, you can start flashing the firmware. The command for installing temporary recovery looks like this:
fastboot boot recovery.imgUsing the command boot runs the recovery image once without writing it to permanent memory. This is a safe way to test functionality. If the TWRP menu has loaded correctly, the sensor is working, and you see the file system, you can write it permanently with the command fastboot flash recovery recovery.img. However, on modern devices with dynamic partitions (A/B partitions), this command may differ or be unavailable.
On devices with A/B partitions (for example, new Pixel, OnePlus, Xiaomi), the firmware is often performed in an inactive slot. In this case, the command may look like fastboot flash recovery_a recovery.img and fastboot flash recovery_b recovery.img, or use a special script. After flashing the firmware, you must immediately boot into recovery, preventing the Android system from starting, otherwise the stock bootloader may overwrite the custom one.
⚠️ Attention: Samsung devices with Exynos processor do not use Fastboot, but Download Mode and the Odin utility. Fastboot commands do not work on such phones. Make sure you are using the correct method for your processor.
After entering the firmware (flash) command, immediately reboot into Recovery mode using the button combination. If the phone boots into a regular Android system, the stock recovery can automatically restore itself, replacing your modification.
Initial setup and creating a backup
After successful loading into TWRP the first step is to allow changes. Swipe the slider Swipe to Allow Modifications. If this is not done, the system will return to stock recovery upon the first reboot. Next, you need to encrypt or format the Data section if you see only strange character sets or mounting errors instead of folders.
Go to the section Wipe → Format Data, enter yes and confirm. This action will delete all data, but is necessary for encryption to work correctly in a custom environment. After this, return to the main menu and select Reboot → Recoveryto reboot into the prepared environment.
Now is the time to make a full backup of the current system. Go to section Backup. Select sections Boot, System (or System Image), Vendor and Data. Swipe to create a copy. This backup will be saved to internal memory or SD card. If the custom OS firmware fails, you can recover to the current operating state in a few minutes.
For ease of managing files inside the recovery, you can connect the phone to a PC. In TWRP mode, the device is often detected as an external storage device (MTP). You can copy zip archives with firmware, Magisk patches or kernels directly from your computer to your phone without using memory cards.
| Section | Description | Required for backup |
|---|---|---|
| Boot | Contains the system kernel and ramdisk | Yes (critical for loading) |
| System | Main files of the Android operating system | Yes (for firmware rollback) |
| Data | Custom applications, settings and files | Yes (saves your data) |
| Vendor | Drivers and hardware-specific libraries | Desirable (for stability) |
| EFS / Persist | IMEI, MAC addresses, sensor calibration | Critical (loss leads to loss of network) |
Frequent problems and ways to solve them
One of the common problems is the reboot loop (bootloop) after installing recovery or firmware. If your phone keeps rebooting endlessly, try going into TWRP, running Wipe → Advanced Wipe and clearing caches Dalvik / ART Cache and Cache. Do not touch the Data section if you want to save the files, but if all else fails, a full reset (Format Data) often solves the problem of version conflicts.
Another situation is the lack of access to internal memory in recovery mode (mounting error). This often happens when moving from one version of Android to another or when changing the encryption scheme. The solution is to format the Data section as described above. It's also worth checking to see if your phone has automatically updated over the air (OTA) to a new version of Android that is incompatible with your version of TWRP.
If your computer doesn't see your phone in Fastboot mode, try installing generic Google USB Drivers through Device Manager manually. Sometimes disabling driver digital signature verification in Windows helps. Also make sure that the cable is not damaged and the USB 3.0 port does not conflict with the device (try USB 2.0).
⚠️ Attention: Menu interfaces and item names may vary depending on the version of TWRP and the specific device. Always check the documentation for your model on the 4PDA or XDA forum, as the nuances of the firmware may change with the release of new versions of Android.
What is Bootloop and how to get out of it?
Bootloop is a state where the phone constantly reboots before reaching the desktop. A common cause is kernel incompatibility or damaged system files. To exit, hold down the power and volume buttons to get into Recovery, and reset the cache or perform a complete wipe. In the worst case, you will need to flash the stock image via Fastboot.
Questions and answers (FAQ)
Is it safe to install custom recovery on your main phone?
The procedure carries certain risks. If you follow all the steps correctly and use compatible files, the likelihood of failure is minimal. However, if you are not confident in your actions, it is better to practice on an old device. Always have stock recovery images on hand.
Will I be able to receive over-the-air (OTA) updates after installing TWRP?
In most cases, no. The presence of a modified bootloader or recovery violates the integrity of the system, and official updates either do not arrive or are not installed. You will have to update manually by downloading full firmware images and installing them through Recovery mode.
What to do if after the firmware the Internet is lost or the camera does not work?
This means that the Vendor partition or kernel modules are incompatible with the new version of the system. Try flashing the Vendor stock image from the original firmware of your Android version. Also check if you need to install additional compatibility patches (fixes) for your model.
Is it possible to remove custom recovery and return everything as it was?
Yes, this is possible. To do this, you need to download the stock recovery image (recovery.img) for your firmware version and flash it via Fastboot with the command fastboot flash recovery recovery.img. After this, it is advisable to completely flash the device using the official method to restore the guaranteed state.