there were FP3 users that saw the “your data may be corrupt” when applying updates and being scarce on available space. I think it can occur outside of updates too. Can you remember having little space left on the device?
If so, there are some long threads where you free up some space via the recovery (twrp is easiest if on the dev/community builds to mount userdata and delete a video or similar to claw back space quickly).
Quick reminder that on FP3 the bootloader can be locked, and most users have it locked, because the phone came this way or because it’s part of the official install guide and the more secure state of the phone.
Using TWRP on a Fairphone 3/3+ in a situation like this here requires a bootloader left unlocked. Unlocking it now would force a factory reset, wiping the data.
@Sterero: Please reboot to fastboot mode (aka bootloader) … if in doubt how to, just reboot and keep Vol - pressed until fastboot mode appears. One of the last lines of text there will say Device State: Locked, or Unlocked.
Which is it for you?
And as you didn’t mention it … have you already simply tried the “Try again” option visible in your screenshot?
Sometimes this actually works (against justified technical intuition), I’ve seen this myself.
Thank you for your message! This is not my phone. I’ve asked the owner regarding scarce space and she told me she had a message that she should free up some space. So I think you are right. Unfortunately bootloader is locked
As you’re already a linux user, you can give this a shot: Fairphone shuts down after entering pin and goes into recovery mode - #7 by tcecyk - that post links another long thread where multiple users go through the motions to varying degrees. The procedure is successful even on a locked FP3 (you delete blindly to free up space - but the group ownership of the files give away their type).
With locked bootloader, things will be tricky. If the issue is low storage, deleting some files through recovery (like mentioned in that thread) might help free up space and let the phone boot properly.
If that doesn’t work, you could try connecting the phone to a computer and see if ADB lets you pull some important files before resetting (though not all stock recoveries allow that). Worth a shot if you’re comfortable with it.
Worst case, if you have to reset, recovery tools “MIGHT” be able to bring back some files, but it really depends on whether new data has overwritten them. If the owner really needs something back, tell them to stop using the phone immediately after the reset to improve their chances.
When I had this issue I did ‘Try again’ like 5 times then it would load to the other slot and older version and it would boot That only works if you update and then that problem occured…