This is an easy way for recovery maintainers or anyone who's interested in building recoveries to finish their dream without a server.

Just Fork this Repository, Go to Actions tab, Select the Recovery Builder workflow.

Then select Run workflow dropdown from workflow_dispatch menu.

Input the following data in the fields.

• Recovery Manifest URL with -b branch: Your manifest URL with appended branch as in https://some_site/manifest_url -b android-x.y
• Device Company / OEM / Vendor: Your Device's Vendor name as in used inside DT. Example: xiaomi, samsung, asus, etc.
• Device Codename: Your Device's Codename as in used inside DT. Example: nikel, phoenix, ginkgo, etc.
• Device Tree link, with optional -b branch: Your Device's git URL with appended branch as in https//some_site/dt_link -b pbrp-x.y
• Kernel repo link with optional -b branch: Your Device's Kernel Source tree with appended branch as in https://some_site/kernel_source -b private_br [OPTIONAL]
• Require to manually have QCOM commonsys: , Set this to true if needed QCOM opensource commonsys
• Require to fix cryptfs_hw conflict: Set this to true if needed
• Build Target: Set as recoveryimage or bootimage if no recovery partition avaiable
• Build Flavor: Set as eng or userdebug

Then trigger the workflow.

That's it.

Your resulting recovery will be available inside the workflow's Summary tab as in recoveryzip and recoveryimage. They both are zip-compressed file.

Download and extract them to use.

• Initial Bringup and Improvements by Team Area69Lab and ElytrA8
• Modification by rokibhasansagar
• Workspace Cleaner and Build Environment Initializer by rokibhasansagar

Enjoy Building Recoveries.