Can't update to 2.1.1 [answered]

Question

2

Can't update to 2.1.1 [answered]

asked 2017-07-27 05:48:41 +0200

soheilbalini
118 ●2 ●6 ●13

updated 2017-08-30 15:34:00 +0200

c.la

4963 ●108 ●137 ●137

Hi guys. that's what I did in last 48 hours on my Jolla C:

updating the device from latest os to 2.1.1.23 via update manager = boot loop
reseting device with usb connection
installing update via update manager = stuck + very slow connection
installing update via terminal from 2.0.2.43 to 2.1.1.23 = full update = boot loop
resetting device with USB connection
installing update via terminal = device only updates two packages and then says: this process will break your device
lot's of investigation and still no luck

now I'm stuck with an old OS & an update manager that has the "problem with store" and a terminal update process that eider fails or make the device enters boot loop. Any Idea?! :/ :/ :/

++ I can't believe or tutorial app has no skip button after all these years!

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by c.la
close date 2017-08-30 15:33:44.944229

Comments

Having similar problems with my Jolla tablet (cant update right now, try again later/critical problem with registry). Have now given up - and left the message to constantly remind me that there is a new software update available

Ryan ( 2017-07-27 10:31:43 +0200 )edit

Having similar problems with my Jolla tablet (cant update right now, try again later/critical problem with registry). Have now given up - and left the message to constantly remind me that there is a new software update available
Ryan ( 2017-07-27 10:31:43 +0200 )edit

Accepted Answer

7

answered 2017-07-27 13:39:28 +0200

jovirkku

23703 ●213 ●311 ●247

moderator

We have found an issue in the OS update repositories such that installing updates from 2.0.5 (or earlier) to 2.1.1.23 tend to fail. This is being fixed in the update servers. Updates 2.1.0.11 => 2.1.1.23 should work ok. Note that 2.1.1 is a big update due to some vulnerability fixes in the libraries. Because of this the download phase can take tens of minutes. Apologies for the inconvenience caused.
-There will be another release candidate 2.1.1.24 for early access subscribers one of these days.

edit flag offensive delete publish link

Comments

1

tnx for the clarification. leaving early access to get the old updates did the trick for me. nice to know that its being noticed.

soheilbalini ( 2017-07-27 14:20:27 +0200 )edit

Hi @jovirkku I reopened the question as on my JP01 I did a factory reset and now I'm upgrading to the latest SFOS release. I'm now at Saimaa, 2.0.0.10 and the sailfish update wants me to update to 2.1.1.26 whereas from your answer I'd expect to go to 2.0.5 first and then update to 2.1.1.26 but this isn't happening.

Can you please check?

c.la ( 2017-08-29 23:02:58 +0200 )edit

@c.la: 2.0.0.10 is the latest so-called stop release. Therefore the update path should be from 2.0.0 directly to 2.1.1. However, we have noticed that an update of JollaC from 2.0.0 may not work to 2.1.1 directly but could require installing 2.0.5 as an intermediate step. Forcing a device to 2.0.5 requires using the command line for the update. JP01 should update from 2.0.0 to 2.1.1.

jovirkku ( 2017-08-30 11:48:30 +0200 )edit

@jovirkku Thank you for the explanation, I'll probably manually update to 2.0.4 first as my last backup was taken at that version.

Or is it safe to restore a 2.0.4 backup from SFOS v. 2.1.1?

c.la ( 2017-08-30 12:25:53 +0200 )edit

@c.la: There were no major architectural changes to backup/restore in 2.0.5, 2.1.0 and 2.1.1, only some bug fixes improving robustness. From this respect we can expect that restoring a backup to 2.1.1 made with 2.0.4 should work. However, if you have the time and want to play safe then why not visit 2.0.4 and restore there.

jovirkku ( 2017-08-30 12:44:00 +0200 )edit

Answer 2

6

answered 2017-07-27 07:25:37 +0200

monkeyisland

1181 ●32 ●41 ●43

Skip tutorial touch the corners
Left top Right top Left Bottom Right Bottom

:)

edit flag offensive delete publish link

Comments

wow this is useful!

magullo ( 2017-07-27 07:32:21 +0200 )edit

3

It's more like a Fatality command of Mortal Combat but ok! :D tnx

soheilbalini ( 2017-07-27 07:42:49 +0200 )edit

Just wow. Thats really good to know. Maybe they should tell that at the beginning of the tutorial.

BlaeX ( 2017-07-27 12:09:09 +0200 )edit

Answer 3

4

answered 2017-07-27 08:21:24 +0200

eson

4617 ●89 ●127 ●141

https://svenskasprakfiler...

updated 2017-07-27 08:43:52 +0200

I had the exact same situation and it's because we are on early access program. The official solution is to first opt out of EA program and then fix your device with the help of Recovery Mode. The problem is that it will take days to opt out of EA program, so I made my own "opt out" solution. A little cumbersome but it works, and this is how...

First upgrade from 2.0.2.43 to SFOS 2.0.2.51

ssu re 2.0.2.51
version --dup

Then repeat version --dup to SFOS 2.0.4.14.

When you're on 2.0.4.14, you should be able to get a normal update to 2.1.0.11 and finally 2.1.1.23.

There might be an easyer solution that I didn't think of, but at least this worked for me.

edit flag offensive delete publish link

Comments

If the problem is EA then we should be able to update with a new user (of course after a hard reset)! interesting!

soheilbalini ( 2017-07-27 09:28:35 +0200 )edit

I guess changing user without even doing the hard reset did the job! I'm now seeing Ijoki as the first update. you helped A LOT.

soheilbalini ( 2017-07-27 09:33:16 +0200 )edit

Great! Good to know, if it happens again.

eson ( 2017-07-27 09:40:08 +0200 )edit

Answer 4

0

answered 2017-07-27 07:01:53 +0200

Rafaelvlmendes
25 ●2 ●3 ●9

updated 2017-07-27 07:04:24 +0200

Hi. Try forced update for terminal..

1) Factory reset
2) Open developed mode
3) write that command:

devel-su
ssu re 2.1.1.23
version --dup

So finish update write reboot
Try and say ews.. Bye

edit flag offensive delete publish link

Comments

As I wrote in my comment I already done that!! (at least 5 times) but tnx anyway

soheilbalini ( 2017-07-27 07:14:17 +0200 )edit

The Resetting device have an option remove looping. Can U try?
Other option U can copy system download here: https://together.jolla.com/question/148893/how-to-make-aqua-fish-to-think-its-jolla-c-not-modem/
Do the 2nd part... PS: I know you user Jolla C but have a system download and you can copy to SD and restore to your device.
Bye

Rafaelvlmendes ( 2017-07-27 07:46:38 +0200 )edit

the problem is not looping. the problem is updating. I can remove the loop, pass the loop but new release is uninstallable for me. I think it's skipping some packages for some reason! I don't know why

soheilbalini ( 2017-07-27 08:04:21 +0200 )edit

Can't update to 2.1.1 [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by c.la
close date 2017-08-30 15:33:44.944229

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Can't update to 2.1.1 [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by c.la close date 2017-08-30 15:33:44.944229

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by c.la
close date 2017-08-30 15:33:44.944229