For info, as another example, mine happened this morning on a full charge. I had the notification of an update when I woke up so downloaded it, then when I restarted it never turned back on.
1 physical SIM
Hadn’t been having any issues with the phone beforehand, apart from disconnecting from Bluetooth devices occasionally since the previous update and the battery is only a month old.
Ok so rather no issue with e.g. 2 SIM or work profile…
Maybe you installed the exact moment it was probably recalled (because yesterday it was intended to roll out to the beta tester only…)
Edit: I at least got confirmation that it was recalled at 9am this morning and that they took note of the reports about the dead phones.
Welcome to the Community forum, although it’s for unfortunate reasons you are arriving here. I moved your post here so you can follow or join the discussion of this issue that others have reported as well (see above).
Have you heard anything wether the ones who successfully installed FP4.QREL.15.15.2 must fear a brick of their phone too?
That’s a rather horrible software management of FP which I can’t believe, especially not in view of the problems with …15.14.3
no I dont think there is any need to fear a brick when it properly installed and rebootet. I just rebootet again and it boots normal, the new update still installed (I’m no beta tester so got the update as you yesterday). However everyone always should have a back-up of important data as such devices can always brick at any time.
If this is true, it’s been a HUGE mistake!
I actually at the moment dont think the update itself is bricking and rather the timepoint you tried to install it. When (and at the moment there are none) there are no issues reported in the beta group it would have gone out in a few days as it is, was yesterday, so the same would have happened in case its really the update and not the timepoint.
Sorry, just to understand, what do you mean with that?
Is it about the time of day? Or about the procedure? Or about something else?
The update was recalled this morning at around 9am and when you tried to install it at that time or maybe after? their might have been any “glitch” because you tried to install something that acrually didnt exist anymore. No idea if reasonable or not, however I think all who reported a brick reort to have updated this morning…
Hi everyone,
We wanted to share a quick update regarding the Fairphone 4 software rollout that began yesterday.
After the initial release, we identified some unexpected issues. To ensure the best experience for all our users, we have currently paused the roll-out and our team is looking into it.
We are checking the issues reported and will share the full release notes as usual once the official update is ready to resume.
Reminder: If anyone is experiencing any issue with their device, please reach out via the official Repair Portal.
Thank you for your patience and for being such an active part of our community!
Best,
The Fairphone Team
Just for the records, I updated my FP4 yesterday (Congstar Germany) and it restarted without any problems.
But I hadn’t any issues before, so maybe I’m just lucky 
That is great news for everyone else but what about those of us who’s phones have been bricked? When can we expect a response to our support tickets?
All affected cases of those who’ve reached out to CS have already been escalated.
You can send me your case number via DM if you like, then I can doublecheck.
Apologies if it is painfully obvious but how do I DM you? (I’m new to this forum community)
I just messaged you 
Installing the update this morning, my FP4 could connect to E only. Tried everything to find another mobile net.
Another restart was the only thing that helped. Could connect to 5G immediately.
Juat remind new user cannot DM
Thanks @yvmuell ! For those users: Please just tag me here & Ill send you a message to which you should be able to respond.
Hi, @Fairphone_CM I just created a case. Please hit me up so the case can be expedited.
Done 
You should have received a message.