Development [RECOVERY][3.7.1_12-0][OFFICIAL][UNIFIED] TWRP with A12-A14 encryption support

Search This thread
By:
Advanced…
T

TheSayaMan

Senior Member
Sep 12, 2016
1,923
1,093
OnePlus 9 Pro
OnePlus 11
Anyone know the proper way to update a ROM? I am rebooting to TWRP recovery, I install updated ROM, install TWRP zip, then install gapps. When I reboot to system, I get a ton of crashes, play store, play services, messages app, etc. If I do a clean install this same way it works fine with no issues. I would rather not have to do a clean install everytime I update crDroid. I would appreciate any assistance. Thank you!!
 
D

der_akinator

Senior Member
Mar 27, 2015
253
454
Berlin
OnePlus 3T
OnePlus 9 Pro
TheSayaMan said:
Anyone know the proper way to update a ROM? I am rebooting to TWRP recovery, I install updated ROM, install TWRP zip, then install gapps. When I reboot to system, I get a ton of crashes, play store, play services, messages app, etc. If I do a clean install this same way it works fine with no issues. I would rather not have to do a clean install everytime I update crDroid. I would appreciate any assistance. Thank you!!
Click to expand...
Click to collapse
After update you have to reboot to recovery again to mount partitions with the slot you have installed the update to and install gapps to them. But sometimes it helps for me to flash gapps a second time if the crashes still occur.
 
mettis88@gmail.com

mettis88@gmail.com

Senior Member
Dec 25, 2013
99
56
35
Pavlodar
4pda.ru
der_akinator said:
After update you have to reboot to recovery again to mount partitions with the slot you have installed the update to and install gapps to them. But sometimes it helps for me to flash gapps a second time if the crashes still occur.
Click to expand...
Click to collapse
1. Install ROM
2. Install TWRP
3. Reboot to recovery
4. Install gapps
5. Install magisk
Correct instructions for updating ROM with gapps?
 
B

bubobih

Senior Member
Mar 25, 2012
93
14
OnePlus 9 Pro
Hello all, does this work on oxygen a 13 official rom? If works does this make factory data? If not what is the best way to install it? Regards
 
F

Flecto

Member
Dec 16, 2021
12
16
Thank you so much @der_akinator! I have tested your build on my OnePlus 9 Pro with stock OxygenOS 12 (C.48) and stock OxygenOS 13 (F.17).

Decryption works in both cases (I only have one default user, user 0, and I use a numeric PIN). I do get the error message "Failed to mount '/vendor_dlkm' (Block device required" (rest is cut off) a few times at the beginning and also when starting a backup. But I think that has already been discussed in earlier messages and can safely be ignored, as I understand.

With OOS 12 I was able to do a backup successfully. But with OOS 13 I ran into the "createTarFork() process ended with ERROR: 255" issue that others have seen as well. As with the others who encountered it, I hit it when backing up /data/fonts/files. While TWRP recovery was open, I opened a shell with adb to figure out what is going on. The /data/fonts/files folder looked like this for me:


Code: 
OnePlus9Pro:/data/fonts/files # ls -lah
total 27K
drwxrwx--x 9 system system 3.3K 2022-12-03 13:16 .
drwxrwx--x 4 root   root   3.3K 1970-12-21 00:39 ..
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~Dq2S8kVqf-Dc6LKcUPIxAg==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~MH9JbGNsVi5FNqTFxYOkzw==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~PDIpcvjXWCGB0L9vu4bRVQ==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~i9uxPse9gJwQHVMzvWO_ew==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~ifyxiQTJ82tMnh85d-S_oQ==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~vVr66c0Pht6y0-g70ZEL1A==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~zZmOMCJqZPx76zYvxoauLA==
Inside each directory is a font file and those files cannot be read:
Code: 
OnePlus9Pro:/data/fonts/files # cat */*
cat: ~~Dq2S8kVqf-Dc6LKcUPIxAg==/GoogleSansText-Medium.ttf: Required key not available
cat: ~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf: Required key not available
cat: ~~PDIpcvjXWCGB0L9vu4bRVQ==/GoogleSans-Regular.ttf: Required key not available
cat: ~~i9uxPse9gJwQHVMzvWO_ew==/GoogleSansText-Bold.ttf: Required key not available
cat: ~~ifyxiQTJ82tMnh85d-S_oQ==/GoogleSans-Medium.ttf: Required key not available
cat: ~~vVr66c0Pht6y0-g70ZEL1A==/GoogleSans-Bold.ttf: Required key not available
cat: ~~zZmOMCJqZPx76zYvxoauLA==/GoogleSansText-Regular.ttf: Required key not available
So these fonts just cannot be read and that's why the backup failed. It failed exactly when it tried to read the first of those files (which happened to be /data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf. Here is the relevant entry from recovery.log:
Code: 
...
I:addFile '/data/fonts' including root: 1
  ==> set selinux context: u:object_r:system_data_file:s0
found fscrypt policy '/data/fonts' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
found fscrypt policy '/data/fonts/files' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
found fscrypt policy '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
I:Error adding file '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf' to '/data/media/0/TWRP/BACKUPS/fd144c5b/2022-12-03--12-20-33/data.f2fs.win019'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/fd144c5b/2022-12-03--12-20-33/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
...
After deleting the entire folder /data/fonts/files, the backup worked. It would probably be great if the TWRP backup code would be able to catch this error and continue with just throwing a warning instead of crashing. But I expect that might be something that needs to be fixed in the common TWRP source since it may not be specific to the OnePlus 9 Pro device.

By the way, there are plenty of files listed in the recovery.log that have "found fscrypt policy" and they all seem to be backed up without issue. Some of those files are even within a folder with a scrambled name (starting with ~~ and ending with ==). So there is something special about these font files.

For those interested, here is how I performed the upgrade. I started on OxygenOS 11.

1) Install the system update from the settings (it showed the update was about 4 GB large and called C.48)
2) BEFORE rebooting after the upgrade: use Magisk app to flash the twrp-installer zip from this thread (will flash to slot A and B)
3) BEFORE rebooting using the Magisk app reinstall Magisk; I did BOTH direct install (will flash to active slot) and install after OTA (will flash to inactive slot)
4) NOW reboot and verify everything works
5) Then the system upgrade showed me the update to OOS 13 (F.17) but it showed it was only 1-poin-something GB in size. So I decided to use the Oxygen Updater app, which downloaded the full F.17 upgrade (over 4 GB). I followed the instructions in Oxygen Updater to apply the update (had to install OPLocalUpgrade)
6) Repeat steps 2 and 3 above.
7) Now reboot, verify everything works and do another backup in TWRP
 
  • Like
Reactions: Smedslund, Aqq123 and der_akinator
F

Flecto

Member
Dec 16, 2021
12
16
bubobih said:
Hello all, does this work on oxygen a 13 official rom? If works does this make factory data? If not what is the best way to install it? Regards
Click to expand...
Click to collapse
See my post above. It works for me with OOS 13 (F.17), but I ran into the issue with the fonts during backup. Which I overcame by deleting /data/fonts/files.
 
D

der_akinator

Senior Member
Mar 27, 2015
253
454
Berlin
OnePlus 3T
OnePlus 9 Pro
Flecto said:
Thank you so much @der_akinator! I have tested your build on my OnePlus 9 Pro with stock OxygenOS 12 (C.48) and stock OxygenOS 13 (F.17).

Decryption works in both cases (I only have one default user, user 0, and I use a numeric PIN). I do get the error message "Failed to mount '/vendor_dlkm' (Block device required" (rest is cut off) a few times at the beginning and also when starting a backup. But I think that has already been discussed in earlier messages and can safely be ignored, as I understand.

