Searching for WD 640Gb - WD6400AAKS-65A7B2 working PCB

[Kleyon]

Hi everyone,

Please consider helping me, I'm searching for a working and flashed PCB for my HDD, firmware on current one is erased by a bad manipulation !

My drive is a Western Digital Caviar Blue 640Gb : WD6400AAKS-65A7B2, here is the informations on the HDD :

S/N : WMASY6075590
P/N : 5189-2868 DFP
CT : 2ADED023HX140C

WWN : 50014EE0ABB6B248
DATE : 15 JAN 2009
DCM : DARNHTJCB

And here the information on the PCB :

2060-701590-000 REV A (directly on the PCB)
2061 - 701590 - L00 AC XW 7G09 KLR6 8 0006290 9296 (on a sticker)

I don't have materials to flash the chip, so I'm searching for an identical PCB already flashed for replacing this one ! It's been many mounths I can't use it and it is the operating drive of one of my computers !

So please consider helping me !

[dmarques]

Hi,

I think it's not so easy as that.
What do you mean flashed PCB?

[Kleyon]

By "flashed PCB" I mean including firmware on it ! Because I can find the same PCB but not flashed ! And I don't have the money for that expensive material.

So I'm searching a PCB already flashed (means including firmware) or someone who can flash it (maybe I should have said program !)

[dmarques]

All PCB's have already the ROM on it (that's what you mean by flash), but the problem is the version.

Do you know the original version anyway?

[Kleyon]

All PCB's have the ROM (chip) but not allways the firmware !

I supposed my HDD have this kind of information, because seems like 65A7B2 refer to the firmware version.

EDIT : What I've found on the net concerning firmware version : WD6400AAKS-65A7B2 FIRMWARE : 1.03B01

[dmarques]

No, you're making some confusion.
Let me try to help you.

Your drive is a WD6400AAKS-65A7B2.
The latest part: 65A7B2 refers to vendor, family and version.

Firmware is stored mostly on the drive platers, and not on PCB. On PCB you have ROM, that may contain some unique information to start the drive. So to swap a PCB, you have 2 ways, swap the ROM into the new PCB, or else copy the ROM contents and save it into a new PCB. But in any of the cases, first you need to know what's your ROM version.

There's also a copy of ROM stored on the platers, that it's possible to access in order to rebuild ROM.

[Kleyon]

I'm not sure understanding ! I'll explain to you : I was on my way to reflash a Scorpio Blue 1200Gb using his original firmware (because I was using a modified one), but when I done that, the program I was using has flashed the bad drive ! Flashing my WD640Gb instead ! So since my drive isn't recognized anymore ! I can't access it and of course it won't works as it !

Concerning the firmware, the information I pasted are from LeDisqueDur who was pretending selling the PCB including firmware, but when I orderd it, he simply tells me that he doesn't have the firmware for it and canceled my order (erasing the product from his website too !).

I've found it on HDDGuru : http://files.hddguru.com/download/Non-P ... /ATLANTIS/

Please, can you explain me what I need to do in that case ?!

Last edited by Kleyon on February 23rd, 2012, 8:08, edited 1 time in total.

[dmarques]

What's your goal, recover data or fix the drive?

[Kleyon]

Fix the drive would be best, but recovering data is the most important thing ! Sorry I've edited my previous message ! It wasn't the 250Gb Scorpio drive, but a 120Gb one.

[dmarques]

If your goal is to recover data, with what you've done, the drive needs to be checked by a pro, someone who has tools and knowledge to do so, because right now I think it's far from a DIY job.

I think who might recover the data, might fix it also.

[Kleyon]

Ok thanks for information, did you know such a professional please ? Hope this will not be a 4 numbers cost :/

[Kleyon]

Sorry to make a double post, but I have some new informations ! Seems like I only need to reflash sectors 16-22 of my drive (sectors that was previously badly flashed !).

I want to try to make it using the same program that make the mistake, but please can you tell me if I can find a file for that in : WDCWD6400AAKS-65A7B2-1.03B01-WD-WCASY8539136.7z found here : http://files.hddguru.com/download/Non-P ... /ATLANTIS/

