That doesn’t make it clearer, because it doesn’t say what would happen when locking after an update.
Can I take it then that there will be an OTA update for the next security patch and running that will make it safe to re-lock the bootloader if it wasn’t safe before?
OK. I get that you were not convinced by my previous answers. The real answer is the full explanation from the install page which is copied in Post #2
It is a very black and white matter.
I am happy to try to answer black and white questions if you still have them after careful reading.
It is a very black and white question
which is not addressed on the install page, and your response
doesn’t answer that question, and vaguely touches on the second part in a way that could be misconstrued as to it being safe to lock again when it’s not, on an old security patch.
Maybe I need to start a new thread to find someone who can understand the question, I don’t know.
Requires knowledge of future events.
You identified that install and lock is a non-runner right now.
Why get into “testing” if you don’t quite understand the risks?
Why not wait till you know it is safe?
After reading the thread, I think I have the correct understanding on when a Phone is bricked.
In my case …
Android version - 15
Android security update - 5 June 2025
… I’d need an /e/OS version that includes the security updates from 5 June 2025 or later to lock the bootloader and not brick my phone. If I install an older version, I’d need to keep the bootloader unlocked until installing a version meeting the above mentioned requirements.
Now I’ve got two questions:
I hope this is not too redundant of a question. I just want to not brick my phone lol
A request for clarification on this 5-June-2025 vs 1-June-2025 “anomaly” was requested Please put the complete date of the security patch date in the release notes.
Both dates are valid as seen:
I do not recall if any users reported an SPL of 5th June, the ones we seemed to see most of were 1st June.
There has been some delay in getting the e-3.1 build with July SPL ready for release
… not sure if we will see it this week but I suggest it safer to wait for that.
Generally it is latest but in the very first days it has been known to deliver the penultimate build.
Mhh okay makes sense. Thanks for all the info.
But in general it would be possible to keep the bootloader unlocked, install 3.0.4 and when the build with the July SPL arrives, upgrade to that and lock the bootloader again?
I know it will erase all data, I’d probably use the meantime to just try out the OS and reinstall / setup everything again with the July build.
Yes … but … Installed 3.0.2 official and tried to lock bootloader.
I coined a term “Late Lockers” (by which I mean those who do not perform the lock immediately after install, without reboot as said on the /e/OS install page) … if you take this route there is another reported success Revert back to stock OS and relock bootloader.
Also you can use Seedvault to make a Backup, since you have no problem with loosing data I guess there is no fear in trying it out.
This topic was automatically closed after 180 days. New replies are no longer allowed.