Seagate F3 ROM Rebuild

[ddrecovery]

I have a ST1500DM003 where the client tried to remove the ROM with pliers. The ROM is physically damaged. I have an exact matching board (model/part/fw) but the drive gives servo errors. Is there anyone out there who can rebuild a ROM on an F3. If so please PM me.

ST1500DM003
Grenada
HP16

[hpw333]

upload picture for terminal output
and try to short contact and goto T-level
then i can help you

[digisupport]

Upload a picture of the chip damage. Maybe i can help you.
Not to rebuild a F3 ROM but to get data out of the butchered chip.

[day1data]

Too many unique adaptives in the ROM to recreate it.

Your better to try an repair the damaged ROM and read the contents in a ROM reader.

Post a pic of the damaged ROM.

[Martin]

Actually, there are three ways:
1. Try to fix physical damage as much as it allow to read ROM content (if there only pins are damaged you can try to remove some part of IC enclosure to fit some small wires by soldering or by some similar way) by programming tool.
2. You can ask one forum member (Peter from Hungary) for help (not for free) to regen ROM.
3. You can wait untill some DR tools vendor (ACElab, SalvationData etc.) research/buy method how to regen ROM content and buy their tool.

[Martin]

upload picture for terminal output
and try to short contact and goto T-level
then i can help you

Did you read the question carefully?

[hpw333]

upload picture for terminal output
and try to short contact and goto T-level
then i can help you

Did you read the question carefully?

it's my error , i post answer to wrong thread

[ddrecovery]

Here is a picture of the ROM. Just had confirmation from the client that he wants to pursue this so I will see if we can read it today. Its a little more than just a leg that's been damaged. But you never know.

Attachments

[lcoughey]

To me, it just looks like the outer shell is damaged and it likely okay.

[ddrecovery]

You were quite right Luke. The ROM did read so the board was also dead. Not sure what the client did but looks like he shorted the board at the same time. Now getting preamp failure message.

Code:

Boot 0x40M
Spin Up
TCC-001F[0x00026F7C][0x000270B7][0x000270B7]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddW
PreampFaultStatus = 0000YW
PreampFaultStatus = 0000YWMMMMMM


[dick]

Looking at the way the rom ic was damaged I would go over every unpopulated solder pad on the pcb just in case small sm components have been knocked off. Of course one would be looking for the tell tell signs ie. sharp edges on the pads. Or are you getting the preamp errors using the replacement board and programmed rom?

[ddrecovery]

Looking at the way the rom ic was damaged I would go over every unpopulated solder pad on the pcb just in case small sm components have been knocked off. Of course one would be looking for the tell tell signs ie. sharp edges on the pads. Or are you getting the preamp errors using the replacement board and programmed rom?

Just to clarify, this output is from the clients drive with donor board and original ROM uploaded via boot code.

[fzabkar]

The logical approach would be to determine what is wrong with the original PCB. The failure mode may then shine a light on the current problem.

[ddrecovery]

The logical approach would be to determine what is wrong with the original PCB. The failure mode may then shine a light on the current problem.

The board has multiple issues such as a removed TVS and smooth chip failure.

[fzabkar]

The logical approach would be to determine what is wrong with the original PCB. The failure mode may then shine a light on the current problem.

The board has multiple issues such as a removed TVS and smooth chip failure.

If the 5V TVS diode has been removed, then most probably there was an overvoltage on this supply. The user then most likely powered the drive without protection, resulting in failure of the preamp and damage to the 5V side of the SMOOTH chip.

See the following examples (yes, I know yours is a Seagate).

Catastrophic failures in Western Digital PCBs:
http://www.hddoracle.com/viewtopic.php? ... 119&p=5033

[ddrecovery]

The logical approach would be to determine what is wrong with the original PCB. The failure mode may then shine a light on the current problem.

The board has multiple issues such as a removed TVS and smooth chip failure.

If the 5V TVS diode has been removed, then most probably there was an overvoltage on this supply. The user then most likely powered the drive without protection, resulting in failure of the preamp and damage to the 5V side of the SMOOTH chip.

See the following examples (yes, I know yours is a Seagate).

Catastrophic failures in Western Digital PCBs:
http://www.hddoracle.com/viewtopic.php? ... 119&p=5033

Agreed. Thank you

[lcoughey]

You were quite right Luke. The ROM did read so the board was also dead.

If you read the ROM to file, take a look and see if the serial number matches up with the drive.

[ddrecovery]

You were quite right Luke. The ROM did read so the board was also dead.

If you read the ROM to file, take a look and see if the serial number matches up with the drive.

Yes it did match, did some checking at several points of the ROM and it doesn't seem like its corrupt or a ROM from another drive.

[fzabkar]

Yes it did match, did some checking at several points of the ROM and it doesn't seem like its corrupt or a ROM from another drive.

If the ROM were corrupt, ie bad checksum, then the drive wouldn't start.

[pcimage]

Yes it did match, did some checking at several points of the ROM and it doesn't seem like its corrupt or a ROM from another drive.

If the ROM were corrupt, ie bad checksum, then the drive wouldn't start.

That's correct. Looks like toasted preamp.