View topic - WD20NMVW-11AV3S2 ROM REGEN

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

WD20NMVW-11AV3S2 ROM REGEN

Page 2 of 3

[ 59 posts ]

Go to page Previous 1, 2, 3 Next

Previous topic | Next topic

Author

Message

shahij

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 8:38

Joined: March 11th, 2008, 4:35
Posts: 1052
Location: Bangladesh

Did you just edited 2 bits to the slow fix issue?

Yes, it's strange to me as well. As of client, it's untouched. I'll try to discuss further when he comes during delivery.

I didn't start to image yet, will do it shortly.

By the way, to get the LDR work properly, I had to modify the SA defects.

_________________
__________
There is no substitute for education and experience
THANK YOU
SHAHI
shahi.mahbub@gmail.com

Top

Amarbir[CDR-Labs]

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 12:05

Joined: August 15th, 2006, 3:01
Posts: 3522
Location: CDRLabs @ Chandigarh [ India ]

shahij wrote:

Hi,

The HDD came with problematic ROM.

Can read ROM,
Can read all modules of ROM Except "47"
The Head Map shows Wrong

I've been able to read TRACKS from SA with a loader+donor rom, tried to regenerate ROM, it produced following 4 modules - [0B 0D 4F 30], also ROM.

47 and 0A still can't be produced.

WD20NMVW-11AV3S2
PCB: 1961 - Converted to SATA 1959

Any assistance would be highly appreciated

Patient & Regenerated ROM is attached

Haa Haa Haa ,
Stop Going Around In Circles Shahi ,Just Contact Me On Skype And Matter Solve ,Nothing Wrong With Your Rom Hee Hee ,Sometimes These Guys Have Too Much Knowledge Which is Injurious To Health .Absolutely No Issue With This ROM

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Top

drHDD

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 13:26

Joined: October 5th, 2015, 18:53
Posts: 488
Location: US

Amarbir[CDR-Labs] wrote:

shahij wrote:

Hi,

Haa Haa Haa ,
Absolutely No Issue With This ROM

There is my HA to you.
At least check sum for 0A are not right.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 14:37

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

There are two directory modules in the ROM -- 20B and 0B. Here is a report by my ROM analysis tool:

Code:

ROYL directory module 0x000B found at 0x0003FCD2
Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
----------------------------------------------------------
0001  N/A    00004000  N/A        00000000             N/A
000A  OK     0000003E  00000200   0003F000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  OK     00000400  OK         0003D000   00000000  OK
0047  FFFF   00000800  01FFFE00   0003F4D2   FFFFFE00  BAD
000D  OK     00000094  00000200   0003F03E   00000000  OK
004F  OK     00000400  OK         0003F0D2   00000000  OK

ROYL directory module 0x020B found at 0x0003ECD2
Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
----------------------------------------------------------
0001  N/A    00004000  N/A        0004DB83             N/A
000A  OK     0000003E  00000200   0003E000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  OK     00000400  OK         0003D000   00000000  OK
0047  OK     00000800  OK         0003E4D2   00000000  OK
000D  OK     00000094  00000200   0003E03E   00000000  OK
004F  OK     00000400  OK         0003E0D2   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.

Module 20B is the correct directory. Directory 0B points to an uninitialised 47 module plus alternative copies of modules of 0A, 0D and 4F.

Here is module 0A from the 20B table:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0003E000  52 4F 59 4C 04 00 1E 00 0A 00 01 00 E8 C4 D6 6A  ROYL........èÄÖj
0003E010  30 30 30 31 30 30 30 30 02 0C 0E 00 00 00 20 06  00010000...... .
0003E020  00 08 08 FF 00 00 7C 51 7C 48 4A 4E 54 33 53 42  ...ÿ..|Q|HJNT3SB
             ^^^^^ ^^
          8 heads   head map = FF

0003E030  00 00 00 00 00 00 00 00 00 00 00 00 86 FB        ............†û

Here is module 0A from the 0B table:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0003F000  52 4F 59 4C 04 00 1E 00 0A 00 01 00 BF FB 05 4C  ROYL........¿û.L
0003F010  30 30 30 31 30 30 30 30 00 00 00 00 00 00 20 06  00010000...... .
0003F020  01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
             ^^^^^ ^^
          0 heads   head map = 00

