[Samsung Galaxy A52 5G] viscoelastic:
I'm having the same issue, also on a Samsung Galaxy A52 5G, unlocked, not rooted, One UI version: 5.1, Android 13

I've never messed with the OS on any of my phones so I'm a newbie.

I was about to go looking for firmware from the previous firmware version (for me it looks to be A526U1UESAEWG1 released 2023-07-18) since I'm not concerned about a full storage wipe, but from what I'm seeing it doesn't even seem worth trying now. I'm feeling in over my head at this point. To add to our list of clues, here's the notes on what happened with my Galaxy A52:

08-18-2023 at 2:13 AM

- OTA firmware update

A526U1UESAEWG3/A626U1OYMAEWG3/A526U1UESAEWG3

08-21-2023

- between 10:00-10:18 AM 1st instance of boot loop

- battery at 100%, recovery logs looked like software was trying to debug, left phone plugged in overnight, phone was functional in the morning

08-24-2023

- 3:50 PM phone begins boot loop while using phone

- tried several things, wipe cache partition in recovery mode, fully deplete battery by allowing boot loop while not on charger, removed and reinserted SD card etc

- left phone plugged in and allowed to boot loop overnight

08-25-2023

- 7:00 AM (ish) battery at 100%, could not make calls, send text messages, toggle on wifi or toggle on bluetooth, but could use all other functions including internet via mobile network data

- turned off phone to back up SD card

- 12:19 PM rebooted phone with SD card inserted, boot loop resumed

- powered down til the evening

- left plugged in and on, allowed to boot loop overnight

08-26-2023 morning

- 7:00 AM (ish) battery at 100%, could not toggle on wifi or toggle on bluetooth, could make phone calls, send text messages, and use all other functions

- left phone on, did not plug in charger, battery remained charge through limited use, did not restart or attempt to connect to wifi or bluetooth, no boot loop occurred

08-27-2023

- backed up contacts, messages, and app data with Samsung Smart Switch

- backed up contacts, messages, and app data

- left phone and kept charged for the next few days while researching options, did not restart, try to use wifi or bluetooth, was able to perform backups

08-28-2023

- used charger a few times, did not attempt to connect to bluetooth or wifi

08-29-2023

- copied update and system info into notes

- restarted phone, immediately began to boot loop

- could connect to wifi and bluetooth, but after 2 minutes began boot loop

- Android Recovery mode - ran "Wipe data/factory reset" (could not tell whether this would reinstall firmware like USSD code *2767*3855#. Since my data was backed up, this seemed to be the safer option to try 1st.

- rebooted

- boot loop started again, put phone on charger

- battery 100%, welcome/setup screen

- got to wifi screen in setup, tried to turn on wifi, bootloop began again, back on charger

- battery 100%, boot loop stopped, tried to connect to wifi, could not, skipped wifi setup and all remaining setup screens

- firmware version was the same

- 7:23 PM boot loop began again

- turned off phone to start looking for Samsung USB driver and older firmware versions based on this [SOLVED!!] Recover data with TWRP after device is stuck on boot loop? XDA post for a Galaxy A22 in January 2023 (see the 2 edits from nanawa)

- came across these threads that make it seem less likely that new firmware loaded through ODIN will fix my issue

-------

other instances I found of users with error "Unable to set property "ro.boottime.init.mount.cache"

- XDA: 09-17-2021 Samsung Tab S7, Galaxy Note 4, Z Fold 4, S23 - multiple users

- Reddit: 12-2021 Galaxy Tab S6 - user hoobaSKANK mentions

- XDA: 02-25-2022 Samsung M31 - user nauxnam mentions

- Github: 07-26-2022 Galaxy A13 4G (SM-A13F) - user Exynos-nibba

- Github: 07-27-2022 Galaxy S21 Ultra (G998B) - user himekifee

- Github: 07-27-2022 Samsung Tab S7 Plus (T976B) - user himekifee

*Note, it looks like there were firmware updates around 07-19-2022 and 12-16-2021 (for OYM/United States location) which seems to line up with the timing of the posts above.

-------

Edit/Update 2023-08-31 5:00 AM

Since I haven't altered the software on my phone, I contacted Samsung's Customer Care Chat.

I told them I had boot loop after OS update on the 18th. They asked me to soft reset the phone (volume down key + power button). No effect.

They asked for IMEI, then responded with the attached reply. Basically that it's a hardware issue from a loose screen connection or motherboard connection and that even if I get it repaired the LCD screen will eventually black out so I should trade in for a discounted new phone.

I replied referencing the boot loop error, they restated that it was the LCD screen. I asked if they were stating it was a loose connection and they confirmed.

I've had the phone for 17 months and apparently that is considered "very old" and a lot of use. They also stated that this issue is mainly caused by "usage of the device".

I got an extension on the offer for trade in so I have time to think about what I want to do next. I'm not convinced yet that it's a hardware issue, since the reply came before I referenced the error code. Seems like it might be a default response to resolve an issue, rather than a real answer. I'm going to price shop and have a think about other options before deciding if I want to take their trade-in deal.

------

Edit/Update 2023-08-31

Apparently didn't include this in original post, but I'm still curious about this GitHub post that claims the boot loop can be fixed by removing "avb flags from the fstab" and whether this only applies to rooted phones or if the issue occurs in unrooted phones as well.