Boot loop after installing e/os on Fairphone 5

Hi everyone!

I know that there are already other posts about this topic, but I feel like they are all a bit different from my situation, so… here another question about a bootloop!

I installed e/os on my new Fairphone, and went through all the steps. Everything was perfectly fine untill I wanted to lock the bootloader again, as I am supposed to do according to this website: https://support.fairphone.com/hc/en-us/articles/10492476238865-Manage-the-Bootloader

After giving the command ./fastboot flashing lock_critical, all was fine and dandy, but then I ended with the command ./fastboot flashing lock, and now my phone is succesfully locked, but also stuck in a bootloop. When I turn my phone on, I get the bootload menu with start/restart bootloader/recovery mode/power off. It says my device is locked, which I guess means I did something right, but it also means that I cannot do anything to get it out of the bootloader menu. Does anyone have an idea of what went wrong? I feel like I followed all the steps correctly, and all was fine untill the last step. And, is there any way I can fix this? There is no data on my phone yet so losing data is not a problem.

Thanks in advance!

It sounds rather as if you have taken a similar path to one of these threads, perhaps you could see if the anti rollback was compromised by the Security patch dates in your case.

Thanks!

The difference with this thread is that when I give the command ./adb devices, it does show my device number + fastboot. For the person in that threat it did not show any device. Does that make a difference?

With regards to this thread, how do I find out if the anti rollback was compromised? I was not aware that this could be an issue.

I am guessing that you may have missed the “hidden” Details on the install page Install /e/OS on a Fairphone FP5 - “FP5”.

If you get the phone to self-identify with both

adb devices

in normal or Recovery mode … and

fastboot devices

in Fastboot mode, then you have a different issue.

Thanks so much for your reply. I did miss that. I actually started off with a different installing page, sent to me by fairphone, which did not have this warning.

As I gather from the printscreen, this is fatal and not to be fixed? Is there nothing I can do to get out of the bootloop, even when I am willing to erase everything that is on the phone? (since I don’t have any data on there yet)

Please bear in mind that I am no expert on Fairphone or Locking. I am just joining the dots as I see them.

You might get the device in Fastboot mode and show the output of

fastboot devices

and if successful in “self identify” …

fastboot flashing get_unlock_ability

Both commands just ask for status, no intrusion.

The screenshot was just to show the “Hidden detail” trick, in case missed. I think you really must read and understand the page so that we don’t come to the wrong conclusions.

Perhaps you can find a way to find the Fairphone OS version and hence Android SPL as delivered? It is a complex subject and the threads I pointed to probably need full and careful reading – or you might reach out to the individuals who themselves faced the anti-rollback issue.

It says that the unlock ability is 0. Honestly, I am in over my head a bit. It seems like the best solution for me would be to contact fairphone and they might be able to fix it. Thanks so much for your help!

In this case you bricked your phone.