PC-3000 Forum

Hi guys.
I have a WD40NDZW-11BCSS0 that is not recognized.
This was taken out of a WD MyPassport for Mac that was brought into My lab.
The PCB was 2060-810035 with a USB interface but the PC-3000 utility recognized it as Spyglass3 but it did not read the ID and showed 0MB () capacity.
I guessed that the translator was corrupted.
I knew that Spyglass had a locked PCB, so I lead-wired USB PCB's 1,2 ,3, and 5 to SATA connector 7pin's 2, 3, 5 and 6 based on the information in this forum.
The PC-3000 utility shows the following:
Techno mode key
Techno mode key......................... : Ok
HDD Status sector....................... : Ok
RAM:
System controller (SoC)................. : 88i1054A1 0x(5471)
HDD Info reading........................ : Ok
Heads number............................ : 8
Cyl Count............................... : 384
ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 755 572
SA regions address...................... : by default
SA Access check in RAM.................. : Static module reading error Device Error Detected: "VSC ERR INV FUNC CODE REQ"
Module 02 access........................ : Granted
Zone allocation table................... : HDDs RAM reading error Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended"
SA SPT.................................. : 500
SA Translator loading................... : Ok
SA defects assigned..................... : 9
ROM Modules:
ROM version............................. : 00.0AB
ROM F/W version......................... : 0000000A
Overlay F/W version..................... : 00.0AB
Servo F/W version....................... : 03.7T
Heads configuration..................... : by map
Heads number............................ : 8
Heads number in use..................... : 8
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5,6,7

Relocations............................. : 0 (0)

Service area:
Power up log reading.................... : Ok
Dir data................................ : No
Permanent overlay....................... : No
CFG data................................ : No
SA dir reading (ID)..................... : Module ID 01 reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
SA SPT Detect........................... : FAIL
SA dir reading (ABA/CHS)................ : Module 01 reading error: ABA 755 572 C:1(1) reading error Device Error Detected: "VSC ERR UNSUP ACTION CODE"
SA Access............................... : Copy 0,Copy 1
Configuration reading................... : Module ID 02 reading error Device Error Detected: "FM ERR NOT FOUND IN DIR"



I would like to upload the loader and work on restoring T2, does anyone have a loader for this ROM version of Spyglass3?
thank you.

ROM version............................. : 00.0AB
ROM F/W version......................... : 0000000A
Overlay F/W version..................... : 00.0AB
Servo F/W version....................... : 03.7T

Did you run the unlock ROM routine in the latest version of the software? You need to do that first.

msurgeon, Thanks for the reply!
Yes, you are correct.
I used the following blog post to do the ROM unlock routine using a ROM programmer.
https://blog.acelab.eu.com/pc-3000-for- ... board.html

When I did that, the HDD ID did not show up and the capacity was 0 MB (), so I am going to use the following blog post to fix the T2.
https://blog.acelab.eu.com/how-to-fix-t ... rsion.html

Thank you.

Do you still need the firmware modules for this case?

I think I need a compatible Mod 2 or LDR for this drive if anyone has one, they will share.
If anyone has a better option for me to recover the data from this drive. Please let me know. I have not had this particular issue before.
I have already unlocked the ROM.

WD50NDZW-11BCSS0

RAM:
System controller (SoC)................. : 88i1054A1 0x(5471)
HDD Info reading........................ : Ok
Heads number............................ : 10
Cyl Count............................... : 384

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 755 572
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted

SA SPT.................................. : 2016

SA Translator loading................... : Ok
SA defects assigned..................... : 10

ROM Modules:
ROM version............................. : 00.0AB
ROM F/W version......................... : 0000000A
Overlay F/W version..................... : 00.0BB
Servo F/W version....................... : 03.7T

Heads configuration..................... : by map
Heads number............................ : 10
Heads number in use..................... : 10
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5,6,7,8,9

Relocations............................. : 0 (2 442)

Service area:
Power up log reading.................... : Ok
Dir data................................ : Yes
Permanent overlay....................... : Yes
CFG data................................ : No
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 647

SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Module 02 reading error: ABA 660 126 C:1(1) reading error VSC Command error: DISK DAM ERROR
UA writing.............................. : Granted

try reading 02 with ignore read error, probably you will see first 512 bytes only with DE AD and rest of module is ok?
replace entire 02 module will likely not give you a good result. Better to try repair 02 by retaining as much original information as possible from it

I replaced 02 with one from a compatible one and got access to the users data.