It appears you're experiencing a boot loop on your Samsung Galaxy Note 10 Plus after installing One UI 6.1.1 (Android 14) and clearing Google Play Store data. This is a common issue when custom ROMs or system modifications encounter unexpected errors, leading to the device being unable to fully boot into the operating system. While a full wipe is often the most straightforward solution, there are several troubleshooting steps you can attempt before resorting to data loss.
According to www.iAsk.Ai - Ask AI:
The "powered by Android" logo boot loop indicates that the initial bootloader and kernel are loading, but the system is failing to initialize the full Android operating system. This can be due to corrupted system files, incompatible modules, or issues with the data partition. Clearing Google Play Store data, while seemingly innocuous, could have triggered an underlying incompatibility or exposed a pre-existing issue with the custom ROM installation, especially if it involved system-level changes or permissions that were then reset or altered.[1] Since you've already tried clearing the cache through TWRP without success, the problem likely lies deeper than just a corrupted cache partition.
Potential Solutions to Resolve Boot Loop Without Wiping
- Re-flashing the ROM (Dirty Flash):
- If you still have the One UI 6.1.1 ROM zip file on your device's internal storage or an SD card, you can try to re-flash it without wiping data. This is often referred to as a "dirty flash." This process overwrites the system files with a fresh copy from the ROM, potentially fixing any corruption, while leaving your user data intact.[2]
- Steps:
- Boot into TWRP recovery.
- Go to "Install."
- Navigate to the location of your One UI 6.1.1 ROM zip file.
- Select the zip file and swipe to confirm flash.
- Crucially, do not wipe data or factory reset.
- After flashing, clear Dalvik/ART Cache and regular cache (if prompted or available).
- Reboot system.
- Flashing a Different Kernel or Magisk (if applicable):
- Sometimes, the boot loop can be caused by an incompatible kernel or issues with root solutions like Magisk. If you flashed a custom kernel separately or installed Magisk after the ROM, try flashing a different, compatible kernel for your device and ROM, or re-flashing the Magisk installer zip if you suspect it's the cause.[3]
- Steps:
- Boot into TWRP recovery.
- Go to "Install."
- Select the kernel or Magisk zip file.
- Swipe to confirm flash.
- Clear Dalvik/ART Cache and regular cache.
- Reboot system.
- Note: Ensure any kernel or Magisk version you flash is specifically compatible with One UI 6.1.1 and your Note 10 Plus model.
- Checking Logcat for Errors (Advanced):
- If you have access to a computer and ADB (Android Debug Bridge) is set up, you can try to capture a logcat during the boot loop. This can provide valuable information about what process is failing and causing the loop.[4]
- Steps:
- Connect your phone to your computer while it's in the boot loop.
- Open a command prompt or terminal.
- Type
adb logcat > logcat.txt
and press Enter. - Let it run for a minute or two while the phone is boot looping.
- Press Ctrl+C to stop the logcat capture.
- Open the
logcat.txt
file and look for "FATAL EXCEPTION," "crash," or other error messages that might point to a specific app or system service failing.
- This method requires technical expertise to interpret the logs.
- Restoring a Nandroid Backup (if available):
- If you made a Nandroid backup (full system backup) in TWRP before installing One UI 6.1.1 or at a point when your phone was working correctly, restoring that backup is the safest way to revert to a working state without data loss.[5]
- Steps:
- Boot into TWRP recovery.
- Go to "Restore."
- Select the backup you wish to restore.
- Swipe to confirm restore.
- Reboot system.
When Wiping Data Becomes Necessary
If none of the above steps resolve the boot loop, then a full data wipe (factory reset) through TWRP is likely your only remaining option to get the phone booting again. This will erase all user data, apps, and settings, returning the device to a fresh state as if the ROM was just installed.
- Steps for Full Wipe:
- Boot into TWRP recovery.
- Go to "Wipe."
- Select "Advanced Wipe."
- Check "Dalvik / ART Cache," "Cache," "Data," and "System." Do NOT check "Internal Storage" unless you want to erase everything, including your ROM zip and backups.
- Swipe to Wipe.
- Go back to "Install" and re-flash the One UI 6.1.1 ROM.
- Reboot system.
Remember to always back up your data before performing any significant system modifications or troubleshooting steps on a custom ROM.
Authoritative Sources
- Android Boot Process Explained. [XDA Developers]↩
- How to Dirty Flash a Custom ROM. [Android Authority]↩
- Understanding Android Kernels. [LineageOS Wiki]↩
- How to Use ADB Logcat. [Developer.android.com]↩
- What is a Nandroid Backup?. [TWRP Official Website]↩
Answer Provided by iAsk.ai – Ask AI.
Sign up for free to save this answer and access it later
Sign up →