Version 5.2.0.11 is the first release mentioned in the release notes.
I can’t say which version the JP26s shipped at the first-day event. I was in batch #1 and received it by posti.
Version 5.2.0.11 is the first release mentioned in the release notes.
I can’t say which version the JP26s shipped at the first-day event. I was in batch #1 and received it by posti.
5.2.0.13 update highlights
I received the phone with 5.2.0.15.
Which does not explain this:
But maybe (random!??) could explain the situation now?
@bardoftruth I would try to reset once more, see if it boots up, then immediately connect WiFi and update again. But definitely after mal answered
Day 1 event phones were 5.2.0.11 if it was Orange and 5.2.0.13 if it was Black. Those who ordered White, got Orange phone.
It’s possible that an update to version 5.2.0.16 will help me with my current situation.
As I wrote, I already installed the update to 5.2.0.16 last Friday. About 12 hours later, the JP26 restarted and then got stuck in a bootloop for several hours (only the Jolla logo is visible at the beginning, then it restarts. I don’t see the UI). After that, I tried a factory reset, and since then version 5.2.0.11 has been installed.
I’ve tried several factory resets, but I haven’t been able to get to the point where the UI (Welcome Screen) appears. A Wi-Fi connection is not possible.
Currently, I can boot into recovery mode and connect via SSH. I can access the system using chroot.
As described above, I can read various debug information if needed. I’ve gotten to the point where I have an internet connection, including DNS (ping sailfishos.org is possible), via USB through my Linux host in recovery mode/chroot.
Unfortunately, an upgrade using the following commands isn’t possible:
/ # ssu re
Device release is currently: 5.2.0.11
/ # ssu re 5.2.0.16
Changing release from 5.2.0.11 to 5.2.0.16
Your device is now in release mode!
DBus unavailable, falling back to libssu
/ # version --dup
Enable developer mode to use rnd-dist-upgrade.
Perhaps there’s another way to perform the upgrade, or I need to do something else first.
Maybe sfos-upgrade from openrepos works?
I screwed up my new J2 tinkering too much. My bad. How can I do a factory reset from terminal (I can ssh into the phone)?
I’m not sure if you should use a factory reset. It might still be possible to repair your JP26 Sailfish OS, but you should start a separate forum thread for that.
I’m still stuck in a bootloop, even after a factory reset.
This seems to be a problem specific to my JP26.
When starting JP26, when the Jolla logo appears, hold the volume up button.
Afterward, three menu items should appear in the middle of the screen:
[Recovery Mode] <<==
[Fastboot Mode]
[Normal Mode]
Use the volume up button to navigate.
Select [Recovery Mode] <<==
Now press and hold the volume down button.
The recovery mode should now start.
Connect the USB cable to your PC/laptop and connect via Telnet to the IP address 10.42.66.66. This should put you in recovery mode, where you can start the SSHD service. After that, you can connect to the IP address 10.42.66.66 via SSH.
On Linux, this works without much effort.
On Arch Linux, I had to add the IP address 10.42.66.67 to the USB network interface for the Telnet connection to work.
I got the instructions from the official documentation.
Thank you. Everything back to normal again. I reset the phone.
So you performed a factory reset and then the JP26 started up normally again?
I’m glad to hear your JP26 is working again. ![]()
don’t screw it up again ![]()
I’ll be more careful ![]()
Have your tried if you can install zypper (pkcon install zypper) and then zypper dup? Maybe zypper ref is needed before the distribution upgrade.
Have you tried the file system check (option #4), in case there is something wrong with the filesystem that prevents the boot?
thanks for your suggestions
Unfortunately, I cannot use pkcon:
recovery:~ # chroot /rootfs/
/ # pkcon
Failed to contact PackageKit: Could not connect: No such file or directory
/ # pkcon install zypper
Failed to contact PackageKit: Could not connect: No such file or directory
zypper is also unavailable.
/ # zypper
/bin/sh: zypper: not found
Yes, I performed a file-system check.
It ran without errors.
Maybe I can install zypper manually.
Does anyone happen to have the URLs for the current RPM packages for the JP26?
I found the following in an old forum thread, but of course I can’t install these packages anymore; they’re too old:
For me in the update limbo-state the pkcon update just complained Failed to contact PackageKit: Could not connect: Connection refused and because there was no Internet-connection, version --dup would wait for eternity in REFRESHING CACHE AND DOWNLOADING PACKAGES. But zypper worked and could finish the incomplete dist-update, so maybe it can help you also. Install at least zypper from these links and if it complains about missing depencies, download install them as well: https://releases.jolla…