Just one more idea - but if you really need your phone as a daily driver, stop reading now.
Otherwise: Why don’t you try to take another step and let UBPorts flash your Lancelot first. If it works, you will have a Not-So-Smart-Linux-Phone without the Xiaomi-Crap. And starting from this base you then might be able to flash E/OS from the scratch. If you consider it, have a look at:
Had the same problem on another version of Windaube, but it appear to be caused by proprietary blobs that are present in Windows but not in LinuxMint (LM), if I understood this right.
Unzipping from the Windaube PC always worked, didn’t find the way to do the same on LM.
I downgraded Android from 12 to 11, as the UBPorts said. And it works. UBPorts failed to install ubuntu touch, but it installed its recovery. I am testing now. Will be back with more results
Solution was: It must be installed FROM MIUI 12, NOT 13.
Conclusion: Guide must add this specification. As a requirement, installing eos in lancelot must be done from MIUI 12 (Android 11). So, if user has miui13 (A12), system must be downgraded to previous version.
Thank you all for your interest, concern, advices and participation.
according to the included /META-INF/com/google/android/updater-script, e-3.2-t-20251026540684-community-lancelot.zip
for lancelot, galahad, shiva is builded on top of
Redmi/lancelot_global/lancelot:11/RP1A.200720.011/V12.5.6.0.RJCMIXM
so Android 11-R, MIUI 12 from july 2020.
I’ve seen similar behavior where the bootloader options don’t always respond as expected, especially on certain device builds. When low-level actions don’t give clear feedback, it can feel a bit like flying blind. In other systems that rely on status tracking, having reliable confirmation of state changes really helps — hopefully this gets improved or clarified in future updates.