wd10jmvw - not id family - unsupported?

[drdoc]

wd10jmvw usb 2.5 inch - is this not supported?

I have a new drive that works but pc3k doesnt id family.

Is there an update or similar which works

[drdoc]

ok by isolating the heads I got it to id as a fblite

[drdoc]

ok so kinda worked...

my drive clicks and spins down but family ids.
but cant read ram or rom
so it looks unsupported
Techno mode key
Techno mode key......................... : Ok

Debug Stop Code......................... : HOST DEBUGSTOP UNEXPECTED HBI INTS UNMASKED

RAM:
HDD Info reading........................ : Ok
Heads number............................ : 1
Cyl Count............................... : 256

Zone allocation table................... : HDDs RAM reading error VSC Command sending error Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended"

ROM:
ROM reading............................. : Ok
ROM Data size........................... : 256 Kb
ROM version............................. : 16.1CH
ROM generation.......................... : 16.1CH
Link table version...................... : NB.18.
Consolidated ROM version................ : 0016001C

ROM Modules:
Flash ROM dir reading................... : Ok (Active)
Flash ROM dir reading (Ext)............. : Ok
Modules directory address............... : 109 650
SA regions address...................... : by default
SA Translator loading................... : Ok

Heads configuration..................... : by map
Heads number............................ : 4
Heads number in use..................... : 4
Switched off heads...................... : No
Heads map............................... : 0,1,2,3
ROM Firmware version.................... : 0016001C

Service area:
Permanent overlay....................... : Not loaded
SA dir reading (ID)..................... : Ok
SA Access............................... : NONE

Configuration reading................... : Module 02 not found

COM PIO data in command sending error Unknown packet type BEEF01000000133F
View ROM information
HDDs ROM reading error Data request error VSC Command sending error Device Error Detected: "Unknown error. Error code: 3742"
HDDs RAM reading error VSC Command sending error Unknown packet type BEEF270008000123

[drdoc]

try #3
ok no drive clicks and spins down - bad heads or media
auto detect usb comport
ids drive and wants to start in NORMAL mode
this doesnt work
change to kernel mode.
now I can read rom and rom modules and hd info
ram head map editting doesnt work
and once you get it stuck you have to repower

Techno mode key
Techno mode key......................... : Ok

RAM:
HDD Info reading........................ : Ok
Heads number............................ : 4
Cyl Count............................... : 256

ROM:
ROM reading............................. : Ok
ROM Data size........................... : 256 Kb
ROM version............................. : 16.1CH
ROM generation.......................... : 16.1CH
Link table version...................... : NB.18.
Consolidated ROM version................ : 0016001C

ROM Modules:
Flash ROM dir reading................... : Ok (Active)
Flash ROM dir reading (Ext)............. : Ok
Modules directory address............... : 109 650
SA regions address...................... : by default
SA Translator loading................... : Ok

Heads configuration..................... : by map
Heads number............................ : 4
Heads number in use..................... : 4
Switched off heads...................... : No
Heads map............................... : 0,1,2,3
ROM Firmware version.................... : 0016001C


Code type to check...................... : TypeN
Code addr............................... : FFE00000
Code size............................... : 327681
Code reading............................ : RAM Range FFE00000 (050001) reading error VSC data reading error Sectors receiving error Data receiving error No response
No HDD RAM access, LDR upload is recomended

[Nick_TS]

Hello!

Yes, that is a problem for USB 3.0 WD drives. Not all of them are supported.
I can offer only one solution with connecting SATA interface onto these drives board.

[drdoc]

ok I can attach a sata board but I usually read the rom first

then write the patient rom to sata board.

Do I have to transplant the chip in this case?

[Nick_TS]

Hello!

A compatible PCB from a regular SATA HDD can be installed on a USB WDC Marvell drive to allow access over the SATA interface. To do so you will have to transfer the native firmware from the USB HDD to the SATA board.
Installation of a donor board is only possible if the USB board contains an external U12 ROM chip soldered onto it.
In that case the donor PCB should be borrowed from the same drive family and it should also have an external ROM chip installed.
To adapt the SATA board for the target drive, you have to solder the U12 ROM chip from its original USB board to the SATA donor board.

[rezafarah]

hi Dima.
usually usb3 pcb's contain 2 ROM chips(2 similar IC's beside each other),can you explain how to deal with this cases when we want to change usb pcb with sata pcb?
thank you

[Nick_TS]

Dear Reza Farah,

There are two chips:
- U12 (ROM);
- U14 (encrypted chip) For example, it could be JM, Symwave or Initio chips.

SATA saves data is really encrypted by encryption chip on PCB. To decrypt the data is usually used MyBook USB-SATA boards with the same encryption chip onboard.

In new PC-3000 version will be realised software decryption from MyBook and MyPassport drives in Data Extractor.

[AJ2008]

In new PC-3000 version will be realised software decryption from MyBook and MyPassport drives in Data Extractor.

