Revision history [back]

This is my continued quest to get SailfishX running on XPeria XA2. I tried but failed on Ubuntu: https://together.jolla.com/question/202834/unable-to-flash-sailfishx-to-xperia-xa2-from-ubuntu/

So another attempt using Windows, following instructions at: https://jolla.com/sailfishx-windows-instructions/

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 34.3.A.0.xxx (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.

Pim

This is my continued quest to get SailfishX running on XPeria XA2. I tried but failed on Ubuntu: https://together.jolla.com/question/202834/unable-to-flash-sailfishx-to-xperia-xa2-from-ubuntu/

So another attempt using Windows, following instructions at: at:
https://jolla.com/sailfishx-windows-instructions/ To be used: https://jolla.com/sailfishx-windows-instructions-xa2/

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 34.3.A.0.xxx (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.

Pim

This is my continued quest to get SailfishX running on XPeria XA2. I tried but failed on Ubuntu: https://together.jolla.com/question/202834/unable-to-flash-sailfishx-to-xperia-xa2-from-ubuntu/

So another attempt using Windows, following instructions at:
https://jolla.com/sailfishx-windows-instructions/
To be used: https://jolla.com/sailfishx-windows-instructions-xa2/

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 34.3.A.0.xxx (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.

Pim

This is my continued quest to get SailfishX running on XPeria XA2. I tried but failed on Ubuntu: https://together.jolla.com/question/202834/unable-to-flash-sailfishx-to-xperia-xa2-from-ubuntu/

So another attempt using Windows, following instructions at:
https://jolla.com/sailfishx-windows-instructions/
To be used: https://jolla.com/sailfishx-windows-instructions-xa2/

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 34.3.A.0.xxx (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.

Pim