FEATURES
Your gadget comes with a stock recovery mode by default. While this enables you to perform simple tasks like installing Over The Air (OTA) updates, Factory reset and backup, its very limited and can be unreliable at times. These are the problems that TWRP solves.
Flash Custom Scripts
Flash scripts in zip format e.g Magisk for root access, Multi disabler to disable FBE (file-based encryption), Vaultkeeper, Process authentication, wsm, Stock recovery auto-restoration etc
Install Custom ROMs
Custom ROMs can enhance your gadget by fixing existing bugs, de-bloating (to free up resources), disabling limiting securities (e.g RW) and adding awesome features for a sleek experience.
Easy Backup & Restore
Custom recoveries like TWRP make universal backups that you and other devices can restore. You can backup select or all partitions, giving you a truly customized backup & restore experience.
Device Management
Functions like Terminal access, ADB Root shell, ADB Sideload, Partition Management, File Manager, Fix Permissions etc enable you to make or reverse desired modifications and fix issues.
TWRP SCREENSHOT
Team Win Recovery Project (TWRP) is an open source, community project which replaces the stock recovery on Android devices with a feature rich custom recovery.
BUILD TWRP FOR YOUR DEVICE
Choose your image type, Android version and upload
FAQ
The sections to take note of are:
Image Type (required): You can choose recovery.img, boot.img or boot.img + vendor_boot.img depending on the stock files you wish to use. See the "Which image type should I choose" section below
Android Version (required): Out tool currently supports Android 9-14
Touch drivers (optional): This is for users who have touch screen not working issues on the built TWRP. See the "Touch is not working" section below.
Reduce TWRP size (optional): If the built TWRP is too large then set this to yes when rebulding else just leave the default.
TWRP flags (optional): This enables you to add custom flags to your device tree. You can request more flags to be added to our list.
Upload: The files you could possibly upload are boot.img, recovery.img, vendor_boot.img and patch.zip (ensure to maintain these file names). If you wish to upload multiple files, you select them all at once.
What is patch.zip and how do I create it?
This file is for users who wish to upload custom files or folders to the recovery > root folder in the device tree. Lets say you wish to fix touch issues by adding a vendor folder to the recovery > root folder. You simply zip the vendor folder, name it patch.zip then select it also when uploading your stock file(s) for build. Its important to keep this file as small as possible so your TWRP doesn't get too large.
To get the names of your touch drivers, install Device Info HW, launch and look under General > Touchscreen.
Lets say you have novatek,nf_nt36672c , it means there are two drivers. Search under vendor and vendor_dlkm (either on your device using a root file manager or by extracting / mounting the vendor.img and vendor_dlkm.img) for files that contain the names or parts of it. For example, searching for novatek, I found oplus_bsp_tp_novatek_common.ko and searching for nt36672c, I found oplus_bsp_tp_nt36672c_noflash.ko.
In this example, my touch drivers / modules are oplus_bsp_tp_novatek_common.ko and oplus_bsp_tp_nt36672c_noflash.ko so I input
oplus_bsp_tp_novatek_common.ko oplus_bsp_tp_nt36672c_noflash.ko
(ensure to separate multiple drivers by space) for touch drivers in the form above.
If touch still doesn't work then include a patch.zip (which would contain your touch drivers in a vendor > firmware folder) when uploading your stock files. See the "How does the tool work" section above for how to create patch.zip
If you find recovery.img then choose recovery.img and upload the file.
If you don't find recovery.img (or it fails) but find boot.img then choose boot.img and upload the file.
If choosing boot.img fails and you have vendor_boot.img then choose boot.img+vendor_boot.img and select both files at once when uploading.
For boot.img, you boot TWRP using the command fastboot boot boot.img. Once in TWRP, navigate to Advanced then choose Flash Current TWRP. Reboot to system once this is done. From this point, you can enter TWRP recovery mode using adb or button combo.
OTG: Yes. If its not detected when you connect then press the power button to trigger the lock screen or keep tapping buttons on the screen if you have touch. The OTG device should eventually show up.
Encryption: Not yet. We're working on a way to automate this process. You could flash DFE Neo v2 in TWRP to disable forced encryption or manually modify the fstab file
- 1. Unpack the TWRP image using Android Image Kitchen
- 2. Unpack the Stock image (same image type as the TWRP) using Android Image Kitchen
- 3. Copy the following from Stock split_img to TWRP split_img (* could be vendor_boot, recovery or boot):
- *.img-base
- *.img-board
- *.img-dtb_offset
- *.img-kernel_offset
- *.img-ramdisk_offset
- *.img-tags_offset
- 4. Repack the TWRP and flash
You need to make a few modifications to the recovery_ramdisk image after unpacking using Android Image Kitchen namely
- 1. Add values for ro.product.board and ro.board.platform to the prop.default
- 2. Unpack the other images (with recovery or kernel in the name) in Android Image Kitchen and search for recovery.fstab. Copy this fstab file to ramdisk > system > etc
- 3. Repack the image and use our tool again
- Install 7zip
- Right-click the TWRP and select 7-zip > Add to archive
- Change Archive format to tar
- Click OK
