Just posting in case this helps someone else.
I had a WD that was locked but after unlocking and disabling the password with MHDD, the drive
still appeared locked after reboot, and then couldn't be unlocked anymore.
The drive was a WD800BB-00CAA1 with master password XBOXSCENE (used in an Xbox).
I used MHDD with the dump2 script as found in this thread to get the password before and after unlocking. The password appeared to be gone after unlocking, but the drive still acted locked and wouldn't let me see the files on it. Someone else on this forum had the same problem however their drive died so they gave up on it. Maybe there are others in the same boat who need help.
I did manage to get the drive unlocked through trial and error, and here's what did it for me:- I used HDAT2 (v6.0 beta 5) instead of MHDD.
- I went into a menu and used the option to dump the password from WD drives (Commands Menu, I think? I'll have to double check and edit this later). That dump function appears to work the same as a couple of the MHDD scripts, but it shows the output right on the screen instead of saving to a file.
- I went into the Security Menu and after pressing down to go to the next item in the menu, I noticed the red options (Set Password, etc) suddenly turned white. So I set the master password back to XBOXSCENE. The trick, though, seems to be that you also need to set the user password. So I set that to XBOXSCENE as well.
- I rebooted and went back into HDAT2.
- I went into the Security menu and unlocked the drive using both the master and user passwords.
- In the same menu, I disabled both the master and user passwords.
- I rebooted and went back into HDAT2, and the drive now showed as unlocked!
The first time I noticed that I could set the password, after using the password dump function, I only set the master password. Then I rebooted, went back in, unlocked and disabled the master password, and rebooted. However, that put me back at square one, where I was after using MHDD. So as I said, definitely set the user password as well as the master password.
I think this would work from MHDD as well. I suspect that if you run the dump scripts and then tried to set the password, MHDD would allow you to, just like HDAT2 does after dumping.
I've attached a screenshot comparing 42.bin before and after unlocking using MHDD. Figured that might be of some interest as well. I noticed a couple of other differences aside from the password.
If this helps you, let me know!