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
November 5th, 2026, 17:06
Hi everyone,
I have a Seagate ST1000LM014 SSHD that I can’t access from either Linux or Windows.
I connected it via the TTY interface. On startup, I get this output:
- Code:
Rst 0x40M
Servo Processor Is Reset.
(P) SATA Reset
Request spin / disc table recovery
ASCII Diag
TCC:001A
mode
Strt Cln1
ABORT!
OpCode = 00000000
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1
Here is the output with additional version information:
- Code:
F3 T>
Kahuna+,DieShrnk, nQNR, ASD WPin+FFB+Combo+PSpin, 8/16/32GB
Product FamilyId: 72, MemberId: 01
HDA SN: W771H0Q2, RPM: 5408, Wedges: 100, Heads: 4, OrigHeads: 4, Lbas: 00000E8E0DB8, PreampType: B6 04
Bits/Symbol: C, Symbols/UserSector: BEB, Symbols/SystemSector: 1A5
PCBA SN: 0000M543BUB3, Controller: LUXORLPLUS_2_0( 203)(FF-FF-FF-F, Channel: STX_DUNRAVEN, PowerAsic: MCKINLEY MOBILE PLUS Rev 8C, BufferBytes: 4000000
Package Version: KH9T80.LVM3.J701DJ.LVD4, Package P/N: 100773086, Package Global ID: 00210313,
Package Build Date: 02/09/2015, Package Build Time: 13:30:44, Package CFW Version: KH9T.LVM3.00809636.00210313,
Package SFW1 Version: C804, Package SFW2 Version: B804, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 02091330, CustomerRel: LVD4, Changelist: 00809636, ProdType: KH9T.LVM3, Date: 02/09/2015, Time: 133044, UserId: 00210313
Servo FW Rev: B804
TCG IV Version: n/a
RAP FW Implementation Key: 16, Format Rev: 0004, Contents Rev: 06 01 03 00
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled v. 4.7.01.0000000000000017
- LTTC-UDR2 disabled
- SuperParity disabled
- Humidity Sensor disabled
- Background Reli Activity Critical Event Logging disabled
- Torn Write Protection disabled
Does anyone have suggestions on what I could try, or an idea of what might be wrong?
I don’t know much about SSHDs, but I suspect there could be an issue with the flash memory.
I also have a donor drive with a near manufacturing date.
If needed, I can try to provide an ROM dump.
November 8th, 2026, 15:58
I wish I had access to PC-3000. For me it is more a Homelab repair.
Unfortunately I also noticed the donor dive is a year apart.
I attached the PCBs for comparison. The patient is on the left. The donor is in the right.
Any things I could try?
- Attachments
-

- PCBs for comparison
November 9th, 2026, 16:44
You'd need someone to create a modified version of the ROM for you.
This means you'd need to be able to read and write to the ROM module.
If this is accomplished, you'd then be able to use the donor PCB after some terminal commands.
November 9th, 2026, 18:37
I should supplement and say, the above instructions are specific to replacing the PCB - not your OP.
November 17th, 2026, 17:59
Hi, thanks for your reply.
I’ve dumped the hard drive’s ROM. It’s attached to this post.
As I mentioned in my previous post, the donor hard drive has a different PCB and firmware.
I’m afraid the donor hard drive isn’t compatible, and I need one with the same model number and firmware. Is this true?
Patient:
PN: 1EJ164-074
FW: LVD4
Donor:
PN: 1EJ164-041
FW: DEMG
- Attachments
-
ST1000LM014_sshd_patient_rom.txt
- Patient-Rom
- (1 MiB) Downloaded 33 times
November 17th, 2026, 19:38
Here is a solution:
https://forum.hddguru.com/viewtopic.php?p=316583#p316583The same patched ROM won't work for you, but the principle may be the same.
November 18th, 2026, 16:54
Here is my donor ROM.
I would be very grateful if a kind soul could help me out and provide me with the appropriate patches.
As noted, the firmware and circuit board differ from those of the patient.
- Attachments
-
ST1000LM014_sshd_donor_rom.txt
- Donor-Rom
- (1 MiB) Downloaded 25 times
November 18th, 2026, 17:00
I've been trying to patch your patient ROM by following the examples, but I can't make F3RomExplorer happy with one of the CRCs, even though it looks good to me.
November 18th, 2026, 17:18
Thank you very much!
Just to be sure, I just read the patient ROM again and verified it several times. That should rule out the possibility that an error crept in during the read operation.
November 18th, 2026, 17:37
If I can't work out that particular checksum, I'll just give you what I have. Sometimes Seagate only pays attention to checksums during a firmware update. Give me another hour.
November 18th, 2026, 18:34
I can't work it out. Try this anyway.
- Attachments
-

-

- Patient_patched_CFW.gif (26.63 KiB) Viewed 1543 times
-
- ST1000LM014_sshd_patient_rom_CRC_7.7z
- (675.32 KiB) Downloaded 33 times
November 18th, 2026, 19:27
I’ll give it a try tomorrow.
I need to flash the patched firmware onto the chip on the donor board, right?
November 18th, 2026, 19:51
Since your drive doesn't spin, I would patch the patient ROM (on the patient PCB) so that you can then initialise the NAND flash. That's unless I'm misunderstanding something.
November 19th, 2026, 18:22
I'm experiencing a very strange issue.
Every time I flash the ROM, the write operation aborts at 0x00020000.
Even when I try to flash the original ROM again. After that all is '0'
November 19th, 2026, 22:57
Are you sure you are selecting the correct capacity for your IC? It should be 1 megabyte (8 Mbits). Your write is aborting at 1 megabit (128KB).
November 20th, 2026, 15:39
The IC is an W25Q80BW31.
AsProgrammer detected it and sets:
Size: 1048576
Page: 256
SPI Commands: 25xx
- Attachments
-

Yesterday, 16:33
I've now desoldered the IC. I was then able to program it successfully. Next, I flashed the patched firmware onto the chip and soldered the chip back onto the hard drive's circuit board.
With the patched firmware, the hard drive doesn’t do anything at all anymore.
I’m afraid I messed it up. I created the dump from the circuit board. That could also explain the incorrect CRC.
Yesterday, 16:37
No, you didn't mess up. The problem is at my end. You still have the original good dump, so you can revert to the original state. I still haven't been able to work out why my CRC is rejected by F3RomExplorer. The problem could be due to this bad CRC, or my edits may be invalid for this firmware version. Sorry.
I'm thinking about posting my analysis of your ROM to my thread at the HDD Oracle. Perhaps something will leap out at me then.
Yesterday, 17:00
I'm not sure if the original dump was correct.
The chip was still on the PCB when I created the dump.
Even though I ran and validated it multiple times, I think there could be side effects even if they did occur consistently.
When my attempts to flash the chip on the board failed, I tried to “blank” it, and when validating the blank, there were repeated bit flips every time on the same address.
On the other hand, if there were checksums that proved the important parts of my dump were correct, I wouldn't complain.
Powered by phpBB © phpBB Group.