With OOS 12 I was able to do a backup successfully. But with OOS 13 I ran into the "createTarFork() process ended with ERROR: 255" issue that others have seen as well. As with the others who encountered it, I hit it when backing up /data/fonts/files. While TWRP recovery was open, I opened a shell with adb to figure out what is going on. The /data/fonts/files folder looked like this for me:


Code: 
OnePlus9Pro:/data/fonts/files # ls -lah
total 27K
drwxrwx--x 9 system system 3.3K 2022-12-03 13:16 .
drwxrwx--x 4 root   root   3.3K 1970-12-21 00:39 ..
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~Dq2S8kVqf-Dc6LKcUPIxAg==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~MH9JbGNsVi5FNqTFxYOkzw==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~PDIpcvjXWCGB0L9vu4bRVQ==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~i9uxPse9gJwQHVMzvWO_ew==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~ifyxiQTJ82tMnh85d-S_oQ==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~vVr66c0Pht6y0-g70ZEL1A==
drwx--x--x 2 system system 3.3K 2022-12-03 13:16 ~~zZmOMCJqZPx76zYvxoauLA==
Inside each directory is a font file and those files cannot be read:
Code: 
OnePlus9Pro:/data/fonts/files # cat */*
cat: ~~Dq2S8kVqf-Dc6LKcUPIxAg==/GoogleSansText-Medium.ttf: Required key not available
cat: ~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf: Required key not available
cat: ~~PDIpcvjXWCGB0L9vu4bRVQ==/GoogleSans-Regular.ttf: Required key not available
cat: ~~i9uxPse9gJwQHVMzvWO_ew==/GoogleSansText-Bold.ttf: Required key not available
cat: ~~ifyxiQTJ82tMnh85d-S_oQ==/GoogleSans-Medium.ttf: Required key not available
cat: ~~vVr66c0Pht6y0-g70ZEL1A==/GoogleSans-Bold.ttf: Required key not available
cat: ~~zZmOMCJqZPx76zYvxoauLA==/GoogleSansText-Regular.ttf: Required key not available
So these fonts just cannot be read and that's why the backup failed. It failed exactly when it tried to read the first of those files (which happened to be /data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf. Here is the relevant entry from recovery.log:
Code: 
...
I:addFile '/data/fonts' including root: 1
  ==> set selinux context: u:object_r:system_data_file:s0
found fscrypt policy '/data/fonts' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
found fscrypt policy '/data/fonts/files' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
found fscrypt policy '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==' - '2DK' - '2312b5d79eb868cb6ff02d908d0fe1a7'
I:addFile '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf' including root: 1
  ==> set selinux context: u:object_r:font_data_file:s0
I:Error adding file '/data/fonts/files/~~MH9JbGNsVi5FNqTFxYOkzw==/NotoColorEmoji.ttf' to '/data/media/0/TWRP/BACKUPS/fd144c5b/2022-12-03--12-20-33/data.f2fs.win019'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/fd144c5b/2022-12-03--12-20-33/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
...
After deleting the entire folder /data/fonts/files, the backup worked. It would probably be great if the TWRP backup code would be able to catch this error and continue with just throwing a warning instead of crashing. But I expect that might be something that needs to be fixed in the common TWRP source since it may not be specific to the OnePlus 9 Pro device.

By the way, there are plenty of files listed in the recovery.log that have "found fscrypt policy" and they all seem to be backed up without issue. Some of those files are even within a folder with a scrambled name (starting with ~~ and ending with ==). So there is something special about these font files.

For those interested, here is how I performed the upgrade. I started on OxygenOS 11.

