6.1 Boot Loop Cause : latest official firmwire is corrupt

[Members_2eKoj97]

I have dumped many logs after crashes and it boils down to the following:

1. Missing Base APKs:
Repeated errors like:Failed to parse /system/framework/arm: Missing base APK in /system/framework/arm Failed to parse /system/priv-app/SamsungCoreServices: Missing base APK in /system/priv-app/SamsungCoreServices
These indicate that critical system files required for Android's functionality are either missing or corrupted. This is a major issue that can cause crashes, instability, and boot failures.

2. SELinux Denials:
Multiple avc: denied errors show that SELinux is blocking access to certain resources, such as: path="/data/data/com.samsung.android.fast/databases/google_app_measurement_local.db"
This suggests that apps like com.samsung.android.fast (related to charging and performance management) are being restricted by SELinux policies, potentially causing app malfunctions.

Root Cause

The crash appears to be caused by a combination of:

• Corrupted or missing system files, particularly in /system/framework and /system/priv-app.
• SELinux policy misconfigurations, leading to blocked access for critical apps.
• File system corruption, which may prevent proper installation or operation of system components.

These issues likely stem from an incomplete or problematic firmware installation, or software bugs specific to this device model (Exynos-based Galaxy S22).

I have freshly flashed with the latest firmwire:

https://www.sammobile.com/samsung/galaxy-s22/firmware/SM-S901B/EUX/download/S901BXXSDEXKA/1895092/

multiple times, so there is no questions left. We can try to turn off this and that and get the illusion that the phone works for a couple of hours or even days but it will crash eventually, it will all depend on the internal working of the system we have zero control over it as it is so close to the core workings of the operating system. 

[lance78]

Is this why my a556e has started re starting by it's self

[Tourbillon De La Vie]

Sounds more like hardware failure

Also see

https://eu.community.samsung.com/t5/galaxy-s22-series/finding-the-reason-behind-the-infamous-s22-boo...

[SocietyGirl]

Why did you flash and not update through official channels?

[Members_2eKoj97]

it's called troubleshooting

[Members_2eKoj97]

no it doesn't, if we were talking about chances, because nobody can be sure, it's 95% probability on SW issue and 5% HW issue

[SocietyGirl]

ok

[Moiramon]

Have you tried flashing the previous firmware.

[Members_2eKoj97]

yes, with the one before the latest, so with this:
https://www.sammobile.com/samsung/galaxy-s22/firmware/SM-S901B/EUX/download/S901BXXUDEXK5/1893604/

unfortunately we can't go back more because of the bootlooder version can't be downgraded for samsungs

[Schillerr]

please tell me, has the firmware manually improved the situation? or do we have to wait for a normal update at the end?