upgrade disaster (twice)

asked 2020-04-10 10:36:14 +0200

objectifnul gravatar image

For the second time, EA release provoked a disaster. Description: I signed up for EA releases (now I reverted to EA opt-out). I did not upgrade my Xperia X from 3.2.1.20 Nuuksio to 3.3.0.14 Rokua when EA was released. However, maybe after packrefresh and/or Storeman update, my system was partially (and wrongly) upgraded to Rokua, then bricked. I had to reflash it from scratch.

I had the same experience last November with Torronsuo to Nuuksio upgrade. In both cases, Fingerterm briefly displayed "3.3.0.14" instead of "3.2.1.20" just before the disaster. ssu s was still returning "3.2.1.20" though. An other "red flag" was a frequent failure of package updates from Openrepos.

edit retag flag offensive close delete

Comments

2

I have opted out EA for many years and I never experienced such problem. It could be related to an application/patch you have installed from openrepos? Most of the time, this is the reason...and not Jolla's fault... That being said I did opt-in for this last release because I felt my X10 was in need ;) so I cannot comment on the last update.

pat_o ( 2020-04-10 12:30:38 +0200 )edit

I have an hypothesis: if you DON'T want to upgrade when a new SFOS (EA or public) is released and notified, DO NOT tap on the notification, even if you close the preparation process immediately. If you do, it's definitely too late. You have then only two options: (i) allow the upgrade process to proceed, (ii) reflash your device. Keeping the 'old' SFOS release unchanged is no longer possible.

objectifnul ( 2020-04-10 14:40:46 +0200 )edit