Ask / Submit
4

Jolla Phone bricked during upgrade to 2.1.1

asked 2017-08-31 11:38:43 +0200

Tapio Peltonen gravatar image

I tried to upgrade my Jolla last night to 2.1.1 (Jämsänjoki) and ended up with a bricked phone. Any ideas for what to try (I really would like to boot the phone without having to resort to factory reset).

The update process failed with some kind of "Could not upgrade at this time" error and prompted me to boot the phone. When booting, the phone shows the Jolla logo, then flashes a white led once, then goes totally dark and does not respond to anything. Nothing is written in logs during these failed boots.

Btrfs seems to be relatively healthy (viewed from recovery shell):

/ # btrfs fi show
ERROR: unable get label Inappropriate ioctl for device
Label: 'sailfish'  uuid: e7a52518-ccc6-494a-8843-b742e7781620
        Total devices 1 FS bytes used 6.51GiB
        devid    1 size 13.75GiB used 10.13GiB path /dev/mmcblk0p28

Btrfs v3.16

/ # btrfs fi df /mnt
Data, single: total=9.00GiB, used=6.40GiB
System, DUP: total=64.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, DUP: total=512.00MiB, used=115.64MiB

I tried chrooting to /mnt to look at journalctl. The log ends like this (looks like something went wrong during systemd upgrade):

Aug 31 00:33:22 Sailfish kernel: [BAT] 51( 51, 51.9, 47.8( 47.6)  0.0)v3744(3828)( 404, 377)t310,c   55333,   94(17360)r208,L3875,s10
Aug 31 00:33:22 Sailfish kernel: [BAT]## SOC= 51( 51, 51),3755(3744),A=0345,T=310,On=0,0,(0),Unknown 000(100),vd=4360(0,0),ib=1000,0,F03,R08,W10
Aug 31 00:33:26 Sailfish packagekitd[13632]: Install progress update: 404 of 667
Aug 31 00:33:26 Sailfish store-client[13738]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotPackage(PackageKit::Transaction::Info, const QString&, const QString&) 12 "systemd;225+git3.1-1.17.3;armv7hl;jolla" "A System and Service Manager"
Aug 31 00:33:26 Sailfish groupadd[15397]: group added to /etc/group: name=systemd-network, GID=990
Aug 31 00:33:27 Sailfish groupadd[15397]: group added to /etc/gshadow: name=systemd-network
Aug 31 00:33:27 Sailfish groupadd[15397]: new group: name=systemd-network, GID=990
Aug 31 00:33:27 Sailfish useradd[15402]: new user: name=systemd-network, UID=995, GID=990, home=/, shell=/sbin/nologin
Aug 31 00:33:28 Sailfish groupadd[15408]: group added to /etc/group: name=systemd-bus-proxy, GID=989
Aug 31 00:33:28 Sailfish groupadd[15408]: group added to /etc/gshadow: name=systemd-bus-proxy
Aug 31 00:33:28 Sailfish groupadd[15408]: new group: name=systemd-bus-proxy, GID=989
Aug 31 00:33:28 Sailfish useradd[15413]: new user: name=systemd-bus-proxy, UID=994, GID=989, home=/, shell=/sbin/nologin
Aug 31 00:33:28 Sailfish systemd[1]: Stopping udev Control Socket.
Aug 31 00:33:28 Sailfish systemd[1]: Closed udev Control Socket.
Aug 31 00:33:28 Sailfish systemd[1]: Stopping udev Kernel Socket.
Aug 31 00:33:28 Sailfish systemd[1]: Closed udev Kernel Socket.
Aug 31 00:33:28 Sailfish systemd[1]: Stopping udev Kernel Device Manager...
Aug 31 00:33:29 Sailfish systemd[1]: Stopped udev Kernel Device Manager.
Aug 31 00:33:29 Sailfish dbus[473]: [system] Reloaded configuration
Aug 31 00:33:29 Sailfish dbus[473]: [system] Reloaded configuration
Aug 31 00:33:31 Sailfish dbus-daemon[952]: Reloaded configuration
Aug 31 00:33:31 Sailfish dbus[473]: [system] Reloaded configuration
Aug 31 00:33:31 Sailfish dbus-daemon[952]: Reloaded configuration
Aug 31 00:33:31 Sailfish dbus[473]: [system] Reloaded configuration
Aug 31 00:33:32 Sailfish systemd[1]: Reexecuting.
Aug 31 00:33:32 Sailfish systemd[1]: systemd 225 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Aug 31 00:33:32 Sailfish systemd[1]: Detected architecture arm.
Aug 31 00:33:32 Sailfish systemd[1]: usb-moded.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
Aug 31 00:33:32 Sailfish systemd[1]: Configuration file /lib/systemd/system/ohmd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 31 00:33:32 Sailfish systemd[1]: [/lib/systemd/system/connman.service:3] Failed to add dependency on oneshot-root, ignoring: Invalid argument
Aug 31 00:33:32 Sailfish systemd[1]: [/lib/systemd/system/connman.service:4] Failed to add dependency on oneshot-root, ignoring: Invalid argument
Aug 31 00:33:32 Sailfish systemd[1]: Configuration file /lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 31 00:33:32 Sailfish systemd[1]: sensorfwd.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring.
Aug 31 00:33:33 Sailfish systemd[1]: Listening on udev Control Socket.
Aug 31 00:33:33 Sailfish systemd[1]: Listening on udev Kernel Socket.
Aug 31 00:33:33 Sailfish systemd[1]: Starting udev Kernel Device Manager...
Aug 31 00:33:33 Sailfish systemd[1]: Started Keep FDO Desktop Entry files in sync with .apk files.
Aug 31 00:33:34 Sailfish systemd[1]: Started udev Kernel Device Manager.
Aug 31 00:33:34 Sailfish systemd[1]: systemd-logind.service: Watchdog timeout (limit 1min)!
Aug 31 00:33:34 Sailfish systemd[1]: systemd-logind.service: Main process exited, code=killed, status=6/ABRT
Aug 31 00:33:34 Sailfish kernel: systemd(1) send signal 6 to systemd-logind(747)
Aug 31 00:33:34 Sailfish systemd[1]: systemd-logind.service: Unit entered failed state.
Aug 31 00:33:34 Sailfish systemd[1]: systemd-logind.service: Failed with result 'signal'.
Aug 31 00:33:34 Sailfish systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Aug 31 00:33:34 Sailfish systemd[1]: Stopped Login Service.
Aug 31 00:33:34 Sailfish systemd[1]: Starting Login Service...
Aug 31 00:33:34 Sailfish systemd[1]: systemd-journald.service: Watchdog timeout (limit 1min)!

