Development [RECOVERY][3.7.0-12.1][UNOFFICIAL] TWRP with A12/A13 encryption support

[der_akinator]

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9pro but it was confirmed to work on OP9 with OOS 12 firmware installed. Other configurations have to be tested.

As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.

For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:

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

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

forum.xda-developers.com

Download:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

Installation:

You have three option for this depending on your current system.

1. Option for rooted devices:

1. Download the twrp-installer zip
2. Flash it with magisk manager or some other kernel flash utility
3. Reflash your custom kernel and magisk if previously installed

2. Option for users with other custom recoveries but without root:

1. Download the twrp-installer zip
2. Flash it with "adb sideload twrp-installer*.zip"
3. Reboot to recovery
4. Reflash your custom kernel and magisk if previously installed

3. Option is universal:

1. OOS13 (firmware) users please download boot-oos13.img. All other users please use boot.img
2. Reboot to bootloader
3. Run "fastboot boot boot*.img" with the boot image
4. Go to Advanced > Flash Current TWRP
5. Reflash your custom kernel and magisk if previously installed

TWRP Updates:

1. Download and flash the twrp-installer zip
2. After that reflash your custom kernel and magisk if previously installed

ROM Updates:

Please follow the official update instructions for your ROM!

If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. And use the "Automatically reflash TWRP after flashing a ROM" option if you are going to install a ROM zip to preserve TWRP.

In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!

Instructions that work for me (on LOS based ROMs):

1. Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
2. Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
3. Reboot to system
4. If Gapps packages keep crashing:
   1. Reboot to TWRP
   2. Flash Gapps again
   3. Reboot to system

For OOS updates you can follow these steps (I haven't tested them):

[RECOVERY][3.7.0-12.1][UNOFFICIAL] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9pro but it was confirmed to work on OP9 with OOS 12. Other configurations have to be...

forum.xda-developers.com

About backups/restore:

Restore data only WITHOUT pin/pattern set.

Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.

In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:

[RECOVERY][3.7.0-12.1][UNOFFICIAL] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9pro but it was confirmed to work on OP9 with OOS 12. Other configurations have to be...

forum.xda-developers.com

Source Code:

• TWRP: https://github.com/TeamWin/android_bootable_recovery
• Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
• Device Tree:
  • https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
  • https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
  • https://github.com/LineageOS/android_hardware_oplus

Bugs:

• Vibration is not working
• vendor_dlkm mount error in fastbootd mode
• In case you notice anything else please let me know.

Thanks to:

• @Nebrassy for the original device tree
• @osm0sis for the installer zip
• TWRP team
• LineageOS

 

[_MartyMan_]

Thank you for this! Will try tomorrow.

 

[kushsix]

Ah man this is dope. Thank you bud!!!

 

[EugenStanis]

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

 

[Shooter7889]

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

 

[der_akinator]

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

 

[vipinpvarghese]

Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...

 

[der_akinator]

Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...

Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.

 

[vipinpvarghese]

Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.

You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?

 

[der_akinator]

You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?

Yes, but it was the same ROM I reinstalled after wipe.

 

[EugenStanis]

Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

 

[EugenStanis]

Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

Sorry i forgot about recovery log

 

[EugenStanis]

Sorry i forgot about recovery log

recovery.log

Zippyshare.com - Free File Hosting

www1.zippyshare.com

 

[sshriss]

Anyone tested it with stock OOS13?

 

[tnchng]

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.

As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.

For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:

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

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

forum.xda-developers.com

Download:

twrp-3.7.0-12.1 - Google Drive

drive.google.com

Installation:

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. Go to Advanced > Flash Current TWRP.
6. After that is done, if you were using a custom kernel, reflash it now.
7. If you were using magisk, reflash it now.
8. Reboot to bootloader.
9. Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.

In the case you just want to test TWRP without installation, please skip steps 5-7.
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. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.


Source Code:

• TWRP: https://github.com/TeamWin/android_bootable_recovery
• Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
• Device Tree:
  • https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
  • https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
  • https://github.com/LineageOS/android_hardware_oplus

Bugs:

Please let me know. I have not encountered anything major yet.


Thanks to:

• Nebrassy
• TWRP team
• LineageOS

 

[tnchng]

For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.

 

[der_akinator]

Update

Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.

Download:

29.11.22 - Google Drive

drive.google.com

 

[der_akinator]

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.

Here is a link to the github issue, maybe it helps you solving the problem.

createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project

Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...

github.com

 

[der_akinator]

For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.

I use C.63 and have not tested with other firmware versions.

 

[EugenStanis]

Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.

Strange, i have never ever in my life used multiuser