HDD GURU FORUMS

I have just had two of these in for evaluation, both these reacted in exactly the same way, why?

I put the card into a reader and started R-Studio for a general look. The card could be seen so I saved off the data asap. About half way through the recovery the card stopped reading. I have not been able to get into either card since. Is this a common faulty with this card. Its strange as both cards from different clients did exactly the same thing.

Personally I think many MicroSD failures are from the flexing during insertion breaking a bond or trace internally. I have seen quite a number of this but mainly from Kingston. I would be hesitant to try and link any 2 cases as these cards are produced in the MILLIONS... the chances of the problem being from the same batch, or the same fault.. *unless* it is a firmware issue and is the same controller/NAND/Firmware combo.. is VERY low.

The multitude of controllers and NANDs and combinations are fairly high. Samsung *may* be different if the whole 3 parts of the device (PCB/Controller/NAND) are Samsung, and there is a chance I suppose of the issue being related.. but finding the REAL cause I think is a wild goose chase.

Much better to try and read NAND, if you have pinout and can solve in a timely fashion... then do so, else decline the job with an explanation.

trying to relate the issues is like saying " I started to drive my car then it stopped and wouldn't start" There are a multitude of things this could be, but in the flash world commonly it is either working or not, and the core culprits are very hard to find. Most people that say "oh this is the cause..XYZ.. are guessing and unless proof is shown such as xray, firmware decompilation or broken circuit pictures.. I would be sceptical.