Welcome to flashing cell phones.
2 Likes
Did you already try Xperia companion?
https://www.sony.com/electronics/support/articles/00236877
I once messed up the partition table of a Xperia 10 iii or V somehow, so that newflasher did not work and I had the same error message of corrupt device at boot.
Only this companion app was able to restore the partition table. After that restore by this companion app, newflasher did the job again.
For me it was a real pain since this companion app runs only on Windows and needed to get access to a Win machine…
1 Like
Are you sure that you messed up partition table?
As that “warning” is by default on Sony if bootloader is unlocked.
There are no sins in SFOS. It’s hackers friendly.
No, I’m being told that this is likely.
No, I can’t recall what the default warning is, but the difference between the two warnings are the symbols used, a warning triangle instead of an open lock, and includes that Your device will be powered off in 5 seconds.
2 Likes
Yes, I was sure because I edited the partition layout along with installing /e/OS before SFOS flashing, I do not remember the details anymore but this specific corrupted device message was not the standard bootloader unlocking message. This partition table mess up I only had once…
1 Like
I saw the “your device will be powered off in 5 seconds” message once or twice while working on my SFOS port due to incorrectly flashing the boot partition. It doesn’t certainly mean the partition table is bad, its just the generic message for not being able to find a bootable kernel.
3 Likes
Just to be sure, since I’ve done the Xperia companion route,
when you correctly flashed, did you do the following?
$ fastboot devices
$ fastboot flash boot_a hybris-boot.img
$ fastboot flash boot_b hybris-boot.img
$ fastboot flash dtbo_a dtbo.img
$ fastboot flash dtbo_b dtbo.img
$ fastboot flash userdata sailfish.img001
$ fastboot flash oem_a SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img
$ fastboot reboot
1 Like
Alright, I think I’m getting somewhere now.
I might not have noticed this:
$ sudo fastboot flash vendor_boot_a vendor_boot.img
Sending 'vendor_boot_a' (328 KB) OKAY [ 0.020s]
Writing 'vendor_boot_a' FAILED (remote: 'Flashing is not allowed for partition
And that’s because it’s not part of this post..
1 Like
If you are running the correct android base you should not need to flash vendor, which is why it is not part of the official flash instructions. Besides, your output of the command shows it has failed.
From Xperia Companion my android base has become 68.2.A.123.
I then did..
$ fastboot devices
$ fastboot flash boot_a hybris-boot.img
$ fastboot flash boot_b hybris-boot.img
$ fastboot flash dtbo_a dtbo.img
$ fastboot flash dtbo_b dtbo.img
$ fastboot flash userdata sailfish.img001
$ fastboot flash oem_a SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img
$ fastboot reboot
And yet again, everything gets through, but when the phone boots, it gets stuck in a bootloop, rebooting every few seconds, although this time without the corrupt warning system.
68.2.A.123 corresponds to Android 15, Security patch 1st July 2026.
From Jolla’s installation instructions, you need:
Please make sure that your phone has Android version 13 or 14.
So I would argue you are not running the correct Android base.
From newflasher, my android has become 68.1.A.2.270
$ sudo fastboot devices
HQ635Q115E fastboot
$ sudo fastboot flash boot_a hybris-boot.img
Sending 'boot_a' (67084 KB) OKAY [ 2.725s]
Writing 'boot_a' OKAY [ 0.216s]
Finished. Total time: 3.634s
$ sudo fastboot flash boot_b hybris-boot.img
Sending 'boot_b' (67084 KB) OKAY [ 2.756s]
Writing 'boot_b' OKAY [ 0.242s]
Finished. Total time: 3.088s
$ sudo fastboot flash dtbo_a dtbo.img
Sending 'dtbo_a' (232 KB) OKAY [ 0.016s]
Writing 'dtbo_a' OKAY [ 0.008s]
Finished. Total time: 0.047s
$ sudo fastboot flash dtbo_b dtbo.img
Sending 'dtbo_b' (232 KB) OKAY [ 0.018s]
Writing 'dtbo_b' OKAY [ 0.005s]
Finished. Total time: 0.040s
$ sudo fastboot flash userdata sailfish.img001
Warning: skip copying userdata image avb footer (userdata partition size: 109313224704, userdata image size: 140735501467600).
Sending sparse 'userdata' 1/3 (786245 KB) OKAY [ 41.662s]
Writing 'userdata' OKAY [ 11.253s]
Sending sparse 'userdata' 2/3 (778261 KB) OKAY [ 46.473s]
Writing 'userdata' OKAY [ 10.173s]
Sending sparse 'userdata' 3/3 (314397 KB) OKAY [ 23.498s]
Writing 'userdata' OKAY [ 6.031s]
Finished. Total time: 142.500s
$ sudo fastboot flash -S 256M oem_a SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img
Warning: skip copying oem_a image avb footer (oem_a partition size: 2147483648, oem_a image size: 140734403639872).
Sending sparse 'oem_a' 1/2 (258232 KB) OKAY [ 13.747s]
Writing 'oem_a' OKAY [ 0.002s]
Sending sparse 'oem_a' 2/2 (186360 KB) OKAY [ 9.618s]
Writing 'oem_a' OKAY [ 0.001s]
Finished. Total time: 23.418s
$ sudo fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And yet again, same issue. And after a few bootloops I get the message that the device is corrupt.
Why did you try to reboot into fastboot? Just run sudo fastboot reboot like the installation instructions say.
I don’t think userspace fastboot exists while you’re running Sailfish on Xperias, only bootloader.