Hello @piero, thank you for your links, I rode many posts on the XDA forum and found interesting things that helped to solve my case.
Hello @stuart, yes I’ve been able to install /e/ OS (S) without running no-verity-opt-encrypt not any other similar package. But in this way, I’m not sure if everything would be OK in the long-term.
I rode this other testimony that goes the same way as mine : it seems that @mospaeda has also been able to install /e/ OS on his S9 without “patching” the device with code to remove the encryption.
But just as him, I installed the stock ROM up to date on my cellphone, through Odin, before to install TWRP and then /e/ OS. Once again, I share this process, well describe. You just need a machine running on Windows for it. (I haven’t tried to install the stock ROM through Heimdall on Linux, but it seems far more difficult due to the fact you have to manually list all the repertories needed for the system, and to do it all in one command, and in the right order because if you don’t respect the expected pattern it will fail. Plus some people experienced a limitation transfer of 4Go with Heimdall.)
So, I really recommend you to update your cellphone with the latest firmware, via the installation of the stock ROM through Odin.
Then, during the first boot on the stock ROM, you have to parameter many things, but you don’t mind all of this because it’s just a transition step for us, who hope to be /e/ OS users .
So I recommend to skip every steps you can skip, especially those related to the encryption (when the system asks you to “protect your phone” with facial recognition, iris, fingerprints, etc…).
I haven’t do many tests so I cannot be certain of it, but I wonder that maybe it plays a role in the encryption you encounter then via TWRP. So just install the stock ROM without connecting your google account, without parameter the “phone protection” etc. Just have a look for updates and activate the developer parameters to activate OEM Enlock and USB flashing etc… At this point, you can follow the official process.
Indeed, when you come from the stock ROM, the official process works fine for me.
The only thing that used to block me was this incapacity to install the “patch” no-verity-opt-encrypt.
Even if I did install /e/ OS without this patch, I was anxious that something could be wrong, so I decided to install again the stock ROM, and try it all again.
I did it, and the only thing I changed is that I installed TWRP 4.0 instead of the 5.0 or even the 6.0. The file I chose to install it through Heimdall is twrp-3.4.0-0-starlte.img dowloaded from the official TWRP site.
I rode on XDA forum that anterior versions (3.0 and below) does not support Android 10 (Q).
TWRP 4.0 has been designed for Android 10 (Q). The upper versions can be more buggy for the functionality we are looking, don’t ask me why as I’m not at all an expert. I just rode it from others, and experienced if myself so I can confirm I didn’t worked for me with TWRP 5.0 and 6.0, but it did work with TWRP 4.0 : I’ve been able to successfully install the no-verity-opt-encrypt-6.1.zip (you can get it from here, as @piero shared it in a previous post) !
Then continue to follow the steps described in the official process, things you have to do with the data, cache, etc. And finally install /e/ OS (Q), and it should work as it did for me .
I hope my experience helped you, please let us know if it works for you as well.
PS = to share it in detail, the /e/ OS Q (0.19) took approximately 3min15sec to be installed on my phone after I launched the command through Heimdall.
And if other people was wondering, the memory place dedicated to /e/ OS Q (0.19) is effectively 8,4Go on my phone. I checked the stock ROM while I reinstalled it, and the memory space dedicated to the system took 11,5Go. That difference is not surprising due to all the proprietary apps on it (Google apps + Samsung apps) on the stock ROM.