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

Search This thread

TheSayaMan

Senior Member
Sep 12, 2016
884
372
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
127
165
Berlin
OnePlus 3T
OnePlus 9 Pro

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,186
34,444
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,186
34,444
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
127
165
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

  • 2
    @der_akinator

    Hey, it's been a while but I wanted to update you. If you remember I was having severe problems with getting my 9 pro going, especially with TWRP. Well, I got profit. I used the crDroid c63 fw flasher instead of TheSayaMan's c66 flasher which apparently doesn't work for my variant, to get fw on both slots. That crDroid flasher installs their LOS style recovery, I believe I saw a post in the crDroid 9.1 thread from you about the kernel on the 20230113 build so I think you already know. But I used that recovery to flash WatchDogs & Magisk, but was getting hella glitches. Seemed like a copy&paste ROM w/different boot animation anyways. So I switched to crDroid. BTW, that comment on the crDroid thread saved my butt again - couldn't figure why Magisk wouldn't go.

    Anyways, got crDroid working, flashed your updated TWRP v3 and it's working great. Magisk too, after they updated the boot.img for the 20230113 build - thanks to your comment.

    However, when I try to flash blu_spark 120 in TWRP, I get an error: vendor_dlkm larger than vendor_dlkm partition: aborting. But I guess that's a question for the blu_spark thread.

    Also, I had meant to say thanks and let you know everything has been working out, but right when I got things going, I got an error on the app/site "oops, someone call neo. We broke the matrix" that my account had been BANNED! I never get in pissing matches or solicit or participate in solicitations or anything, so I dunno. It mentions being hijacked and I hadn't noticed any unusual activity, but now that I got it back (finally), I went to my account info and there was some weird stuff. Said I was in Sweden and an associated account id never heard of. The error msg says "allow 72 hours for response" - took 10 days. But that's still better than starting over from a new account. Kinda sad, but I'd prolly cry if I lost my "senior" status, which is probably just due to membership time. 😒 DroidNerd 4 life.

    Thanks again.
    I installed blu_spark on top of crdroid 20230113 build because of the magisk issues, but everything went fine for me. Maybe try the latest r123 blu_spark release.
    1
    So maybe I'm confused or maybe I'm doing something wrong. IDK. So one plus 9 pro bliss custom ROM. Android 13 based on 12.1. kinda new to 9 pro my last was a 6t. Anyway i had ROM installed flashed TWRP reboot recovery flash magisk again. Reboot system. Decided to reboot to recovery to check it out farther and TWRP is no longer there. It's back to LOS recovery again. So am I doing something wrong or is TWRP not suppose to retain.


    Edit: figured out my problem. After I flashed TWRP I rebooted to system. Installed magisk again, select file and patch, with TWRP installed. Then reboot to recovery and flash the magisk patched img. That had TWRP flashed and that did it.
    You can also flash the Magisk.apk directly in TWRP like a zip. That's a bit more comfortable.
    On this device it's also a bit more complicated to keep TWRP installed, because every time the boot partition is overwritten it is gone.
  • 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!

    7
    Update
    • fix Magisk installation bug
    • fix "failed to mount '/vendor_dlkm (Block device required)" error message on OOS
    5
    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
    First of all, edit your old post instead of making a new one each time you try...

    Second, maybe if xda's having trouble with attachments for you then you should stop trying to upload to xda? Try Google Drive or something instead...

    5 posts in a row like "did it work?" is a bit ridiculous.
    3
    Restore doesn't work on LOS 19.1. Force checked twice...

    I made the backup without pattern/pin, now when it comes to restoring I try to do a factory reset first, I restart I enter the OS, I go back to TWRP and I do the restore, I restart and the lineageos logo stays loading, it restarts only a couple of times, I enter TWRP to get the logs (it doesn't ask for a pin) but I'm going to mount the files and it's empty, it seems that everything has been deleted, in the "mount" option there is a button that says decrypt data, but it asks for a password (text)....
    I could reproduce your issue when restoring backup with pattern set. It looks like super and data shouldn't be restored at the same time.
    May solution:
    1. Factory reset but NOT format data in TWRP
    2. Flash previously installed OTA zip.
    3. Reboot to system
    4. Don't set any pin/password
    5. Reboot to TWRP
    6. Backup should show up again and restore only data
    7. Reboot to system
    8. If that doesn't help reboot to TWRP and restore only super

    Edit: It doesn't matter if backup is made with or without pin/pattern. It is important that pin/pattern is not present when restoring it.
  • 41
    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 installer zip
    • 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!

    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
    5
    Now it's working fine. I'm trying to find a way to flash twrp again.

    Edit flashed vendor.boot image and boot.img and now my phone is dead I gues it's not responding at all.

    Phone is booted to bootloader now.
    If you flashed boot then that's the problem. You don't flash boot. You boot it first.
    fastboot boot boot.img
    Follow the instructions and you won't have any problems.