Switch to full style
Discussions related to Visual NAND Reconstructor tool
Post a reply

Bad NAND? Or bad read?

September 30th, 2020, 6:41

For the sake of learning, I ripped open a 16GB CF-card which has 4x FT32G08UCT1-B7 and Phison PS3016-P9 on it. When trying to read the ID of the chips I got basically "00000000" or "2121212121" or similiar. There's no exact match for the chip in the db but FT32G08UCM1-15 seems to be closest so I used that one. Dumped all four chips without any problem.

However, I do run into problems when I check the dumps in bitmap viewer. Image 0 looks like this:

Screenshot_4.png


Image 2 looks like this:

Screenshot_3.png



Is Image 0 a dead chip, or has there been some error during the dump?

Image 2 shows a lot of bit-errors in the SA. Is that because of a bad dump?


(VNR 2.4)

Re: Bad NAND? Or bad read?

September 30th, 2020, 12:31

Hi ,
Please Post Post Photos Of Device And NAND Flash ,You Need To Update Version Of VNR to 3.9 ,Speak To Katarina Please .You Said 4 Chips Or 2 Chips ? . Are There 2 Parts Per Each 4x Chips or 4x Parts Per 2x Chips .

PS : Its Very Interesting To See This Controller ,I Have Always Seen SM2236 Under Its Own Name Or Sandisk Name

Re: Bad NAND? Or bad read?

October 1st, 2020, 7:22

It's four physical chips, all marked FT32G08UCT1-B7.

And I cannot upgrade to VNR 3.x, I'm kind of stuck with 2.4.

Re: Bad NAND? Or bad read?

October 2nd, 2020, 0:33

Google suggests that these are remarked by Kingston. The 64Gbit versions are claimed by some to be Toshiba chips.

https://www.insidegadgets.com/2013/07/02/inside-the-kingston-60gb-ssdnow/
https://proclockers.com/review/kingston-ssdnow-v300-128gb-solid-state-drive-review/
Post a reply