this device is encrypted with FDE full-disk-encryption. depending on how you installed Magisk the forceencrypt= flag is gone. that's what the "crypto key location" refer. edit your fstab and restore encryptable= flag that might help to use Samsung encryption in boot mode. but TWRP is most likely not able to decrypt anyway, so there is no benefit of ...
I was in a similar issue on a Nokia running a stock ROM. Basically Magisk module killed my phone and the TWRP won't allow decryption.
I was able to boot successfully to system again by.. Removing Magisk, because in the absence of Magisk, the Magisk modules shouldn't load and hence the system should boot just fine. I did that by flashing my stock boot image....
I don't think is documented anywhere the syntax but looking at this code
I was able to set a different password.
Initially I used a PIN for unlocking, so the command to run on a terminal on lineageos 17.1 as root is:
vdc cryptfs changepw TYPEOFNEWPASSWORD OLDPASSWORD NEWPASSWORD
/boot, /system, /vendor, /vbmeta and ODM Partitions are protected by android verified boot (AVB). They are not encrypted but their integrity is verified during boot. Any modification to these partitions will halt the boot flow and brick the device. At this point without EDL mode, you won't be able to flash stock OS to unbrick it.
AVB verifies vbmeta ...
So I had the same problem with an employee to whom I had given a phone. She kept forgetting to charge the phone, so when it rebooted after charging she had to hand me the phone so I could type in the password and then switch to her secondary account. Tired of this, I read some articles about multiple users. I couldn't find the right answers (or didn't ...
Your phone launched with Android 10.
In Android 10 Full Disk Encryption has been dropped in favor of File Based Encryption
You no longer need to "encrypt a disk" as everything is encrypted provided you have a lock screen with pin/fingerprint/etc. in Android 10
In the settings where you choose a new PIN/pattern/passwords it said something like 'Because you enabled an accessibility feature you're PIN won't be used for enhanced encryption protection'.
I had to disable Lastpass auto-fill and my phone asked for my PIN at startup again.
Copied from comments:
TWRP needs a working firmware for decryption. If system vendor or
modem is wiped, the workaround is to format userdata in order to
remove encryption completely, so TWRP can mount it unencrypted.
Through experimenting I was able to get it to work by doing the following. First, try reflashing just TWRP in fastboot mode: fastboot flash ...
Actually Android 6.0 had Full Disk Encryption as specified in the Android 6.0 Compatibility Definition Document - Section 9.9 Full Disk Encryption with exceptions if the hardware was insufficient to perform the operation.
So your case of a not specified lockscreen password is actually called out:
If the user has not specified a lockscreen passcode or ...
Searching a lot over the web I saw this question and by reading the entire post, and in particularly this answer https://android.stackexchange.com/a/176124/77853 I brought back my phone to life and without losing anything !
What I had to do was (as suggested in the answer) repair the /data partition plus the /system partition !
You cannot encrypt data which has been deleted. As Tetsujin mentioned, you are meant to encrypt the data beforehand. You can then discard the encryption key.
What you want to accomplish, then—ensure that cleartext deleted data be unrecoverable—is inherently difficult. It's not trivial to hide these things from experienced forensic laboratories.
That said, ...
First let's have a look why it is not (yet) possible to mount encrypted userdata partition from TWRP especially on Samung devices.
Encryption is hardware-backed in TEE and therefore vendor specific. Furthermore ...
... some vendors such as Samsung use their own encryption techniques. Without heavy deconstruction/decompiling of custom library blobs, and ...
Good news: trying the following command successfully decrypted my SD card without any errors:
sudo dmsetup create crypt1 --table "0 `sudo blockdev --getsize /dev/mmcblk0p2` crypt aes-cbc-essiv:sha256 [16-BYTE HEX KEY] 0 /dev/mmcblk0p2 0"
A couple of minor issues:
sudo mount -t /dev/mmcblk0p2/crypt1 /media/mint/sd returned the error mount: /media/...
I ended up using Frida to hook sqlite3_key dynamically and got the encryption key. Simple enough.
Brief steps I took:
Setup Frida to connect to your Android device
# Attach to target app
session = frida.get_usb_device().attach("cn.com.company_name.app_name")
# Load ...
I had the same problem, and what worked for me, I formatted it from command line, so while in fastboot mode I typed:
fastboot format userdata
Then I flashed TWRP and rebooted into it and the files in the storage were all showing, all was working.