At first I tried to encrypt using the UI but that somehow put the phone into a TWRP bootloop.
Later on I tried debugging it via adb. After executing vdc cryptfs enablecrypto wipe password <password> I see this error in the log:
03-26 17:31:02.388 I/Cryptfs ( 1653): Using scrypt for cryptfs KDF
03-26 17:31:02.918 D/BootAnimation( 4723): Use save memory method, maybe small fps in actual.
03-26 17:31:03.958 I/Cryptfs ( 1653): load_crypto_mapping_table: target_type = crypt
03-26 17:31:03.958 I/Cryptfs ( 1653): load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p25, extra_params =
03-26 17:31:08.961 E/Cryptfs ( 1653): Cannot load dm-crypt mapping table.
I was looking into the error cited there and found this:
E/Cryptfs ( 2221): Cannot load dm-crypt mapping table.
The actual encryption used for the filesystem for first release is 128 AES with CBC and ESSIV:SHA256. The master key is encrypted with 128 bit AES via calls to the openssl library.
This is done by enable CONFIG_CRYPTO_SHA256 in kernel.
Could that be the issue? Or am I fishing in the dark?
At first I tried to encrypt using the UI but that somehow put the phone into a TWRP bootloop.
Later on I tried debugging it via adb. After executing
vdc cryptfs enablecrypto wipe password <password>I see this error in the log:I was looking into the error cited there and found this:
Could that be the issue? Or am I fishing in the dark?
I was also doing some of the things mentioned here: http://android.stackexchange.com/questions/117405/how-do-you-encrypt-your-device-running-cyanogenmod-12-1
The data partition on /dev/block/mmcblk0p25 is ext4