How to handle the Encryption disaster - Xiaomi Poco F1 Questions & Answers

After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.

---

SilentEYE said:
After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.
Click to expand...
Click to collapse
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470

---

pingufanpoy said:
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470
Click to expand...
Click to collapse
I already had installed twrp with encryption support.
After flashing havoc rom the system started encrypting my internal storage.
TWRP was asking for encryption password, but there was none, because it was a clean flash.
The first time my system got encrypted ( maybe even deleted) was after upgrading to vendor / firmware v10.
Gesendet von meinem Redmi Note 4 mit Tapatalk

---

You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too

---

AntwnhsAnt said:
You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too
Click to expand...
Click to collapse
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?

---

Uqbar said:
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?
Click to expand...
Click to collapse
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.

---

Mooatreides said:
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.
Click to expand...
Click to collapse
I surely haven't fully understood this encryption thing.
Mainly because on one phone, the OP3T, it was done by the OS itself upon my request with my encryption key.
While on another one, the POCO F1, is being done by something else, the so called "vendor software".
I was willing to have encryption on the POCO F1, it looks like I cannot have it. Bare truth.
With LOS v16 on an OP3T, if I reboot to TWRP recovery (or system) and don't provide the key I defined myself, I won't get access to the storage.
With LOS v16 on a POCO, I can reboot to TWRP recovery (or system) and have the storage decrypted by the " vendor software" without providing any key.
So, to my very limited understanding at least, POCO F1 doesn't have encryption unless you are trying to access the storage from the bootloader or from a device which has been turned off!
Or am I missing something very important?
P.S.
I don't see how a uSD card would save me. Can I enable user controlled encryption on an uSD?