To me it sounds more like a configuration/setup difference.
Which means your phone on the SW side is obviously not the same so it’s not stock. Same non stock as if you reinstall windows on a OEM laptop.
There are several options on the reason in my opinion:
If people for instance flashed A12 instead of A11.
then it could be also that the Factory image is different to the release image (release image has some fixes which have been only patched in stock).
To know if that’s possible we would need to know, if FP4 got manufactured in different batches and if the flash the FP4 images always the same and then update or if they change the image.
Thx!
I reckon, I need to extract the boot.img myself from payload, since it’s not directly included in the ota.zip, is it?
Appearently, the problem seems to sit somewhere else.
Today we had one user, who mentioned he had black screen issues without ever touching the OS or the bootloader.
And we have me, who definately had several custom roms installed and still got the update installed perfectly fine.
No idea, maybe its rather here?
1 Like
I moved that post, as this was rather talking about a screen freezing maybe black, however overall working.
You are my personal hero of the day! 
Thank you very much, that saves me quite some time and effort! 
Hello,
First of all thanks a lot for this thread, it is full of useful advice and hope to me 
I have the black screen problem, in the past I installed LOS but then I went back to FPOS an locked the bootloader again.
Following the comments, I tried two different USB-C docks with the following results.
I am able to see the four blue points dancing until the screen with a clock and a lock appears, but unfortunately no mouse or keyboard inputs looks to have any effect, ofc I tried the sequence space - pin - enter but without luck.
During the tries it happened that the lock screen turned black and pressing the space it came back, because of this I guess the keyboard is working. But no way I can enter the home screen…
I am still resisting to do a factory reset because I have the hope to be able to make a backup of my data…
Any ideas or help would be much appreciated.
Thanks!
1 Like
Hello @Txor ,
What is your keyboard layout ? and what touch did you use ? (num pad ?).
For me, I use a french keyboard (AZERTY) and I notice that the keyboard is by default in QWERTY. I use num pad without problems. If you use numerical touch above letters it can be difficult if you don’t use qwerty.
Keep in mind that you see nothing when you type your pin code.
The mouse is working after enter your pin code and after your phone is unlock.
I hoppe you will resolve your issue.
Julien
2 Likes
Hi all,
I want to share my experience and my thoughts about this issue.
(Sorry for my bad english)
First, I use to have IODE OS before I re install the official rom Android 12 FPOS in september. I went to foreign countries for my hollidays and need the google stack to travel. I take many pictures during my trip and one day I received the notification to upgrade to android 13…
I did it and cannot use my phone anymore for the last week of my hollidays.
My mystakes :
- I didn’t take time to backup. At the beginning of my hollidays I did not have internet but when I applied the upgrade I had so…
- I didn’t reboot the phone before the upgrade.
Fairphone positives things :
- They answer to my support ticket
- They have a community forum (thankfully)
Fairphone things that irritates me.
- When they answer to me, they give me the possibility to send them my phone to restore android but they will erase my datas because of RGPD. I am agree with that procedure but…
- They didn’t give me other option, they just give me basic informations (you have to backup your phone, but I cann’t anymore… You can use a recovery compagny to get back your datas).
I’m a little annoyed and disappointed by the fairphone compagny because they have engineers, they can give me the informations I found in this thread ! They can give other informations about what is going on and how I can try to recover my datas (photos and videos of my trip). They were not helpfull at all about that in the offcial reply. Perhaps there are some fairphone engineers in this forum who give us helpfull informations but the offcial answer to my ticket has to be accurate and more than just an “erase datas” and “use recovery compagny” (IMHO).
Anyway, thanks to all of you for your informations and good tips. It worked for me. I was able to retrieve my data and flash the official ROM android 13 to my FP4.
Thanks
Julien
Received my FP4 from repairs again. Tried the upgrade and receive this error now:
The only thing I can do is reset and then start again from A12
Have you tried again multiple times already?
However, why would you start with A12 after a factory reset? From the yellow part it shows the A13 version, so with the factory reset you can start from scratch with A13.
What have they done at Cordon?
So at Cordon, the have done some “software repairs” and then send the device back. Started it today and it was A12. The update was provided to A13, which I did. After the reboot it gives this screen in recovery. Try again gives me the same issue. Factory reset brings me back to A12 once I restart.
Did you test, because I dont think so. Factory reset does not touch the system it only erases your data and settings.
And thats really without words, why dont they just do the upgrade to check it works this time?
2 Likes
weird, so you did you end up in the other slot with A12 and did you try to update again? If so, I guess easiest would be to unlock the bootloader and do a manual install and tell support what bad work Cordon did.
I guess this will be the way to go… I just hope that once I hand this FP4 to my mother, that this won’t happen with the next big upgrade… Oh man…
Just as a heads up…
I have now proceeded to manually install the A13 Update for the FP4
-
enabling developer options
-
enabling usb-debugging
-
enabling oem-unlock
-
then unlocked the bootloader (normal and critical)
-
changed the Toggles of the flash_fp4_factory.command to the following:
AUTO_REBOOT=“true”
DATA_WIPE=“true”
DRY_RUN=“false”
FRP_WIPE=“true”
INTEGRITY_CHECK=“false”
REBOOT_TO_BOOTLOADER=“true” -
Executed the flash_fp4_factory.cmd and then due to the change of the toggles rebooted into bootloader.
-
Checked again in fastboot mode the current status with fastboot oem device-info (to see that device is still unlocked) and with fastboot flashing get_unlock_ability (to see if it delivers get_unlock_ability=1. Unlock ability was 1 so I relocked the bootloader accordingly.
I am now with Android 13 but I do not know what the heck that repair from Cordon was…
7 Likes
Hi all, thanks for all your helpful comments.
I am in bit of a pickle.
My FP4 screen has been damaged a while back (say 5 weeks ago or so) but it still functioned all right. I figured I would replace it the next time I dropped it if it got worse. Did not happen so far.
Recently, I kept ignoring the update my FP proposed. On the 12th of october, I started facing blackscreen. I do not recall really actively pushing the install update, but it could have happened by an erronous prompt in the touch perhaps. I was however not charging so this is not super likely (unless it can it start installing updates when battery is charged at high percentage but not charging actively).
All of a sudden, the screen does not work anymore. When restarting, the only thing i get is a faint black screen (somewhat lighted). I can shut off the phone by 30sec power button, but in restarting, i get the same black screen (somewhat lighted), no FP logo or blue dot, just but one vibration. Then it is stuck and backlighting goes off. Tricks to go to recovery mode also do not work, nothing on the screen. After that it seems stuck.
-I’ve tried opening the phone, tightening all screws, but also disconnecting and reconnecting the display specifically. Does not change.
-plugging it in the pc generates a “tudohduhtu sound” but no fairphone shows up in ‘this pc’ and thus no change of downloading my data/pics.
The pickle is this:
did
- I accidently push the update to go ahead and i am now facing the “black screen/booting issue”
- my screen stopped working actively because of hardware and only has a bit of black backlighting as a last dance so to speak.
Option 1 Seems a bit unlikely since I had no idea what a “custom ROM” was until today; so i assume i did not have it. 2) Seems unlikely because there was no physical recent trigger at that time and the backlighting gives the idea that the screen still the nondamaged hardware but the software steering it is wrong (so 1).
Tomorrow i will try to connect to the Dock at work which could display something. I am worried the phone will not be generating a VGA output (or whatever output it needs to show stuff on an external screen) before i am logged in with the pin…
PS: also today, it started vibrating obsessively (15 times or so, untill i pushed the power button briefly) as if someone called me. But if i call it myself: voicemail…
Sorry for my lament.
I will keep you posted as to the external screen trials tomorrow.
At the end nothing worked to get past the lock screen.
So I assumed to loose the data and did a factory reset, with this I was able to enter into the Android setup and managed to unlock the bootloader using my USB-C dock, then I installed A13 as explained in the official guide, and now the phone works again.
Well, I like the phone and the company, but loosing time and data because their fault is not acceptable at all…
Hope everyone can get their phones working back.
Thanks a lot for this great thread!
4 Likes
3 posts were merged into an existing topic: Random reboots After android 13 update