Posts

Within the new DFL-DDP data recovery software, users can set sector mark easily for ‘all sectors 0’ areas. This feature is very helpful to get lost data from WD SMR hard drives.

‘All sectors 0’ failure has two situations:

The 0 sectors have data and the 0 sectors don’t have data. It’s normal many sectors are 0, empty and no data at all;
For WD SMR hard drives, many 0 sectors may contain real data which is controlled by the dynamic translator module 190.

In real cases, it’s not possible to tell which 0 sectors have data or not and therefore, users need to mark these sectors and put them aside.

Next the engineer ticked the WD SMR all sectors 0 mark, went to set up head map, image good heads, image good sectors first or load 190 automatically to image; After the first round of image, users can edit the disk image settings, for example change the read block size to smaller, disable pre-read, change to lower-rated data transfer mode, etc. After these settings, users can image all the 0 sectors again.

By above method, users can definitely get more data back from the WD SMR hard drives.

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

One more WD SMR HDD WD40EZAZ-00SF3B0 was recovered by DFL-WD hdd repair tool and DFL-DDP data recovery equipment.

Before repairing the second-translator module 190, the hdd had only 0.2GB data remained, the engineer got the following report:

2022/11/02 09:12:43 —T2 analysis—
2022/11/02 09:12:43 —————————-
2022/11/02 09:12:43 Check SIT:
2022/11/02 09:12:43 SIT Check…OK!
2022/11/02 09:12:43 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:43 Traversal completes
2022/11/02 09:12:43 ***Tree root node no. error(Tree=7507,File=7942)
2022/11/02 09:12:43 —Param—
2022/11/02 09:12:43 T2 Format:LBA64V2
2022/11/02 09:12:44 Capacity 512:7814037168
2022/11/02 09:12:44 Capacity 4K:976754646
2022/11/02 09:12:44 Root:7942
2022/11/02 09:12:44 Entry pre node:29
2022/11/02 09:12:44 Max entry sects:65535
2022/11/02 09:12:44 Node size:256
2022/11/02 09:12:44 —Summary—
2022/11/02 09:12:44 Node count:198850
2022/11/02 09:12:44 Used count:13005
2022/11/02 09:12:44 Free count:185845
2022/11/02 09:12:44 —T2 modules—
2022/11/02 09:12:44 T2 size:50905696
2022/11/02 09:12:44 Data pos:13C6800
2022/11/02 09:12:44 Block size:4096
2022/11/02 09:12:44 Free Node ID:24183
2022/11/02 09:12:44 Entry Count:14967
2022/11/02 09:12:44 Used Entry:46
2022/11/02 09:12:44 Total node count = 198850 Used:13005
2022/11/02 09:12:50 Sort LBA
2022/11/02 09:12:51 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:51 Valid data = 0.20(GB) Unallocated = 3725.83(GB)
2022/11/02 09:12:51 Vacant Nodes:>=0

After repairing the module 190, the report change to repaired status as below:

