After reset, and updating via commandline to 2.1.0.11, phone still wants to install 1.1.2.16

asked 2017-10-02 10:06:47 +0300

martin gravatar image

updated 2017-10-02 21:54:05 +0300

My original issue was with downgrading the device (see below). I solved it by resetting the device, but now I have a new issue.

After resetting the device and installing all the updates to 2.1.0.11 (see comments below), I am now stuck in a state, where some part of the phone thinks it is still on 1.1.1.x and wants to update to 1.1.2.16.

I am not sure, if it is related, but I cannot apply any patches with patchmanager. And without the volume-buttons-control-only-media patch the phone is unusable for me (Nothing terrifies me more than a phone that might not be in silent mode).

How can I fix this update problem or is the patch problem unrelated to the update problem?


Original issue:

So, I got fed up with the wifi problems in 2.1.1 and decided to downgrade the phone. However, I think I made a mistake.

So, here's what I did:

  • battery was around 49%, I was on mobile network, no wifi
  • unapply all patches from patchmanager
  • ssu release 2.1.0.11
  • version --dup
  • forget phone for a few hours

When I finally looked back at the phone, it seemed to be off, or at least the screen was black. Pushing the power button did not do anything. Pushing and holding the power button did not do anything. Connecting the charger to the phone did not do anything.

After removing the battery and putting it back in, the phone at least does something, when turning it on. The backlight of the display turns on, it vibrates once, but then it vibrates again and the backlight turns off again.

So I started the phone in recovery mode. I tried the btrfs recovery option, but that only took like a second and did not help. So, I opened the shell, mounted the filesystem, went into a chroot and shared my computers internet connection with the jolla.

version returns SailfishOS 2.1.0.11 (Iijoki) (armv7hl)

version --verify returns

  • geoclue-provider-hybris-0.2.11-10.26.2.jolla.armv7hl
  • geoclue-provider-hybris-0.2.12-10.28.2.jolla.armv7hl
  • hybris-libsensorfw-qt5-0.8.30-10.25.3.jolla.armv7hl
  • hybris-libsensorfw-qt5-0.9.0-10.26.1.jolla.armv7hl

One ore more packages are not at the expected version for SailfishOS 2.1.0.11 (Iijoki) (armv7hl) (+ = expected version, - = installed version)

Calling version --dup again, it just says REFRESHING CACHE AND DOWNLOADING PACKAGES but does not do anything.

I also tried zypper update, but it does not work, because apparently it needs to get the store credentials from dbus, which does not work in the chroot environment.

Is there any way I can save my Jolla, except for the factory reset?

edit retag flag offensive close delete

Comments

My experiences with my both J1 are:

  • the "version --dup" process reboots the phone at some point, when some system files have been replaced (don't remember which ones), so it's a must to do "version --dup" at least twice.
  • when you find the "REFRESHING CACHE blablah" stuck it's an indication something blocks the packet management (for example you call zypper or pkcon before). When I had this situation I rebooted the phone, maybe there's a simple command which I don't know.
  • I've made a downgrade too and was not able to reactivate the screen and input methods because of a failed DBus start. Needed to do a factory reset, upgraded then until 2.1.0.11, installed patchmanager 2 and some patches and had the same problem again. Something is different now,
  • So I did a second factory reset, used only patchmanager (without 2) and it works now.

So, if you can figure out how to fix your problem without factory reset, please give a summary here. I'm very interested in this topic.

Robomike ( 2017-10-02 11:20:44 +0300 )edit

I decided to do the factory reset. Now I have the problem, that I need to enable the developer mode to configure eduroam, to be able to sign into my jolla account. But I need a jolla account to enable developer mode. I already used the recovery mode to copy the connman profile to the phone. It does recognize the profile, and tries connecting to eduroam, but then it says Error with connection. And for some reason the mobile connection does not work either with this old version of Sailfish OS. Is it possible start doing the updates from the recovery mode?

martin ( 2017-10-02 15:06:42 +0300 )edit

I actually managed to get mobile connection working by switching to 3G only, so I could sign into my jolla account. I then could download the update to 1.1.2.16, but I could not install it. It would just go to a black screen immediately, and not do anything. After forcing it to reboot, I could update successfully to 1.1.2.16 via the terminal after enabling developer mode. Once on 1.1.2.16 I managed to get the wifi working. However, the automatic update function did not show the next update, so I tried again via the terminal (update to 1.1.7.28). After some time it rebooted, but it is only showing the background image of the lockscreen now. Otherwise it is not responsive. However, I can connect it to my computer via USB, then it asks me if I want to have developer mode or PC connection and I can choose developer mode. So, in theory I could connect to the phone via ssh over USB but I don't recall the automatically generated password. I guess, I could back to the recovery mode, to configure ssh to be able to connect again.

martin ( 2017-10-02 18:02:12 +0300 )edit

After configuring ssh from the recovery mode, I could continue the updating process to 1.1.7.28 via ssh, so the phone started working again. However, while version reported 1.1.7.28, the GUI update function in the settings, still wanted me to update to 1.1.2.16. I decided to ignore the GUI, and kept updating via the commandline all the way up to 2.1.0.11. Even now, the GUI still wants me to update to 1.1.2.16. This is not a problem now, but I assume it will be a problem once 2.1.3 becomes available. Does anyone know, how I can make the update GUI aware of the current version?

martin ( 2017-10-02 21:07:51 +0300 )edit

I've had this kind of notification for almost one year :( with no negative effect. GUI-updates of the whole system weren't possible anymore after upgrading once from command line. Not sure if this is disfunctional behaviour or what. I don't trust GUI updates anymore. I once read a note how to remove the false update notification but I don't remember where. Relevant seems the information in "settings | product information".

For the patch: don't think that's related. Tried to find the patch you mentioned above in warehouse but with no success, maybe it's obsolete? But there's a patch called "Volume control settings 0.6-1" by alina, which does the job (after reboot).

Robomike ( 2017-10-03 12:02:18 +0300 )edit