Thanks for claryfing the error @hirnsushi.
I opened a ticket with the support 13 hours ago, still waiting for first replying, let’s hope for the best.
1 Like
have you received the automatic response with the ticket number? Then I would call them tomorrow, as waiting can else be up to a week.
2 Likes
Yes I got the ticket number. I’ll follow your suggestion and call the support tomorrow morning. Thanks again.
Actually you could call them today (I keep thinking Tag der Deutschen Einheit was everywhere, too 
) at the number at support.fairphone.com (bottom of the page, also note office hours there).
2 Likes
Upps I thought its Sunday today so thanks for reminding me tomorrow is not Monday 
3 Likes
Opened a request as well, since my phone died with the update to A13 as well. Just seeing the splash screen and then black (but illuminated).
Was on original software with locked Bootloader. Ready to ship it to France I guess.
2 Likes
Do you have an USB-C to HDMI/DisplayPort adapter? Try connecting your phone to a screen using such an adapter (or a screen that already has an USB-C connector).
In case this is a backlight configuration issue, you should still see the phone’s screen on the external display. I had that on Android 11 on the FP4 once, when I imported the config of my old phone.
I don’t expect this to work, but it’s worth a try. If that’s the case, let me know, and I can help you further.
3 Likes
Thanks for the advice, unfortunately I don’t have such a cable at home and is pretty difficult to find one, I should buy on Amazon with the risk that this would not help at all 
You can just return it if it doesn’t work.
Same thing here:
I actually returned to default stock (factory reset) because I was preparing it for my mother to use.
The phone was logged in using a gmail account and no apps whatsoever. So incredibly stock.
I thought I’d upgrade for her, so she wouldn’t have to wait. And now I as well am experiencing black screen during boot and after a minute or two, the device just shuts down.
It even interrupts the Fairphone Logo that normally would appear when booting. Just turns black.
3 Likes
I just did a wipe/factory reset from the recovery menu (holding down volume button while powering on).
Does not help, device still only shows a black screen and turns off after two minutes.
Fairphone may want to pause the rollout of this update. This is feeling serious.
5 Likes
I’ve tried installing the Factory ROM: https://support.fairphone.com/hc/en-us/articles/18896094650513
But since I cannot boot into android to unlock the bootloader there using the unlock code (https://support.fairphone.com/hc/en-us/articles/10492476238865) it seems I’m stuck with an unbootable phone.
I made a support request, Keeping you posted.
Not helpful now, however one reason why I always have OEM unlocking enabled as well as USB debugging from initial set-up
2 Likes
I have edited my earlier post as I am getting the worrying impression that it could make FP4 users attempt a downgrade while the bootloader is locked.
3 Likes
While that might help, it’s not something I would expect from an average user before installing an official update.
Just to add: the dangerous part bricking the FP4 is trying to relock the bootloader after the manual install using fastboot.
Interestingly the new support article is again not covering that (still a bit hidden only mentioned in the manage bootloader support article) and states
Flashing with fastboot
Pros
- Works regardless of what version you are on.
- Can be used to downgrade to an older version (e.g. Android 13 → Android 11).
- Can be used to return to Fairphone OS from a custom ROM.
2 Likes
Well now. Suddenly I’m glad I was unable to flash Android 12. And also getting frustratingly mad “-ish” about this situation.
Why has the Android 13 ROM not been available then on that official ROM page? Why offer the upgrade without also having that?
To upload a new update always takes a bit time… However as long as your bootloader is locked it will not help you for your current issue
2 Likes
That risk is non-existent, recovery only accepts OTAs that target the right version.
Since Fairphone doesn’t publish OTAs that downgrade the system to a previous version (or full OTAs) it’s not possible to accidentally brick the phone that way (at least while the bootloader is locked).
But that also means the only way is forward, in the OPs case (and probably the others as well) that would be the next OTA update, whenever that is released …
6 Likes
I updated my FP4 to Android 13. With the success that it no longer boots. I have FP OS on it, but with an open bootloader. The installation went smoothly, but the subsequent reboot failed. There comes the hint of the open bootloader, then the Fairphone sign and then the display turns black and shortly afterwards, the phone goes out completely. Can’t you run FP OS with an open bootloader?
Greetings Martin V.