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?
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!
1 Like
Yes it’s that one.
Are you on community or an unlocked FP3 that you were able to switch slots.
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!
2 Likes
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!
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:
officialcommunity
But then, I’ve seen three different sources for downloading these files:
https://ota.ecloud.global/official/FP3/orhttps://ota.ecloud.global/community/FP3/https://test.ota.ecloud.global/official/FP3/orhttps://test.ota.ecloud.global/community/FP3/https://images.ecloud.global/official/FP3/orhttps://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 
Before A14, the android level was referred to by a letter :
here is the correspondency
1 Like
from the URL.
please see also Different Build Types
3 Likes
@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 officialONLY.
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 forsideload official
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
3 Likes
Thank you! That helped me made the choice to confidently update to 3.0.1
1 Like
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?
Perhaps try Clear cache and Storage in System updater.
1 Like
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?
1 Like
Which devices do you have? Official or Community?
1 Like
FP3 (good), FP3+ (not good) I said
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 
When nothing else works? I wait still until the weekend is over.
1 Like
Plesase excues my laziness to check in the posts before 
As @AnotherElk stated hit that button atleast 5 times 
The files for Official and Commumity are online.
First there was 3.0, which got retracted because of considerable trouble, which could have resulted in devices updated already, and devices still waiting.
Then 3.0.1 came, and official or community build type made a difference in the past few days, because 3.0.1 came for official first, then for community just recently. But now the FP3 update files are there for both build types.
@aibd’s hint still applies, if not done already …
Same as yours (Galaxy S7 “herolte”).
I rolled back to 2.9 (from 3.0), because of the GPS issue. Couldn’t use my navigation without Wi-Fi on Airplane Mode. Can you confirm if this is the case with 3.1 release? My problem was that on Airplane mode I wasn’t able to see the satellites, thus not able to use maps in offline mode.
- Vendor Name: Fairphone
- Device name: FP5
- Device CodeName: FP5
- Previous version of /e/OS: 2.5 T
- Installed version: 3.0.1 T (OTA)
- Not rooted
I’ve waited for a while to update to 3.0 as I depend too much on my device for breaking issues. With 3.0.1 I was able to OTA update from 2.5T to 3.0.1T and everything seems to be working.