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

ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 4:45

Hello, I get an error when I read the ROM with PC3K terminal.

When I import adaptive from donor rom, SAP gives an error again.

I tried to fix it with F3 Rom explorer but it fails.

I change the Head Map via ROM with PC3K, but it doesn't work.

Help would be great.

Thank you

Code:
Software can`t control COM port signal level for this USB/COM adapter

Software can`t control COM port signal level for this USB/COM adapter
Software can`t control COM port signal level for this USB/COM adapter
Selected family......................... : 55, Sentosa
Model by ID............................. : <HDD ID NOT READ>

Loading default settings!
Use the options dialog to review and save utility settings.
Then press OK!


Family default settings loading!


Tech Key...
Error executing command  "En Tech" (ABR)
Terminal : error detecting HDD terminal baud rate
Drive identification reading ........... : Ok


Switching HDD power supply OFF

Switching HDD power supply ON
ROM Type: 0xFF(STM)
ROM Size: 0x80000




WARNING!
ROM image contains crytical damaged objects
[SAP]





Multipart flash image found. Reparsing...

Saving ROM to profile folder
File  : C:\Program Files (x86)\ACE Lab\PC-3000\Bin\!Profiles\SgF3\F3 Arch (common)\ST_M13FQBL-12131528-QNR_BFW\Data\ROM\ROM.bin




WARNING!
ROM image contains crytical damaged objects
[SAP]



Parsing container segment....... Flash ROM image
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM image

Multipart flash image found. Reparsing...

Parsing multipart flash image....... Flash ROM image

Part 1...

Parsing container segment....... Flash ROM part 1
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 2
Attachments
ROM_SAP_ERROR.rar
(166.18 KiB) Downloaded 139 times
read_error.JPG

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 6:36

Someone corrupted this ROM by messing with the head maps. I restored the original (?) SAP from the copy in the Extra Space.

Was there a ROM error before you messed with the head maps, or did the ROM error happen afterwards?
Attachments
ROM_SAP_ERROR_fixed.7z
(162.48 KiB) Downloaded 130 times

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 6:47

Thank you very much fzabkar.

HDD has been processed somewhere before, but we have no information about what happened. The heads has been replaced and there are damages on the platters. First I checked rom ( this is my rituel :) and encountered this problem.

sabotage perhaps?

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 6:54

I think it looks like ineptitude rather than sabotage.

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 6:57

fzabkar wrote:I think it looks like ineptitude rather than sabotage.


:lol:

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 7:07

BTW, the ROM has two halves, and there are copies of the adaptives in each half. F3RomExplorer incorrectly detects the second half as Extra Space.

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 7:14

fzabkar wrote:BTW, the ROM has two halves, and there are copies of the adaptives in each half. F3RomExplorer incorrectly detects the second half as Extra Space.


is that why F3 explorer didn't work?

i'm pretty sure you have own tool for this.

The rom works great ( thanks again) but unfortunately there are still mechanical issues to be resolved.

Re: ROM image contains crytical damaged objects [SAP]

January 8th, 2025, 7:17

F3RomExplorer (free version) was written before the ROM formats began to change. I just have a CRC calculation tool and a different tool for locating single-bit errors.
Post a reply