2022/11/02 09:12:43 —T2 analysis—
2022/11/02 09:12:43 —————————-
2022/11/02 09:12:43 Check SIT:
2022/11/02 09:12:43 SIT Check…OK!
2022/11/02 09:12:43 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:43 Traversal completes
2022/11/02 09:12:43 ***Tree root node no. error(Tree=7507,File=7942)
2022/11/02 09:12:43 —Param—
2022/11/02 09:12:43 T2 Format:LBA64V2
2022/11/02 09:12:44 Capacity 512:7814037168
2022/11/02 09:12:44 Capacity 4K:976754646
2022/11/02 09:12:44 Root:7942
2022/11/02 09:12:44 Entry pre node:29
2022/11/02 09:12:44 Max entry sects:65535
2022/11/02 09:12:44 Node size:256
2022/11/02 09:12:44 —Summary—
2022/11/02 09:12:44 Node count:198850
2022/11/02 09:12:44 Used count:13005
2022/11/02 09:12:44 Free count:185845
2022/11/02 09:12:44 —T2 modules—
2022/11/02 09:12:44 T2 size:50905696
2022/11/02 09:12:44 Data pos:13C6800
2022/11/02 09:12:44 Block size:4096
2022/11/02 09:12:44 Free Node ID:24183
2022/11/02 09:12:44 Entry Count:14967
2022/11/02 09:12:44 Used Entry:46
2022/11/02 09:12:44 Total node count = 198850 Used:13005
2022/11/02 09:12:50 Sort LBA
2022/11/02 09:12:51 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:51 Valid data = 0.20(GB) Unallocated = 3725.83(GB)
2022/11/02 09:12:51 Vacant Nodes:>=0
2022/11/02 09:13:20 —T2 analysis—
2022/11/02 09:13:20 —————————-
2022/11/02 09:13:20 Check SIT:
2022/11/02 09:13:20 SIT Check…OK!
2022/11/02 09:13:20 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:13:20 Traversal completes
2022/11/02 09:13:20 —Param—
2022/11/02 09:13:20 T2 Format:LBA64V2
2022/11/02 09:13:20 Capacity 512:7814037168
2022/11/02 09:13:20 Capacity 4K:976754646
2022/11/02 09:13:20 Root:8192
2022/11/02 09:13:20 Entry pre node:29
2022/11/02 09:13:20 Max entry sects:65535
2022/11/02 09:13:20 Node size:256
2022/11/02 09:13:20 —Summary—
2022/11/02 09:13:20 Node count:198850
2022/11/02 09:13:20 Used count:22503
2022/11/02 09:13:20 Free count:176347
2022/11/02 09:13:20 —T2 modules—
2022/11/02 09:13:20 T2 size:50905696
2022/11/02 09:13:20 Data pos:13C6800
2022/11/02 09:13:20 Block size:4096
2022/11/02 09:13:20 Free Node ID:22504
2022/11/02 09:13:20 Entry Count:476879
2022/11/02 09:13:20 Used Entry:475696
2022/11/02 09:13:20 Total node count = 198850 Used:22503
2022/11/02 09:13:22 Sort LBA
2022/11/02 09:13:22 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:13:22 Valid data = 3708.95(GB) Unallocated = 17.07(GB)
2022/11/02 09:13:22 Vacant Nodes:>=0

After repairing module 190, the user wrote the new module 190 to patient HDD and then users get 3708.95(GB) data back by DFL-DDP data recovery equipment.

Any question is welcome to [email protected] or add Dolphin Skype iD: dolphin.data.lab

This is one WD SMR HDD WDC WD40EDAZ-11SLVB0 data recovery case by one client who was using other data recovery tools but failed and finally bought Dolphin data recovery tools to fix the SMR HDD format case and get most data back.

The engineer helped the user to backup the second level translator-module 190 by DFL WD HDD repair tool and then go to DFL DDP data recovery equipment, repair 190.

Before repairing 190, all the data nodes records remained in module 190 indicates the valid data is only 15.01GB after format and the user couldn’t get lost data back at all,the user tried all methods and tools he had.

After repairing the 190 by DFL-DDP data recovery equipment, the engineer got the following result:

2022/10/25 09:41:14 —T2 analysis—
2022/10/25 09:41:14 —————————-
2022/10/25 09:41:14 Checking SIT:
2022/10/25 09:41:14 SIT Checking…OK!
2022/10/25 09:41:15 **********Vacant nodes count = 0 Overlapped nodes count = 0
2022/10/25 09:41:15 Traversal completes
2022/10/25 09:41:15 —Param—
2022/10/25 09:41:15 T2 Format:LBA64V2
2022/10/25 09:41:15 Capacity 512:7814037168
2022/10/25 09:41:15 Capacity 4K:976754646
2022/10/25 09:41:15 Root:8192
2022/10/25 09:41:15 Entry pre node:29
2022/10/25 09:41:15 Max entry sects:65535
2022/10/25 09:41:15 Node size:256
2022/10/25 09:41:15 —Summary—
2022/10/25 09:41:15 Node count:198850
2022/10/25 09:41:15 Uesd count:38690
2022/10/25 09:41:15 Free count:160160
2022/10/25 09:41:15 —T2 modules—
2022/10/25 09:41:15 T2 size in sectors:455808
2022/10/25 09:41:15 Data pos:13C6800
2022/10/25 09:41:15 Block size:4096
2022/10/25 09:41:15 Free Node ID:38691
2022/10/25 09:41:15 Entry Count:781243
2022/10/25 09:41:15 Used Entry:620135
2022/10/25 09:41:15 Total node count = 198850 Used:38690
2022/10/25 09:41:48 Sort LBA
2022/10/25 09:41:51 **********Vacant nodes = 0 Overlapped nodes = 0
2022/10/25 09:41:51 Valid data = 3544.93(GB) Unallocated = 181.09(GB)
2022/10/25 09:41:51 Vacant nodes count:>=0

