• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [RECOVERY] [11] [UNOFFICIAL] TeamWin Recovery Project

Search This thread


Senior Member
Mar 30, 2013
Savannah, GA
once you put the twrp the phone freezes does it happen to you too?
No because you're not supposed to flash it, fastboot boot NAME.img and then you have the option to install it but by booting it you can flash anything you want, but if you still need to install it once you boot TWRP go to advance then Flash Current TWRP to install recovery.
  • Like
Reactions: osm0sis


Senior Member
Mar 30, 2013
Savannah, GA


Senior Member
Aug 3, 2009
OnePlus 9
So I've read the entire thread, and if I understand things correctly, the current state of affairs (9/26/21) is that TWRP currently cannot decrypt the data partition or mount OTG/USB drives. As such,
- any ROM flash will require a full format of the data partition (typing 'yes' to wipe internet storage)
- any flashing activity can only be achieved via ADB sideload
- TWRP will have to be reinstalled via fastboot after every ROM flash

And lastly, the disable dm-verity zip does NOT work to leave the data partition decrypted and thereby eliminate the first couple of issues listed above.

That's my impression, at least. Am I right so far...? Thanks to anyone for confirmation or correcting me!
Last edited:
  • Like
Reactions: galaxys


Senior Member
Aug 3, 2009
OnePlus 9
Switching ROMs would need a format, updating an existing ROM would probably work fine despite no /data access.

While I have a tremendous amount of respect and appreciation for your knowledge and work over the years, I think that there might be a significant exception to your statement:
if the monthly security patch includes a different encryption scheme (which Google is known to do), then the ROM update will necessarily require a data partition format upon flashing to actually work...

Just a thought from my experiences with flashing a variety of ROMs on the OP6 through 7Pro and running decrypted.


Senior Recognized Developer / Contributor
Mar 14, 2012
Nexus 7 (2013)
IIRC the key gets updated in metadata and/or /data/uncrypted and /data doesn't have to technically be decrypted for either of those, just mounted (for the latter). But hey, decryption has never been my area, so 🤷‍♂️


Senior Member
Aug 3, 2009
OnePlus 9
Okay, so all that said (and now that I reread), decryption worked last time I tried. Did that change?
For everyone's sake who's flashing this, I hope not! I personally haven't installed this TWRP yet on my mission-critical device because of the current inherent limitations (I don't always have a PC around).

I was just getting PTSD recollecting the difficulties updating Havoc ROM on the OP6T due to near-monthly encryption changes... I think I wiped and restored internal storage several times before giving up and flashing the disable dm-verity zip. That's an experience I'm not looking to replicate -- maybe things are quite different in updates since then.

Thanks for the discussion at least, it's good to have devs around.

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Adb push?
    as in able to put zips/imgs on device, while twrp booted? 🤔
    yes at the moment it's possible. Sure should be possible.
    does anyone know if twrp retention script (magisk module) will work so I don't need to fastboot install (I'm not able to use a computer at the moment). that module would be great for my current situation
    Hi, yes I just updated using the "full" zip, installed TWRP retention script, flashed magisk to inactive slot, and I'm happy to report everything worked beautifully. 👍👍
    Hi, yes I just updated using the "full" zip, installed TWRP retention script, flashed magisk to inactive slot, and I'm happy to report everything worked beautifully. 👍👍
    dude this is exactly what I was about to do and thank you for letting me know it works! and thanks @osm0sis for the awesome module
    friend where do I download oos boot img?
    Hi guys this working op9 global for oxygenos 12 (android 12)
    its made for 11
  • 52


    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.

    Key Features:

    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)
    Onscreen keyboard
    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.

    Source Code:

    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

    Download: https://www.androidfilehost.com/?w=files&flid=326293
    new build is up

    fixed decryption on newer roms
    further fixes for flashing
    data can be formatted directly after flashing a rom
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    While TWRP development's ongoing here, I figured I'd also upload an OP9x Series version of my stock recovery adb insecure patching AK3 zip, which can be handy if, for example, after an OTA TWRP doesn't work anymore due to some change in OOS. So if something then goes wrong at least we've got decrypted data and adb shell dmesg access for our various devices via stock recovery. Attached below. Simply flash via FKM or EXKM once you're already rooted, before you flash TWRP, and then you may dump that patched stock recovery boot.img for later use.

    Supporting OnePlus9/lemonade, OnePlus9TMO/lemonadet, OnePlus9VZW/lemonadev, OnePlus9Pro/lemonadep and OnePlus9ProTMO/lemonadept.

    For OnePlus9R/lemonades see my OP8x+9R Series zip (since 9R is closer to 8T than 9): https://forum.xda-developers.com/t/...-unified-stable.4101313/page-57#post-84204575

    For more instructions see my original OP7T Series zip post: https://forum.xda-developers.com/t/...-adb-in-recovery.4002843/page-3#post-82376013
    So 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)
    the instructions say fastboot boot twrp.img, NOT fastboot flash
    released new build which solves the display issue on custom roms