Bootloader unlock and SPL

/e/OS Devices Fairphone
1

I have just get back my FP5 from service after I locked bootloader with community build.

Unfortunately they installed factory OS with SPL 5.09.2025. /e/OS/ 3.1.4 SPL is 01.09.2025. Can anyone say if it’s safe to install 3.1.4 and stay with unloced until release of 3.2 /e/OS? As I uderstand critical part with SPL lock mechanism is when trying to lock bootloader with older SPL than latest ever installed?

If yes, another question - will OTA update work on device with official build but with unlocked bootloader?

I am one month on replacement phone and I’d like to have most of my apps restored.

2

Hi,

even if the FPOS SPL reports the 5th, it is probably ok to install eOS. At least, I successfully did so some 3 months ago. Please make sure your bootloader is unlockable before locking (see last paragraph in the cited post).

Cheers

Ingolf

3

luckily 3.2 is just to be released, I will wait few more days…

[EDIT]

Due to some delay in 3.2 release installed 3.1.4 using online installer. there is unlock ability = 1. So, it’s safe to lock? And will it be possible to upgrade to 3.2 using OTA?

4

My FP5 is bricked after locking with SPL 1.09.2025 (factory was 5.09). But I was able to unlock it. Now I am using 3.1.4 unlocked and waiting for 3.2 to upgrade.

5

So it was not bricked …
You still have access to bootloader mode and can run fastboot commands

6

Just a matter of what you called it :wink: /e/OS documentation called it bricked.

obraz
obraz824×128 6.16 KB

Anyway - I was no able to lock bootloader and start using OS normally. Some years ago I’d start to freaking out thinking I destroyed my phone :smiley:

I just let the other know that it wont work with FP5 to fool SPL…

1 Like
7

Hi

So, do I see that right: At the moment - got a Fairphone 5 with current Android - I cannot properly and completely install /e/os. But instead I have to wait until there is a newer patch of /e/os? How often do new releases come out usually?

But as an alternative, I could install the current /e/os and leave the bootloader unlocked. As soon as a newer /e/os is out, I can update /e/os and THEN I can lock the bootloader again?

→ My dauther is quite persistent in her will for a smartphone she wants and so it’s good to be well prepared for discussions :slight_smile: (because I am persistent with my will too wanting her phone being on /e/os)

Sorry, maybe my question is a bit silly, but I an quite new to this topic…

Thank you for any feedback, David

8

If current Android means Android with SPL dated 5.09.2025 then yes, you can just install /e/OS and leave bootloader open. But keep in mind that when 3.2 /e/OS will be released (hopefuly next week) and you’ll install it and lock bootloader your data will be wiped (lock/unlock wipes userdata). So if you don’t want to double your efforts with OS configuration you shall wait few more days.

I installed in only to check if it’s possible to fool SPL - and no, it isn’t :frowning:

9

BTW/JFI: there is some good write up on reddit on why one might not want to relock the bootloader:

https://www.reddit.com/r/LineageOS/comments/n7yo7u/a_discussion_about_bootloader_lockingunlocking/

Doesn’t mean I am recommending anyting. Just wanted you to have that information.

1 Like
10

Monthly,

Next 3.2 build is expected soon..

11

I think that if one wants to use banking apps than locking bootloader is a must….

12

Banking apps are a complex story, really.

As a current example, look at https://community.e.foundation/t/securego-plus-app-stopped-working/75832. It has some tables that includes the bootloader lock state, but it doesn’t seem to be the real factor.

All depends on your precise needs. And it’s of course up to you.

For example for me “being able to recover by installing a different recovery and debugging from there” is more important then 105% working banking apps. Just my 2 cent.

1 Like
13

Warning: The bootloader is lockable in official builds only. The procedure to lock the bootloader will not work on community builds.

14

Hi cabnedor

Do I understand that correctly (as soon as 3.2 is out):

  • I can install /e/os official build (a14) on my Fairphone 5 and it will be possible to lock my phone

  • I can install /e/os community build (a15) on my Fairphone 5 but it won’t be possible to lock the bootloader

Just for me to properly understand my options…

Thank you and greetings, David

15

You can lock community build as wellbut only once and then unlocking costd you some around 60€ :slight_smile:

But being serious - I did lock community build by accident - all is described in manuał install instructions and I shiuld be more careful.

Widi:

  • I can install /e/os official build (a14) on my Fairphone 5 and it will be possible to lock my phone
  • I can install /e/os community build (a15) on my Fairphone 5 but it won’t be possible to lock the bootloader

A15 was avaliable for FP5 but for some reason it dissappeared from the webpage. Hopefuly it will return with 3.2

16

One has to decide about relocking (as a high priority) A discussion about bootloader locking/unlocking… AKA I want to relock my bootloader, should I? already mentioned.

… and wiping all you daughter’s data ??

I think not … in my experience younger people know what they want … and it is not jumping through hoops …

17

Well, she gets her first phone and I am now preparing it:

She does not have data on it yet, therefore this is not a problem yet. But she wants her phone NOW and so it might be difficult to argue to let her wait for long time further :wink:

19

Just to give my feedback to this posts question of mine: With the new /e/os 3.2 all worked fine (I did not update Android in advance :wink: )

Thank you for all your help

20

please how did you do ?

i am interrested to help someone in another thread…

21

It wasn’t hard, since my phone bootloader_unlock_ability was still set to true so I unlocked it via adb. In my SSR the problem was that I installed OS with older SPL than last installed OS.

1 Like