I’ve followed the instructions related to my device here.
After I managed to unlock my phone, I flashed the recovery image onto my phone by ADB and got a success message (maybe the step where I made a mistake).
Then at the stage 5 when I try to reboot my phone on recovery mode, the same screen appears: Redmi logo in the middle, Android at the bottom, and an open lock below the front camera (meaning that the bootloader is unlocked I assume) . I’m stucked and only able to start in fastboot mode.
Any idea of what I can do to solve that problem ?
Thanks in advance for your help !
5. Manually reboot into recovery mode
= Now reboot into r/e/covery to verify r/e/covery installation.
Do not reboot into the existing OS, since it will overwrite the recovery you just installed.
Thanks @Xxpsilon for your answer.
However I’m not sure to understand what you mean: how to reboot into r/e/covery instead of existing OS ? I held Volume Up + Power as indicated
You must get into Recovery without allowing the phone to do a normal shutdown cycle.
Sometimes it goes a bit like long press Power to leave Fastboot, but catch the shutdown as soon as the screen goes black and change the finger presses to Vol Up + Power at just that moment.
at the time the screen goes black, I remove my finger from the Power button and immediately put my fingers on Power button + Volume Up simultaneously (I also tried to keep my finger on Power button and add the Volume Up button once out of fastboot mode)
Every attempt I get the same screen: Redmi + unlock + Android
Do I make something wrong ? How to make sure that the device the computer recognizes as fastboot device is the phone and nothing else ?
Sorry I’m late for the discussion but, even if I can enter recovery, flashing the ROM hardbricks my phone, a Poco M5s. Did you achieve a successful installation? If you did, can you guide me through the process?
I’m not a newbie with this, but I can’t make it work. It always gets me to a bootloop and a hardbrick. Haven’t tried e 2.8 though, but it’s just tiring to try again without knowing someone out there is running /e/ in their Rosemary.
Could this be the reason why it doesn’t boot in my installation?
This suggestion you make is opposed to the one in the documentation:
Before following these instructions please ensure that the device is on the latest Android 13 firmware.
Latest firmware version is V14.0.17.0.TFFMIXM. Do you think this may be an error in the documentation, and we should try installing with that specific firmware version from Lineage OS documentation?
Just so you know. This V14.0.7.0.TKLMIXM firmware won’t even boot the recovery image as reported: a reboot into recovery won’t display anything and will make the device enter into a bootloop state.
With V14.0.17.0 firmware, the latest out there, /e/ OS 2.8 boots into recovery. You can follow the instructions in the documentation, everything goes fine but, if you reboot your phone as instructed, you will enter into a bootloop:
dm-verity encryption
Your device is corrupt.
It can't be trsuted and may not work properly.
Press power button to continue.
Or, device will power off in 5s.
If you press the Power button to avoid going into Power Off state and continue booting the letters will disappear but it just won’t pass from the boot splash screen, it will stay there seemingly forever, though, I’ve only waited 10-15 minutes there. Can’t get any log because it’s just not booting. Tried flashing a blank vbmeta.img to disable dm-verity with:
That won’t help either. This build shouldn’t be promoted as installable unless someone is actually using it, and can replicate a successful installation process. GOOD LUCK to any other one who wanted to try.
