Feedback for v3.0

Google
Pixel 5
redfin
2.9-t
Not rooted

Everything is fine so far. The update went very fast compared to every update up to v2.8 and it didn’t require a second reboot as it did before.
No problems with AppLounge right now, it failed to install all available updates and had severe problems with f-droid apps in the past, maybe that’s solved now.
The stock camera app was unusable so far, I don’t know if that has changed with v3.0 because I removed it and installed an GCam port instead. I had the stock camera app until a few weeks ago so the issue existed on this phone at least until recently.

That’s it for now, as always many thanks to the Murena team!

Urgent Help needed - My phone doesn’t work after the OTA :rotating_light:

  • Vendor Name : Google
  • Device name : Pixel 5
  • Device CodeName : Redfin
  • Version of /e/OS or Stock which existed previously : 2.9-t Official
  • Is the device Rooted / Not rooted : Not rooted

The issue : After downloading the update OTA via the settings → Update, the phone has restarted normally. I was asked (as usual) to enter the pin code of my phone and once I entered it then the phone restarted automatically and the screen show “Recovery screen Version 3.0 Active slot : a”
“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.”
I then have two choices :

  • Try Again
  • Factory data reset

I selected “Try again” but it did not change anything, the phone has restarted and again I was asked to enter the pin code of my phone and once I entered it then the phone restarted automatically and the screen show “Recovery screen”.

This phone is my daily driver and I need to recover it asap. Please help me to solve this issue :pray:

2 Likes

Capture d’écran 2025-06-03 à 21.37.25

Do we have a way to test that beaconDB is properly used by default, and not the old proxy?

1 Like

Check on the settings :woman_shrugging::woman_shrugging:

In the microG settings, there is for sure a toggle allowing for /e/OS to select their own default location provider. But I’m looking for a way to prove that before v3.0 it was reaching a proxy for a commercial provider, and that now it reaches the API of beaconDB.

1 Like

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

Notified of update, went smoothly, all seems well from initial checks, will monitor.
My big thank you to the Team

1 Like

Samsung
Galaxy S7 (SM-G930F)
herolte
before: 2.9-s-20250321478216-official-herolte
now: 3.0-s-20250528496287-official-herolte
not Rooted

Thanks a lot for keeping that hardware alive!

… all well, no issues from what I see so far…
besides residues of MDM-implementation that still state the device´d be owned by my organization

edit: comment in reopened gitlab-ticket

1 Like
Vendor Name : Samsung
Device name: Galaxy S7
Device CodeName: herolte
Version of /e/OS or Stock which existed previously: 2.9-s
Is the device Rooted / Not rooted: Not rooted

Same return as obacht
:oP

1 Like

:rotating_light: Urgent Help needed - My phone doesn’t work after the OTA eOS 3.0 update :rotating_light:

  • Vendor Name : Google
  • Device name : Pixel 5
  • Device CodeName : Redfin
  • Version of /e/OS or Stock which existed previously : 2.9-t Official
  • Is the device Rooted / Not rooted : Not rooted

You can find a video of the issue here : Telegram: View @murena_event

The issue : After downloading the update OTA via the settings → Update, the phone has restarted normally. I was asked (as usual) to enter the pin code of my phone and once I entered it then the phone restarted automatically and the screen show “Recovery screen Version 3.0 Active slot : a”
“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.”
I then have two choices :

  • Try Again
  • Factory data reset

I selected “Try again” but it did not change anything, the phone has restarted and again I was asked to enter the pin code of my phone and once I entered it then the phone restarted automatically and the screen show “Recovery screen”.

This phone is my daily driver and I need to recover it asap. Please help me to solve this issue :pray:

Support ticket created here : 🚨 eOS V3.0 OTA update failed - Help please - #3

1 Like

hey,

I think i had this too when i flashed my fairphone 5.

it was fixed for me by using a different usb cable and usb port. i redid al the steps again from the murena website to flash my phone.

when it comes to failures, always rule out the possible causes. OTA is always a bit jank.

Hi Wasbeer, thank you for your response.
I did not use a USB cable as the update was OTA (directly downloaded from the phone via 5G data).
I did this procedure several times before, for each last new updates but never had an issue until now…
In this case you are advising to reflash the phone, this mean that I would lost all my data if my understanding of your advice is correct?

unfortunately, yes.

and always apply the 321 backup procedure next time.

we have all learnt this the wrong way.

Maybe you are in luck and you can still mount your phone to your computer as a drive and extract your files using a usb cable.

But before reflashing, wait till some of the experts possibly supply a solution.

I’m just a random guy on the internet.

Why don’t you install fastboot/adb like I told you…

G’day,

I have an Oneplus 8T with /e/OS 2.69.
Tonight I download in settings phone the update 3.0 and install it. It was OK until the phone ask to reboot.
Since the reboot my 8T boot in loop
After few hours to seach why I have this problem on each update … I found the point …

On my phone, /e/Os is install on slot B (I don’t know if it’s normal) but when update the phone, the reboot does on slot A… so there is no OS.

To solve it, I switch to slot B and it works and I still have my datas.

I don’t know if this situation is normal. Maybe someone have some advices.

++

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

1 Like

@Anonymous Switch to other slot !

Vendor Name: Xiaomi
Device name: K40 pro
Device CodeName: Haydn
Previous Version: 3.0 beta 4

It for some reason, did not receive OTA update.
Therefore, I downloaded the zip myself and successfully update by using local update option.
I have not observed any problem after update.

Thank you

Galaxy S7 “herolte” SM-G930F
Not rooted
Dirty installation from:
e-2.9-s-20250321478216-official-herolte.zip

Via /e/OS updater built in the system.

My updated download is:
e-3.0-s-20250528496287-official-herolte

The ROM is working flawlessly, banking apps are working, communicators working.
The browsing is faster and smoother than previous release, especially in Brave.

After installation did clear cache for all apps, and formatted cache partition, so far no problems.

Thank you for a great work!

1 Like

Hi Roos, thanks for your feedback.
Would you be able to explain to me the process or do you have a link for me to follow the process?

Thanks for your response, how can I do that please?

@piero Does switching slots also work with locked bootloader?

2 Likes