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

Search This thread
Nah, not at this point anyway. I've been trying to simply set up my new laptop for like 5 months, but there just hasn't been enough time between work and with our 7 month old baby at home.
I would try and get infected to help but he abandoned the 8 pro and haven't been able to communicate with him for months so not sure what's going on there
 

CZ Eddie

Senior Member
Sep 27, 2011
6,332
2,377
Austin, TX
What am I doing wrong?
I'm on Android 11 AOSP custom ROM that uses their own custom recovery.

When I go into fastboot mode and run "fastboot boot twrp.img" it "flashes" without any error.
Then when it reboots and tries to go into TWRP, my phone gets stuck at a "fastboot mode" splash screen.

This is my TWRP file. twrp-3.6.2_11-0-lemonadep.img

EDIT: RESOLVED:


I tried to reflash my ROM but it failed.
Then, I flashed this kernel: Requiem-Nightly-03092022-LEMONADE.zip
That soft-bricked me. So, then I flahed a much older version of my ROM and that worked fine.
Now I'm able to fastboot boot to TWRP without any issue.

I figured it was probably a kernel issue. I think I was previously on Arter kernel.
 
Last edited:
  • Like
Reactions: bluebirdsysx
Nah, not at this point anyway. I've been trying to simply set up my new laptop for like 5 months, but there just hasn't been enough time between work and with our 7 month old baby at home.
Anyone try it yet?
 

Attachments

  • Screenshot_20221013-015355_Chrome Beta.png
    Screenshot_20221013-015355_Chrome Beta.png
    352.5 KB · Views: 63
  • Screenshot_20221013-015503_Chrome Beta.png
    Screenshot_20221013-015503_Chrome Beta.png
    356.8 KB · Views: 63
  • Screenshot_20221013-015459_Chrome Beta.png
    Screenshot_20221013-015459_Chrome Beta.png
    386 KB · Views: 63

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,120
34,310
Halifax
GT-i9250
Google Nexus 4
  • Like
Reactions: Samuel Holland
Android 12 decryption is listed in the changelog under the Android 12 branch. Unless something crazy has happened I think you'll find once you boot the ROM and it sets up encryption you won't be able to use TWRP decrypted, if at all.
I was able to boot ROM, And go back to twrp and use it again just fine. You need this to do a full device decryption
 

Attachments

  • DFE-NEO-1.2.0.010-STABLE.zip
    7.6 MB · Views: 57
  • IMG_20221013_083214_884.jpg
    IMG_20221013_083214_884.jpg
    37.1 KB · Views: 62
  • Like
Reactions: Samuel Holland

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,120
34,310
Halifax
GT-i9250
Google Nexus 4
I was able to boot ROM, And go back to twrp and use it again just fine. You need this to do a full device decryption
Right, so DFE = Disable Force Encrypt. Most people don't want to run their devices unencrypted. So yeah, TWRP _11 doesn't support Android 12 decryption, as previously stated.

