Feedback for v3.0

/e/OS Smartphone Operating System Build Feedback
147

Hello,
Reboot trouble for me too after update this morning with FP4 (3.0-a14-20250528496285-official-FP4). Some precisions about my trouble :

  • Reboot occured a first time immediately and sometimes after few minutes (~5) even in safe mode (all app deactivated) with airplane mode activated. Phone seems functional during few minutes (I was able to save contacts).
  • I noticed after update that “advanced privacy” settings have automatically been turned off on home but that is not true.
  • It seems better I now turned off 3 “advanced privacy” settings (21 min without crashing now).

Anwsers to your questions :

  • FP4 devices bootloader locked : No
  • Official builds : yes (automatically downloaded since 1st installation)
  • Would it be possible to get a log before the reboot happens : It might be possible, if I can access it quickly. How can we get a log ? I can access to “recovery log”.
  • User on premium accounts. That is with additional storage on the Murena cloud : No
  • Were Parental Controls activated on the device : No
  • Multiple users on the system : No
  • Default language on the phone : French (France)
  • Is Hide my IP activated : I turned it off before to download update.

:tada: Edit : 2h35 without crash now…

2 Likes
148

Thanks @fgervais for the tips of disabling the “advanced privacy” features. I got the same problem here, it’s very annoying and I still don’t understand what I should do to fix it

149

I’m still having issues with my mails, When I turn on 2FA, I can’t sync my mails with the mail app because the password I use to connect my account is a generated one and when I change my password to the right one in the mail app settings, it keeps being changed by the wrong generated one.
It’s really annoying because I can’t stop the mail app to work and change it by another one, so I just have to turn off 2FA.
Will there be a fix for that issue ?

2 Likes
150

Did you succeed to fix it ? without factory data reset ?

151

Did you succeed to fix it now ?

152
153

Hi Mir4d0r, unfortunately not.
I’m trying to investigate with the Murena Team.
I’ll keep everyone updated here as soon as there is any progress.

1 Like
154

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

Citation If you are feeling adventurous, the partition images are in the update ZIP file for fastboot (filename starting with “IMG”).

With the phone in bootloader mode, I tried switching the active slot manually with fastboot set_active — and it worked.

Then, still in bootloader mode, I tried:

bash
fastboot flash boot boot.img

But I got this error:

FAILED (remote: 'partition flashing is not allowed')

So it seems the bootloader is locked, which prevents flashing partitions.

You mentioned:

“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.”

And honestly, I’m afraid that might be the case now.

I was able to force an ADB sideload update with this package:

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

Now here’s the issue:

→ The phone boots up normally,
→ But as soon as I unlock the lock screen (pattern), it automatically reboots into recovery mode with the “Can’t load Android system…” screen. Erratum, now it’s impossible to boot to lock screen with slot a.

So I guess this is due to a build mismatch or a corrupted/inconsistent state, and I’m still trying to find a way to fix it without losing data, if possible.

155

Unfortunately not yet. To make matters worse, backups have been made, but last months the uploads have failed for some reason. So I’m really hoping for a solution.

Will also contribute as many details as possible here.

156

What about sideloading 2.9?

157

Doesn’t one need to enable USB debugging for this? If @WikiTang experiences the same as I do, there’s not enough time to do this (few second between unlocking and forced reboot). Or do I forget something?

158

You can ‘adb sideload’ from eRecovery

159

In my case at least, that option is not offered in eRecovery.

160

Citation What about sideloading 2.9?

I actually tried that, but the system explicitly blocks the downgrade.

Both slots (A and B) already have /e/OS 3.0 installed, and when I try sideloading a 2.9 version — even the correct one for my device — I get signature verification errors or status 21.

The recovery refuses to install older builds over newer ones. So unfortunately, downgrading to 2.9 via adb sideload isn’t allowed. The system sees it as an unsafe operation.

To go back to 2.9, I would need to fully wipe the device (factory reset or flash via fastboot), which I want to avoid in order to preserve my data.

So at this point, I’m hoping for a fix or patch that can be sideloaded over 3.0.

1 Like
161

Hmm, then lets hope there will be a 3.0.1 soon and users can sideload it. Thank you @WikiTang for your efforts.

@theredspecial ‘Apply update’->‘Apply from ADB’

162

the “echo-problem” is a known issue for S7, it is not new and can (or will) not be fixed.
It seems to vary depending on unknown parameters somehow → some receivers complain, some don´t …

The only safe workaround that I know is using a headset.

1 Like
163

Citation Thank you @WikiTang for your efforts.

I feel truly upset and even angry, because this phone represents a real investment for me, and it holds important files I deeply care about.
I put my trust in this system, and right now I feel that this trust has been broken.
What I need most is practical support — especially a way to recover my data without having to erase everything.

1 Like
164

No problems with V3 so far. Runs nice and smooth on a OP8T. Takes to using dual sims perfectly. Only issue I have found is not with the OS but with Micro G. The F Droid keeps showing an update available for Micro G and its companion app but when I try to install it shows an error. {This app was built for an older version of android and can not be installed automatically}
Micro G is still working fine so I am not bothered about a late update. Just posting in case others encounter this.
Thanks for a great system!!! Been here since the early announcement of E OS and haven’t been disappointed yet.
Have a great day!

1 Like
165
  • Vendor Name: Xiaomi
  • Device name: Poco X3 Pro
  • Device CodeName: vayu
  • Version of /e/OS or Stock which existed previously: 2.9 T Community (actually on: 3.0-t-20250531497057-community-vayu)
  • The device is not rooted

Everything works well no issues so far.
Great job and thank you to all the team

166
  • Vendor Name: Nothing
  • Device name: CMF Phone 1
  • Device CodeName: Tetris
  • Version of /e/OS: e-2.9-a14-20250321478214-official-tetris
    -Is the device Rooted / Not rooted: Not rooted

Update went well and seems to work as well as.

On boot it still gives the orange state 5 sec. message (hoped that would disappear)

Big thanks to E team!