Problems to flash Sailfish on Xperia 10 IV (fastbootd menu)

Bug Reports
1

REPRODUCIBILITY: 100%
OS VERSION: Android 14, Windows 11
HARDWARE: Xperia 10 IV
UI LANGUAGE: german/english
REGRESSION: -

DESCRIPTION:

I follow the step-by-step instructions in “How to install Sailfish X on Xperia™ 10 IV” (via Windows 11), but the flashing of Sailfish X (point 8) cannot be completed.
The Windows script does not continue to run, I end up in the fastbootd menu on the smartphone after Rebooting into fastboot at the Windows script.

PRECONDITIONS:

at CMD:

  • fastboot devices
    [serial number] fastboot
  • fastboot getvar secure
    secure: no
  • fastboot getvar unlocked
    unlocked: yes
  • fastboot getvar version-baseband
    version-baseband: 65.2.A.2.179

STEPS TO REPRODUCE:

  1. start with blue LED on the phone the flash-on-windows.bat
  2. at CMD:

Searching for a compatible device…

The device is unlocked for the flashing process. Continuing…

Found ‘SW_binaries_for_Xperia_Android_14_5.4_v3a_murray.img’ that will be used as vendor image. Continuing…

[folder]>fastboot.exe -s [serial number] reboot fastboot
Rebooting into fastboot OKAY [ 0.004s]
< waiting for [serial number] >

  1. fastbootd options on phone are reboot system, enter recovery, reboot to bootlader, power off
  2. after waiting ~15 minutes I click on any of the four options
  3. at CMD:

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

ERROR: Failed to execute ‘fastboot.exe -s [serial number] reboot fastboot’.

FLASHING FAILED

Please go to https://forum.sailfishos.org/ and ask for guidance.

EXPECTED RESULT:

flashing of Sailfish X

ACTUAL RESULT:

the phone starts into Android

MODIFICATIONS:

no

ADDITIONAL INFORMATION:

  • tested it with german and english language at the phone
  • tested it with different usb cables and inputs at the laptop
  • tested it several times with the same result

I am not a programmer at all and would be grateful for any help!

2

Hi, I confirm, it behaved the same way for me, Vbox/Win10 and on PC/Win10.
I used Win as a replacement solution, because the USB did not work properly for me on Linux, everything is here Xperia 10 IV flash 4.6.0.15 faulty

3

Thank you. but this was a solution for flashing via Linux?! Because I have no idea what I can do in Windows 11.

4

I also ran into the exact same problem with Xperia 10 IV. Flashing from new win 11 laptop and old win 10 laptop. No difference. Then flashing AOSP with Emma. Ok. Tried flashing several times but no luck. I also tried running fastboot commands from flash-on-windows.bat from a cmd promt skipping the first one “fastboot reboot fastboot” whitch starts gui mode on phone. Most off them executes successfull except flashing “vendor_boot.img”.
Output from console.

fastboot flash vendor_boot_a vendor_boot.img
Sending ‘vendor_boot_a’ (328 KB) OKAY [ 0.016s]
Writing ‘vendor_boot_a’ FAILED (remote: 'Flashing is not allowed for partition
')
fastboot: error: Command failed

fastboot flash vendor_boot_b vendor_boot.img
Sending ‘vendor_boot_b’ (328 KB) OKAY [ 0.016s]
Writing ‘vendor_boot_b’ FAILED (remote: 'Flashing is not allowed for partition
')
fastboot: error: Command failed

Linux Ubuntu (ubuntu-24.04.1-desktop-amd64.iso ON Oracle VirualBox)
Almost the same error.

Found XQ-CC54, serialn:XXXXX, baseband:65.1.A.5.65, bootloader:6375-0001_X_Boot_SM6375_LA2.0.1_T_106
Found matching device with serial XXXXX
Fastboot command: fastboot -s XXXX
…
…
Blue led lit on phone
After 5-10 min.
Phone displays fastbootd gui.
I select Reboot system now.
Phone boots into android AOSP again.
:cry:

5

Should i give up flashing 4.6.0.15 on xperia 10 IV :cold_sweat:

6

Solved :slight_smile: . Xperia 10 IV is now running Sailfishos 4.6.0.15

7

how? I am still waiting for a solution

8

Check the device manager and the driver again, it might be that the device no longer is as required with the sonydriver. You can update the driver to the sony one for the device and then the flashing will continu.

9

Also curious to know the solution. :slightly_smiling_face:

10

Mine solution. After starting windows flash script phone start fastbootd and command window at the pc wait for connection. Phone lit red. Started device manager and realice that android driver was not properly instaled. Updated driver on win11 with the driver supplied from Sony. When the driver was upgraded the install .bat continued flashing OK. Disconnected USB cable and rebooted phone. Wery happy. I have the same problems mentions on the forum. Happy to help you.

3 Likes
11

Thanks for sharing!
You are right, somehow the driver is not recognized when the boot is done during the flashing.
Installed the driver and it works.

12

thanks! does that mean you used a different driver than the one in the instructions? or did you simply update the driver at that time?

13

Its the driver from the instructions.
When you first boot it in fastboot mode and start the bat script it will connect and your phone will reboot.
But if you look at the device manager again it shows the device is missing a driver.
Install it again and it should begin the flash.

1 Like
14

No. Before starting the flashing process I folowed the documention from Jolla inklude the install of Sony driver.Checked device manager after volume up and connect USB cable to phone.All looked perfect. When i started flashing and the phoe rebooted into fastbootd (not documented) i realiced a new devic with yelow excamation mark was detected. Earlier flash attemt i did notsee this. I clicked this unknown device and upgraded withi the same Sony driver.Then the flashing process finished OK.
God luck. I’m happy to have Sailfishos on my 2 year old Xperia waiting for sailfishos. My Jolla C is wery slow and has bad battery life.

1 Like
15

Thanks you both for the solution, it worked for me in the end.
I just made a wrong step after the driver update. Unfortunately i got into a reboot loop in the meantime and had to reflash Android version 13 via emma.
But now Sailfish is on the 10 IV and I’m happy when a few bugs are fixed in future.

2 Likes
16

I ran in the same issue as described.
I am sure I have installed the device driver from Sony.
BUT! I had to install it twice because after unlocking the bootloader the phone was no longer recognized by the driver. I think to remember that the device name for the locked device was different, but I am not sure about that.
Installing the Sony driver a second time resolved the issue for me.

1 Like