0003F030  55 55 00 00 00 00 00 00 00 00 00 00 2B FF        UU..........+ÿ

It appears that MRT is extracting those modules in the 0B directory (wrong) rather than the 20B directory (correct). This suggests to me that the wrong directory is being selected as the active directory by either MRT or the ROM or both.

Note that the ABA of module 01 is 0x00000000 in directory 0B and 0x0004DB83 in directory 20B.

BTW, there is no problem with any of the module checksums. All are 0x00000000.

ISTR someone telling that there is a flag that indicates which of the two directories is the active one. Unfortunately I can't remember where this flag is located.

Could this be the problem?

Directory 20B

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 02 01 00 35 9A 20 F4  ROYL........5š ô
00000010  30 30 30 33 30 30 30 30 00 00 00 02 00 00 0A 1A  00030000........
                                           ^^
                                           inactive flag ?

Directory 0B

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 00 01 00 05 B5 23 AE  ROYL.........µ#®
00000010  30 30 30 33 30 30 30 30 00 00 00 01 00 00 0A 1A  00030000........
                                           ^^
                                           active flag ?

_________________
A backup a day keeps DR away.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 16:08

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

This is the donor's 20B directory:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 02 01 00 35 82 1F F4  ROYL........5‚.ô
00000010  30 30 30 33 30 30 30 30 00 00 00 02 00 00 0A 1A  00030000........
                                           ^^
                                           inactive flag ?

... and the 0B directory:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 00 01 00 05 B6 23 AE  ROYL.........¶#®
00000010  30 30 30 33 30 30 30 30 00 00 00 01 00 00 0A 1A  00030000........
                                           ^^
                                           active flag ?

My ROM analysis tool suggests that 20B is the active directory.

Code:

ROYL directory module 0x000B found at 0x0003FCD2
Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
----------------------------------------------------------
0001  N/A    00004000  N/A        00000000             N/A
000A  OK     0000003E  00000200   0003F000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  OK     00000400  OK         0003D000   00000000  OK
0047  FFFF   00000800  01FFFE00   0003F4D2   FFFFFE00  BAD
000D  OK     00000094  00000200   0003F03E   00000000  OK
004F  OK     00000400  OK         0003F0D2   00000000  OK

ROYL directory module 0x020B found at 0x0003ECD2
Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
----------------------------------------------------------
0001  N/A    00004000  N/A        0004DB83             N/A
000A  OK     0000003E  00000200   0003E000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  OK     00000400  OK         0003D000   00000000  OK
0047  OK     00000800  OK         0003E4D2   00000000  OK
000D  OK     00000094  00000200   0003E03E   00000000  OK
004F  OK     00000400  OK         0003E0D2   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.

Therefore my guess as to the location of the flag appears to be incorrect.

_________________
A backup a day keeps DR away.

Top

drHDD

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 16:19

Joined: October 5th, 2015, 18:53
Posts: 488
Location: US

fzabkar wrote:

BTW, there is no problem with any of the module checksums. All are 0x00000000.

It is not true for real 0A module.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 16:49

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

drHDD wrote:

fzabkar wrote:

BTW, there is no problem with any of the module checksums. All are 0x00000000.

It is not true for real 0A module.

The patient's real 0A module has a size of 0x0000003E bytes and is located at offset 0x0003E000.

Code:

C:\Downloads\WD\Firmware\WD20NMVW-11AV3S2\shahi\ROM>\downloads\chksum2\chksum2 -32 0A_3E000.bin
0A_3E000.BIN:   512 bytes       checksum32 = 0x00000000

I have computed the checksum using my own tool and that of Pete Disdale. We both agree on 0x00000000.

Attachments:

0A_3E000.rar [149 Bytes]
Downloaded 792 times

_________________
A backup a day keeps DR away.

Top

drHDD

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 17:46

Joined: October 5th, 2015, 18:53
Posts: 488
Location: US

I used pc3000. I didn't see that pc3000 calculates check sum wrong.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 17:56

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

