Sailfish 3.0 update
asked 2018-10-31 18:40:55 +0300
I have a work phone and a private phone. Both Xperian X.
One phone did update the other is hanging at the Sailfish OS screen. Did not start the update at all.
Do not know what to do now.
1
9 Answers
answered 2018-10-31 20:59:22 +0300
Got my Xperia X to update:
- Reboot by pressing volume up + power button for few seconds
- Go to terminal, devel-su and type:
# ssu release 3.0.0.5
# version --dup
Comments
answered 2018-10-31 19:08:34 +0300
Comments
1
Same here with Jolla 1. Stuck at 0%. After two hours I removed the battery to reboot. Then update runs within some minutes.
SaimenSays ( 2018-11-01 02:37:02 +0300 )editSame here with Jolla 1, Removed the battery after about 1 hour, tried again. The interesting thing is that it redownloaded the update again. After that, the update behaved the same way - progress bar stuck at 0 %.
EDIT: tried the command line way. It crashed while downloading the data, with the following in dmesg. I have switched off WiFi and connected via cellulal network, and then the update downloaded and installed correctly.
[12227.897480] PK-Backend: unhandled page fault (11) at 0x412a7e20, code 0x017
[12227.897510] pgd = dbad4000
[12227.897510] [412a7e20] *pgd=aebac831, *pte=00000000, *ppte=00000000
[12227.897572] Pid: 17314, comm: PK-Backend
[12227.897572] CPU: 0 Tainted: P W O (3.4.108.20180601.1 #1)
[12227.897602] PC is at 0x4019a8f4
[12227.897602] LR is at 0x11dc3
[12227.897602] pc : [<4019a8f4>] lr : [<00011dc3>] psr: 200e0030
[12227.897633] r10: 4376ee50 r9 : 4376ee50 r8 : ffffffff
[12227.897633] r7 : 0000501a r6 : 00004c9b r5 : 00000000 r4 : 451ec5f8
[12227.897663] r3 : 00005382 r2 : 43f676d4 r1 : 00000002 r0 : 41219008
[12227.897663] Flags: nzCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[12227.897694] Control: 10c5787d Table: 9bcd406a DAC: 00000015
[12227.897724] [<c010b73c>] (unwind_backtrace+0x0/0x118) from [<c010f658>] (__do_user_fault+0x6c/0xb4)
[12227.897755] [<c010f658>] (__do_user_fault+0x6c/0xb4) from [<c08a3664>] (do_page_fault+0x358/0x3e8)
[12227.897785] [<c08a3664>] (do_page_fault+0x358/0x3e8) from [<c01002f8>] (do_DataAbort+0x134/0x1a8)
[12227.897816] [<c01002f8>] (do_DataAbort+0x134/0x1a8) from [<c08a1ed4>] (__dabt_usr+0x34/0x40)
[12227.897816] Exception stack(0xe8ad7fb0 to 0xe8ad7ff8)
[12227.897846] 7fa0: 41219008 00000002 43f676d4 00005382
[12227.897846] 7fc0: 451ec5f8 00000000 00004c9b 0000501a ffffffff 4376ee50 4376ee50 00000001
[12227.897877] 7fe0: 00000000 446dd6e8 00011dc3 4019a8f4 200e0030 ffffffff
[12227.897877] PK-Backend(17305) send signal 11 to PK-Backend(17305)
[12227.973384] wlan: [801:E :PE ] __limProcessAddBAReq: 1425: ADDBAREQ NUMBUFF 40
answered 2018-10-31 22:19:37 +0300
Went for an icehockey match tonight and just checked the news and i was suprised and updated during the game ota. Worked perfectly as always. SF3 runs smoothly and feels way faster than sf2 on my Xperia X. Great job guys. I like the new top-menu. Offers many new options i've missed in the past. So far i like it!
Comments
answered 2018-10-31 21:43:38 +0300
Update from GUI failed on both Jolla 1 and Aquafish (made as Jolla C). Version bump from the terminal went okay. All seems to work on first look.
Comments
In series of stupid questions...
Long time since used Jolla 1 last time (newer needed to manually update but have connected through terminal some times). Now did update and failed (hanged) for me also. So what are the correct steps to do manual update like mentioned here to not get Jolla 1 bricked while it's freezing at sailfish os proggress bar after reboot (when update should have begin).
I did check out tutorials at jolla.zendesk.com but none of those fully describes situation what update seemed to end up with.
So what are simple steps to preceed the safe way?
huuhaa ( 2018-10-31 22:55:59 +0300 )editanswered 2018-11-10 20:23:34 +0300
I have experienced two different kinds of upgrade failures at the GUI, lately.
Unfortunately most posts in this thread do not mention the original and target version of SailfishOS for which the upgrade failed, on which device and when exactly in the upgrade process the failure occurs.
The two modes of failure I experienced were:
- When upgrading from SailfishOS 2.2.1 to 3.0.0 (tested on an Xperia X):
Upgrade is downloaded, rebooting into upgrade screen occurrs, upgrade is not installed (progress bar does not start at all), hence the upgrade screen hangs.
When rebooting (e.g. per pressing Volume up and Power buttons simultaneously for a while), the old SailfishOS version is booting fine.
The /var/log/systemupgrade.log shows a packagekit (PK-Backend with kernel: functions_store: android_usb: Cannot enable 'none' (-22)) failure exactly as @teve has posted it (the other extracts from the systemupgrade.log show slightly different PK-Backend failures).
When performing the same SailfishOS upgrade (from 2.2.1 to 3.0.0) at the command line all output messages are looking fine.
Furthermore, also the same pattern of error message #2 is also found in the systemupgrade.log (additionally). - When upgrading from 2.2.0 to 2.2.1 (tested on an Xperia X and a Jolla 1):
Upgrade is downloaded, rebooting into upgrade screen occurrs, upgrade is installed (progress bar reaches the end), finally the upgrade screen hangs.
When rebooting (e.g. per pressing Volume up and Power buttons simultaneously for a while), everything is fine (checked that version --dup does not want to install / remove anything).
The /var/log/systemupgrade.log shows many entries interspersed and ends in a couple of ten such entries (this may or may not be related to this upgrade failure):
mce[3275]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
When performing the same SailfishOS upgrade at the command line, all output messages are looking fine. - Other failure modes may occur. Specifically the Jolla C seems to show a separate issue.
Comments
This morning I had the same problem. I downloaded the new version and after the reboot the white bar of the installation did not move on. The solution was to clear the free space of internal memory. I delete some apps and the after the reboot the update start. It needs many space! I had 1,2GB free space and after the update I had 4kb with a warning after the first start SFOS 3. I delete also all movies and pictures from Whats app to get more space. I think SFOS need this only temporary then after some minutes I had more free space. Please test and you would see it helps.
Ralf ( 2018-11-10 21:31:34 +0300 )edit1
I tried to update my Jolla Phone today to 3.0.0.8 as I don't use Early Access and got the same problem like many other people here, GUI update stuck with progress bar at the very beginning. Then I tried to reboot but pressed the wrong button (volume down instead of up), so I removed the battery for a moment. Then fortunately the phone started normally to current OS version 2.2.1.18 (I was very scared I would have messed up my phone completely). I'd like to upload my systemupdate.log here (maybe it's helpful for the dev team) but I don't have enough Karma for that (need only 11). Most of the lines are the same and read:
Nov 10 12:00:04 Sailfish mce[614]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Btw. there seems to be a typo (curernt) in the log file in line 3553:
Nov 10 12:18:46 Sailfish kernel: USB::otg msm_otg_notify_chg_type chg_type=INVALID_CHARGER(0) curernt chg_type=2
Maybe I'll try the update via console. Does it make any difference if I do this over SSH or with the native CLI app directly on the phone? What is it about devel-su? Is it the same like the su or sudo command? Which password?
Pohli ( 2018-11-10 22:55:56 +0300 )editanswered 2018-12-07 13:40:34 +0300
Jolla 1 user here. Unfortunately, less of an answer, but another update issue.
I attempted an update in the GUI to 3.0.0.8. It was downloaded and the update started with the progress bar steadily moving. When it reached 100% (maybe less, but close, wasn't looking) the device rebooted, but only shows a black screen after the Jolla boot logo.
Interestingly, short presses of the power button toogle the LED on/off (white). Long press, the device seems to shutdown (LED become red). I removed the SIM, which makes no difference. There was no SD card present during the update, but the phone was on charger the whole time.
I booted into Recovery Mode and can mount mmcblk0p28.
/var/log/systemupdate.log abruptly ends:
Dec 07 09:24:47 Sailfish systemd[1]: Starting Sailfish OS upgrade UI....
Dec 07 09:24:47 Sailfish mce[567]: modules/display.c: mdy_flagfiles_osupdate_running_cb(): osupdate_running flag file present: true
Dec 07 09:24:47 Sailfish systemd[1]: Started Sailfish OS upgrade UI..
Dec 07 09:24:47 Sailfish sailfish-upgrade-ui[614]: Upgrading to Sailfish OS 3.0.0.8 from 2.2.1.18
Dec 07 09:24:47 Sailfish systemd[1]: Started OS update logging.
...
Dec 07 09:38:30 Sailfish packagekitd[626]: Install progress update: 610 of 798
Dec 07 09:38:30 Sailfish sailfish-upgrade-ui[614]: Package: ssu-network-proxy-plugin;0.43.11-1.7.2.jolla;armv7hl;jolla, Network Proxy support for ssu
# grep -A 10 'SW update' systemboot.log shows that the sequence of the update and reboot(s) was somewhat different than in the previous two upgrades.
20180801_110402 Shutdown: SW update reboot
20180801_110406 Startup: pwr_on_status=pwr_on_by_SW_reboot
20180801_110408 Received: dsme internal state USER
20180801_110920 Received: reboot request from dsme
20180801_110922 Received: dsme internal state REBOOT
20180801_110924 Shutdown: SW reboot request
20180801_111013 Startup: pwr_on_status=pwr_on_by_SW_reboot
20180801_111014 Received: dsme internal state USER
20180804_024530 Received: battery empty
20180804_024538 Received: dsme internal state SHUTDOWN
20180804_024547 Shutdown: Battery empty
--
20180925_112926 Shutdown: SW update reboot
20180925_112930 Startup: pwr_on_status=pwr_on_by_SW_reboot
20180925_112930 Received: dsme internal state USER
20180925_113612 Received: reboot request from dsme
20180925_113613 Received: dsme internal state REBOOT
20180925_113616 Shutdown: SW reboot request
20180925_113700 Startup: pwr_on_status=pwr_on_by_SW_reboot
20180925_113700 Received: dsme internal state USER
20181031_210307 Received: battery empty
20181031_210315 Received: dsme internal state SHUTDOWN
20181031_210325 Shutdown: Battery empty
--
20181207_083757 Shutdown: SW update reboot
20181207_083759 Startup: pwr_on_status=pwr_on_by_SW_reboot
20181207_083759 Received: dsme internal state USER
20181207_084147 Startup: pwr_on_status=pwr_on_by_SW_reboot
20181207_084147 Received: dsme internal state USER
20181207_094738 Received: shutdown request from dsme
20181207_094738 Received: dsme internal state SHUTDOWN
20181207_094744 Shutdown: SW shutdown request
20181207_094903 Startup: pwr_on_status=pwr_on_by_pwr_key
20181207_094903 Received: dsme internal state USER
20181207_094744 Startup: pwr_on_status=pwr_on_by_pwr_key
I also noticed that the timestamps of the upgrade are off by one hour.
- device was updating with progress bar
- it rebooted and was showing a blank screen after Jolla boot logo
- I switched off the device manually ~10mins later
- as described above, normal boot does not progress beyond boot logo...
Is it possible that the upgrade was still in progress when I shutdown the device, despite it had already rebooted once by itself during (at the end of?) the upgrade but nothing was shown on screen for 10 minutes? Is there a way to yank the device back into trying to proceed with the upgrade without a factory reset? Cheers.
EDIT: 08.12
It seems that the normal boot reaches network.target, because the device connects to known WiFi and SSH is listening.
Too bad I used the auto-generated SSH password the last time and don't remember it. So it seems that somehow graphical.target fails.
Comments
1
Thanks a lot, @JSE, this is what I ended up doing by myself too.
There was no GUI to work with on the phone, so once I figured out that the network stack actually starts, I changed nemo's password manually in /etc/shadow in recovery mode and also changed sshd config to allow me in, skip PAM, etc... Developer mode had been already activated previously, so after a reboot from Recovery Mode, I could ssh in. The device already reports 3.0.0.8, but it does not work correctly.
Before hacking the password, I also tried setting various boot targets as default: getty.target did not work, then I tried system-update.target which actually truncated /var/log/systemupdate.log and started writing to it, but it did not look like a successful attempt at an upgrade.
I'm just about to run version --dup, fingers crossed...
Unfortunately it did not resolve the issue. Upgrade from CLI completed, but after reboot, there's still no GUI. At least I can still ssh in and investigate the running system.
Tried to run csd from the ssh terminal, not hoping for it to actually start, but at least report an error that there is no display, etc..
- I seem to have a corrupted shared library "csd: error while loading shared libraries: /usr/lib/libsystemsettings.so.0: file too short"
- -rwxr-xr-x 1 root root 0 Nov 5 22:03 libsystemsettings.so.0.4.30
- rpm/pkcon says nemo-qml-plugin-systemsettings-0.4.30-1.14.2.jolla.armv7hl provides this shared lib, which is already installed,
- However, I cannot reinstall this version of the package, pkcon says it cannot find it in any repository...strange, I seem to have newer nemo-qml-plugin-systemsettings and csd than what the 3.0.0.8 repo has.
- could these ended up being installed when the device was in for repair? csd was working fine on 2.x.x.x
- furthermore, jolla-devicelock-encpartition.service and nemo-devicelock.socket are in a failed state, but I don't have a device lock code set, so it may be just that
Maybe I'll try a downgrade to 2.x.x.x, but first try downgrading nemo-qml-plugin-systemsettings and csd to see if it makes any difference.
Installed nemo-qml-plugin-systemsettings-0.4.30-1.14.2.jolla.armv7hl (installed)
Available nemo-qml-plugin-systemsettings-0.3.0-1.3.1.armv7hl (jolla)
Installed csd-0.14.8-1.16.3.jolla.armv7hl (installed)
Available csd-0.11.0-10.4.1.jolla.armv7hl (jolla)
1
Success. It seems there have been some weird package cache issue.
devel-su
pkcon refresh force
pkcon install --allow-reinstall nemo-qml-plugin-systemsettings
Then after a reboot, the SFOS 3.0 welcome screen appeared. There are a bunch of packages that cannot be updated via pkcon still, but that's for another day.
[root@Sailfish nemo]# pkcon update
The following packages have to be installed:
droid-system-packager-0.1.9-10.1.1.jolla.noarch
factory-session-0.1.2-10.1.1.jolla.noarch
fastdormancyd-0.0.3-10.1.1.jolla.armv7hl
feature-xt9-0.0.5-10.2.1.jolla.armv7hl
geoclue-provider-here-0.0.17-10.2.1.jolla.armv7hl
here-agreements-1.5.2-10.1.1.jolla.noarch
here-daemons-1.5.3-10.1.1.jolla.armv7h
jolla-handwriting-0.1.1-10.2.1.jolla.armv7hl
jolla-recovery-sbj-0.3.1-10.2.3.jolla.armv7hl
jolla-xt9-0.5.9-10.2.1.jolla.armv7hl
jolla-xt9-cp-0.2.7-10.2.1.jolla.armv7hl
libherepositioning-1.5.3-10.1.1.jolla.armv7hl
libhybris-sbj-0.0.0.51-10.2.1.jolla.armv7hl
libhybris-sbj-libEGL-0.0.0.51-10.2.1.jolla.armv7hl
libhybris-sbj-libGLESv2-0.0.0.51-10.2.1.jolla.armv7hl
libhybris-sbj-libhardware-0.0.0.51-10.2.1.jolla.armv7hl
libhybris-sbj-libnfc-0.0.0.51-10.2.1.jolla.armv7hl
libhybris-sbj-libwayland-egl-0.0.0.51-10.2.1.jolla.armv7hl
libofonooemraw-1.0.2-10.1.1.jolla.armv7hl
qtscenegraph-adaptation-0.7.4-10.3.1.jolla.armv7hl
sailfish-hciwait-0.0.1-10.1.1.jolla.armv7hl
sailfish-rfkill-plugin-0.0.3-10.2.1.jolla.armv7hl
tohd-plugin-nfc-nxp-1.2.5-10.2.1.jolla.armv7hl
Fatal error: File './noarch/droid-system-packager-0.1.9-10.1.1.jolla.noarch.rpm' not found on medium 'https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-qualcomm-sbj/armv7hl/?credentials=store'
answered 2018-11-01 01:33:23 +0300
Aqua fish user here. Still on the Lapuanjoki. Should I upgrade to the next release first or I can go straight to SFOS 3 (via terminal, ofc)?
ok, I successfully installed it and it's great. Is it normal that I don't have white ambiences?
Comments
answered 2018-11-09 06:37:48 +0300
I had similar hang-up with Xperia X at the very start of the upgrade from 2.2.1 to 3.0.0 as OP. The upgrade was downloaded but SFOS upgrade screen showed no progress. systemupdate.log:
Nov 09 05:36:33 Sailfish sailfish-upgrade-ui[759]: Upgrading distribution jolla-configuration-f5121
Nov 09 05:36:33 Sailfish PackageKit[766]: uid 0 is trying to obtain org.freedesktop.packagekit.upgrade-system auth (only_trusted:0)
Nov 09 05:36:33 Sailfish sailfish-upgrade-ui[759]: Progress: 101
Nov 09 05:36:33 Sailfish PackageKit[766]: uid 0 obtained auth for org.freedesktop.packagekit.upgrade-system
Nov 09 05:36:33 Sailfish sailfish-upgrade-ui[759]: Progress: 101
Nov 09 05:36:34 Sailfish sailfish-upgrade-ui[759]: Progress: 0
Nov 09 05:36:34 Sailfish systemd[1]: Started ohm daemon for resource policy management.
Nov 09 05:36:34 Sailfish systemd[1]: Startup finished in 2.959s (kernel) + 3.443s (userspace) = 6.402s.
Nov 09 05:36:34 Sailfish sailfish-upgrade-ui[759]: Progress: 100
Nov 09 05:36:34 Sailfish sailfish-upgrade-ui[759]: Progress: 0
Nov 09 05:36:34 Sailfish sailfish-upgrade-ui[759]: Progress: 100
Nov 09 05:36:34 Sailfish systemd[1]: packagekit.service: Main process exited, code=killed, status=11/SEGV
Nov 09 05:36:34 Sailfish kernel: PK-Backend[781]: unhandled level 3 translation fault (11) at 0xf35d7a90, esr 0x92000007
Nov 09 05:36:34 Sailfish kernel: pgd = ffffffc0ae896000
Nov 09 05:36:34 Sailfish kernel: [f35d7a90] *pgd=00000000cd60b003, *pmd=00000000cdfe5003, *pte=0000000000000000
Nov 09 05:36:34 Sailfish kernel:
Nov 09 05:36:34 Sailfish kernel: CPU: 5 PID: 781 Comm: PK-Backend Tainted: G W 3.10.84 #1
Nov 09 05:36:34 Sailfish kernel: task: ffffffc0ad44c800 ti: ffffffc0ad7fc000 task.ti: ffffffc0ad7fc000
Nov 09 05:36:34 Sailfish kernel: pc : [<00000000f46988f4>] lr : [<000000000000f951>] pstate: 200e0030
Nov 09 05:36:34 Sailfish kernel: sp : 00000000f3a8c6e8
Nov 09 05:36:34 Sailfish kernel: x12: 0000000000000000
Nov 09 05:36:34 Sailfish kernel: x11: 0000000000000001 x10: 00000000aabaa978
Nov 09 05:36:34 Sailfish kernel: x9 : 00000000aabaa978 x8 : 00000000ffffffff
Nov 09 05:36:34 Sailfish kernel: x7 : 00000000000043f3 x6 : 000000000000407a
Nov 09 05:36:34 Sailfish kernel: x5 : 0000000000000000 x4 : 00000000f343f768
Nov 09 05:36:34 Sailfish kernel: x3 : 0000000000004756 x2 : 00000000f343f5fc
Nov 09 05:36:34 Sailfish kernel: x1 : 0000000000000002 x0 : 00000000f355b008
Nov 09 05:36:34 Sailfish kernel:
Nov 09 05:36:34 Sailfish systemd[1]: packagekit.service: Unit entered failed state.
Nov 09 05:36:34 Sailfish systemd[1]: packagekit.service: Failed with result 'signal'.
Nov 09 05:36:36 Sailfish mce[674]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Nov 09 05:36:36 Sailfish mce[674]: modules/proximity.c: report_proximity(): state: CLOSED -> OPEN
Nov 09 05:36:41 Sailfish mce[674]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Nov 09 05:36:46 Sailfish mce[674]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Nov 09 05:36:51 Sailfish mce[674]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Nov 09 05:36:57 Sailfish mce[674]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
After waiting over half an hour with no progress, and seeing these reports here, I rebooted and ssh'd in. I also checked from the GUI that phone was running 2.2.1 but the OS update tool said it was up to date. Device release was already set to 3.0.0.8 hence no upgrade available for downloading:
[root@Sailfish nemo]# ssu release
Device release is currently: 3.0.0.8
I did version --dup which succeeded cleanly and after a reboot I was running 3.0.0.8 just fine.
Comments
Just a silly question: Did anyone try to disconnect and reconnect power to the phone at the hanging state? I did not... Another question: Did you have your phone connected to power (me: yes). What happened to people with full battery and not connected to power?
The error message looks like the battery stuff is not available or no more available at that point.
cy8aer ( 2018-11-09 08:50:06 +0300 )editI didn't have charger connected at that time (had recharged overnight and had 100% battery when starting update from GUI), and also didn't connect the charger at any point. This was the first time I tried to update without charger, I guess (and immediately it failed, duh).
zagrimsan ( 2018-11-09 10:24:32 +0300 )editanswered 2020-04-28 15:13:32 +0300
Hi,
I found my old jolla and decided to test the SFOS 3 on it, but i'm having problems installing the 3.0.0.8 update. I noticed there were old post saying that i should try to install 3.0.0.5 first to get it working, but that didn't help at all. I am trying to install trough terminal.
ssu status
Device registration status: not registered
Device model: Jolla (SbJ / JP-1301)
Device UID: 359745050077921
Release: 3.0.0.8
Domain: sales
ssu lr
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-android-common/armv7hl/
- adaptation1 ... https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-qualcomm-sbj/armv7hl/
- aliendalvik ... https://store-repository.jolla.com/releases/3.0.0.8/aliendalvik/SbJ/
- apps ... https://releases.jolla.com/jolla-apps/3.0.0.8/armv7hl/
- customer-jolla ... https://store-repository.jolla.com/features/3.0.0.8/customers/jolla/armv7hl/
- eas ... https://store-repository.jolla.com/features/3.0.0.8/eas/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/3.0.0.8/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/3.0.0.8/jolla/armv7hl/
- xt9 ... https://store-repository.jolla.com/features/3.0.0.8/xt9/armv7hl/
Enabled repositories (user):
- store ... https://store-repository.jolla.com/SbJ/armv7hl/?version=3.0.0.8
Disabled repositories (global, might be overridden by user config):
Disabled repositories (user):
- home ... https://download.jollamobile.com/home:/honeybadger/latest_armv7hl/
The error code im getting is that pkcon refresh returns
Fatal error: File '/repodata/repomd.xml' not found on medium 'https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-android-common/armv7hl/?credentials=store'
Getting same error while doing the version --dup.
I am currently stuck in version 2.2.0.29.
Comments
You have two adaptation repositories while Jolla1 has only one. And they are incorrect.
devel-su
ssu rr adaptation0
ssu rr adaptation1
ssu ar adaptation0 https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-qualcomm-sbj/armv7hl/
ssu up
version --dup
reboot
If you get 3.0.0.8, the next stop release is 3.2.0.12. After that, you can request 3.3.0.16.
jovirkku ( 2020-04-28 16:54:49 +0300 )editssu up gives me
[root@Sailfish nemo]# ssu up
Device is not registered, can't update credentials
I guess ssu rr wont be updated to the list without that ssu up command?
ssu register gives me
[root@Sailfish nemo]# ssu register
Username: izba
Password:
Last operation failed:
Host requires authentication
Edit: Also run ssu ur, but that didn't change ssu lr output either. It is still trying to fetch the repodata from adaptation-android-common
Izba ( 2020-04-28 17:00:48 +0300 )edit=> I am currently stuck in version 2.2.0.29.
Lucky you. Mouhijoki is the best release so far.
objectifnul ( 2020-04-28 17:14:49 +0300 )edit@jovirkku Yeah when i disabled the adaptation0 and left only the adaptation1 it went to bootloop. Now i have reseted it back to factory state so i am again at 1.0.0.5. Still even at this state if i take a look of ssu lr it gives me the same
[root@localhost nemo]# ssu lr
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/1.0.0.5/jolla-hw/adaptation-android-common/armv7hl/
- adaptation1 ... https://store-repository.jolla.com/releases/1.0.0.5/jolla-hw/adaptation-qualcomm-sbj/armv7hl/
- aliendalvik ... https://store-repository.jolla.com/releases/1.0.0.5/aliendalvik/SbJ/
- apps ... https://releases.jolla.com/jolla-apps/latest-release/armv7hl/
- eas ... https://store-repository.jolla.com/features/latest-release/eas/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/1.0.0.5/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/1.0.0.5/jolla/armv7hl/
Enabled repositories (user):
- adaptation0 ... https://store-repository.jolla.com/releases/1.0.0.5/jolla-hw/adaptation-android-common/armv7hl/
- store ... https://store-repository.jolla.com/SbJ/armv7hl/
Disabled repositories (global, might be overridden by user config):
Disabled repositories (user):
- home ... https://download.jollamobile.com/home:/honeybadger/latest_armv7hl/
i tried to use that ssu rr and ar and after that do a pkcon refresh but that didn't help. Are those lines in some file that i could just manually go edit as a root?
EDIT: Well got it working this time from the update UI. Thanks for the help.
Izba ( 2020-04-29 16:18:06 +0300 )editStats
Asked: 2018-10-31 18:40:55 +0300
Seen: 9,233 times
Last updated: Apr 28 '20
did you try from the command-line ?
DrYak ( 2018-10-31 18:47:22 +0300 )editHere is snippet from my upgrade.log
teve ( 2018-10-31 18:56:12 +0300 )editNot able to do that, it is hanging, in the update screen
elkiaer ( 2018-10-31 19:05:52 +0300 )editFor me it also hangs in the update screen, holding the unlock button with the volume+ button is the only way to reboot the device. (The "Reboot" button on the screen is not responsive)
Keeper-of-the-Keys ( 2018-10-31 19:36:41 +0300 )editSame here on a Jolla1
Fellfrosch ( 2018-10-31 20:13:54 +0300 )edit