Gigaset GX290 Plus

Dear all,

as decribed GIGAGSET GX290 (Rugged phoned) - #20 by schoeller /e/ v0.17.1-q ROM was build and successfully installed on Gigaset GX290 Plus. IMG-files may be published for other to try. Please advise whereto.

Best

Sebastian

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

1 Like

As recommended images have been stored as per URL

1# Boot.img
2# Recovery.img
3# System.img

For testing purposes please follow installation instructions as per GS290. Be aware of no warranty for bricking your device. Best of luck

2 Likes

Kindly be aware that I had to use fastboot 30.0.5 as mentioned under [SOLVED] Fastboot flash Boot shows uncaught exception of type std::out_of_range: basic_string - #11 by Nils. Using higher version would lead to wrong flashing and a bootloop to fastboot.

1 Like

Hi, Iā€™m thinking about flashing e on a volla-x aka GX290+. What is your experience with e on GX290+?
Does everything run smoothly?
Is microG included?
Will there be updates possible in future?
Regards

Does NOT work. Installation works, but boots always into fastboot mode. What to do?

C:\fastboot>fastboot flash --disable-verity --disable-verification boot boot.img
Rewriting vbmeta struct at offset: 9957376
Sending 'boot' (32768 KB)                          OKAY [  0.785s]
Writing 'boot'                                     OKAY [  0.469s]
Finished. Total time: 1.540s

C:\fastboot>fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB)                      OKAY [  0.801s]
Writing 'recovery'                                 OKAY [  0.454s]
Finished. Total time: 1.271s

C:\fastboot>fastboot flash system system.img
Sending sparse 'system' 1/16 (130136 KB)           OKAY [  3.219s]
Writing 'system'                                   OKAY [  1.819s]
Sending sparse 'system' 2/16 (128164 KB)           OKAY [  3.135s]
Writing 'system'                                   OKAY [  1.802s]
Sending sparse 'system' 3/16 (129060 KB)           OKAY [  3.235s]
Writing 'system'                                   OKAY [  1.817s]
Sending sparse 'system' 4/16 (128164 KB)           OKAY [  3.241s]
Writing 'system'                                   OKAY [  1.786s]
Sending sparse 'system' 5/16 (129060 KB)           OKAY [  3.220s]
Writing 'system'                                   OKAY [  1.803s]
Sending sparse 'system' 6/16 (128164 KB)           OKAY [  3.204s]
Writing 'system'                                   OKAY [  1.789s]
Sending sparse 'system' 7/16 (129060 KB)           OKAY [  3.136s]
Writing 'system'                                   OKAY [  1.802s]
Sending sparse 'system' 8/16 (128164 KB)           OKAY [  3.170s]
Writing 'system'                                   OKAY [  1.786s]
Sending sparse 'system' 9/16 (129060 KB)           OKAY [  3.179s]
Writing 'system'                                   OKAY [  1.783s]
Sending sparse 'system' 10/16 (128164 KB)          OKAY [  3.127s]
Writing 'system'                                   OKAY [  1.802s]
Sending sparse 'system' 11/16 (129052 KB)          OKAY [  3.187s]
Writing 'system'                                   OKAY [  1.803s]
Sending sparse 'system' 12/16 (129052 KB)          OKAY [  3.169s]
Writing 'system'                                   OKAY [  1.787s]
Sending sparse 'system' 13/16 (129052 KB)          OKAY [  3.088s]
Writing 'system'                                   OKAY [  1.787s]
Sending sparse 'system' 14/16 (129052 KB)          OKAY [  3.042s]
Writing 'system'                                   OKAY [  1.820s]
Sending sparse 'system' 15/16 (129052 KB)          OKAY [  3.118s]
Writing 'system'                                   OKAY [  1.801s]
Sending sparse 'system' 16/16 (95280 KB)           OKAY [  2.389s]
Writing 'system'                                   OKAY [  1.350s]
Finished. Total time: 78.319s

C:\fastboot>fastboot -w
Erasing 'userdata'                                 OKAY [  0.069s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 13899515 4k blocks and 3481600 inodes
Filesystem UUID: 1ee9ed80-5929-11ec-9dda-db5d0824c78a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (316 KB)                        OKAY [  0.016s]
Writing 'userdata'                                 OKAY [  0.084s]
Erasing 'cache'                                    OKAY [  0.000s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 110592 4k blocks and 110592 inodes
Filesystem UUID: 1f157482-5929-11ec-a0cd-cd60f1f498ab
Superblock backups stored on blocks:
        32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'cache' (68 KB)                            OKAY [  0.000s]
Writing 'cache'                                    OKAY [  0.031s]
Erasing 'metadata'                                 OKAY [  0.016s]
Erase successful, but not automatically formatting.
File system type raw data not supported.
Finished. Total time: 0.517s

C:\fastboot>

Have you been using the adb version as mentioned? Otherwise there is also a stock ROM procedure to move back to default.

Android Debug Bridge version 1.0.41 Version 30.0.5-6877874
Found no stock rom for gx290plus, only for gs290?

Is the lineage OS working?

So this is your error. Did you search it?

Erase successful, but not automatically formatting.
File system type raw data not supported.

It is complex, and maybe you need to sleep on it!

I read several posts ā€¦ I do not know your device!

Please keep searching, but does this fit? https://www.droidwin.com/fix-erase-successful-but-not-automatically-formatting-cant-determine-partition-type/

What I tried without success:
USB 2 port, new cable.
Partition scheme should be correct A-only, cause Magisk showed it on Stock ROM.
I can boot into /e/ recovery and format cache and data from there without error.
I can do ā€œfastboot format:ext4 systemā€ without problems.
Tried newest adb 31.0.3, same error. An old adb version, another error:

fastboot -w
wiping userdataā€¦
CreateProcess failed: Das System kann die angegebene Datei nicht finden. (2)
error: Cannot generate image for userdata

There are scatter files for GX290 (plus?): https://github.com/dpeckett/opengs
But SP flashtool needs an authentification file?
Here seems to be sourcecode: https://www.gigaset.com/es_es/cms/lp/open-source.html
Stock ROM firmware seems to be only available for GS290:
(New users can only post 2 links???)

Would it be possible to make a ROM dump from a running /e/ with SP flashtool? And then flash it with SP?
I think I have to send it to Gigaset for a resetā€¦
Anyway thanks for your help

I think that is correct, the bar will lift soon, particularly if your read and jump some hoops!, in the meantime try code block to include a link :slightly_smiling_face:

https://service.gigaset.com/en/support/tickets/new

Maybe ask Gigaset for a ROM first!? I doubt they will oblige, but they should know their customers want one; unless anyone knows a better source.

ROM dump from a running /e/

I have no experience of https://forum.hovatek.com/thread-526.html

I asked Gigaset, they donā€™t give the ROM but they flash it for 25ā‚¬, thatā€™s ok.
SP flashtool is not so open like in this description anymore. You cannot backup the whole memory easily, because anybody could copy it. You can backup parts but you need this authentification file. So manufacturers can secure their software by copy protect part of flash memory. I will write Gigaset again, perhaps I find an interested technician.

1 Like

I once flashed the GX290 image and ended in a boot loop on my GX290+. The Mediatek tool chain and a initial image I could find in the wild.

I own a GX290 plus now for a while and it is the only real outdoor phone I have seen so far. Not to compare with any Samsung or equivalent. IP86 is one thing, MIL STD 810 G is just another level. Alloy frame, power bank functionality, wireless charging - all there. I use it on my offroad motorcycle for all kind of purposes under ALL conditions.

If I just could get rid of the preinstalled OS and use the beloved e.foundation just like on my FP3+

If e.foundation would make an official image, I would support this by purchasing another e Backer worth 128ā‚¬. :grin:

BR
Uwe

Hi, where did you find the ā€œinitial imageā€ stock rom?

I searched the internet and eventually found oneā€¦
Canā€™t remember where, but the filename was MT6763__10__Gigaset_GX290_10.0_V11_20200813__QP1A.190711.020__GX290

found it again
https://github.com/GS290-dev/gigaset_gx290_dump

On github is only boot and recovery.img. I found something here but donā€™t know if itā€™s for GX290plus and if I can trust the link.

i am also for supporting rugged phones,
why not this one as it seems to be the esiest porting as possible because its brother is already supported.

As you can read in Gigaset GX290 Plus - #13 by Howie, there is some difference ā€¦ :wink:
So, /e/ could not be build on this device unless Gigaset release complete sources.
Itā€™s a quite new device, so I think we just have to be patient and wait for it !

Sorry, i was thinking about gs290<ā€“>gx290

2 Likes