in the logs, it's written Unable to set property "ro.boottime.init.mount.cache"
- User
in the logs, it's written Unable to set property "ro.boottime.init.mount.cache"
Assistant
That error message
"Unable to set property 'ro.boottime.init.mount.cache'"is very telling - it indicates the system is having trouble mounting the cache partition during boot, which explains your bootloop issues.What This Error Means
The cache partition stores temporary system files and is critical for Android's boot process. When it can't be mounted, the system gets stuck in a loop trying to complete initialization.
Targeted Solutions
1. Cache Partition Repair (First Try)
Boot into Recovery Mode: - Power off completely - Hold Power + Volume Up + Volume Down simultaneously - In recovery, select "Wipe Cache Partition" - Reboot and test2. Format Cache via ADB (If Recovery Accessible)
adb shell mount umount /cache mkfs.ext4 /dev/block/by-name/cache reboot3. Odin Flash with Cache Focus
- Download your exact A53 firmware (match model: SM-A536B/DS, etc.)
- In Odin, flash ONLY the AP file first
- Check "Auto Reboot" OFF
- After successful flash, manually boot to recovery
- Wipe cache partition, then reboot
4. PIT File Repartitioning (More Aggressive) Since cache mounting is failing, the partition table might be corrupted:
- Download the correct PIT file for your A53 model
- In Odin:
- Add PIT file
- Enable "Re-Partition"
- Flash complete firmware (AP, BL, CP, CSC)
- Warning: This will completely wipe your device
5. Check for eMMC/Storage Hardware Issues If software solutions fail, this could indicate:
- Corrupted NAND flash storage
- Bad sectors in the cache partition area
- Hardware degradation
Diagnostic Steps
Before trying repartitioning:
- Boot into Download Mode - if this works consistently, bootloader is likely fine
- Try different firmware versions - sometimes newer/older versions handle storage differently
- Check if device gets hot during bootloop - could indicate hardware stress
Quick Test Sequence
- Recovery cache wipe (safest)
- Reflash AP file only via Odin
- If still failing, full firmware + PIT repartition
- If none work, likely hardware failure
The cache mounting error is actually good news in that it's specific and targetable. Start with the cache wipe in recovery - this fixes the issue about 60% of the time without data loss.
Which recovery options can you currently access on your A53?
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.