This programe use BIN file for flashing.

[dmarques]

I don't know anyone personally in France.

Just in Belgium, Switzerland, Spain, Portugal (me), Germany, etc etc.

[Kleyon]

Depending on final cost, but if I have to ship it I will !

[fzabkar]

Sorry to make a double post, but I have some new informations ! Seems like I only need to reflash sectors 16-22 of my drive (sectors that was previously badly flashed !).

I want to try to make it using the same program that make the mistake ...

Which program? Is it a secret?

[fzabkar]

Sorry to make a double post, but I have some new informations ! Seems like I only need to reflash sectors 16-22 of my drive (sectors that was previously badly flashed !).

I want to try to make it using the same program that make the mistake, but please can you tell me if I can find a file for that in : WDCWD6400AAKS-65A7B2-1.03B01-WD-WCASY8539136.7z found here : http://files.hddguru.com/download/Non-P ... /ATLANTIS/

This programe use BIN file for flashing.

It sounds like you used HddHackr to modify the firmware in a 120GB WD drive to make it look like the original drive in an Xbox. Sectors 16-22 are in the user area of the drive — they are not part of the firmware. What actually happens is that HddHackr modifies a particular firmware module (MOD 02) so that the WD drive then identifies itself as the original Xbox drive, eg Fujitsu. If you want to try a DIY recovery using freeware, then the first thing you need to do is to determine whether you can read MOD 02 using MHDD. I don't know whether this is possible with the drive is in its present state, but try to follow the procedure in the following thread:

unlocking-ata-password-for-western-digital-t8374-220.html

If you can retrieve the BIN files, then we may be able to do something.

[Kleyon]

Man ! Many thanks ! You understood everything ! It's exactly what happened ! (In fact I wasn't on my way to modify it as a Fujitsu drive, but on my way to restore it as original WD drive, and that's the undo.bin corresponding to sectotrs 16-22 of my WD Scorpio Blue 120Gb that has been flashed on my WD640Gb :/)

I don' t have time to see that by now, but I will look at it and give it a try as soon as possible, then I will give you a feedback !

It wasn't a secret concerning the program, just the fact I was thinking it was not a program known by this forum's users !

So you confirm me what I was thinking : maybe if I can have the BIN files concerning sectors 16-22 I will be able to restore it !

You explained me more details concerning Hddhackr, many thanks again ! And thanks for telling me wich programs I should use !

[fzabkar]

You have misunderstood me in regard to sectors 16-22. Those sectors are in the user area — they are not firmware sectors.

HDDSS.BIN contains a backup of LBAs 16 -> 22 on the original Xbox drive.

UNDO.BIN contains a backup of the original WD firmware module 0D plus module 02.

You need to restore the original MOD 0D and MOD 02 of your WD6400AAKS drive, not sectors 16-22. MOD 02 is located in the hidden System Area on the platters, whereas MOD 0D is located near the end of the "ROM" on the PCB.

BTW, here is my understanding of how HddHackr works:
http://www.users.on.net/~fzabkar/HDD/Hd ... lysis.html

I don't have any firsthand experience with HddHackr, so there may be errors.

[Kleyon]

Hummm ok ! But I hardly understand how I could restore modules 0D and 02 because Hddhackr has flashed them !

I repeat myself, but this kind of dump aren't on that archive ? : WDCWD6400AAKS-65A7B2-1.03B01-WD-WCASY8539136.7z found here : http://files.hddguru.com/download/Non-P ... /ATLANTIS/

I will try it soon anyway (like you tell me to do). Thanks again for spending time on it and trying to understand how HDDhackr works and what happened !

[fzabkar]

The MODs in those archives have their own version numbers (not the drive's firmware version). Therefore I don't know if a particular MOD will be a suitable replacement.

In any case, the technique that I propose to use to write the MOD is the same technique that will be used to read the MOD. So if you can't read it, then you won't be able to write it.

I propose to try reading MODs 109 and 802F, and then use their contents to reconstruct MODs 02 and 0D.