Replacing the PCB on a ST1000LM014 SSHD

[Fesiplatio]

Hello guys,

I need help replacing the board on my SSHD ST1000LM014 with liquid damage.

The plan:
1. Secure Erase of the donor drive with a Seatools USB Stick and the option "Overwrite Full".
2. Transfer of the ROM from the patient to the donor PCB (with a CH341A ROM reader, an 1,8V adapter and an Pogo Pin WSON 6x5 adapter).
3. Swapping the PCBs.
4. Init of the NAND using the diagnostic port with the command /O and I.
5. Restarting the hard drive.

I base my plan on these two posts:
https://forum.hddguru.com/viewtopic.php?f=1&t=39477
https://forum.hddguru.com/viewtopic.php?p=251854

The Hard Drive Informations:

Patient Drive:
ST1000LM014
Date: 15085
Site: WU
P/N: 720278-002
SN: W382FQW1
PN: 1EJ164-021
FW: HPM6

Donor Drive:
ST1000LM014
Date: 14515
Site: WU
P/N: 720278-002
SN: W3823AG9
PN: 1EJ164-021
FW: HPM6

Now I have these questions:
Do you think my plan is realistic or would you do something differently?
Do I have to pay attention to something?
Can I try to read the ROM with a 1,8V adapter or should not use a adapter and try it with 3,3V?
Is "Overwrite Full" the right option for the secure erase or "Erase Track ZERO" or
should I use a other secure erase tool?


It would be very nice if someone could help me.

[Fesiplatio]

Hello again,

I did a secure erase on the donor drive with hdparm (It was ready after about 3 hours).
After that I transferred the ROM (It worked with a CH341A, a 1,8V apdapter and a pogo pin adapter).
And after that I swapped the PCBs.

The drive is now spinning but the computer does not recognize the SSHD.
The terminal say:

Code:

Rst 0x40M
Servo Processor Is Reset.

(P) SATA Reset


Waiting drive spin up

(S) SATA Reset


Waiting drive spin up

Waiting drive spin up

Waiting drive spin up

Waiting drive spin up



...
Everytime I click Ctr + Z comes: Waiting drive spin up.
But if I click on Ctrl + Z immediately after connecting the SSHD, I am in the F3 terminal for a short time.
It looks like this:

Code:

Rst 0x40M
Servo Processor Is Reset.
(P) SATA Reset

Request spin / disc table recovery
ASCII Diag mode

F3 T>
Set Transfer Mode selected
PIO selected
Set Transfer Mode selected
Ultra DMA selected
ASCII Diag mode

F3 T>
ASCII Diag mode

F3 T>/O+
Input_Command_Error

F3 T>

F3 T>
RECOV Servo Op=0100 Resp=0005
TCC:001F
/
RECOV Servo Op=0155 Resp=0005O
ABORT!
OpCode = 00000060
SenseCode = 03310000
ReadyStatusFlags = 0002A181

ABORT!
OpCode = 00000060
SenseCode = 03310000
ReadyStatusFlags = 0002A181

Unrecoverable Read Verify Error Reported

(S) SATA Reset




Any idea how I can run the command "/O I"?
Or any idea how can I go on?

[Lardman]

Hello again,
After that I transferred the ROM (It worked with a CH341A, a 1,8V apdapter and a pogo pin adapter).

Double check the patient rom contents against the rom now on the donor. When you say liquid damage - how bad is the original board?

[Fesiplatio]

Hello again,
After that I transferred the ROM (It worked with a CH341A, a 1,8V apdapter and a pogo pin adapter).

Double check the patient rom contents against the rom now on the donor. When you say liquid damage - how bad is the original board?

Hello Lardman,
thanks for you answer.
I saved the ROMs on the computer in .bin files.
The hash of the ROM file now on the donor is the same like the file from the patient ROM.
So I think the ROMs should also be identical.

As I can see it is the orignial board only slightly damaged, but it has a dark through hole.
I heard it was only little liquid.

PS: I post the two ROM files below.

[Fesiplatio]

The links to the two ROM .bin files:

The current donor ROM: https://drive.google.com/file/d/1TnHfAMFrRiEO-LE21w_AWQa1lkqN0od3/view
The patient ROM: https://drive.google.com/file/d/1k9hztTikhQPUTp3uNQ9VA31UK_EdYqeH/view

[Lardman]

Both are identical and PC3K doesn't see anything wrong.

Code:

FLASH ROM Info
==============
Image size............... : 1048576

QNR Revisions:
Flash ROM image.......... : 0


CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0x72 (Kahuna_5400)
Fam Member............... : 0x1
Head count............... : 4
Date..................... : 20 Aug 2014
SN....................... : W382FQW1
PCB SN................... : 0000N5074VNN
PCB PN................... : ÿÿÿÿÿÿÿÿÿÿ
WWN...................... : 5000C5007C447242
MDL1..................... : ST1000LM014-1EJ164-SSHD                 
MDL2..................... : ST1000LM014                             
Capacity................. : 1953525168

