0xC801 = DCO_FREEZE_LOCK_IN_PLACE - SA Format not completed.

[pikus_09]

Hey, today, i have very strange case, because while format SA,
I get the error: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE, and format SA not completed.

Drive: WD2002FAEX-007BA0 Mantis_PL_RE, FW: 00050016F/05.01D05
Log:

Code:

Action: Read Head Map............................................ OK!

Number of physical heads: 8

Number of heads in use: 8

Native head map: 255

Good head map: 255

File E:\HDD_REPAIR\SeDiv\WD2002Modules\0001.bin Load OK!



--------------------------------- Task Begin --------------------------------

-----------------------------------------------------------------------------

Load External Resident File Dir

Number of File Entries = 456

------------------------------- Task Completed ------------------------------

-----------------------------------------------------------------------------

File E:\HDD_REPAIR\SeDiv\WD2002Modules\0001.bin Load OK!



--------------------------------- Task Begin --------------------------------

-----------------------------------------------------------------------------

Load External Resident File Dir

Number of File Entries = 456

------------------------------- Task Completed ------------------------------

-----------------------------------------------------------------------------

HZ File Not Found!

HZ File Not Found!

HZ File Not Found!

HZ File Not Found!

Action: Read Flash............................................... OK!

Action: Reset Immediate.......................................... OK!

Action: Write Buffer Extended to permanent overlay buffer........ OK!

Module ID 0011 Load - OK!

Action: Write Buffer Extended to transient overlay buffer........ OK!

Module ID 001B Load - OK!

Write Code File - OK!

Load Data File C5 - OK!

Action: 4........................................................ OK!

Start: 01.18.23

Waiting for test to begin: = 30 seconds remaining until timeout

Start: 01.18.24

=========================   START   TESTS   ==========================

ARCO Run completed successfully!

Ecode Description= No Error

Action: Write Buffer Extended to PST Buffer...................... OK!



Start Self SA

--------------------------------- Task Begin --------------------------------

01.53.10

-----------------------------------------------------------------------------

Self SA - Running

01.53.10

01.56.12

Action: Check Module ID 0030..................................... OK!

Copy 0: 0030.............  OK

Copy 1: 0030.............  OK

Action: Check Module ID 0035..................................... OK!

Copy 0: 0035.............  OK

Copy 1: 0035.............  OK

Process Validation PASSED!!!

------------------------------- Task Completed ------------------------------

01.56.13

-----------------------------------------------------------------------------

Action: Read Resident file: 0035................................. OK!

File 0035 is a new header format file.



Format Reserved Start

--------------------------------- Task Begin --------------------------------

01.58.54

-----------------------------------------------------------------------------

Action: Format Reserved Area..................................... Error: DCO_FREEZE_LOCK_IN_PLACE

------------------------------- Task Completed ------------------------------

02.01.29

-----------------------------------------------------------------------------



I Used Sediv Repair tool(most power full soft), and WD marvel(very poor soft) in both cases error is the same, btw generated modules, are empty, no SA Bad Sectors in all Heads.
Moreover, drive is fully mechanical working, but Firmware, and ROM, Adaptives are incorrect.

[pikus_09]

Any ideas for this case?

[saltwater]

Hi!
I have Sediv too!
Are you sure that HSA can write without any problem? If write heads are not stable enough, then you have SA error when try write.

[waqas_ali766]

Hi
The drive is Firmware lock, that's why SA Format gives DCO lock Freeze error

Follow these steps, load 01 and 35, then power reset, and load all modules and make hdd in detection.

1. Use SA operation ---> SA Unlock wait for finish
2. Power reset
3. backup all firmware
4. Format SA
5. Repair DIR
6. Load all modules Except 01 and 35 on both copies.

Now you can do all operation what you want.

If you want to unlock Drive SA then you must need to edit 02 module.

For Example
Hdd family = Hubble_LT
open 02 module in hex view, goto offset 725 (offset 725 have value 01), before this offset you see value 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

you need to change it 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

you need to change just one byte from 01 to 00 at offset 725.

For different families offset is little bit different , but bytes values are always same.

Regards
Waqas Ali
http://www.sediv.net

[pikus_09]

Hi!
I have Sediv too!
Are you sure that HSA can write without any problem? If write heads are not stable enough, then you have SA error when try write.

Hi Saltwater. Yes, all 8 heads read/write 3x runs test OK.

Hi
The drive is Firmware lock, that's why SA Format gives DCO lock Freeze error

