Ask / Submit

Unable to flash sailfish to Xperia XA2 from windows [answered]

asked 2019-04-05 14:43:19 +0300

Pim gravatar image

updated 2019-04-16 06:11:52 +0300

zagrimsan gravatar image

This is my continued quest to get SailfishX running on XPeria XA2. I tried but failed on Ubuntu:

So another attempt using Windows, following instructions at:
To be used:

Since this device is already unlocked, I followed the steps 1.2.* instructions and installed Emma to upgrade the device to the latest Adroid version. Emma recognizes the device, and offers two services: a Software update content erase service and a firmware update service.

However, the Jolla instructions state: "Please make sure the build number is (where xxx is 228 or higher), or is 34.4.A.yyy (where yyy can contain any number)." Emma did not offer a 34 version. It offered an 50.1.A.13.123 version. Is this a problem? Since I have nothing to lose I went ahead and applied both updates. This went OK.

Further problems in step 2, "Installing the Boot Loader". When using the Device Manager, the phone does not identify itself as a "S1Boot Fastboot" device, but as "Android", with "!" to indicate a missing driver. When following the instructions in step 2.11 I try to install the drive a0114adb.inf, Windows states that the folder does not contain a compatible driver. If I understand correctly, this means it does not think the device is a "fastboot" device.

Could it be that something went wrong during the OEM unlocking? When booting to Android the phone is shown as unlocked, but maybe it did not successfully change to become recognizable a fastboot device. It this is the case, I might buy another XA2 to see if I can get it to work.

Any other suggestions?

Side note: Jolla or some entrepreneur really should sell XA2s pre-loaded with Sailfish. I would happily pay for it.


edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by jovirkku
close date 2019-04-17 09:59:34.708317


Is the notification LED solid blue when you enter fastboot mode?

Giacomo Di Giacomo ( 2019-04-05 16:34:45 +0300 )edit

@Giacomo: yes it is blue. But the connection is not stable.

When testing before with Ubuntu, if I run "sudo fastboot devices", sometimes the phone is found, sometimes not. Usually I can only run the command once (sometimes a few times), after which the LED turns red and the phone switches to USB charging mode.

Pim ( 2019-04-05 16:38:48 +0300 )edit

do you have this on all usb ports?

Chris_ ( 2019-04-05 17:00:32 +0300 )edit

@Chris_ I've tried all ports available on the computers I tried this on.

On Ubuntu, I've also tried forcing USB2 as described on Also, I've also tried putting in a USB hub in between, but the reason people mention it is maybe that it's another way to force USB3.

Anyway nothing worked.

Pim ( 2019-04-05 17:12:33 +0300 )edit

Maybe it's a stupid question, but have you tried another cable? It could be low quality or damaged. Also, I would try on a native USB 2.0 port, possibly on another machine.

Giacomo Di Giacomo ( 2019-04-05 18:03:11 +0300 )edit

7 Answers

Sort by » oldest newest most voted

answered 2019-04-05 19:59:20 +0300

aQUICK1 gravatar image

Disable Driver Signature enforcement on Windows 10, then u can install the driver for the hardware to be recognized.!

edit flag offensive delete publish link more


Thanks for the comment. I will try that next week (all my laptops are Linux, the Windows PC is not my own).

Pim ( 2019-04-05 20:00:53 +0300 )edit

stay on linux.
what i saw about the fastboot driver install by the windows instructions, don't give me a trusty impression (because of similar past tinkering actions with the ms OS...).

cemoi71 ( 2019-04-05 20:10:52 +0300 )edit

I flashed SFOS with W10 and Linux Mint , both worked like a charm, just a preference of the user,thnx.

aQUICK1 ( 2019-04-05 20:12:54 +0300 )edit

@aQUICK1 with this tinkering paragraph from windows instructions? should you do all those steps like described? or worked through because of special windows edition or admin rights, whatever?...
Only the Driver Signature enforcement disabled?

