"system corrupted" after trying to switch the boot slot

Gigaset GS6 from murena store
After trying to switch back to V 4 via fastboot (active slot), I get a message “device corrupted … press power to continue” when booting up the phone. If I confirm, it boots ub in the original slot with V 4.1.1
So far I have not bricked it … but is there a possibility to get rid of this message and its confirmation?

(I used to work with adb and fastboot as modem QM and R&D but not on phones)

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

The message didn’t disappear after this morning’s OTA update to SW 4.2
Maybe I can get a hint to remove that boot message? I can send logs from the phone if needed.

This sounds like the “Custom ROM” yellow warning. A gift from Android Boot verification described https://source.android.com/docs/security/features/verifiedboot/boot-flow.

These warnings are deeply built in but with some MediaTek devices it has been recorded as possible to remove it. I have no idea whether it might work on this new device but you might search online. Or for instance How to fix MTK orange, yellow & red state warnings.

First step (as you want a backup) might be to download the ROM and check whether the LK (or such) partition is found there or is it only on a manufacturer ROM said to be unpublished.

Edit. From your OP, @csi, do I gather that the yellow warning was not present as delivered?

This might imply that the Murena ROM had already been “adjusted” to eliminate the warning, but the adjustment is not included in the ROM as downloaded. Idk

1 Like

The text is white and in microscopic size. I need a magnifier glass + my reading glasses to read.
"dm-verity corruption

… device may be corrupted …
confirm with power or restart will occur in 5 seconds"

Not much time to read and react to this.
It is still a kind of command line, while the “murena” logo is shown.

It is present since I tried - after the v4.1.1 installation - to switch the boot partition back to the previous version.

(I knew this kind of switching from my previous job in modem QM but did not note that in that case both partitions did contain the same SW version as a backup. So it was definetly my fault)

So yours is bootloader locked? A locked bootloader would complain at intrusion.

dm-verity corruption

Simplest is just Factory reset (no guarantee it would work) but you will see various other approaches with an online search.

This may give you insights

https://xdaforums.com/t/guide-how-to-remove-dm-verity-corruption-dialogue-2-methods.4604297 but expects unlocked bootloader.

1 Like

@aibd Great … I love it … a forum full of experts!
fastboot oem cdms was the solution.
I never locked or unlocked anything but the debugging options on the phone the confirmation of the debugging channel.
Thank you!

2 Likes

Ha, ha… how true! :grin: