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

[andrew_yousry]

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:

GitHub - nilz3000/device_oneplus_lemonadep-TWRP

Contribute to nilz3000/device_oneplus_lemonadep-TWRP development by creating an account on GitHub.

github.com

GitHub - nilz3000/device_oneplus_sm8350-common-TWRP

Contribute to nilz3000/device_oneplus_sm8350-common-TWRP development by creating an account on GitHub.

github.com

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

 

[der_akinator]

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:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

 

[TheSayaMan]

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:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

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!!!!

 

[der_akinator]

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.

 

[TheSayaMan]

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 must be blind lol because I don't see that option in twrp?

 

[der_akinator]

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.

 

[der_akinator]

I must be blind lol because I don't see that option in twrp?

It's the third checkbox in the install zip menu. I think it performs the same action as the "Install current TWRP" function in the advanced tab.

 

[Shooter7889]

I must be blind lol because I don't see that option in twrp?

 

[TheSayaMan]

It's the third checkbox in the install zip menu. I think it performs the same action as the "Install current TWRP" function in the advanced tab.

Got it, I never realized it was there. Trying that now and see what happens.

 

[TheSayaMan]

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]

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]

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]

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.

 

[jamescable]

Has anyone flashed new GPU yet?

 

[andrew_yousry]

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:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

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]

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.

 

[andrew_yousry]

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.

did that already, can boot now normally to system, but can't boot TWRP

 

[der_akinator]

did that already, can boot now normally to system, but can't boot TWRP

Maybe it has to do with the firmware. What ROM, android version and firmware Version are you running?

 

[Mr.Conkel]

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:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

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]

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.