Feedback for v3.0

[plank]

Hi folks, I’m new here.
After the 3.0 update on my Fairphone 3 the apparatus rebooted and, after signing in, it rebooted again without my consent or wishes. I’m stuck now with the options in Recovery Version 3.0 which options suggest a “Factory reset”, and also “Apply update”. The reset of course will delete all my data. I see a E/OS 3.0,1 is in the making. Would it be possible to apply the 3.0.1 update through Recovery? I’m not a very technical person.
So any advice on how to proceed is appreciated.

[aibd]

@plank

I see a E/OS 3.0,1 is in the making

You should be able to find this now. Meanwhile the correct way to apply the update for affected phones is in Post #203.

You must establish if you are running official or community and download the appropriate build. This is revealed from your phone’s build_version_string

[obacht]

@Aln

VPN settings → Advanced Privacy Connected → Permanent VPN (grayed out) and Block connections without a VPN (grayed out). I can’t modify these options.

I think that´s how it should look like…
Nevertheless, unless You´ve already done that You could try to → switch off “hide my IP” → delete the AP-VPN in these settings → reboot the device → reestablish the AP-VPN by restarting “hide my IP”.
Could be worth the try…

[Didou]

Vendor Name : Samsung
Device name : Galaxy S7 (SM-G930F)
Device CodeName : herolte
Version of /e/OS or Stock which existed previously : `2.9-s-20250321478216-official-herolte`
Now : `3.0.1-s-20250609498926-official-herolte`
device : Not rooted

All seems OK, thank you team !

[wuestenkatze]

So there was this problem with FP3 's in my case and the newly installed eOS 3.0 crashing and randomly powering off the phone and then requiring a factory reset. I went back to 2.9t. I have now seen that there is an update called 3.0.1 which mentions Advanced VPN causing a crash. Is this the same crash as the one I experienced with the FP3’s?

[soldan]

Vendor Name : Motorola
Device name : Moto G7 Power
Device CodeName : Ocean
Version of /e/OS or Stock which existed previously : `2.9`
Now : `3.0.1`
device : Not rooted

everything works fine, thanks teams

also i have a pixel 5

Vendor Name : Google
Device name : Pixel 5
Device CodeName : redfin
Version of /e/OS or Stock which existed previously : `3.0`
Now : `3.0.1`
device : Not rooted

everything works fine!

[mihi]

Yes it’s that one.

Are you on community or an unlocked FP3 that you were able to switch slots.

[stanwood]

Vendor Name : Fairphone
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 3.0-U Official
Now : 3.0.1-U Official
device : Not rooted

OTA update was done today. Smooth and fast. Everything’s fine, for both my spouse and me. Thank you!

[Meikel]

Vendor Name: Fairphone
Device Name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: 3.0-t-official-FP3
Not rooted

No issues so far. Thanks to the team!

[WikiTang]

---

Quick clarification question about the sideload procedure (FP3)

I’d prefer to double-check everything before trying another sideload, as I’m a bit lost with all the available versions and different download sources.

First, I noticed there are two types of builds:

• official
• community

But then, I’ve seen three different sources for downloading these files:

1. https://ota.ecloud.global/official/FP3/ or https://ota.ecloud.global/community/FP3/
2. https://test.ota.ecloud.global/official/FP3/ or https://test.ota.ecloud.global/community/FP3/
3. https://images.ecloud.global/official/FP3/ or https://images.ecloud.global/community/FP3/

Question: Which of these sources is the correct one to use for a sideload?
Should one be prioritized (for example, number 2)? Or is there even a fourth source I haven’t identified yet?

---

Then, regarding the .zip file used for sideload, I’ve seen specific naming formats like:

e-x.x.x-x-yyyymmddxxxxxx-official-FP3.zip or e-x.x.x-axx-yyyymmddxxxxxx-community-FP3.zip

Is this the right format to use for sideload?
And most importantly:
Should I remove the IMG- prefix from the file name or the download URL if it appears?
I’ve seen comments suggesting that the sideload won’t work if IMG- is included.

Thanks a lot to anyone who can clarify these points

[Didou]

@WikiTang

specific naming formats like:

e-x.x.x-x-yyyymmddxxxxxx-official-FP3.zip or e-x.x.x-axx-yyyymmddxxxxxx-community-FP3.zip

Before A14, the android level was referred to by a letter :
here is the correspondency

[piero]

@WikiTang

Should I remove the IMG- prefix from the file name or the download URL

from the URL.

@aibd

Addendum: The naming convention has changed.

• old dev builds are now named community.
• old stable builds are now named official.

Addendum 2: Android SPL also now ended for AOSP 12 (S) ~ March 2025

please see also Different Build Types

[aibd]

@WikiTang

• official
• community

@piero gave the link above to read the different Build types. If your phone was originally sold to you by Murena then you will have official.

You must be sure of this and you must not sideload community on top of official; with a locked bootloader this must fail.

You must not sideload a build with the prefix IMG. With IMG- prefix the file is not an Update ROM it is a Fastboot Install ROM. The builds are constructed differently for the different purposes.

You must follow Post #203

---

I will assume now your phone was originally from Murena and you had official.

When you follow the recommended source from Smartphone Selector → FP3 Install page → Downloads you find here only Install images.

• The INSTALL file https://images.ecloud.global/official/FP3/IMG-e-3.0.1-t-20250606498724-official-FP3.zip USE FOR NEW INSTALL official ONLY.

To download an Update image we are told to remove IMG- from the URL →

• https://images.ecloud.global/official/FP3/e-3.0.1-t-20250606498724-official-FP3.zip ← this is the Update file suitable for sideload official

---

@WikiTang

Which of these sources is the correct one

The source implies the first part of the url for instance https://test.ota.ecloud.global this is less important. (Seems to me that source was provided as a workaround for the weekend when the main source became unavailable.)

Perhaps bear in mind my earlier comments in Post #323

[graz]

Thank you! That helped me made the choice to confidently update to 3.0.1

[irrlicht]

@irrlicht

Question: where is the OTA update on our second device? It is an FP3+ running 2.9-t. My own device (FP3, then also 2.9-t) had the OTA update already six days ago. Why the difference?

Meanwhile my own device got an OTA update 3.0.0-t → 3.0.1-t.

But the other device is still on 2.9-t. Is there a possibility to trigger an OTA update somehow?

[aibd]

Perhaps try Clear cache and Storage in System updater.

[AnotherElk]

@irrlicht

Is there a possibility to trigger an OTA update somehow?

Apart from working around the staggered release mechanism by hitting the refresh button in the updater several times until the update is offered?
Are you interested in manually applying an OTA update file via ADB or via recovery?

[mihi]

Which devices do you have? Official or Community?

[irrlicht]

FP3 (good), FP3+ (not good) I said

[irrlicht]

@AnotherElk

Apart from working around the staggered release mechanism by hitting the refresh button in the updater several times until the update is offered?

I did this. I also changed the update options (especially “Show all available updates”) back and forth several times, in the past this had often an impact: suddenly an update came - not in this case

@AnotherElk

Are you interested in manually applying an OTA update file via ADB or via recovery?

When nothing else works? I wait still until the weekend is over.