Seagate Barracuda 2TB ST2000DM008 FW 0001

[RobertMax]

The drive is not visible in BIOS. The terminal is locked, and I cannot access the drive data. Is there any way to access the drive? (I am attaching photos and a ROM dump.)

Attachments

Zrzut ekranu 2025-10-20 111212.png (28.58 KiB) Viewed 684 times

MX25U1635F@SOP8.ZIP

(853.02 KiB) Downloaded 20 times

[Lukas]

The unlocked ROM is attached.
To do anything, you need to send a handshake, so simply unlocking it won't do you much good...

Attachments

MX25U1635F@SOP8-unlock.rar

(246 KiB) Downloaded 23 times

[pclab]

Without proper tools I'm afraid you can't do nothing...

[Lukas]

Wait, I'm looking at this terminal log now – I see you have level T enabled.
Can you send commands? What do you get when you press CTRL+L?

[pepe]

No Phy

this may refer to bad cable/connector, but i also saw such thing with a bad mcu (sata port damage?)

pepe

[RobertMax]

CTRL+L = "Diagnostic Port Locked"

Attachments

[RobertMax]

Interestingly, before uploading the unlock, I made a copy of the ROM and uploaded the file. A message popped up as shown in the photo. I thought it was over, but I uploaded the file from the second copy and the drive started up as before, only this last copy has the correct drive SN than the first copy.

Attachments

MX25U1635F@SOP8v2.zip

(577.67 KiB) Downloaded 18 times

Zrzut ekranu 2025-10-21 072806.png (11.33 KiB) Viewed 611 times

[E123]

Are no gentlemen confused by the fact that there are different serial numbers in the ROM and on the sticker?

[Lukas]

Are no gentlemen confused by the fact that there are different serial numbers in the ROM and on the sticker?

Indeed. In the first attached ROM dump:
Incorrect model: ST500DM009-2F110A
Incorrect serial number: Z990VRXM
Everything is wrong.
Now, author, tell us what exactly happened with this drive, where you got it, what you did...
Do you have the original ROM from it?

[Lukas]

Interestingly, before uploading the unlock, I made a copy of the ROM and uploaded the file. A message popped up as shown in the photo. I thought it was over, but I uploaded the file from the second copy and the drive started up as before, only this last copy has the correct drive SN than the first copy.

The second ROM you uploaded seems to fit.
The head map is set to MaxHead: 2: 00,01,03,03.
Can you provide the history of this drive?

[RobertMax]

I received a drive at work to check after an unsuccessful repair by an IT specialist. The drive did not connect to the computer and was not visible in BIOS (the drive could be heard working). After connecting the terminal, I wanted to repair the drive connection, but Seagate has blocked the terminal in newer models for service purposes. After unscrewing the board and connecting to the MX25U1630F ROM via XGecu T48, I read the contents, but on the MX25U1635F because 30 was not on the list. I am not sure if I messed up the file or if the programmer read it that way. Before saving this from you, I read the ROM again and that's it.

[RobertMax]

XGecu T48 and Seagate drive.

Attachments

[pepe]

In the terminal screenshot i saw it loaded the discfw, so i guess it had the correct ROM that time. There is very low (ie only mathematical) chance of loading discfw with a foreign rom. The no phy msg is still there...
overwriting the original rom is not a good idea in any circumstances, btw.
pepe

[RobertMax]

I know what went wrong with the first ROM. It was a 500GB drive and a 25Q80EWS01 EEPROM. The drive will be scrapped, as there is no point in trying without the right equipment. Thank you all for your help.

Attachments