Hi everyone,
I’m stuck in a BROM boot loop on my Gigaset GS290 and I need help finding the official signed stock firmware.
What happened
I successfully installed Ubuntu Touch on my GS290 using the UBports Installer. Everything was working fine. I then attempted to install Sailfish OS using piggz’s flash script (yggdrasil-ci), which flashed hybris-boot.img, sailfish.img001, logo.bin and lk-yggdrasil.img via fastboot.
After rebooting, the screen stayed black. The phone is now stuck in a permanent BROM boot loop.
What I’ve already tried
Using mtkclient, I successfully communicated with the phone in BROM mode (MT6763 / Helio P23, unprotected) and reflashed the following partitions using the VollaOS bootstrap package:
- preloader_k63v2_64_bsp.bin → Boot1 and Boot2
- lk.img and lk2.img
- tee.img (tee1 and tee2)
- spmfw.img, sspm.img (sspm_1 and sspm_2)
- recovery.img → boot and recovery partitions
- seccfg partition erased
Despite all this, the phone remains in BROM mode. mtkclient always detects “BROM mode” instead of “Preloader mode”, which strongly suggests that the eMMC PARTITION_CONFIG register (EXT_CSD byte 179) was modified by the UBports Installer to boot from the User partition instead of Boot1.
I also tried SP Flash Tool v5.1924 under Windows with “Format All + Download” mode, but the available firmware packages I found online are missing the signed images (md1img-verified.img, tee-verified.img, etc.) and generate STATUS_SEC_INSUFFICIENT_BUFFER errors.
What I need
I’m looking for the official signed stock firmware for the Gigaset GS290 (Android 10, MT6763), ideally version Gigaset_GS290_10_V04_20200313 or later, containing all verified/signed partition images including:
- md1img-verified.img
- tee-verified.img
- spmfw-verified.img
- sspm-verified.img
- dtbo-verified.img
Alternatively, if anyone knows how to reset the eMMC PARTITION_CONFIG register using mtkclient or another Linux tool, that would also solve my problem.
The phone is NOT hard-bricked — mtkclient communicates perfectly with it every time in BROM mode. It just won’t boot because of this register issue.
Any help would be greatly appreciated!
Thanks