Sorry, but it is unclear to me what your current status is and how you got there. You wrote in the other thread that you had IodeOS installed. Then you somehow went back to stock FPOS, (then?) you had the black screen problem, connected to a dock and saw something? What is the status now? Does your screen actually show anything?
Iām not sure if anyone knows, yet. It depends on what sort of issue was caused by installing the custom ROM.
Has anyone with the problem contacted support and also pointed to the findings in this thread? If theyāre still not aware of the connection, it might take even longer for them to figure out.
2 Likes
Iāve sended an email yesterday to the support. Waiting for the answer.
I hesitate to contact them by phone directly
Yes, because I didāt lock the bootloader and flashed the latest StockRom for A13.
Yes. Status is still the same: boot, fairphone logo, vibrate, black screen >Device is on. I can see the Screen on the monitor. I can manage the device over the usb-c dock with mouse and keyboard.
1 Like
Ok, that is indeed interesting! This would mean that the update did not (fully) brick the phone and might open some possibilities for recovery with a new update without having to send it in.
Even stranger, though: Why would the previous use of custom ROMs prevent the screen from working properly? 
It would also explain why the automatic A/B fail-over wonāt do anything - bugged or not.
I confirm what HereWeAre is saying. Iāve plugged in my FP to my USB-C dock and Iām able to see my screen and obviously use keyboard and mouse
3 Likes
Does the phoneās touch layer work in that case?
Also, can you try rebooting into safe mode?
Nope touch layer is not working
Just a short summary for those not reading the whole thread and who got ābrickedā phone after the update.
The phone is most probably not bricked!!! From forum user reports, it seems it is only the display driver that fails. And it seems it only fails on phones that have ever tried installing another OS (even if they reverted back to FPOS and locked bootloader).
If you donāt mind factory-resetting your phone, you can try to unlock the bootloader using a USB-C dock and reinstalling the system. That would be destructive for your data. It is still unclear whether there is a non-destructive way (probably, waiting it out for the next update could help).
In any case, to prepare for the destructive way, you can utilize a USB-C dock to backup your data that arenāt stored in clouds.
7 Likes
I can use touchscreen for input.
What do you mean with safemode?
Still all a bit vague to me what happened to your device, could we sort finally which OTA caused the issue, FPOS or Iode OS?
See here: FP4 booting issues running/updating IodeOs - #5 by HereWeAre
Since the appearance of this to the finaly blackscreen where more than one Update on A13 Iode.
So in my case it was Iode OS. But others have the same issue when have/had installed an other OS, even if theyāre back on StockRom.
At this point I would support the opinion of @USB-2:
Thanks to clarify. As IodeOS is on Android 13 since a long time already, the below seem to bevtrue for this FPOS upgrade 12 to 13 and I would rather call your issue a coincidence, as normally IodeOS is not that fast to include such updates in their system
Only to sort things out, not to say anyone is wrong.
That should cause a factory reset, just to make some of the obstacles clearer
I moved your statement and marked it as solution knowing its just an update, however so everyone can find it easier. Its still in the other topic as well
1 Like
Oh, I wanted to have the report in the update thread so that people who donāt follow this topic would also get the information. But youāve put there a reference, so it might be enough.
I donāt have this problem, so I canāt test whether this advice actually works. Is there someone who has susccessfully switched partitions to get back to A12?
I even updated the initial post from yasen and added a warning linking your post
Not everyone having the issue will read over there and rather here.
You seemed quite confident about the root cause having information from somewhere else, arent you?
Unfortunately, not. I just tried to distill information available in this thread.
Iām one of the (un?)lucky betatesters who still havenāt got A13 update, so I followed this thread closely to be ready for whatever comes.
4 Likes
So maybe you want to rephase your post, to make clear that those are possible guesses based on 1 report plus a phone running Iode and nothing confirmed by anyone officially.
Ok, I rephrased it a bit. Maybe you can remove the āSolutionā mark until someone confirms switching partitions is actually possible?
1 Like
on an external monitor i also see that FP loads and then displays the lock screen. Touch layer does not work for me.
I hope to connect my FP4 to a normal dock station tomorrow and experiment further.