Unable to decrypt data with LineageOS 14.1-20170828-nightly and TWRP 3.1.1-0

[Fusl]

Setting up encryption on LineageOS installed on the Nextbit Robin seems to cause issues for TWRP trying to decrypt the partition.

What I tried so far:

• Set the pattern to represent the code "123456789", enabled pattern prompt during boot up, trying that pattern in TWRP, results in Failed to decrypt data
• Set the pattern to represent the code "123456789", enabled pattern prompt during boot up, trying to unlock with vdc over ADB, results in /sbin/sh: vdc: not found
• Set the passcode to 1234, disabled password prompt during boot up, TWRP asks for a passphrase (not a passcode), trying 1234 or default_password result in Failed to decrypt data

dmesg in the recovery prints this while trying to unlock the phone:

<3>[  119.776227] QSEECOM: qseecom_query_app_loaded: App id 3 (keymaster) already exists
<3>[  120.818700] QSEECOM: qseecom_query_app_loaded: App id 3 (keymaster) already exists

recovery log:

I:Set page: 'mount'
I:Set page: 'decrypt'
I:Set page: 'decrypt_pattern'
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
crypt_ftr->fs_size = 53239743
Using scrypt with keymaster for cryptfs KDF
Trying to convert ascii string of odd length
Failed to convert passwd from hex, using passwd instead
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Error starting keymaster signature transaction: -24
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 53239743
Using scrypt with keymaster for cryptfs KDF
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Error starting keymaster signature transaction: -24
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
Failed to decrypt data.

[spinda]

I've run into the same issue with lineage-14.1-20171114-nightly-ether. This means I'm unable to upgrade unless I decrypt my device first, then re-encrypt after the upgrade process completes. @deadman96385 and @Dees_Troy, are you still actively maintaining this?

[spinda]

...Ugh, replace "decrypt my device" with "perform a full wipe and reset", as Android doesn't offer a way to decrypt directly. Fantastic.

[spinda]

It would appear error code -24 corresponds to KM_ERROR_KEY_NOT_YET_VALID.

[spinda]

Looks like this happens because TWRP thinks it's sometime in 1970.

edit: Hmm, but setting the clock to the correct date and time via the terminal doesn't fix it...

[osopolar]

I have the same problem with my huawei honor 5 and LinageOS 14.20170809-NIGHTLY-kiwi. I wanted to update the OS to a new version and found that I cant decrypt the HD. Any workarounds? Or do I need to perform a full wipe?

Edit: Sorry, I just found the right issue for my phone. Anyway it seems to be a more general problem with TWRP.

[Alex9001]

Issue persists in 3.2.0-0