I tried yesterday with the same result like you
Is it enough to use fastboot flash SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img for newer Sony blobs on 10 V?
fastboot flash oem SW…img
is to be used to try the new blobs
╰─➤ $ fastboot devices -l 1 ↵
HQ63BJ0498 fastboot
usb:1-2 /0.5s
--------------------------------------------
╭─ ~/Downloads/SAIL
╰─➤ $ fastboot flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
Warning: skip copying oem image avb footer (oem partition size: 0, oem image size: 432464996).
Sending 'oem' (422329 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed /0.9s
--------------------------------------------
shouldn’t be there oem_a ?
No, I did not specify a or b.
Only fastboot flash oem did work flawlessly with A13 or A14 blobs for me every time
There isn’t more information about this error? Strange
Hmm… verbose mode is not so verbose 
╰─➤ $ fastboot -v flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
fastboot: verbose: Do flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
fastboot: verbose: target didn't report max-download-size
Warning: skip copying oem image avb footer (oem partition size: 0, oem image size: 432464996).
Sending 'oem' (422329 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
Neither this works :-/
That’s funny, because oem only without -a was sufficient and worked on my device.
Just double checked from my terminal history
??
Sorry, just reflashed my oem partition on my X10V, and ‘fastboot flash oem SW…ing’ works with new and old blobs.
Sorry, I cannot reproduce your error.
Your verbose claims partition size zero??
Sounds unusual to me
if i understand correctly that with new blob, modem, Wland and Bluetooth does not work but with SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img it is working fine here (except camera of course)
5G is working fine having speedtest around 230d/95u
I can confirm that modem, WLAN and Bluetooth are inactive with the new November zambei blobs, while with the ones recommended by Jolla in the beta 4.6 15 release all three work
1 Like
It worked for me after the first boot but then soon drained the battery and now it’s stuck between airplane mode and not detecting the SIM. At least data worked as I didn’t made a call. WLAN and Bluetooth look like they would work but I haven’t tested yet.
Edit: I double checked and I have the problems above with SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.img.
1 Like
As the target did not report the maximum chunk size it supports one may set it manually by the fastboot option -S 256M to 256 MByte.
But this should only become an issue for files one flashes which are larger than 512 MBytes, and this file is slightly below that (422329 KB).
Good morning!
I reverted my 10 V with SFOS 4.6.0.15 back to android 13. Locked the bootloader. Moved to android 14 wirh Xperia Companion. And then unlocked BtL again.
I added the Sony aosp new file in Sailfish 4.6.0.15 image file.
The normal flashing does not succeed. The is some error with partition file??? I tried loading from Sony pages with Edge and Firefox. No differences.
If I use the long script for reflashing as shown in [Release notes] Sauna 4.6.0.15, the phone 10 V is corrupted. I wil get it in live again with Xperia Companion app. I did this twice. No result.
So, what shall I do now? My 10 V has at the moment Andr 14 and bootloader is opened again.
Do you mean you substituted the original blob that Jolla recommended with the November blobs and put the November blobs in the folder that contains the install.sh script?
If so, this did not work for me. The Jolla install scripts requires the old blobs.
I needed to reflash oem after installing 4.6.15 with fastboot. Substituting the Jolla recommended blovs with different version and using the Jolla install script in one step did not work for me.
Fresh clean install according to Jolla instructions and then flash oem with fastboot is probably the way to go
Dear Meego-Junky,
Exactly. Or what should I do? If I’m in Sfos 4.6.0.15, wha should I do with the new blobs? The instructions are so mixing up!?
were you able to install 4.6.15 with blobs “SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi”??
This should work in freshly installed Android. In addition the fresh installed Android needs to booted up once and initialized before Sailfish flashing
Yes, I booted up with Android. Now I’m back in Sfos 4.6.0.15 with v3a blobs again.
now after rebooting into fastboot you should be able to flash the new blobs “SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img” with
fastboot flash oem SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
or
fastboot flash oem_a SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
as @direc85 pointed out
in my device the result is the same, flashing oem or oem_a
Hopefully this is then what you wanted
1 Like