Problems flashing Xperia 10 V on Linux

Devices
1

I bought a brand new Xperia 10 V (XQ-DC54) and went through the installation process as per the instructions here: How to install Sailfish X on Xperia™ 10 V on Linux - Free - Jolla

Before unlocking I had run all the updates availeble on Android (14).

The flashing seemed to start fine but then suddenly failed:

Flash utility v1.2
Detected Linux
Searching device to flash..
Found XQ-DC54, serial:XXXX, baseband:68.1.A.2.187, bootloader:6375-0005_X_Boot_SM6375_LA2.0_T_16
Found matching device with serial XXXX
Fastboot command: fastboot -s XXXX
>> fastboot -s XXXX getvar secure
<< secure: no
>> fastboot -s XXXX reboot fastboot
Rebooting into fastboot                            OKAY [  0.003s]
< waiting for XXXX>
Finished. Total time: 22.241s
>> fastboot -s XXXX flash:raw boot_a hybris-boot.img
Sending 'boot_a' (67092 KB)                        OKAY [  1.774s]
Writing 'boot_a'                                   OKAY [  1.427s]
Finished. Total time: 3.293s
>> fastboot -s XXXX flash:raw boot_b hybris-boot.img
Sending 'boot_b' (67092 KB)                        OKAY [  1.775s]
Writing 'boot_b'                                   OKAY [  0.406s]
Finished. Total time: 2.249s
>> fastboot -s XXXX flash dtbo_a dtbo.img
Sending 'dtbo_a' (232 KB)                          OKAY [  0.006s]
Writing 'dtbo_a'                                   OKAY [  0.006s]
Finished. Total time: 0.029s
>> fastboot -s XXXX flash dtbo_b dtbo.img
Sending 'dtbo_b' (232 KB)                          OKAY [  0.006s]
Writing 'dtbo_b'                                   OKAY [  0.007s]
Finished. Total time: 0.022s
>> fastboot -s XXXX flash vendor_boot_a vendor_boot.img
Sending 'vendor_boot_a' (328 KB)                   OKAY [  0.009s]
Writing 'vendor_boot_a'                            OKAY [  0.009s]
Finished. Total time: 0.027s
>> fastboot -s XXXX flash vendor_boot_b vendor_boot.img
Sending 'vendor_boot_b' (328 KB)                   OKAY [  0.009s]
Writing 'vendor_boot_b'                            OKAY [  0.009s]
Finished. Total time: 0.027s
>> fastboot -s XXXX flash userdata sailfish.img001
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::compare: __pos (which is 917456) > this->size() (which is 0)
./flash.sh: rivi 121:4018366 Keskeytetty             (luotiin core-tiedosto)$@
Flashing failed (134)

Now trying the flashing again only gets this far and then the phone goes to an endless boot loop:

Flash utility v1.2
Detected Linux
Searching device to flash..
Found XQ-DC54, serial:XXXX, baseband:68.1.A.2.187, bootloader:6375-0005_X_Boot_SM6375_LA2.0_T_16
Found matching device with serial XXXX
Fastboot command: fastboot -s XXXX
>> fastboot -s XXXX getvar secure
<< secure: no
>> fastboot -s XXXX reboot fastboot

I tried holding the volume up button down to help the phone get back to the fastboot mode while it was looping which breaks the loop:

Rebooting into fastboot                            OKAY [  0.003s]
< waiting for XXXX>
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Flashing failed (1)

Any ideas how I could get the flashing to finish properly?

//P

2

Maybe reading this topic will help.

2 Likes
3

Yes, I already read that -didn’t solve my problem.

Trying to run the commands one-by-one gives these errors:

# fastboot -s XXXX flash userdata sailfish.img001
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::compare: __pos (which is 917456) > this->size() (which is 0)
Keskeytetty (luotiin core-tiedosto)

# fastboot flash userdata sailfish.img001
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::compare: __pos (which is 917456) > this->size() (which is 0)
Keskeytetty (luotiin core-tiedosto)

