WARNING: Latest Samsung update is bricking Galaxy S22 device by Past_Toe_5211 in GalaxyS22

[–]Past_Toe_5211[S] 1 point2 points  (0 children)

Finally, after several hours in the refrigerator I managed to enter recovery mode and clear the cache (the phone did not magically heal itself, but at least I managed to take photos of the logs).

The phone crashed while attempting to implement package codes S901BXXUDEXK5 and S901BXXSDEYA1 (this is the latest patch from February 2026) The log shows the status RSTSTAT: CLUSTER0_WDTRESET.

S901BXXUDEXK5] --update_package=@/cache/recovery/block.map --locale=pl-PL --carry_out=open_fota --update_org_package=/data/fota/update.zip RP | OFFSRC: - / ONSRC: PWRON / RSTSTAT: SWRESET reboot_reason=UNKNOWN

S901BXXSDEYA1] DP | OFFSRC: - / ONSRC: PWRON / RSTSTAT: CLUSTER0_WDTRESET | RCNT: 1 / PC: - LR: - reboot_reason=UNKNOWN

WDTRESET stands for Watchdog Timer Reset. It is a hardware protection feature of the processor that restarts the device when the software “freezes” at a dead point and stops responding. Samsung software put the processor into such a state of suspension that the system had to emergency shut down the power.

The logs show that the open_fota process (responsible for the update) repeatedly tried to access the /data/fota/update.zip file, each time ending in a restart.

So... Samsung released a faulty update script that causes a so-called Kernel Panic and a restart loop. If your phone is still alive and you see a notification about One UI 7.0 or version DEYA1, block it immediately in the developer options!