Gigaset - GS290 - gs290 - Documentation Suggestions

eOSWiki Documentation Suggestions
24

Hi, while the existing instructions for installing /e/ are really well written and easy to follow, it would be very helpful if the install page could also provide instructions for upgrading to a new e/os version.

The instructions on the install page currently do only cover the installation of the “dev” version on devices which did not come with e/os preinstalled. Trying to install the “stable” OTA upgrade afterwards (which will eventually be offered and downloaded by the device itself in Settings -> System Updates) will fail with a signature error after the necessary reboot to recovery.

I’d suggest this additional documentation regarding the upgrade process should cover at least the following - based on the current installation instructions:

  • step-by-step instructions which *.img files need to be downloaded and flashed for a “dev” upgrade (and, in contrast to a first time install, which do not), and how
  • if there is a risk of data loss by this kind of manual upgrade, i.e. will the device be reset to factory settings afterwards, or will user data and settings be preserved after the upgrade
    • if there is risk of data loss, short instructions or link to information how to backup and restore user data before upgrading, especially with regards to users who do not run an account with the /e/-cloud
  • comprehensive instructions how to migrate from dev to stable on the same version (before upgrade) without loss of user data, in order to be able to install future upgrades OTA
3 Likes
25

Found a working way to upgrade from 0.13-dev to 0.15-stable - please add to future update/troubleshooting section:

Upgrade: to upgrade from 0.13-dev (manual install as per official instructions) to 0.15-stable (OTA from within the phone) without losing your personal data or getting stuck at the signature verification after reboot, first flash the latest recovery.img for the GS290 as described in the workaround here:

https://gitlab.e.foundation/e/backlog/-/issues/2462#note_77242

Afterwards, the upgrade to 0.15-stable works OTA directly from the Systemupdates section of the phone’s settings, i.e. without the need for rebooting/flashing the system image manually.

1 Like
26

How to reach the bootloader

Volume up + Power (from phone powered off)

is still missing from https://doc.e.foundation/devices/GS290/.

1 Like
27

Could there be an emergency case like how to restore and reflash system update with /e/ if your GS290 smartphone get bricked perhaps ?

28

There are instruction here to restore the stock but it was tested on openSuse Linux

1 Like
30

The installation instructions at Install /e/ on a Gigaset GS290 - “GS290” seem to be outdated.

The ‘recovery.img’ image link should always point to the latest stable image. (Which is at the time of writing this https://images.ecloud.global/stable/GS290/recovery-e-0.18-q-20210827132306-stable-GS290.img). The OTA later on could fail otherwise (Please refer to here if you want to read more about that issue.).

Kind regards
Chris

2 Likes
31

@Manoj : could you please update the link to Recovery ?
I was mislead by this documentation when fixing someone else’s device :frowning:
Thanks ! :pray:

1 Like
32

I am checking with the team on this and will update the documentation shortly

1 Like
33

I knew that a new page exists with instructions to flash the GS290 stock ROM but it took me a while to find.
https://doc.e.foundation/pages/revert_e_GS290_windows

34

It is listed at bottom of https://doc.e.foundation/devices/GS290 (“Would you like to roll-back to stock ROM ?”) :wink:

However, @Manoj , I think that both OS (Windows & Linux) should be listed on each page (main device page, and install instructions).
Also, URL for Windows MTK driver may be changed to https://mtkusballdriver.com/download/mtk-usb-v1-0-8.

1 Like
35

Actually both were listed on the page…somehow it got overwritten after some recent changes. I am waiting for the links to the /e/ recovery for dev and stable to be added and post that will modify the documentation.

2 Likes
36

Hello,

this is my first post in this forum. I don’t know what is the right place for this topic,
I want to install /e/OS on an Gigaset GS290, so I try it here.

On my Gigaset GS290 there is currently a non-Android OS running (SailfishOS).
I want to install /e/OS. So I tried it with this guide:
https://doc.e.foundation/pages/install_e_GS290_linux

When I open SP Flash Tool and set the Scatter File and click on “Download” nothing happens.
SP Flash Tool seems to have no internet connection, but I am not sure what exactly is the problem.
libpng12-0 is installed. I deleted modemmanager from my system.

The guide says to run the command “sudo adduser dialout”. The command “adduser” does not exist on my system. Are you sure that this is the right command? Maybe this is the step I am missing?

When I start SP Flash Tool from console, this is the output I get:

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/virtual/bdi/0:61

Maybe someone can help me?

37

Did you tip :

wrong

chmod +x flash_tool flash_tool.sh
sudo adduser <austrasier> dialout
newgrp – dialout


Or


right

>```
chmod +x flash_tool flash_tool.sh
sudo adduser austrasier dialout
newgrp – dialout
38

I typed

sudo adduser austrasier dialout

but the command adduser ist not installed on my system, so it does not work.

The command line says, that I shall look up with command-not-found (cnf) in which package adduser is, to install it. But when I run

cnf adduser

it just says “command not found”

39

Just a thought, could adduser be not in your $PATH? On Debian I see:

which adduser
/usr/sbin/adduser

which useradd
/usr/sbin/useradd

Does some combination of this provide the answer?

which adduser

$PATH

Can you run the command actually as Root? Is root login allowed? or

sudo su or sudo su -

Then, acting as root, run your command, and/or

# which adduser

40

When I type as a normal user:

which adduser

I get the following output:

which: no adduser in (/home/austrasier/bin:/usr/local/bin:/usr/bin:/bin)

and when I type

which useradd

I get the following output:

which: no useradd in (/home/austrasier/bin:/usr/local/bin:/usr/bin:/bin)

When I type su in command line and enter the password to become super user
and type

which adduser

I get the following output:

which: no adduser in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin)
41

So mine was a bit of an x y response! :slight_smile:
Edit, sorry I confused it by introducing adduser and useradd - and I did not read your response carefully enough! Having done a little research since my first post I see some clues to OpenSuse and sudo sometimes having reduced permissions.

So could managing users have changed between 15.2 and 15.3?
https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-yast-userman.html

42

I am not 100% sure, but as far as I remember, this also did not work with openSuse 15.2 for me.

43

have you tried :

chmod +x flash_tool flash_tool.sh
sudo useradd austrasier dialout
newgrp – dialout

1 Like
44

I have opensuse 15.2 here and I do have the useradd executable in the package shadow.

But nevertheless, what the failing command is supposed to do: add your user to the group dialout. That should be doable with

sudo usermod -a -G dialout austrasier
newgrp - dialout
1 Like