Black Screen/Booting Issue After FPOS C.073 Android 13 Update

Help Fairphone 4
, ,
26

While that might help, it’s not something I would expect from an average user before installing an official update.

27

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
28

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?

29

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
30

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
31

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.

32

Good morning guys,
just finished my talk with Fairphone support and I will be forced to send the phone to France.

I reported the presence of this post in the forum to allow the technical team to investigate the problem based on what we have tested.

I’ll eventually update this topic when the phone will be back in my hands.

4 Likes
33

Did you try to keep Magisk? I regularly had problems with that and need to re-root from scratch.
This time I reboot immediately and re-rooted the system-

What you could try is reboot into bootloader, switch the active slot and try rebooting and restart the OTA.

34

No, I didn’t use Magisk. Sure, I can try reflash the software, but I want, that it I can start an update without any trouble.

35

Update from me as well: Just finished talking with the support. It seems that more and more people are calling in, reporting the same:

Updated the phone and did a restart. Just seeing the initial splash screen and then the screen goes black. Illumination stays active for 1-2 minutes and then the phone turns off.

Fairphone will send me a return label to Cordon Electronics for the phone to be reflashed (no costs included).

Greetings,
Alex

3 Likes
36

The question is, if you were able to boot the phone with A12 from the old slot and do not loose your config. Then you could start the OTA again to get A13. At least that is how I understand the setup with the two system slots.

1 Like
37

I will try it in the next time.

38

So I have the same issue, and now all I can do is wait for them to release the full zip on their website… wow…
I’ve been using android for at least 15 years and I have never been in this situation before - with countless shakey custom roms, modded stuff and so on I have never been bricked, but now on a stock rom doing a OTA my phone is a brick… wow FairPhone lost me as a customer now.

1 Like
39

Moved you over here…

40

Do you have a locked or an unlocked bootloader?

1 Like
41

No, you shouldn’t wait for the next OTA and there won’t be a full OTA either. That’s not the solution, just the things the recovery would accept (if your bootloader is locked).

You should however contactsupport and send your phone to Fairphone (Cordon) to get fixed.

1 Like
42

I made a support request yesterday evening and haven’t heard anything yet? Guess calling them is a better bet then?

43

Standard response time is about 5-6 working days. If this is urgent (which i guess it is :slight_smile: ) then you should call them directly. Be ready to wait 10-20 minutes on the phone.
Due to the launch of FP5, a lot of requests are coming in.

3 Likes
44

I just tried to call. After 20 minutes, I got a notice “we are very busy unfortunately.” and they hung up. o_O

Second attempt after 17 minutes waiting I was helped by a lovely person.

And yes, also need to send it to France. I was asked not to upgrade my wife’s Fairphone 4 (bought at the same time, so probably the same issues) and that not all Fairphone 4’s are experiencing this issue.

4 Likes
45

Did anyone try the USB->HDMI cable to see if it is the phone or just the screen? I have such a cable but I am lacking the problem after the update. :wink: