eufix-force-fbe-oreo not working since TWRP 3.3.1-1 for sagit

[shunf4]

TWRP 3.3.1-1 and above (at least for sagit) provided a broken sed executable, which fails to match \b to a word boundary. This caused eufix-force-fbe-oreo script entirely not to work.

Btw, TWRP 3.3.1-1 for sagit also fails to decrypt fbe-encrypted /data partition. If you are using a sagit device, DO NOT USE TWRP 3.3.1-1 or above!

[apemix2s]

I'm having the same issue on Mi Mix 2s (Polaris). I followed the instructions, ran the script (TWRP 3.3.1-1) and it is showing that my phone is not encrypted.

Any help would be much appreciated. I might try using a different recovery like OrangeFox, but not sure if that will make a difference.

[shunf4]

@apemix2s You could try TWRPs of lower versions, or check if there were any unofficial TWRPs specially customized for polaris. Hope it helps.

Try running sed "s/\b\(encryptable\)=/fileencryption=/g" <path of fstab.qcom> on a fresh install of xiaomi.eu under TWRP terminal, and see if the word encryptable is successfully replaced with fileencryption. If so, you got a good TWRP. Remember to do full backup of data!

[apemix2s]

Thanks. I'm using OrangeFox Recovery 10.0.

I tried running that file, and it did replace the word "encryptable" with "fileencryption". However, when I reboot into system (for the first time) and go to Settings -> Additional Settings -> Privacy -> Encryption & credentials, it still says "Phone not encrypted". Additionally, the "Encrypt device using Lock screen password" is greyed out. Very strange.

I noticed when I installed MIUI.eu stable 10.4, one of the lines that appeared on the installation process seemed to disable encryption and mess with the fstab.qcom file. Even after running the command you suggested to fix it, it doesn't seem to have worked.

Any other ideas?

[apemix2s]

AH! FINALLY! Just managed to boot in again, and this time it is encrypted.

Here's what I did:

• Install custom recovery - OrangeFox v10.0
• Reboot to recovery
• Format data partition
• Reboot to recovery
• Wipe everything except USB-otg
• Reboot to recovery
• Copy MIUI.eu 10.4 stable across via Android File Transfer (MTP)
• Install MIUI.eu
• Reboot to recovery (do NOT boot into system).
• Copy eufix-force-fbe-oreo.zip across
• Copy forceencrypt_mix2_v3.3_android9pie.zip - found here - https://forum.xda-developers.com/mi-mix-2/how-to/xiaomi-mi-mix2-encryption-android-9-pie-t3929322 across
• Mount vendor partition
• Install eufix-force-fbe-oreo.zip
• Install forceencrypt_mix2_v3.3_android9pie.zip
• Reboot into system, perform initial setup, check Settings -> Additional Settings -> Privacy -> Encryption and make sure that it says "Phone Encrypted".

You should also reboot into recovery afterwards and make sure that it is actually encrypted and that you can't access the files through there. OrangeFox prompted me for the decryption password immediately and wouldn't let me do anything to the Data partition without it.

Some of the steps above may be unnecessary, but this is what worked for me on Mi Mix 2S.

Hopefully that helps someone in the future. Still disappointed that I have to resort to this to get encryption - shame MIUI.eu devs haven't fixed this themselves!

Thanks for your help @linusyang92 and @shunf4

[shunf4]

@apemix2s The command is only for testing the full functionality of sed, and it won't do any changes to fstab.qcom. Have you flashed eufix-force-fbe-oreo after running it on your first attempt?

Flashing forceencrypt_mix2_v3.3_android9pie.zip replaces fstab.qcom with its own version in the zip. Are extra changes needed to be made besides replacing encryptable to fileencryption and ice to ice,quota, as eufix-force-fbe-oreo does? Perhaps you could provide a diff between the original fstab.qcom of xiaomi.eu 10.4 for polaris and that in forceencrypt_mix2_v3.3_android9pie.zip.