bro am delighted to have TWRP on Android 11, but will also go for android 12 .a greeting
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 9/Pro
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
huge thanks to @osm0sis for help in making and testing this recovery
Telegram group: https://t.me/NSSFB
In the title of this thread, it's written "[RECOVERY]  [OFFICIAL] TeamWin Recovery Project"
ok thx, this is very badIn the title of this thread, it's written "[RECOVERY]  [OFFICIAL] TeamWin Recovery Project"
 Refers to the Android version.
Also, it's well known already that TWRP is not officially there on A12 (rather ported/compiled/modded), and TWRP is incapable of decrypting on A12. In rare cases, some people managed to mod it and make it work with A12 including decryption.
If you search crashdump in this thread, you will see many causes of it. Most common cause is people not reading the OP fully and tried to flash TWRP on OOS 12.I get stuck after step 1.. computer sends it over fine, says booting finished. Phone goes into qualcomm crashdump mode. All my googling about this just says to hold vol up and power to reboot (which works fine), but no way to get past this for actually installing TWRP.
Not really. Devs are not interested in porting TWRP since Decryption is broken on A12 (Some managed to fix it). Most of the ROMs come with their own Lineage based recovery.
I'm pretty sure they're still working on it. I just don't know if Nebrassy has made any progress on his though.
You can nave rootI'm pretty sure they're still working on it. I just don't know if Nebrassy has made any progress on his though.
And is there a Lineage based recovery available for use with the stock OS in the meantime for A12? It'd be nice to update and still have root with A12.
the instructions say fastboot boot twrp.img, NOT fastboot flashSo far i have read onlyvup to page 8. But i noticed a lot of people having problems with fastboot (me included). I think fastboot flashes to inactive slot without saying so.
With slot a active, doing fastboot flash boot <filename>.img works fine (it goes to slot b) but rebooting anything (system, recovery, bootloader) ends up rebooting to fastboot mode in slot a (because of corrupted partitions).
I am now in twrp on slot b but can't sideload files to install ramdisk. Pc is not detecting device even with mtp enabled. Stuck at this point...
Edit: I was able to load the system on slot b. Transferred twrp img and installed ramdisk. Rooted and rebooted to system. On slot b.
Should i start again everything from the top to slot a (reboot slot a, fastboot twrp, install rom reroot)