I updated my post. Follow the thread mentioned. If you join the Telegram group Sailfish OS Fan Club, there are people most willing to help with specific problems.
Thank you for the tips but I have a problem entering to sshd
I enter to jolla recovery 2.0
Option 5) Run sshd
Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won’t be shown for security reasons)
Device /dev/sailfish/home doesn’t exist or access denied.
Device /dev/sailfish/home doesn’t exist or access denied.
[OK] Code accepted.
Starting sshd on 10.42.66.66.
Login: xxxx
Password: xxxxxx
Press [Enter] to stop sshd…
Cant enter any command.
If use option 3) Shell
If you continue, this may void your warranty. Are you really SURE? [y/N] y
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
2 logical volume(s) in volume group “sailfish” now active
Device /dev/sailfish/home doesn’t exist or access denied.
Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won’t be shown for security reasons)
Device /dev/sailfish/home doesn’t exist or access denied.
Device /dev/sailfish/home doesn’t exist or access denied.
Device /dev/sailfish/home doesn’t exist or access denied.
[OK] Code accepted.
/ #
And no more, cant enter commands, any clue?
Hi,
for me it’s the same problem. After updating to the official Sailfish OS Pallas-Yllästunturi (3.4.) today my XA2 shows also 3 white flashing screens and nothing happens.
How can I resolve this and how can I connect via SSH into my phone than it doesn’t start?
Thanks.
Had the same issue with “Try again later”. Phone restartet and was not update, even after some retries. For me tool “sfos-upgrade” worked and the update finished successful.
I still cant use my phone, cant access to telegram so my hopes are this forum, it seems that it is a mistake that affects many people but all the fixes are explain for people that have a average use of linux terminal.
Maybe im stupid but i cant even connect to ssh.
1 Like
OK I re-explain all…
I can boot into recovery mode, if you read the post up there I can get the recovery menu but sshd or shell doest response. Please I get out of ideas, some help ors welcome.
I have just updated my xperia X to 3.4.0.24 and after reboot I got black screen just a few seconds after system already booted. When arriving new messages their pop-ups displayed corrrectly though.
I connect to it through ssh (not from recovery but as usual ssh nemo@ip_addr) and remove storeman:
pkcon remove harbour-storeman
and it helps for me.
2 Likes
So I dont need recovery mode?
Just with putty and nemo@ip adress?
How to know the ip adress?
1 Like
If you try to connect through WLAN, it is the IP given to the phone by the DHCP of the access point, or if you are trying the USB-cable, the default is 192.168.2.15
More info about this in at least these articles:
https://jolla.zendesk.com/hc/en-us/articles/202011863
https://jolla.zendesk.com/hc/en-us/articles/202004823
Phone dont boot, these links are for a phone that works.
Then recovery mode is your only option. Are you sure the phone doesn’t boot at all instead of booting, but the screen staying blank?
Screen is black but not turned off
happend to my xperia xa2 ultra too. phone is now bricked: it boots, shows the sony logo, screen blinks 2 times or so and then nothing, the phone stay black.
how do i get into this famous recovery mode everbody here talks about?
@strobovalo
You can find IP in your router config, like “device lists” or “dhcp settings”. Then connect to it by nemo username and password, you previously enabled in developer mode section and ssh.
If you cannot boot the phone or connect to it, your only option is to reset to defaults by recovery mode, could you try this?
Yes i know my phone is bricked cant access to wlan, by the way is now with factory reset and 2.x version, los many things but at least works.
Thanks to all for help.
Now I’m finding myself in the same situation: Upgrade to 3.4.0.24 (using sfos-upgrade) failed, due to the faulty Aliendalvik Control version. I was unaware that it didn’t update (had read about it in the release notes but missed the version differences). Booting shows Sony Splash plus 3 flickers as described in OP.
Well, I did manage to delete the package but now I’m stuck in recovery mode (chroot /rootfs) without any network connection.
Does anyone know how to connect to WLAN from recovery so I can retry upgrading?
Alternatively I would try to SSH into the running OS (I imagine only lipstick fails to start), but can’t since I don’t know how to turn on WLAN and configured USB mode to always ask before granting SSH access. Can this be modified from terminal?
1 Like
Did you try to install the rest of the upgrade packages while in recovery mode?
1 Like
If in recovery but unable to access file system, this might help - https://together.jolla.com/question/138839/how-to-run-command-from-recovery-mode/?answer=138840#post-id-138840
If I remember right, (it’s been a while since I did it), I think you don’t need the chroot part on X. Just mount Sailfish_home to /mnt, and cd to mnt and roots should be there…
Another thing that might help with a brick is fastboot flash system file from your original download zip. If the system was unmodified, it should flash back without any effect on your data…
1 Like
In the end that was what did the trick. I was under the impression repeating the whole upgrade process is necessary. At first I tried to enable ethernet forwarding in order to use my desktops internet connection while in recovery. That was fruitless.
Somewhere in the process I also enabled the ‘rescue usb connection mode’ allowing me to ssh into the running system. I knew from the journald logs that Lipstick couldn’t start. All the rest seemed intact. No factory reset necessary. So I tried manually enabling wlan0 interface in order to redo the upgrade (no dice thanks to rfkill).
Literally the last thing I did before calling it a night was executing ‘pkcon update’. 2 Minutes later Lipstick came to life asking for my lock code. I had left the zypper cache alone even though one ZenDesk article I consulted suggested removing it in case of a failed upgrade .
Lucky me…
I understand why in some cases removing the zypper cache is something you would want to do on failed upgrade and why they recomend it, but on 3.3 -> 3.4 upgrade my Xperia 10 got stuck to the point the recovery console without internet and broken pkcon was only I had and using zypper to complete the upgrade from already downloaded cache saved me from doing factory reset or reflash.