Follow these steps, load 01 and 35, then power reset, and load all modules and make hdd in detection.

1. Use SA operation ---> SA Unlock wait for finish
2. Power reset
3. backup all firmware
4. Format SA
5. Repair DIR
6. Load all modules Except 01 and 35 on both copies.

Now you can do all operation what you want.

If you want to unlock Drive SA then you must need to edit 02 module.

For Example
Hdd family = Hubble_LT
open 02 module in hex view, goto offset 725 (offset 725 have value 01), before this offset you see value 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

you need to change it 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

you need to change just one byte from 01 to 00 at offset 725.

For different families offset is little bit different , but bytes values are always same.

Regards
Waqas Ali
http://www.sediv.net

Hi Waqas, but problem shows then SA is Empty.
When Run SA Selftest, Selftest SA completed, New mods 30, and 35 generated are empty, so run Sa Format using Mod 35(in hdd, no external file) and after 3 min SA Format show: 0xC801 = DCO_FREEZE_LOCK_IN_PLACE.

[waqas_ali766]

Yes its a fault of SA lock, mostly its appear in Denali drives.

You can use SA unlock function first then power reset and backup the firmware. then do all of your required process.
If it not helps then let me know

i will check it by remote

Regards
Waqas Ali

[fzabkar]

IIUC, here is the general procedure for unlocking the SA.

The following example is for a Hubble_LT:

http://files.hddguru.com/index.php?action=downloadfile&filename=WDC%20WD3200LPVX-08V0TT5%2005.01A05%2006.3TJ%20-%20Hubble%20LT.zip&directory=Non-PC-3000%20firmwares/Western%20Digital/HUBBLE%20LT

Offset 0xAA defines the desired section of module 02, ie location 0x0708, size 0x0099. The next section begins at 0x07A1.

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

Code:

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

00000700                          00 01 32 90 01 00 00 1E
00000710  00 00 00 64 00 00 00 64 00 00 00 64 00 00 00 64
00000720  00 00 00 00 04 00 00 00 02 00 00 06 00 00 00 FD
00000730  FF 00 00 FF FF 00 00 05 0A 0A 00 00 00 FD FF 00
00000740  00 FF FF 00 00 01 0E 00 00 00 00 00 00 00 00 00
00000750  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000760  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000770  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000780  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000790  00 00 00 00 00 00 00 00 00 00 D6 06 00 1E 00 00
000007A0  00                         ^^ change to 01 to unlock

[fzabkar]

Sorry, I think that should have been "change from 01 to 00 to unlock".

[pikus_09]

Yes its a fault of SA lock, mostly its appear in Denali drives.

You can use SA unlock function first then power reset and backup the firmware. then do all of your required process.
If it not helps then let me know

i will check it by remote

Regards
Waqas Ali

Well, My denali work fine ie SA self, and SA format without Error.
Only Wd Black have this problem in SA Format, so I click SA Unlock, and wait 5 sec, done. Drive perfect initialize, and must perform Full ARCO procedure, because Total Parameters are incorrect.
Now currently Run ARCO procedure, if done check your procedure.

IIUC, here is the general procedure for unlocking the SA.

The following example is for a Hubble_LT:

http://files.hddguru.com/index.php?action=downloadfile&filename=WDC%20WD3200LPVX-08V0TT5%2005.01A05%2006.3TJ%20-%20Hubble%20LT.zip&directory=Non-PC-3000%20firmwares/Western%20Digital/HUBBLE%20LT

Offset 0xAA defines the desired section of module 02, ie location 0x0708, size 0x0099. The next section begins at 0x07A1.

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

Code:

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

00000700 00 01 32 90 01 00 00 1E
00000710 00 00 00 64 00 00 00 64 00 00 00 64 00 00 00 64
00000720 00 00 00 00 04 00 00 00 02 00 00 06 00 00 00 FD
00000730 FF 00 00 FF FF 00 00 05 0A 0A 00 00 00 FD FF 00
00000740 00 FF FF 00 00 01 0E 00 00 00 00 00 00 00 00 00
00000750 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000760 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000770 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000780 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000790 00 00 00 00 00 00 00 00 00 00 D6 06 00 1E 00 00
000007A0 00 ^^ change to 01 to unlock

Sorry, I think that should have been "change from 01 to 00 to unlock".

Ok, so if done procedure ARCO, I will try to check yours suggestion.

[fzabkar]

