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

Search This thread

MENINBLK

Senior Member
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?
I'm will look how to overwrite the 3.7.0_12-0 but it's just cosmetic.

Everything seems to be working.
The error doesn't bother me.
I have been playing with different application and so far no problems.
Play Store is happy and Device is Certified.
DRM Security Level is L1.

I tried doing a full backup from TWRP.
It got caught on a Google Font and crashed with error 255.
I am going to give Titanium Backup Pro a try.
 
  • Like
Reactions: der_akinator

IamTheBRAVE

Senior Member
Flashed latest version. Decryption worked ( Paranoid Android 13)
Thank you🙏
Instructions say
1. Option for rooted devices:
  1. Download the twrp-installer zip
  2. Flash it magisk manager or some other kernel flash utility
  3. Reboot to recovery
  4. Reflash your custom kernel and magisk if previously installed
After flashing in magisk, i rebooted to system but then rebooting to recovery brought me back to my old recovery.
Edit: tried again. After booting twrp, it only lets me flash ramdisk not current twrp, and after flashing magisk i reboot to recovery and it's my old one.
What am i doing wrong?
 

der_akinator

Senior Member
Mar 27, 2015
127
167
Berlin
OnePlus 3T
OnePlus 9 Pro
Instructions say

After flashing in magisk, i rebooted to system but then rebooting to recovery brought me back to my old recovery.
Edit: tried again. After booting twrp, it only lets me flash ramdisk not current twrp, and after flashing magisk i reboot to recovery and it's my old one.
What am i doing wrong?
Sorry for that. I build a new version of the boot image that is able to boot without flashing vendor_boot but it broke the zip installer. I uploaded a new tested installer. https://drive.google.com/drive/u/0/folders/16PqxF4ryoiNCYbwPuL5eve7GtNoE7Nna
 

IamTheBRAVE

Senior Member
Sorry for that. I build a new version of the boot image that is able to boot without flashing vendor_boot but it broke the zip installer. I uploaded a new tested installer. https://drive.google.com/drive/u/0/folders/16PqxF4ryoiNCYbwPuL5eve7GtNoE7Nna
Tried again with same boot, new installer, didn't stick. Here's what i do:
Flash installer in magisk. Reboot👍
Reboot to TWRP recovery 👍
Install Ramdisk and magisk👍
Reboot Recovery --> Old recovery.
fastboot boot.img -> make ramdisk from boot.img -> flash full update f72 - > flash magisk is ok ?
Maybe this is the best way?
Thanks for taking the time to help us🙏
 

der_akinator

Senior Member
Mar 27, 2015
127
167
Berlin
OnePlus 3T
OnePlus 9 Pro
Tried again with same boot, new installer, didn't stick. Here's what i do:
Flash installer in magisk. Reboot👍
Reboot to TWRP recovery 👍
Install Ramdisk and magisk👍
Reboot Recovery --> Old recovery.

Maybe this is the best way?
Thanks for taking the time to help us🙏
Maybe try to use your steps again without "Install Ramdisk". I think I should change the update instruction. What I meant is to use either the install to ramdisk option OR the installer zip.
Edit: Yes, it's definitely the install to ramdisk step that breaks the update.
 
Last edited:
  • Like
Reactions: IamTheBRAVE

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,189
34,448
Halifax
GT-i9250
Google Nexus 4
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.
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.
I noticed a similar error when rebooting into fastbootd. Even on Lineage. Not sure what's up there.

I believe there is no twrp-12 branch in effect, only 12.1, so 3.7.0_12 is correct and matches mainline TWRP. Best to leave it alone.

Would be nice if you could adjust the status header to be below the holepunch when you get the chance! Awesome (and rapid!) work here! 🤘😁

Edit: Oh wait, you just meant the build iteration from -0 to -1! 🤦‍♂️😅
 
Last edited:
  • Like
Reactions: der_akinator

MENINBLK

Senior Member
Everything seems to be working.
The error doesn't bother me.
I have been playing with different application and so far no problems.
Play Store is happy and Device is Certified.
DRM Security Level is L1.

I tried doing a full backup from TWRP.
It got caught on a Google Font and crashed with error 255.
I am going to give Titanium Backup Pro a try.
Titanium Backup Pro works great!
I can export Full Backups to my external 2TB SanDisk SSD.
Thank you for all your quick responses and hard work!!
 
  • Like
Reactions: galaxys

patkoz16

Member
Jul 2, 2020
22
0
OnePlus 9 Pro
after instal twrp instaler in old twrp i my touch screen no responde . recovery reload but i cant unlock . i do this in old oos a11 is important ?
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,189
34,448
Halifax
GT-i9250
Google Nexus 4
@der_akinator i was wondering... The installer installs to both slots, so switching slots would let us boot to twrp?
Edit: I know what i was doing wrong. I was flashing a magisk-patched-boot.img (with old recovery)
It flashes to both slots so that hopefully if your current slot breaks and Rescue Party switches slots you'll still have recovery access.
 

javi2246

Member
Jul 22, 2022
31
6
I confirm that it works on a oneplus 9 (lemonade) with 19.1 lineageos. Installed using magisk.
The only problem I had is error 255 when making the backup, I had to delete the folders/files from /data/fonts
So far I have not tried a restoration.

Thanks to the developers!!
 

javi2246

Member
Jul 22, 2022
31
6
Yes. Copy/paste the lines of recovery.log

I:Error adding file '/data/fonts/files/~~KkPG4uxtzUMZudXdUn6XaQ==/GoogleSans-Regular.ttf' to '/data/media/0/TWRP/BACKUPS/ccbf8d84/2022-12-02--16-08-52_lineage_lemonade-userdebug_12_SQ3A220705004/data.f2fs.win005'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/ccbf8d84/2022-12-02--16-08-52_lineage_lemonade-userdebug_12_SQ3A220705004/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
 

der_akinator

Senior Member
Mar 27, 2015
127
167
Berlin
OnePlus 3T
OnePlus 9 Pro
I confirm that it works on a oneplus 9 (lemonade) with 19.1 lineageos. Installed using magisk.
The only problem I had is error 255 when making the backup, I had to delete the folders/files from /data/fonts
So far I have not tried a restoration.

Thanks to the developers!!
@MENINBLK had the exact same problem also with google fonts. Maybe he found a solution for that. I will try to replicate for myself and search for a solution.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.