After having installed /e/OS, and after the successful reboot into it, I checked my unlock_ability in fastboot, and it returned a 1. Further following instructions on the /e/OS website, I booted into fastboot again, issued the two commands fastboot flashing lock_critical and fastboot flashing lock and rebooted only to see a message that my phone was corrupt and would not boot.
I booted back into fastboot and did fastbook flashing unlockand fastboot flashing unlock_critical, and it seems to have worked, since the fastboot screen says "DEVICE STATE - unlocked.
I did adb devices, but adb did not “see” anything. fastboot devices, however, returns my phone ID and fastboot, like so: 56f4737b fastboot.
I have intended to flash /e/OS again, but since adb does not recognize my phone (I cannot boot into /e/OS anymore unfortunately to change settings there), fastboot cannot flash anything and waits forever for the device.
Is there a way out of this mess? Any help greatly appreciated.
Thanks for your reply. On the e/OS/ download website it said SPL 2026-01-01. After the installation the device rebooted into e/OS successfully. It worked until I had locked the bootloader.
So much for now. Tomorrow I will read that guide, and hopefully it can give me some clues…
it will be for e-3.4-a15 that is already out from “community branch”, but will be released soon from “official branch” /e/OS official FP5 download
Thank you for all you r answers. From what you say I can safely conclude that I have involuntarily bricked my phone. I have flashed /e/OS 3.3 onto my phone. I have no idea how something like this can happen at all: I swear an oath that when I followed that link on the FP5 /e/OS install page (see screenshot obove) stating that what I would find was on SPL 2026-01-01 I found to .zip archives of /e/OS 3.3 with suspicious file names as for the SPL dates. I trusted the info on the preceding page, however, thinking that they know what they are doing.
And after having read your posts, I went there again, and lo and behold: all of a sudden there were three .zip archives, the top one being 3.4!
I am downloading it at present, and I will try to flash this onto the phone now. Hopefully this will work. My Fastboot output is as follows, which looks good to me:
Report: After the download was finished, I tried to flash /e/OS 3.4 onto my phone. The script got stuck a couple of times in different places, but I aborted it and tried again and again - seven times in all, but my perseverance paid: I got it to run through to the end once, and now I am on /e/OS 3.4!
The bootloader is still unlocked, I must say that now I am reluctant to lock it again, although it says that I can lock it in an official /e/OS version. The situation I have been in and out of which I could wiggle with some amount of good luck (it seems to me) has really been a big hassle.
So I ask: what do you recommend now: leave the bootloader unlocked (I know what that means, but the risk in my case seems to be more on the hypothetical side to me) or can I safely lock it now? At least I have flashed something with a more recent SPL over something with an older SPL.
Security fixes