My attempt at flashing Sailfish 5.0 on Sony Xperia 10 V model pdx235 with an unlocked bootloader failed. The flashing process hangs at the stage “waiting for HQ…” ; the serial identification of the phone. Waiting for the flashing to proceed, the blue led turns off and the fastbootd menu is displayed on the phone with the option “reboot system now” highlighted. Waiting longer without executing any function automatically boots the phone into Android. If I try to switch off the phone, unplug it and then re-plug it with the blue led back on, the following message is displayed:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable
Error: Failed to execute ‘fastboot.exe -s HQ…A6 reboot fastboot’
Flashing Failed
The PC is Windows 10 Pro 22H2. Phone details: Sony Xperia 10 V XQ-DC54 with Android 13 kernel 5.4.210. I tested the following:
Xperia Drivers: sa0114 year 2016, sa0200 year 2020
SW binaries: Android_13_5.4_v2a_zambezi, Android_14_5.4_v3a_zambezi,
*v2a is not accepted.
An original Sony USB cable that was included with the Xperia XA2 was used for the connection. The Xperia USB drivers seem to be properly installed.
I appreciate any suggestions on successfully flashing Sailfish 5.0 on this phone. Thank you.
1 Like
Check that you are using a usb2 port, usb3 creates problems
1 Like
I already tried that, to no avail, by connecting the phone to an old PC with USB 2 ports.
If the flashing gets stuck on cmd terminal and the fastbootd appears on the phone:
While phone is still connected open device manager.
Check phone model with yellow exclamation symbol e.g. pdx235
Update its driver to sa0200 or sa0114; the USB driver you originally installed for Sony Xperia 10 V
The flashing with Sailfish will resume. Special thanks to “rgrnetalk” for this solution.
6 Likes
I’m pretty sure this is the same issue I encountered.
I reported it to Jolla 3 months ago, when it happened, together with very detailed steps of what happened and how the official tutorial should be improved, but they just don’t give a shit and said their tutorial is good, so they won’t improve it.
Apparently, the fact that the “good” tutorial fails is not a Jolla problem.
2 Likes
works by updating the driver! thanks
1 Like
Great, although a host of features don’t work upon installing SFOS which should be sorted out with an update when they get around to it. Currently the phone with the latest update installed is unusable.
1 Like
It’s a beta version, this is made quite clear by posts mentioning it on the forum. Same reason there is no paid licence for it currently.
Also, they’ve been trying to fix it for about a year and a half now, it is not that simple by the looks of it. We have been waiting for ages
1 Like
I realised the hard way never to install anything beta on any device. I also learnt that once you unlock the boot loader on a Sony, the DRM keys get erased, the camera functions are degraded and you cannot get it back to factory condition without replacing the motherboard. You can flash android back on the device but you won’t be able to upgrade the OS though Sony flashing tools with the bootloader unlocked. Consequently, I’m keeping this phone for the official Sailfish release.
1 Like
I recommend that you always read instructions and release notes before flashing.
AFAIK relocking the bootloader is possible.
I tried to flash using Sony Mobile Flasher by Androxyle and it failed with the following error: Cannot invoke “String.split(String)” because the return value of “java.util.Properties.getProperty(String)” is null.
My phone is Sony Xperia 10 V, XQ-DC54 model: pdx235, Android 13. I appreciate any suggestions on relocking the bootloader.
1 Like
This sounds like a bug in that flasher. Please check if fastboot can relock. There are others as well: Piriform, Emma.
2 Likes
I have Xperia Flash Tool which may be the equivalent of Emma. I don’t know anything about Piriform. However, I used platform tools and typed in the command “fastboot oem lock” which successfully locked the bootloader. I restarted the phone and it did so normally without displaying the unlocked bootloader message. I bought this phone specifically for Sailfish but thought about upgrading to Android 14 because someone on this forum mentioned that the battery indicator functions with this version, Zambezi v4b binaries, and Sauna. Imagine driving a gasolene car without a fuel gauge. Ultimately I’ve decide to wait for the official release of the licensed SFOS, as there are too many faults with the current beta version.
1 Like
