Ask / Submit

Sailfish X stuck on spinner after tutorial [answered]

asked 2017-10-12 08:57:18 +0300

tochi gravatar image

updated 2017-10-12 10:34:47 +0300

jiit gravatar image

Last night, I followed the instructions from the Sony Developer World website to unlock the bootloader on my Sony Xperia X using Windows 10. I then purchased Sailfish X from the Jolla store, and followed the instructions to extract the image, add the Sony vendor binaries, and flash the new OS using flash-on-windows.bat.

The phone boots and enters the Sailfish OS tutorial, but once the tutorial is complete, the screen remains stuck on a Sailfish loading spinner.

The phone recognizes the top-down swipe gesture to list available ambiences and show the power off function. Switching ambience changes the colour of the loading spinner, and the Power Off function works.

I have tried:

  1. Waiting a long while
  2. Rebooting the phone
  3. Using flash-on-windows.bat to reflash the OS

All to the same effect.

Has anybody else encountered 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 jiit
close date 2017-10-12 10:43:14.317993


Hi @tochi, is your Xperia X single SIM (F5121) or dual SIM (F5122)?

sledges ( 2017-10-12 10:07:08 +0300 )edit

It's a single SIM (F5121).

tochi ( 2017-10-13 23:50:14 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-10-12 10:37:57 +0300

tochi gravatar image

I have managed to solve my own problem! :)

It appears that the particular fastboot driver installed is key here. I had followed the instructions from the Sony Developer World website to unlock the Xperia X bootloaders, as I didn't have Jolla's detailed instructions until I had purchased Sailfish X.

Looking into Jolla's instructions in more depth, I noticed that they specify installation of the sa0114adb.inf driver before flashing, whereas I still had the customised android_winusb.inf driver from Sony's instructions. After I updated the driver and re-flashed using flash-on-windows.bat, I found the Sailfish OS setup steps including configuring network connection, and the tutorial was slightly different (it used answering calls as the example for the swipe up and swipe down gestures, instead of snoozing and dismissing alarms as it had previously).

Having completed the tutorial, I am now on the Sailfish home screen!

edit flag offensive delete publish link more


Hi tochi, really nice job figuring this out! I had the same issue, unfortunately though, the other driver sa0114adb.inf cannot be installed. First I had huge problems stopping Windows from using the fastboot driver, now I am stuck with the other driver, that for some reason does not want to load... Do you or does anyone have an idea why this is? I have tried on both a Win 10 and Win 7 computer.

siggg ( 2017-10-12 16:11:41 +0300 )edit

Great that you figured it out. Android drivers under Windows are just a big mess, with every manufacturer / software using another special version for adb or fastboot and weird bugs (note: bugs, not errors) if you are using the wrong driver.

ghling ( 2017-10-12 17:44:19 +0300 )edit

@siggg - Windows wouldn't let me update the android_winusb.inf driver with sa0114adb.inf - I got some message like "You already have the most up-to-date driver available". To get around this, I had to uninstall android_winusb.inf, and I was then able to follow Jolla's instructions to install sa0114adb.inf and flash the OS successfully. I hope that helps!

tochi ( 2017-10-12 19:30:39 +0300 )edit

Thanks for your reply, tochi! I managed to get the phone running on the sa0114adn.inf driver yesterday evening on a "unspoiled" computer. However, although the flashing did work I ended up with the same faulty installation of Sailfish X. I seem to be back at square one. I will try some more before I maybe end up writing a ticket, since other than us two, no one seems to have issues with that...

siggg ( 2017-10-13 09:15:55 +0300 )edit

@siggg That's a bummer. Sorry to hear that it's still not working for you.

I didn't mention this in my answer as I didn't think it was relevant to what fixed the issue for me. I still think it's unlikely, but just in case it helps you or somebody else ...

Before I realised that the fastboot driver I was using wasn't the one specified in Jolla's instructions, I thought perhaps I had made a mistake by not completing all of the setup steps after flashing the latest Android image using Emma. I went back and re-flashed the phone with the Android image a couple of times, because I found that Android had become unstable at this point. When I booted the phone, it would crash and reboot after a few seconds of clicking through the Android setup screen.

It was at this point that I realised that my driver was incorrect, so once I tried to re-flash Sailfish using the correct driver, it was from a baseline of a (broken!) Android installation.

As I say, I'm not convinced that this is significant, but I hope it helps!

tochi ( 2017-10-13 12:12:52 +0300 )edit

Question tools



Asked: 2017-10-12 08:57:18 +0300

Seen: 307 times

Last updated: Oct 12 '17