Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 3:23

Hi members,,,
I have HDD laptop 2.5' ,after I connect it, the spindle doesn't work at all
after diagnosis, the problem is ROM damage, after change the ROM, the HDD become works with cliking noise because ATA/ ROM dosen't match,
The question is, How I can make the new ROM adaptive "ATA/ ROM adaptive" , to be able to browse modules
note/ I have SD tools

Image

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 3:49

how did you figured it's the the rom ?
it can be bad heads, preamp, or damage SA

edit: giving the situation i would vote for preamp
Last edited by jermy on April 30th, 2015, 3:51, edited 1 time in total.

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 3:50

is ROM is physically damage ?
did you try the original ROM with Donor PCB ?
did you try to read the original ROM with programmer ?

I think SD tool has this option to build ROM from SA, but you have to reach SA first.
you need a closet drive's pcb to reach SA, backup all modules and build the original from backup data.

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 4:07

jermy wrote:how did you figured it's the the rom ?
it can be bad heads, preamp, or damage SA

edit: giving the situation i would vote for preamp


Hi jermy

how did you figured it's the the rom ?
I know it's ROM damage after I done that
I change the PCB with another PCB have the same number, the spinde work up but when I replaced the orginal ROM to the new PCB the spindle doesn't work at all

it can be bad heads, preamp, or damage SA
the Hdd doesn't drop,and if the HDD have bad heads, preamp, or damage SA, at least the spindle work up when I connect to the power.

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 4:14

chinopk wrote:is ROM is physically damage ?
did you try the original ROM with Donor PCB ?
did you try to read the original ROM with programmer ?

I think SD tool has this option to build ROM from SA, but you have to reach SA first.
you need a closet drive's pcb to reach SA, backup all modules and build the original from backup data.



Hi chinopk,
is ROM is physically damage ?
No physically damage appear,


did you try the original ROM with Donor PCB ?
did you try to read the original ROM with programmer ?
I'll try that

I think SD tool has this option to build ROM from SA, but you have to reach SA first.
you need a closet drive's pcb to reach SA, backup all modules and build the original from backup data.
If I doesn't have a closet drive's, are they any another way to to reach SA in order rebuild ROM from SA

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 4:34

eng.mas wrote:the Hdd doesn't drop,and if the HDD have bad heads, preamp, or damage SA, at least the spindle work up when I connect to the power.

even if it doesn't dropped, these problems can occur.
eng.mas wrote:If I doesn't have a closet drive's, are they any another way to to reach SA in order rebuild ROM from SA

it's not about a closest drive it's about a matched PCB

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 4:46

jermy wrote:it's not about a closest drive it's about a matched PCB


even I a matched PCB without the orginal ROM, you conn't access to SA, there are another parameter should be the same on HDD in order to access to SA

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 4:56

jermy wrote:it's not about a closest drive it's about a matched PCB


exactly, a closest drive will have a good matched PCB. .. :)

Re: WD5000BUCT-63PUZY0 \ ROM damage

April 30th, 2015, 5:40

Is this another PUIS case?

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 2nd, 2015, 6:25

Spildit wrote:Can you post a dump of the original ROM ?

If you post a dump of the "damaged" ROM i can confirm if it's really damaged and hopefully copy the ROM modules to rebuild the original ROM.

If that is not possible a copy of the same version should allow you to access SA, then you just have to rebuild ROM modules by using the data on the SA copies.


Hi Spildit

Sorry for late, I upload a dump of the original ROM

https://www.mediafire.com/?o2kaz418fo2lymd

I'm looking forward to your reply

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 1:23

Spildit wrote:Can you please upload it to somewhere where i can donwload it without having to create an account ?

I'm not able to download it from mediafire. Just zip/rar the ROM file and upload it here at the forum.


Gladly,, the file in the attachment
Attachments
ROM.rar
(222.69 KiB) Downloaded 462 times

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 4:58

Can you upload the donor ROM so that we can compare?

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 7:05

fzabkar wrote:Can you upload the donor ROM so that we can compare?


Hi fzabkar,,

I attached the two files
Attachments
ROM- Donor.rar
(228.22 KiB) Downloaded 337 times
ROM-Patient.rar
(222.57 KiB) Downloaded 329 times

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 9:19

The patient and donor ROM dumps both have the structure of a WD ROM, but neither has any intelligible data. How are you reading these ROMs?

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 12:11

IMHO he is using SD, as the OP wrote @ the beginning
eng.mas wrote:I have SD tools

and something is wrong with that

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 15:29

Try reading the ROMs with the demo versions of SeDiv or WDR, or preferably with a chip reader. If the patient drive is detected in BIOS with its original ROM, then I suspect it may be powering up in standby (PUIS). If so, then that's an easy fix.

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 19:47

I suspect that the heads are toast; there is media damage; and the ROM is OK.

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 3rd, 2015, 20:08

ISTM that the donor ROM must be OK since it is able to spin up the drive. The problem appears to be that the [OP's unknown] tool isn't dumping it correctly.

Furthermore, even with the strange dumps, both patient and donor ROMs have a similar structure. I still suspect that the OP may be seeing a PUIS issue, especially if the patient PCB + patient ROM identifies in BIOS, albeit with zero capacity or a blank model number. An Identify Device dump with a tool such as CrystalDiskInfo would confirm this.

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 4th, 2015, 2:25

Thank you fzabkar,Spildit, and jermy for your interactive,,

I read the ROMs with the SD tools "flash programmer in WD utility"
Image

I think it's possible something is wrong with reading, because I 'm sure the Donor ROM is working, I take it from working HDD
I'll try reading the ROMs by another way such the demo versions of SeDiv, but I did'nt use it before.

Re: WD5000BUCT-63PUZY0 \ ROM damage

May 4th, 2015, 2:59

fzabkar wrote:ISTM that the donor ROM must be OK since it is able to spin up the drive. The problem appears to be that the [OP's unknown] tool isn't dumping it correctly.

Furthermore, even with the strange dumps, both patient and donor ROMs have a similar structure. I still suspect that the OP may be seeing a PUIS issue, especially if the patient PCB + patient ROM identifies in BIOS, albeit with zero capacity or a blank model number. An Identify Device dump with a tool such as CrystalDiskInfo would confirm this.


Dear fzabkar

When I used the patient ROM on PCB the spindle of HDD didn't work at all, so with this can identifies in BIOS?
Post a reply