[keith]

(4385)

ID not in database. Will send TV details in skype

[keith]

Just wondering if there is any update on this one? Thanks

[Сергей]

i read zeros

i think there is problem with connection

may be chip have different id

[arvika]

This ID: 98 de 90 92 means that it is internal problem with some data signal (it is cutted / crack inside the card). Correct ID should be 98 de 98 92. This case is unrecoverable. You can little try heat the card but never help for me.

[jeremyb]

I must argue this point, while I think something is "wrong" I don't think the wires are cut.. I personally think the proper "read" mode hasn't been selected by software when the NAND chip is booted and it's stuck in purgatory. ie: the controller inside the NAND chip expects to be programmed by the external controller.

Reasons being..
#1 If you measure diode voltage across all rails the values are constant, so there is no breakage, lets say D0 -> | <- Controller, connection to D0 is cut, the value would be different as voltage passes through the controller to ground instead of NAND to ground.

#2 if you FORCE DDR mode you'll get data..

In NAND Reader goto

Conf->Options
Debug -> After Reset paste

Cmd 0x9c
 
Cmd 0x00
Addr 0x0 0x0 0x0 0x0 0x0
 
Cmd 0xef
Addr 0x80
Data 0x0 0x0 0x0 0x0
Wait
 
Cmd 00
Addr 0x80 0x0 0x0 0x0 0x40
 
Cmd 0xef
Addr 0x80
Data 0x0 0x0 0x0 0x0
 
Cmd 0xef
Addr 0x10
 
Cmd 0x9e
Wait

Now pick out the suspected cfg (eg: 98 de 98 92), make sure DDR is checked in Options->Chip..

Presto, data

[arvika]

Interesting. For example I have now case Sandisk MicroSD 16GB with similar problem, I get ID like 98 * a0 92 (I do not remember second byte). I use your method, and select manually chip ID: 45 4c a9 92, put info to Debug and set DDR and try read. But dump is usually empty, there is some data but it is trash. Interesting is that after i disconnect reader, close NR and connect again reader and run NR it shows me correct ID: 45 4c a9 92. But still trash in dump. Resistance on all Data signal is same.

Some time ago I have typical MicroSD card 4x6. One bank give good ID: 98 de 98 92 and was read, second bank give: 98 de 90 92 and can't read.

I will test this method on more cases.

[HDDRCVR]

I also have a similar situation I will report back. Maybe this thread can be moved to chat after.

[jeremyb]

FYI: Run this command on ANY Toshiba/SanDisk WL NAND and it will enable/force DDR. Saves a lot of time reading high capacity NAND (NON-DDR) chips.

Also weird is how sometimes on the first ID by the controller the NAND ID is 100% different (but valid) and the second ID is correct.

Also many thanks to Sergey for added Before Read & After Reset debug commands, it makes hunting for proprietary NAND commands much easier.

eg:
Prefix SLC Reads as
Cmd 0xa2