Used by NASA · the FBI · the U.S. Navy · Since 1999
NAND Flash Not Detected? What It Means — and Who to Call to Get Your Files Back
- No Data, No Data Recovery Fee
- Controller failure vs. bad NAND die, explained
- Written by a 27-year recovery engineer
- Chip-off & monolith NAND recovery in-house
Your SSD, USB drive, SD card, or phone suddenly stops showing up at all — the device is not recognized, no drive letter, no capacity, nothing but silence where your files used to be. Underneath almost every one of those devices sits the same component: NAND flash memory. When it “disappears,” the instinct is to assume the memory itself burned out and everything on it is gone. After 27+ years of NAND flash not detected cases in our lab, that assumption is wrong far more often than it’s right. This guide explains what actually happens when NAND flash stops being detected, how to tell a failed controller from failed memory, what to avoid doing next, and who to call for NAND flash data recovery when it’s time for a professional — the same controller-plus-NAND failure shows up on a failed SSD as it does on any other NAND-based device.
“NAND flash not detected” almost always means the controller chip that talks to your computer has failed — not that the NAND memory holding your files has been erased. Controller failure, firmware corruption, and physical/electrical damage account for most cases, and on unencrypted media (USB drives, SD and microSD cards, monolithic chips) the data can usually be read directly off the NAND chips in a lab, bypassing the broken part entirely. Phones tie their encryption to the processor, so a direct chip read returns unreadable data. SSDs depend on the controller: many modern ones always encrypt and some older ones only scramble, so we identify the controller first.
What Does NAND Flash Not Detected Mean for Your Files?
Usually, the files are still there. NAND flash not detected means the controller, firmware, or electrical path failed, while the memory chips keep their contents without power. The fix depends on the device: chip-off suits USB drives and SD cards; SSDs and phones depend on the controller or processor, so we identify it first. We have done this since 1999.
“Not detected points at the gatekeeper, not the vault. The chip behind it rarely forgets.” — Bruce Cullen, founder, eProvided
Do RIGHT NOW
- Stop using the device the moment it goes undetected
- Try it once on a second computer or port, then stop
- Note any smell, heat, or clicking — write it down
- Set the device aside exactly as it is
DON’T Do
- Don’t keep replugging or power-cycling it
- Don’t run repair or format tools on an undetected device
- Don’t attempt a firmware update or controller swap yourself
- Don’t open the case or apply heat to “dry it out”
Worried about specific files on a device with undetected NAND flash? Before trying anything else, you can start a free evaluation to check if your files are recoverable »
- What Happens When NAND Flash Is Not Detected?
- Common Causes of NAND Flash Failure
- Controller Failure vs. a Bad NAND Die
- Detected, Recognized, Mounted: What Each Word Means
- Detected, but 0 Bytes or “No Media”
- Which Devices This Affects — SSDs, USB Drives, SD Cards & Phones
- NAND Flash Myths — What’s True and What Isn’t
- NAND Flash Not Detected: What to Do Next
- Can NAND Flash Be Repaired or Fixed?
- Who to Call: What Happens During Professional NAND Recovery
- Real Cases: What “Not Detected” Looked Like
- How to Prevent NAND Flash Failures
- What Our Customers Say
- Frequently Asked Questions
- Recover Data from Undetected NAND Flash
- Related Recovery Services
What Happens When NAND Flash Is Not Detected?
NAND flash memory is the chip that physically stores your files — it sits inside SSDs, USB flash drives, SD and microSD cards, and the internal storage of every smartphone. It never stands alone: a small controller chip sits between the NAND and your computer, translating requests, tracking wear-leveling, and reporting the drive’s identity. “NAND flash not detected” means that conversation broke down — the operating system asked the device to identify itself and got silence, a garbled answer, or nothing at all.
EnlargeThe critical distinction: the NAND memory chips themselves are usually undamaged. They hold their contents without power, the same way they did the day they were manufactured. What fails is almost always the layer in front of them — the controller, the firmware, or the electrical path that lets your computer reach the chip at all. How that door gets opened depends on the device. On a USB flash drive, an SD card, or a microSD card, the memory is not locked to its controller, so reading the chip directly on lab hardware, which is how NAND flash recovery works for these devices, is a sound path when the controller is dead. On phones, and on SSDs whose controller encrypts, the key that unscrambles the data lives in the controller or processor, not in the memory chip, so a direct chip read returns only scrambled bytes. SSDs vary: many modern controllers always encrypt, while some older or budget ones only scramble the data. So we identify the controller first, then choose the path: repair the original board, move the controller and memory together onto a donor board, or read the memory directly and descramble it only when the controller does not encrypt. On a phone, the work is repairing the original board or moving the processor and memory together onto a donor board, so the original silicon can decrypt again. We cannot promise a result before the free evaluation.
Common Causes of NAND Flash Failure
Five failure modes account for most of the NAND flash not detected cases in our NAND flash data recovery and NAND chip data recovery queue.
| NAND Flash Failure Causes — What Happened & What It Means for Your Data | |||
|---|---|---|---|
| Cause | What’s actually happening | Software or hardware? | Files recoverable? |
| Controller failure | The chip managing the NAND has died or can no longer communicate; the memory behind it is untouched | ⚠ Hardware | ✓ Yes, by a method that fits the device |
| Firmware corruption | Often triggered by a sudden power loss mid-write, scrambling the map the controller uses to find your files | ⚠ Hardware-leaning | ✓ Yes, in most cases |
| Power surge / electrical damage | A surge or short can fry the controller or its power circuitry while leaving NAND cells intact | ⚠ Hardware | ✓ Usually, by the same device-specific methods |
| Physical damage | A cracked board, snapped connector, or water intrusion breaks the electrical path to the chip | ⚠ Hardware | ✓ Yes, via lab repair |
| Severe wear (worn-out cells) | Heavily used NAND cells lose the ability to reliably hold a charge after many write cycles | ⚠ Hardware, gradual | ✓ Often, degrees vary |
Controller Failure vs. a Bad NAND Die
EnlargeEvery recovery starts with the same question: is this a controller problem or a NAND-die problem? A quick test narrows it down — try the device on a second computer or a different port or cable. If it’s recognized intermittently, or works briefly before dropping out, that points to a controller or firmware issue rather than dead memory, since a marginal controller can sometimes limp through the handshake under different conditions. If the device never registers on anything, shows zero capacity, runs hot, or makes repeated connect-disconnect sounds, treat it as hardware failure and stop using it.
Controller failure is by far the more common and more recoverable pattern: the NAND die is intact, but the translator in front of it is dead. On a USB drive or SD card, recovery bypasses the controller entirely, either through direct access points on the board or by lifting the memory chip off and reading it on a specialized programmer — a true chip-off recovery. A failing NAND die itself (cells that have physically worn out or been damaged by heat or moisture) is a harder case, but even then partial or full recovery is often possible, since flash memory degrades in patches rather than failing all at once. A bad NAND die usually looks different from a dead controller: the drive is still detected but throws read errors, or its capacity shrinks over weeks. A dead controller is silent from the first second.
Detected, Recognized, Mounted: What Each Word Means
People use “not detected,” “not recognized” and “not mounted” as if they were one problem. They are three stages, and the stage where your drive stops tells you what broke, whether a NAND flash drive is not mounted or never shows up at all.
| Where Your Drive Stops Tells You What Broke | ||
|---|---|---|
| What you see | What it usually means | What to do |
| Not detected: no sound, no new entry in Device Manager or Disk Utility | Power, connector or controller is dead, so the computer never hears the device | Try one other computer, then stop and get an evaluation |
| Detected, not recognized: an “Unknown USB Device” or generic name, but no drive | The controller is alive but cannot present its storage; the memory is usually intact | Do not format or run repair tools |
| Detected, 0 bytes or “No Media” | The controller answers but cannot reach or map the memory | Same as above (see the next section) |
| Recognized, not mounted: right size, no drive letter, or a RAW volume | Usually a file-system problem, not a dead controller | Do not format; stop and ask before any repair |
The same words show up in tools. Some repair and flashing tools print “error NAND flash was not detected” when they ask the controller for the memory chip’s ID and get no answer, the same silence your operating system gets. Windows has its own error codes for these stages, and the related guides at the end of this page cover them.
Detected, but 0 Bytes or “No Media”
A drive that shows zero capacity, or “No Media” in Disk Management, is the most confusing case, because the computer clearly sees something. What it sees is the controller. The controller answers over USB, but it cannot reach its memory, or it cannot read its own map of where your files sit, so it reports an empty disk. The files are usually still in the NAND chip. The memory did not lose them; the controller lost the way to them.
Windows may list such a drive under a generic name that comes from the controller itself, for example “NAND USB2Disk USB Device.” That name only says which kind of controller answered. It is not a brand label, and it does not mean the memory is blank. Do not format, initialize or run CHKDSK, and do not run a mass-production or “repair” tool, because those can rewrite the controller’s tables or erase the memory. Try one other computer and port, then stop. A flash drive stuck at 0 bytes on a second computer is a lab case, and a free evaluation tells you which kind.
Which Devices This Affects — SSDs, USB Drives, SD Cards & Phones
EnlargeNAND flash sits inside far more devices than people realize, and “not detected” looks slightly different on each one. An SSD (SATA or NVMe) that stops showing up in BIOS or Disk Management, a USB flash drive that Windows or macOS can’t see at all, an SD or microSD card a camera or card reader refuses to read, and a smartphone data recovery that won’t boot past a logo screen because its internal NAND storage can’t be reached are all variations of the same underlying failure. Slim, sealed “monolith” NAND packages — common in compact USB-C drives and many phones — complicate DIY diagnosis further, since there’s no separate, socketed chip to inspect; recovery on these requires reading directly through test points on the package itself.
EnlargeOn a USB stick or SD card the controller and the memory often share one thin board, so a single crack or a bent plug can silence both at once. On an SSD the controller is a separate, larger chip with several memory chips beside it. That is why one failed part can make a whole device look dead while the files stay untouched. The same pattern shows up across every major brand of NAND-based storage, because Samsung, Western Digital, SanDisk, Kingston, Lexar, Seagate and ADATA devices all use the same controller-plus-NAND design. The logo on the case does not change the cause, and a device that Windows, macOS or a phone cannot see is almost never a wiped chip.
Not detected in BIOS, Disk Management, or File Explorer · shows as an “unknown device” · reports the wrong capacity · disconnects and reconnects repeatedly · feels hot to the touch or shows visible corrosion. Any one of these on its own is a hardware warning sign — stop using the device and have it evaluated rather than waiting for a second one to appear.
NAND Flash Myths — What’s True and What Isn’t
Myth: if NAND flash isn’t detected, the data is permanently gone. This is the single most common misconception we hear, and it’s wrong far more often than it’s right. NAND cells retain their charge without power indefinitely (barring extreme age or heat); “not detected” describes a communication failure, not an erasure. On USB drives and SD cards, chip-off reads the memory directly, sidestepping whatever failed in front of it.
Myth: water damage always destroys the NAND chip. Water is far more likely to corrode the board, connector, or controller than to penetrate the sealed NAND package itself. Devices that were quickly dried and never powered back on after exposure recover at meaningfully higher rates than ones that were repeatedly plugged in to “test if it still works.”
Myth: recovery software can fix a device that isn’t detected. Recovery software needs the operating system to see the drive in the first place; if NAND flash is not detected at the OS level, no scan-based tool can reach it, and running one repeatedly on an unstable device adds risk rather than removing it.
NAND Flash Not Detected: What to Do Next
EnlargeRun this quick decision check the moment a NAND-based device goes undetected. Step 1: Does it show up on any computer, port, or cable at all? If nothing sees it anywhere, treat it as hardware failure. Step 2: Does it disconnect repeatedly, run hot, or make unusual sounds? Stop using it immediately — every extra power cycle risks further damage. Step 3: Is there any visible physical damage — a cracked board, bent connector, or water exposure? That’s a lab case from the start. Step 4: Did it work moments ago and simply vanish with no physical cause? That points to controller or firmware failure — often still recoverable, but not something software troubleshooting fixes.
Nothing you can safely do at home changes whether the memory still holds your files. What changes the outcome is what happens next: more power cycles, repeated recovery-software scans or a DIY controller swap can turn a recoverable controller failure into a much harder case. An SSD not detected in BIOS gets the same advice as a USB drive or SD card: stop, don’t self-repair, and get an evaluation.
Can NAND Flash Be Repaired or Fixed?
It depends on what “fixed” means. Getting your files back and getting the drive working again are two different jobs, and the second can destroy the first. Free “NAND repair” tools, mass-production tools and firmware flashers rewrite the controller’s tables and can erase the memory while they do it. Heating a board, baking it or reflowing it with a heat gun does not repair a memory chip; it can crack solder joints and turn a readable chip into a dead one. Worn-out cells cannot be repaired at all, only read while they still hold a charge.
What a lab can do is get past the failed part. A broken connector or trace is repaired so the chip can be read. On a USB drive or SD card, a dead controller is bypassed by reading the memory chip directly. On an SSD, we identify the controller first, then repair the original board, move the controller and memory together onto a donor board, or read the memory directly when the controller does not encrypt. Once the files are safe on another drive, replacing the old one is cheap. Professional recovery, described below, follows those same steps.
Who to Call: What Happens During Professional NAND Recovery
EnlargeWhen a device with undetected NAND flash arrives at the lab, the first step is diagnosis — determining exactly which layer failed: connector, controller, firmware, or the NAND die itself. Connector and board-level faults get micro-repair; on USB drives and SD cards a failed controller gets bypassed with direct NAND access, and on SSDs and phones we identify the controller or processor first.
In a true chip-off recovery, the NAND memory chip is desoldered from the board and read raw on a specialized programmer, independent of the dead controller. The raw data that comes off the chip is scrambled by design — wear-leveling and error-correction algorithms spread and encode data across the memory — so it’s then reconstructed and reassembled into a usable disk image, restoring the original file structure. Monolith packages (sealed single-chip designs in slim USB-C drives and similar devices) are read through exposed test points rather than a removable chip. Every recovery works from the original device, and most NAND flash not detected cases resolve in 1–3 business days under eProvided’s “No Data, No Data Recovery Fee” policy — you only pay when your files actually come back.
For the full process, see our NAND flash recovery page. A NAND failure, whether controller, firmware or physical, is not the same thing as recovery being impossible.
Real Cases: What “Not Detected” Looked Like for These Customers
Six cases from our own records, 2018 to 2025. Each customer wrote what follows when they filled out our online form; we corrected the spelling and removed all names and contact details. Our case record shows a successful recovery in all six. Every case is different, and no lab can promise a result.
M.2 SSD that no adapter or slot could see, August 2025
“I have an M.2 SATA SSD and I had a computer go bad. But when I try to get onto the drive with another computer, with both an adapter and a motherboard M.2 port, it won’t see it, and the adapter says it can’t read it because of a fault. So I don’t know if it is dead. It does warm up like I would expect.”
Two paths, both silent: a controller-side failure, with power still reaching the drive. Our case record shows the data came back. An SSD that is not detected depends on its own controller, so we treat it differently from a USB stick.
MicroSD card that just stopped working in a phone, December 2022
“Micro SD card, was in the phone and just stopped working. Laptop does not recognize it either, Windows 10 cannot fix it. Has photos and videos. Last 30 days of content would be nice to recover; older files are at backup.”
The customer named what mattered: the files no backup had. Our case record shows a successful recovery. A microSD card that is not recognized in two devices is a classic controller-side failure.
USB drive with a cracked controller, March 2022
“USB got damaged physically, the controller had a crack in it. Had a tech try and look at it from work with no luck, and not sure if anything can be done, but thought I’d give y’all a try. Was wondering if y’all could move the NAND from this USB into a working USB to recover the data.”
A cracked controller leaves the memory chip intact. Moving the chip to another stick does not work alone, because the new controller does not know how the old one arranged the data. Our case record shows a successful recovery.
SD card after the camera battery came out, July 2020
“The battery came out when the camera was trying to review pictures. Now the SD card is not recognized by the camera or multiple computers. There are 1000+ pictures and videos on the card.”
Power cut while a card is in use can scramble the controller’s map, and the pictures stay in the chip. Our case record shows a successful recovery. If your memory card is not recognized, take it out of the camera and stop.
Four-gigabyte flash drive full of teaching documents, July 2020
“My wife has a 4 gb flash drive that suddenly became unrecognizable on our home computers. It has documents on it from when she taught (now retired).”
Small old drives hold years of work. Our case record shows a successful recovery; capacity made no difference. For a flash drive that became unrecognizable, the same first steps apply.
Flash drive that dropped out for an hour, then vanished, March 2018
“A flash drive containing almost 256 gb of data began intermittently disconnecting from the computer and then, about 1 hour later, ceased being detected by any device I connected it to. I need everything that can be recovered, and the file types ran the gamut from MP3 to MP4 to JPG to PDF to AutoCAD, RTF and others.”
The on-and-off hour is the warning stage. Each replug asks the controller to start again, so try once on a second computer, then stop. Our case record shows a successful recovery.
How to Prevent NAND Flash Failures
A power surge or a dropped phone happens however careful you are, but a few habits lower the odds. Use a surge protector or a UPS for desktop SSDs. Use “Safely Remove Hardware” on USB drives, because a pull mid-write is the power loss that corrupts firmware. Do not let flash storage sit completely full for long. Above all, keep a second, independent backup of anything irreplaceable, because no flash device is immune to controller failure.
What Our Customers Say
Frequently Asked Questions
That same chip-level read is what let us pull NASA Helios mission data off a module recovered from the Pacific after the aircraft broke apart. Government archive or a silent SSD at home, the diagnostic starts the same way — see our highest-stakes recovery work.
Recover Data from Undetected NAND Flash
SSD, USB drive, SD card, or phone gone silent? Our engineers will tell you exactly what’s recoverable — free, no obligation, completely confidential.
Start My Free NAND Recovery Evaluationor call (866) 857-5950 now
Related Recovery Services
Whatever device the undetected NAND flash lives inside, these recovery services get the data back:
