Reattach the usb cable. Open a cmd prompt in the directory and type: fastboot reboot
I’m afraid I went with @miau 's choice there as I hadn’t yet seen yours @arpadf78 … is this gonna be a problem? … because I can tell you … once I did that I was spent … but I can see now … I’ve got Sailfish on my device … finally! : ) …
now is there anything I need to bear in mind? … anything more I need to do so?
Thanks to @ljutica for first creating this entry … have you ever made it properly work?
for @nephros , @jameson and @Blumenkraft to have helped me a little here and there too to get my issue solved
and in a way my biggest thanks to @miau there for patiently walking me through stuff with various entries
and thanks Jolla for this nice system
3 Likes
if I have forgotten someone, please let me know and I’ll add you to the list … I am sorry …
I understand it can be / was quite a chore to work with me and a chore for me to figure things out. Some things I’ve never heard of before like VOL+ / VOL- and booting it up, etc … all these modes and the tool Emma and separate drivers, etc … Thanks everyone for your patience and help! Keep up the good work and I hope I didn’t cause too many grey hair? ; ) I’m new to the whole thing … there’s unfortunately lots I sitll don’t know but the phone is now using Sailfish, hooray!
3 Likes
After the reboot you should be happy Sailfish OS owner 
thank you … I’ll definitely check this out too : )
Thanks a lot, your guide is exactly right!
After a lot of fuss, I succeeded.
It should read:
Unlock bootloader
Emma → 62.0.A.3.109
Relock bootloader
OTA → 62.0.A.3.131
OTA → 62.0.A.3.163
OTA → 62.0.A.9.11
Unlock bootloader (again)
Install SailFish
2 Likes
Hello,
Presumably like a lot of people, I stopped at this point (as per the Jolla instructions, and then installed Sailfish.
What additional functionality does the further updates bring (if known?), and should I be thinking of a reflash (though actually, presume with Android that’s not possible anymore)??
The phone is generally working well (much nicer than the xperia x) but I do have a few annoying bugs/issues.
2 Likes
We’re happy to confirm that Android 12 is ok for Xperia 10 III. Installation instructions as well as help desk article are updated. That said, Xperia 10 III devices with Android 11 have been used more as daily devices. Thus, we recommend using Android 11.
We hope that this helps you all. Thank you!
12 Likes
Could flashing the phone from Android 12 solve some bugs?
The echo cancellation and this bug are annoying.
1 Like
Is this likely to be the case for the 10 II at some point too?
Unfortunately flashing Android 12 to your Xperia 10 III will not fix echo cancellation issue. Discussed also over here. Further, I do not believe that disappearing sound and freezing video would get fixed either.
From my past experience it has been actually other way round. When developers have (back)ported something for a device adaptation let’s say for wlan driver, then when upgrading beyond the recommended Android version the wlan driver started acting up as the adaptation fix no longer worker.
1 Like
The audio bug is also present when Android 12 was installed prior to SFOS. I tested Android 12 and 3 different Android 11 releases and the bug always occurs.
This good news.
The first thing my 10 III did at power on/config, was to immediately update to android 12 as soon as the wifi was running.
1 Like
Posting here for posterity:
https://combinedfleet.keybase.pub/Firmware%20backups/XQ-BT52
This nice gentleperson has kept an archive of past Sony firmware packs, including the 62.0.A.9.11, enabling a simple and direct path using newflasher, rather than jumping through multiple hoops.
4 Likes
Could you also tell us which is the recommended Android 11 version?
62.0.A.3.109 that can be installed by Emma, and version that shipped with my phone,
or 62.0.A.9.11 that can be installed by OTA?
What is the recommended one? Official guide only mentions the first one, and not doing any further OTAs, meanwhile people here recommended to OTA. Which one was tested the most?
2 Likes