Stuck in a boot loop after install attempt on FP5

[sander_malschaert]

Hi All,

Just tried to install on on a brand new FP5. Was the third time I did it. Got it to boot in e/OS. Then went back to fastboot mode to relock the bootloader and after:

fastboot flashing lock

like described here:
https://doc.e.foundation/devices/FP5/install

got a message that the phone was corrupted and could not boot. Now it only displays the fastboot menu and keeps going back there. Also I cannot connect to it any longer through my PC. Does this mean I bricked it? Could use a pointer here as to if this is fixable

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[piero]

@sander_malschaert

Does this mean I bricked it?

probably yes, because of security patch date dismatch

[aibd]

@sander_malschaert

it only displays the fastboot menu and keeps going back there. Also I cannot connect to it any longer through my PC.

By this do you mean that with the phone apparently in fastboot mode, with the green START at the top you get no response from

fastboot devices

??

This would tend to define “Non functioning fastboot” which would indicate requiring reimaging by by Fairphone if you tried to lock the phone after downgrading Android SPL.

This is mentioned as

Caution: The FP5 comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information

… but you really do have to Click on Details below to fully understand the issue.

[sander_malschaert]

This is exactly what I mean. No matter what option I choose, it goes back to this screen.

‘adb devices’

shows no devices now.

“which would indicate requiring reimaging by by Fairphone if you tried to lock the phone after downgrading Android SPL.”

I think this is what happened yeah. Does this mean I should ask Fairphone if they can reimage it? I don’t get how I did not have this problem with previous attempts. Don’t rememeber if I just didn’t relock or that versions were different at those times.

[aibd]

@sander_malschaert

should ask Fairphone if they can reimage it?

I think so. I guess they will also be able to go through the symptoms with you before you put it in the post to them or their agent.

[sander_malschaert]

Thanks, I will contact them tomorrow then.

[sander_malschaert]

Contacted Fairphone. They will indeed reimage it for a reasonable fee <3 Then I will try again and hopefully don’t fudge up

thanks all

[snupeli]

Rollback protection errors are FATAL when the bootloader is LOCKED.
Rollback protection errors are IGNORED when the bootloader is UNLOCKED.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.you must keep it UNLOCKED

[mihi]

Or wait about a month then update with newer e/OS/ version and then lock it (if used during that time all data will be wiped)

[mihi]

Not sure if any of this helpes (you are not the fir.t one with that issue)

My new fairphone blocked in bootloop

Somebody else reports success in seemingly the same scenario … Fairphone 5 UNBRICK w/ Bootloader locked - Android 14(+?) Bootloader Only - #13 by tofbouf - Guides - Fairphone Community Forum

Fairphone 5 - locking bootloader

Hi there, I did install e/OS 2.6.3 on fairphone 5 fp5 according to the install guide . The install went well, apparently and according to that guide, the next (and last) step would have been to lock the bootloader again. The guide suggested to lock the Bootloader before a reboot Once you have completed the above steps and before rebooting you can lock your Bootloader. However, the device rebooted automatically. There was no chance for me to stop the device from rebooting and lock the Bootloa…

Another one but in German:

FP5 hängt in fastboot wegen Fehler nach /e/ Installation

Hallo zusammen Ich habe einen Fehler gemacht. Nach der Installation von /e/OS und Neustart habe ich die Option “OEM Unlock erlauben” ausgeschaltet. Bei einem Neustart bemerkte ich die Fehlermeldung beim Bootloader, dass der Speicher nicht geschützt sei. Also habe ich fastboot flashing lock ausgeführt. Danach kam die Meldung, dass das System unsicher sei und nicht mehr gestartet werde… Was kann ich jetzt noch tun? Bin um jede Hilfe dankbar! Liebe Grüsse Sege

[snupeli]

When you are not sure whether it can be locked, you can try to enter the command.
Fastboot flashing get_unlock_ability is not 0, it must be 1! If it is zero, don’t continue!

[sander_malschaert]

Thanks all, phone is on it’s way to be reimaged so will try again next week.

[sander_malschaert]

Update: the phone got reset by Cordon Electronics in France for around 50€ all in. I have installed e/OS without incident on it. This time I left the bootloader unlocked. Can anyone tell me what it means to have the bootloader unlocked? I mean are there risks involved with keepong it unlocked?

[aibd]

Good to hear that your FP5 was returned fixed.

@sander_malschaert

anyone tell me what it means to have the bootloader unlocked?

There is quite a full discussion on the topic here https://www.reddit.com/r/LineageOS/comments/n7yo7u/a_discussion_about_bootloader_lockingunlocking/ and many contributions seen in a forum Search.

---

For others finding this thread it is unfortunate that documentation does not cover this point better.

To check the security patch level on your phone with a locked bootloader, prior to installing /e/OS, open your phone Settings » About Phone » Android Version » Android Security Patch Level.Then compare it against the level of the security patch on the /e/OS build as visible in the Downloads for FP5 section below.

In the excitement of the phone arriving with Fairphone installed and starting the install adventure, I believe one must first go to

Settings » About Phone » Android Version » Android Security Patch Level

and take a screenshot of this information and store it off the device as internal storage will be wiped during the /e/OS install.

Following /e/OS install one can now compare that date with the date published here Releases · e / os / 🚀 Releases · GitLab and found when one searches that page for

Security fixes

where for instance one currently finds

This /e/OS v2.7 version includes the Android security patches available as of December 2024.