The scatter will come in v2.5 which is on A12 or /e/OS S for the GS290. It will not be available on older builds.
I’ve read in other threads, that people have bricked their phones as they used firmwares of higher Android versions as they had previously installed. Have I got this correctly and if so, will the A12 firmware help me if my phone runned A10 versions so far?
Sorry for the obvious question I am not that experienced in all this flshing stuff.
The updated version will replace previous one.
Ok, so I will wait till I hear something about the 2.4 version and use it with the flash tool on my A10 phone.
I have some bad news. The scatter file would be coming in v2.5. The v2.4 builds have already been initiated and it is too late to incorporate the file as well as the correct firmware into the build as the SP Flash tool requires all the files to be flashed at the same time.
| Device | Market launch | Made in Germany | System launch | Upgrade system version | Upgrade performed | Releases | Update-Support end |
|---|---|---|---|---|---|---|---|
| GX290 | 2019 | No | Android™ 9 | Android™ 10 | Jul. 2020 | Link | Feb. 2023 |
.
-
i am quite sure it is possible to first restore the device to the “20211202” android 10 based firmware, linked here Reverting to stock ROM on the GS290 for Windows users using SP Flash Tool,
Caution : Go to “download” tab (NEVER use “format”) -
then update to the latest stock version “20230214” linked here Downloads | Gigaset or here Service-Portal | Gigaset using recovery or system updater,
-
then finaly upgrade to “e-2.3-s-20240816” following Install /e/OS on a Gigaset GS290 - “GS290” using fastboot
here is the IMG-e-2.3-s-20240816426374-stable-GS290.zip content :
Including the preloader in the flash tool? In the last guide it was adviced to uncheck it.
1 Like
Step 1 worked. The phone is responding and has the regular Android running. (with preloader checked)
Is this:
https://doc.e.foundation/devices/GS290/install
The right documentation for the second step?
No.
update to the latest stock firmware version “20230214”
- using stock system updater, go to → settings → system updater
or
- using stock recovery, reboot to recovery mode, then Apply update
I am a bit stuck again. I am on the recent Android (step 2 complete) and try step 3 (eOS install).
Sadly the fastboot commands dont work. adb devices and starting fastboot mode works but after typing in fastboot commands it says “waiting for any devices”. After some searching I’ve found 2 suggestions:
- starting cmd in admin mode (didnt work)
- the usb driver is not working correctly.
I’ve installed the USB driver like in the guide here
So, here: Gigaset GS290 USB Drivers (DOWNLOAD) - Android USB Drivers
afte rinstalling I get the message in the picture. (it says its installed but may not work)
Any hints?
i don’t know windows for about 20 years
i read @aibd talking about open the device manager, looking for a disfonctional icon, and launch windows update
your image show a driver for ABD
there are 4 drivers availables on this page Gigaset GS290 USB Drivers (DOWNLOAD) - Android USB Drivers
i think you took the first one (for ADB) and need the second (for Fastboot) or the fourth
as shown here MediaTek Preloader USB VCOM Drivers for MT65xx, MT67xx, and MT68xx Chipsets
I’ve installed all 4 of them. The screenshot isnt from installing the 1st one but from the 3rd.
what is the output when typing
fastboot --version
what is the output when typing
fastboot devices
C:\platform-tools>fastboot --version
fastboot version 35.0.2-12147458
Installed as C:\platform-tools\fastboot.exe
C:\platform-tools>fastboot devices
C:\platform-tools>
But adb devices works.
adb works only when the device is in normal mode or in recovery mode
fastboot should works when the device is in fastboot mode…
have you checked in windows device manager (when the phone is plugged and in fastboot mode) ?
have you tried another cable, another USB port ?
also in /e/ documentation, it is written :
Tip: In case of issues with the latest fastboot version, try using version 30.0.5
often buggy, but easy-installer sometimes works…
Possibly to many drivers?
Both.
I’ve noticed but wasnt able to find a source of less recent versions.
one is needed for MTP file transfert in normal mode, another for adb protocol, another again for fastboot protocol
switch between differents mode to see some changes in the “Windows Geräte-Manager” …
have you tried to run windows update when the device is plugged in fastboot mode ?
here it is :
https://dl.google.com/android/repository/platform-tools_r30.0.5-windows.zip
Your up to date it sais.
Thank you. I will try it tomorrow and after that the easy installer.
1 Like