Android-based smartphones begin to work slower over time, applications crash, and the system freezes. Often the root of the problem lies not in the processor or RAM, but in the degradation of the drive. Flash memory has a limited resource of rewrite cycles, and over time it may develop bad sectors or logical file system errors. If you notice strange artifacts, data loss or sudden reboots, you need to urgently diagnose.
In this article we will look at all the available ways to check the integrity of your device's storage. We will not rely on guesswork, but use system tools, USB debugging capabilities and specialized software. Timely diagnostics can save your important photos and documents from irretrievable loss. Let's take a look at how to distinguish a software failure from physical wear and tear of the memory chip.
Symptoms of memory failure and primary diagnostics
Before running complex tests, you should pay attention to indirect signs that indicate problems with the drive. The user may encounter a situation where the phone sees the file, but cannot open it, or the data copying process freezes at a certain percentage. These are classic symptoms bad blocks of physical damage to memory cells.
One of the obvious markers is the appearance of error messages when installing system updates. If the download is successful, but failures occur during the writing stage, it is likely that the sector where the firmware is trying to write is damaged. You should also be wary if the names of files in the gallery turn into a set of incomprehensible symbols or hieroglyphs.
Pay attention to the speed of the device. A sharp drop in performance when working with large files often indicates that the memory controller is trying to repeatedly read data from damaged areas. Logic errors file systems can cause similar symptoms, but they are easier to fix than physical wear.
⚠️ Attention: If your device starts making strange sounds (which is rare for modern smartphones, but possible when the controller vibrates) or gets very hot in the area of the camera and processor when idle, immediately make a backup copy of the data and stop active use.
For an initial assessment of the condition, you can use the built-in diagnostic tools that many manufacturers have. For example, in smartphones Samsung or Xiaomi there are hidden engineering menus. However, they do not always show detailed wear statistics, so we move on to deeper verification methods.
Using the engineering menu for a quick check
The fastest way to access diagnostic tools is to enter special codes in the Phone application. This method does not require installing third-party software or connecting to a computer. However, it is worth remembering that the set of commands depends on the processor manufacturer and the specific Android shell.
For processor-based devices MediaTek code often works ##3646633##. After entering, the engineering menu will open, where you need to go to the Hardware Testingtab, then select Memory. Here you can run a read and write test. If the test fails, this is a direct signal of problems with the chip.
On devices with processors Qualcomm the situation is more complicated, since there is no single universal code. The combination ##4636##is often used, which opens the testing menu. In the Device information section you can find usage statistics, but a detailed memory test is less common here. In such cases, it is better to use ADB.
- 📱 Enter the code into the standard dialer without pressing the call button.
- 🔧 Go to the Hardware Testing section.
- ▶️ Run the Read/Write test and wait until the process completes.
⚠️ Attention: Do not change the settings in the engineering menu if you do not know exactly what they are responsible for. Resetting sensor calibration or changing processor frequencies can lead to unstable system operation.
It is important to understand that the engineering menu shows the current state, but does not always predict future failure. If the test is passed, but the symptoms persist, the problem may be at the file system level, not the physical media.
What to do if the code does not work?
Many manufacturers block access to the engineering menu in global firmware versions. In this case, try to find a specific code for your model on the 4PDA forum or use the ADB method described below.
Advanced diagnostics via ADB and computer
The most accurate data about the health of the drive can be obtained by connecting your smartphone to the computer and using the tools Android Debug Bridge (ADB). This method requires you to enable USB debugging in the developer menu. Connect the device with a cable to the PC and make sure that the computer sees it in debugging mode.
You can use the fsck command to check the file system for logical errors, but this requires root access. Without superuser rights, we can check the availability of memory blocks through reading. Open a command line on your computer and enter the command to enter the device shell:
adb shellNext, using utilities like dd or specialized scripts, you can try to read memory sectors. A safer option is to use the command sm list-disks to check the visibility of drives, as well as analyze system logs. Enter the command to view the system log in real time:
adb logcat | grep -i "error"If you see constant messages about I/O error or read failurein the logs, this is a sure sign that the memory controller cannot access certain addresses correctly. Such errors often precede a complete failure of the device.
- 💻 Install ADB drivers and the tools platform on your computer.
- 🔌 Connect your smartphone and enable debugging in the window that appears.
- 📝 Analyze the log output for I/O errors.
Use a high-quality original USB cable. Poor contact can simulate data transmission errors, which the user will mistake for a faulty phone memory.
This method requires some technical literacy, but it gives the most objective picture without installing dubious applications directly on the phone. If you are not confident in your abilities, it is better to use graphic utilities.
Checking the SD card and external storage
Often problems are attributed to the internal memory of the smartphone, while the culprit is the microSD card. Memory cards wear out much faster than built-in storage, especially if they are of a low speed class. You can check them both on the smartphone itself and using a computer.
On Android, the built-in verification utility works quite effectively. Go to Settings → Storage, select your SD card and find the menu item (three dots) where there will be an option “Check” or “Fix”. The system will scan the file system for errors and try to eliminate them.
For a deeper check, it is better to remove the card and insert it into the computer card reader. Use the free utility H2testw or FakeFlashTest. These apps write test data to the card and then read it back by comparing the checksums. This allows you to identify not only bad sectors, but also fake cards with fake volume.
| Error type | Symptom on Android | Cure method |
|---|---|---|
| Logical failure | Files do not open, name distorted | Format or chkdsk |
| Bad blocks (physics) | Stuck when copying | Replacing the drive |
| Wear of the controller | Card is detected as empty | Replacing the drive |
| Fake volume | Data disappears after filling | Return to seller |
If the utility is on computer shows errors, try formatting the card into a file system exFAT or FAT32 through standard Windows tools. If errors are repeated after formatting, the card should be disposed of, since storing data on it is dangerous.
The built-in memory (eMMC/UFS) is soldered on the board and cannot be replaced at home, unlike an SD card, which can be easily replaced with a new one.
Third-party applications for stress testing
There are many applications on Google Play that promise memory diagnostics. However, you should be careful: many of them simply show free space, and not the actual health of the chip. We need tools that put stress on the drive.
One of the reliable options is the application AIDA64. In the “Devices” section, it displays the memory type, its capacity and the current temperature. Although it does not perform a write test, overheating of the memory controller during operation can indirectly indicate heat dissipation problems or a faulty chip.
To conduct an actual write test, you can use benchmarking applications such as AAndroBench or CPDT. Run a write speed test. If the speed drops to zero or the application crashes with an error in the middle of a test, this is a sign of memory instability. Normal speed for modern UFS 2.1 memory should be at least 200 MB/s for sequential writing.
- 🚀 Download the benchmark from the official application store.
- 📉 Run the Sequential Write test.
- ⏱️ Follow for speed stability throughout the test.
Remember that intensive data recording during tests creates additional load on a worn-out drive. If you suspect that memory is on its last legs, first save important data to the cloud or computer, and only then run stress tests.
⚠️ Attention: Application interfaces and testing methods may change with developer updates. Always check the official documentation for a specific utility before starting aggressive tests.
Radical measures: Resetting and replacing the drive
If software testing methods reveal errors, but the device is still working, you can try to correct logical damage using a hard reset. This will delete all data, but will repartition the file system, eliminating bad sectors from the address space (if the controller supports it).
Be sure to make a backup copy before resetting. Go to Settings → System → Reset settings and select “Delete all data”. After rebooting, the device will be clean. If the memory errors were logical, they will disappear. If the problem is physical, the failures will return very quickly, perhaps already during the initial setup.
In the event of physical wear and tear of the built-in memory, repairs at a service center are often not economically feasible. Replacing a memory chip requires the use of a soldering station and a programmer to bind the new chip to the processor (especially on encrypted devices). It is often easier to buy a new smartphone.
☑️ Preparing for a full reset
Ignoring memory problems can lead to the smartphone turning into a “brick” at the most inopportune moment. Regularly checking the storage condition is part of the culture of digital hygiene, which prolongs the life of your gadget.
Is it possible to recover data from damaged Android memory?
Data recovery is only possible if the damage is logical (deletion, formatting, file system failure). If the chip is physically worn out (bad blocks), the chances are close to zero, since the data is physically missing or unreadable. Specialized laboratories can try to re-solder the chip, but this is very expensive.
Does filling the memory affect speed and errors?
Yes, filling flash memory by more than 90% critically reduces its speed and increases wear. It is more difficult for the controller to find free cells to write to, which leads to fragmentation and errors. Always leave at least 10-15% of free space.
Why does memory work slower after updating Android?
After a major update, the system indexes files and optimizes applications in the background. This creates a high I/O load in the first hours or days after the upgrade. Typically, performance recovers on its own after 2-3 days of active use.
How to check memory without root access?
Without root access, only indirect methods are available: speed tests through benchmarks, log analysis via ADB (without deep partition access) and built-in file system checks for SD cards. Direct scanning of physical sectors of internal memory without superuser rights is not possible for Android security reasons.
What are eMMC and UFS, and is there a difference in reliability?
eMMC is an older memory standard that operates in half-duplex mode (read or write). UFS is a modern standard that operates in full duplex mode (simultaneous reading and writing). UFS is much faster and, as a rule, more reliable due to a more advanced controller, but both types have a limited rewriting resource.