Hello, im in the same page as all of you, what should I do?
Its best just to contact the Support team and explain my problem or just send it as a return?
I have read the warranty policy installing third party software breaks the warranty
And if so, what will be the cost of the “unbrick” or if they will do anything about it.
I was really happy to use this phone, ill love to continue using it in the future. Rn is a pretty brick that reminds me of my stupidity
Thanks in advance
Well if its your falt you would have to pay for repair else warranty still is in place for the pbone. In the past the cost was approx 50€.
Here there seem to be a bug in the phone or script, so I would not agree to pay for the repair.
4 Likes
When are the online chat opening hours?
I seem to always get the AI bot and never actually reach an agent, despite trying multiple times at different times in the day.
Check the hompage at the bottom I dont know, as its changing
Hello: You’ll have to do what I did and return the device to a Fairphone center to have it unlocked. I had no other option.
You can manage the return through Fairphone Support.
1 Like
Did you have to pay something?
So far, nothing. The phone is already on its way to France.
1 Like
How did you get the return label? I have been talkimg to the IA for hours
No real human will talk to me
During the times that live chat is available, tell the AI assistant that you wish to speak to an agent and it should put you through to a human.
3 Likes
Looks like I might have some good news to share, at the very least for those who haven’t bricked their phone yet. 
With today’s release of FP6.QREL.15.105.0 (SPL June 2025), I felt confident enough to attempt to flash Fairphone Android from /e/OS 3.0.2 (Official, SPL May 2025), and did so with success! 
Mind you, I am no expert on this matter, so proceed at your own risk.
I followed Fairphone’s instructions on unlocking the bootloader and manually installing Android.
As warned, the bootloader was left unlocked after booting into Android, with fastboot flashing get_unlock_ability returning 0 in Fastboot. So I did some minor research into the issue as it occurred for the Fairphone 4, which is when I found these comments:
So I returned to Fastboot, reflashed the phone with the recently installed Android release, and held the “Volume Down” during boot – preventing it from booting into Android and instead returning to Fastboot.
Now, fastboot flashing get_unlock_ability returned 1, so I was able to relock the bootloader according to the official instructions, making sure that the phone never fully booted into Android between each step, instead loading back into Fastboot and retesting fastboot flashing get_unlock_ability before proceeding.
And… that’s that. I am now back on Android and have not encountered any quirks so far. 
All the kudos and big thanks to @AnotherElk and @hirnsushi for being the giants upon whose shoulders I could stand. 
5 Likes
Getting the labels is a bit long. They take a few days. If you access support from the website, there are several options. Choose to return the phone. You’ll have to fill out some forms that they’ll review. They’ll send you several emails until a final email where they send the labels. I couldn’t get them from AI. You write that you want to speak with an agent, but that never arrives.
1 Like
Congrats!
So it really was a question of booting into /e/OS between lock_critical and lock and not a SPL issue.
My question for you is : at the end of lock_critical, what did it prompt you to do? Did it propose to stay in bootloader or reboot to bootloader or reboot to system? Or did it just reboot and you had to make sure it got into bootloader?
It sure looks like it, although I can’t confirm that, as I waited for the new Fairphone Android update and associated SPL. However, I did see that letting it boot into Android post-flash caused get_unlock_ability to return 0, so it seems likely.
Allow me to answer these questions with some (pseudo)code, which I think better highlights the order and results of my actions. 
Flash the Fairphone (Gen. 6) with the Fairphone Android OS.
# Desktop PC is running Linux.
# Phone is running /e/OS 3.0.2, SPL May 2025.
# Phone has a fully-unlocked bootloader.
> adb devices
# Confirm USB debugging is working by detecting phone.
> adb reboot bootloader
> sudo fastboot devices
# Confirm phone is visible to Fastboot.
> sudo fastboot flashing get_unlock_ability
# Returned 1.
> sudo ./flash_fp6.sh
# Scripts starts flashing the phone.
# Once completed, hold VOLUME DOWN to boot into Fastboot instead of Android.
Locking the bootloader, part one (lock_critical).
> sudo fastboot devices
# Confirm phone is visible to Fastboot.
> sudo fastboot flashing get_unlock_ability
# Returned 1.
> sudo fastboot flashing lock_critical
# Phone prompt: Are you sure you want to lock the bootloader?
# Yes.
# Phone clears and resets.
# Hold down VOLUME DOWN to boot into Fastboot instead of Android.
Locking the bootloader, part two (lock).
> sudo fastboot devices
# Confirm phone is visible to Fastboot.
> sudo ./fastboot flashing get_unlock_ability
# Returned 1.
> sudo fastboot flashing lock
# Phone prompt: Are you sure you want to lock the bootloader?
# Yes.
# Phone clears and resets.
# Allow phone to reboot into Android.
Hope this helps, and if not, do let me know so I can clarify further! 
2 Likes