Hello tried to flash according to your instructions. Unfortunately it gets stuck in the start screen after reboot. What’s my mistake? Can I get back to Ubuntu from your rom?
1 Like
This is a section for suggestion to the documentation. For support on the Gigaset from other users pl create topics or reply to posts here
1 Like
Hi, I just installed /e/ on my new GS290 and I think you forgot to unlock the bootloader in “Developer Options” Even if you are in developer mode it will still be locked by default
3 Likes
Yes, I saw the same. I did this explicit unlock and the process went smooth.
1 Like
Dear Manoj,
I’ve installed /e/ on my mom’GS290 yesterday : it works !! 
…but it was a little bit tricky because of some missing points.
-
In addition of “enable-usb-debugging”, I had to enable the OEM unlocking option in the Developpers options. As @sugit and @keesson01 mentionned.
-
As a Linux based host for the flashing, I had to create a “plugdev” group and install the
android-sdk-platform-tools-commonpackage (as it is mentioned in the android doc). -
It might be unclear - if not explicitly written - that the use of fastboot command can’t be available (
fastboot devicesfor instance) before adb command is launched (adb reboot bootloader).
Hope it could help !
And… thanx a lot to you and all the /e/team for that superbe work !!! My Mom is happy again … 
A /e/ user happy
1 Like
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:
- 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