Hi there,
have a GS290 too, and follow the “documentation” to install /e/ on my phone … now it stuck on bootloader
"Orange State
Your device has been unlocked and can´t be trusted
Your device will boot in 5 seconds"
on/off and Volume up/down no reaction … in adb no Device is listed … how i can fix it ? or i bricked that funny thin now ?
greetings
Smorbsom
Same problem. I can boot to fastboot mode only. But I don’t know what to do next.
> fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x80000
(bootloader) hw-revision: ca01
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 3843mV
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: d416fbe00
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:vendor: 32000000
(bootloader) partition-type:vendor: raw data
(bootloader) partition-size:tee2: c00000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:dtbo: 800000
(bootloader) partition-type:dtbo: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 100000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:gz2: 1000000
(bootloader) partition-type:gz2: raw data
(bootloader) partition-size:gz1: 1000000
(bootloader) partition-type:gz1: raw data
(bootloader) partition-size:sspm_2: 100000
(bootloader) partition-type:sspm_2: raw data
(bootloader) partition-size:sspm_1: 100000
(bootloader) partition-type:sspm_1: raw data
(bootloader) partition-size:spmfw: 100000
(bootloader) partition-type:spmfw: raw data
(bootloader) partition-size:md1dsp: 1000000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 4000000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: e78000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: 800000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 2000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: GS2900000009055
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: k63v2_64_bsp
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR12A.R2.MP.V91.7.P6
(bootloader) version-bootloader: k63v2_64_bsp-1ef71aa-20191025134709-201
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.338sOk, installation instructions from the documentation works fine after the flashing “gs290_10.zip” firmware using SP Flash Tool. It was really hard work. But it’s all good now.
Looks like this problem comes from latest official OTA updates. Please update the docs!
Pl can you share what steps need to be updated in the documentation.
@Manoj There should be added a section 2.1. OEM Unlock, unless it’s a better choice to add it to https://doc.e.foundation/pages/enable-usb-debugging. Although the OEM Unlock is different for some devices (i.e. FP3 where you need a code).
This has been brought up here: GS290 not supported in easy-installer?
We can add the extra step to unlock oem in the https://doc.e.foundation/pages/enable-usb-debugging document as that is where the user sees the option.
Hi , I cannot find how to manually boot in fastboot mode ? this should be in the Doc.
If you meant how to reboot into fastboot mode it is available in the documentation Step 3 in the Before flashing
adb reboot bootloader
Thx , i read that but the guy I’m trying to help on fr telegram channel is stuck in bootloop , he needs key combination
Hi everyone,
I saw your discussions with interest.
I need some help : I can’t install e/OS on a my new (last Android 10 built) GS 290. Neither with “manual” way, neither with “Easy installer”… I have exactely followed all the steps and recommandations.
Actually I am locked at the step fastboot (I can read on my smartphone screen “fastboot mode”).
Has someone had the same issue ?
Many thanks in advance.
I’m very keen on e / OS on tablet, and would like to go on such an experience on smartphone …
Hey Jimmy, have a look at this earlier reply
Many thanks !
I’ve understood that it was a driver issue.
I fixed it with installing the Windows driver for Mediatek chipset, here : https://www.thecustomdroid.com/mediatek-preloader-usb-vcom-drivers/
And e/0S has been installed !
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:
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.
How to reach the bootloader
Volume up + Power (from phone powered off)
is still missing from https://doc.e.foundation/devices/GS290/.
Could there be an emergency case like how to restore and reflash system update with /e/ if your GS290 smartphone get bricked perhaps ?
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
@Manoj : could you please update the link to Recovery ?
I was mislead by this documentation when fixing someone else’s device 
Thanks ! 