If it's a normal partition and is normally flashed with "fastboot flash ... param.bin", it probably works. But I can't confirm it since I don't own a TMO device.
Development [RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
- Thread starter der_akinator
- Start date
osm0sis
Senior Recognized Developer / Contributor
Update
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.
- Fix backups and logs not accessible from system
14-03-23 - Google Drive
drive.google.com
The Restore list issue is still present, unfortunately.
Steps to reproduce:
1) Use Advanced > File Manager to ensure /sdcard/TWRP/.twrps is deleted
2) Reboot Recovery to ensure using /data/recovery/.twrps
3) Make a backup of something small for our testing, like boot partition
4) Advanced > Change TWRP folder to name: Recovery
5) Reboot to Recovery to start fresh
6) Check Restore list, it'll just show contents of /sdcard instead of actual backups
Last edited:
Sorry, I forgot to add latest patch. Latest build is now replaced with fixed version.
osm0sis
Senior Recognized Developer / Contributor
Update
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.
- Fix backups and logs not accessible from system
14-03-23 - Google Drive
Awesome! Can confirm it works as expected now.
Only thing I noticed is that there now seems to be a rogue empty TWRP folder created at /TWRP which I don't recall happening before.
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.
Edit:
This is also useful for custom ROMs, because it makes first boot faster and eliminates the need to reboot again.
Last edited:
Hey, quick question. To update this TWRP, when the OP says flash the twrp-installer.zip, that means flash the zip in TWRP, then reboot to recovery into said updated TWRP, correct? Just wanna be 100% sure, since this is my first A/B device (been using a OP5 since it was released and only JUST switched to a OP9). If I'm just updating TWRP, I don't need to flash to any specific slot, right? Since there's other ways to flash ZIPs, it seemed like a prudent question . . at least in my case.
Thanks you for this TWRP! It always nice to have a backup(s) of all of my partitions on my backup SSD, just in case my device decides to have a bad time! So thank you for your contributions to the community!
Thanks you for this TWRP! It always nice to have a backup(s) of all of my partitions on my backup SSD, just in case my device decides to have a bad time! So thank you for your contributions to the community!
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!
Thanks!
There is no changelog. You can either look for update posts which contain a summary of some changes or look into the git history.
I didn't know if it was only OOS 12 based a13 roms or OOS 13 based ones also
Hello! If not difficult, tell me. Is there a custom TWRP today, capable of not only creating a backup system, but also restore data from a backup? I have an OnePlus 9PRO phone, T-Mobile operator (LE-2127), Oxygenos, Android 12, the bootloader is unlocked, there is a root. Would be very grateful!
Have you tried to restore data from backup? If so, then on which version of TWRP and what specific sections of the system?
Similar threads
- Sticky
Top Liked Posts
-
3
I would also like to add my own two cents, as a senior UNIX/Linux system administrator, to these already helpful excerpts of information.
@PartyZone
Even if the stars could align and a decrypted version of the file that the pattern/pin is stored in could be found, one could never get the actual pattern/pin out of it; the reason being that the actual pattern/pin is being hashed (with blowfish/bcrypt being the latest trend) and usually salted too.
This means that when one enters a password/pattern/pin, the input is being hashed once more and compared against the stored hash. Hashing is typically considered to be a one-way process, which cannot be reversed (while in theory it technically could, it would require immeasurable processing power to do so).
As you also might've guessed, an added salt makes the possibility of a successful decryption even more unfathomable. (Further details and explanation can be found here)
As @der_akinator most eloquently and accurately put; an encryption process which could be reversed (at least not without an insurmountable cost), would defeat it's whole purpose and existence in the first place. -
6
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.6
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.6Update
- 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
16-05-23 - Google Drive
drive.google.com
5 -
54This 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
Download:
twrp-3.7.0-12.1 - Google Drive
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:
- Download the twrp-installer zip
- Flash it with Magisk manager or some other kernel flash utility
- 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.
- Don't reboot
- Rename downloaded Magisk.apk to Magisk.zip
- Open Magisk app
- Select Modules tab
- Click "Install from storage"
- Select Magisk.zip
- Download the twrp-installer zip
- Reboot to recovery
- Flash it with "adb sideload twrp-installer*.zip"
- Reboot to recovery
- Reflash your custom kernel and Magisk.apk if previously installed
- Download boot.img
- Reboot to bootloader
- Run "fastboot boot boot.img" with the boot image
- Go to Advanced > Flash Current TWRP
- Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
- Download boot.img
- Reboot to bootloader
- 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.
- Reboot to bootloader
- Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
- Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
TWRP Updates:
- Download and flash the twrp-installer zip
- 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):
- Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
- Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
- Reboot to system
- If Gapps packages keep crashing:
- Reboot to TWRP
- Flash Gapps again
- Reboot to system
[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
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
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):
- Connect phone in specific mode
- Open device manager
- Right click on phone either under "Android device" or "USB device", depending on mode
- Select "update driver"
- Select 2. option "browse my computer"
- Select "pick from available drivers"
- Pick driver according to above description
- Intall the fastboot and adb packages for your distribution
- Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
- Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
- TWRP: https://github.com/TeamWin/android_bootable_recovery
- Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
- Device Tree:
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.
Thanks to:
13Update
- /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.)
22-12-30 - Google Drive
drive.google.com
10Update
- 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)
08-02-23 - Google Drive
drive.google.com
10Update
- add vendor_boot and dtbo to backup targets
- add CPU temperature output
- fix vibration (still doesn't work in fastbootd mode)
04-02-23 - Google Drive
drive.google.com
10Good 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.
![[GR]Frostbyte](/data/avatars/s/4429/4429283.jpg?1685172710){kind=avatar}
