Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Samsung S9+ encryption silently fails

  • /e/ version: e-0.7-o-2020031044619-dev-star2lte.zip
  • Device model: Samsung S9+ (G695F)
  • When it started to occur: After fresh installation
  • Reproducible with the last /e/ version: YES, it is latest stable
  • Reproducible with LineageOS: YES (15.1)

Summary

Attempt to encrypt the phone unsuccessful

  • The device is unusable
  • The bug is the source of a data loss or a big waste of time
  • The bug concerns a third-party application
  • The bug concerns security
  • [?] The bug concerns privacy

The problem

Steps to reproduce

  1. Turn on the phone
  2. Unlock screen
  3. Navigate Settings -> Security & Privacy -> Encryption & Credentials -> Encrypt phone
  4. Click "ENCRYPT PHONE" button
  5. Enter PIN code
  6. Click "ENCRYPT PHONE" button (again)

What is the current behavior?

  1. Android logo picture shows up for a few seconds
  2. Phone reboots
  3. Phone is NOT encrypted

What is the expected correct behavior?

  1. Android logo picture shows up
  2. Phone reboots
  3. Phone is encrypted

Technical informations

Relevant logs (adb logcat)

03-11 19:42:44.949  4351  5846 I ActivityManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from uid 1000
03-11 19:42:46.281  4351  5128 D CryptdConnector: SND -> {6 cryptfs setfield PatternVisible 0}
03-11 19:42:46.282  4351  4503 D CryptdConnector: RCV <- {200 6 0}
03-11 19:42:46.283  4351  5128 D CryptdConnector: SND -> {7 cryptfs setfield PasswordVisible 1}
03-11 19:42:46.283  4351  4363 I ActivityManager: START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from uid 1000
03-11 19:42:46.283  4351  4503 D CryptdConnector: RCV <- {200 7 0}
03-11 19:42:46.287  4351  4363 D CryptdConnector: SND -> {8 cryptfs setfield SystemLocale en-GB}
03-11 19:42:46.287  4351  4503 D CryptdConnector: RCV <- {200 8 0}
03-11 19:42:46.288  4351  5128 I ActivityManager: Killing 5416:android.process.acore/u0a1 (adj 906): empty #17
03-11 19:42:47.009  4351  5846 D CryptdConnector: SND -> {9 cryptfs enablecrypto inplace pin [scrubbed]}
03-11 19:42:47.009  4351  4503 D CryptdConnector: RCV <- {200 9 0}
03-11 19:42:47.011  3997  6058 E Cryptfs : Bad magic for real block device /dev/block/platform/11120000.ufs/by-name/USERDATA
03-11 19:42:47.011  3997  6058 E Cryptfs : Orig filesystem overlaps crypto footer region.  Cannot encrypt in place.
03-11 19:42:47.035  3997  6058 E ProcessKiller: Process zygote64 (4069) has open filemap for /data/dalvik-cache/arm64/system@framework@boot.art

Relevant screenshots

N/A

Solutions

Phone is functioning fine after it reboots. However it is NOT encrypted. Consequential attempts fail in the same manner. Rebooting into safe mode and encrypting from there does not help either.

This post seems to be describing similar issue and fix: https://github.com/CyanogenMod/android_device_motorola_xt907/issues/3

Edited by chocko