1) Install the system update from the settings (it showed the update was about 4 GB large and called C.48)
2) BEFORE rebooting after the upgrade: use Magisk app to flash the twrp-installer zip from this thread (will flash to slot A and B)
3) BEFORE rebooting using the Magisk app reinstall Magisk; I did BOTH direct install (will flash to active slot) and install after OTA (will flash to inactive slot)
4) NOW reboot and verify everything works
5) Then the system upgrade showed me the update to OOS 13 (F.17) but it showed it was only 1-poin-something GB in size. So I decided to use the Oxygen Updater app, which downloaded the full F.17 upgrade (over 4 GB). I followed the instructions in Oxygen Updater to apply the update (had to install OPLocalUpgrade)
6) Repeat steps 2 and 3 above.
7) Now reboot, verify everything works and do another backup in TWRP
Click to expand...
Click to collapse
First of all thanks for your extensive test and documentation.

About vendor_dlkm:
The current solution isn't very nice, but I have to specify vendor_dlkm in fstab to mount it on device with LOS based ROMs because that's the partition containing necessary kernel modules for USB OTG, battery status etc. Unfortunately OOS isn't using a separate partition for that and stores modules directly on the vendor partition. Luckily this only throws an error but doesn't crash. To fix this I would have to build two versions with and without the vendor_dlkm entry in recovery.fstab.

About failing backups:
I have read a bit about fscrypt which is used for android's encryption. The "fscrypt policy" lines in recovery.log only give information about which policy and key is used to encrypt a directory and all subdirectories or single files. Whats interesting is the 32 character string at the end of each line that is an ID of the key used for encryption. "2DK" just means FBEv2 encryption method is used. I think /data/fonts/* is encrypted with a different key than the one derived by your initial password/pattern input. You can check that by comparing the ID of /data/fonts/* with an ID of any other directory under /data.
Reading directories that can't be decrypted by TWRP doesn't seem to be problematic but accessing one of those files is. A possible fix for this could be to store key IDs that TWRP has access to and compare them with the key ID of the currently accessed directory. If it's a match continue else backoff and try next node.
I will try to apply this idea to TWRP's tar wrapper next week.
 
Last edited:
  • Like
Reactions: gsser, SaintZ93, Aqq123 and 1 other person
F

Flecto

Member
Dec 16, 2021
12
16
der_akinator said:
Reading directories that can't be decrypted by TWRP doesn't seem to be problematic but accessing one of those files is. A possible fix for this could be to store key IDs that TWRP has access to and compare them with the key ID of the currently accessed directory. If it's a match continue else backoff and try next node.
I will try to apply this idea to TWRP's tar wrapper next week.
Click to expand...
Click to collapse
I don't know what the code looks like, but if there is a way to catch the error, that might be easier than trying to figure out if the key is available. For each file, just catch if it wasn't able to be added and if so, print a warning and move on. But again, I don't know the code, so maybe that's not feasible...
 
D

der_akinator

Senior Member
Mar 27, 2015
253
454
Berlin
OnePlus 3T
OnePlus 9 Pro
Flecto said:
I don't know what the code looks like, but if there is a way to catch the error, that might be easier than trying to figure out if the key is available. For each file, just catch if it wasn't able to be added and if so, print a warning and move on. But again, I don't know the code, so maybe that's not feasible...
Click to expand...
Click to collapse
Yes, thought about that too. It seems to be a bit more inefficient but makes it also easier to implement for non encrypted devices. I also have to investigate further to find a point I can apply it.
 
  • Like
Reactions: osm0sis
D

der_akinator

Senior Member
Mar 27, 2015
253
454
Berlin
OnePlus 3T
OnePlus 9 Pro
TheSayaMan said:
Didn't work for me. I got stuck factory resetting and starting over. Frustrating.
Click to expand...
Click to collapse
Yes you are right direct reboot to recovery and installing gapps doesn't work for me on crdroid either. But as I said if you get crashes after rebooting to system. Just reboot again to recovery and flash gapps a second time. I had the same problem with crashing gapps and official crdroid recovery too.
 
T

TheSayaMan

