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

Damn, my FP4 is affected as well. I hope there will be a solution soon! :frowning:

Def. contactsupport and let them know

2 Likes

Thanks, done! :slight_smile: Let’s see if they get a solution hopefully w/o needing to wipe all …

FP from July '22
Installed every version of FP OS without problems
No changes to the phone
All apps from the Google Play Store

So far I haven’t updated and won’t until the errors/problems that have arisen on other phones are officially fixed.
Instead, I first looked up the FP Forum in the “Help” section. I will continue to do this in the future before deciding whether or not to update.

I’m not an expert, unfortunately.
Thanks to everyone here in the forum for helping me avoid making mistakes in advance. I’ve learned / I’m learning so much just from reading through. It’s fun and reassures me and my husband, who also bought an FP on my advice and resents me quite a bit once in awhile.:wink:

5 Likes

5 posts were split to a new topic: Fp4 booting issues running/updatung IodeOs

A post was merged into an existing topic: FP4 booting issues running/updating IodeOs

Wow, I first thought the wifi test has to fail because the wifi won’t connect without PIN. But now I’ve found out (on a working FP4) that it actually connects even before entering the PIN. However, I think the tries to call the phone have to fail because it should always request a PIN to unlock the SIM card.

2 Likes

Overall I think we have different issues which I split so to get back the wifi connection point

This is to test if the phone boots comletely and just the screen is black, as discussed in the topic about Iode.

I personally doubt this, nevertheless its worth a try for sure.

That’s absolutely right!
So, in order to check this, one would have the put the SIM card into another device and temporarily(!) disable the SIM code. Then, after reentrering the SIM into the FP4, the test should not fail on a working phone and it should be callable.

I have fear to do the update :scream:
If there will be a new safer update dose the phone recgnize it?

1 Like

Are you sure even a PIN-less SIM would get unlocked without the phone being unlocked? I thought the phone will not register to the network without being unlocked (as a security measure).

Yes. The phone should then be in the same condition as after entering the SIM-PIN. Would be sad if no one could call you, when your phone is in your pocket, and locked. :wink:
So SIM PIN means SIM is permanently unlocked.

Edit: To check, I have rebooted my FP4 and entered the SIM code. Then I gave it a call and it worked.
Other than my Samsung work phone. This I can only call after once logging on to the phone with the screen PIN. Maybe it’s my company’s default setting as an additional security feature. But it is not standard on the FP4. So, removing the PIN and calling it should make it ring, if it is alive after the update, only black screened.

I, of course, meant the initial unlocking after a reboot. My phone doesn’t ask for PIN, but does ask for screen password.

Whether you’re asked also for the SIM PIN, is given by “SIM Card lock” setting.

Yes, and if you unclick it, the PIN will be deactivated on the SIM card. So, if you do this on another device and put it back to a black screened FP4, the question is if it is callable after booting up.

But this is something only someone with an affected phone can tell us.

1 Like

I was having a look;
The phone seems to not boot, at least I can’t ping it’s IP which I usually can (I have pi.alert monitoring)

Also I thought to switch slot which does not work in locked status:

./fastboot set_active b
Setting current slot to 'b'                        FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed

Unlocking is not allowed…so not sure how to go on here! If somebody had the phone unlocked before it might work?

1 Like

And at the same time, when it’s stuck in the black screen ADB reports: “unauthorized”

Would the fix be Fairphone releasing the 2nd version of FP4OS running on A13 as an OTA Sideload update here, so we could Sideload it to get it running again or am I not getting something?

1 Like

I am hoping to hear something by tomorrow. But as the support cannot promise anything, i cant either…
But i can add info about my FP4.
I bought it around christmas '22 and i tried LineageOS. But i did not want to keep the bootloader unlocked, so i went back to Fairphone OS and stayed with that since that time.

Did anyone have this problem without having tried another OS on the FP4? I did not read anyone exactly stating that, although trULLAs post sounded like she just uses the FairphoneOS.

2 Likes

same issue:
after the Android 13 upgrade and reboot:

  • my FP4 starts
  • displays Fairphone logo
  • blue dot
  • black screen, screen turned on, adb unauthorised
  • after ~2 minutes - black screen, screen turned off, adb unauthorised
  • after ~7 more minutes - screen turned off, adb shows no devices
1 Like