HDD GURU FORUMS

i have this type of HDD, FW : TN003 on label and TN005 show in PC3000 tool,
Model : ST4000NM0035-1V4107
Serial : ZC19TAMJ
Firmware : TN05
Capacity : 4 TB (7 814 037 168)

tried to unlocking into all ways but nothing work,

i get this info after tech unlock code send :

Rst0x80MAA006ATN05
(P)SATAReset

NVCScramSavedHBSize:020A
LD:MD_Alloc:00000050HB_Alloc:0000FlashRestorePowerDevReg7E:7005 PowerDevReg7D:0044MD_Saved:00000050HB_Saved:00000000MD_CRC:FF13
PP:MD_Alloc:0000C000HB_Alloc:0000FlashRestore
PVTSize:00053C3C CompSize:00000ABA DeCompSize:00053C3CMD_Saved:00000ABAHB_Saved:00000000MD_CRC:8EAE
TW:MD_Alloc:00000400HB_Alloc:002EFlashRestoreMD_Saved:00000148HB_Saved:00000000MD_CRC:0000
GC:MD_Alloc:00001000HB_Alloc:0000FlashRestoreMD_Saved:00000028HB_Saved:00000000MD_CRC:13B4
DSP0024
2Sync:0 4
ASCII Diag mode

F3 T>
HighPowerMode Status 0001 Req 0002
Overlay PartNum: 07061320
CFW PartNum: 04061443
Overlay CompileDate: 20160706
CFW CompileDate: 20180406

OverlayCompatibilityCheck failed

Overlay PartNum: 07061320
CFW PartNum: 04061443
Overlay CompileDate: 20160706
CFW CompileDate: 20180406

OverlayCompatibilityCheck failed

Unable to load Diag Cmd Processor Overlay


i have any hope to can unlock it ?

Thanks !

The pcb or Rom content is not original....Probably someone changed the pcb.

its possible to be custom ROM , the pcb looks original bcause was inside into a Huawei Server, tryied to find a good version of ROM or something to can unlock it...
or maybe any advice to change the FW to replace this customable firmware

Overlay PartNum: 07061320
CFW PartNum: 04061443
Overlay CompileDate: 20160706
CFW CompileDate: 20180406

OverlayCompatibilityCheck failed

Overlay PartNum: 07061320
CFW PartNum: 04061443
Overlay CompileDate: 20160706
CFW CompileDate: 20180406

OverlayCompatibilityCheck failed

This messages indicates that the installed ROM is not compatible with the overlays recorded to SA.You have to defeat this to be able to send commands in terminal.

Rgds

got it mate,
hope that i will find a solutions someday...
to keep you close can you add skype : popa.gabriel.93

CFW is not in rom, it is in the SA. Overlay is not compatible with the CFW actually loaded. However, it is possible that it can be solved by changing stuff in rom...
can you post the txt produced by pc3k during rom reading?

pepe

https://www.seagate.com/au/en/support/internal-hard-drives/enterprise-hard-drives/exos-7E/

Seagate's web site states that no firmware updates are available for the OP's serial number, so I'm wondering how the drive was upgraded from TN03 to TN05.

FYI, here is a Dell DA05 update for this model (31 Mar. 2017):

https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=w45c8

There is also a DA06 update (24 May 2017):

https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=r100w

fzabkar wrote:https://www.seagate.com/au/en/support/internal-hard-drives/enterprise-hard-drives/exos-7E/

Seagate's web site states that no firmware updates are available for the OP's serial number, so I'm wondering how the drive was upgraded from TN03 to TN05.

FYI, here is a Dell DA05 update for this model (31 Mar. 2017):

https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=w45c8

There is also a DA06 update (24 May 2017):

https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=r100w

Those steps about firmware update are available only with a Dell system ? also already tried but no succes with a HP system and Seagate tools firmware update

pepe wrote:CFW is not in rom, it is in the SA. Overlay is not compatible with the CFW actually loaded. However, it is possible that it can be solved by changing stuff in rom...
can you post the txt produced by pc3k during rom reading?

pepe

Here is it :
Saving ROM to profile folder
File : C:\Program Files (x86)\ACE Lab\PC-3000\Bin\!Profiles\SgF3\MakaraPlus\ST4000NM0035-1V4107-TN05-ZC19S0S9\Data\ROM\ROM_ZC19S0S9_03D642D3.bin
Parsing container segment....... Flash ROM image
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_0
Parsing container segment....... BOOTFW_CONT_0
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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
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: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_0
Parsing container segment....... BOOTFW_CONT_0
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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Empty container!
End parsing container segment... Flash ROM part 2

This log does not tell us much about the package version, are u using an old version of pc3k?

i also checked a FW update of version TN05 and it was actually missing the ovls. I think that's how this situation happened, downloading such fw update leaves the original ovls intact, leaving us without compatible ones. There is a chance that orig CFW is in the SA, so in theory it could be read from there, but quite complicated without the compatible ovls. Trap 22.

pepe

Can you upload the ROM dump? Maybe F3RomExplorer can extract the package version, etc.

Rom Attached,
Thanks for you attention guys

fzabkar wrote:Can you upload the ROM dump? Maybe F3RomExplorer can extract the package version, etc.

Rom Attached,
Thanks for you attention!

pepe wrote:This log does not tell us much about the package version, are u using an old version of pc3k?

i also checked a FW update of version TN05 and it was actually missing the ovls. I think that's how this situation happened, downloading such fw update leaves the original ovls intact, leaving us without compatible ones. There is a chance that orig CFW is in the SA, so in theory it could be read from there, but quite complicated without the compatible ovls. Trap 22.

pepe

my last version is 6.9.16
Hope that i will find a solution on them

Try this ROM. It must return drive to TN03.
https://disk.yandex.ru/d/1rstD6H126Fsew

E123 wrote:Try this ROM. It must return drive to TN03.
https://disk.yandex.ru/d/1rstD6H126Fsew

full write this one or i need to import SAP/CAP etc ?

thanks for you time

Write this file "as it is". It's your "patched" rom.

i doubt it would do any good, as the CFW is not compatible with the OVLs in the SA.

pepe

E123 wrote:Write this file "as it is". It's your "patched" rom.

Awesome, and if it work ( i will test it in 2h ) can i succed to do all ? 30 pcs.....

Thanks for your time

pepe wrote:i doubt it would do any good, as the CFW is not compatible with the OVLs in the SA.

Did you check it?

AIUI, this firmware keeps a backup copy in a container. The ROM has two "csiD" containers -- one has the original TN03 firmware components while the other has TN05. @E123 has merely reverted to the original container.