drHDD wrote:

I used pc3000. I didn't see that pc3000 calculates check sum wrong.

You place too much trust in your tools. Calculate the checksum yourself, if you can.

BTW, you may at least do me the courtesy of downloading my version of module 0A before you pass judgment.

_________________
A backup a day keeps DR away.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 19:08

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

This is the "head map" section from the "real" 0A module:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  20 06 00 08 08 FF 00 00 7C 51 7C 48 4A 4E 54 33   ....ÿ..|Q|HJNT3
00000010  53 42 00 00 00 00 00 00 00 00 00 00 00 00 86     SB............†

The 8-bit checksum for these bytes is 0x00.

This is the same section from the "uninitialised" 0A module:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  20 06 01 00 00 00 00 00 00 00 00 00 00 00 00 00   ...............
00000010  00 00 55 55 00 00 00 00 00 00 00 00 00 00 2B     ..UU..........+

The 8-bit checksum is 0xFC.

_________________
A backup a day keeps DR away.

Top

drHDD

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 20:28

Joined: October 5th, 2015, 18:53
Posts: 488
Location: US

Yes, you are right and I am wrong. Sorry.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 23:12

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

AISI, if there is a flag byte in module 0A, then there would need to be flag bytes in each copy of 0D, 47 and 4F. I doubt that this would be the case.

The OP states that the donor ROM is OK but the patient is bad. This statement seems a little vague. Perhaps those two bytes are indeed the flag bytes as I originally suspected. If so, then could it be that the OP's ROM "problem" is simply a red herring arising from a bug in MRT's software? I notice that in most other models those same bytes are 0x00 and 0x01, with the latter being the active directory. In one other example I saw 0x06 and 0x07, with 0x07 being active. Could it be that the active directory is the one with the larger flag, ie 02 vs 01, 01 vs 00, 07 vs 06? Moreover, could it be that MRT is simply looking for a flag value of 0x01?

The other question is, how is MRT extracting those ROM modules? Is it using VSCs, or is it carving them out of the ROM dump? If the latter, then this would support my bug theory.

_________________
A backup a day keeps DR away.

Top

Amarbir[CDR-Labs]

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 22nd, 2016, 23:26

Joined: August 15th, 2006, 3:01
Posts: 3522
Location: CDRLabs @ Chandigarh [ India ]

Spildit wrote:

Amarbir[CDR-Labs] wrote:

And the hero arrives to save the day ....

When the problem is already solved, of course .... :mrgreen:

shahij wrote:

Your patched Version 02 worked!

Well,
He Did Not Contact The Hero Initially ,Thats Why You People Had To Spend a Lot of Your Time And Effort ,This Hero Has Helped Him Many Times .I Never Trust 1 Tool [ Infact i have all 4 lol ] . I repeat nothing wrong with this rom from start

One Link To Open Your Eyes Spildit [ God of Data Recovery ] - > http://forum.acelaboratory.com/viewtopi ... 155&t=8909

PS : Posted 6th month of 2016 lol

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Top

Amarbir[CDR-Labs]

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 0:03

Joined: August 15th, 2006, 3:01
Posts: 3522
Location: CDRLabs @ Chandigarh [ India ]

drHDD wrote:

Amarbir[CDR-Labs] wrote:

shahij wrote:

Hi,

Haa Haa Haa ,
Absolutely No Issue With This ROM

There is my HA to you.
At least check sum for 0A are not right.

Well,
Take a Ha From Me On This Then .Once you Take USB PCB Out of Patient Sherk LT Drives [ A Lot of Them ,Baring a Few " Which are according to me are the once that do not have SED enabled "] And Use COM Port Interface to read rom and rom modules there its gonna behave like exactly shahi case .But then if you program the read complete rom dump to a sata pcb then read it in kernel mode its all fine .Go to the acelab forum i asked this to developer but i am sure developer cannot do anything because nothing really is wrong .Cos if there was anything wrong why will writing complete rom work properly in sata 959 board in all of my cases .Come on wayne i do not write much does not mean i know less .As Far As God of data recovery's research is concerned [ Mostly he sees what the tool does and then tries to do it with hex editors ,recalculate checksum To get a pat on his back from people whats original ? nothing ] .So Merry Christmas One peg from my side with a slogan " Hail Amarbir :mrgreen:

]

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 2:41

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

Amarbir[CDR-Labs] wrote:

http://forum.acelaboratory.com/viewtopic.php?f=155&t=8909

PS : Posted 6th month of 2016 lol

Your post at Ace Lab does not demonstrate any understanding of the problem, merely that a problem exists. In fact it appears that PC3000 has exactly the same bug as MRT.

BTW, it's "Shrek", not "Sherk" or "shark".

_________________
A backup a day keeps DR away.

Top

shahij

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 2:58

Joined: March 11th, 2008, 4:35
Posts: 1052
Location: Bangladesh

Amarbir[CDR-Labs] wrote:

Spildit wrote:

Amarbir[CDR-Labs] wrote:

And the hero arrives to save the day ....

When the problem is already solved, of course .... :mrgreen:

shahij wrote:

Your patched Version 02 worked!

People spent effort and time was fruitful. The case is solved. We discuss in some points with several people, but we usually don't go into Conclusion like this case. The case got a Conclusion by the way.

In your PC3k, I don't understand why it can't read, but in my case, I've same family/same model HDD and it can be read PROPERLY without any issue. Also, after fixing the patient, the ROM/ROM MODULES, and HDD loads NORMALLY without any issue.

I repeat, the case I had ROM issue as well as FW issue. You have to read the case all over to understand things

[img]

Attachment:

shrek.png

[/img]

Attachments:

shrek.png [ 24.14 KiB | Viewed 12328 times ]

_________________
__________
There is no substitute for education and experience
THANK YOU
SHAHI
shahi.mahbub@gmail.com

Top

Amarbir[CDR-Labs]

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 8:46

Joined: August 15th, 2006, 3:01
Posts: 3522
Location: CDRLabs @ Chandigarh [ India ]

Well,
Its Upto you To Understand Or Not To As Far As i am concerned i have the same issue with virtually every shrek sorry dolphin sorry shark family with SED enabled [ Mr Frank You Can Choose Whatever Words you want to lol ] . BTW Shahi a Video On My Youtube Channel Would Be Made On The Subject Might Be Few Can Understand

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com

Top

shahij

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 17:23

Joined: March 11th, 2008, 4:35
Posts: 1052
Location: Bangladesh

1. Ill restore the rom n modules to original state, Just Will keep the mod02. Then Will update the report to verify if the theory Is correct.

2. Ill test the patched rom by spildit tomorrow n update u

3. I worked with more 3shrek lt earlier. 2 dropped case, 1 fw issue. Didnt face any abnormal thing like This one.

4. If I wouldn't work with the rom, there was no way to deal the case, do u have any comment on This one?

_________________
__________
There is no substitute for education and experience
THANK YOU
SHAHI
shahi.mahbub@gmail.com

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 17:31

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

I have patched the original patient ROM so that each copy of each module is the "real" one. This should make MRT happy while not affecting the function of the ROM.

Attachments:

patient_ROM_copied_mods.rar [237.06 KiB]
Downloaded 592 times

_________________
A backup a day keeps DR away.

Top

fzabkar

Post subject: Re: WD20NMVW-11AV3S2 ROM REGEN

Posted: December 23rd, 2016, 18:51

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia

Spildit wrote:

Looks like MRT is happy with donnor ROM of the same family/model .... So my guess is that som flag is set so that the drive itself uses the worng copy of the modules and MRT does the same.

The patient drive is SED locked whereas the donor is not. This means that MRT can get the modules directly from the donor by way of VSCs. However, in the case of the patient HDD it would need to carve them out of the ROM dump. Maybe that is the difference?

Donor - 02.rpm

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000790                                         00 00 00
000007A0  00 00 00 00

Original - 02.rpm

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000790                                         00 00 00
000007A0  00 00 00 01

_________________
A backup a day keeps DR away.

Top

Page 2 of 3

[ 59 posts ]

Go to page Previous 1, 2, 3 Next

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 38 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum