…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services
Just signed up to tell this. You can use MTKClient (GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool) to unlock the phone’s bootloader, instead of Xiaomi’s arbitrary way of unlocking the bootloader. This tool can also unbrick this phone.
The process of using MTKClient to unlock the bootloader:
- Download and install it (GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool)
- Then, go to the directory where mtk.py resides (repo’s root directory)
- Run this command
python mtk.py da seccfg unlock(this unlocks your bootloader and it will not erase your data for some reason, though don’t take my word for it) - Make sure your phone is turned off, plug your phone to your computer, then press all hardware button. (MTKClient waits for your phone to go to the “brom” mode)
- You will see the “dm-verify” thing, but you can easily ignore it by pressing the power button
The process of unbricking the phone:
This process depends, because if you just locked the bootloader, you can unlock it by following the 3rd and 4th step of unlocking the bootloader. You can also flash stuff by using the command python mtk.py w, similarly to fastboot flash.
I’m trying to install this ROM following these instructions, but I just can’t make it boot. I believe there is something crucial lacking in the documentation, probably a specific firmware version for the current build, as it was done in the Lineage OS version, which required a firmware based on Android 12.
As instructions are written right now, there is no problem booting the recovery images from any version in the repo, but flashing the actual OS ends up in different outcomes like failing verification signature, and different errors. Version 2.6.4 flashes correctly, then it boots into a loop. There must be something wrong, the installation process needs to be reviewed as the latest official firmware version was released a couple of weeks ago, in my experience, this firmware is incompatible with the most recent builds o /e/OS for rosemary. Anyone trying this firmware will hardbrick their phone, and coming back from this brick is a daunting job for your average user.
Hello there!
Please do something about the documentation of this build. In January, I reported that the instructions in the wiki will not finish up with a successful installation of /e/ OS, you get instead a bootloop, as it’s also documented here. I have tried different combinations of firmware+builds and none of them seem to work. Logs can’t be retrieved from an OS that does not boot. I appreciate you guys wanting to support more and more devices, but I’m telling you, doesn’t seem to be anyone running this build.
I plan to use this device (the Poco M5S variant) as long as possible, so, if you want to actually make it boot and find the exact instructions to install a build successfully, just contact me. Likewise, I’ll be around to test any ideas.