In this guide, we will show you the steps to flash a different AOSP Recovery on a custom ROM. While we still have the likes of TWRP and OrangFox as the preferred custom recovery, however, they are mostly used in the stock ecosystem or when you are about to flash a custom ROM. However, as soon as you make a transition from the stock to custom, you’ll now get their associated recovery.
For instance, if you flash a LineageOS ROM, then you’ll get a LieanegOS ROM, crDroid will give you its crDroid Recovery, likewise for EvolutionX, and so on. While these recoveries do not have a standalone Install option, however, they do have the ADB Sideload that allows you to easily flash the file of your choice [though only the ZIP files]. Moreover, since all these recoveries are based on AOSP, you’ll find them having the same set of features, with just a slight change in UI/UX.
With that said, we have come across a few instances wherein the associated AOSP Recovery of that ROM doesn’t tend to work along the expected lines. While some are unable to sideload the file, others cannot perform a reset and some ROMs cannot even boot their device to the Recovery. So can’t we flash the TWRP Recovery and get the job done?
Well, you can but the thing is some don’t like the very idea of having the likes of TWRP or OrangeFix with them. Instead, they prefer or rather support just the AOSP-based recoveries. So in this guide, we will show you how to get this job done, in other words, flash a different AOSP Recovery on a different custom ROM. For instance, flashing a crDroid recovery on a LineageOS ROM, flashing EvolutionX Recovery on a PixelOS ROM, and so on. So without further ado, let’s get started.
How to Flash a Different AOSP Recovery on Custom ROM
While the below process will not wipe off any data on your device, still take a complete device backup, just to be on the safer side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
STEP 1: Download Android SDK Platform Tools
- To begin with, download and extract the Android SDK Platform Tools on your PC.
- This is the official ADB Binary given by Google and is required for ADB commands.
- After that, type in CMD in the platform-tools folder address bar and hit Enter.
- This will launch the Command Prompt and will act as our working directory.
STEP 2: Download Fastboot Enhance
- Next up, download and extract the Fastboot Enhance Tool on your PC.
- This tool will be used to extract the ROM file and get the custom recovery from it.
STEP 3: Extract Recovery from ROM
- Download the desired custom ROM whose custom recovery you wish to use.
- Once downloaded, extract the ROM ZIP and you’ll get the payload.bin file.
- Now transfer this payload.bin file to the Fastboot Enhance folder on your PC.
- Then launch the Fastboot Enhance Tool and go to its Payload Dumper tab.
- Click Browse, choose the payload.bin file, and select it. It will be loaded to the tool.
- Now select the recovery.img/boot.img/vendor_boot.img file from there, whichever is the recovery file for your ROM.
- You may refer to the ROM’s website or Downloads section to verify your ROM’s recovery.
- Moving on, once you have selected the file, check Allow Incremental, and hit Extract.
- Now choose a location and the recovery file will be extracted there.
- Transfer the recovery.img file to the platform tools folder on your PC.
STEP 4: Enable USB Debugging
USB Debugging is required so that your PC is able to identify the connected device in ADB Mode, which in turn will allow you to execute the desired ADB Command. So refer to the below steps and enable it right awayL
- Go to Settings > System > About Phone.
- Then tap on the Build Number 7 times.
- This will enable the Developer Options.
- Now go to System > Developer Options.
- Then enable the USB Debugging toggle.
STEP 5: Boot to Fastboot Mode
- First off, type in the below command in the CMD window:
adb reboot bootloader
- Your device will now boot to the Fastboot Mode.
- Now type in the below command to verify the connection:
fastboot devices
- If you are not getting any serial ID, then install Fastboot Drivers.
STEP 6: Flash AOSP Recovery
Now comes the most important part of this guide: flashing the AOSP Recovery. But before that, make sure that you have verified whether the custom recovery for your device is recovery.img, boot.img, or vendor_boot.img. Once that is done, you may then proceed with the below instructions:
- If the recovery is recovery.img, then use the below command to flash it:
fastboot flash recovery recovery.img
- On the other hand, if the recovery is boot.img, then use the below command:
fastboot flash boot boot.img
- If the recovery is vendor_boot.img, then the following command should be used:
fastboot flash vendor_boot vendor_boot.img
- Once flashing is done, let’s verify the result. For that, use the below command:
fastboot reboot recovery
- Your device should now boot to the newly flashed AOSP Recovery.
That’s it. These were the steps to flash a different AOSP Recovery on a different ROM. If you have any queries concerning the aforementioned steps, do let us know in the comments section below. We will get back to you with a solution as soon as possible.
