Hello friends, good day. I'm here with a ROM study case that I want a little help to understand.
This Seagate Granada is allways Busy, without any weird noise when you turn it on.
Looking to terminal messages we have this:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:001C

EDAC Value = 0000F018E59FE12A
SNOOOZZZZZZEEE Retry
EDAC Value = 0000F018E59FE12A
No HOST FIS-ReadyStatusFlags 0002A1A1
TCC:001D

TCC:001D

TCC:001E

TCC:001E

TCC:001F

And when I try to read sysfiles or get the preamp head resistances I get "Diagnostic Port Locked
" message.

Ok... I've got some cases like that before. Made an original ROM backup and used MRT virtual start to get rid of the "No HOST FIS-ReadyStatusFlags" and Diagnostic Port Locked.

After that HDD get in DRD and DSC status, but whenever I try reading sysfiles or preamp head resistances again I get this:

Spin Up
SpinOK
TCC:0022

EDAC Value = 0000F018E59FE12A
SNOOOZZZZZZEEE Retry
EDAC Value = 0000F018E59FE12A
6Gb Max Speed lowered to 3Gb for Intel bug
Send Status: COMRESET seen
TCC:0022

ASCII Diag mode

F3 T>/7

F3 7>X

Overlay PartNum: 09141132
CFW PartNum: 06261507
Overlay CompileDate: 20160914
CFW CompileDate: 20150626

OverlayCompatibilityCheck failed

Unable to load Diag Cmd Processor Overlay

F3 7>

So... different from cases I've found here, this drive doesn't ID at all. Don't have LBA access and can't read any sysfile. Here is the original ROM.
My question is: How can I get compatible overlays or Patches to use terminal properly?
Thank you so much for any help.

Sorry... here is the original ROM file

When the HDD tries to read. Does the HDD disconnect and turn on again?

_________________
Is Earth an intelligent being?

mhp666, Yes, this happens when i try to reload after i get DRD / DSC status.

In my experience and I may be wrong, that could be due to two things.
a) The HDD restarts upon finding a read failure in the SA.
b) In some Seagate if you clean the SATA connector well (you can also give it some oil for electrical contacts), the voltage stays more stable and does not reset.

There is a problem with the Seagate when connecting them to the MRTLAB that the 5V voltage drops many and they reset themselves. Option b) does not always work.

Please, if you test it, comment on the result.

_________________
Is Earth an intelligent being?

Another solution is to try the different channels of the MRTLAB or connect the HDD with an external power supply.

_________________
Is Earth an intelligent being?

Is your PCB native?

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

I had experienced this error in MRT yesterday. When I play with my stock drives. I made Firmware unlock, Regen translator. I have access short time to drive. Don't remember what fault occurred after then .maybe led

_________________
A Recovery Service In Turkey . Veri Kurtarma Türkiye https://www.digitalverikurtarma.com
Donor Drives hdddonormarket.com

mhp666, Thank you for your reply. I'll check it and come with the results later.

northwind, Yes, PCB is native.

HddDonorMarket, Unfortunately I can't read/write any sysfile, so it's not possible to regen translator (nor even doing a backup) ...

Are you guys guessing that the problem might be on PCB? Really didn't suspected that, but I can try to write ROM to other one.
Thank you so much for all your replies. I'll try this later and come back with results.

Your original ROM version 20160914. However, the message to the terminal: "Overlay CompileDate: 20160914
CFW CompileDate: 20150626
OverlayCompatibilityCheck failed " says:
either virtual loading is not working correctly for you, or the unlocker is not working correctly.
Show your ROM after unlocking and your 3D Loader.

Well... I tried everything mhp666 said, unfortunately nothing changed.
E123, Here it is the ChangedROM and the 3D loader. IS there any way to edit these CompileDate or something like that using something like F3RomExplorer?

Thank you so much for any other suggestions.

3D loader is not from this version of firmware.
Either read the native 3D.rpm, or look in the ready-made resources, or use this one, but then additionally load into your memory a regular (not 3D) loader with diag-overlays from the same set.

E123, Thank you so much for clarifying this for me. It's really another version of firmware.
But I don't have CC46 from ST2000DM006-2DM164 (neither HDDSurgery have it)... I have it from other models. Would it work even from other HDD model?
Thank you so much again.

Try 3D loader from ST2000DM006-2DM164-СС26 kit and a regular loader from the same kit. Only "in memory"(!), without recording on platters.

E123, I'm getting an error when I try to update microcode. It starts to send it via serial port, but doesn't finishes and shows and fail message.
I'll try to find someone with 3D.rpm from this model with CC46 fw version.
Thank you for all your help.