Error reports on Xiaomi devices are automatically stored in the system after application crashes, MIUI crashes or hardware problems. These logs take up space in memory, can contain sensitive data and even affect performance. However, there are no standard tools to remove them from the smartphone menu - hidden commands or technical manipulation are required.
In this article, we will discuss all the current ways to clean error logs: from simple (via Settings β Memory) to advanced (using ADB and Fastboot). Separately, we will focus on the nuances for different versions of MIUI (12-14) and models (Redmi Note 12, POCO X5, Xiaomi 13T, etc.). If you are faced with constant notifications of βcritical errorsβ or want to free up space, read on.
Why error reports accumulate and how dangerous it is
MIUI detects errors in two types of files:
- π Logs of applications (/data/anr/, /data/tombstones/) β Remains in the event of a software crash (e.g. Google Play Services or MiuiHome).
- π System dumps (/data/system/dropbox/) β are created when the kernel, drivers or hardware modules fail (camera, sensors).
Without cleaning, these files may:
- π¨ Burn internal memory (up to 500 MB-1 GB in a few months of active use).
- π Contain personal data: file paths, process names, geolocated log fragments.
- β οΈ Call the lags when filling out the section /data (especially on devices with 64/128 GB memory).
For example, on the Redmi Note 11 Pro+ with MIUI 13, users complained about cyclical reboots due to a crowded /data/log partition. On POCO F4, error logs prevented the update via OTA - the system demanded to vacate space.
β οΈ Attention: Deleting error logs does not correct the cause of the error. If crashes occur regularly (for example, Camera or Google Play crashes), after cleaning the files will appear again, in which case you need to diagnose the system or reset to factory settings.
Method 1: Cleaning through the Memory menu (without root)
The easiest method is to use the built-in MIUI tool to clean up the garbage, which removes some of the logs, but not all of the system dumps.
Instructions:
- Open the Settings β Memory.
- Click Clean (or Free in new versions of MIUI).
- Choose Deep Cleanup and confirm the action.
- Go to Files β Other β find the folders log, anr, tombstones and delete them manually.
This method works on all devices, but has limitations:
- β Doesn't clean core dumps (/data/system/dropbox/).
- β Requires manual folder search (hidden by default).
- β Secure and does not require superuser rights.
Enable the display of hidden files in the file manager
Check the vacant space (needs at least 10% of the total)
Close all applications before cleaning
Restart the device after the procedure-->
Method 2: Use of ADB (for power users)
If standard cleaning didnβt work, connect to the device via ADB (Android Debug Bridge), which removes all error logs, including system dumps, but requires a computer and enabled USB debugging.
Step-by-step:
- Enable USB Debugging in Settings β About Phone β MIUI version (click 7 times, then go back to Additional Settings β For Developers).
- Connect your smartphone to your PC and confirm the debugging permission.
- Open the command line (Windows) or terminal (macOS/Linux) and type:
adb shell
su
rm -rf /data/anr/*
rm -rf /data/tombstones/*
rm -rf /data/system/dropbox/*
rm -rf /data/log/*
exit
exitIf the su command doesn't work, you don't have root rights. In this case, use the alternative option without su (it will only delete part of the logs):
adb shell
rm -rf /sdcard/MIUI/debug_log/*
rm -rf /sdcard/log/*
rm -rf /sdcard/tombstones/*
exitβ οΈ Note: Delete files in /data/ without root, it can cause some services to fail (e.g. Google Play Services.
What if the ADB canβt see the device?
Method 3: Reset to factory settings (radical method)
If error logs take up a critical amount of space or the device is unstable, the only guaranteed way to delete them is to completely reset, which erases all data, including the system partitions where the dumps are stored.
How to reset:
- Create a backup of important data (photos, contacts, messages).
- Go to Settings β About the phone β Reset settings.
- Choose to erase all data and confirm the action.
- After the reboot, the device will be as new as it is β without logs and user files.
Advantages and disadvantages of the method:
| Pluses | Cons |
|---|---|
| Deletes all error logs, including hidden system logs | Wipes all user data (photos, apps, settings) |
| Fixes many software failures | It takes time to reset the device. |
| It works on all models Xiaomi, Redmi, POCO | It does not help if errors are caused by hardware problems. |
π‘
Before resetting, write down your device's IMEI (type *#06# in the dialer). In rare cases, after a hard reset, you may need to restore the IMEI through an engineering menu.
Method 4: Using Custom Recovery (TWRP)
For users with an unlocked bootloader and TWRP installed, an advanced method of cleaning logs through a recovery menu is available, which allows you to selectively delete system files without completely resetting.
Instructions:
- Turn off the device and press Volume up + Power to log into TWRP.
- Go to Advanced β File Manager.
- Find and delete the following folders: /data/anr /data/tombstones /data/system/dropbox /data/log
Reboot β System
Warnings:
- β οΈ Delete the wrong files in TWRP It can cause a blink (inoperability) of the device.
- β οΈ Without backup, data recovery will not be possible.
- β The method works even if the system does not boot (for example, due to critical errors).
Cleaning through Memory
ADB-team
Reset to factory settings
TWRP
None of the above.-->
Method 5: Disabling the collection of error logs (prevention)
To prevent the accumulation of new logs, you can disable some of the system services responsible for collecting them, which will not delete existing files, but will reduce their growth.
How to turn it off:
- Activate Developer Mode (as in Method 2).
- Go to Settings β Additional settings β For developers.
- Disable the following options: MIUI Error Report Automatically Collect USB Debugging Reports (if not used)
Reset the device.
Limitations of the method:
- β It does not work for some models with MIUI 14 (like Xiaomi 13 Ultra) where options are hidden.
- β It can interfere with certain functions (e.g. Game Turbo or Second Space).
- β Reduces processor load and reduces battery consumption.
π‘
Disabling log collection does not affect the warranty, but it can complicate the diagnosis of problems when contacting the Xiaomi service center.
Frequent Mistakes and How to Avoid Them
When cleaning logs, users often face the following problems:
- ADB can't see the device: π Check the cable (use the original USB Type C). π₯οΈ Install Xiaomi and Google drivers USB Drivers. π Restart your PC and smartphone.
- Lack of rights to delete files: π Unlock the bootloader and get root (instructions for Xiaomi are available on the site). 4PDA). π± Use it. TWRP instead ADB.
- After cleaning, the logs appear again: π οΈ This means that there is an unresolved problem in the system (for example, a firmware Conflict or a hardware defect). π Check the stability of the operation after disabling the Error Reports (see Method 5).
If none of the methods worked, and the device continues to "spray" errors - contact the service center.
- π Flash memory failure (especially on older Redmi models) 4X, Redmi Note 5).
- π€ Firmware damage after failed update.
- π Problems with the motherboard (for example, after a fall or moisture hit).