Hello to all of you

The board of the drive in subject is really much dead

I can't read the ROM neither through terminal

Unfortunately it is a board WITHOUT U12 so I have no info about ROM version.

I've tried many in my DB and from the hddguru stock

So if you kindly want to help providing the .bin ROM file, please verify the FULL board number
2061-701640-700 02PD1

The drive is made in THAILAND it is manufactured OCT 2009 and the s/n is WCAV5269XXXX

needless to say DragonFly2

Thank you so much in advance for any help

Try this, from nearest s/n I have (WCAV5230xxxx)...

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Thank you M8!

Ouch!

Unfortunately I don't have the right donor board

All of mine 2061-701640-xxx are equipped with the U12

I need one U12-less

I'll update you thank you

As long as the PCBs are compatible and that you MATCH ROM SIZE you should be able to write to a PCB with ROM chip the data that you have on the PCB without ROM chip.

Just DUMP your ROM chip either by programmer or vendor specific command or TTL and patch the ROM code and modules with the 192kb version from the drive with masked ROM on MCU and write it back to the ROM chip.

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

Thank you Spildit
But I must admit this confuses me.
I've tried a bunch of ROMS from my db and from hddguru files, but maybe I do something wrong

In fact I got also this info: "write a bare ROM then write needed modules"

I never had to deal with this before and also acelab support doesn't help so much with this case.

What do you kindly mean?

P.S. There is no way to read the original ROM, I have 6.0.16 and also through terminal, no way.

Thank you for some more details

Get a compatible PCB. Drive should spin up ok, then try to gain access to SA so that you can rebuild original ROM from modules on SA.

http://blog.acelaboratory.com/pc-3000-f ... -v6-x.html

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

This is the point
I have only two boards with same number but different revision.
Both have the U12
So i'm not sure they are good.
With both I have the drive that clicks and spins off.

IF you have a PCB from any other WD10EADS-22M2B0 you should be able to access SA on your damaged drive EVEN IF DONOR PCB HAVE EXTRENAL ROM.

If your DONOR PCB have external ROM and you can gain access to SA you can REBUILD ORIGINAL ROM (from data on platters) and write that to the PCB even if the PCB have a ROM chip and a bigger ROM SIZE.

You just have to MAKE SURE that you DON'T CHANGE the size/end of your ROM CHIP DUMP as ROM chips tend to have bigger size capacity then embeded ROM on MCU.

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

Rebuild from SA is my original goal

The problem I face is the drive that don't keep on spinning

and blocking SA access I suppose makes no sense if the board basically "points head to the wrong place"

Though the two board I have are not from a 22M2B0

So I tried to burn ROMS from various 22M2B0

But also writing those ROMS (which some are not fine and go to brick the board) no way, still the same behavior

Drive clicks and spins off

Ok maybe that when the board blown off (it is exploded the head/spindle controller), also the heads preamplifier went dead too.

Either the Pre-amp is gone or your PCBs are NOT COMPATIBLE.

Just buy another identical drive and with that you should be able to properly check and even attempt HOT SWAP if needed....

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

Yes
That was the final option.
I've located one with same board label

Thank you really much for the suggestions

Let us know of the progress with this recovery when you recieve your donor drive.
Regards.

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

On WD drives with burnt VCM highly likely also have burned preamp.
You need firstly check +-5V resistance.

PS. WD drives after 2009 year doesn't contain in SA modules for rebuild ROM.

in the link provided above by "Spildit"

the guinea pig drive were used by ace lab was manufactured on 05 OCT. 2009

Well,
Have You Tried This -> http://ts.acelaboratory.com/index.php?/ ... connection .Also Note That When You Power On The Board Inspect All IC With Fingers And See If Something Is Getting Too Hot If It Does Its Short If Not You Have a Chance

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Hello Amarbir
I've written that above

where I've written that the board is dead so much and also the attempt to read through terminal didn't work.

WOW !!!

I've just "fetch" from my pile of broken drives an DragonFly2 PL 4K with damaged ROM. Aparently the old owner attempted to regen ROM with WDR.
I was able to read ROM by PSV/Kernel and the ROM modules were "NOT INITIALIZED" meaning that WDR attempted to get what it could from SA, created a new ROM and flashed that to the drive.

So no native ROM for me.

Attempted to write ROM files from the HDDGuru file section here :

http://files.hddguru.com/download/PC-30 ... /DragFly2/

On my case i've matched only WD10EADS-00M2B0 and attempted to write this ROM to my PCB :

http://files.hddguru.com/download/PC-30 ... 970624.rar

Version of ROM is 0010000C and was diferent from my drive but it did work.

Full access to SA and USER AREA !!!!

This is very tolerant drive as i didn't use native adaptives neither native ROM code yet it still works !!!

This is my module 11 :



Version 0090002B

All ROM modules are not initialized except ROM image :

103 - Adaptives :



So i've patched my 0010000C version with ROM image on 109 starting at offset 0x200 and wrote that back to get 01.00A01 90.2AM





On my drive there is no ROM MODULES copy on SA but aparently i was very lucky to get close adaptives as so full access is granted.

I'm now Self-Scaning the drive as data is not needed with full script (mod 28).

Just get a compatible PCB from exact same model and try ROM files on Firmware section or from Data Base.

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

I think that all 2061-701640-xxx should be compatible even the ones with external ROM chip....

Just make sure that ROM size is the same.

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