Ask / Submit
1

Updating Jolla 1 to 2.2.0.29 fails [answered]

asked 2018-06-09 02:54:44 +0300

PatsJolla gravatar image

updated 2018-06-09 03:14:35 +0300

Hi folks, I seem to have several problems with my old Jolla1 Phone: Im still stuck in Ver. 2.1.2.3 and somehow cannot update anymore. I don't use the phone anymore but I keep it still as a backup and wanted it to be up to date.

When I try to search for updates I get the message that my account Info is not set so I try to set up an account using my Jolla-Account (I don't know why the account isn't active there anymore). But whenever I try to Login the App just closes and nothing is saved/logged in. Neither through Accounts page in settings nor through the store-client I have a chance to connect my account. Even creating a new one fails - again the app just closes.

If I try to update via terminal with version --dup I get the following error message:

ssu re 2.1.4.14
Changing release from 2.1.2.3 to 2.1.4.14
Your device is now in release mode!
[root@Sailfish nemo]# version --dup
/usr/bin/rnd-dist-upgrade: symbol lookup error: /usr/bin/rnd-dist-upgrade: undefined symbol: _ZN13SsuDeviceInfoC1E7QString

the same happens if I try to update directly to 2.2.0.29.

pkcon refresh stops at 98/99% with:

Message: connection-refused: adaptation0: Store credentials not received. Did not receive a reply.

I couldn't find any info on this error message. Is it related to the account problem? I seem also to have lost the developer tools in the settings page but accessing the phone via ssh is still working... I would not like to reset the device completely - I first want to fix the problems step by step if possible...at least I learn something by than ;-)

Any suggestions?

little update: developer tools are back. using pkcon install I managed to reinstall them

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by PatsJolla
close date 2018-06-10 10:42:31.708716

Comments

Whilst you have SSH access would be inclined to backup as much data as you can, as don't see reset being avoidable unfortunately. On the two previous occasions this error posted upon forum that has been the conclusion.

aspergerguy ( 2018-06-09 18:15:51 +0300 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2018-06-10 10:42:02 +0300

PatsJolla gravatar image

updated 2018-06-10 10:43:28 +0300

Looks like @aspergerguy was right, after trying different approaches and searching in internet I came to the conclusion that its easier to start from zero...

so for others who might come to such an error message:

  1. Make a backup
  2. do a factory reset and
  3. start updating from Sailfish stone-age ;-)
edit flag offensive delete publish link more

Question tools

Follow
2 followers

Stats

Asked: 2018-06-09 02:54:44 +0300

Seen: 483 times

Last updated: Jun 10