I believe that WDMarvel prints out all the sections of module 02. Otherwise you could use my program to do the same.

Code:

Usage:  MOD2DUMP filename [section_number]

C:\>mod2dump "\wd\firmware\hubble_lt\02.mod" 31

ROYL header found

Module 02 consists of 47 sections


Section 31     Length 153 bytes

Addr  00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0000  00 01 32 90 01 00 00 1E 00 00 00 64 00 00 00 64  ..2........d...d
0010  00 00 00 64 00 00 00 64 00 00 00 00 04 00 00 00  ...d...d........
0020  02 00 00 06 00 00 00 FD FF 00 00 FF FF 00 00 05  ................
0030  0A 0A 00 00 00 FD FF 00 00 FF FF 00 00 01 0E 00  ................
0040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0050  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0070  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0090  00 00 D6 06 00 1E 00 00 00                       .........

Attachments

MOD2dump.rar

(85.08 KiB) Downloaded 1114 times

[pikus_09]

Yes, WD marvel show all contents in module 02, but is very poor if Regarding Arco seqence, or self test, or refurb.
As I write, If Arco procedure will done, i will check Yours suggestions.
Thank you very much Friends.

[waqas_ali766]

Hi
Pikus_09 you problem is with SA lock, not a SED lock, 02 editing is used to unlock SED drives.

Editing 02 is used to unlock WD SED drives,
the WD SED drive cannot allow you to read and write firmware and rom,

in this condition , you have to show tv9 and tv10, then wait for ready status, after that remove short points, then auto detect and enter into the program

goto Main and click init hdd0, then goto dir manager, and press dir edit, then close it,
now backup 11 12 13 1b modules, backup 5c if hdd have.

now again power off, short tv9 and tv10 wait for ready status, load overlays, then remove short points

Init HDD 0 (this is used to initilize 01 module from hdd SA to ram, to get access on firmware )
Dir edit, then close it,
now open 02 in hex, find the byte, Hubble_lt locked hdd have offset 725, different families have different offsets. but the byte structure is same.


NOTE : If you need data then must backup original 02, and after repair you must write original 02 or make byte same to same as original.

Change this byte from 01 to 00 unlock the SED protection but encrypt the data (you can check sector 0 after and before edit 02 to understand properly)


This method is used for repairing only.

Regards
Waqas Ali
www.sediv.net

[pikus_09]

Hi
Pikus_09 you problem is with SA lock, not a SED lock, 02 editing is used to unlock SED drives.

Editing 02 is used to unlock WD SED drives,
the WD SED drive cannot allow you to read and write firmware and rom,

in this condition , you have to show tv9 and tv10, then wait for ready status, after that remove short points, then auto detect and enter into the program

goto Main and click init hdd0, then goto dir manager, and press dir edit, then close it,
now backup 11 12 13 1b modules, backup 5c if hdd have.

now again power off, short tv9 and tv10 wait for ready status, load overlays, then remove short points

Init HDD 0 (this is used to initilize 01 module from hdd SA to ram, to get access on firmware )
Dir edit, then close it,
now open 02 in hex, find the byte, Hubble_lt locked hdd have offset 725, different families have different offsets. but the byte structure is same.


NOTE : If you need data then must backup original 02, and after repair you must write original 02 or make byte same to same as original.

Change this byte from 01 to 00 unlock the SED protection but encrypt the data (you can check sector 0 after and before edit 02 to understand properly)


This method is used for repairing only.

Regards
Waqas Ali
www.sediv.net

Ok, I will check your suggestion, if ARCO completed.

[waqas_ali766]

Hi
Also if it show you msg DCO lock, in back ground its already finished the format Sa. you can check Regions after this format SA.

Regards
Waqas Ali

[pikus_09]

Hi
Also if it show you msg DCO lock, in back ground its already finished the format Sa. you can check Regions after this format SA.

Regards
Waqas Ali

Hi, checked your suggestions and SA format work in wd black, you are right, SA Unlock function first, then SA format.
But, self test scanning A lot of bad sectors in Head 0, and exceeds the limit of defects, and Self STOP, well i don't think that head 0 is BAD in User Area, because TEST all heads passed in Sa Area, and User area, well i think maybe Adaptives? What do you think?

[pikus_09]

Hi
Also if it show you msg DCO lock, in back ground its already finished the format Sa. you can check Regions after this format SA.
Regards
Waqas Ali

