Unable to upgrade on my 10 V. I manage to get to the screen with the white bar, but when it reaches the end, it just says “Sailfish OS could not be updated. Please try again later.”. Upon reboot, the system starts as normal, but is not updated (obviously). Have repeated four times with the same issue.
After a failed attempt, look in /var/log/systemupdate.log for any errors.
Also, make sure there is plenty of space on the root partition before starting the update.
5 Likes
stupid me acted first read later and got into trouble - I was not sure what code it asked when #3 (shell) and aborted telnet - now i cannot connect to the phone!? 
$ telnet 10.42.66.66
Trying 10.42.66.66...
Connected to 10.42.66.66.
Escape character is '^]'.
Sorry too many failed lockcode attempts.
And it has not been 24 hours since last attempt.
Connection closed by foreign host.
is this lock code the one I use for unlocking the device? can I do anything but waiting for 24 hours? I need the phone tomorrow for work…
I cannot even switch off the phone (XA2 Plus)
Yes, the lock code is the device lock code you have set. And you probably have to wait for the 24 hours timeout.
You can force power off the device by holding down the volume up and power key until it vibrates 3 times.
2 Likes
I tried the forced power off now it does not connect to the device…
$ telnet 10.42.66.66
Trying 10.42.66.66…
telnet: Unable to connect to remote host: Connection timed out
@Keto now I’m in but Iget different result for cat - can I use the mentiond dd fix?
~ # cat /proc/cmdline
rcupdate.rcu_expedited=1 core_ctl_disable_cpumask=0-7 lpm_levels.sleep_disabled=1 display_status=on selinux=0 androidboot.selinux=permissive msm_rtb.filter=0x3F ehci-hcd.park=3 coherent_pool=8M sched_enable_power_aware=1 user_debug=31 systemd.legacy_systemd_cgroup_controller=yes androidboot.hardware=voyager androidboot.verifiedbootstate=orange androidboot.keymaster=1 androidboot.veritymode=enforcing root=/dev/dm-0 dm="system none ro,0 1 android-verity /dev/mmcblk0p78" androidboot.bootdevice=c0c4000.sdhci cei_project_id=BY46 cei_phase_id=MP cei_sku_id=GINA cei_simslot_id=dsds cei_mainboard_id=SM42 androidboot.ceibootmode=0 cei_color_id= androidboot.baseband=sdm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_td4328_tianma_fhdplus_cmd:config0:1:none:cfg:single_dsi androidboot.slot_suffix=_a rootwait ro init=/init androidboot.bootloader=xboot oemandroidboot.xboot=1310-0301_X_Boot_SDM630_LA1.0_O_123 androidboot.serialno=CQ3001AV82 startup=0x00008001 warmboot=0x77665502 oemandroidboot.babe08b3=50000000 oemandroidboot.imei=*** oemandroidboot.security=0 oemandroidboot.securityflags=0x00000003
Check output of hexdump -C /dev/mmcblk0p64, and if it has that boot-recovery, then you can try the dd command fix.
3 Likes
moi, kiitos for your help, system is recovered now…
4 Likes
Also to everyone, do not post the full /proc/cmdline here as it does contain the device IMEI. I should have noted that earlier.
6 Likes
moi, kiitos for your help, system is recovered now…
btw. my bootloader is different from other’s reporting the issue…
oemandroidboot.xboot=1310-0301_X_Boot_SDM630_LA1.0_O_123
1 Like
I have kde connect enabled on all my device, so after update I immediately noticed (seems to not be shown on sailfishos itself) it go through a so called optimization process for every android app installed. Bit curious what exactly this does.
I’ve never had this issue before in my 2 years of using SFOS, but indeed it was actually storage-related, per the update log. It took me removing what felt like half of the apps installed (the largest being MeeCast) but I got there in the end, lol.
Thank you for your help 
1 Like
Everything went buttery smooth on my Xperia 10 iii.
Nice additions to the AppSupport options!
Connectivity on AppSupport now seems to be completely rectified. Tested it with multiple connections, disconnections and VPN ON/OFFs, no hick-ups detected.
Since I did not read anything regarding progress on Xperia 10 V, I still did not try to install SFOS on it (currently on LOS). Apart from @catonyourcomputer , has anyone else with a 10 V tried to upgrade?
Edit: @catonyourcomputer I just read your last message. Do you see any noticeable improvements for 10 V?
5 Likes
I have temporarily disabled the update advertisement for XA2 devices, while we investigate what would be the possible ways fix the boot issues.
9 Likes
No immediate changes I’ve noticed, apart from the advertised ones relating to the AppSupport settings page. Camera, fingerprint sensor, and voice recorder remain non-functional.
I would test the other things, but I’m pretty sure it will be the same.
I’ll be keeping an eye on bluebinder as well throughout the next few days, as systemctl status seems to now be reporting it working correctly, whereas I recall it outputting a “no device found” error and having my battery for lunch (that is, unless I stopped the service). Maybe something changed? Will report back if anything of note.
1 Like
Update on 10 V appears to be fine here, flight-mode and camera issues still present but these are known.
(Update went smoothly on 10 III and C2 here also.)
1 Like
Ah, I didn’t see this and forced the upgrade with ssu haha. Mine also booted in recovery mode but it was easily fixed with your instructions.
I noticed that the new AppSupport settings appeared on my Xperia 10 iii but not on the XA2. Is this for newer devices only or did I do something wrong?
Upgrade on my Sony Xperia 10iii seemed to go fine, and new appsupport options have appeared in settings. Appsupport itself won’t start now (it was working fine before the upgrade) - it’s just in an endless cycle of trying to start, then stopping with the status ‘unable to start’, then trying to start again and so on. I’ve tried re-booting multiple times with different new options (MicroG, Contacts, Gallery, start at boot) set or unset, but it still keeps cycling endlessly. Any advice on how to fix this would be welcome.
4 Likes
It seems Patchmanager can sometimes be broken after the update.
It will appear to be running fine in the UI etc, but active patches don’t have any effect.
The fix is to re-install Patchmanager and reboot.
5 Likes
The new AppSupport settings are slightly different depending on the device and which AppSupport Android version it has. But Xperia 10 III and XA2 should both have AppSupport Android version 11, and same setting available.