[G3 Original Android Development] engmia:
[MENTION=4574857]finnq[/MENTION] Okay now I've ran into the following scenario (weekly from 02.13):

Had a password prior to encryption -> Phone rebooted and showed XX minutes left --> After it finished, it did reboot automatically -> Upon first boot, it accepted the password, but it said the data is corrupted -> Reboot the system once more -> It accepts the password correctly now, however if you go into recovery, it will not accept it (says wrong password, even if the pass is correct). -> The workaround is to go to the Settings menu and re-set you password again, and make sure to choose the "Enable password at boot" message.

Changing encryption password works.

Revoking password feature, does not.

Also when changing encryption password, if you click the back button (without inputting a password), it actually asks for a new password as if you've typed the right password. Fortunately it doesn't actually change the encryption password, even though it seems like it does, so it's only a minor bug.

So in total, there's 2 scenarios, if you don't have a password prior, you'll need to reboot manually. If you do have a password prior, you'll need to re-set the password from the settings menu.

Keep in mind that I haven't retested the scenario encryption without a pass on the latest weekly from 02.13.

----------------------------------------------------------

No, the problem is not in Lineage OS, it's in TWRP. So it's TWRP that needs to be updated, not Lineage. Read below for information how to get everything up and running successfully (including recovery)

[MENTION=4272903]NightWolf1396[/MENTION]

Here is a guide how to get encryption set-up on the device, and how get TWRP to properly decrypt the data:

1. Flash [MENTION=3362019]sleeplessnerd[/MENTION] custom TWRP recovery. As far as I'm aware, the only changes from official 3.0.2.0 are support decryption on current ROMS. If you don't do this step, or install another recovery you won't be able to decrypt the information from recovery (it will work fine in system though) and updating the device will become an unnecessary hard and time consuming task.

2. Set a password before encrypting. Yes, you can also use a PIN, but I would strongly advise against doing that. PIN numbers are extremely easy to crack with modern hardware, so it doesn't make much sense to use such a weak method for security. Google also allow unlocking your device with a trusted voice, but my friend manages to do unlock it with his voice. And we don't even sound alike. In my humble opinion if you use a PIN you are merely slowing down your boot times for no reason.

Make sure you also use a strong and unique password.

3. Start the encryption procedure. Your device will reboot and ask for a PIN. The next display will show you how much time is there left for the encryption to finish. Wait for it to finish, and the device will reboot automatically.

4. Upon first reboot, it will accept your password and say it is correct but your data is corrupted. Ignore this message and click reboot. It will reboot into recovery (there it will say your password is wrong -- ignore that too) and you just click the cancel button and reboot the system. Enter your password and on second boot everything will be okay and your data will be successfully decrypted.

5. Go into the Settings menu, and re-set your password. Before asking for a new pass, it will ask you if you want to use the password before booting the device, select yes.

6. Now you can successfully decrypt both from recovery and from the system.

Bonus: If you want to change your password -- for the encryption password use the new menu in the encryption tab, and for the system password re-set it from the lock screen menu.