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

Search This thread
By:
Advanced…
T

TheSayaMan

Senior Member
Sep 12, 2016
1,122
495
OnePlus 9 Pro
MENINBLK said:
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.
Click to expand...
Click to collapse
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.
 
Z

Zeus0fyork

Senior Member
Nov 30, 2020
85
34
TheSayaMan said:
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.
Click to expand...
Click to collapse
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)
 
D

der_akinator

Senior Member
Mar 27, 2015
211
336
Berlin
OnePlus 3T
OnePlus 9 Pro
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,440
34,991
Halifax
GT-i9250
Google Nexus 4
DirtryElectroOP3 said:
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🙏🏽
Click to expand...
Click to collapse
You just haven't mounted it yet; you're looking at the ramdisk.
 
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,440
34,991
Halifax
GT-i9250
Google Nexus 4
DirtryElectroOP3 said:
i thought the same, so i mounted it but there was no change :/
Click to expand...
Click to collapse
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:
  • Like
Reactions: der_akinator, Aqq123 and DirtryElectroOP3
M

MENINBLK

Senior Member
May 4, 2011
62
23
Yonkers, NY
OnePlus 3T
OnePlus 8 Pro
der_akinator said:
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.

oos-fix - Google Drive

drive.google.com drive.google.com
Click to expand...
Click to collapse
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 ?
 
D

der_akinator

Senior Member
Mar 27, 2015
211
336
Berlin
OnePlus 3T
OnePlus 9 Pro
MENINBLK said:
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 ?
Click to expand...
Click to collapse
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:
You must log in or register to reply here.

Similar threads

eng.stk
Development [KERNEL] [blu_spark r145 OP9/Pro] [A13 Custom]
Replies
916
Views
115K
LOTIN
LOTIN
Steve0007
  • Sticky
How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Replies
2K
Views
329K
TheGhost1951
TheGhost1951
pranavasri
Development [ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonadep][FINAL][08/09/2022]
Replies
498
Views
73K
V
vsinha71
Nebrassy
Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Replies
613
Views
101K
TheGhost1951
TheGhost1951
T
Development OP9PRO-LEMONADEP-A13-ROM-WATCHDOGS-JUNE 3, 2023
Replies
571
Views
46K
Alberhasky
Alberhasky

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 6
    osm0sis
    osm0sis
    fastbootd should work...

    Also you can also flash abl while booted if you are rooted and want to do it manually, like `dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a`

    Same works in TWRP Terminal/adb shell.
    View
    6
    S
    shadabkiani
    orifori said:
    Hello, I installed an Android 13 custom rom on a Samsung device with twrp-3.7.0_9-0 but unfortunately there is no encryption. Does encryption depend on the rom or on TWRP and will this TWRP version work on a Samsung phone? And is there some trick to enforce encryption when flashing custom rom with TWRP?
    Click to expand...
    Click to collapse
    First of all, this is a thread for OnePlus 9/Pro; not Samsung. Please refer to your phone's forum for better support.

    Secondly, you should have written your phone model and ROM specifically in your message, rather than just "Android 13 custom rom on a Samsung device".

    Thirdly, encryption depends on the ROM you are using. Most latest phones/ROMs automatically encrypt data upon first boot. And if they don't, you can manually enable encryption from Settings > Security (requires charger plugged in). Just go to Settings > Security to see if it's already encrypted or not. There is no trick to enforce encryption at the time of flashing ROM in TWRP; not to my knowledge at least. It's a ROM-dependent feature (and "almost" all ROMs support it).

    Lastly, looking at the TWRP version, I assume your phone is from 2017-18, and most probably TWRP would be official for your phone, and it would support decryption. If your phone/ROM is encrypted, it would ask for decryption when TWRP boots.
    View
    6
    D
    der_akinator
    andrew_yousry said:
    I can'y thank you enough @der_akinator for reviving the TWRP recovery for OnePlus 9 Pro. I'm really happy for it.
    Thank you so much, everything works fine, except MTP. I can't see my storage when connected to my PC using USB cable.
    if you can fix this it would be great.
    Thank you again.
    Click to expand...
    Click to collapse
    I can't reproduce your issues too, and it's the same for the sideloading issues addressed by @Rallyharry. I tested under windows and linux with the latest builds. The only thing I noticed was that I had to switch drivers under windows manually to WinMTP and I couldn't use mtp and adb simultaneously. But the whole windows driver system is a mess anyway.

    I pulled some minimal changes from qcom's upstream usb repo and also added a proposed patch series regarding mtp into twrp source. My tests with those changes are fine, and I can upload a new build tomorrow, if you want.
    View
    6
    D
    der_akinator
    Update
    • unified boot image (tested on los-20221227 (OOS 12) and latest crdroid (OOS 13))
    • update usb/mtp stuff
    • exclude "/data/system/users/0/package-restrictions.xml" from backup
    Testers for the unified boot image are welcome, especially OP9 users. I think for existing backups "/data/system/users/0/package-restrictions.xml" has to be deleted manually after restore, but I haven't tested it.

    16-05-23 - Google Drive

    drive.google.com drive.google.com
    View
    5
    D
    der_akinator
    Of course, I'm talking about his existing device tree. But enough with Samsung.
    View
  • 54
    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 OP9 pro, but it was confirmed to work on regular OP9 too.

    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.

    Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.

    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.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
      1. Don't reboot
      2. Rename downloaded Magisk.apk to Magisk.zip
      3. Open Magisk app
      4. Select Modules tab
      5. Click "Install from storage"
      6. Select Magisk.zip
    2. Option for users with other custom recoveries but without root:
    1. Download the twrp-installer zip
    2. Reboot to recovery
    3. Flash it with "adb sideload twrp-installer*.zip"
    4. Reboot to recovery
    5. Reflash your custom kernel and Magisk.apk if previously installed
    3. Option is universal:
    1. Download 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.apk if previously installed

    Try without installation:
    1. Download boot.img
    2. Reboot to bootloader
    3. Run "fastboot boot boot.img" with the boot image

    Uninstall:

    Just flash the boot partition with your current ROMs boot image with the following steps.
    Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
    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. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.

    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 should work out of the box, but if you have issues 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.

    If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.

    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

    How to use MTP, adb and fastbootD:

    Windows:
    Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
    You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.

    To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.

    Steps for choosing a specific driver (no the exact wording):
    1. Connect phone in specific mode
    2. Open device manager
    3. Right click on phone either under "Android device" or "USB device", depending on mode
    4. Select "update driver"
    5. Select 2. option "browse my computer"
    6. Select "pick from available drivers"
    7. Pick driver according to above description
    Linux:
    1. Intall the fastboot and adb packages for your distribution
    2. Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
    3. Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"

    Source Code:

    Bugs:
    • Permanent installation alongside TMO stock isn't possible
    • Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
    • In case you notice anything else please let me know.
    If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.

    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!

    22-12-30 - 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
    10
    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