RAP
###
Format revision.......... : 0x0004
Contents revision........ : 0x06010300
Number Sys Zones......... : 1
Number User Zones........ : 60
Heads count.............. : 4
FW Implementation Key.... : 0x16

SAP
###
Addr 0................... : 0x0001D400
Addr 1................... : 0x40002000

Fam ID................... : 0x72, (Kahuna_5400)
Fam Member............... : 0x1
SN....................... : W382FQW1
Servo FW rev code........ : 0xB639
Max head................. : 3
Seek mode................ : 2000
Flags.................... : 1AC9
Head vendor.............. : alternative
RRO mode................. : 0005
Preamp type.............. : 00D1
Logical head map......... : 00 01 02 03
Phys head maps........... : 00 01 02 03
                          : 00 01 02 03
                          : 00 01 02 03

IAP
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFFFFFF
NAND ROM cache flag, Kahuna like........ : 12345678
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

CODE info
#########
Bank 0
ProdType................. : KH6T.HPM1
Controller FW Rev........ : 01141206
Customer Release......... : HPM6
Changelist............... : 00650592
Build date / time........ : 14/01/2014 12:06:38
Package Global ID........ : 00503913
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : CU0SAN
Pkg P/N.................. : 100747282
Servo FW................. : B640 / ---- / ---- / ----
Package Version.......... : KH6T6B.HPM1.CU0SAN.HPM6
Pkg CFW Ver.............. : KH6T.HPM1.00650592.00503913


I hate these drives - you may have more than just a board problem. Someone with a higher success rate with these will be able to confirm.

[Lardman]

Upload the attached rom - see if it gives you terminal access.

Attachments

patient_patched.zip

(676.82 KiB) Downloaded 1737 times

[Fesiplatio]

Lardman,
Many thanks for your help.
I don't see how mechanical damage could have occurred because there really was very little fluid and no other problems.

I'll try the patched ROM right away.

[Fesiplatio]

I tested the patched ROM and now I have access to the terminal after pressing Ctrl + Z.

I tried to init the NAND with "/O and I" but after reconnecting the SSHD Windows still says "No media".
This is the terminal output:

Code:


Request spin / disc table recovery
ASCII Diag mode

F3 T>/O

F3 O>I

ALF Parametric Tables Preserved

Flash was erased and ALF Tables have successfully been initialized
F3 O>


[Lardman]

Is the drive seen in the bios and is it shown as the correct size.

[Fesiplatio]

No, I don't see it in the BIOS and Windows shows the drive only with 0 bytes.

[Tomset]

Fesiplatio,
after initialization NAND, you need to write the native ROM

[Lardman]

But the drive is ID'd correctly? I thought it would have given the full drive metrics and just blocked UA access. As Tomset say rewrite the original patient ROM back and give it a power cycle.

[Fesiplatio]

The drive is also not properly identified.
This is a screenshot from the windows explorer (in German).

I'll change the ROM again right now.

Attachments

[Fesiplatio]

Lardman and Tomset,
Yes, wow it worked.
I changed the ROM again to the original patient ROM and after reconnecting the SSHD, I have all data back.
Thank you soooooooooo much.
I've been busy with this hard drive for an extremely long time and now it worked.
You really helped me alot.
Many Thanks.

[Lardman]

Good stuff. Now make a back up (just not on another hybrid drive)

[Fesiplatio]

Yes definitely

[Eastcoast]

Lardman and Tomset,
Yes, wow it worked.
I changed the ROM again to the original patient ROM and after reconnecting the SSHD, I have all data back.
Thank you soooooooooo much.
I've been busy with this hard drive for an extremely long time and now it worked.
You really helped me alot.
Many Thanks.

Well done Lardman, Tomset. Glad it worked out for him.

I can see from another forum the OP has been trying since the start of the year to get help with this and has done a lot of research on getting another drive with the same FW and finding a way to read off the ROM and also researching the terminal commands.

[gsmart]

Hi, guys.
I have almost exact same case, except of I have another FW (LVD3)
I'm getting "Waiting drive spin up" on Ctrl-Z after swapping the patient's ROM to donor's PCB.
Please help me with a ROM patch

Attachments

flash_W25Q80BW_ST1000LM014_Donor.zip

(674.63 KiB) Downloaded 1282 times

flash_W25Q80BW_ST1000LM014_Patient.zip

(672.02 KiB) Downloaded 1414 times

[Mikippp]

Hi,
Only the patient's ROM was successful

Mikippp

Attachments

flash_W25Q80BW_ST1000LM014_Patient_Patch_1.zip

(672.03 KiB) Downloaded 1138 times