cemoi71 ( 2019-04-05 21:34:55 +0300 )edit

Its been a while I flashed SFOS on my XA2 but yes to install those drivers needed to reinstall the correct driver for flashing /fastboot/recovery , but also im sure u need powershell as admin .

I just followed the procedure from the link inside the mail when u bought the licence from jolla, as I can recall.

But I must say im back to any using emma tool and flashed Lineage OS 16 on my XA2, waiting for SFOS the be more stable and full android(out of beta).

aQUICK1 ( 2019-04-06 21:53:31 +0300 )edit

answered 2019-04-05 16:31:47 +0300

Levone1 gravatar image

Most likely, the 34.x firmware is Oreo, which was probably the latest at the tome the guide was written, and 50.x is the current latest Pie. Emma,being Sony's official tool, probably only offers the latest. If the latest doesn't work, I guess Jolla should update their guide.

The most common problem with installing drivers on Windows 10 is driver signature enforcement. Make sure it's disabled, and see if it works. But, is your phone in fastboot mode when you are connecting it, (power off, hold volume up, connect cable, holding volume key until blue led)? Once you get successful fastboot connection, if there are errors in flashing, you might need to downgrade to Oreo, which can be done with unofficial flashtool -

This flashtool also includes a very helpful driver installation program, which will make sure you are installing the right fastboot driver.

edit flag offensive delete publish link more


The fastboot connection is there sometimes, but it's not stable. It can sometimes find the device, but not always.

Pim ( 2019-04-05 16:40:09 +0300 )edit

answered 2019-04-05 17:19:37 +0300

as400 gravatar image

Putting USB hub in between or forcing USB2 will not work. Been there done that. Just find computer with USB2 port and it will work.

edit flag offensive delete publish link more


maybe have an usb-hub with extern power for high transfer data

cemoi71 ( 2019-04-05 21:31:03 +0300 )edit

answered 2019-04-05 18:28:44 +0300

pawel gravatar image

updated 2019-04-05 22:28:40 +0300 does that

at least it appears as they would sell already flashed ones

edit flag offensive delete publish link more


??? Drunk?

Pohli ( 2019-04-05 20:00:42 +0300 )edit

@Pohli :-D

cemoi71 ( 2019-04-05 21:38:10 +0300 )edit

no using the awesome jolla browser and my eyes are aging, as yours will too

pawel ( 2019-04-05 22:27:42 +0300 )edit

yes for sure! and with big sausages as fingers too.... ;-)

cemoi71 ( 2019-04-05 23:35:18 +0300 )edit

predictive keyboard text is not working? or not set to english...

cemoi71 ( 2019-04-05 23:37:15 +0300 )edit

answered 2019-04-05 19:43:46 +0300

cemoi71 gravatar image

updated 2019-04-05 20:06:19 +0300

Please recheck all the process.
I found first a wrong link for flash instructions.
Check then all point inside of it
especially the "IMPORTANT – Do not skip this step" (try the device a couple days with android, & verify if it has an unlockable bootloader).

edit flag offensive delete publish link more


note: i'm not sure, but currently win10 might react with exact the same commands as on the ubuntu instructions, because it use the same bash shell (is at last integrated in my business machine).

cemoi71 ( 2019-04-05 19:44:25 +0300 )edit

answered 2019-04-15 18:55:12 +0300

Pim gravatar image

Update: my problem is solved.

Details on

edit flag offensive delete publish link more

answered 2019-04-16 23:25:34 +0300

N1cetatoooo gravatar image

updated 2019-04-16 23:26:16 +0300

You can also do it manually by installing fastboot and then boot into fastboot mode then open the in the sailfish folder with text editor and then you're ready to go

fastboot flash boot hybris-boot.img fastboot flash oem_a sw........ You just have to check it out and then img flash for img just like the flash sh does works 100%

edit flag offensive delete publish link more

Question tools



Asked: 2019-04-05 14:43:19 +0300

Seen: 321 times

Last updated: Apr 16