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

Search This thread

ThePresence

Senior Member
May 24, 2011
1,073
233
31
Mumbai
OnePlus 9 Pro
Sounds like you flashed it incorrectly then... If you're trying to use Lineage Recovery then follow the flashing instructions on their OP9Pro wiki page. Also that's the end of our troubleshooting here since it's not TWRP's fault you didn't format data when switching from custom to stock ROM.

I flashed it from TWRP only. I'm now trying to flash lineage.
 

der_akinator

Senior Member
Mar 27, 2015
127
167
Berlin
OnePlus 3T
OnePlus 9 Pro
Works great on 9 pro oos13 F17. One issue I've noticed is factory data reset doesn't work until you unmount and mount data. Also "Failed to mount '/vendor_dlkm ' ( Block device required" showed but doesn't seem to cause any issues.
Data restore worked didn't try to restore super.img yet tho.
It does work installing .img from internal storage. Tried super.img and boot.img both successful.
Could you safe the logcat output from the factory reset problem? Otherwise I can't do much. The vendor_dlkm thing is already listed at bugs but isn't problematic.

I didn't know twrp can flash super images. Do you think it's possible by directly flashing super to switch from custom roms back to stock? It seems that thsi is currently only possible with the MSM tool. Maybe I will try that.
 

JWnSC

Senior Member
Jul 9, 2010
514
281
Virginia Beach
Could you safe the logcat output from the factory reset problem? Otherwise I can't do much. The vendor_dlkm thing is already listed at bugs but isn't problematic.

I didn't know twrp can flash super images. Do you think it's possible by directly flashing super to switch from custom roms back to stock? It seems that thsi is currently only possible with the MSM tool. Maybe I will try that.
Not near a PC currently I'll grab log later. You would need more than super.img (boot, dtbo,vendor_boot..ect)to switch from customs back to stock. If you create a flashable.zip it's possible. Most customs that are out lately have fw included. I've used twrp to flash A12 & A13 customs.. Even though it's not recommended😅 stay decrypted though so it's easier to switch between roms.
Recently flashed an ext4 r/w oos13 super.img(converted from erofs) using this twrp with no issues.
I'm only using fastboot and recovery to flash between stock and customs. If you need anything to test let me know. Thanks for your work 👍
 
Last edited:
  • Like
Reactions: der_akinator

TheSayaMan

Senior Member
Sep 12, 2016
887
374
OnePlus 9 Pro
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.
 

Skynet30

Member
Jul 27, 2014
38
14
I have TWRP, Magisk and OOS F.17 on my 2nd device. It is running w/o issues, I'm just wondering if there is something to take into account with OTA updates? My gut tells me I should only install full .zips from oxygen updater since TWRP and Magisk alter the boot.img and the image restore option in Magisk would only "restore" the boot.img to a state that still has twrp in it and incremental OTA would fail. Correct?

Update procedure should then be:
1. install the full zip from Oxygen Updater
2. install magisk to "inactive" slot
3. reboot to system
4. install TWRP zip from Magisk Manager
5. profit?
 

TheSayaMan

Senior Member
Sep 12, 2016
887
374
OnePlus 9 Pro
I have TWRP, Magisk and OOS F.17 on my 2nd device. It is running w/o issues, I'm just wondering if there is something to take into account with OTA updates? My gut tells me I should only install full .zips from oxygen updater since TWRP and Magisk alter the boot.img and the image restore option in Magisk would only "restore" the boot.img to a state that still has twrp in it and incremental OTA would fail. Correct?

Update procedure should then be:
1. install the full zip from Oxygen Updater
2. install magisk to "inactive" slot
3. reboot to system
4. install TWRP zip from Magisk Manager
5. profit?
The OTA would definately fail if you have the T-Mobile variant, but not on the Global variant. Not sure about the India, or Europe variants. If you have the T-mobile variant, it won't work because you have to install update first before you install magisk to inactive slot and it will detect root and fail. However the Global version will work and I'm not sure of the rest. Wouldn't hurt to try. Won't brick your phone for trying, it will just fail.
 
  • Like
Reactions: Skynet30

rboone18

Senior Member
Jan 16, 2007
241
38
OnePlus 8 Pro
OnePlus 9 Pro
I always did boot twrp.img or flash twrp.img or million other steps. Right now I am after get gf her Christmas present next week having to replace USB port. Not sure exactly , I don't do hardware got someone locally going to put new one in
 

TheSayaMan

Senior Member
Sep 12, 2016
887
374
OnePlus 9 Pro
Unfortunately I had to give up on this because every time I flash a custom rom update, my phone bootloops and ultimately I have to factory reset, format data and start all over. Custom recovery works fine with updates. reboot to bootloader, fastboot --set-active=other then reboot to recovery, adb sideload rom, reboot recovery, adb sideload gapps. reboot to system, no issues. I tried all recommendation to install via twrp will all failures. I reboot to twrp, install update rom, it automatically flashes to opposite slot, I reboot twrp, install gapps, phone boots up with all kinds of force closes. I've tried flashing update then not rebooting and then flashing gapps and doesn't boot at all. I give up!! Staying on custom recovery. Too bad because it would be nice to not use my computer for updates.
 

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.