And the photo on the right shows the memory stick after the 48 pins (2×24 pins) nand was removed. The 2 photos on the left and the middle show the module before the nand was removed. It was auto verified being okay! Which confirmed the nand was still fine! Next the screenshot from the RT809H with verified good nand.įollowing photos show the defect 4GB Sandisk memory stick with bad FC8708 controller. And I checked and read the entire chip with the RT809H in a few seconds and saved the entire 4GB data file as bin file to my computer as a precaution in case the chip would fail later on.
Of course without removing any of the other components on the other side of the board. The nand was easily removed with hot air by just turning the chip downwards until it fell off the board without any real force. Below a photo of this controller and the nand. These controllers not only control the communication between USB and the Nand, but also the 5V voltage conversion to the voltage that the nand requires (1.8V or higher). Now that we know the most important facts we will start with recovering all files from a now 4GB defect Sandisk stick with a bad FC8708 (square 48 pins type) controller chip. But we need to take special action to recover back the data that is stored on it in its original format. These USB memory chips are mostly 2 x 24 pins (48 pins_ 8 or 16 bit) nands or newer bga chips. Although the nand and the data that was stored on it could be gone too, in most cases the nand or nands (if larger sticks are involved) are still intact.There is a good Russian site that knows all about every stick on the market but it takes a lot of reading to comprehend all that is written on that site about recovering.
AU6987HL MPTOOL CODE
We only see binary numbers or hex code we can’t interpret without knowing how the controller arranged that data.
And memory stick data capacity keeps on growing bigger by the day with no end in sight. Today’s USB memory sticks have made a lot of media obsolete, including the old but trusted floppy drive.