Gigaset GS290 can't update to v0.16

Hello,

I can’t update to /e/OS 0.16 version on my GS290.
In “Settings → System Updates”, I can see the follwing information:

If I click on install, new window emerges with the text: “You are about to upgrade to /e/OS 0.15 - Apr 22.2021.”

Question: Why it refers to 0.15 and not 0.16?

If I click on “OK”:
Preliminary update preparation
Android system update
Phone reboots

And then,
Finding update package…
Opening update package…
Verify update package …
E: failed to verify whole-file signature
Update package verification took 6.2 s (result 1).
E: Signature verification failed
E: error::21
Installation aborted.

Note: I flashed the most recent recovery file available (I read in the forums that is the current workaround, but still no success).

Any help will be appreciated.
Thanks!

2 Likes

Hi,
similar issue here. Just one release step later (0.16 to the new 0.17).

I got currently 0.16 installed on the device (according to GS290 /e/ Systemupdates Menu).
On offer for install (and already downloaded) is 0.17.
When I choose to install, I end up eventually on a recovery screen, where I can choose to

  • Reboot
  • Apply Update
  • Factory Reset
  • Advanced

with a terminal output below that says:
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signatue
Update package verification took 6.2 s (rersult 1)
E: Signature verification failed
E: error 21
Installation aborted
Install completed with status 1.
Installation aborted.

I guess choosing Apply Update would bring me to the same point again,
but I didn’t dare to and choose Reboot instead.

Any advise for this one?

Thanks,
Marcel

Hi @devl

I created a ticket in the gitlab issue tracker for this problem. You may just add a comment to the ticket that you’ve got the same problem to increase the probability that is topic is getting any attention at all. The gitlab repository needs another account, but it is quickly set up.

Here is the ticket:

Cheers, Marcel

1 Like

There is a lot of follow up discussion going on, here:

Hi @marcel.f,
Thank you for all your responses, I will look the discussion you mentioned.

EDIT:
As refering to your 1st post:
I guess choosing Apply Update would bring me to the same point again,
Yes, I tried that too, can confirm it does not solve the problem.

Regards,
devl

1 Like

Hi @marcel,
I set up an account and I will follow up the gitlab ticket.

Thanks!

1 Like