S22 bricked by One UI 6.1 update! It keeps boot looping and ocasionally move forward and crash shortly then boot looping again

[Members_2eKoj97]

I tried everything 

- wiped cache

- factory reset

- re-flashed with the same firmware

- turned off wifi-BT everything

no matter what sooner (1s) or later (1-3 hours) it starts the boot loop again

I won't pay $500+ on motherboard replacement what is:

- a blanket solution because they care less to acknowledge, identify and solve it promptly

- clearly caused by 6.1 update of One UI (S901BXXSDEXKA)

- now I feel Samsung is playing with our trust, it's basically a scam I won't let myself pay them for the mistake and yes I won't pay for them for another samsung phone what they can turn into a brick remotely and overnight!

THEY MUST DO A BARE MINIMUM AND AT LEAST COMMUNICATE THE ISSUE CLEARLY, BUT THEY DON'T!!!

See below how quickly (probably in panic) they were releasing in December, right before holidays, they tried to wash away their blunder they had done previously in December, but they only made bad to worse!
Obviously, it was intended to be a cover-up patch, but failed that too!
This phenomenon is widespread and not a coincidence!

https://www.sammobile.com/samsung/galaxy-s22/firmware/SM-S901B/EUX/#SM-S901B

[Members_2eKoj97]

Yes, ocasionally it stays alive for a while but only for a while
- it keept alive for a night long in idle just one opened app then in the morning crashed
- I flashed set power saving and thought it is resolved and managed to install every app and config them all everything looked fine then crashed after 3 hours of intense usage
- once I also just reseted and ran a 30min benchmark test which obviously intense and havn't crashed then it ended, cooled I did nothing special and suddenly crashed

but everytime it ended with a sudden crash and entered in a boot loop...

So I am able to get it alive by flashing it then couple of hours max and boot loop but that's unreliable and useless, I gave up at this point with trying out stuff... 

[Schillerr]

Energy saving didn't help me.

Disabling Wi-Fi and deleting the weather clock widget helped.

[GODFIBER]

sorry to here that because for me iv managed to have it continuously operate for 10 hours without boot looping not even once i also did the catch wipe before starting this test yesterday

to get that to work i had to use a different type c wire plugged into my pc(works with laptops too) for my pc to recognize it then i was able to get onto the menu after doing the steps.

[GODFIBER]

iv managed to have it continuously operate for 10 hours without boot looping not even once i also did the catch wipe before starting this test yesterday

to get the data catch wipe to work i had to use a different type c wire plugged into my pc(works with laptops too) for my pc to recognize it then i was able to get onto the menu after doing the steps.

[Members_2eKoj97]

I have dumped logs out of the system, which shows a short cycle of turning the system on to the Home screen then very shortly after it crashed and starts the boot loop.
I have used: "adb logcat *:E" so it only logs out the important messages.
I have analyzed it and also aked ChatGPT to anylze it for me and looks more like software related just as we assumed all the time.
Here is the dump: https://filebin.net/frhttvnsb6uspgh6

[Members_2eKoj97]

The log file contains a variety of error messages from multiple system components, suggesting a possible systemic issue or a corrupted system configuration. Key observations include:

Key Errors
Filesystem/Key Management Errors:

FsCrypt: Multiple errors related to encryption keys and filesystem preparation (e.g., "Cannot find key for 0").
vold: Issues related to volume management and metadata encryption.
Permission Denials (SELinux AVC Errors):

Multiple avc: denied entries from SELinux indicate that processes were attempting unauthorized operations, such as accessing system files or performing privileged tasks.
Driver and Hardware Errors:

HYPER-HAL: Errors related to resource management, such as missing configuration files and failed library loads.
SehLight and hwc-drm: Missing system files for various hardware components.
Daemon and Service Failures:

engmode_world and engmode_cp_watcher: Failures to connect to critical services.
KeyStorage: Issues with accessing or retrieving keys.
StrongBox: Mention of hardware support issues.
Boot Process Errors:

bootstat: Missing system boot information files.
SurfaceFlinger and BootAnimation: Issues with rendering or initializing display during boot.
Likely Causes of the Crash and Boot Loop
Corrupted Filesystem or Encryption Keys: Errors in key retrieval and filesystem preparation suggest that a critical part of the system (e.g., /data) may be corrupted or encrypted with missing keys.

SELinux Policy Violation: The extensive avc: denied errors indicate that essential processes were blocked due to misconfigured SELinux policies.

Driver or Hardware Failures: Missing files and failed library loads (e.g., libqti-perfd-client.so) could lead to crashes in key hardware-dependent services.

System Configuration Errors: Missing or corrupted configuration files for hardware components and services could prevent proper initialization during boot.

Incomplete or Failed Update: If the system was recently updated or modified, incomplete changes might have led to inconsistencies.

[Schillerr]

Reboots do not occur when the device is heating up. But from something else. But then, when rebooting, the device heats up. It's definitely software.

[Members_2eKoj97]

yep, hence I ran another time a intense 30mins benchmark it heated up the device heavily and was fine and dandy, then after cool off after a while it just crashed randomly, so unrelated to heating and able to withstand even the extremee cpu, gpu usage. Samsung is careless to react in a meaningful way for us, we are probably 10s of thousands of people if not hundreds of thousands with flagships phones s22 and s23...

[Schillerr]

• I have an old s10. I use it as a second phone. There have been no similar problems since 2020. If the s22 does not stop doing this (bootloop), then I will use the s10 as the main one (you only need to replace the battery), and I will take a Chinese smartphone as the second one.

[Members_2eKoj97]

this year I wanted to upgrade to a new s24 or s25 Ultra from my current s22 (basic one) but now I couldn't stomach the purchase and I am inclinced to switch back to iPhone for an iPhone Pro Max prbably. In the past I have used iphone, xiaomi and for a while samsung. My temp phone is Xiaomi currently works like a charm if I count in how old it is, feels much more reliable than samsung. I am surprised the lack of care samsung shows. There has been so many reports with the same update since september for s23 users and we got the same updates later as s22 users and got the same problems but probably even more widespreaded! Shame on you samsung!