Feedback for v3.0

/e/OS Smartphone Operating System Build Feedback
106

[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
107

[FR]

Bonjour,
Je suis bloqué suite à une mise à jour OTA qui a planté mon Fairphone 3+. Le téléphone démarre uniquement sur l’écran de récupération “Recovery 3.0” avec le message :

“Can’t load Android system. Your data may be corrupt…”
Et les options : “Try again” ou “Factory data reset”.

Comme je ne veux pas perdre mes données, j’essaie de passer par l’option “Apply update” > “Apply from ADB”, mais quand je tente d’installer un fichier .zip via adb sideload, j’obtiens :

Install completed with status 3.
Installation aborted.

J’ai compris que les fichiers nommés IMG-e-... ne sont pas faits pour être installés en sideload. Il faudrait plutôt un fichier comme e-3.0-t-...-FP3.zip, mais je ne sais pas où le trouver ou s’il est compatible.

Je pense devoir flasher un recovery adapté (officiel ou TWRP compatible), mais pour ça, je dois passer le téléphone en mode fastboot et trouver le bon fichier .img de recovery pour le FP3+ (version eOS 3.0-t).

Est-ce que quelqu’un peut :

  • me confirmer cette démarche ?
  • m’indiquer un lien vers le bon fichier recovery ?
  • me dire si cette méthode risque de supprimer mes données ?

Merci pour votre aide :pray:

[EN]

Hi,
I’m stuck after an OTA update failed on my Fairphone 3+. The phone now only boots into the “Recovery 3.0” screen, showing:

“Can’t load Android system. Your data may be corrupt…”
And options: “Try again” or “Factory data reset”.

Since I don’t want to lose my data, I tried going through “Apply update” > “Apply from ADB”, but when I attempt to install a .zip file via adb sideload, I get this error:

Install completed with status 3.
Installation aborted.

I’ve learned that files named IMG-e-... are not sideloadable. It seems I need something like e-3.0-t-...-FP3.zip, but I don’t know where to find it or whether it’s compatible.

I believe I now need to flash a working recovery image (official or a compatible TWRP), but that requires switching the device to fastboot mode and using the correct .img file for the FP3+ (with eOS 3.0-t).

Could someone please:

  • confirm if this is the right approach?
  • point me to the correct recovery image?
  • let me know if this process would wipe my data?

Thanks a lot for any help :pray:

1 Like
108

You are mixing tools and modes

  • bootloader mode → .img → fastboot
  • recovery mode → .zip → adb (or SDcard)

Here is the file you need using recovery :
https://ota.ecloud.global/official/FP3/e-3.0-t-20250528496286-official-FP3.zip

1 Like
109
  • Vendor Name : Motorola
  • Device name : Edge 30
  • Device CodeName : Dubai
  • Version of /e/OS or Stock which existed previously : 2.9-U Community
  • Is the device Rooted / Not rooted : Not rooted
    Everything works, even Find My Device, but Location isn’t precise enough. Somewhere within 500m Radius.
    Thanks for the nice built.
110

Hi,

It looks like I may need to switch to bootloader mode, because I haven’t been able to perform the ADB sideload update from recovery using this file:

:point_right: https://ota.ecloud.global/official/FP3/e-3.0-t-20250528496286-official-FP3.zip

I also tried with this one, which got a bit further but ultimately ended with the same issue (signature verification failed or status 21):

:point_right: https://ota.ecloud.global/community/FP3/e-3.0-a14-20250529496779-community-FP3.zip

So I suspect that I now need to flash a new recovery image manually, likely via:

fastboot flash recovery recovery-e-3.0-…img

To do this, I believe I need the exact .img file for /e/OS 3.0-t and the Fairphone 3+.
Could someone please help me locate the correct recovery image?

Thanks

111
  • Vendor Name: OnePlus
  • Device name: Nord
  • Device CodeName: avicii
  • Version of /e/OS or Stock which existed previously: /e/OS 2.9-a12
  • Is the device Rooted / Not rooted: Not rooted

Seem good so far

112
  • Vendor Name: Fairphone
  • Device name: Fairphone 5
  • Device CodeName: FP5
  • Version of /e/OS or Stock which existed previously: 2.9 e/os
  • Is the device: Not rooted

After download of the update and reboot thr device ended in “corrupted state” as it was reported by some users already.
Option to use Factory reset helped, and I am now running 3.0. Restored everything from backups.

This just proves the need for backups. Not just for photos, but also app data (mfa, …) and other types as well.

2 Likes
113

Yeah I know. I specifically bought an FP5 over the FP4 only because of 90hz display, which is now longer broken than working since I bought it from Murena. My next big hope lies in the Android 14 Upgrade wich should be coming “soon”.

1 Like
114

“soon” is the equivalent to Elon Musks “two weeks”. :wink:

1 Like
115

You could boot into bootloader (aka fastboot mode) and try whether you can switch the slot to A with the fastboot set_active a command.

I suspect your bootloader is locked (if you didn’t actively unlock it yourself). Switching the slot manually might be forbidden on FP3 devices with a locked bootloader, but then we’ll at least know.

It’s not rooted. Rooting is something you have to do yourself after hopefully enough research about how to do it and what the consequences are.

Which steps exactly are you taking to do this, and what exactly is the result on screen?

Worst case could be that by attempting to switch the build type you just triggered the OS to really require a factory reset to boot.

There is no recovery partition on FP3 devices, the recovery is embedded in the boot partition.
If you are feeling adventurous, the partition images are in the update ZIP file for fastboot (filename starting with “IMG”).
The download page doesn’t show them yet, but substituting the new version string into the available 2.9 version links it seems these files already exist …

https://images.ecloud.global/official/FP3/IMG-e-3.0-t-20250528496286-official-FP3.zip

MD5: https://images.ecloud.global/official/FP3/IMG-e-3.0-t-20250528496286-official-FP3.zip.md5sum

SHA256: https://images.ecloud.global/official/FP3/IMG-e-3.0-t-20250528496286-official-FP3.zip.sha256sum

4 Likes
116

Vendor Name: Fairphone
Device name: FP5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 2.9 official
Not rooted

Major issues! Device boots, show launcher (which was not Bliss btw) and then reboot. Goes into recovery and shows:

Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

If I don’t unlock my phone, it stays on. So it is something post unlocking that causes the phone to shut down.
Booting into safe mode makes no difference.

117

@Manoj: Here’s what’s happening for me.

I left my smartphone turned off for several hours. When I started it up, it asked me to enter my PIN, then it immediately shut down. I restarted the smartphone and got the recovery screen. I pressed ‘Try again’ and the device started up normally. I entered my PIN and got the interface. Yesterday, I used the device for a while (internet), no problem. I shut down and restarted the device several times in a row, and the system started normally (no Recovery screen). I noticed one thing: when I go to the left screen (shortcuts, advanced privacy options, weather), all the advanced privacy options are in red, and access to these options is blocked. I have to go through the settings to get these options to work. Then, they are active again on the left screen. I don’t think the bootloader is locked. I don’t have any parental controls enabled, nor any additional options enabled (Find my device). Now, I don’t know what to do, wait for a new update ?

118

When the system started did it start on 2.9 or 3.0

119

Galaxy S7 “herolte” SM-G930F
Not rooted
Fresh install after full Format Data and then Wipe from TWRP.

My download is:
e-2.9-s-20250321478216-official-herolte.zip

And then Updated to:
e-3.0-s-20250528496287-official-herolte

Found major problem with the calls, involving microphone

People who are calling me are telling me that they are hearing themselves, even when I’m not using a loudspeaker. Verified it on other phones, and it’s a problem on my end, because when I cover my lower microphone near USB port, they are not hearing themselves. So it’s probably the ROM problem involving managing microphones. My phone is in mint condition, not even a scratch and not dirt.

120

The system information told me that I’m on 3.0 official.

121

This is very strange, I should try to reproduce !

EDIT : have you try call before flashing

??

122

I think on both ROM’s were the same 2.9 and 3.0.
My mother called me like 1 week ago, and I didn’t update yet. She was complaining about it, but I ignored it, because it was in the bathroom, so I assumed it was the bathroom problem, but it probably was the same problem.

Now I checked and when I’m disabling microphone on my end (by clicking from the call menu), they don’t hear themselves anymore.

I could downgrade to stock ROM, but I’m afraid that something could go wrong, and I don’t want to lose my data. But if you tell me to do this, I will do it.

123

I don’t have this issue with my SM-G930FD, but this is a slightly different device.
I own another one witch is 930F, so I will try to reproduce. If I manage to find time ^^

124

It would be perfect. This would eliminate if it’s only my problem, but I doubt. Because again, disabling microphone from the menu when somebody is calling me, or physically covering the lower microphone, eliminates this problem

125

Thanks for the update. Ill quickly answer the points for my case:

  • The bootloader is locked yes, I have never unlocked it either or changed to a custom ROM
  • Its running an official build, it was on the most current v2.9-a14 before the update, no other updates were available
  • Im afraid I cant send a log anymore because in my case im already stuck in fastboot and cant boot into recovery anymore
  • Im not using premium services
  • Parental Controls were not activated on the device
  • There were no other users on the system
  • The default language was english (UK)
  • Hide my IP was activated
  • The other advanced privacy tools (tracker blocking and location spoofing) were activated aswell
  • Find my device was not setup yet or activated
  • My location was Berlin, Germany
  • I was using lawnchair for theming
  • I did not have the murena cloud setup

After Update:

  • The system was successfully updated to 3.0
  • The phone rebooted into recovery noticably rhythmically every 8-10 minutes
  • Initially I thought it was caused by the lockscreens ambient display (whatever thats called) but the issue persisted after deactivation
  • Charging / not charging dident change anything either
  • I got stuck in fastboot after attempting to backup data via adb, the connection was cut due to another reboot
  • After reboot the message “Your device is corrupt. It can’t be trusted and will not boot” appeared
  • Pressing restart booted directly into the fastboot menu

If you have any other questions I would be happy to help!

Also, in my case, do you think I will realisically be able to recover the data on the device? Given that im stuck in fastboot, im not sure how I would apply any updates. Im guessing I will have to send in the phone which will result in a wipe?

1 Like