Finally about 3.5T data was recovered from the WD SMR hard drives.

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

T2Data auto loading to RAM is one featured data recovery solution within DFL-DDP data recovery equipment for WD SMR hard drives. Users can find this data recovery solution within the common WD hdd repair column or disk image settings.

Dolphin DFL users can backup T2data by DFL-WD hdd repair tool or users can extract the T2data from the module 190 within DFL-DDP data recovery equipment.

When the WD SMR hard drives are all sectors 0000 or data area is not accessed, users can try to load the T2data auto to RAM for access to the data.

Here is the video on how to load T2data auto to RAM for WD SMR HDD data recovery

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

Most WD SMR HDD data recovery cases are concerned with the second-level dynamic translator-module 190.

For example, the WD SMR HDDs are formatted, all sectors 0000, wrongly detected, no data access, etc. Users can try to backup the module 190, repair 190, load module 190 to ram to fix the issue.

For all Dolphin DFL users, it is much easier and more successful to recover WD SMR HDDs. In the video below, users can learn how to use DFL-WD firmware repair tool to backup the module 190 in different ways.

01: Double click module 190, select all hex data and then save as 190.rpm;
02: FW Operations>Read Modules>Read Module 190 by ID mode;
03: FW Operations>Read Modules>Read Module 190 by ABA mode, read copy 0 or copy 1, sometimes copy 0 fails, then try to read copy 1, sometimes if both copies fail, try read valid data only;
04: Read SA regions and users can try to extract module 190 from the SA region.

Users can find detailed steps and instructions on how to backup WD SMR HDD second level translator module 190 here.

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

For data recovery from all WD SMR HDDs, it’s necessary to learn how to read the original rom, how to generate unlock rom, how to write unlock rom and unlock firmware area, how to backup firmware resources.

Tools used for WD SMR HDD Firmware Unlock and Backup:
DFL-WD HDD firmware repair tool
HDD ROM chip pin reader

Users can learn from the video here on how to do all above

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

WD SMR 2060-810035 Spyglass II HDDs have both MCU lock and SED lock. To repair firmware corruption and recover lost data, users need to fix the MCU lock first: swap with special 2060-810035 firmware unlock PCB or writing unlock rom to bypass the MCU lock by DFL-WD hdd repair tool.

Please note: not all 810035 PCBs support MCU lock bypass by unlock ROM.

Most common HDD failures for WD SMR 2060-810035 Spyglass II HDDs:

The data area is not accessed;
The data area is full of 0000;
The drive is undetected due to 190 corruption;
Physical head damage.

Most common functions and solutions used in repairing and recovering WD SMR hard drives:

Read/write ROM by HDD ROM Chip Pin Reader;
Generate unlock ROM by DFL WD hdd repair tool;
Sort nodes within module 190 by LBA/tree;
Scan missing nodes;
Delete overlapped nodes/wrong nodes;
Repair wrong nodes, etc.

Users can save all the modification to one new module 190 and then users can write the new module 190 or load the module 190 or T2data to RAM by DFL-DDP data recovery equipment for immediate data recovery.

WD SMR 2060-810035 Spyglass II HDD Common PCB number and Models:

PCB number: 2060-810035-000 REV P0

WD40NDZW-11BCSS0 USB 3.0
WD40NDZW-11A8JS0
WD40NDZW-11A8JS1
WD40NMZW-59A8NS1
WD40NMZW-59BCBS1
WD50NDZW-11A8JS1
WD50NMZW-59BCBS0
WD50NMZW-11BCBS0
WD50NMZW-59A8NS1
WD50NDZW-11BCSS0

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

Dolphin team has released new DFL-WD hdd repair software and new DFL-ST HDD repair software and users can download these new software from Dolphin user-only forum. With the new DFL-WD hdd repair software, users can further enhance the WD SMR HDD data recovery success rate.

With the new software, users can unlock more WD SMR HDDs by the original PCB without using special firmware unlock PCB, 800041, 800066, 800077, 800069, 810011, 810035, etc.

