0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not completed.

Loooool. Ehh, servo error's in scan D1, and limits full. Still I am not sure whether the script is , however, servo . Log attach tomorrow.

Case Closed, Unlock Sa solved problem DCO.

Can you show us the contents of module 02 before and after unlocking?

Yes, And there are some differences, and not just one byte.

Attachments

02.rar: 02 Before Unlocking; (903 Bytes) Downloaded 870 times

0002.rar: 02 After unlocking.; (870 Bytes) Downloaded 895 times

Hi
There are many many types of locking in wd 02 modules. Sed lock. Sector read and write disable (for dvr hdd). Dco lock. Etc

Yes will upload picture of 02 after and before for sed locked drives. For dco unlock i think pukius upload 02 module.

Every wd family have different location of byte which we need to change for unlock. But the design and structure is same. Only location of byte goes on high offset and some time low offset.

Regards
Waqas Ali

waqas_ali766 wrote:Yes will upload picture of 02 after and before for sed locked drives. For dco unlock i think pukius upload 02 module.

Well, I preferred to attach the module unlocks the original before and after unlocking.

waqas_ali766 wrote:Every wd family have different location of byte which we need to change for unlock. But the design and structure is same. Only location of byte goes on high offset and some time low offset.

ok thanks for suggestion.

Aside from the model and serial number sections, I found the following differences:

section 3 - Feature Control

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 000000F0 00 01 A4 02 00 00 00 00 07 7F 00 ..¤........ 00000100 00 06 F4 01 01 00 01 00 02 9A 05 64 80 00 00 00 ..ô......š.d€... 00000110 20 0A 14 00 00 00 14 00 00 00 00 00 00 00 00 00 ............... 00000120 0A A0 0F 00 00 00 BC 34 00 00 00 00 10 01 00 02 . ....¼4........ 00000130 1E 1E 00 00 00 00 00 00 00 00 00 00 00 00 01 01 ................ 00000140 AC 0D 00 ¬.. 000000F0 00 01 A4 10 00 00 00 00 07 7F 00 ..¤........ ^^ 00000100 00 06 F4 01 01 00 01 00 02 9A 05 64 80 00 00 00 ..ô......š.d€... 00000110 20 0A 14 00 00 00 14 00 00 00 00 00 00 00 00 00 ............... 00000120 0A A0 0F 00 00 00 BC 34 00 00 00 00 10 01 00 02 . ....¼4........ 00000130 1E 1E 00 00 00 00 00 00 00 00 00 00 00 00 01 01 ................ 00000140 AC 0D 00 ¬..

section 13 - Background Configuration

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000300 00 01 E0 01 0F 0F 01 02 02 0A 01 01 00 02 ..à........... 00000310 02 04 01 00 FF FF 05 00 00 01 00 00 00 00 00 40 ....ÿÿ.........@ 00000320 0B 02 00 E8 03 64 00 FF FF 10 00 00 00 00 01 0A ...è.d.ÿÿ....... 00000330 40 42 0F 00 E0 C8 10 00 00 00 00 00 @B..àÈ...... 00000300 00 01 E0 01 0F 0F 01 02 02 0A 01 01 00 02 ..à........... 00000310 02 04 01 00 FF FF 05 00 00 01 00 0A 00 00 00 40 ....ÿÿ.........@ ^^ 00000320 0B 02 00 E8 03 64 00 FF 00 10 00 00 00 00 01 0A ...è.d.ÿ........ ^^ 00000330 40 42 0F 00 E0 C8 10 00 00 00 00 00 @B..àÈ......

section 14 - CDD Configuration

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000330 00 01 00 00 .... 00000340 00 00 05 00 00 00 00 00 FF FF 00 00 00 00 12 0A ........ÿÿ...... 00000350 12 00 00 00 05 00 00 00 00 00 1E 00 00 00 00 00 ................ 00000360 00 00 00 00 4D 00 24 00 07 00 12 2E 00 00 00 0E ....M.$......... 00000370 00 01 00 00 05 ..... 00000330 00 01 00 00 .... 00000340 00 00 05 00 00 00 00 00 FF FF 00 00 00 00 12 0A ........ÿÿ...... 00000350 12 00 00 00 05 00 00 00 00 00 1E 00 00 00 00 00 ................ 00000360 00 00 00 00 4D 00 24 00 07 00 12 2E 00 01 00 0E ....M.$......... 00000370 00 01 00 00 05 ^^ .....

section 27 - ??? ("slow fix" section)

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000560 00 01 02 ... 00000570 02 00 32 00 00 80 0C 00 00 00 00 32 00 00 00 64 ..2..€.....2...d 00000580 00 00 00 1E 00 00 00 05 D6 06 00 4B 00 00 19 00 ........Ö..K.... 00000590 00 00 01 01 08 01 00 00 00 00 40 00 02 40 00 10 ..........@..@.. 000005A0 04 00 40 01 00 01 ..@... 00000560 00 00 00 ... 00000570 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000580 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000590 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 000005A0 00 00 00 00 00 00 ......

Yes, because 02 before unlock is in oryginal backup SA,
no changed, but After unlocking 02 preparation for ARCO, slow fix and test B2

Hi
Here is the modules for SED lock and unlock for Firebird hdd,

Editing will make data recovery impossible , because it change the reading method of a sector.

must save the original 02 module if you need data, or after edit 02 for drives repair, convert the 02 editing to original position.

SED LOCK.rar: (2.11 KiB) Downloaded 858 times

Regards
Waqas Ali

Ok, Thanks for suggestion.
But Self test, Test 1003 - shows error 7000 Servo PTM_code Base 704F, then self test stops, and not continue, checked in 10 scripts, but problem the same.

Hi
Remote ammy admin id please, PM me remote ID

It appears that section 31 is not the relevant section. Instead it is section 32.

SED locked

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000710 00 00 00 00 00 00 00 00 D6 06 00 1E 00 00 00 00 00000720 00 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 ^^ 00000730 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00 00 00

SED unlocked

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000710 00 00 00 00 00 00 00 00 D6 06 00 1E 00 00 00 00 00000720 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00000730 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00 00 00

The relevant section of Mod 02 is section 32, not section 31.

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 000000A0 43 00 59 06 11 00 6A 06 1C 00 86 06 99 00 1F 07 ^^^^^ 000000B0 07 00 81 02 43 00 26 07 09 00 2F 07 69 00 98 07 ^^^^^

Section 32, offset 0x71F, size 0x7 bytes

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

Hi fzabkar.
I didn't understand what you want to say.

You need to change only one byte from 01 to 00 to unlock.

I not understand you means by section 31 or 32 and 7 bytes.

Regards
Waqas ali

Waqas ali, you need to understand the structure of Mod 02. Then all will be clear. It makes no sense to refer to absolute addresses within the module.

Analysis of Western Digital ROYL firmware MOD 02:
http://www.hddoracle.com/viewtopic.php? ... 821&p=3191

Hi friends Calmly I checked wd Black and probably has damaged the second servo . Heads 0, 2 , 3, 7 in the user area sequences have bad sectors and which may be interesting for this test does not pass the calibration selftest. Understand me?

well no one have time to learn in deep, only the address is good for every one, just change and do a work, thats it.

What is in back ground of 02 and structure of 02 module is a work or researcher or software developer.
normal person don't need this thing. he just need to do as quick as possible.

But in real your theory about 02 is 100% real and perfect. :beer:

Regards
Waqas Ali
http://Www.sediv.net
http://www.datamagicme.com

@waqas_ali766, Firstly, let me say that I am grateful for your information. It was very enlightening. However, your initial post was confusing and misleading for several reasons.

Firstly you stated that one needed to change the following data set from ...

01 D6 06 00 1E 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 01 00 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00 00 00
... to ...

01 D6 06 00 1E 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 01 00 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00 00 00
In fact the two data sets are identical.

Then you stated that "you need to change just one byte from 01 to 00 at offset 725". Clearly there are several instances of 0x01 in the data set, so it is not clear which byte must be changed.

Furthermore, your reference to offset 0x725 does not clarify your instructions. Worse still, the Hubble_LT resource which I downloaded from HDD Guru differs from your own, so this means there is no consistency even within the same family.

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000790 00 00 00 00 00 00 00 00 00 00 D6 06 00 1E 00 00 000007A0 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 000007B0 00 00 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00

The only consistent fact appears to be that the SED unlock byte is located at offset 0x06 within section 32.

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

Here are the relevant data for section 32 in the index:

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 000000A0 45 00 DC 06 10 00 EC 06 1C 00 08 07 99 00 A1 07 ^^^^^ 000000B0 07 00 B6 02 45 00 A8 07 09 00 B1 07 69 00 1A 08 ^^^^^

As you can see, section 32 has a size of 7 bytes and is located at offset 0x7A1.

If we apply similar logic to pikus_09's 02 module, we find that his section 32 is located at offset 0x611.

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

Furthermore, the surrounding data differ significantly from your example.

Code:: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000600 00 00 05 0A 0C 00 00 00 FD FF 00 00 FF FF 00 00 00000610 01 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00000620 00 00 01 00 09 0F 0F 0F 0F 0F 00 00 00 00 00 00

Here is a locked example:

Code:: C:\mod2dump C:\WD10JMVW-11AJGS2\0002.rpm 32 ROYL header found Module 02 consists of 47 sections Section 32 Length 7 bytes Addr 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 0000 00 00 00 00 00 00 01 .......

Demm, nice suggestion. But at this time I don't know what is, because Sediv software for me locked. I can't run execute SA calibrator, or selftest. Nothing was change. Always Reset impermentiale and nothing.

Hi fzabkar
i told in my previous post that the location of SED locked Byte vary on different families.

on Hubble_LT SED locked drive offset is 725, but in non-SED drives you will not find this byte and this sections of SED lock.

May be you download non-SED drive 02 from internet that why you get confuse.

Also some DVR drives which yous Port locked, also unlock by 02 module, but the offset which you need to change is at different location.

Some drives SPECIALLY denali become read only, you cannot edit any module of any other thing, this also because of 02 lock.

And in Pikuis case its Mantis Drives, Mantis and some more families have Issue, Hdd cannot Start format SA, and shows DCO freeze lock, this also because of 02 and some thing in ROM.

There is many many secrete in WD 02 module.

also the latest drive may change the user data by editing 02 module. same like Seagate SID drives, in Seagate SID drive if you use Z0,0,22 then the Seacos encrypted sector will be removed, and you get permanent access to terminal. now you can recover the data, once you edit any of user data sector then you will loss all user data.
Because after editing the sector , hdd write it by encryption, and when you read all byte of same sector goes in to garbage shape, because the decryption key is erased. (Seacos SID key) , the Key is always written on the HDD sticker, some one have to make a software to clone all sector of drive using the SID key, if the data goes garbage.

After that you cannot use this hdd in pc, because the hdd have encryption sector and not have decryption sector.

then you have to LOAD LOADER with winfof to update the firmware, also you can use Seagate firmware update.
after firmware update, like in my case hdd have FW=0003LVM3 anf after Loader write with Winfof the firmware version become 3LVM1
i attached my loader you can download

0003LVM1.zip: (598.47 KiB) Downloaded 802 times

Its not easy to work with Latest drives, they are making it more and more complex.

Picture of Seagate SID self encrypted drive

you can see the SID key
Will upload the picture of Data sector soon, what happened if we remove the Seacos Security sector and AT overlay.

as written in the F3 commands document

Erase Seacos Data And Code (Level T 'Z')

0 - Minimal erase level
"0" to erase serial flash and reboot to mask ROM code Not supported yet
"1" to erase Appcode Not supported yet
"2" to erase Cert Not supported yet
"3" to erase Cert Table Not supported yet
"4" to erase AT Overlays
"5" to erase Congen Not supported yet
"6" to erase Security
"7" to erase Seasos
Type: Unsigned 8-bit value
Range: 0 to 0xFF
Default: None
1 - Erase mode
This parameter specifies the following options:
"1" means to erase the level the first param specify.
"0" means to erase from 7th level to the minimal level the first param specify.
Type: Unsigned 8-bit value
Range: 0 to 0xFF
Default: None
2 - Valid Command Key.
this parameter must be equal to 22 Hex. If this parameter is not equal to 22 Hex,
the command will not be executed.
Type: Unsigned 8-bit value
Range: 0 to 0xFF
Default: None
Output Data:
If an error occurred, the following information will be displayed.
"DiagError aaaaaaaa "
where
aaaaaaaa is the Diagnostic Error Code
If no error occurred, one of the following messages will be output to indicate the
status of the Seacos operation performed.
"Resetting"
"Erased Seacos"
"Erased Security"
"ConGen, not supported"
"Cert, not supported"
"Cert Table, not supported"
"Erased AT Overlays"
"AppCode, not supported"
"SFlash, not supported"
"Invalid level"
"Request dummy file failed"
"Open SIM file failed"
"Write SIM file failed"
"Erase Overlay failed"

Regards
Waqas Ali
www.sediv.net
www.datamagicme.com

0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not completed.

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple

Re: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not comple