Ok, next try on encryption … coming from an encrypted phone with LineageOS 14.1. 20180711 …
(TL;DR: Encryption works when prepared the right way, but TWRP can’t handle it afterwards.)
- Disassembled both new camera modules.
(On another try I’m happy to report that you can leave the top module in the phone, disassembling the main camera module was enough for me.)
TWRP 3.2.2-0
- Destroyed the LUKS header to really seriously get rid of prior encryption (Advanced - Terminal -
dd if=/dev/zero of=/dev/block/mmcblk0p20 bs=4096 count=512) - Formatted data to get a valid Ext4 again (Wipe - Format Data).
- Resized data to not regret later that I left that out (Wipe - Advanced Wipe - data - Repair or Change File System - Resize File System)
- Wiped everything except Micro SD card (Wipe - Advanced Wipe).
Rebooted into TWRP to make sure encryption is gone (no request for the encryption password when starting).
-
Checked file systems (visible via Wipe - Advanced Wipe - [file system of choice] - Repair or Change File System) …
system: ext4
cache: ext4
data: ext4 -
Installed test build (Install - Select Storage etc.).
Rebooted into LineageOS 15.1
- Set Screen Lock to None/ a PIN/ a password (Settings - Security & privacy - Screen lock)
- Encryption (Settings - Security & privacy - Encryption & credentials - Encrypt phone)
Showed the Android robot for a moment, then rebooted and in the process somewhen showed the Android robot again and encrypted the phone.
So far, so good 
.
But … @z3ntu TWRP 3.2.2-0 can’t handle this encryption yet?
It prompts for the password (even if the setting in LineageOS 15.1 was “None”), but fails to decrypt. Even if I set a password (not a PIN like I used to) for the encryption in LineageOS 15.1 and I’m trying the correct password in TWRP.
And … @chrmhoffmann While a start pattern works, I noticed that regardless of whether I set a start PIN or a start password the phone then prompts me for a PIN and I can only enter numbers. Which isn’t intended when having set a password, I guess?