With the new software, users can fix more WD SMR hdd format cases, more all-sector-0000 cases, inaccessible data area cases, etc.

Users can download the latest WD hdd repair software from the forum.

More WD SMR HDD repair and recovery cases and tips below:

WD SMR HDD WD20EZAZ 810011 DATA RECOVERY CASE BY DFL USER IN SRI LANKA;
WD SMR 800077 CARMEL HDD REPAIR AND DATA RECOVERY STEPS
WD SMR 800065 800067 810003 CHARGER HDD REPAIR AND DATA RECOVERY SOLUTIONS
WD 800069 800066 SMR PALMER HDD REPAIR AND DATA RECOVERY SOLUTIONS
WD SMR SPYGLASS SPYGLASS2 800041 HDD REPAIR AND DATA RECOVERY STEPS

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab

This data recovery case study is shared by one of our experienced, smart, friendly and kind users from Sri Lanka, his name is Dananjaya who offers very professional data recovery services in Sri Lanka.

HDD ID Information:
Patient drive: WD20EZAZ
PCB: 2060-810011

Reported symptoms
According to the drive owner, when he was copying wedding pictures to HDD, windows OS popup error massage called “not enough space”

HDD Repair and Recovery steps:

1.Once our user received the HDD, he checked. He found that when power on HDD, it spin up, but then two times’ clicking and power down. Like platter damage;
2.He tried to unlock, but same scenario. No modules showed, only power up, two clicks, power down;
3.So he guess it can be module damaged. But couldn’t power up. He used only pcb and disable module 02, module 411 and kernel mode. But same clicking;
4.He found a donor PCB with same microcode HDD. Then used patient PCB to donor for test, donor drive can be detected as normal;
5.He put donor to PAITENT HDD. Luckily the patient drive can be detected. But after 10 seconds, gave one click and went to busy status. Not responding;
6.He managed to power on and off till enter the inside of FW program;
7.He disabled module 02. After doing that HDD shows module and no clicking. But once enabling module 02, start clicking again. He had to disable again to get all modules;
8.He edited module 02 manually and write it SA. Fortunately no clicking, smoothly worked with HEX 00;
9.DFL repaired the corrupted module 190, he then wrote it to SA and load to RAM. “missing node function ” and “repair nodes function” which built in version 2.31 were used for this case;
10. Two partitions are displayed properly, the image speed is quite good, up to 150M per second.

HDD Repair and Data Recovery Equipment used in this data recovery case study:

DFL WD HDD Repair Equipment
DFL-DDP Data Recovery Equipment

Welcome to send your questions or enquiry to [email protected] or add Dolphin Skype ID: dolphin.data.lab for any consultation.

How to recover lost data from WD SMR 800077 Carmel patient hard drives?
2060-800077-003 HDD Family: CARMEL

WD CARMEL HDD Failure Types:

SED lock and MCU lock;
Weak heads
Slow issue by firmware corruption;
All sectors 0;
Inaccessible data area;

Common Functions to be used to repair and recover lost data from WD SMR Carmel HDDs

HDD ROM chip pin reader to read/write ROM content;
MCU unlock ROM generation;
Disable 411;
Sector response time modification;
T2Data backup;
SMRzone backup;
190 backup, repair(Scan missing nodes, repair wrong nodes, delete overlapped nodes, etc ), write, ram loading(T2 auto loading);
Head map set up;
etc

WD CARMEL HDD Models:

WD60EDAZ-11BMZB0 2060-800077-003 REV P1
WD60EMAZ-51TKPB0 2060-800077-003 REV P1
WD60EZAZ-00ZGHB0 2060-800077-003 REV P2
WD60EFAX-68SHWN0 2060-800077-003 REV P1

WD20EZAZ-00GGJB0 2060-800077-003 REV P1

To repair and recover lost data from WD SMR Carmel hard drives, users need to have the following hdd repair tool and data recovery equipment:

HDD ROM Chip Pin Reader
DFL-WD HDD Repair Tool
DFL-DDP Data Recovery Equipment

WD SMR Carmel HDD Repair and Data Recovery Steps:
DFL-URE AND HDD ROM CHIP PIN READER HELP WITH EASIER WD SMR HDD FIRMWARE UNLOCK

Helpful links:

WD 2060-800077 WD20EZAZ HDD Firmware Unlock PCB

Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab