HDD GURU FORUMS

Does anyone know pinout for this chip?



Thank you.

Can't you work it out from the TSOP-48 pinout, assuming it follows the ONFI standard?

Wouldn't it have been better to leave the chip in place and wire up a TSOP-48 adapter?

Its' BGA-63. 10 seconds search at google for pinout.

you would usually add a pic of the other side of the chip as well. or at least the Mark Code

fzabkar wrote:Can't you work it out from the TSOP-48 pinout, assuming it follows the ONFI standard?

Yes I worked it out of TSOP-48 pinout. Here is it:

fzabkar wrote:Wouldn't it have been better to leave the chip in place and wire up a TSOP-48 adapter?

No because it has a COB controller. Picture bellow.

arvika wrote:Its' BGA-63. 10 seconds search at google for pinout.

Thank you arvika. I never had BGA-63. I found pinout in ONFI file but pinout is upside down which kind of confused me.

HaQue wrote:you would usually add a pic of the other side of the chip as well. or at least the Mark Code

that's useful too, but I really meant the NAND chip. Sometimes with unfamiliar chips, if you search the part number/mark Code, you will find a datasheet or other info.

Anyway, looks like you are on the way now. Good Luck with the recovery. Please post back with the NAND ID, and what the controller turns out to be if possible!

HaQue wrote:that's useful too, but I really meant the NAND chip. Sometimes with unfamiliar chips, if you search the part number/mark Code, you will find a datasheet or other info.

Anyway, looks like you are on the way now. Good Luck with the recovery. Please post back with the NAND ID, and what the controller turns out to be if possible!

Chip is Samsung K9F1208R0B.

Datasheet: https://datasheetspdf.com/pdf-file/2648 ... F1208R0B/1



Chip ID is: EC 36 A5 C0



Pretty much game over, because Acelab does not have this chip and I don't know how to add it.

MasterT wrote:Pretty much game over, because Acelab does not have this chip and I don't know how to add it.

If you are comfortable, there are folks here who can help remotely (for pay, of course).
Asking for help may do the trick.

that's the wrong datasheet, here is the correct one. ( yours may be close enough to figure it out though)


also this is a 1.8v chip (ace may have sorted this out for you - I don't know their reader)

you should be able to read it by using this as a starting point:

labtech wrote:

MasterT wrote:Pretty much game over, because Acelab does not have this chip and I don't know how to add it.

If you are comfortable, there are folks here who can help remotely (for pay, of course).
Asking for help may do the trick.

I know there is plenty of help available. Thing is flash recoveries are hard to sell in my area.

The small quote i gave to the customer he barely accepted. So there is no room for paid help.

In future cases where customers are willing to pay more and I need help I'll contact you. Thank you for understanding.

Besides I'm trying to learn how to do it myself.

HaQue wrote:that's the wrong datasheet, here is the correct one. ( yours may be close enough to figure it out though)

also this is a 1.8v chip (ace may have sorted this out for you - I don't know their reader).

I tried to add the chip myself with the help of the chip config print screen you attached and the datasheet. All It reads is FF FF. I'm not sure what reading algorithm should i use. Or I did something wrong.



Roman at Acelab said:

"Well, it's not a ONFI chip, and not a JDEC.

It's internal Samsung development. This chip is very-very tricky - it reads all sectors by 3 commands;

Command 00 read first 256 bytes
Command 01 read second 256 bytes
Command 50 reads the rest 16 bytes

Command 00 - is a basic command for NAND reading, while commands 01 and 50 are optional and belongs only for this chip. They are not in used and usually you can meet them in very old flash drive where the memory chip was even not a classic NAND Flash (something between NOR and NAND technology)

I'm afraid, existing tools can't read it."

do you have FE reader?

It is good that they provided that info for you. It isn't anything I have come across before. But what it tells me is that it IS possible to recover - with the right amount of work!