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

Search This thread
By:
Advanced…
M

MENINBLK

Senior Member
May 4, 2011
58
19
Yonkers, NY
OnePlus 3T
OnePlus 8 Pro
der_akinator said:
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.
Click to expand...
Click to collapse

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

IamTheBRAVE

Senior Member
Jan 29, 2017
769
637
Morocco
Samsung Galaxy Tab 4
Samsung Galaxy A20
IamTheBRAVE said:
Flashed latest version. Decryption worked ( Paranoid Android 13)
Thank you🙏
Click to expand...
Click to collapse
Instructions say
der_akinator said:
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
Click to expand...
Click to collapse
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?
 
D

der_akinator

Senior Member
Mar 27, 2015
168
258
Berlin
OnePlus 3T
OnePlus 9 Pro
IamTheBRAVE said:
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?
Click to expand...
Click to collapse
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
 
  • Like
Reactions: osm0sis, Aqq123 and IamTheBRAVE
IamTheBRAVE

IamTheBRAVE

Senior Member
Jan 29, 2017
769
637
Morocco
Samsung Galaxy Tab 4
Samsung Galaxy A20
der_akinator said:
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
Click to expand...
Click to collapse
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.
patkoz16 said:
fastboot boot.img -> make ramdisk from boot.img -> flash full update f72 - > flash magisk is ok ?
Click to expand...
Click to collapse
Maybe this is the best way?
Thanks for taking the time to help us🙏
 
D

der_akinator

Senior Member
Mar 27, 2015
168
258
Berlin
OnePlus 3T
OnePlus 9 Pro
IamTheBRAVE said:
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🙏
Click to expand...
Click to collapse
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

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,307
34,655
Halifax
GT-i9250
Google Nexus 4
MENINBLK said:
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.
Click to expand...
Click to collapse
der_akinator said:
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.
Click to expand...
Click to collapse
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
M

MENINBLK

Senior Member
May 4, 2011
58
19
Yonkers, NY
OnePlus 3T
OnePlus 8 Pro
MENINBLK said:
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.
Click to expand...
Click to collapse
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
P

patkoz16

Member
Jul 2, 2020
23
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

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,307
34,655
Halifax
GT-i9250
Google Nexus 4
IamTheBRAVE said:
@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)
Click to expand...
Click to collapse
It flashes to both slots so that hopefully if your current slot breaks and Rescue Party switches slots you'll still have recovery access.
 
  • Like
Reactions: Smedslund, der_akinator and IamTheBRAVE
J

javi2246

Member
Jul 22, 2022
33
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!!
 
J

javi2246

Member
Jul 22, 2022
33
6
EugenStanis said:
tar fork 255 error?
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
 
D

der_akinator

Senior Member
Mar 27, 2015
168
258
Berlin
OnePlus 3T
OnePlus 9 Pro
javi2246 said:
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!!
Click to expand...
Click to collapse
@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.
 
You must log in or register to reply here.

Similar threads

eng.stk
Development [KERNEL] [blu_spark r136 OP9/Pro] [A13 Custom]
Replies
842
Views
100K
U
unzumutbar
Steve0007
  • Sticky
How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-F20/F74
Replies
2K
Views
302K
TheGhost1951
TheGhost1951
pranavasri
Development [ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonadep][FINAL][08/09/2022]
Replies
498
Views
70K
V
vsinha71
Nebrassy
Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Replies
613
Views
98K
TheGhost1951
TheGhost1951
mukesh22584
Development [ROM][A13][OP9Pro][r30][OOS-CAM] XTENDED XT-v5.0 [GAPPS][19-02-2023]
Replies
348
Views
49K
mettis88@gmail.com
[email protected]

Top Liked Posts

24 Hours 30 Days All time
  • 1
    TheGhost1951
    TheGhost1951
    Need4Sneed said:
    Maybe someone can answer a question for me: If I wanna replace this TWRP with LineageOS recovery, can I still follow the instructions for installing LOS 20, or do I need to take any extra steps? I remember reading that there is no dedicated recovery partition anymore, so it says to flash it to boot, but just wanted to confirm that that'll replace TWRP with LineageOS revovery.

    Thanks!
    Click to expand...
    Click to collapse
    Flash the required boot.img will replace TWRP.
    View
  • 9
    D
    der_akinator
    Good 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.
    View
    6
    D
    der_akinator
    osm0sis said:
    Seems to take a lot longer to boot and show the decryption prompt than -5. 🤔
    Click to expand...
    Click to collapse
    Uploaded a new build that reverts some of the fstab changes. Works fine on my device and hopefully on yours too.

    22-02-23 - Google Drive

    drive.google.com drive.google.com
    View
    5
    D
    der_akinator
    Update
    • Fix backups and logs not accessible from system
    If you already have backups that aren't accessible from system, flash change_backup_selinux_context.zip which is available in the latest download folder. All backups made with TWRP builds starting from 14-01-23 (aka 3.7.0-12.1-4) are affected.

    14-03-23 - Google Drive

    drive.google.com drive.google.com
    View
    5
    D
    der_akinator
    NAGARAJU02 said:
    👍
    Click to expand...
    Click to collapse
    Found the issue. New build is up.

    28-02-23-test - Google Drive

    drive.google.com drive.google.com
    View
    4
    D
    der_akinator
    Jack Droid said:
    Hi der_akinator,
    thanks for your reply.

    Why only boot.img can be flashed at the moment ?

    I do not understand the difference between TWRP flashnig methid and Fastboot / ADB sideload and the other stuff.....

    I ask only for better understand as I have anyway understood that the correct procedure is by using Fastboot / ADB sideload and so on.....
    Click to expand...
    Click to collapse
    I uploaded a new build with which you can flash vendor_boot and dtbo. It also adds backup support for additional firmware partitions.

    21-02-23 - Google Drive

    drive.google.com drive.google.com
    View
  • 46
    D
    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...
    forum.xda-developers.com forum.xda-developers.com

    Download:

    twrp-3.7.0-12.1 - Google Drive

    drive.google.com 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:
    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

    Uninstall:

    Just flash the boot partition with your current ROMs boot image with the following steps:
    1. Reboot to bootloader
    2. Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
    3. Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
    Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.

    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][UNIFIED] TWRP with A12/A13 encryption support

    This is an unofficial build of TWRP, based on...
    forum.xda-developers.com 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 forum.xda-developers.com

    Source Code:
    Bugs:
    • Permanent installation besides TMO stock isn't possible
    • 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
    View
    13
    D
    der_akinator
    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!

    30-12-22 - Google Drive

    drive.google.com drive.google.com
    View
    10
    D
    der_akinator
    Update
    • 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)
    Tested on LOS 19.1 (OOS 12 firmware) and crdroid 13 (OOS 13 firmware).

    08-02-23 - Google Drive

    drive.google.com drive.google.com
    View
    10
    D
    der_akinator
    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.

    04-02-23 - Google Drive

    drive.google.com drive.google.com
    View
    9
    D
    der_akinator
    Good 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.
    View

New posts