Congrats on 10iii support.
I’ll join the party with v4.5.
Have you had any luck finding a firmware for Android 11. I’ve done as much searching as I can and the only thing I can find is site claiming to have them but downloads are behind a paywall (https://romdevelopers.com/index.php?a=downloads&b=folder&id=42274). Everything else I can find are Android 11 firmwares. Pretty stuck at this point.
No, i had no luck either. I ended up installing Windows 10 in an VM and downgraded with Emma.
Good news! Thanks to all contributors! Today I purchased a license for 10III. It has been a few years since I flashed and it makes me sweating carrots but I will try again.
Congratulations @Kea, great that you’re getting your Xperia 10 III. You’ll be fine with the flashing, if not, we’re all here to help
here you are, XQ-BT52_Customized EEA_62.0.A.3.109, extract files in a folder
You can install chum first and then install/update storeman via chum, too.
Hi all I just purchased a refurbished Xperia 10 III and a new license. I’ll give my current Xperia 10 II to my girlfriend, as her original Xperia X is slowly failing. Thanks to all involved for this new release Cheers, Sam
I have bought my 10 III licence - thank you Jolla.
Look forward to making use of it soon ™.
Yesterday, I managed to install SFOS 4.4 on my Sony Xperia 10 III. Basically, it went smooth, but there were a few unclear issues. Perhaps the following can help to improve the instructions.
First of all, it was not clear to me which service level of Android 11 is best. Perhaps it doesn’t matter, as long as it is Android 11: then it would be good to day so. I recall that in the past it was recommended to install all the latest Android updates before flashing, that’s why I’m asking. In the end I updated to 134 and things worked fine.
Second, on the latest Ubuntu (22.04), perhaps already earlier, the Android fastboot package is called “fastboot”, not “android-tools-fastboot”.
Third, after flashing everything looked as described in step 7.11, but after removing the cable the blue light stayed on and no combination of keys could make the device reboot. After panicking a bit, I decided to try out the following: reconnect in fastboot mode and reissue the flash command. That command failed (as expected), but afterwards the device booted without problems. Something must have completed that didn’t before.
After using the phone for one day, I can say all seems well. All apps seem to run fine. Smooth user experience. Thanks to the Jolla team for a great job!
About that persistent blue led and unwillingness to react to on/off switch; for me “sudo fastboot reboot” did the trick. No need for reflash.
With help from a family member with a linux computer flashing went smooth. Jolla’s instruction was clear. When unlocking with Sony’s program I had to do Google’s ReCaptcha… Don’t remember that I had to do that formerly.
Positive: the system now works much faster and wifi connection is more reliable! Having more storage is also nice.
Problem: after choosing a language, Sailfish asked for a security code, which I typed. Then the screen froze. I only could go further after inserting a sim and typing the sim code. Encryption info says that the device is encrypted.
Installing fingerprints does not work. A new code is asked and nothing happens when touching the home button.
Problem : I installed Search Engines from Storeman, but no list appears in the browser app. I don’t like the ‘big four’ so I installed a Duckduckgo app from FDroid.Hope this is temporaily.
Apps: several apps that I used disappeared from Jolla Store: Tooter, Bible’me (where is thebootroo?), Unit Converter, Tiny Todo, Quicklist, Nieuwsfoto’s, ForgetitNot, Petals, Wifi Analyser and more. Some apps from Storeman cannot be installed, such as Sailfish Podcast (Pod).
Device: lightweight, that’s nice! It also feels good in the hand.
A negative point is readability. Fortunately Sailfish texts can be enlarged, thank you! Yet other texts still are very small. To my opinion the ratio of the XA2 was the best, together with the larger XA2+.
Thanks to the developers, I can go on using Sailfish!
Probably because they do not have a aarch64 binary at Store. Try Chum or Storeman.
About that persistent blue led and unwillingness to react to on/off switch
I believe instructions are slightly off: they meant to write “longpress the power button until device reboots”, as that’s how it’s been for previous devices.
There are e.g.two metronome apps in Storeman from 2014 and 2017. They can’t be installed because of no aarch64. So not one metronome app available.
Well, if you can find the source then maybe, just maybe, someone can help you build one.
That’s open source, sometimes you have to do it your self.
At least the names would be helpful. There is a wiki page at Apps that haven't been ported to aarch64 which I track and try to 1. alert the authors, 2. failing that try to move things to chum to make the apps available if they have licenses that permit. All help appreciated!