HDD GURU FORUMS

Guys, got this USB drive.

Controller: 20-82-00188-2
Memory IC: STDNLMCHSM-8192 (ID: 45xCEx9Ax83 AEx13x0Bx01).

Does anybody have an experience/success or know/have datasheet for this device?

Thank you.

Pretty sure this is a 16bit nand chip.

some of the early sandisks are encrypted. But the ones that arent can have fairly complex mix's such as 3 block pairs, rotating pages in the block, mixing data between blocks etc. Also most need some divide on the markers.

What tools do you have for flash?

Datasheets for controllers dont exist, and havent seen many useful SanDisk Nand datasheets either.

Thank you for reply.

HaQue wrote:Pretty sure this is a 16bit nand chip.

Exactly.

HaQue wrote:some of the early sandisks are encrypted

It is optional and user didn't use this option.

HaQue wrote:But the ones that arent can have fairly complex mix's such as 3 block pairs, rotating pages in the block, mixing data between blocks etc. Also most need some divide on the markers.

You are talking about assembling operations, my main question is about memory chip configuration, I can't read the chip correctly.

HaQue wrote:What tools do you have for flash?

PC3000 Flash. And by your terminology, probably, you are using SC FE, but they do not have a config as well. So may be some guy with a different tools will help, I'm not sure.

HaQue wrote:Datasheets for controllers dont exist, and havent seen many useful SanDisk Nand datasheets either.

It exists, but with NDA it is very complicated to get this, I have no such "contacts"

Martin wrote:

HaQue wrote:Pretty sure this is a 16bit nand chip.

Exactly.

Have you tried 16-8 configuration? where chip is wired as 16-bit but read as 8?
Also forgot to ask, does it ID correctly and what is the issue you are having, bit errors, bad read or other?

Martin wrote:

HaQue wrote:some of the early sandisks are encrypted

It is optional and user didn't use this option.

No, I mean natively by controller and transparent to user.
Example, some 20-82-00162-1's are encrypted, but I have had some not, all 20-82-00162-2's I have in my database are. I have one 20-99-00128-3 that is encrypted and one that isn't, but everything else is exactly same..chip, pcb.

You can tell by looking at hex dump. From memory it looks like a 64 bytes from offset 0x0 then 00's till encrypted data, but I can check exactly if you need. It may not be encryption, but some kind of dynamic XOR or other algo, but I don't think it has ever been identified/reversed.

Martin wrote:

HaQue wrote:But the ones that arent can have fairly complex mix's such as 3 block pairs, rotating pages in the block, mixing data between blocks etc. Also most need some divide on the markers.

You are talking about assembling operations, my main question is about memory chip configuration, I can't read the chip correctly.

Are you sure of the number, and it isn't SDTN instead? I think the ID should be 45xCEx9AxC3 maybe you have a dirty/broken pin and not ID correctly?

Martin wrote:

HaQue wrote:What tools do you have for flash?

PC3000 Flash. And by your terminology, probably, you are using SC FE, but they do not have a config as well. So may be some guy with a different tools will help, I'm not sure.

HaQue wrote:Datasheets for controllers dont exist, and havent seen many useful SanDisk Nand datasheets either.

It exists, but with NDA it is very complicated to get this, I have no such "contacts"

I know! SanDisk, when they finally responded told me data recovery was not a valid reason for getting access. For Micron NDA, I had to talk to a Micron person for Micron/Spectek, but eventually they were reasonable. SanDisk, for having so much clout and input in Flash are exceptionally non-helpful, and pretty much couldn't give a toss about standards either.
I am using SC terminology but it is similar in VNR, VNR has this chip config. Depending on where you are, you could get a read from someone. lots of VNR people in Poland for example.

20-82-00188-1 is not encrypted, but I don't know about 20-82-00188-2

and as you know in flash and or SanDisk, there is no rules

I've try this as well. Chip name and ID are correct.

I'm not sure for 100%, but this controller uses encryption as option, so not only hardware encryption.

I can't read chip correctly, there is a problem.

Martin wrote:I've try this as well. Chip name and ID are correct.

I'm not sure for 100%, but this controller uses encryption as option, so not only hardware encryption.

I can't read chip correctly, there is a problem.

Martin ,
Please invest in a second tool ,This really helps in getting to the root of these kind of cases .I have PC3K flash i am buying
vnr soon

Investment cannot go before understanding of advantages.

@Martin: Main advantage of VNR is that it read chip correctly and if you don't have correct config you can create one by your own for it in 10 minutes..... we got many situations that need to use VNR for reading and then putting dump into PC3000 for making Dynamic XOR for example since PC3000 itself cannot read NAND correctly (shifts in pages, moved from left to right, wrong ID detection... especially with microSD Cards)

Martin wrote:Investment cannot go before understanding of advantages.

Well,
What My Senior Haque Tells me is that it helps to understand the whole recovery scenario correctly and hence you start understanding the case and controller/nand better

Martin wrote:I've try this as well. Chip name and ID are correct.
I can't read chip correctly, there is a problem.

You 100% sure number is STDNLMCHSM-8192 ? As I havent seen any with that prefix. If so maybe a new breed of chips. I have big problems reading SDTNSCAMA-008G, maybe it is same issue. I havent found a recent SanDisk Part Decoder, though not looked all that hard yet.

could you possibly provide photos of each side of PCB?

Maybe it is a fake.

Bolo wrote:@Martin: Main advantage of VNR is that it read chip correctly and if you don't have correct config you can create one by your own for it in 10 minutes..... we got many situations that need to use VNR for reading and then putting dump into PC3000 for making Dynamic XOR for example since PC3000 itself cannot read NAND correctly (shifts in pages, moved from left to right, wrong ID detection... especially with microSD Cards)

PC3000 Flash allows to create config manually as well. I was trying to do...

HaQue wrote:

Martin wrote:I've try this as well. Chip name and ID are correct.
I can't read chip correctly, there is a problem.

You 100% sure number is STDNLMCHSM-8192 ?

Of course you are right, SDTNLMCHSM-8192. Unfortunally it makes small changes in situation.