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

[GunniMator]

Hi Martin,

I do not see something under Ota Sideload . In my browser, it states “coming soon…” and if I would use the fast load thing, my data would be lost. But you said, that you used adb sideload. I am confused.

Can you help?
Best regards
Gunnar

[yvmuell]

Is your bootloader unlocked or at least OEM unlocking enabled as well as USB debugging (for the latter I’m not completely sure its required)?

If not, fastboot is no option and for sideload see above (click on the arrow to show hidden text behind the warning)

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

EDIT 18:50:

NEVER attempt a DOWNGRADE (like from Android 13 to Android 12). From what has emerged over the last 1-2 years in this forum, downgrading to an older security patch level can hard brick your phone (which can only be fixed by Fairphone's Repair Service for a fee).

Have you considered the OTA sideload option here: <a href="https://support.fairphone.com/hc/en-us/articles/18896094650513">https://support.fairphone.com/hc/en-us/articles/18896094650513</a> I notic…

And be prepared it might fail

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

There is your problem, your phone is already on the latest build (TP1V). Those are delta OTAs and they can only bring you from one specific version to another. You are definitely already running A13, but the boot fails for some reason. The bootloader should fall back to the other slot after a few attempts if the phone didn’t manage to boot after an update, but if it doesn’t there’s not a lot that can be done. There are no full OTAs available and with a locked bootloader I think that’s sadly a…

[peci1]

Could it be this one?

Software update: FP4.TP1V.C.073.20230905 | Upgrade to Android 13 - #18 by AndreasChris .

[GunniMator]

Thanks to you two. I read the whole thread, but i did not know, that there can be hidden text behind a small arrow

So i will give it a shot and i am just downloading the ota. Fingers crossed…

[GunniMator]

Hm. I downloaded the ota.zip and worked as described in the “Install Fairphone OS Manually” using the OTA from Linux (Mint).
It aborts stating that “E:Package is for source build SP2K but expected TP1V”.
So i guess, it wont work for me, as the update took place, but is somehow screwed and there is currently no other idea but to contact fairphone for a repair somewhere in France?

[peci1]

I have no experience doing this, but did you try switching the A/B slots during the OTA sideload?

[GunniMator]

Hi Peci1, no i havent. i could give it a try. Just have to find out the commands. Give me a minute and i will come up with the results. But i am not sure, whether it is possible without any debugging options enabled.

[GunniMator]

Hum, unfortunately, it seems, that i cannot switch A/B slots, when i did not unlock the bootloader. If that is wrong, please give me a hint, how to do it. Everything i found, needed it to be unlocked.

[yvmuell]

@yvmuell

If not, fastboot is no option

Not=“not unlocked” so no you cant switch slots

And this is true for you as well

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

There is your problem, your phone is already on the latest build (TP1V). Those are delta OTAs and they can only bring you from one specific version to another. You are definitely already running A13, but the boot fails for some reason. The bootloader should fall back to the other slot after a few attempts if the phone didn’t manage to boot after an update, but if it doesn’t there’s not a lot that can be done. There are no full OTAs available and with a locked bootloader I think that’s sadly a…

As you didnt answer

@yvmuell

or at least OEM unlocking enabled as well as USB debugging

So if this isnt the case yes contactsupport

[GunniMator]

Alright, then be it.
Thank you all for your help anyway! It is very nice to have people around, that share their time to help,

[hirnsushi]

Reading that page it sounds like they will provide the link to the delta OTAs directly, so no more extracting it from logcat, which is great

Still, it doesn’t look like they’ll offer full OTAs, so it won’t be really useful for affected people with a locked bootloader unless they publish a bugfix release very soon …

[GunniMator]

I was in contact with the support and they will check, whether an OTA-file that can heal the problem will be made available in a duration, that it might make it okay to wait for it and use another phone(if available) instead of wiping all data.

[Devilicate]

Is this supposed to update from A12 to A13 without the risk of getting the black screen or is it for fixing the black screen after the update? I already tried it (with the black screen issue), but it didn’t change anything.

[yvmuell]

I moved your post here the ota.zip was not published for the black screen issue and there is proof it will not help because

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

There is your problem, your phone is already on the latest build (TP1V). Those are delta OTAs and they can only bring you from one specific version to another. You are definitely already running A13, but the boot fails for some reason. The bootloader should fall back to the other slot after a few attempts if the phone didn’t manage to boot after an update, but if it doesn’t there’s not a lot that can be done. There are no full OTAs available and with a locked bootloader I think that’s sadly a…

[metafan3]

So, after reading this thread and the one on the black screen issue, I am a bit worried about updating, due to the possiblity of an unusable phone. Is there a fix for the black screen issue or some insight as to which devices are affected? Do you think performing the update is safe or is it recommended to wait for the next one?

[Lars_Hennig]

Yes, there is a small chance you could get a problem after the update. However, I guess the vast majority is very happy with the A13 update (like myself ).

[peci1]

See Black Screen Issue After Android 13 Update - #24 by yvmuell . With OEM unlocking enabled and adb debugging on, you should be able to restore the phone if anything goes wrong. You might still lose your data, though.

[USB-2]

I would find it intersting to know which sort of FP4’s are or can be affected. Is it a software or maybe a hardware issue? So, the question is, what do the FP4’s with a failed update have in common?
Is maybe a certain batch affected? What system version was the update perfomed from? If we knew, maybe we can tell something about likelyhood of an update to fail.

So, people with a failed update could post whether they have one of the first phones after FP4 hit the market, or rather a later one.

I bought mine in Feb. 2023 and the update worked just fine from Version B.089.

[KleinerAdmin]

Good Idea!
Mine is from Dec '21
Installed every Version of FP OS
No modifications (e.g. rooting or unlocking)
Apps only from Google Play Store
Original Launcher

Update went smooth, no reboots

[melzrob]

My FP4 was purchased in February 2022 and the update to A13 went flawlessly. No modifications, some F-Droid-Apps installed.