Page 1 of 2

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Sat Aug 04, 2018 1:33 pm
by Freakazoid
searching bios for this hard drive, date as close as possible + - 1 week
I think my bios chip is dead since I can not read it. After what I've learned, there's no copy of bios inside SA.

I use DFL-PCIe 4X Data Recovery Express.
Wd5000lmvw-11CKRS0
Date 28 Oct 2018
DCM HACTJHNB
Product of Thailand

When I'm trying to read original ROM I'm getting this error
Image

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Sun Aug 05, 2018 5:34 pm
by jol
I assume the case is solved by now ?!
wd5000lmvw-dead-rom-t2280-10.html#p11267

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 9:12 am
by Freakazoid
Not really. Because when I flash that ROM on a donor chip the driver won't spin up at all.

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 9:40 am
by Jared
Like I was first trying to tell you, that's often caused by a short-circuited read/write head. Try putting the donor PCB/ROM onto a working donor with the same head map and see if it'll spin up that drive.

I think all your fussing around with the PCB was the wrong diagnosis from the start.

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 9:54 am
by Freakazoid
I'll think I'm getting confused because with donor PCB and donor ROM the driver spin up. And making the click of dead noise.

Sorry too be a newbie

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 10:32 am
by Jared
And, as I explained before, that's likely due to the fact that the donor ROM is expecting a different head map and isn't trying to use the short-circuited head. Since it's not testing for and discovering the shorted head, it's not aborting the spin up. Your methodology is wrong here.

Put PATIENT PCB/ROM onto DONOR HDA (with the same physical head map) and see if it'll spin up. If it does, you'll know that your ROM code isn't corrupt and that the issue isn't likely the PCB.

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 3:56 pm
by Freakazoid
Thanks for all the help Jared. the case is closed. Imagine I'm stupid, it's possible that I'm working on the wrong ROM. I think someone may have mixed up more when I switched to a garden. can anyone tell me about ROM 25U20A is for 771859? There is also a possibility that the original can be deleted by trying to restore the contents of the 25U20A.

I give up this disk.

(Hope I can look back on this thread and laugh at the whole thing in 1 year or 2)

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Mon Aug 06, 2018 6:29 pm
by Jared
I'm able to read the ROM code directly through the PCB in 99% of cases. It's very rare to need an external programmer. Usually, boot ROM code mode will work even if the PCB is bad.

Is this a real case, or one you're just learning on? If it's actually for a customer you shouldn't be giving up right now.

Also, if you're looking for a close ROM you should post the serial number so we can look for the closest matching numbers we have to it.

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Tue Aug 07, 2018 1:13 am
by Freakazoid
I'm normally not a person that give up easy.

This case is both for training and a customer (customer is an cx- college and it's like if you can do it you do it if not so no worries but it wouldnu been great if)

I'm also able to read the ROM from PCB but the 25U20A seems dead when I put it on the pcb (I think this one is from a wd5000lmvw-11VEDS3 or something other scorpion) maybe that's why it won't spin up on that PCB.

Some more info about the disk:

WD5000LMVW-11CKRS0
DCM: HACTJHNB
DATE: 28 Oct 2012
PRODUCT OF THAILAND
S/N: WX31A9298045

Hubble Wd5000lmvw-11CKRS0 bios

Posted: Wed Aug 08, 2018 9:42 am
by jol
Freakazoid wrote:Source of the post it's possible that I'm working on the wrong ROM.

have you checked the ROM if its original ?