Hi,
This is my first post so hello to everybody! I’have already used /e/ in a couple of devices and it just worked fine.
Now my dobt is: according to this post https://android.stackexchange.com/questions/238980/why-is-it-possible-to-re-lock-the-bootloader-after-installing-a-custom-rom-on-s it seems that theoretcally /e/ ROMs for ufficial Murenas phones are able to lock the bootloader after the rom has been installed without probs (no brick, everything goes smooth). I guess they send them like this.
This, as the author of that post hypothesize, is becaus the /e/ OS images are probably signed with some official keys, so when you lock the bootloader they’re recognize and everytjing works fine.
My question is: 1) I have a Oneplus NORD 5g “avicii” AC2001 which is the same model sold by Esolutions. Do you think that after flashing e OS I can safely lock the bootloader? 2) Do you think it would work also for other devices/rom which a re not official /e/ Murena devices?
Thanks
I installed /e/ on my Pixel 3a and relocked the bootloader after installation. Unfortunately, it wiped out the OS and I had to reinstall it and leave the bootloader unlocked lol. But, it would be pretty cool if they could add relocking the bootloader to the phones that are capable.
I locked the boot loader on my FP3+ after manually installing /e/OS. It is perfectly working !
My guess is : it depends on your device. For the Fairphone, locking the boot loader is even included in the install instructions.
Pixel models seem to be very fine for locking the bootloader after you flashed a custom ROM. Just did it with a Lineage OS Microg on my Pixel XL. Everything’s ok.
I loaded via fastboot TWRP recovery, made a factory reset, format data and wipes. Then I Sideloaded Lineage 17.1 Microg OS then I went in fastboot and gave the command: “fastboot flashing lock” then of course you have to confirm it on the device, Done
When I relocked the bootloader with /e/os I had already booted into the os and was checking it out and went back into fastboot mode after the fact. I’ll try locking it this time before I boot into the system after installation.
Hello,
i use a Xiaomi Mi8, since one year with e/oS/ unlocked.
Should I definitely lock my phone again after e/OS/ installation?
And if so, where can I find instructions?
I didn’t find anything here in the forum or on the installation guide.
My suggestion: be careful, this is why I opened this thread. I Begin asking to /e/ programmers (but sadly they didn’t answer yet) if locking e OS bootloader on the same officially devices (Murena) would wofk without issues. It should, as the devices E sells are identical for the hardware to the same we maybe have, but we don’t have a confirm. This is why I was thinking to buy a Oneplus Nord AC2001 (1st version), to install and lock E OS like the one delivered by E. That said with my old Pixel XL everything went ok. It was logical to me that it would work -. but I used Lineage 17.01 Microg. I didn’t use E because the development of that ROM stopped in an old version. So again, until E don’t gives any instruction and also about their Murena, I would be careful.
I will try my amateur explanation again, it was not contradicted last time!
Android is carefully built and secured to do all the consumer facing jobs which Google can say are secure enough for a bank or any secure organisation to be able to assume the person typing on the keyboard is their customer without a doubt.
Some free thinking people, like many readers here, do not want to be part of that. LineageOS and /e/ in slightly different ways allow us to unlock the system and put in a “cleaner” one with surprising ease.
One reason the answer is not sounding quite straight is that different manufacturers implement the Android security features slightly differently. When you ask the OP question of one particular device you can get a more well defined answer!
Having unlocked it can we just lock it back up again? Well, not without making good all the missing pieces of the lock, perhaps including a Google presence. Put it another way, re-locking the device would attempt to “turn the key” but are all the internal components there, or is there a booby trap?
If the device would lock, the install guide writer would have included it.
Check out other alternative ROM builders. This forum has a few topics worth study. I deliberately include the link to the very well informed author on DivestOS first.
My account is still purposely restricted by /e/ team so I cannot post links.
I recently overhauled the verified boot enablement scripts in DivestOS.
/e/ is still very much welcome to use it.
You also need all the lines commented “Resurrect dm-verity” in the other scripts for the /recovery and some device specific changes.
And you need 0001-OTA_Keys.patch for /build.
And lastly the signing function:
https:github[.]com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L187
