WD OG Rom Showing corruption, analyzing with fzabkar 's Utility

[Mustafa Rampura wala]

Analysing E:\UserDataFile\Programmer\WD20SDRW-11VUUS0-WX11E79FN1LY\0-FFFFF 1.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 ED   04      20 -  1B47       1000     1B24  1B24  000AA627 000AA627 OK (digitally signed)
 2000  01 49   04    2180 -  4AA0      49688     2820  2820    B9   B9   OK
 2020  02 07   11    4AA1 -  8B05   30080000 c   5580  4064    18   18   OK
 2040  03 66   0C    8B06 -  8EFA   24000000      3F4   3F4    D3   D3   OK
 2060  04 AC   40    8EFB -  DCD3   FFE00200     4DD8  4DD8    19   19   OK
 2080  05 D3   01    DCD4 -  E7E0   38268800 c    D48   B0C    2D   2D   OK
 20A0  06 C4   04    E7E1 -  EC81   38269800      4A0   4A0    79   79   OK
 20C0  07 12   01    EC82 - 14B12          0 c   7894  5E90    DD   DD   OK
 20E0  08 B6   01   14B13 - 14F33       DE84 c    4EC   420    1B   1B   OK
 2100  09 98   03   14F34 - 175CC      40340 c   3160  2698    40   40   OK
 2120  0A AD   03   175CD - 179A5   6026A800 c    9BC   3D8    34   34   OK
 2140  0B 29   01   179A6 - 2FEA2   38352800 c  208A8 184FC    AD   AD   OK
 2160  0C 20   01   2FEA3 - 555D7   38008230 c  32D84 25734    E6   E6   OK
82000  01 49   04   82180 - 84AA0      49688     2820  2820    B9   B9   OK
82020  02 07   11   84AA1 - 88B05   30080000 c   5580  4064    18   18   OK
82040  03 66   0C   88B06 - 88EFA   24000000      3F4   3F4    D3   D3   OK
82060  04 AC   40   88EFB - 8DCD3   FFE00200     4DD8  4DD8    19   19   OK
82080  05 D3   01   8DCD4 - 8E7E0   38268800 c    D48   B0C    2D   2D   OK
820A0  06 C4   04   8E7E1 - 8EC81   38269800      4A0   4A0    79   79   OK
820C0  07 12   01   8EC82 - 94B12          0 c   7894  5E90    DD   DD   OK
820E0  08 B6   01   94B13 - 94F33       DE84 c    4EC   420    1B   1B   OK
82100  09 98   03   94F34 - 975CC      40340 c   3160  2698    40   40   OK
82120  0A AD   03   975CD - 979A5   6026A800 c    9BC   3D8    34   34   OK
82140  0B 29   01   979A6 - AFEA2   38352800 c  208A8 184FC    AD   AD   OK
82160  0C 20   01   AFEA3 - D55D7   38008230 c  32D84 25734    E6   E6   OK

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


ROYL directory module 0x000B found at 0x7F43E

Active directory flag = 0x01

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x000A6338  0x00000000
0x01  0x000A6338  0x000AA49C

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00000000             N/A
000A  OK     0000004E  00000200   0007E000   00000000  OK
000B  OK     0000013D  00000200   0007F43E   00000000  OK
020B  OK     0000013D  00000200   0007D43E   00000000  OK
0030  OK     00000400  OK         0007B000   00000000  OK
0047  OK     000006A4  00000800   0007E556   00000000  OK
000D  OK     00000108  00000200   0007E04E   00000000  OK
004F  OK     00000400  OK         0007E156   00000000  OK
0181  OK     00000C00  OK         0007B400   00000000  OK
01A2  OK     0000007E  00000200   0007EBFA   00000000  OK
01B6  OK     0000069E  00000800   0007EC78   00000000  OK
01B0  OK     00000128  00000200   0007F316   00000000  OK

ROYL directory module 0x020B found at 0x7D43E

Active directory flag = 0x02

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x000A6338  0x00000000
0x01  0x000A6338  0x000AA49C

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00000000             N/A
000A  FFFF   0000004E  01FFFE00   0007C000   0000FFEC  BAD
000B  OK     0000013D  00000200   0007F43E   00000000  OK
020B  OK     0000013D  00000200   0007D43E   00000000  OK
0181  OK     00000C00  OK         000FE400   00000000  OK
0030  OK     00000400  OK         000FE000   00000000  OK
0047  FFFF   000006A4  01FFFE00   0007C556   FFFFFE57  BAD
000D  FFFF   00000108  01FFFE00   0007C04E   FFFFFFBE  BAD
004F  FFFF   00000400  01FFFE00   0007C156   FFFFFF00  BAD
01A2  FFFF   0000007E  01FFFE00   0007CBFA   0000FFE0  BAD
01B6  FFFF   0000069E  01FFFE00   0007CC78   2643F628  BAD
01B0  OK     00000128  00000200   0007D316   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_01\000Bmods and Flash_01\020Bmods

Active directory is 0x20B

Analysing active 0x0A module ...

Module has bad checksum -- processing aborted

Analysing active 0x0D module ...

Module has bad checksum -- processing aborted

Analysing active 0x4F module ...

Module has bad checksum -- processing aborted

Analysing active 0x47 module ...

Module has bad checksum -- processing aborted

[Mustafa Rampura wala]

Drive Details : 

WDC WD20SDRW-11VUUS0

0006008J

tried replacing 20b modules with 0b , It is now giving SA access , Read all Firmware, But the Data is Showing Encrypted, is it due to ROM Corruption

[Desert Data Recovery]

Are you using the original PCB? They are encrypted by the MCU.

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/e196e8ba-8a87-4913-8440-eb0cfbc5f7acn%40googlegroups.com.

[Mustafa Rampura wala]

It's Original , Since i have got the case, and client also denies any alteration or tampering

[Desert Data Recovery]

Have you used the correct loader?

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/01c6a33c-8310-484b-810f-295ae614cdd2n%40googlegroups.com.

[pbzcbf...@gmail.com]

ROM resident modules 0x1B6 and 0x1A2 are both empty. Isn't that a problem?

Can these modules be recovered from 0x129 and 0x130?

[pbzcbf...@gmail.com]

If the active directory flag is pointing to the wrong module directory, doesn't this mean that the ROM was manipulated? Or is this a benign firmware bug? That said, if the drive was not spinning up prior to your 0B/20B module transfer, then that would suggest manual interference.

[Shariq Mansoori]

I Can Help Sir, but need some time.

+91 82185856878

MSM DATA RECOVERY

[Shariq Mansoori]

Hello Sir,

I hope you are doing great.

Yes these modules can be recovered.