Hello.

I have wd 160gb scorpio drive and i dont know the password.
Followed Arden instructions but i dont know what to do when i enter mhdd.
In mhdd, i press f2 to scan drives,then i select my hdd and i get message something like "your drive is locked".
Then i press f4 and it begins to scan the drive,at least i think so.
All i can see then are pink exclamation marks on the left.
Is this correct procedure or i got something wrong?
Thanks for the help.

I got this...

Passwords are clear to me! If you can't work out what to do next then read the posts by Splidit on the previous page

I guess passwords are 1111 or h2oinsyde.
Have tried both of them when my laptop boots up and asks for hdd password but none of those matched.
I will try to enter it through victoria and hex file like in that tutorial.

I have tried to enter password through victoria but i cant get it to work in pio mode.When i start it i get errors:
Unknown error or driver not exist
PORTTALK Error.Invalid driver handle.
PortTalk driver not installed!Available only in API access.

I guess it cant work on win7 like it says on google.

Hi there ! User password is 1111
Use MHDD with the commands unlock and dispwd and use 1111 as user password
Victorias needs the Porttalk driver.
It should work on windows 7, the problem might be related to 32 bit OS versus 64 bit os.
If your windows 7 is a 64 bit windows then the DRIVER will not install (64 bit windows have driver installation protection - drivers have to be signed, blá blá blá).
Just use MHDD as you used to get the password by script and use the commands to unlock and to remove the password from the drive.
Let us know if it worked out for you !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Maybe the laptop is "Hashing" what you enter. When you enter 1234 the laptop hashed it to something else like "qwedugqw23u9frt23ufrg23" whatever random looking string of data and sends that to the drive. Each password you input will be a different hash. When you input 1234 again it will hash to the same code. Google about hashing on crypto to understand the concept. MD5, SHA, etc are very popular hash algorithms.

You have to send the password as is - 1111 - directly to the drive and not by a BIOS that can be manipulating what you write and sending a different "code" to the drive.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

When i enter mhdd i select my wd drive.
Then i type dispwd and program asks master(1) or user(0) password.
I tried both of them and then typing 1111 and it says fail.
I guess the password does not match or something like that.

It worked!
I had to unlock it first and then use dispwd command.

Thank you guys,Spildit especially,i thought that i will throw this hdd in garbage.

Sure, first unlock and then dispwd.
Nice to know it worked !
Regards.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I have a WD Scorpio Black that I've owned since 2011 which has a ATA password that I know and set. The motherboard for that system fried but putting the drive in a different laptop doesn't let the drive unlock using my own set password or the common master password.

I've read this entire thread at least twice and similar guidance on a few other sites.

I'm using MHDD 4.5 and the posted dump script with the cs.bin.

at LINE 8: SECTORSFROM = CS.BIN
MHDD doesn't continue to the next line and seems to slow down time. The clock in the corner begins to tick very slowly, where the seconds increase 1 or 2 seconds every 5-10 seconds. I've left this operation in place for more than 10 minutes and nothing seems to change other than the clock slowly increasing. I'm assuming that it shouldn't actually take any noticeable time to actually perform this command.

I've also tried it using a different command in the binary as found at http://www.hddoracle.com/viewtopic.php?f=59&t=821#p4271 but had the same result.

control-break is the only way to proceed without powering down and it returns an exception unknown run time error:
0x000197BF
0x0000857C
0x00046029
0x0003F1C2
0x00002051

Any thoughts on what is going wrong at the line where I get sectorsfrom a binary?

Thank You!

I've run zu with all three options even though I think that the drive is in the secondary slot. In any of the attempts zu runs for more than a minute and I ctrl-c to escape when it doesn't work.

Is there an error message in zu or in the MHDD scripts that would indicate what is happening when it can't do the sectorsfrom?

I've downloaded the ROM using WDR Demo, but don't see anything inside which looks like a password.

Is there anything else to try other than order a replacement motherboard to try a transplant, and hope that my CPU and RAM are not fried like the original motherboard so that the effort is not wasted?

Thank You!

Hi! Before running the Mhdd script or ZU did you set the bios to ide/compatibility mode? Also what make/model laptop was the drive removed from?

This is HDD was from a Dell XPS.

In order to get to the point of attempting MHDD or ZU I made the following bios changes:

Secure boot:OFF (To allow me to change the csm setting)

CSM:Enabled (Required to let me boot off of something besides the built in SDD which cannot be removed from this new laptop.)

SATA: To IDE from AHCI (If not set then MHDD will not see the drives)

I also have to add a master or user password to the internal SDD before connecting the drive in question, to get into the bios. Once the drive in question is connected, the bios asks for a password before booting or getting back into the bios. If I have previously set the SDD to have a password then that password will work to continue but does not allow access to the drive in question. If I don't set a password and try to use the known password of the drive in question, or the typical WD master pw, then it does not proceed.

I don't know the keyboard codes associated with the original keyboard, but have also tried taking a common set of keyboard codes and my pw, converted the pw to dec, and entered it with the alt-gr in MHDD.

Thank You!

With the same WDR DEMO that you used to DUMP ROM go to ACTIONS - CLEAR PASSWORD

http://www.hddoracle.com/viewtopic.php?f=32&t=33

If this doesn't work then your drive is LOCKING SA ACCESS when the password is present and you will have to use another "trick" as the MHDD script will not work either. If the drive doesn't LOCK SA ACCESS WHEN password is set then this procedure will remove the password of the drive. Use the same port configuration on WDR that you used to DUMP ROM.

Password IS NOT stored on ROM, it's stored on module 02 on the platter.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The WDR Demo said that it was a success to clear password, but then I rebooted and the password remained.

It seems strange that WD had some drives which would hide the SA, and others that it wouldn't. Is there any sort of consistency within one company?

I received a pm pointing me to a different program, but it will take me a few days to review the documentation for the program and various notes on the forums about it.

Spildit, what sort of other "trick" might you recommend?

Thank You!

Try using an older pc. 5 to 10 years old would be good! Run the Mhdd script. If that doesn't work then install windows xp try the Wdr route. Lastly check what service tag revision that dell xps laptop had. There might be a way to generate a password.

If SA access is locked by the presence of the password using another PCB with diferent ROM version will make the drive NOT TO load SA at start up but will allow module access. This way you can use WDR to remove password. Also possible to write new ROM with diferent version so that at power on module 11 will not match ROM, password will not lock SA access and module 02 can be edited.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

So I ordered a PCB. It was supposed to have the same part number as my existing drive. When I exchanged the replacement PCB with my original board, the bios showed that something was in the port, but it was labeled as "Empty". The system was able to boot using the windows XP boot disk and I managed to get a copy of the ROM using WDR Demo. The filename for the replacement PCB ROM was 082c.bin while my original PCB ROM was 092c.bin. I ran the Clear Password Action, and was told that it was a success, but on a subsequent boot it still acted as if the password was in place.

I then booted and tried MHDD and HDAT2, but neither program could actually see this drive on any port.

Looking at the original and replacement ROMs shows that the PCB is actually for a 500GB drive while my original was 750GB. The order was supposed to match the part # for a 750GB drive.

Should swapping the boards be sufficient or do I need to flash the replacement ROM into the original ROM? I'm a little concerned about writing this replacement ROM to my original PCB now that it appears that the replacement PCB/ROM is not actually for my drive. Especially if there is a high chance that the original ROM can't be flashed back based on a copy that I made earlier.

The replacement PCB seemed a little mangled where one of the board contacts touched the other part of the drive so I tried to rebend the metal so that it was more similar to the other 3 contacts. Since then when I boot, my bios will now recognize that the replacement PCB is a "Hard Drive", but does not get any other device information, and the system will not boot off my CD drive in order to get into the win xp or MHDD if the replacement PCB is on the HD.

Haven't tried SeDiv or had a chance to get an older computer.

Thank You.

Place original pcb back to the drive and test it out.
If it still doesn't work out your best chance is to send the drive to someone with better tools for unlock.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.