Request: ROM + modules (02,32,33) for ST12000NM001G — QNR Boot / HPSR loop

59 views
Skip to first unread message

Fabio Ferreira

unread,
Nov 2, 2025, 1:01:24 AMNov 2
to DataRecoveryCertification
Hello everyone,

I have a Seagate Exos X16 ST12000NM001G that is stuck in boot loop and does not show F3 prompt.
Symptoms:
- Boot: 0x0100MAA0053SN03
- Motor started / Heads loaded
- Repeating HPSR
- Ctrl+Z -> "QNR Boot: Interface Reset Received"

PCB number: 100833707 (REV B/C?) — please advise.
I urgently need either a ROM dump compatible with PCB 100833707 (same FW family, SN03 if possible), AND the SA modules 02, 32 (Translator), 33.

I understand ROMs are proprietary; I am requesting assistance from certified/data recovery professionals. I can provide additional logs, photos of PCB, and firmware version if needed. Prefer replies by PM for direct exchange.

Thanks in advance,
[Fábio] — Brazil

Justin Skinner

unread,
Nov 4, 2025, 11:42:53 AMNov 4
to DataRecoveryCertification
Last time I checked it was impossible to rebuild a missing ROM for Seagate.

drbc...@gmail.com

unread,
Nov 4, 2025, 12:44:54 PMNov 4
to datarecovery...@googlegroups.com

Is it possible to read something by hot swap?

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/9dab47f7-316e-401c-8a03-d58810144fc7n%40googlegroups.com.

t...@desertdatarecovery.com

unread,
Nov 4, 2025, 12:55:20 PMNov 4
to datarecovery...@googlegroups.com

Terminal will be locked until you read the ROM and unlock it.

These drives have dual ROM In a RAID configuration that PC3K can unlock and re-assemble, but they need to be removed and read with a particular reader.

Until you read the ROM and unlock it and get a terminal output there is little you can do.

However I doubt it’s a ROM issue.

What happened to the drive, was it dropped?

When you say ‘boot loop’, what do you mean?

Fabio Ferreira

unread,
Nov 18, 2025, 6:14:44 PMNov 18
to datarecovery...@googlegroups.com

Hello,

Due to a high service workload, my response was delayed.

The drive did not fall, as previously suggested. The user reported there was an unexpected power loss, and after that the HDD began showing failures and no response during data access attempts.
Initially, it looked like a translator failure, due to the lack of logical access.

However, during startup, the drive spins up, the heads load, and then it enters a repetitive cycle. The terminal displays:

“Flash boot code Digital Signature Verification failure / checksum failure”

After this message, the drive automatically restarts, repeats “Motor started / Heads loaded / HPSR”, and returns to the same point without allowing access to the F3 T> prompt.
That is why I described it as a “boot loop”.

There are no signs of mechanical damage — the spindle and preamp are detected correctly. The pattern indicates a failure in the bootcode stored in the PCB’s NAND, which is not passing digital signature verification. Reading a donor SPI ROM will help confirm this.

I also have the latest version of MRT, fully compatible with this HDD model and equipped with the hardware required to extract firmware from both ROM chips (SPI and NAND).

I will proceed with extracting the firmware from both chips and perform the unlocking process. I will send the results as soon as possible.

Thank you.


pbzcbf...@gmail.com

unread,
Nov 18, 2025, 8:50:25 PMNov 18
to DataRecoveryCertification
This happens when the MCU and ROM are mismatched. Can you dump your ROMs and upload them?
Reply all
Reply to author
Forward
0 new messages