When will this be available? And will it support all encryption bridges from all passports and mybooks?

[datasolution]

Dear Reza Farah,

There are two chips:
- U12 (ROM);
- U14 (encrypted chip) For example, it could be JM, Symwave or Initio chips.

SATA saves data is really encrypted by encryption chip on PCB. To decrypt the data is usually used MyBook USB-SATA boards with the same encryption chip onboard.

In new PC-3000 version will be realised software decryption from MyBook and MyPassport drives in Data Extractor.

HI DIMA,
I HAVE SAME PROBLEM I HAVE WD10TMVW-11ZSMS5 . I HAVE CONVERT IT TO SATA .I CAN SEE HDD WITH SATA BOARD BUT AGAIN FAIL TO FIND FAMILY BY AUTO DETECT AND SO THAT I AM NOT ABLE TO SA ACCESS.CAN U PLS TELL ME ANYTHING ABOUT IT.WHAT SHOULD I DO ?AND IN ANOTHER SAME DRIVE I AM ABLE TO GET ACCESS OF SA FROM SAME DRIVE.I CAN SEE HEAD 4 IN THAT DRIVE IS BAD.IN DE I HAVE DISABLED HEAD .BUT AS THIS IS SATA SO I CANT SEE DATA FROM IT.CAN YOU PLS TELL ME HOW DO I IMAGE THIS SECTOR BY SECTOR TO ANOTHER SATA OR USB DRIVE .I MEAN TO SAY MAKE IMAGE TO DESTINATION WHAT SHOULD I CHOOSE?TO DECRYPT THIS IMAGE WITH ANOTHER MY BOOK SATA CONTROLLER.DO I CHOOSE FILE IMAGE OR ANOTHER DISK ? PLS TELL ME AS I AM TOO MUCH CONFUSE.IF I USE ANOTHER SAME WD USB 3.0 HDD TO EXTERNAL USB PORT AND I SELECT THAT DRIVE AS DESTINATION AND START IMAGE AND THAN AGAIN MAKE NEW TASK AND TRY TO RECOVER THAT DATA, IS IT DECRYPTED ?IS IT POSSIBLE ?THANKS IN ADVANCE FOR REPLY.I KNOW I HAVE ASKED TOO MANY CONFUSING QUESTION.BUT PLS TRY TO HELP ME.

[VaibhavS]

Hello All,

I have this problem after Changing PCB to SATA and ROM chip

Make WD 2.5'' SATA
Model WD10JMVW
Size 1 TB
FW Not seen
Symptoms On Power ON-- Clicking Sound 6 time then Two time then Two time.. the Ready


Techno mode key
Techno mode key......................... : Ok

RAM:
HDD Info reading........................ : Ok
Heads number............................ : 4
Cyl Count............................... : 256

Zone allocation table................... : HDDs RAM reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended"

ROM:
ROM reading............................. : Ok
ROM Data size........................... : 256 Kb
Flash ROM dir reading................... : Ok (Active)
Flash ROM dir reading (Ext)............. : Ok
Modules directory address............... : 105 387
SA regions address...................... : by default
SA Translator loading................... : Ok

ROM Modules:
ROM version............................. : 06.0MH
ROM F/W version......................... : 0006000M
Overlay F/W version..................... : 06.0MH
Servo F/W version....................... : N0.0V

Heads configuration..................... : by map
Heads number............................ : 4
Heads number in use..................... : 4
Switched off heads...................... : No
Heads map............................... : 0,1,2,3

Service area:
Permanent overlay....................... : Not loaded
SA dir reading (ID)..................... : Unknown error code: 5496
SA SPT Detect........................... : FAIL
SA dir reading (ABA/CHS)................ : Module reading error: ABA 484 267(1) reading error Physical read error C/H/S: -46/1/388 Device Error Detected: "VSCE KEY SECTOR MUST PRECEED DATA XFER REQUEST"
SA Access............................... : NONE

Configuration reading................... : Module 02 not found

[Maxim_TS]

Hello VaibhavS,

If the drive doesn't start, the problem could be in bad heads or damaged SA modules.
To check the heads try to change head map in RAM first.
To check the SA you can block SA access and run the utility with shifted SA regions.
Then uoload a loader and check the SA.

[VaibhavS]

Thanks for reply sir,

I successfully recovered DATA,
I first time done this PCB USB to SATA change process..
Now I'm trying the on second model..

[protech]

Thanks for reply sir,

I successfully recovered DATA,
I first time done this PCB USB to SATA change process..
Now I'm trying the on second model..

Hi VaibhavS,

I have the same drive an FBLite 2.5 that shows the same symptoms. Patient PCB is a 771961-001 REV A and the donor PCB is a 771960-000 REV P2, after writing ROM on the donor PCB the drive fails to id at all, no MDL, no Serial...nothing but it gets DRD DSC. Could you please elaborate on how you were able to recover yours. I was thinking may be the PCB is not a perfect match or...

Thanks