Western Digital WD10JMVW Data Recovery

We offer professional data recovery services for WD10JMVW hard drives. If your Western Digital drive has failed or is no longer being detected, we can help. We accept mail-in jobs Australia-wide, and our expert team is equipped to recover data from even the most complex cases.

WD10JMVW Common Problems

• Drive not detected or spinning up with no response
• Slow or freezing when accessing files
• Clicking or beeping sounds from the drive
• USB-SATA bridge failure on integrated PCB
• Firmware corruption or translator issues
• Physical damage from drops or impact
• Water or liquid exposure
• Overheating or burnt components

WD10JMVW Models

• WD10JMVW-11AJGS0
• WD10JMVW-11AJGS1
• WD10JMVW-11S5XS1
• WD10JMVW-11S5XS0

WD10JMVW-11AJGS4 Data Recovery Case Log

1Nov23: The drive was freezing up the system. When you connected the usb cable to any computer it would freeze the computer. We could recover data from this drive and return it to the customer.

PCB 2060-771961-001 Rev B

WD10JMVW Head Stiction Data Recovery Caselog

This drive had stiction; the read/write elements and sliders on the original head stack are completely destroyed. After successfully replacing the MHA with parts from a compatible donor drive, the drive was able to spin up. It comes ready and we get a full ID. The drive reads quite slowly, after some time it gets stuck BSY, stops IDing and we no longer have SA or DA access. Resolved by uploading a compatible module 11 to RAM - the drive still runs slow but is able to read. Edited head map in RAM, enabling just H0 and H1 to read SA modules. Built a complete module 11 from copies with bad regions. Disabling bad heads allows DE to build it's head map OK, then can revert to default head map in RAM. H1 and H3 are good, imaged all the data on these. H0 and H2 are weak and have a lot of bad regions, so imaging is slow.

WD Elements USB Hard Drive Not Responding Case log

29Aug24 - A customer recently brought their hard drive to Zero Alpha Data Recovery, reporting a troubling issue: the drive, which had never been dropped or subjected to physical trauma, had simply stopped working. The drive intermittently clicks every five minutes but remains spinning continuously. Upon examination, it was noted that after about ten minutes, the drive appears in Drive Management as "Not Initialized." The PCB number, 2060-771961-001 Rev B, was recorded, indicating a potential issue with the drive's internal electronics or firmware. 

MRB hard drive but a lot of system files were damaged (24, 6F, 123, 124, 125, 126, D002, D003). Module 24 should be the most important, but heads cannot write. Attempted to fix files from Donor firmware and writing by ID.

Attempted Hotswap using 3 different compatible hard drives. Two hard drives not similar enough. Killed the last hard drive.

PCB 2060-771961-001 Slow Response Bug Case Log

Patient PCB (USB interface) is 2060-771961-001. This is compatible with the SATA PCB model 2060-771960-000. Our first step will be converting the drive to SATA interface.

1. Connect patient to terminal
2. Enter boot ROM mode
3. Read external ROM
4. Save to file
5. Connect 771960 to terminal
6. Enter boot rom mode
7. Write external rom from file
8. Physically swap the PCBs

Powering on the drive, we notice that it comes ready initially but goes (and stays) busy when we attempt to read the drive ID. This is a typical symptom of the slow responding firmware issue. To resolve this, we do the following:

1. Enter boot ROM mode
2. Write external ROM from the file we saved before, this time blocking access to ROM module 30 (SA translator)
3. Repower the drive
4. Start utility in kernel mode
5. Upload DIR and LDR to RAM
6. Make backup of SA (may need to restart utility in normal mode for this)
7. Apply slow response solution
8. Allow module 30 access (in ROM)
9. Repower drive
10. Restart utility

After this, the drive comes ready and is able to ID in a timely manner, ready for the data to be saved!

1.0TB WD10JMVW SED Locked Case Log

03Apr24 - Opened the external casing. 

03Apr24 - Did PCB swap to 771960. see page on how to transfer ROM

04Apr24 - The PCB was SED locked. Unlocked using this document

04Apr24 - Error when decrypting in utility. Need to open a task to decrypt

05Apr24 - Mapping and saving data

Apple MacBook WD10JMVW-11AJGS2 Bad Sector Data Recovery Caselog

11Apr24- WD10JMVW-11AJGS2. Very slow. A lot of BS. Sata Convert from 771961 to 771960. Goes busy when trying to MRB and clicks on Module 121. Went busy. Software reset - came ready. Made a task. Tried to build heads map-drive was very slow.

Check if heads can write like in this article. Heads could write. Saved module 32. Slow Response solution. Turned off the drive. Turned back on and entered utility.Drive is still slow. I had to give it 2 mins every time I tried to do something. However, I was able to partially MRB and it went fast. Drive still times out on some modules. Apply Slow Responding Parameter for the task like here . Omg, it worked!!! This Drive even if it is SED locked it does not need decryption!

Got these errors in the task: 

CatalogFile BTree header is invalid
(LBA + Count - 1) <0!partition_entry_array not read
Init Primary EFI_GPT failed
EFI_GPT_Header valid
Try [EFI_GPT_Header.alternate_lba]
[EFI_GPT_Header.alternate_lba] read OK
(LBA + Count - 1) <0!partition_entry_array not read
Init Secondary EFI_GPT failed

Solution:

Imaged the beginning of the drive and scanned in another program. It found HFS system and all folders and files. Imaged a bit more and it found all files and folders. 

Drive kept being slow. I turned in the Task if looses readiness: Turn off/on drive's power and it would turn itself off and back on and would image 100 mb/s.

Not detecting WD10JMVW-11AJGS1 Data Recovery Case log

30Sep24 : The customer reported that this drive would freeze and did not detect when they tried to copy their files. This hard drive has got hard ware issues and has to be modified. PCB# 71961.