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

Help Fairphone 4
, ,
135

At least for me this analysis seems to be correct. I have not unlocked the bootloader and I have not installed a custom ROM and the update to Android 13 (C.073) went fine. I have an uptime of >25 hours and not a single reboot or any other issue that might be related to the Android system update. On the contrary, my FP4 feels better (more responsive) since the update and even the overly aggressive vibration seems to have improved.

I did, however, modify some system settings including developer options (enabled USB debugging and a few other settings) and I did disable/uninstall a few core apps (e.g. GBoard, the Google app, YouTube, …) using universal android debloater as described in this thread (with a few deviations).

4 Likes
136

I was worried at first and didn’t do my updated.

Thanks for the conclusion USB-2, it brought me to the update.
I never modified and mine is now A13.

Not much changed but overall quite some pleasant tweeks. Essentially the same experience as user0815

Put a hart to one of the 3 posts with successful updates, if yours went through as well and you never changed your OS. Like that we don’t spam the thread more.

1 Like
137

Was also worried, but then i started the update on my almost-untinkered FP4 and it updated flawlessly :slight_smile:

138

Is there anyone here who had a custom ROM on their phone in the past but now managed a successful upgrade to A13?

139

Will there be a patch (OTA update via adb) from the Fairphone Company? Is that even possible? Or do I have to send in my FP4 brick.

140

I know my post has been moved to another thread.

But I want you to let you know following post on the other thread:
So I was able to test the device via an USB-C Dock. I have seen the screen and setup the device over the dock as you setup normaly over the screen.
Means Device is up an running on StockROM A13.

1 Like
141

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?

142

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
143

I’ve sended an email yesterday to the support. Waiting for the answer.
I hesitate to contact them by phone directly

144

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
145

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? :thinking:
It would also explain why the automatic A/B fail-over won’t do anything - bugged or not.

146

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
147

Does the phone’s touch layer work in that case?

Also, can you try rebooting into safe mode?

148

Nope touch layer is not working

149

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
150

I can use touchscreen for input.

What do you mean with safemode?

151

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?

152

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:

153

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.

154

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