# fastboot flash oem_a SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img 
Sending 'oem_a' (2097152 KB)                       FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

The other commands worked fine.

4

5.0.0.62? I’m fresh off of installing .62 on a 10 V running Android 13 (un-upgraded since last year’s spring) by the linked instructions and everything went well for me and my Sailfish OS is up and running. Can the latest 14 contribute to the issue?

5

Yes, my first attempt was with Sailfish_OS-Jolla-5.0.0.62-xqdc54-1.0.0.39 and when that didn’t work out I also tried the Sailfish_OS-Jolla-4.6.0.15-xqdc54-1.0.0.25.

I think upgradfing to the latest Android 14 (installing all the available updates) might be the culprit here.

I’m not sure it’s possible to downgrade now that the phone is in this boot loop. At least it’s still booting to fastboot… :thinking:

6

I restored the phone to Android 13 with Emma and then tried to flash again but the same result:

Flash utility v1.2
Detected Linux
Searching device to flash..
Found XQ-DC54, serial:XXXX, baseband:68.0.A.0.797, bootloader:6375-0005_X_Boot_SM6375_LA2.0_T_13
Found matching device with serial XXXX
Fastboot command: fastboot -s XXXX
>> fastboot -s XXXX getvar secure
<< secure: no
>> fastboot -s XXXX reboot fastboot
Rebooting into fastboot                            OKAY [  0.003s]
< waiting for XXXX>
Finished. Total time: 22.164s
>> fastboot -s XXXX flash:raw boot_a hybris-boot.img
Sending 'boot_a' (67092 KB)                        OKAY [  1.776s]
Writing 'boot_a'                                   OKAY [  1.400s]
Finished. Total time: 3.293s
>> fastboot -s XXXX flash:raw boot_b hybris-boot.img
Sending 'boot_b' (67092 KB)                        OKAY [  1.779s]
Writing 'boot_b'                                   OKAY [  0.401s]
Finished. Total time: 2.241s
>> fastboot -s XXXX flash dtbo_a dtbo.img
Sending 'dtbo_a' (232 KB)                          OKAY [  0.007s]
Writing 'dtbo_a'                                   OKAY [  0.006s]
Finished. Total time: 0.030s
>> fastboot -s XXXX flash dtbo_b dtbo.img
Sending 'dtbo_b' (232 KB)                          OKAY [  0.006s]
Writing 'dtbo_b'                                   OKAY [  0.006s]
Finished. Total time: 0.018s
>> fastboot -s XXXX flash vendor_boot_a vendor_boot.img
Sending 'vendor_boot_a' (328 KB)                   OKAY [  0.009s]
Writing 'vendor_boot_a'                            OKAY [  0.008s]
Finished. Total time: 0.023s
>> fastboot -s XXXX flash vendor_boot_b vendor_boot.img
Sending 'vendor_boot_b' (328 KB)                   OKAY [  0.009s]
Writing 'vendor_boot_b'                            OKAY [  0.008s]
Finished. Total time: 0.024s
>> fastboot -s XXXX flash userdata sailfish.img001
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::compare: __pos (which is 917456) > this->size() (which is 0)
./flash.sh: rivi 121:4108566 Keskeytetty             (luotiin core-tiedosto)$@
Flashing failed (134)

Seems it wasn’t the latest Android 14 after all.

Don’t really know what to try next… :hushed:

7

Are you using using an USB3 port for flashing? I can’t remember the specifics, but that is a thing that can cause some issues in some circumstances. USB2 should be safe.

8

There is a reason everyone says “search before posting”.
std::out_of_range gives no less than 6 hits on the forum.

Among those:

9

Are you using an up to date version of fastboot? I had similar problems using an old version.

10

It turned out the fastboot version was too new:

The solution was in to revert to Android 13 with Emma, install an earlier version of fastboot and flash with that.

So, @attah thank you for pointing that thread out to me! :slightly_smiling_face:

6 Likes