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

do not update your XA2 device to Android 9 [answered]

asked 2019-05-05 19:09:15 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2019-05-05 19:09:15 +0300

seehas gravatar image

Does this apply to LineageOS 16, which is based on Android 9, too? How can I get rid of this problem?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by seehas
close date 2019-10-21 20:57:14.767320


i ssume flash back to older lineage vesion

pawel ( 2019-05-05 19:13:28 +0300 )edit

That's what I thought. So I'm actually looking for a downgrade instruction for LineageOS. But why does the initial OS play any role at installing Sailfish? There will be installed an image, so the whole storage will be overwritten by this image no matter which data were stored before.

seehas ( 2019-05-05 19:37:43 +0300 )edit

XA2 is working fine with Lineage 16 and Andy 9, official version !

aQUICK1 ( 2019-05-05 19:38:04 +0300 )edit

Sorry, this was not my question. I tried Lineage, but will go back to Sailfish and now I found this hint not to upgrade to Android 9.

seehas ( 2019-05-05 19:58:45 +0300 )edit

Sailfish X is installed on top of an Android installation, basically replacing the OS, but re-using the (compatible) kernel. If you don't provide the exact foundation to run Sailfish on, it will break your system.

Maus ( 2019-05-05 22:06:51 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2019-10-21 20:56:55 +0300

seehas gravatar image

Now I got back from LineageOS 16 to Sailfish by means of the installation instruction https://jolla.com/sailfishx-windows-instructions-xa2/ and the downgrade manual https://jolla.zendesk.com/hc/en-us/article_attachments/360003683140/How_to_revert_XA2_from_Android_9_to_8.1_and_then_install_Sailfish_OS.pdf. It works fine and without any issues. Now I'm happy to be back at Sailfish. Thanks to Jolla.

edit flag offensive delete publish link more

answered 2019-05-07 15:12:31 +0300

DrYak gravatar image

updated 2019-08-07 11:46:45 +0300

For people with a "bricked" Smartphone (i.e.: who tried to flash Sailfish X over an Android 9 phone and got it non-booting any more), until Jolla official devs provide an official solution :

Some random last-hope things before trying to get your warranty working:

  • try using the open source flashtool instead of Sony's proprietary Emma for downgrading? (it even comes with its own copy of xperifirm to fetch the firmware from Sony).

    Back with the Xperia X, in my experience it seemed more reliable for downgrading to older Android version to perform "backup TA". Maybe it will also work better to downgrade you XA2 back to Android 8 ?

    Note that you might need to repackage a bit the firmware you fetch from xperifirm, see guides that were written here for doing the downgrade+backup TA for Xperia X.

  • manually :

    fastboot flash oem_b SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_nile.img

    currently only oem_a gets flashed (because that's where Sailfish X mounts its blobs from), but perhaps the bootloader somewhat needs the drivers even before booting into the kernel ?

edit flag offensive delete publish link more


Thank you so much for this tip! flashtool saved me :)

macrum ( 2019-06-12 23:55:07 +0300 )edit

It seems weird to me that you could really brick a mobile device these days - you might need to use low level tools & it might be some work, but it should always be possible to recover it.

MartinK ( 2019-08-07 15:19:07 +0300 )edit

Luckily it seems that XA2 is Soft bricked in this case.

Filip K. ( 2019-08-07 17:21:40 +0300 )edit

Question tools



Asked: 2019-05-05 19:09:15 +0300

Seen: 2,609 times

Last updated: Oct 21 '19