No update since October

Using /e/OS
, ,
1

Hi,
maybe someone can help me. My Fairphone 5 is running /e/OS 3.2. Which is, according to the system updater, the most current version, and there are no updates available.

But because since October /e/OS 3.3 and 3.4 were released, I am wondering if my phone might not have all the information available.
Or is the FP5 at a dead end? The newer updates spell out changes for the FP5, so that is probably not the case.

Can anyone give me a hint as to what might cause this behavior and what can I do to get access to a current system version?

Many thanks in advance!
Per

EDIT: Please excuse that I didn’t add all the necessary info at once.
I hope I got everything:
Phone model: FP5
Android version: 13
/e/OS version: 3.2-beta.2-t-20251004532706-official-FP5
My problem: it appears that newer versions of /e/OS are available, but my phone doesn’t update.

3

Thank you for your info.
I am not sure I understand the images you sent. Are those the versions available?
I would not be surprised if I miss something very obvious to anyone. If I am, I am sorry – I don’t mean to be wasting your time.

4

so it is the last android 13 (t) based beta test version.

go to --> settings --> system --> developer options, and disable the “test release channel”
then go back to --> settings --> updater, and try to refresh,

what do you see ?

2 Likes
5

You realise that you have the Testing channel turned on in Developer options? You should turn that off.

Then clear storage in Updater, restart the phone and try to update. If this fails someone can help with manual update.

2 Likes
6

Thanks for pointing that out! I am not sure why that was even activated. Probably it seemed like a good idea at the time … :see_no_evil_monkey:

I am not sure what you mean with “clear storage in Updater” – do you mean “App Info” for the settings app? Or is there another place where I can clear storage?

When I just deactivate the beta channel and restart, the updater still shows no updates.

EDIT: Okay, I found where to clear storage on the updater (App list → three dots → show System apps → “Updater” → storage → Clear storage)
It still shows no updates, though.

7

From the Telegram group (testing group) I know that local update is possible. If you should take the files from test server or regular one, I can’t tell. When someone wants to use test channel then my understanding is that a fresh install is needed because different keys are used :man_shrugging::man_shrugging:

I can provide links later or some one else but they should not be with IMG… in the file name → @aibd posted the regular one

Oh and be aware that you have Android t(a13) but now is a15

2 Likes
9

Post deleted, as pointed out by @mihi and @piero, there is more than one thing to consider here due to you seeming out of phase for the OTA Upgrade

I suggest to invest a bit of time in ensuring that you have a backup of essentials.

2 Likes
10

Oh, thank you for your help! I didn’t foresee I would get myself into such a pickle with that. (Developer options have such a complicated way to get into for a reason … I remember having felt less of a fool than I do right now.)

That means I will probably have to do a complete reinstall, and a Seedvault backup would probably not help, because that includes the system, right?

11

Go for it. Some say Seedvault on a13 (T) is a little “awkward”, but it is worth having … if it works on this device. No backup of system is included.

Think also how best to backup other things … Murena, if used, potentially contains a lot. I suggest a backup of SMS manually (if required) should be possible from within the app.

As you set up Seedvault watch for what is included / excluded.

1 Like
12

you need to refresh more than 3 or 7 time

no, as @mihi said : I know that local update is possible.

clic to see how !
1 Like
13

@aibd I would also suggest doing that it was also suggested like that in the testing group with a brocken upfate path for avicii

@Civetto As suggested try to do a backup with seedvault it can backup appdata and system settings, but not files. The disclaimer that it is experimental is true and it doesn’t work properly (with higher Android version like a15, Seedvault can do like a device backup with everything, did it 2 weeks ago). After you have a backup try local update and maybe let us know what the ‘keys’ say in the system info setting

1 Like
14

Thanks, this refers to the idea of local update to perform Upgrade of Android version – I suggested this in my deleted post. It should (probably) work but is not part of the documented methods.

But where users want and expect stable official the mix with “testing” seems non optimal.

Users who feel confident to be testing should ofc go ahead.

To turn back from testing … a fresh install ensures a clean start.

2 Likes
15

Merci bien, danke schön and thank you all very much for your kind efforts to help me wriggle out of the mess I got myself into.
Things look way less bleak to me now. :blush:

In the How-To piero kindly posted, there is a link “download the latest /e/OS build for your device”. On the page it leads me to, for the FP5, I have the option to run the /e/OS installer or to build my own, no download link – or did I miss it?
I found this page, is that what I need? /e/OS stable FP5 download
If so: Right now, I have /e/OS 3.2 on my phone. Should I download 3.2 from that page, and update the intended way later, or should I go for 3.4 directly?

Many thanks again for your kind support.

16

The flow of official FP5 pages starts at

omitting eosinstaller the Command line install page is

and from there links the Download page you correctly found

If you plan a fresh install just take the newest build … what is on the phone will be totally wiped by the install script so there is no need to consider what is there now.

1 Like
17

Thank you. I was under the impression that with the latest /e/OS build as a download I could avoid doing a fresh install, which would definetely be my preferred solution.

So, if I just want to update vom the test channel to the stable version, should I rather update 3.2beta → 3.2, or could I update to 3.4 directly?

18

To break it down further … you would like to change out of official Testing … but it seems you will have to Upgrade Android version.

It seems that the last official published a13 (T) build was e-3.1.4-t-20250915526530-official-FP5 … this, I think, points to the reason you had no Upgrade since October … It seems the correct OTA Android version upgrade path was broken somehow. [1], [2]

This proposal would be the Android version Upgrade 3.2-beta-a13 to 3.2-a15. (“3.4-a15 directly” is I think of less significance, as change of keys is the likely potential point of fail.) The suggestions from @piero and @mihi describe how this can be accomplished via Local update.

[1] The official documented sources would indicate a Fresh install to fix.
[2] e-3.1.4-t-20250915526530-official-FP5.zip
"is_upgrade_supported": true

1 Like
19

Latest official OTA is 3.4 (see Builds – Django REST framework).

Example how to manual (‘local’) install an OTA upgrade here (german language for Fairphone 3).

1 Like
20

to do it, you have several options :

1 Like
21

Thank you all very much for your kind support. After making sure I had everything backed up sufficiently in case of the next phase of my self-inflicted difficulties, I started a local update to version 3.2, and everything seems to work fine: I get the option to update to 3.3, 3.4 and 3.5. :partying_face:

I appreciate your patience and your generosity with your knowledge.
When I spread the word about /e/OS, I already always mention that the community is one of the best features about it. Now, I will do so with even more confidence.
Thanks again!

1 Like
22

This topic was automatically closed after 60 days. New replies are no longer allowed.