Flashing Sailfish 5.0 on Sony Xperia 10 V fails

[SAMIRAL]

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.

[defactofactotum]

Check that you are using a usb2 port, usb3 creates problems

[SAMIRAL]

I already tried that, to no avail, by connecting the phone to an old PC with USB 2 ports.

[SAMIRAL]

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.

[iolala]

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.