Crashes in the Android operating system are often associated with damage to system libraries or critical firmware files. The user may encounter endless reboots, application launch errors, or unstable operation of the modem. Data integrity is a fundamental requirement for stable operation of a mobile device. Violation of the file structure can occur due to a power failure during the update, physical memory corruption, or malware.
To diagnose such problems, it is not enough to simply restart the smartphone. It is necessary to use specialized tools that can verify checksums or analyze the partition structure. In this article we will look at methods from simple applications to advanced commands ADB. Understanding these processes will help you determine whether the device requires flashing or the problem can be solved programmatically.
Ignoring signs of file corruption often leads to complete inoperability of the gadget. If the system reports errors during boot, you need to act immediately. Modern verification methods make it possible to identify even minimal deviations in the code.
Causes of violation of the integrity of system data
Physical wear of memory chips eMMC or UFS is one of the most common reasons for the appearance of bad sectors. Over time, memory cells lose their ability to hold a charge, which leads to distortion of the recorded information. In such cases, a software check only states the fact of damage, but does not eliminate the physical malfunction.
The second common reason is incorrect completion of recording processes. If you interrupt the installation of the update OTA or disconnect the device from the computer while transferring files, the structure of the file system may be damaged. This is especially critical for the section systemwhere the main operating system libraries are stored.
⚠️ Attention: Frequent sudden power outages can lead to irreversible damage to the bootloader. If the device stops turning on after a failure, do not try to charge it indefinitely while it is turned off - contact the service.
Malware can also intentionally modify system files. Viruses-miners or Trojans often replace original libraries with their own versions to gain deep access to the system. Checking the hash sums of critical files allows you to identify such substitutions, since the digital signature will no longer match the standard.
Poor-quality custom firmware or modified_recovery_images often contain compilation errors. If you installed unofficial software, integrity problems may be present from the start. In this case, the only solution is to return to the stock version of the software.
Using file managers for basic scanning
The most accessible method of primary diagnostics is the use of advanced file managers with support for calculating checksums. Applications like Total Commander or Mixplorer allow you to calculate the hash of a specific file directly on the device. This is useful for checking downloaded archives or installation packages APK.
The verification process is as follows: you select the file, call the context menu and find the "Properties" or "Information" item. The extended data displays the value MD5 or SHA-256. The resulting string of characters must be compared with the reference value, which is usually published by the developer on the official website.
- 🔍 Open the file manager with superuser rights to access the system partitions.
- 📂 Find the target file in the directory
/system/binor in the downloads folder. - ⚡ Use the built-in hash sum calculator function in the action menu.
- ✅ Compare the received code with the official value on the manufacturer's website.
It is worth considering that standard file managers without root access do not have access to protected sections of the system. Therefore, it will not be possible to check the integrity of the kernel or critical drivers in this way. For in-depth diagnostics, more powerful tools will be required.
Use the "Compare files" function in file managers if you have a copy of the original file on the memory card. This will speed up the process of finding differences without manually entering hashes.
Checking via Recovery Mode and Fastboot
Recovery Mode Recovery provides access to low-level file system checking functions. In stock recovery from manufacturers like Samsung or Xiaomi detailed logs are often hidden, but the cache clearing function (Wipe Cache Partition) indirectly checks the integrity of temporary files. If the process ends with an error, this is a signal of problems with the partition cache.
Custom recovery, such as TWRP, have much wider functionality. They allow you to mount partitions and check their status through a terminal built into the interface. The fsck (File System Consistency Check) command starts scanning and correcting logical errors in the file system.
fsck.ext4 -f /dev/block/mmcblk0pXXIn Fastboot mode, you can check the status of the bootloader and critical sections before flashing. The command fastboot getvar all displays detailed information about the device status, including lock flags and partition versions. This helps determine whether the structure of the boot images has been corrupted.
⚠️ Warning: The fsck command may cause data loss if the file system is severely damaged. Always make a full backup of the data partition before running file system recovery utilities.
Some manufacturers implement a boot verification function into the recovery itself. If, when you try to enter recovery mode, you see a warning about image corruption, this means that the partition signature does not match the keys hardwired into the bootloader. In this case, loading the original system is impossible.
☑️ Actions before entering Recovery
Integrity analysis via ADB and terminal
The most professional method is to use a debug bridge Android Debug Bridge. By connecting your smartphone to your computer, you can execute commands that are not available from the system interface itself. This allows you to check files even if Android boots but is unstable.
First you need to gain access to the device shell. Enter the command adb shell in the computer terminal. If received root accesson the device, run the command su to escalate privileges. Without superuser rights, access to most system files will be denied.
The main verification tool is the utility md5sum or sha256sum. You can pass the path to a specific file and get its hash. For example, to check the interface library:
adb shell su -c"md5sum /system/framework/framework-res.apk"It is also possible to check the integrity of the entire section by creating a dump and comparing it with the standard. However, this process requires a lot of time and free space on the computer. Most often, critical points are checked: the bootloader, kernel and main frameworks.
| ADB command | Purpose | Root required |
|---|---|---|
adb shell pm list packages |
Checking the list of installed applications | No |
adb shell su -c"md5sum /path" |
Calculating the file checksum | Yes |
adb reboot bootloader |
Rebooting to Fastboot mode | No |
adb shell dmesg | grep error |
Searching for errors in the system kernel | Yes |
Analysis of kernel logs via command dmesg allows you to identify disk read errors in real time. If the command output contains messages about I/O error or Buffer I/O error, this is a direct indicator of physical memory corruption or a serious controller failure.
What to do if ADB does not see the device?
Make sure that ADB drivers are installed. Try a different USB cable or port. On your phone, in the developer menu, enable “USB Debugging” and confirm the RSA key fingerprint on the smartphone screen.
Automatic verification of AVB and dm-verity
Modern devices based on Android 10 and higher use the mechanism Android Verified Boot (AVB). This technology verifies the integrity of every step of the boot process, from the bootloader to the system. If even one byte in the signed section is changed, the device will refuse to boot or go into limited functionality mode.
Mechanism dm-verity works at the block device level. It transparently verifies the data when reading it. If a hash mismatch is detected, the system may attempt to correct the error or block access to the file. In the logs, this is reflected as messages from the kernel about a verification violation.
The user can see the verification status in the developer menu or through special applications. An "Orange" or "Red" status in the bootloader indicates that the integrity of the software has been compromised. This often happens after unlocking the bootloader or installing a custom recovery.
A critical feature of AVB: on many modern smartphones, re-locking the bootloader after installing custom firmware is impossible without returning the original signing keys, which can lead to the device being "bricked."Disabling dm-verity is only possible on devices with an unlocked bootloader and custom kernel. For the system to function normally, this mechanism must be active, as it ensures that the operating system has not been compromised by malicious code.
The presence of messages about AVB violations at boot means that the system does not trust the current state of the software environment. This is not always an error, but requires an understanding of the reasons for changing partitions.
Restoring damaged files and partitions
If the scan reveals violations, the next step is recovery. For logical file system errors, it is often sufficient to perform a factory reset (Factory Reset). This procedure recreates the structure of data and cache partitions, eliminating minor damage.
In more complex cases, a complete flashing of the device through official utilities is required. For Samsung used Odin, for Xiaomi — Mi Flash Tool, for universal devices - SP Flash Tool. These apps write fresh images of partitions to the device, guaranteeing their perfect integrity.
- 💾 Download the official firmware exactly for your model and region.
- 🔌 Put your smartphone in Download Mode or Fastboot.
- ⚙️ Launch the app firmware and select the file with the system image.
- 🚀 Click the Start button and wait until the process completes without disconnecting the cable.
Sometimes only a specific application or its data is damaged. In this case, clearing the application data through the settings or completely reinstalling it helps. If the problem is a system application that cannot be removed, a system update or reset may be required.
⚠️ Attention: When flashing firmware using the SP Flash Tool, never select formatting all partitions (Format All + Download) if you are not sure of the memory layout structure. This can erase the IMEI and serial number of the device.
In case of physical memory damage, software methods are powerless. If, after flashing, integrity errors return or the writing process is interrupted with an error, the chip most likely has failed. In such a situation, only replacing the motherboard or memory chip at a service center will help.
Is it possible to restore IMEI after a failure?
Restoring IMEI is only possible if you have a backup copy of NVRAM/NVDATA. Without a backup, recovery in a legal way is extremely difficult and depends on the processor model.
FAQ: Frequently asked questions about file integrity
Is it possible to check the integrity of the system without root access?
A full check of system files without superuser rights is impossible, since access to section /system closed. However, you can use the built-in diagnostic functions in the phone menu or check the integrity of user files through regular file managers.
What does the "Verification Failed" error mean during boot?
This message indicates that the Android Verified Boot mechanism has detected a mismatch in the digital signature of the boot image. Most often this happens when you try to load custom firmware onto a device with a locked bootloader.
How often should you check file hashes?
Regular checking is not required. It is enough to perform diagnostics when symptoms of unstable operation appear: crashes, reboots or update installation errors. For ordinary users, this procedure is redundant.
Does a factory reset restore damaged files?
A reset restores the logical structure of the data partition and returns the system settings to their original state, but it does not overwrite the partition itself system. If kernel files or system libraries are damaged, a complete flashing will be required.
Is it safe to disable dm-verity?
Disabling dm-verity reduces the security level of the device, allowing changes to be made to the system partition. This is necessary for deep customization, but makes the phone vulnerable to rootkits and system viruses. Do this only if you understand the risks.