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 Bootloader before the reboot.
I’ve tried to fix it by booting into the Bootloader with fastboot, but I ended up in a disaster. After I did the last 2 steps adb reboot bootloader + fastboot flashing lock_critical + fastboot flashing lock
I’ve got an error message saying " Your device is corrupt. It can’t be trusted and will not boot" and I was indeed not able to boot anymore. I’ve tried locking the Bootloader again, but I got stuck in Bootloader bootloop. I couldn’t get to the recovery anymore and I couldn’t boot to system either.
Fastboot commands still worked and the following command has saved me fastboot flash boot boot.img from a bricked phone.
My question is now, should I lock the bootloader and if so, how (without bootloop/bricked phone)?
Usually your phone should start just fine with an unlocked bootloader, if the flashing went well. That’s what I did, in order to check everything and take the time because of the anti-rollback feature. You should NOT lock your bootloader, before being sure your /e/os version’s security patch has the same (or newer date) your stock android version had.
There is a command to check, if it is safe to lock your bootloader. I’d have to look it up, or maybe someone here has it at hand.
Locking your bootloader will wipe your user data though, if you already use /e/os before doing so, and you will have to go through settings again.
" Before going in and locking use the following command to check whether you would be able to unlock again afterwards if there was some sort of problem:
fastboot flashing get_unlock_ability
If the output =1, then you would be able to unlock again
if the output=0, do not lock. You will not be able to unlock again and if the phone doesn’t boot properly you’ve had it. Fairphone will need to reset it."
Thanks for your hints.
the flashing went well. I’ve checked the installed security patch version in advance. It was June 2024 or something and e/OS 2.6.3 has Dec. 2024. Also after flashing e/OS, it booted into system normally and all looked good.
fastboot flashing get_unlock_ability seems to be Okay in my device.
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
fastboot oem device-info this one state’s that it’s unlocked, but I think I would need to know what got me in that bootloader bootloop situation before I should try again locking the Bootloader.
I’ve only installed e/OS A14 community build for testing. I will use the phone only when the A14 / U stable is out and then I will wipe and flash anyways again.
The community build here says November 1st not December. Are you sure about your stock android security patch then? Or where did you get your unofficial build from?
indeed it’s Nov. 24, but that is still far off from June 24 and also I was able to boot into system after installation. The bootloop only came after I’ve tried to lock the Bootloader. So that doesn’t sound to me like a problem with anti roll-back feature, doesn’t it?
If you think it’s worth trying again to lock the Bootloader, I can do. Now that I know to get out of such a bootloop
Hi, I had the same problem. I flashed again and left the bootloader unlocked.
After that I went into some wifi problems, so I flash stock rom and I was able to lock the bootloader again. I will wait now for a new version of eOS, with new security patch.
