asked 2019-06-02 11:21:13 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Hello, I have some issues with my Xperia XA2 Plus running with 3.0.3.10. SMS are not sent, apps freeze. Is it possible to downgrade to the previous version? If so, how can I do it?
answered 2019-06-02 14:24:09 +0200
Here is an up to date (May 2019) statement from Jolla. In short, Sailfish OS doesn't support downgrading. The only way to "downgrade" is to use the factory reset.
The answer linked in the comment by Edz is from 2014. MANY things have changed since. Doing what that answer tells you to may mess up your device so that you will need to reflash.
the exact link for this is the following one https://jolla.zendesk.com/hc/en-us/articles/201836347#6
cemoi71 ( 2019-06-03 01:51:23 +0200 )editPlease read carefully. Even Jolla's statement "...couldbrick your device." seems to be a bit much, as it is most likely just the existing SailfishOS installation becoming unusable. Then one can still perform a "factory reset" at the recovery console.
But AFAICS "...willbrick your device." is not documented anywhere.
Still never downgrade "across" a "stop release", because that will most likely break your SailfishOS installation.
Even downgrading to a slightly minor version (not "across" a stop release, e.g. from 2.2.1.18 to 2.2.0.29) may result in a multitude of issues, hence downgrading is generally not recommended.
The proper way to downgrade is to execute a "factory reset" followed by upgrading to the intended release.
Specifically downgrading from 3.0.3.10 to 3.0.3.9 may work fine, although I have not tried that (I am staying on 3.0.3.9).
olf ( 2019-06-03 05:35:32 +0200 )editThere was this incident just a day before, where a guy tried downgrading Xperia X from 3.0.3.10 to 3.0.2 and reportedly got himself into a bootloop and had to reflash his device:
https://together.jolla.com/question/207148/303-connectivity-issues/
But yes, "will brick" was maybe a non-exactly-accurate hyperbola. Nevertheless, Jolla tells you never to downgrade, and what is linked above is what happened when it was tried with a current release.
The move down to 3.0.2 is exactly what many might at this particular point of time be contemplating on, and the initial answer in this thread was link to a very old post telling you to do exactly the same thing that got pawel's device all messed up. I felt a warning against it was in order, but I maybe did it in a bit too overt way in my haste.
Is there an official definition to a phone "getting bricked"? Should the term only be used in case of a permanent unrecoverable inoperability?
teemu ( 2019-06-03 05:58:23 +0200 )editAsked: 2019-06-02 11:21:13 +0200
Seen: 888 times
Last updated: Jun 03 '19
