Same situation here with a Fairphone 3. I posted about it in the wrong place, but I think it will be merged here.
2nd device:
- Vendor Name: Fairphone
- Device name: Fairphone 3
- Device CodeName: FP3
- Version of /e/OS or Stock which existed previously: 2.9 T official
- Not rooted
No problems
3rd device:
- Vendor Name: Samsung
- Device name: S5e (wifi)
- Device CodeName: gts4lvwifi
- Version of /e/OS or Stock which existed previously: 2.9-a14 community
- Not rooted
No problems
I currently havenât updated my FP4, because of the issues reported here.
Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9 officiel
Not rooted
Works for me.
Since I posted in the wrong place at first, my Fairphone 3 constantly powers off and restarts after update 3.0. I canât get past the pin screens for more than a few seconds. Then I get the message
âCanât load Android system. Your data may be corruptâŠâ
Then it proposes a âfactory resetâ to me, but I would like to avoid it if possible (my last backup of my contacts isnât that recent unfortunately).
Edit: is there some sort of log I should provide?
Vendor name: Fairphone
Device name: FP3
Active slot: âbâ
Previous working version of e/OS: 2.9
Do you have a locked bootloader ?
If NO, you can switch to slot A, where the working previous version 2.9 should be located.
Would this work with locked boot loader?
I think my bootloader is locked, since I donât have the option to switch and I get the âDevice state - lockedâ flag in the bootloader sceen.
The FP3 can be unlocked in fastboot
-mode with this method.
But all data will be lost.
Do you happen to know of an unlock method for the FP4?
This wonât work for the FP4. The FP4 only can be unlocked in EDL
-Mode having the suitable firehose loader, which is not available to public.
I have the exact same issue. Hoping for a permanent fix soon as this is quite annoying.
Vendor Name : Google
Device name : Pixel 3 XL
Device CodeName : crosshatch
Version of /e/OS or Stock which existed previously : 2.9
Is the device Rooted / Not rooted : Not rooted
@Manoj still a huge lag when launch camera FYI.
After many updates going well, the 3.0 update got me stuck in the recovery mode, with a âCanât load Android system. Your data maybe corruptâ. I have two questions:
-
Is there a way to fix it without a factory reset?
-
If I need to do a factory reset, how can I backup my personal data from a computer first?
Vendor Name : Fairphone
Device name : FP5
Device CodeName : I canât answer because my phone is turning off when i unlock it.
Version of /e/OS or Stock which existed previously I canât answer because my phone is turning off when i unlock it. But I had the latest (previous) update
Is the device Rooted / Not rooted i supposed it is not rooted (e/os was installed when i buy the phone).
Ty by advance
Vendor name: BQ
Device name: BQ Aquaris XPRO
Device CodeName: âbardockproâ
Version of /e/OS or Stock which existed previously: 2.9-t-20250326478876-community-bardockpro
Updated to: 3.0-t-20250531497058-community-bardock-pro
Is the device Rooted? Yes
So far so good. No issues & everythingâs working fine as before, including the battery, which continues to work remarkably well. I had to install the previous /e/OS version manually since no OTA upgrade was available as I posted here.
Many thanks for continued support for this device.
No response at all. Leaving it on charge for 30 minutes there is no heat detected. Tried different chargers/USB cables.
Screen remains black.
Dear Community,
After many updates going well, the 3.0 update got me stuck in the recovery mode, with a âCanât load Android system. Your data maybe corruptâ. I have two questions:
- Is there a way to fix it without a factory reset?
- If I need to do a factory reset, how can I backup my personal data from a computer first? Is it possible with the system instantly rebooting after entering the two pins?
My Phone is a Fairphone 3.
Hi there, I have the same issue on the FP4. Its been happening to quite a few people. I have not found a way to access my files nor to actually reset it (even if that deletes the files).
If you check the âFeedback for v3.0â thread you will see the other posts. This one will be merged there anyway.
@Manoj as you are going to be closing this and hence will see this thread 100%, please would you mind responding in the main âFeedback for v3.0â thread?? We are patiently waiting for a response from your team after your update bricked our phones! As I (and most others) do not have a bunch of replacement phones lying around it would be great if you could prioritize this a little more than the closing of these threadsâŠ
Hi,
Same matter with fariphone 5. And i have the same questions than PensiveJellyfish.
Ty.
The issue being faced by some FP4 official build users has been passed back to the build team. Awaiting a response from them. Should have some updates by EU work hours later today.
Update:
The team has asked for a few inputs to help debug this issue: We want to check all possible reasons behind this
- Are all these FP4 devices bootloader locked
- Assuming that we are all on the official builds âŠany community build user with FP4 facing this issue
- Would it be possible to get a log before the reboot happens
- Are any of the users on premium accounts. That is with additional storage on the Murena cloud.
- Were Parental Controls activated on the device.
- Do you have multiple users on the syste
- What is the default language on the phone
- Is Hide my IP activated
Any additional details you can share like location , Find my device or any other of the features that were activated
[FR] Jâai exactement le mĂȘme problĂšme ; mais jâai âActive slot : Bâ
Mon appareil est un Fairphone 3+, il est probablement rootĂ© (je ne suis pas sĂ»r, je lâai achetĂ© directement sur le site/shop de Murena.OS).
Comment est-ce quâon peut rĂ©soudre ce souci ? Est-ce quâil nây aurait pas moyen dâutiliser lâoption âApply updateâ â âApply from ADBâ dans le mode recovery ?
Mon tĂ©lĂ©phone Ă©tait bien configurĂ© avec ADB activĂ©, donc je me dis que câest peut-ĂȘtre faisable.
Est-ce quâil serait possible de :
- télécharger une version fonctionnelle de la recovery ?
- ou bien la mise à jour 3.0 spécifique au Fairphone 3+ ?
et ensuite lâinstaller via ADB sideload ?
Quand jâessaie cette mĂ©thode, voici ce que jâobtiens Ă lâĂ©cran (en deux blocs de deux lignes) :
Install completed with status 3.
Installation aborted.
Now send the package you want to apply to
the device with "adb sideload <filename>"...
Merci dâavance pour toute aide
[EN] Iâm experiencing exactly the same issue ; but with âActive slot bâ
My device is a Fairphone 3+, and itâs probably rooted (not entirely sure â I bought it directly from the Murena.OS shop/site).
How can we fix this?
Is there any way to use the âApply updateâ â âApply from ADBâ option from the recovery screen?
My phone was properly set up with ADB enabled, so Iâm wondering if this method could work.
Would it be possible to:
- download a working version of the recovery, or
- the specific 3.0 update for the Fairphone 3+,
and then install it via ADB sideload?
When I try this method, I get the following output on screen (in two blocks of two lines):
Install completed with status 3.
Installation aborted.
Now send the package you want to apply to
the device with "adb sideload <filename>"...
Thanks in advance for any help