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

Search This thread

andrew_yousry

Senior Member
Jan 31, 2012
52
5
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:
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
 
  • Like
Reactions: Stogie87

der_akinator

Senior Member
Mar 27, 2015
132
194
Berlin
OnePlus 3T
OnePlus 9 Pro
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:

 
Last edited:

TheSayaMan

Senior Member
Sep 12, 2016
918
385
OnePlus 9 Pro
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:

It works flawlessly for permanent install. Problem is, after installing a different ROM or updating a current one, no way to keep twrp without defaulting back to custom rom recovery. I tried flashing boot.img inside twrp to recovery ramdisk after flashing rom for testing purposes and it results in a crash dump. This is still much better than what we had to work with before. At least decryption and backups work, we didn't even have that before. Excellent work on this!!!!
 
Last edited:

der_akinator

Senior Member
Mar 27, 2015
132
194
Berlin
OnePlus 3T
OnePlus 9 Pro
It works flawlessly for permanent install. Problem is, after installing a different ROM or updating a current one, no way to keep twrp without defaulting back to custom rom recovery. I tried flashing boot.img inside twrp to recovery ramdisk after flashing rom for testing purposes and it results in a crash dump. This is still much better than what we had to work with before. At least decryption and backups work, we didn't even have that before. Excellent work on this!!!!
Have you tried the option "Automatically reflash TWRP after flashing a ROM"? I just updated to the latest crdroid and it worked without removing twrp. With OTA updates you will probably wipe twrp with any update. But now I'm stuck in a bootloop too.
 

der_akinator

Senior Member
Mar 27, 2015
132
194
Berlin
OnePlus 3T
OnePlus 9 Pro
Have you tried the option "Automatically reflash TWRP after flashing a ROM"? I just updated to the latest crdroid and it worked without removing twrp. With OTA updates you will probably wipe twrp with any update. But now I'm stuck in a bootloop too.
I just reflashed magisk and gapps after the bootloop, which fixed the issue. I don't exactly know what caused this.
 

Shooter7889

Senior Member
Mar 24, 2019
236
128
FLORENCE
OnePlus 7 Pro
OnePlus 8T

Attachments

  • Screenshot_2022-11-26-18-28-22.png
    Screenshot_2022-11-26-18-28-22.png
    125.3 KB · Views: 58

TheSayaMan

Senior Member
Sep 12, 2016
918
385
OnePlus 9 Pro
Have you tried the option "Automatically reflash TWRP after flashing a ROM"? I just updated to the latest crdroid and it worked without removing twrp. With OTA updates you will probably wipe twrp with any update. But now I'm stuck in a bootloop too.
This method worked the first time. It booted into system fine, then it booted into twrp fine but when I booted back to system again it bootlooped.
 

der_akinator

Senior Member
Mar 27, 2015
132
194
Berlin
OnePlus 3T
OnePlus 9 Pro
This method worked the first time. It booted into system fine, then it booted into twrp fine but when I booted back to system again it bootlooped.
Yes had the same problem. From bootloop I rebooted to twrp, performed advanced -> "Install current TWRP", installed magisk and gapps. I don't know which step recovered me from bootloop but after that everything worked fine.
 

TheSayaMan

Senior Member
Sep 12, 2016
918
385
OnePlus 9 Pro
Yes had the same problem. From bootloop I rebooted to twrp, performed advanced -> "Install current TWRP", installed magisk and gapps. I don't know which step recovered me from bootloop but after that everything worked fine.
For some reason that didn't work for me. I kept getting force closes after it booted to system. I had to factory reset and I flashed ROM and gapps through twrp. Now I'm all good.
 

IamTheBRAVE

Senior Member
I think flashing a rom doesn't overwrite some leftover gapps files (in /data i think) which causes the bootloop. I had that happen to me a while ago on another device with TWRP. All i had to do is reboot to twrp, remove those files in file manager (i think it was related to framework and services) then i rebooted to system ok. I reflashed gapps later.
 
  • Like
Reactions: der_akinator

andrew_yousry

Senior Member
Jan 31, 2012
52
5
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:

Thank you for the clear steps, actually didn't work for me.
after step 4. Run "fastboot boot boot.img" with the TWRP boot image, my phone is frozen on a screen with Fastboot Mode. Not booting TWRP or anything
any suggestions?
 

der_akinator

Senior Member
Mar 27, 2015
132
194
Berlin
OnePlus 3T
OnePlus 9 Pro
Thank you for the clear steps, actually didn't work for me.
after step 4. Run "fastboot boot boot.img" with the TWRP boot image, my phone is frozen on a screen with Fastboot Mode. Not booting TWRP or anything
any suggestions?
Hold vol up + power until the screen turns black and reboot to bootloader with vol down + power. Then flash the rom vendor_boot to be able to boot into your normal OS again.
 

Mr.Conkel

Senior Member
Oct 10, 2020
292
81
London
Nexus 7 (2013)
OnePlus 5T
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:

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!
 

TheSayaMan

Senior Member
Sep 12, 2016
918
385
OnePlus 9 Pro
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 agree. I have a otg cable and being able to use it would avoid the use of my laptop pc to flash roms. Unfortunately it won't detect it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi!


    I'm trying to install the TWRP on my LE2113 but i'm unable to do that.
    I do the unlock OEM and then:


    I can see the TWRP splash screen but, after that, anything.
    Only: Qualcom CrashDump Mode.

    More info:

    md5sum twrp*
    feeb319a795b6e8fe30578f8e81ba6fd twrp-3.7.0_11-0-lemonadep.img
    feeb319a795b6e8fe30578f8e81ba6fd twrp.img

    Fastboot info:
    Fastboot mode
    Product name: lahaina
    variant: sm_ ufs
    bootloader version: -
    Baseband version -
    serial number : XXXX
    secure boot : yes
    device state : unlocked.


    I'm doing something bad?

    Many thanks
    Are you not in the wrong forum trying to use the wrong TWRP? This is the OnePlus 9 Pro forum.
    1
    True, depending on what you have stored on internal storage, it could take hours to backup or restore. I prefer to copy internal storage to PC and use Swift Backup for apps and data call logs sms and export contacts
  • 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?