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

[yvmuell]

@urs_lesse

When you try to reboot (into the standard operating system, a) does the FP3 vibrate, but b) stays all black (display) without any “Fairphone” lettering? Do you g) get the 1 mm LED light at the top of the front display

I’m confused as the OP has a FP4🤔

[urs_lesse]

Yes, has been clarified in #3 (at the latest).

[Tuzzaman]

I appreciate your guidance and support, @urs_lesse. However, I have a question regarding the sideload procedure, and I hope you can provide some clarification.

1. I’ve successfully downloaded the zip file (aa907f00e7c5446fb6b00fa481e089dcacde21ef.zip) and extracted it to my desktop. (I’m using Ubuntu as my operating system).
2. I’ve put my Fairphone 4 into recovery mode and selected “Apply update from ADB.”
3. Now, I understand that I need to launch a command from the terminal using the “adb sideload [filename]” format. However, I’m unsure about which specific file I should select for this procedure.

Could you please advise me on the correct filename to use in the adb sideload command? Your guidance would be greatly appreciated.

Thank you once again for your assistance.

[urs_lesse]

Frankly I’m not that deep into the matter beyond the instructions in the Support article. On a glance, I am not sure if you are supposed to extract the installation OTA .zip or should actually keep it in .zip state (my GUESS: it’s the latter). I tend to think @AndreasChris or @yvmuell are more well-versed here.

EDIT: You followed the instructions right (extraction is mentioned there).

EDIT 2: I am not sure what exactly “the previous step” in “Extract the .zip you downloaded in the previous step and move the unarchived folder to your desktop” refers to (Android Platform Tools OR the OTA installation file), thus my confusion.

[Tuzzaman]

Ok here’s the two cases:

1. When I lunch the command adb sideload [UNZIPPED FOLDER] my linux terminal says “adb: failed to read package block: Is a directory” and the phone terminal says

E: Signature verification failed
E:error:21
E: (adbd status 10)
Install from ADB completed with status 2.
Installation aborted

2. When I lunch the command adb sideload [ZIPPED FOLDER] my linux terminal says ar first: “serving: ‘[file name]’ ([percentage])” until, at the end of the process i get the message “Total xfer: 1.00x”
   But my phone terminal says:

Finding update package...
Verifying update package...
Update package verification took 49.5 s (result 0)
Installing update...
E:Package is for source build SP2K but expected TP1V

Install from ADB completed with status 1.
Installation aborted.

[yvmuell]

@urs_lesse

or @yvmuell are more well-versed here.

not at all… I was surprised to see that this seem to be finally be a solution for all devices (adding to my FP3 vs. FP4 confusion mentioned above) as this was just recently published due to the A13 Fingerprintsensor issue on the FP3. so most likely still kind of “beta” state…

and I would mention @hirnsushi here, although he is not not so much active recently

Edit: I dont know if the article was fixed as it was incorrect/incomplete somehow

Android 11 updates: Do I need to unlock the bootloader?

There is now a new support article for this problem, also see the original solution post by @Yasen_Tomov. However, as noted by some members of the community, that support article still has some rough edges. I tried to add all enhancements discussed here and some more to the installation guide to create a more complete set of instructions (a mod may convert this to a wiki post if they want so that other users can add enhancements): Download and locate the file that you need to sideload: Go to…

[hirnsushi]

@Tuzzaman

E:Package is for source build SP2K but expected TP1V

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 case for contactsupport

[Tuzzaman]

Thanks for claryfing the error @hirnsushi.

I opened a ticket with the support 13 hours ago, still waiting for first replying, let’s hope for the best.

[yvmuell]

have you received the automatic response with the ticket number? Then I would call them tomorrow, as waiting can else be up to a week.

[Tuzzaman]

Yes I got the ticket number. I’ll follow your suggestion and call the support tomorrow morning. Thanks again.

[urs_lesse]

@yvmuell

Then I would call them tomorrow

Actually you could call them today (I keep thinking Tag der Deutschen Einheit was everywhere, too ) at the number at support.fairphone.com (bottom of the page, also note office hours there).

[yvmuell]

Upps I thought its Sunday today so thanks for reminding me tomorrow is not Monday

[G33K2303]

Opened a request as well, since my phone died with the update to A13 as well. Just seeing the splash screen and then black (but illuminated).
Was on original software with locked Bootloader. Ready to ship it to France I guess.

[Dakkaron]

Do you have an USB-C to HDMI/DisplayPort adapter? Try connecting your phone to a screen using such an adapter (or a screen that already has an USB-C connector).

In case this is a backlight configuration issue, you should still see the phone’s screen on the external display. I had that on Android 11 on the FP4 once, when I imported the config of my old phone.

I don’t expect this to work, but it’s worth a try. If that’s the case, let me know, and I can help you further.

[Tuzzaman]

Thanks for the advice, unfortunately I don’t have such a cable at home and is pretty difficult to find one, I should buy on Amazon with the risk that this would not help at all

[Dakkaron]

You can just return it if it doesn’t work.

[M4rk]

Same thing here:

I actually returned to default stock (factory reset) because I was preparing it for my mother to use.
The phone was logged in using a gmail account and no apps whatsoever. So incredibly stock.

I thought I’d upgrade for her, so she wouldn’t have to wait. And now I as well am experiencing black screen during boot and after a minute or two, the device just shuts down.

It even interrupts the Fairphone Logo that normally would appear when booting. Just turns black.

[M4rk]

I just did a wipe/factory reset from the recovery menu (holding down volume button while powering on).
Does not help, device still only shows a black screen and turns off after two minutes.

Fairphone may want to pause the rollout of this update. This is feeling serious.

[M4rk]

I’ve tried installing the Factory ROM: https://support.fairphone.com/hc/en-us/articles/18896094650513

But since I cannot boot into android to unlock the bootloader there using the unlock code (https://support.fairphone.com/hc/en-us/articles/10492476238865) it seems I’m stuck with an unbootable phone.

I made a support request, Keeping you posted.

[yvmuell]

Not helpful now, however one reason why I always have OEM unlocking enabled as well as USB debugging from initial set-up