We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2020-04-16 12:39:24 +0200

XA2 Ultra stuck @ Sony logo after OTA

Gd evening ppl!

OK, so I had activated the early access in order to receive the 3.3 update, which was received successfully. 3 days ago, I deactivated the early access option from my account, and expected the "stable" version to come as an OTA update when available.

The problem: Last night, an OTA came to my device, which was actually a previous version firmware (3.2.1.20 if I remember correctly). Initially I thought that it would be wise to avoid it, since I know that downgrading is not safe (and impossible via OTA), but then I decided to do it, since Jolla "pushed" this OTA to my device. So, flashing failed, and since then my device is unable to boot.

Is there any way to flash 3.3 again, without losing my user data? (I have a backup, but I have also performed lots of "hand-made" configs to the Android partition, and would like to avoid losing them and doing them from scrap)?!

Thank you all in advance for your time!

Konstantinos

XA2 Ultra stuck @ Sony logo after OTA

Gd evening ppl!

OK, so I had activated the early access in order to receive the 3.3 update, which was received successfully. 3 days ago, I deactivated the early access option from my account, and expected the "stable" version to come as an OTA update when available.

The problem: Last night, an OTA came to my device, which was actually a previous version firmware (3.2.1.20 if I remember correctly). Initially I thought that it would be wise to avoid it, since I know that downgrading is not safe (and impossible via OTA), but then I decided to do it, since Jolla "pushed" this OTA to my device. So, flashing failed, and since then my device is unable to boot.

Is there any way to flash 3.3 again, without losing my user data? (I have a backup, but I have also performed lots of "hand-made" configs to the Android partition, and would like to avoid losing them and doing them from scrap)?!

Thank you all in advance for your time!

Konstantinos

[3.3->3.2 after automatic OTA] XA2 Ultra stuck @ Sony logo after OTAlogo, anyway to find and reflash 3.3?!

Gd evening ppl!

OK, so I had activated the early access in order to receive the 3.3 update, which was received successfully. 3 days ago, I deactivated the early access option from my account, and expected the "stable" version to come as an OTA update when available.

The problem: Last night, an OTA came to my device, which was actually a previous version firmware (3.2.1.20 if I remember correctly). Initially I thought that it would be wise to avoid it, since I know that downgrading is not safe (and impossible via OTA), but then I decided to do it, since Jolla "pushed" this OTA to my device. So, flashing failed, and since then my device is unable to boot.

Is there any way to flash 3.3 again, without losing my user data? (I have a backup, but I have also performed lots of "hand-made" configs to the Android partition, and would like to avoid losing them and doing them from scrap)?!

Thank you all in advance for your time!

Konstantinos

[3.3->3.2 after automatic OTA] XA2 Ultra stuck @ Sony logo, anyway to find and reflash 3.3?!

Gd evening ppl!

OK, so I had activated the early access in order to receive the 3.3 update, which was received successfully. 3 days ago, I deactivated the early access option from my account, and expected the "stable" version to come as an OTA update when available.

The problem: Last night, an OTA came to my device, which was actually a previous version firmware (3.2.1.20 if I remember correctly). Initially I thought that it would be wise to avoid it, since I know that downgrading is not safe (and impossible via OTA), but then I decided to do it, since Jolla "pushed" this OTA to my device. So, flashing failed, and since then my device is unable to boot.

Is there any way to flash 3.3 again, without losing my user data? (I have a backup, but I have also performed lots of "hand-made" configs to the Android partition, and would like to avoid losing them and doing them from scrap)?!scratch)?!

Thank you all in advance for your time!

Konstantinos