I don't recommend anyone else try using TWRP _11 on an Android 12 ROM with encryption either, since I just did and now I can't get Lineage 19.1 to boot, so :(

Edit: Dirty flash of ROM from Lineage Recovery (+GApps +Magisk since addon.d doesn't work in Lineage Recovery) got it booting again. 😅
 
Last edited:
Edit: Dirty flash of ROM from Lineage Recovery (+GApps +Magisk since addon.d doesn't work in Lineage Recovery) got it booting again. 😅

FWIW, I don't ever rely on addon.d working, no matter which recovery I use. Whenever I update my ROM, I always flash the new version, reboot to recovery, flash MindTheGapps, flash Magisk, reboot, profit. :D
 

Flecto

Member
Dec 16, 2021
11
16
Hmm, or not: https://jenkins.twrp.me/view/TWRP Release Android-12.1/ ☹️

We need a new maintainer to bring-up the device tree to android-12.1, since @Nebrassy has confirmed he is stepping down.
I **might** be interested in helping out. I want to get TWRP running on A12 on my OnePlus 9 Pro, too. I am a software engineer, so I'm familiar with dealing with code, git, and whatnot. But I've never done anything with Android, so I would need some pointers in what exactly is involved with maintaining a device tree. What is the purpose of the code in the device tree? I'm assuming it has to do with configuring TWRP for a specific device? What is the process for figuring out what the configuration is? How do I get started?
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,120
34,310
Halifax
GT-i9250
Google Nexus 4
I **might** be interested in helping out. I want to get TWRP running on A12 on my OnePlus 9 Pro, too. I am a software engineer, so I'm familiar with dealing with code, git, and whatnot. But I've never done anything with Android, so I would need some pointers in what exactly is involved with maintaining a device tree. What is the purpose of the code in the device tree? I'm assuming it has to do with configuring TWRP for a specific device? What is the process for figuring out what the configuration is? How do I get started?
Hey! Join us on the TWRP Zulip at the link in the release post: https://twrp.me/site/update/2022/10/10/3.7.0-released.html

All the active maintainers are there so I'm sure there will be someone to point you in the right direction! 😁
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Would it be possible to fix mounting a usb drive in this version, I really like being able to have twrp again however I'm still forced to boot the old img in order for my otg drive to mount. It'd be extremely nice if it were fixed in this version!
    I uploaded a new build that fixes OTG and a couple of other things.

    Here is the link to its thread:
    4
    Decryption is working now. But the caveat is that you have to flash a vendor_boot image to boot twrp. I'm looking to find a way around this either by avoiding it at all, which might not be possible, or by merging the rom and twrp vendor_boot into one. If someone has some experience or ideas please let me know.

    If you want to test it, the best way is to download or extract a copy of your rom's vendor_boot. After that you flash the twrp vendor boot and boot the boot.img the same way as the old twrp. In order to boot into your normal OS, the rom's vendor_boot image has to be reflashed.

    Edit: Permanent installation seems to work. So after installation as described by Nebrassy reboot to bootloader and reflash rom's vendor_boot. After that you should be able to boot into your normal OS and TWRP. I tested it with crdroid 13.

    Here is a link to the two images you need:

    3
    can you please explain again how to test it?
    and steps to flash because I didn't understand.
    what are the files needed
    thank you
    1. Get your rom's vendor_boot image. For most roms this can usually be downloaded. For OOS based roms you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
    2. Reboot to bootloader.
    3. Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
    4. Run "fastboot boot boot.img" with the TWRP boot image.
    5. Optional permanently install TWRP as described by Nebrassy in the first post.
    6. Reboot to bootloader.
    7. Run "fastboot flash vendor_boot vendor_boot.img" with the rom vendor_boot image from step one.

    Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other roms or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot.

    Here is the link for the two images:

    2
    Hi everyone,
    I have got TWRP 3.7 based on android 12.1 working, but data decryption still does not work. Any ideas how to get the logs? They are by default written to data which does not work. Is there a way to get them over adb or so?

    In the case someone is interested here are the links to the device tree:
    1
    I asked the dev earlier, and he said his script is to decrypt data not to get r/w. But if you do decrypt, does everything work in TWRP? Some people seem to think not. Can you give us screenshots of backup, restore, zip flash, etc? Also of file manager making r/w changes to /system partition? Thank you.
    This was discussed in crdroid telegram
  • 64



    Introduction:

    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

    Installation:
    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

    Trees:
    https://github.com/TeamWin/android_device_oneplus_lemonadep
    https://github.com/TeamWin/android_device_oneplus_sm8350-common

    Telegram group: https://t.me/NSSFB

    Download: https://twrp.me/oneplus/oneplus9pro.html
    19
    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
    17
    Official builds have started

    10
    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
    9
    Hmm, or not: https://jenkins.twrp.me/view/TWRP Release Android-12.1/ ☹️

    We need a new maintainer to bring-up the device tree to android-12.1, since @Nebrassy has confirmed he is stepping down.
    I **might** be interested in helping out. I want to get TWRP running on A12 on my OnePlus 9 Pro, too. I am a software engineer, so I'm familiar with dealing with code, git, and whatnot. But I've never done anything with Android, so I would need some pointers in what exactly is involved with maintaining a device tree. What is the purpose of the code in the device tree? I'm assuming it has to do with configuring TWRP for a specific device? What is the process for figuring out what the configuration is? How do I get started?