FP3 Updater crashes before reboot and update to OTA 3.0.4

[toch]

• Vendor Name : Fairphone
• Device name : FP3
• Device CodeName : FP3
• Version of /e/OS existed previously : OTA 3.0.1-t-20250606498724-official-FP3 (A13)
• Is the device Rooted / Not rooted : not

Updater crashes cannot go further :

• Install OK
• Button “Install”, but
• Updater fails after download and preparing reboost
• Updater app crash
• If you wait enough or clear its cache, you can restart the app Updater
• If I enable the next updates, 3.1.1 is displayed and the button “Apply button” is displayed
• If I try to install again 3.0.4, same behavior
• some apps crashes when started (Browser, Fennec, Search in Settings, Clock, Calculator, Phone, Music, Gallery, Contacts), it seems to correspond the an interrupted a update of the system and e/os apps before reboot

others ;

• if i have before doing the Update enabled “Developer options” with “USB Debugging”
• I don’t find the same issue (even there are a few simulated but it is not storage or the cache of Updater)
• Storage has enough 4.8GB
• I always look for feedback before apply update, I didn’t find anything for FP3

I don’t got further and make it worse. For instance, could I reboot? maybe reinstall the previous of the apps, at least Phone.

gitlab : FP3 Updater crashes before reboot and update to OTA 3.0.4 (#8905) · Issues · e / Backlog · GitLab

I would really your help as I cannot do anymore what I can a 1 year ago due my health issue

I would really your help as I cannot do anymore what I can a 1 year due my health issue

I find a solution to call and be reachable by phone, the app fossify phone does the job.

I’ve installed other app fossify (contact, clock, calculator) and it works. It confirm the while happen during the replacement of few apps before rebooting.

Some links about crash of Updater (but do not work, not totally the same (e.g. crash during reboot), or possibly breaking and advanced action in the actual state) :

• Issues with the Updater and a solution
• Phone crashes after Update
• Feedback for v3.1.1 - #76 by nicosg
• Samsung S9, v3.0.4 official, /e/ Recovery loop, Signal backup - #6 by jomoreau
• Feedback for v3.0 - #187

[toch]

according the doc of the udater How to update /e/ the sequence of button seems correct.

the community doc says the same in details Update /e/OS software

When i updated the list of available updates, the 3.1.1 with the button “Apply Updates” that is confusing. What search of it, I found

Feedback for v3.1.1

Vendor Name: Google Device name: Pixel 5 Device CodeName: Redfin Previous Version of /e/OS: 3.0-t-official Device: Not rooted I had no intention of installing this update unless it was moving to A15 from A13 (t). I am utterly confused by the messaging on devices that are/aren’t/have/haven’t received/not received upgrades to Android 15. So when I went to check the update name to check which Android level I was updating, I discovered that the update had already downloaded and was waiting fo…

that mentions the button and it would have always downloaded the packaged

[toch]

issue updated logs

according the error, update has already applied an now we need reboot. that’c correct?

Can I safely reboot then? and then run the update to 3.1.1?

[aibd]

A reboot after a failing update is usually “a good thing”.

When one has a fail there is always the possibility of loss of data.

• An update on completion does always require one reboot.

[toch]

@aibd thanks

Indeed, after each a update there a reboot. When no feedback is given, it’s hard if you can reboot or it has corrupted.

[aibd]

@toch

the list of available updates, the 3.1.1 with the button “Apply Updates” that is confusing.

Is the confusion that two updates are offered?

If you were or are still currently running

e-3.0.1-t-20250606498724-official-FP3

Then I would expect the Updater to offer you both

• e-3.0.4-t-20250709507786-official-FP3
• e-3.1.1-t-20250828521480-official-FP3

Here you can chose to move to e-3.0.4 or you could bypass that and go straight to e-3.1.1.

I just say this as either choice is OK.

[toch]

indeed, i’m 3.0.1 and i have started the update to 3.0.4 and it was stopped before rebooting.

now the following one 3.1.1 is listed also (because I’ve enabled the next available update).

it seems run reboot to end the update to 3.0.4, I would like to know the reboot is safe as the error as a little cryptic.

[aibd]

@toch

it seems run reboot to end the update to 3.0.4

Yes it should.

@toch

and it was stopped before rebooting.

Will one ever know if it is 100℅ “safe” ??

a) The phone has two “Slots” A and B. The use of A and B alternate with update. Following update the phone should choose to take the “new” slot. If the new slot is “bad” the phone will revert to the “old” slot.

b) The First boot after update (or install) takes extra energy (why we are advised battery state >60%). A First boot can fail (just a transient fail) but manages at second boot.

c) In normal circumstances one can boot into e-Recovery to see which is active.

I see two choices

• Reboot
• Decide not to reboot and see if you can keep your phone running nicely on e-3.0.1 by clearing cache on badly affected apps. You will inevitably reboot one day.

Do you have a backup of essentials ?

If not, perhaps that is the priority right now.

[toch]

I have backups, I took time to check them and take a recent version. Always good to check.

the reboot did the job and was reboot with the retrieved stacktrace with adb.

thanks for taking the time, it was nice to do be alone.