good evening ;

i have this wd800jd-00lsa0 , pcb # 2060-701335-005 rev a
which has a burned PCB , simple pcb swap with the same model had made the drive spins ok , but detected as


wdc rom model UNICORN
sn WDC-ROM SN:xyz

in bios , after swaping the rom , drive recognised just it was before doing the swap .
swapped the rom to another 2 diff boards wit the same pcb# and the drive just read the same .

what is the problem ?
is this a drive reading from pcb rom only and not from SA ?

thank you

If drive isn't clicking you will need tools to check and fix the SA.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

edited out

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Had one of these same issue. Finally got it working with donor ROM. What tools do you have? If using SD tools find a donor ROM and write to the PCB and see if you can make it work. I had to use 4 or 5 different donor ROM files before I got one that worked good for me. Also if this one is giving XYZ check the forum on SD for this repair. I know they had a case study on this one before. Look it up on their forum and if not on their forum go to their blog and search for this one. Should help you out on this. Good luck.

_________________
Iorana Haraharaini

Download this free tool :

http://www.nazyura.newmail.ru/Mavrik.zip

And run it on your drive.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I know this person and he has the tools from SD already. He does not need this one. He just needs to find the case study and follow this one and he can get the data off the drive. This one is well documented from SD on forum and case study.

_________________
Iorana Haraharaini

Last time i spoke with him (some days ago) ge only had DDI and TLL adaptor.

That is why he wasn't able to load firmware to the drive on this thread :

st3808110as-broken-t25550.html

(No tools) - Unless he aquired a WD tool from Salvation and i don't know, but i really don't think so.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

thank you all for your help .

unfortunatly , i donut have SD tools right now , and llooking to get pc3000 UDMA soon .
i am trying to get around this problem "thanks to all people who is contacting me"

thank you again

Ok !
Do the following :
Connect a good "test drive" to the pc by sata, dont use usb, and using you tool detect the drive and note the port it uses.
Shut down pc and plug damage drive there.
Dont plug power to damage drive, just the sata cable.
Start computer and tool.
Make sure that tool is on the same port as drive.
Power on the drive, plug power cable.
Use tool to check modules.
Use Marvell option at start, not royl.
Good luck !
If you want post log here and i will try to help !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

And next time instead of swapping the ROM chip, run the utility, place bad pcb on the defined port without drive, just the Pcb. Put power on the pcb, wait for it to report rdy, go to action, flash operations and read the rom. Plug the new pcb and do the same thing but this time, write ROM.
If you dont have original pcb or if its damaged, place compatible pcb on drive and do the same, but this time on flash operations use repair and it will fetch data from sa to flash the ROM.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

good evening ;

after testing the modules (I/O >> check all by id) i found out that those have defects .

17 - FM_ERR_COMPAT
4C - FM_ERR_COMPAT
1C - FM_ERR_COMPAT
1B - FM_ERR_COMPAT
19 - FM_ERR_COMPAT
1E - FM_ERR_COMPAT
11 - FM_ERR_COMPAT
2F - FM_ERR_COMPAT
15 - FM_ERR_COMPAT

my drive is
wmam9u135722
wd800jd-00lsa0

and i did find 1 similar FW located here
http://www.datadonor.net/HD%20Western%2 ... 00LSA0.zip

extracted and now in the module window , i do right click on the bad modul >> I/O >> write multi selected and i choose the same module from the donor downloaded FW "with extension .mod" to get
No Module: 0 in Map

a friend has sent me his backup ".rpm" and each time i select replace my module by the donor one , i get
Write Module: **

where ** is the module name

after finishing i repower the drive and re do all the previous to find that the bad modules are still there !


can any 1 of these drive's modules replace the bad onces on my drive ?


thank you

Maybe Bad sectors on SA ?
Maybe the drive is write protected ?

Try something, using the "dump" on a good module, change (with hex editor) a bit on the model name, and write the module back to the drive. Check if it wrote ot correctly or not.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Can you post a screeshot of the module list with the checking marks on the bads ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

hello again , i am attaching photos .

This might sound stupid but maybe there are bad sectors in SA preventing you from writting modules to the same location where the damaged ones are.

Maybe someone can confirm if those modules are important or not.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I don't like that XYZ at the ROM version.
Maybe you should start by "read" rom to backup it and then "write" ROM from those firmware packs that you fetch on the net. Try to see if it identify with a correct version number. If so, try to "Repair" that will re-gen the ROM from modules. If it doesn't work maybe you will have to try lots of different ROMs untill you find some that work ???
I'm lost too, i would love to help you better but i don't have many experience with this .... I'm just starting to "play" with modules on WD ..... And don't forget that there modules that are exclusive for the drive, like defect list .... and you can't just copy modules from other drive on it.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I can see ERR and ABRT when you try to write module back .....
Maybe it's indeed BAD SECTOR on that part of the drive.
Maybe a hot swap will help you gain access to the data ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Upsssss .... Spildit made a mistake.

Regen the rom is for ROYL, where you fetch info on the modules to put on the ROM to make it compatible with SA, Adaptive, whatever ....

You have Marvel MCU ....

Try to use diferent ROMs and see if one of them works without the XYZ at the end of the firmware number.....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I would like to suggest that you go to the SD Blog site and search on WD drives case studies. In there is a good case study for why this drive has XYZ and how it can be repaired. You might want to read this one before offering a lot more help on this to the guy. Understand you need SD WD Doctor tool to do it but you will get the idea on this one.

_________________
Iorana Haraharaini

XYZ is a symptom of some failure, not a fault in itself. Your problem is somewhere else. Assuming ROM is OK and is transferred to known good compatible PCB, and no other faults with the disk, then you should reach ID, which you dont, meaning you very likely have other problem elsewhere.