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

Search This thread

TheSayaMan

Senior Member
Sep 12, 2016
914
383
OnePlus 9 Pro
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.
That's weird because I'm on crDroid a13 and decrpyt works for me through internal storage and even otg cable works on latest updates. Maybe it's carrier specific. I have the unlocked T-Mobile variant. I wouldn't think so.
 

Zeus0fyork

Senior Member
Nov 30, 2020
74
30
That's weird because I'm on crDroid a13 and decrpyt works for me through internal storage and even otg cable works on latest updates. Maybe it's carrier specific. I have the unlocked T-Mobile variant. I wouldn't think so.
I just MSMd and am in the process of attempting to get it working again on a fresh install. I'll update if it works. I'm on LE2125 (global unlocked)
 

der_akinator

Senior Member
Mar 27, 2015
131
188
Berlin
OnePlus 3T
OnePlus 9 Pro

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,197
34,473
Halifax
GT-i9250
Google Nexus 4
im running the latest version right now & somehow my /system folder is showing no other subfolders like /priv-app or /app (except for addon.d & apex and 1-2 others). anybody got the same issue? would love a fix, but im still grateful that i have a working twrp at all🙏🏽
You just haven't mounted it yet; you're looking at the ramdisk.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,197
34,473
Halifax
GT-i9250
Google Nexus 4
i thought the same, so i mounted it but there was no change :/
Oh wait, you're right, but only sort of! It's mounting to /system_root now, and /system is still the ramdisk. I think that's the new norm from twrp-11 onward? Though I thought it was supposed to use /mnt/system or something at some point. 🤔
 
Last edited:

MENINBLK

Senior Member
Maybe I have found a fix for OSS users but I can't test it because I'm not running OOS. So please test this build.

SUCCESS !!!!

This is on F.16 OSS13.
F.17 incremental just was released but my bootloader is unlocked and I can only flash Full Updates.

There is just one little problem, the display says "Failed to mount '/vendor_dlkm' (block device required
I can't read the whole line, it runs off to the right of the screen,
it does not affect anything that I can tell.

TWRP display still says 3.7.0_12-0 not 12-1.

Do you want the log files again ?
 

der_akinator

Senior Member
Mar 27, 2015
131
188
Berlin
OnePlus 3T
OnePlus 9 Pro
SUCCESS !!!!

This is on F.16 OSS13.
F.17 incremental just was released but my bootloader is unlocked and I can only flash Full Updates.

There is just one little problem, the display says "Failed to mount '/vendor_dlkm' (block device required
I can't read the whole line, it runs off to the right of the screen,
it does not affect anything that I can tell.

TWRP display still says 3.7.0_12-0 not 12-1.

Do you want the log files again ?
So decryption is working on OOS13? Great. Yes I know there isn't an vendor_dlkm partition on OOS but this is needed to load kernel modules for custom roms. Does it affect you in any way or is it just the error message? Can you maybe test backups?
I'm will look how to overwrite the 3.7.0_12-0 but it's just cosmetic.
 
Last edited:

Top Liked Posts

  • 1
    Have seen that there is a test version on your google drive. What needs to be tested?
    I uploaded a new test builds with vibration enabled and some additional safety measures to prevent lagging or freezes. Feel free to test it.

  • 9
    Update
    • add vendor_boot and dtbo to backup targets
    • add CPU temperature output
    • fix vibration (still doesn't work in fastbootd mode)
    I tested this build on LOS 19.1 (OOS 12 firmware) and crdroid 13 (OOS 13 firmware). Also keep in mind that you have to use the boot image according to your installed firmware, if you want to install/test via fastboot.

    6
    Update

    This is mainly for OOS13 users that want to install via fastboot.
    • new OOS13 boot image for installation option 3 (tested on OP9pro with OOS13-F72 and F73)
    • adb works independently of mtp now. So it works before decryption and in fastbootd mode.
    4
    @der_akinator, could you add vendor_boot and dtbo to the list of partitions available on the Backup page? It'll cover everything important for custom kernels and recoveries in a backup/restore that way. 🤞😁
    Yes, I can upload a new build in a couple of hours.
    3
    The only issue now is that twrp is giving an error when installing magisk24.2.zip stating "error installing zip file"
    You should probably use version 25.2. The apk can be flashed like a zip installer. This works at least on OOS13-F73
    3
    OP9 not Pro version.
    Stock rom full updated to the last version. ( I can't remember what version was)

    Finally I got a brick and I unbricked with MSM and with stock rom.


    At this point I'm on Oxygen OS 11.2.10.10 LE25AA on OP9 model LE2113.
    with fastboot boot twrp.img was not working.
    I installed official "twrp-3.7.0_11-0-lemonadep.img" and then install with adb sideload twrp-installer-3.7.0-12.1-2-lemonadep.zip


    Recovery is loaded correctly but i'm not able to use (touch isn't working) also I tryed OTB mouse & keyboard but not working.
    I might have found a fix but for testing I depend on you because I haven't an OP9. If you want to stay on OOS11 you should probably use the official TWRP 3.7.0-11.0 version due to differences in encryption.

  • 42
    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:

    Download:


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

    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:

    Source Code:
    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 zip installer
    • TWRP team
    • LineageOS
    13
    Update
    • /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.)
    Have a happy New Year tomorrow!

    9
    Update
    • add vendor_boot and dtbo to backup targets
    • add CPU temperature output
    • fix vibration (still doesn't work in fastbootd mode)
    I tested this build on LOS 19.1 (OOS 12 firmware) and crdroid 13 (OOS 13 firmware). Also keep in mind that you have to use the boot image according to your installed firmware, if you want to install/test via fastboot.

    7
    Update

    Sorry for the short update cycles but there are some problems with vibration that results in heavy input delays.
    But the new update also includes a zip installer by @osm0sis which you can just flash to update your currently installed version.

    Download:
    7
    Update
    • fix Magisk installation bug
    • fix "failed to mount '/vendor_dlkm (Block device required)" error message on OOS