Development [RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
- Thread starter der_akinator
- Start date
Yes, I tested both option with stock crdroid recovery installed. They both work and I have updated the installation instruction accordingly.Now that there's a TWRP zip you could skip vendor_boot shenanigans altogether by, a) flash from Magisk app, or even b) flash from custom ROM recovery like Lineage Recovery.
In the modules tab -> Install from storage. I also never realized that until now.
Okay, I was rooted with Magisk 25.2.
I flashed the TWRP using Magisk from the 30.11.22 folder.TWRP works but decryption does not.
I can not get to my data from TWRP to flash Magisk back.
HELP !!
I flashed the TWRP using Magisk from the 30.11.22 folder.TWRP works but decryption does not.
I can not get to my data from TWRP to flash Magisk back.
HELP !!
I uploaded a new version with the timestamp script used in op7.
drive.google.com
30.11.22 - Google Drive
Which android version are you using? A11 ROMs use a different encryption which is supported by the official builds. You can use the patch boot image option in magisk installer to get it working again.
Tested and doesn't work for me. Now it won't even try installing. Screen goes blank for a second and reloads twrp.I uploaded a new version with the timestamp script used in op7.
30.11.22 - Google Drive
Edit: My bad. It works. I had a bad download. Thank you!!!!
I am running OOS F.16 on my OP 9 Pro rooted with Magisk 25.2.
I used Magisk to install the unofficial TWRP image from the 30.11.22 folder you posted.
TWRP worked on the reboot to recovery but I could not see my folders at all.
When in TWRP, I tried to decrypt my data folder, I entered my password and it came back with FAILED.
So I rebooted back to System and Fastboot Boot the Magisk Boot.img and Directly installed Magisk from the Magisk app.
So not both apps are working, the decryption is not working in TWRP for OOS F.16.
Oh, one more thing, TWRP shows 3.7.0_12-0 not 12-1....
Last edited:
The TWRP install script flashes to both slots.
You will see it do this as it installs.
Strange that decryption is not working on OOS13. I just looked into the fstab of OOS F.11 and the encryption they use is the same as in TWRP. But I will note that there are problems with OOS13 in the first post
I downloaded the file again, just in case I had a bad download like @TheSayaMan did.
Installation went through without a hitch. Rebooted into TWRP and could not see my folders again.
I plugged in a USB Drive and reinstalled Magisk from the USB and then rebooted back into OOS13.
Everything except Decrypting is working.
Is there anything you need from my Oneplus 9 Pro that can help you ??
I just looked up the encryption on Android 13 from source.android.com,
it seems that Android 12 and below can use Full Disk/File encryption,
but Android 13 can only use File encryption.
I don't know if this helps or not.
Last edited:
It would be helpful to get a logcat output and recovery.log that captures the failure. You can select your usb as storage and copy those files with Advanced -> copy log.
Similar threads
- Sticky
Top Liked Posts
-
2
-
10Good new for OOS users. One of the TWRP devs found a workaround for data restore on OOS. Just delete "/data/system/users/0/package-restrictions.xml", after data is restored. I will exclude this file by default in a future build, but for existing backups, the file must always be removed manually.
Edit:
This is also useful for custom ROMs, because it makes first boot faster and eliminates the need to reboot again.6
Uploaded a new build that reverts some of the fstab changes. Works fine on my device and hopefully on yours too.Seems to take a lot longer to boot and show the decryption prompt than -5.
22-02-23 - Google Drive
drive.google.com
55Update
- Fix backups and logs not accessible from system
14-03-23 - Google Drive
drive.google.com
3
I'd use Swift Backup instead if I were you. TiBu hasn't been updated in ages, and it can't handle split APKs properly, thus you'd be boned when you tried to restore those apps (and it's not possible to tell if an app uses split APKs without, presumably, an app that can examine the APKs and tell you). Swift doesn't have nearly the number of esoteric bells and whistles that TiBu has (so if you need them, you can still use TiBu for them), but it has the advantage of a modern interface and can properly handle app backups on modern versions of Android. (It'll also back up text messages, call logs, wallpapers, and WiFi networks.) -
46This 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...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
To temporarily boot TWRP, use the first three steps of Option 3.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
- Download the twrp-installer zip
- Flash it with Magisk manager or some other kernel flash utility
- Reflash your custom kernel and Magisk if previously installed
- Download the twrp-installer zip
- Flash it with "adb sideload twrp-installer*.zip"
- Reboot to recovery
- Reflash your custom kernel and Magisk if previously installed
- OOS13 (firmware) users please download boot-oos13.img. All other users please use boot.img
- Reboot to bootloader
- Run "fastboot boot boot*.img" with the boot image
- Go to Advanced > Flash Current TWRP
- Reflash your custom kernel and Magisk if previously installed
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps:
- Reboot to bootloader
- Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
- Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
TWRP Updates:
- Download and flash the twrp-installer zip
- 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):
- Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
- Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
- Reboot to system
- If Gapps packages keep crashing:
- Reboot to TWRP
- Flash Gapps again
- Reboot to system
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on...
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.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to 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][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on...
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:
- Permanent installation besides TMO stock isn't possible
- In case you notice anything else please let me know.
Thanks to:
13Update
- /data/fonts/* is excluded from backups (has to be verified by someone with backup errors)
- screen turns completely off now
- updated firmware files from LE2125_11.C.63 (maybe this helps with OOS13 problems)
- initial installation is now possible without flashing vendor_boot (I tested a few combinations of installation methods and initial system configurations. So hopefully nothing is broken this time.)
30-12-22 - Google Drive
drive.google.com
10Update
- improve vibration support
- fix kernel modules loading in fastbootd mode for custom roms (might result in an error message regarding vendor_dlkm for OOS users, but it's just cosmetic)
08-02-23 - Google Drive
drive.google.com
10Update
- add vendor_boot and dtbo to backup targets
- add CPU temperature output
- fix vibration (still doesn't work in fastbootd mode)
04-02-23 - Google Drive
drive.google.com
10Good new for OOS users. One of the TWRP devs found a workaround for data restore on OOS. Just delete "/data/system/users/0/package-restrictions.xml", after data is restored. I will exclude this file by default in a future build, but for existing backups, the file must always be removed manually.
Edit:
This is also useful for custom ROMs, because it makes first boot faster and eliminates the need to reboot again.
