| HDD GURU FORUMS http://forum.hddguru.com/ |
|
| WD palmer damaged rom file data recovery http://forum.hddguru.com/viewtopic.php?f=11&t=45702 |
Page 1 of 3 |
| Author: | tarasheh [ November 2nd, 2025, 3:04 ] |
| Post subject: | WD palmer damaged rom file data recovery |
I am attempting data recovery on a WD10SPZX drive using a PC-3000. I performed the following steps: 1. I read the ROM from the IC using an external programmer and saved a backup. 2. I used PC-3000 to unlock the sed lock with this backup. 3. I then soldered the ROM IC back onto the PCB. The Problem: Now, the drive will not turn on and spin up, and the PC-3000 shows no activity lights. Rewriting the original ROM file back to the IC results in the same issue, leading me to believe my programmer may have created a corrupted backup. Additional Info: When I try a different ROM file, the drive does spin, but it shows no model, serial number, and 0MB capacity. The data is critical. Could you please advise me on how to proceed? Thank you |
|
| Author: | Lukas [ November 3rd, 2025, 8:49 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
A caution for the future is to not modify the original batch. Always work with a replacement ROM chip. What programmer did you use? Include the original ROM dump on forum. |
|
| Author: | tarasheh [ November 3rd, 2025, 10:56 ] | ||
| Post subject: | Re: WD palmer damaged rom file data recovery | ||
oh thanks i will do that in future. I use TNM 5000 programmer
|
|||
| Author: | fzabkar [ November 3rd, 2025, 17:44 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
Code: Analysing WD10SPZX_orginal.bin ...
Searching for LDSCs and verifying PCMBlocks ... LDSC LDSC Att PCMBlock RAM size PCMBlk CS Start ID CS Start - End address RAM / ROM Exp/Act ----- -- -- -- ----- ----- -------- ------ ----- --------- 0 5A FB 04 20 - 1ACF 1000 1AAC 1AAC 000A7455 000A7455 OK (digitally signed) 2000 01 BF 04 2180 - 49DC 49688 275C 275C B2 B2 OK 2020 02 3B 11 49DD - 88E9 30080000 c 542C 3F0C 02 02 OK 2040 03 47 0C 88EA - 8CDE 24000000 3F4 3F4 D8 D8 OK 2060 04 60 40 8CDF - DF9B FFE00200 52BC 52BC FE FE OK 2080 05 9A 01 DF9C - EAA8 38248600 c D48 B0C E3 E3 OK 20A0 06 9B 04 EAA9 - EF49 3824A600 4A0 4A0 79 79 OK 20C0 07 F9 01 EF4A - 14F26 0 c 7A14 5FDC 5F 5F OK 20E0 08 A7 01 14F27 - 152E7 DD88 c 484 3C0 42 42 OK 2100 09 34 03 152E8 - 178E0 40340 c 3088 25F8 C6 C6 OK 2120 0A A0 03 178E1 - 17CB9 60249600 c 9AC 3D8 26 26 OK 2140 0B 2E 01 17CBA - 2FB7E 3832D000 c 20174 17EC4 52 52 OK 2160 0C 7F 01 2FB7F - 5415F 38008230 c 317EC 245E0 00 78 BAD LDSC = PM Loader Config String (32 bytes) ID = ID byte of LDSC (byte #0) CS = Checksum byte or word Att = Attributes PCMBlk = Program Code Memory Block Exp = Expected checksum for PCMBLock Act = Actual checksum for PCMBLock c = compressed PCMBlock size = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes No ROYL directory modules (0x0B or 0x20B) found in ROM |
|
| Author: | tarasheh [ November 4th, 2025, 1:56 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
Ok. How did you analyzing rom and how i can fix No ROYL directory modules (0x0B or 0x20B) found in ROM error? |
|
| Author: | fzabkar [ November 4th, 2025, 2:17 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
https://groups.google.com/g/datarecoverycertification/c/1JG6YtDdXHk/m/wC5T4dS7DgAJ |
|
| Author: | tarasheh [ November 4th, 2025, 3:19 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
The process I just saw in that group for hard drive repair was very different from the method I've always used. If you can, could you help me out? |
|
| Author: | fzabkar [ November 4th, 2025, 3:23 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
tarasheh wrote: The process I just saw in that team for hard drive repair was very different from the method I've always used. If you can, could you help me out? You have PC3K. I don't have anything other than a tool that I wrote to assemble the ROM from the modules that you recover from the SA (0x109 and 0x129). If you upload those modules, I'll rebuild the ROM for you. |
|
| Author: | tarasheh [ November 4th, 2025, 3:30 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
how can i get that module when hdd and pcb dosen't turn on. that rom file i get directly from ic with programmer not SA. |
|
| Author: | fzabkar [ November 4th, 2025, 3:33 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
Use a donor. |
|
| Author: | tarasheh [ November 4th, 2025, 3:43 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
I have a drive similar to this and i tried swap pcb and i got no model and 0mb capacity and my broken driver MDL end with 22z10t0 and driver similar to that end with 21z10t0 |
|
| Author: | tarasheh [ November 4th, 2025, 9:41 ] | ||
| Post subject: | Re: WD palmer damaged rom file data recovery | ||
I backup all module of 21z10t0 i think they simlar the only thing is diffrent is MDL module name are diffrent with pc3k i send you some of them i think it's right. if they are not correct tell me how can i send all of them to you
|
|||
| Author: | tarasheh [ November 4th, 2025, 11:53 ] | ||
| Post subject: | Re: WD palmer damaged rom file data recovery | ||
fzabkar wrote: Use a donor. I backup all module of 21z10t0 i think they simlar the only thing is diffrent is MDL I send some of the module i think you need. site don't let me send all of module
|
|||
| Author: | gold6565 [ November 4th, 2025, 18:16 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
tarasheh wrote: I am attempting data recovery on a WD10SPZX drive using a PC-3000. I performed the following steps: 1. I read the ROM from the IC using an external programmer and saved a backup. 2. I used PC-3000 to unlock the sed lock with this backup. You wouldn't be able to do this. You would receive a response from the PC-3000: Rom data corrupt. Sections CS error . |
|
| Author: | fzabkar [ November 4th, 2025, 20:02 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
109 is OK, but I need 129 (or 130 ?) as well. |
|
| Author: | fzabkar [ November 4th, 2025, 20:55 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
https://groups.google.com/g/datarecoverycertification/c/cOD2r7vxvXA/m/8tULZP-RAgAJ Tim - Desert Data Recovery wrote: I just ran the search again that I posted to include nested modules and 129 was still not found. It can only be found by ID.
|
|
| Author: | tarasheh [ November 5th, 2025, 2:44 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
gold6565 wrote: You wouldn't be able to do this. You would receive a response from the PC-3000: Rom data corrupt. Sections CS error . I don't know why, but the PC-3000 was able to unlock my corrupted ROM without showing any errors fzabkar wrote: 109 is OK, but I need 129 (or 130 ?) as well. I couldn't find that module. Instead, I've zip all accessible modules from the donor drive and uploaded the archive to a temporary site https://limewire.com/d/qAGpl#xEBN6YMtMj |
|
| Author: | fzabkar [ November 5th, 2025, 13:10 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
I can't find any backups of ROM-resident ROYL modules. Try a full track dump. |
|
| Author: | fzabkar [ November 5th, 2025, 13:58 ] |
| Post subject: | Re: WD palmer damaged rom file data recovery |
This is the relevant section in module 0x11: Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 000CADC8 52 4F 59 4C 01 80 30 00 ROYL.€0. 000CADDC 01 00 00 00 00 00 00 00 30 30 30 32 30 30 30 30 01 02 03 04 ........00020000.... 000CADF0 05 00 06 00 00 00 07 00 08 00 00 00 09 00 00 00 0A 00 00 00 .................... 000CAE04 10 00 12 02 40 00 5F 03 00 00 03 18 00 00 00 00 00 00 00 00 ....@._............. 000CAE18 00 00 12 02 01 00 20 00 00 00 03 18 80 42 00 00 00 00 00 00 ...... .....€B...... 000CAE2C 00 00 12 02 35 00 0A 00 00 00 03 1A 00 00 30 2C 0F 00 30 2C ....5.........0,..0, 000CAE40 0F 00 12 02 EF 00 1E 00 00 00 03 1A 00 00 82 2A 0F 00 82 2A ....ï.........‚*..‚* 000CAE54 0F 00 12 02 B5 11 10 00 00 00 03 1A 00 00 72 2A 0F 00 72 2A ....µ.........r*..r* 000CAE68 0F 00 12 02 90 00 90 01 00 00 03 1A 00 00 68 28 0F 00 68 28 ..............h(..h( 000CAE7C 0F 00 12 02 C0 00 7A 00 00 00 03 1A 00 00 F8 29 0F 00 F8 29 ....À.z.......ø)..ø) 000CAE90 0F 00 12 01 3B 25 32 00 00 00 01 1A 00 80 00 00 00 00 00 00 ....;%2......€...... 000CAEA4 00 00 12 01 3B 2D 28 00 00 00 01 1A 00 80 00 00 00 00 00 00 ....;-(......€...... 000CAEB8 00 00 12 01 00 1A 40 00 00 00 01 1A 00 80 00 00 00 00 00 00 ......@......€...... 000CAECC 00 00 12 01 05 06 06 00 00 00 01 1A 00 80 00 00 00 00 00 00 .............€...... 000CAEE0 00 00 12 01 06 06 06 00 00 00 01 1A 00 80 00 00 00 00 00 00 .............€...... 000CAEF4 00 00 12 02 29 01 C8 00 00 00 03 1A 00 00 A0 2A 0F 00 A0 2A ....).È....... *.. * 000CAF08 0F 00 12 02 30 01 C8 00 00 00 03 1A 00 00 68 2B 0F 00 68 2B ....0.È.......h+..h+ 000CAF1C 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................... 000CAF30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .................... 000CAF44 00 00 00 00 37 00 00 00 ....7... It appears that modules 0x129 and 0x130 each have a size of 0xC8 sectors and are located at ABAs 0xF2AA0 and 0xF2B68, respectively. Code: ID size address 1 address 2
---- ---- --------- ---- ---- --------- --------- 00000000 1202 4000 5F03 0000 0318 0000 0000 0000 0000 0000 00000014 1202 0100 2000 0000 0318 8042 0000 0000 0000 0000 00000028 1202 3500 0A00 0000 031A 0000 302C 0F00 302C 0F00 0000003C 1202 EF00 1E00 0000 031A 0000 822A 0F00 822A 0F00 00000050 1202 B511 1000 0000 031A 0000 722A 0F00 722A 0F00 00000064 1202 9000 9001 0000 031A 0000 6828 0F00 6828 0F00 00000078 1202 C000 7A00 0000 031A 0000 F829 0F00 F829 0F00 0000008C 1201 3B25 3200 0000 011A 0080 0000 0000 0000 0000 000000A0 1201 3B2D 2800 0000 011A 0080 0000 0000 0000 0000 000000B4 1201 001A 4000 0000 011A 0080 0000 0000 0000 0000 000000C8 1201 0506 0600 0000 011A 0080 0000 0000 0000 0000 000000DC 1201 0606 0600 0000 011A 0080 0000 0000 0000 0000 000000F0 1202 2901 C800 0000 031A 0000 A02A 0F00 A02A 0F00 <-- 0x129 00000104 1202 3001 C800 0000 031A 0000 682B 0F00 682B 0F00 <-- 0x130 |
|
| Page 1 of 3 | All times are UTC - 5 hours [ DST ] |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|