Hey so I recently tried to update my pixel 5 to murena os to android 14.
I flashed the stock google android 14 → worked well
Used the easy installer → got to the last step →
“cant find valid operating system”
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
on the internet
A locked bootloader will only boot Android Verified Boot signed images/systems.
Due to the complexity and hassles that comes with making such builds most ROMs aren’t built AVB signed (so they require an unlocked bootloader)
You should not use easy-installer, it is not supported anymore instead use the e/OS/Installer (web).
And depending on the security patch you can’t lock it (yet). Please check install guide first.
Thanks for your time and support.
Yes, I used the web service under “/e/OS Installer”
I only locked the bootloader, because I followed the instruction of the automatic installation over the web service. I didn’t know myself, that it won’t work.
Also, bootloader locking is part of the manual instruction, too, so I assumed, that all would work fine.
I am currently using stock os again.
As mentiond, check the section about ‘risk of security patches’ 
.
Let me know if you don’t understand it.
Edit: It doesn’t say it Pixel 5 guide but it does with FP5… Check here the red part with examples:
https://doc.e.foundation/devices/FP5/install
I cannot find the specific section you mentioned, however I found the mention that bootloader locking doesn’t work on community builds.
Then I have to give fault back to the installer, because upon autoamtic installation I assumed the installer knows what it’s doing, so I locked the bootloader when it required me to do it
I edited my post, I was wrong with my comment.
e/OS/Installer doesn’t install community for Pixel 5. But it’s true only ‘official’ can be locked.
Okay, I see what you mean, but when running the installer, I couldn’t have imagined to check the security patches.
Does it make sense, running the installer again and skip the bootloader locking stage?
Ah, I see that was my mistake then. Okay, have I overlooked that, or was it not mentioned?
You could skip it but I don’t think it is needed. What security patch month do you have now?
‘About missing that part’, no you didn’t there is no disclaimer about as you are aware. And as you experienced with me together it also is not in every install guide for ‘official’ devices.
On the stock version it says November 2023.
The version itself is redfin-up1a.231105.001.b2-factory-4e5a2679,
the newest version you can get from Google on their website.
I tried manual install once and bootloading lock didn’t work. So I did the automatic install, with the bootloading, then it got locked, but also bricked the device.
Would be nice, if there would be an alert to not lock community build.
Sorry I wasn’t focused, your device is not supported by Google anymore. Locking the bootloader with ‘official’ should not be a problem. No matter if with e/OS/installer or manual.
But as said before you can’t lock bootloader if you install community (only manual possible).
Written on a Pixel 5 
Blockquote (only manual possible).
What do you mean? Is a download only manually possible? Or can you lock the bootloader manually (I know you can’t lock bootloader on community edition. I’m just irritated.
Thanks
I meant:
‘official’ (a13) can be installed manually or with e/OS/installer
‘community’ (a14) only possible to install manually