Feedback for v3.0

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 :+1:

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 :+1:

I currently haven’t updated my FP4, because of the issues reported here.

1 Like
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.

1 Like

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

1 Like

Do you have a locked bootloader ?

If NO, you can switch to slot A, where the working previous version 2.9 should be located.

1 Like

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.

1 Like

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.

1 Like

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:

  1. Is there a way to fix it without a factory reset?

  2. 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.

1 Like

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:

  1. Is there a way to fix it without a factory reset?
  2. 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


2 Likes

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

2 Likes

[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 :pray:


[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 :pray:

2 Likes