Did I understand it right, that it doesn’t matter if I lock it or not when it comes to get a bricked phone? The risky part is to install later the FPOS?
For what exactly do I have to lock for? I read quite a bit of the Topic and I didn’t find like the cause of the bricked phones. What does the get_unlock_ability exactly mean? And what should I do when it is 0 or 1?
For your future risk of bricking the phone it doesn’t matter if you’ve locked it in the past, that’s correct. But, the risk isn’t only present with FPOS, you can brick it with any OS you install if something goes wrong and you didn’t make sure fastboot flashing get_unlock_ability_ is 1 beforehand.
The CalyxOS device flasher just checks that for you and stops if it isn’t, that’s the part that makes it safer.
You don’t have to, there are some (banking) apps that check for that and will refuse to work and there are several security benefits that are only in effect if the bootloader is locked.
Whether you can unlock the bootloader again by issuing fastboot flashing unlock or not (which means it’s bricked if you can’t boot into the proper Android userland)
If it’s 0 don’t lock, reflash the ROM you were trying to install, check again. If you want to lock the bootloader, don’t boot into Android userland after flashing, there’s a high likelyhood that resets the value and you definitely shouldn’t lock after that.
As long as you don’t brick your phone you can always go back to FPOS, but as @AvidAlbatross noted, make sure, if you are locking the bootloader on a custom ROM, that that’s actually supported.
That’s generally what happens, since it’s a bug in the bootloader so Fairphone’s responsibility, but none of us work there, we can’t guarantee it, the policy might change any time.
Just a small addendum, if you decide to go that route and updated your phone to the latest FPOS already, you’ll need to use the beta factory images, not the ones mentioned in the instructions. More info here.
Just for documentation:
I installed /e/OS and after that LineageOS on my FP4 (purchased 22/03 with FPOS), all worked nice. Then I needed to go back to stock-ROM, because my banking-app only works on phones with locked bootloaders. After installing the latest Stock-Rom ( https://support.fairphone.com/hc/en-us/articles/4405858261777?s=09 ) I locked the bootloader. And voila: Stuck in bootloader with no possibility to unlock or boot into recovery.
Now I contacted FP support and wait for an answer.
To be continued…
So I bought a used fairphone 4 from a big online retailer. Said in the description: foil on the screen was removed, functions flawlessly.
Well turns out it doesn’t work flawless. it is stuck at fasboot the bootloader is locked and booting to recovery or the system does show a quick fairphone logo and returns then to fastboot.
So i guess either someone bricked it and sent it back to the retailer and they sold it again without checking the function of the device, or it was not working from the beginning or magic happend.
I reached out to the online retailer to find a solution.
And it all makes me pretty angry, since i bought a fairphone because it is easily repairable - at least thats what i thought. And rn idk how much of that i can really believe anymore. since it seems to be a problem that needs the intervention of the official support. so what was then the point of getting a repairable phone if i cant repair it on my own.
Also that this wasn’t fixed yet. also the lack of replies to this from fairphone on this all disappoints me, i was hoping that with a company that is invested in repairability and sustainability things would be different but maybe a big part of it is just marketing. thank you all for helping me finding out what’s wrong by reading this thread. i hope the retailer i bought the phone from comes to a good solution for me. And i guess if buying used fairphone 4 phones if possible make sure that it boots beyond the fastboot before buying, especially when buying from private people.
Hey all ,
I recently got my FP4 as a present and was really hyped using it and trying out a custom ROM. But unfortunately I’ve run into the same problem as many in this thread have.
My story (short):
(at first I ran into some issues because I, unexperienced and completely new to the topic as I am, forgot to update my FPOS to the latest release)
then I installed /e/ OS using their EasyInstaller. Everything worked perfectly (except the automatic locking in the end of the installation process; that (fortunately) didn’t work)
after locking the bootloader (because I read that it’s recommended) my FP wouldn’t boot (because of a corrupt OS)
fortunately, I could unlock the bootloader and installed FPOS again and did the whole process over again except for the last step. Because of reasons my present-self doesn’t understand, my past-self tried locking the bootloader again (reversing the order of the commands, first lock and then lock_critical, because I’ve read it somewhere)
and then my device got into said brick state, that is well known around here. Doesn’t boot and keeps returning to the fastboot screen.
Unfortunately I only discovered this thread after I bricked my device (next time, I hope I will be more careful).
I’ve contacted support 2 days ago (til now no answer, but they said in their mail that they would need 5-6 days, so no hurry on my side, my old phone works). I would be willing to pay the 30€ (after all, the accident happened while installing a custom ROM), but after reading this thread and as far as I understand the matter this is caused by a bug in Fairphone’s bootloader. I’ve already written in my support ticket that I tried installing /e/ (and I don’t like the idea of giving false information, e.g. that the error happened while installing FPOS, especially with a company like Fairphone, whose mission and goal I really care about).
Let’s see what will happen. In every case, I’m very excited for my new Fairphone (and waiting a few more weeks is a bummer, but won’t stop me from (hopefully) becoming a very satisfied Fairphone user).
Just wanted to inform you, that this is still relevant and still happens to inexperienced users like me.
(Sorry, this post unfortunately got longer than I planned.)
Thanks for the loads of really helpful advice in this thread (I wished I would have read it earlier). You’re all great!
Wait a sec. You mean that if I run into a 0, I can simply reflash the same rom and without rebooting there is a high chance that afterwards it’s 1 again?
Somewhere on here I read, that it might also help to alter the current slot. Is that true?
If yes, that will only help once, right? Because when let’s say slot a gives me a 0, then I change it to slot b and this one also get corrupted, there is no going back, right?
If you reflash the same ROM there is basically a guarantee that it’s 1 again. Once you boot it for the first time you will end up with a 0 (at least with stock FPOS and CalyxOS).
That’s why you shouldn’t boot into Android and lock it afterwards, that’s how you end up with a
No, the install script will set the slot, don’t mess with it if you don’t have a good reason. Switching slots won’t bring back get_unlock_ability.
If your system is unbootable, your bootloader is locked and you have lost get_unlock_ability, then there is no way for you to switch slots. Changing slots only works with an unlocked bootloader.
my fairphone 4 is blocked in fastboot mode.
after installing /e/ OS i wanted to secure again my phone and enter these commands:
fastboot flashing lock_critical
fastboot flashing lock
but my oem was locked by the official e installer…
so my phone always start in fastboot mode and the only authorized operation is poweroff
is there any possibility to unlock oem?
fastboot see my phone but not adb
fastboot flashing unlock : FAILED (remote: ‘Flashing Unlock is not allowed’)
– fastboot devices find my device
adb devices didn’t see anything
i tried to contact fairphone support to be helped but, i’v bought my phone in Orange Store (and neither the store nor the 3900 want to help me at this time). so i only receive an automatic message from fairphone telling me to contact them. No answer from fairphone at this time (contacted from a week ago)
I’m sorry to say, but there’s no way for you to fix this yourself other than going through support. You’ll need a shipping label from support, the phone gets sent to Cordon, they’ll charge you ~30€ and you get it back.
If support doesn’t answer soon, try calling them, that usually speeds things up.
I want to try different custom roms to see, which one suits best for me. I was on eOS 1.81 and want to try iodeOS 4.0 now.
In the documentation it says you need to be on latest stock FW with locked bootloader - locked critical to be precise.
I was on unlock ability 0 until I found your post yesterday. Thanks to your kind help I was able to flash stock without automatic reboot, therefore unlock ability was 1.
I then sucessfully run fastboot flashing lock_critical, but afterwards the phone booted automatically and I’m back on unlock ability 0.
This is ok as a prerequisite for iodeOS installation, but is still very frustrating when someone wants to go back to stock completely.