Samsung / Seagate st1000lm024 Damaged ROM Recoverable?

[gtd4242]

I have a Samsung that came in. The drive does not power up. Powers up fine with an exact match parts drive PCB. I swapped the ROM, and the drive does not power up. I swap the parts drive ROM to the failed drive's PCB and it powers up, so it is definitely a ROM issue. The drive just stays in a BSY state though, which I would expect.

Any hints, or tips on anything that I can do to try and get this working through terminal? I work with Seagates quite a bit in terminal, but never Samsung variations. It appears the baud rate is different on these, and I'm assuming the commands are going to be different. Without the native ROM is it even possible to get the donor ROM to be compatible, or do you have to do a hot swap type procedure? Feel free to PM if you prefer. Thanks.

[fzabkar]

Can you provide a ROM dump? Could it be a FIPS corruption problem?

[gtd4242]

They said the drive had a voltage surge and then wouldn't spin up after that. I'm thinking it damaged the ROM.

[MindMergepk]

@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

have seen some Samsung drives with ROM bug, not this model. thanks to pcimage for pointing those out.
you can adapt new PCB by writing 02 modules from working drive to patient drive by hot-swap.

what tools you have BTW ?

[fzabkar]

@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643

[fzabkar]

They said the drive had a voltage surge and then wouldn't spin up after that. I'm thinking it damaged the ROM.

Measure the resistance between the chip's Vcc and Ground pins.

As for baud rates, etc ...

How to connect a terminal cable on a Samsung drive ?
http://www.hddoracle.com/viewtopic.php?f=116&t=189

If you can upload the contents of patient and donor ROMs, I can try to verify their checksums.

[chinopk]

deleted.. sorry

[MindMergepk]

@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643

thank you, always an admirer of you

[nuwanddi]

hello everyone. this is the ROM from My HM500JJ Drive. Drive doesnt spin up with this ROM. i dont have a exact same donner. i have a HM320HJ with same board. so when i swap the board Drive spins up and stays busy, can someone help me to solve this case ?? i have MRT with me

Attachments

W25X40_20190322_174315.zip

(177.27 KiB) Downloaded 443 times

[Mikippp]

Hi,

Mikippp

Attachments

W25X40_20190322_174315_FIPS.zip

(176.85 KiB) Downloaded 446 times

[pcimage]

Nothing in terminal?

[fzabkar]

According to my program ...

Code:

Searching for FIPS block (expected checksum = 0x0000) ...

Found FIPS text string at 0x014362
Checksum for 0x0400 byte FIPS block = 0xCE80  - BAD
Checksum for 0x0800 byte FIPS block = 0x8337  - BAD
Checksum for 0x0C00 byte FIPS block = 0x4A34  - BAD
Checksum for 0x1000 byte FIPS block = 0x66E0  - BAD

Found FIPS text string at 0x0194BC
Checksum for 0x0400 byte FIPS block = 0xD568  - BAD
Checksum for 0x0800 byte FIPS block = 0x535F  - BAD
Checksum for 0x0C00 byte FIPS block = 0x9CE2  - BAD
Checksum for 0x1000 byte FIPS block = 0x26E4  - BAD

Found FIPS text string at 0x019CB8
Checksum for 0x0400 byte FIPS block = 0x8279  - BAD
Checksum for 0x0800 byte FIPS block = 0xC52D  - BAD
Checksum for 0x0C00 byte FIPS block = 0x5B54  - BAD
Checksum for 0x1000 byte FIPS block = 0x98EC  - BAD

Could not find a FIPS block with valid checksum

[sin]

@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643

thank you, always an admirer of you

Count me in
--

[Amarbir[CDR-Labs]]

Frank ,
Its Not The FIPS Always ,Sometimes the client changed the pcb without saying that to the DR lab ,In that case a terminal dump is imp to see if Heads are compatible or not ,Even that stage the hdd does not power up