Seagate ST4000DM004 ROM corruption ?

[Takanashi_Hina]

Glad it did work out for you.

Credits goes to @fzabkar and @E123 (F3romExplorer creator) that did "fix" the ROM for you.

Now let's just remember that HDD Surgery firmware "backups" might sometimes have ... suprises ...

Same goes to drives send to Helpdisk / HDD Surgery for recovery ...

No way that they did manage to backup resources from your drive without a spinning drive so ... Also if the "ROM" were to be "damaged" later on why is the ROM on the firmware dump also damaged ?



It was done intentionaly, no doubt about that.

[Pepe]

... or they repaired the rom themselves, then took the fw backup, but maybe their quote was refused, so gave back the drive in its original state...

[Nikola Radovanovic]

On our web site you can find both roms, original and fixed one. Original is in folder ROM and Repaired one is in SA backup rom.

[Nikola Radovanovic]

You can see in our job tracking sistem that first log was written that client brought a hard drive witch is does not spin. We did what guys suggested to Miodrag. He can read serbian so he can see and corupted is more less same on Serbian.
Since he did not know how to do this him self, clearly shows client brought it to a good company first and bad one later, but it is his right.
@ Mr Takanashi, Sir you do not know me or sow me and you call me a liar and a thief?
After rom is fixed he cloned it , yes?
Shame on you!

[northwind]

I think it's unfair to throw accusations without proof or without taking the time to ask what really happened...
Sad. Very sad.

[Takanashi_Hina]

Source of the post ... or they repaired the rom themselves, then took the fw backup, but maybe their quote was refused, so gave back the drive in its original state...

Yes, most likely this was the case. But the ROM was altered by "someone else" to start with. Maybe the drive was with someone else first ? Well ...

[Takanashi_Hina]

Source of the post On our web site you can find both roms, original and fixed one. Original is in folder ROM and Repaired one is in SA backup rom.

Too bad that now I do have to pay for firmware as my account on HDD Surgery Firmware database (not surprisingly) got deleted...

[Doomer]

Source of the post
But the ROM was altered by "someone else" to start with.

Could be bugs in some DR tools, judging by locations of the "problems". Possibly results of "unlock unfixing" that went wrong

[Doomer]

Source of the post
Too bad that now I do have to pay for firmware as my account on HDD Surgery Firmware database (not surprisingly) got deleted...

You and everybody else

[Takanashi_Hina]

Source of the post

Source of the post
Too bad that now I do have to pay for firmware as my account on HDD Surgery Firmware database (not surprisingly) got deleted...

You and everybody else

It was working fine yesterday ...

I was deleted just now ...

[Takanashi_Hina]

Source of the post

Source of the post
But the ROM was altered by "someone else" to start with.

Could be bugs in some DR tools, judging by locations of the "problems". Possibly results of "unlock unfixing" that went wrong

Yeah ... It can ... But someone did had to use a firmware tool on the drive to get that "problematic" ROM that doesn't spin up the drive.

[Takanashi_Hina]

Source of the post I think it's unfair to throw accusations without proof or without taking the time to ask what really happened...
Sad. Very sad.

To be fair ...

Hddsurgery's Log.log file (in the resource dump) suggests that they received a ROM with two corrupt segments. The first corruption is in the GLOB_FLASH_DIR segment, and the second is in the RAP.

Code: Select all

Parsing container segment....... Flash ROM image
Warning! Segment header check sum is not zero: 1B5F433B
Segment: GLOB_FLASH_DIR
...
Parsing segment....... RAP
Warning! Segment whole-space check sum is not zero: 0000B8B0
Warning! Segment  used space check sum is not zero: 0000481C

These two bad areas are present in the "original.bin" ROM that was uploaded by Miodrag.

However, ROM_ZFN0K0V9_07FF405F.bin in the resource dump has a good (repaired ?) GLOB_FLASH_DIR, but a bad RAP.

Therefore, it appears that Hddsurgery have uploaded a partially repaired ROM.

[Nikola Radovanovic]

Source of the postTo be fair ...

Hddsurgery's Log.log file (in the resource dump) suggests that they received a ROM with two corrupt segments. The first corruption is in the GLOB_FLASH_DIR segment, and the second is in the RAP.

It's too late for apologizing, you already made damage with your false accusations. It's always easy to write from your comfortable chair and say that somebody sabotaged it on purpose with any single proof.

There are two ROMs in the package, one with original corrupted content and the other one which is fixed and with which we cloned the disk. You can also see the times when we read original ROM (8:36), extracted CAP, SAP, RAP... parts and assembled fixed ROM. Then at 9:20 we got fully working disk with full ID and made full internal firmware backup and cloned the disk. At 9:35, if you take a look at the screenshot from our software, our engineer noted bad ROM, and that disk is being cloned, and a couple of hours later at 6 PM that disk was cloned without any BS.

Too bad that now I do have to pay for firmware as my account on HDD Surgery Firmware database (not surprisingly) got deleted...

What did you expect, to throw false accusations without consequences??

[Takanashi_Hina]

This is childish.

[Takanashi_Hina]

Source of the post

Source of the post
But the ROM was altered by "someone else" to start with.

Could be bugs in some DR tools, judging by locations of the "problems". Possibly results of "unlock unfixing" that went wrong

There should be no need for any DR tool to mess with the RAP. Consequently the bad used-space and whole-space CRCs in the RAP are either the result of a flipped bit in the data section, or deliberate action.