Senior Member
Sep 12, 2016
1,923
1,093
OnePlus 9 Pro
OnePlus 11
der_akinator said:
Yes you are right direct reboot to recovery and installing gapps doesn't work for me on crdroid either. But as I said if you get crashes after rebooting to system. Just reboot again to recovery and flash gapps a second time. I had the same problem with crashing gapps and official crdroid recovery too.
Click to expand...
Click to collapse
I tried that. I tried flashing gapps several times then gave up. Was still crashing.
 
IamTheBRAVE

IamTheBRAVE

Senior Member
Jan 29, 2017
796
649
Morocco
Samsung Galaxy Tab 4
Samsung Galaxy A20
TheSayaMan said:
I tried that. I tried flashing gapps several times then gave up. Was still crashing.
Click to expand...
Click to collapse
Crdroid dev stated he uses his own blend of nikgapps-core so it might interfere with the brand of gapps you're flashing.
Edit: @der_akinator since Crdroid already has gapps, you wouldn't need to flash it.
 
Last edited:
  • Like
Reactions: der_akinator, Smedslund and osm0sis
You must log in or register to reply here.

Similar threads

eng.stk
Development [KERNEL] [blu_spark r166 OP9/Pro] [A14 Custom]
Replies
1K
Views
151K
xlinux_
xlinux_
T
Development OP9PRO-LEMONADEP-OPCAM-A14-ROM-WATCHDOGS-KERNELSU-APR 24, 2024
Replies
1K
Views
118K
T
TheSayaMan
Nebrassy
Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Replies
631
Views
114K
trulane
trulane
chandu dyavanapelli
Development [ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][Android 14]Nameless AOSP[2024/03/09]
Replies
2K
Views
271K
U
unknown_2
OPTeam
  • Sticky
General [OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Replies
940
Views
285K
Nimueh
Nimueh

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    cerj
    cerj
    der_akinator said:
    The bad news is that the OOS 14 decryption issue is a kernel/dtb issue, which requires more time to hopefully identify and fix.

    The good news is that, you can use an unofficial OOS 14 boot image, which is linked below, to fastboot boot and decrypt data properly. I don't think it's compatible with OOS 13 firmware-based custom ROMs, but haven't tested that.
    Permanent installation with the official boot image and zip installer still works, but throws a lot of error messages.

    24-02-27-OOS-14 - Google Drive

    drive.google.com drive.google.com
    Click to expand...
    Click to collapse
    Is the boot.img in your G drive folder TWRP that I can use in fastboot? Thank you
    View
  • 56
    D
    der_akinator
    This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12-14 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 Android 11 encryption, please use the official Android 11 based builds by     @Nebrassy from:

    Download:

    Unofficial OOS 14 images:

    24-02-27-OOS-14 - Google Drive

    drive.google.com drive.google.com

    New official images:

    OnePlus 9 Pro (lemonadep)

    Disclaimer:Team Win strives to provide a...
    twrp.me

    Old unofficial images:

    twrp-lemonadep - Google Drive

    drive.google.com drive.google.com

    Installation:

    Permanent installation is not possible with TMO 12 stock ROM installed. With TMO 13 stock it's possible, but it was reported that uninstalling causes issues. OOS 14 is currently not supported.

    OOS users should make a backup of boot before installation. Otherwise incremental updates can't be applied.

    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 TWRP boot image on your PC
    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 TWRP boot image on your PC

    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.

    Collection of OOS boot images:

    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
    OOS full OTA updates should work out of the box.
    For incremental OOS updates, you have to flash the original boot image. Your can follow this short guide and use the boot image from link in the uninstall section.

    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:

    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
    12
    D
    der_akinator
    Update
    • add Android 14 encryption support
    • sync all other changes
    I've done some quick tests with crdroid 9 (A13) and crdroid 10 (A14).

    23-11-19 - Google Drive

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

    23-02-04 - 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).

    23-02-08 - Google Drive

    drive.google.com drive.google.com
    View

New posts