Hi, checked your suggestions and SA format work in wd black, you are right, SA Unlock function first, then SA format.
But, self test scanning A lot of bad sectors in Head 0, and exceeds the limit of defects, and Self STOP, well i don't think that head 0 is BAD in User Area, because TEST all heads passed in Sa Area, and User area, well i think maybe mismatch MJog Adaptives? What do you think?

[waqas_ali766]

Hi
Its not a MR jog problem.

The process of ARCO and SF is as follow

44 ARCO
6a
6f
6b or 290b or 2420
69 or 290b or 2420
46
4a

after this 4a hdd is ready for Self test, or manually testing of sector and adding into p-list, but without WRRO read and write test HDD never run format with P-list. and without WRRO read test hdd always full the SF logs.

B2 Write = WRRO write
B2 XMS
B2 READ = WRRO Read
D8 OR 3421
D1
Dd
DB etc

also you can use Sediv 5152 version and use ARCO+SA FULL TEST and choice the path of hdd original firmware. if will automatic repair all things and make hdd ready for you. auto start B2

if after B2 the logs still full, then its a fault of some zone, you can follow my video to find and cut faulty physical zone.

viewtopic.php?f=22&t=33829


Regards
Waqas

[pikus_09]

Hi
Its not a MR jog problem.

The process of ARCO and SF is as follow

44 ARCO
6a
6f
6b or 290b or 2420
69 or 290b or 2420
46
4a

after this 4a hdd is ready for Self test, or manually testing of sector and adding into p-list, but without WRRO read and write test HDD never run format with P-list. and without WRRO read test hdd always full the SF logs.

B2 Write = WRRO write
B2 XMS
B2 READ = WRRO Read
D8 OR 3421
D1
Dd
DB etc

also you can use Sediv 5152 version and use ARCO+SA FULL TEST and choice the path of hdd original firmware. if will automatic repair all things and make hdd ready for you. auto start B2

if after B2 the logs still full, then its a fault of some zone, you can follow my video to find and cut faulty physical zone.

viewtopic.php?f=22&t=33829


Regards
Waqas

Yeah, Arco 44 not work in sediv 5152 propertly New adaptives not work, Hdd restart after 5sec, can not calibrated.
6a = OK without error
6f = OK without error
2909 = OK without error, and TPI and Head Qual adjusted
69 or 290b or 2420 = My WDek not have test C8, because this test in implemented in 2909.
46 = Ok without error
4a = Ok without error

Then Run Self test, and check now if limit the defects will be filled again.

B2 Write = WRRO write
B2 XMS
B2 READ = WRRO Read
D8 OR 3421
D1
Dd
DB etc

also you can use Sediv 5152 version and use ARCO+SA FULL TEST and choice the path of hdd original firmware. if will automatic repair all things and make hdd ready for you. auto start B2

if after B2 the logs still full, then its a fault of some zone, you can follow my video to find and cut faulty physical zone.

viewtopic.php?f=22&t=33829


Regards
Waqas

Yes, but I run selftest using oryginaly Factory Selftest script for WD Black for WD2002FAEX not in internet, understand?
Yes, I Use Sediv5152.
Btw, Waqas you had a WD Blacks in repair, or similar to My WDek?

[waqas_ali766]

Hi
I will Calibrate 44 mantis family 100% good.
if you are using function create and start calibrate, then it have a different procedure.
you must have to see my video on real case studies.

yes i repair all WD drives even the latest Hybrid drives SED locked.

By mistake i write 2909, its 290b

The original SF script in the hard disk is not perfect, because after hard disk manufacture factory remove many many important tests from the script.

you must have to use universal scripts. you can download from forum.

By the way from where you buy Sediv ?

Regards
Waqas Ali

[pikus_09]

Hi
I will Calibrate 44 mantis family 100% good.
if you are using function create and start calibrate, then it have a different procedure.
you must have to see my video on real case studies.

yes i repair all WD drives even the latest Hybrid drives SED locked.

By mistake i write 2909, its 290b

The original SF script in the hard disk is not perfect, because after hard disk manufacture factory remove many many important tests from the script.

aaaa, that's it, IN my oryginal script not perfect, but in forum hddguru not found correct script for My Mantis_PL_RE, only Mantis_RE/DRAGFLY-4

By the way from where you buy Sediv ?

Regards
Waqas Ali

Sediv I bought from the author Mr. DIV, He helped me in this my friend Vides. And if you have correct script for mantis_pl_RE send to my pm. Or this therard thank you friend for help.