Why the usual methods all fail
Ask how to check a phone's storage and you get the same four answers, all of which quietly assume a working device:
| Method | Needs | On a dead board |
|---|---|---|
| Settings → Storage | Android fully booted | Unavailable |
| Dialler / secret codes | A working dialler | Unavailable |
| USB / ADB from a PC | Board enumerates on USB | Usually unavailable |
| Recovery or download mode | Bootloader still runs | Often unavailable |
| Memory IC marking | Light and a loupe | Works |
The last row is the point. The part number laser-etched on the memory package is a physical property of the board. It does not care whether the board has power.
What still works, and why
Storage capacity is fixed at manufacture by which memory part was fitted. That part carries a manufacturer part number on its face, and that part number maps to exactly one capacity. So the question "how much storage does this board have" has a definite answer as long as the chip is still readable — regardless of whether the board boots, has been wiped, has water damage, or has been pulled out of a housing and thrown in a tray.
The procedure
- Remove the shield over the SoC area. On most boards it is a thin stamped can, either clipped or soldered.
- Identify the memory package — the large chip next to or stacked on the CPU. Detail in how to identify the memory IC.
- Clean it with isopropyl. Flux and dust hide laser etching more effectively than you would expect.
- Light it from a shallow angle and read the top line. The lines beneath are lot and date codes.
- Look it up in the IC checker — 16,776 part numbers, free, no install.
What you get back
Storage capacity, the package type (eMMC, UFS, eMCP or uMCP), the physical package, and where the part is a stacked one, the LPDDR RAM in the same package. For a scrap or repair decision that is the full picture: what the board holds and what a replacement would have to match.
Raw capacity vs usable space
The figure on the chip is raw capacity. What a user would have seen in Settings is smaller — the firmware, system partition and reserved blocks come out of it first. A 64GB part presents as roughly 52–58GB depending on the build; a 128GB part somewhere in the 105–115GB range.
So a mismatch of ten to fifteen percent between the chip figure and a remembered Settings number is normal and expected. A mismatch of fifty percent means you are reading a different chip, or the board has been reworked.
When the chip cannot be read
Two cases where visual identification runs out:
- The marking has been polished off. Reballed and reworked packages sometimes lose their etching to abrasive cleaning. Nothing to read; treat the board as unknown capacity rather than assuming.
- The package is physically damaged — cratered, cracked, or lifted. Even if you can read part of the code, a damaged package is not worth pricing as functional.
In both cases the only remaining route is electrical: reading the chip's identification registers with a programmer. That needs the package to still be functional, which on a physically damaged part is unlikely.