XPeria 10 plus fastboot hang

Devices
1

Hi there,

I just wanna share a feedback about installing SFOS on my XPeria 10 plus (dual SIM). TLDR : I had to use fastboot version 34 instead of the 35 (latest at time of writing)

First big thank for those who write the “how to install …”, that’s great!

Config

Device

XPeria 10 Plus, running Android 9 (manually downgraded from 10, as asked in the install guide).

Computer

Archlinux, fastboot 35.0.2

Steps

Bootloader unlocked without issues. Then flashing:

$ sudo bash ./flash.sh
Flash utility v1.2
Detected Linux
Searching device to flash.

And then nothing more, programm hangs and never ends.

Note that fastboot devices correctly shows up my phone.
Looking at flash.sh it seems to be stucked at fastboot getvar commands. Trying to run those directly, for instance

$ fastboot getvar version

also hang.

Workaround

I finally tried from an ubuntu laptop, shipping fastboot in version 34 and everything works at first try. No idea why … but I have now a nice OS on my phone :smiley:

2

This might be caused by the known issue of flasher not working when the phone is connected to USB3 port on your computer. If your problem was caused by the USB3 issue, using USB2 port or a dongle with USB2 port should get your phone flashed with no issues also on the first computer you tried the flashing with.

1 Like
3

absolutely right what @avhakola wrote, and a second thing is:
On my computer (Debian 12) it was different if I start the command

$ sudo bash ./flash.sh

from a user cli (didn’t work), or if I become root by su command and then entered

# bash ./flash.sh

did work!

4

Thanks for your inputs!

Indeed, I forgot to mention this point in my inital post. I have both USB3 and 2 ports on my laptop, and using the USB2 port didn’t solve the issue.

This is definitely strange! But good to know.

5

Does the sudo bash starts the new bash in /root instead of the current directory? If so, and the ./flash.sh -script is in different directory (some where under /home probably?), it doesn’t work because bash can’t find the script? Maybe trying to run the command with full path to the script or copying the script to /root first works?

6

Sorry my late reply, but I always checked what’s the working directory (by pwd command). But I have no control what the computer really does if executing a command with sudo. Using a full path for sure is a good idea.