ST2000DX001 2TB with FW CC43 does not spin

[cocovios]

Hello,

this is my story.
the pc started to recognize my ST2000DX001 as 0MB. The disk some times did spin (with a delay) on system startup and some times did not.
After a few days and without doing anything special the Hdd now does not spin and not recognized at all.

i found an exact same pcb with number 100716565 REVA (but from an 1TB hdd) and copied the fw data from my disk but the disk still does not spin.
Also i have downloaded a same CC43 firmware and tested it to see if is going at least to spin but it does not.
When i use the firmware from the ST1000DX001 1TB board i found, the disk spins and recognized as an 1TB but as expected is not working.

I was planning to transfer the chip to see if it is going to make any difference but it has a physical damage from someone that tried to remove it.
Vcc pin is missing but i can still read the data if i need. The firmware data was backed up and verified before the damage was done.

i noticed that the the disk was spinning in first place ONLY when i had the ATA cable connected too.
When i use the 1TB firmware it spins with cable power only just like other disks usually do.

Bellow are my disk specs and data.
i will appreciate if anyone can guide me what else to do before sending it to a recovery lab.

Thanks in advance.
A.

MODEL: ST2000DX001 2TB SSHD
FW: CC43 (attached in the message)
PCB: 100716565 REVA
PN: 1CM164-500
SN: Z1E8MZNA
DATE: 15047
WWN: 5000C50078FE6D54
FW chip: Winbond 25Q80BWS09

Attachments

ST2000dx001.7z

my original firmware

(578.25 KiB) Downloaded 493 times

[unknown]

This is SSHD and most likely a NAND issue.

Contact Northwind, I believe they can help you.

[cocovios]

Hi,

in case the Nand is good and you make a pcb swap, is it necessary to transfer (except the fw chip) the Nand flash also?

A.

[unknown]

Post a terminal output with native (PCB+ROM)

[cocovios]

please give some more details of what to do
as i understand you want me to post some data by connecting the "original" pcb through the serial connector?

[cocovios]

here it is.


Bridge PLL Enable Failed
Bridge PLL Enable Failed
Bridge PLL Enable Failed
Bridge PLL Enable Failed
ERROR: Flash Led 9C08 - ALF Hardware Initialization Process Failed
Flash HW Init Attempts = 0004

Clump Parametrics:
Clump = C224
DataType =

[saltwater]

Can't initialize NAND, so the NAND is NOT good.
The ROM transfer to another PCB is not enough for SSD drives.
Try disable NAND in ROM's IAP seggment using F3ROM explorer.

[cocovios]

hi Saltiwater,

where can i download this software?
does this software require some kind of special equipment or i can use it through the serial connection?

A.

[cocovios]

Hi saltwater,

F3ROM explorer is a terminal application or the command interface?
i am using putty and after those errors prompted it does not respond when i am trying to type anything

A.

[unknown]

You will need to backup the patient ROM then use the app then upload it again after modification.

[fzabkar]

Doesn't "Bridge PLL Enable Failed" mean that the MCU is unable to communicate with the ASIC?

[fzabkar]

See this thread:

https://forum.hddguru.com/viewtopic.php?p=275459#p275459

The OP was able to provoke a "Bridge PLL Enable Failed" error by disabling the 3.3V supply for the NAND IC. I would check this voltage.

I would check the output voltage of the small "1L05" IC at the left hand edge of the PCB:

https://sep.turbifycdn.com/ay/yhst-14437584971410/91606159-15.gif

ST1L05CPU33R, ST Microelectronics, LDO regulator, 3.3V, 1.3A, marking 1L05C33:
http://www.st.com/web/en/resource/technical/document/datasheet/CD00186925.pdf

Upload a photo of your PCB if you need more help.

[saltwater]

1.Read ROM with terminal in boot code mode
2.open saved ROM with F3 ROM Explorer. (F3 rom application does not communicate with your drive)
3.open IAP segment in F3 ROM explorer, and fill all bytes with "FF" except the first line.
4.recalculate checksum, and save new ROM to file.
5.upload the updated new rom to PCB with boot code mode, and do a power reset.

[fzabkar]

I think is what @saltwater wants you to do (see attached ROM).

Attachments

new_rom.7z

(578.24 KiB) Downloaded 496 times

[cocovios]

I will try all of the above this weekend and I will let you know. I found the chip. I am sending also a photo of the pcb.

Also i have replaced the fw chip with a new one because the original one was physically damaged.

The terminal does not respond to ctrl z or anything else to do anything so I copied the data from the chip using a usb eprom programmer.

is that ok with the programmer or do i have to use the F3 console?
can i do all the the changes to my file with a hex editor and write it back to the chip?

many thanks to all of you!!
A.

Attachments

[cocovios]

I think is what @saltwater wants you to do (see attached ROM).

Fzabkar is that my original firmware file modified like saltwater said or it is just a sample?

[fzabkar]

I modified your ROM according to @saltwater's instructions. Go ahead and use it.

[cocovios]

thanks fzabkar. i did but with no effect.it prompts the same data to the terminal.

[cocovios]

See this thread:

https://forum.hddguru.com/viewtopic.php?p=275459#p275459

The OP was able to provoke a "Bridge PLL Enable Failed" error by disabling the 3.3V supply for the NAND IC. I would check this voltage.

I would check the output voltage of the small "1L05" IC at the left hand edge of the PCB:

https://sep.turbifycdn.com/ay/yhst-14437584971410/91606159-15.gif

ST1L05CPU33R, ST Microelectronics, LDO regulator, 3.3V, 1.3A, marking 1L05C33:
http://www.st.com/web/en/resource/technical/document/datasheet/CD00186925.pdf

Upload a photo of your PCB if you need more help.

At pin 4 i get 3.3 and at pin 6 i get 5v

[fzabkar]

Measure the voltages at the two test points.

Attachments