Any ideas on what is going on appreciated.

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted
4

answered 2017-08-31 13:26:09 +0200

Tapio Peltonen gravatar image

Oopsie. I think I found an explanation for this problem. No solution yet, it might be that I have to do a factory reset, but well... Should have read the release notes bit more carefully. From "Known issues":

If you have Call Recorder from Openrepos installed, uninstall it before the upgrade. Otherwise the upgrade will fail and most likely put the device in unbootable state.

edit flag offensive delete publish link more

Comments

1

In our 4 Jolla's (2 Jolla1's, 1 Jolla C and 1 converted AF/~JollaC) - they all had Call recorder installed - but only one wen't to unbootable state (Jolla1) - plus the Call Recorder notes have stated for about 2 years that ONLY earlier versions of CR cause problems when updating? (I've done all updates from summer 2015 onwards without removing the CR) ...so it maybe be debatable if CR is to blame?

ehakkarainen ( 2017-08-31 16:55:16 +0200 )edit

I second that - never had any issues with Call Recorder, only uninstalled it after upgrading to 2.1.1.23 and being left without connections (which resulted from TOHKBD attached as had been found later). What part of CR would be troubling if so?

Lutwolf ( 2017-08-31 19:25:13 +0200 )edit

Well, something caused systemd to be unable to upgrade.

I finally resorted to factory reset, and the phone is working again, and I have the tedious work of restoring all the data I would like to have from the btrfs image.

Tapio Peltonen ( 2017-09-01 11:26:00 +0200 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2017-08-31 11:38:43 +0200

Seen: 459 times

Last updated: Aug 31 '17