WD5000BCUT - Help

[Core.iStores]

can anyone helps me solve this problem i have WD 500G and the log as follows:

Family:................................. : Zephyr 2.5"
Techno mode key......................... : Ok

HDD Status sector....................... : Ok

RAM:
System controller (SoC)................. : 88i9146B2 0x(7412)
HDD Info reading........................ : Ok
Heads number............................ : 3
Cyl Count............................... : 256

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 256 Kb
Flash ROM dir reading................... : Ok
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted

SA SPT.................................. : 1098

SA Translator loading................... : Ok

ROM Modules:
ROM version............................. : 10.2DA
Module 4F F/W version................... : 0010002D
Overlay F/W version..................... : 10.2DA
Servo F/W version....................... : 02.18

Heads configuration..................... : by map
Heads number............................ : 3
Heads number in use..................... : 3
Switched off heads...................... : No
Heads map............................... : 0,1,2

Relocations............................. : 0 (0)
Read ROM DCM............................ : Ok

Power up log reading.................... : Ok
Power up load dir data.................. : Yes
Power up load permovl................... : Yes
Power up load CFG data.................. : No
----+------+--------+----------+----------+--------------------------------------------------
NN | Step | Time | Flags | Info | Description (32-bits)
----+------+--------+----------+----------+--------------------------------------------------
18 | 107 | 8.00 s | 2000087E | 514051A2 | EXEC_POWERUP_LOAD_PERMOVL(DISK ECU UNSAFE ERROR)
----+------+--------+----------+----------+--------------------------------------------------

Service area:
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 446

SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
CFG tech mode lock...................... : No
Self encryption drive................... : No
Master Password......................... : has not been set
User Password........................... : has not been set

DCM in module 47........................ : QM
DCM in module 0A........................ : |M|EQMSHEF
DCM in module 02........................ : S|BML|PEMQHMCSRHVEKJUJ

and after uploading the Loader it shows the details that in the attached photo

Attachments

Untitled.png (3.39 KiB) Viewed 10237 times

[unknown]

Did you try to load LDR?

[Core.iStores]

Did you try to load LDR?

this is after uploading the LOADER

[unknown]

Did you try to edit head map in RAM to start from head 1 ?

[Core.iStores]

Did you try to edit head map in RAM to start from head 1 ?

yes i did

[unknown]

Do you hear the drive calibrate normally?
Is it taking more time to reach ready state?

[Zero Alpha]

Log shows it can access system area. Did you check the firmware?

[Core.iStores]

Log shows it can access system area. Did you check the firmware?

I DID THE BACKUP AND IT ALWAYS SHOWS CAPACITY IS 188 G

[unknown]

Upload ROM + module 02 here

[Core.iStores]

Upload ROM + module 02 here

here they are

Attachments

Data.rar

(241.06 KiB) Downloaded 254 times

[fzabkar]

Mod 0x02 shows full capacity (0x3A38602F = 976773168 - 1), so there is no HPA. The size must be coming from the ROM.

Code:

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

000000E0                                         2F 60 38
000000F0  3A 2F 60 38 3A 2F 60 38 3A 2F 60 38 3A

[fzabkar]

This is the ROM directory (mod 0x0B):

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19

00000000  52 4F 59 4C 04 00 1E 00 0B 00 01 00 73 11 CB ED 30 30 30 32 30 30 30 30 00 00
0000001A  00 00 00 00 09 1A 01 0A 00 3E 00 00 19 00 00 B2 FF 03 00 00 00 00 00 00 00 00
00000034  00 00 00 00 00 1A 01 0B 00 4F 01 00 19 00 00 63 FE 03 00 00 00 00 00 00 00 00
0000004E  00 00 00 00 00 1A 01 30 00 00 04 00 19 00 00 63 FA 03 00 00 00 00 00 00 00 00
00000068  00 00 00 00 00 1A 01 47 00 00 04 00 19 00 00 D3 F5 03 00 00 00 00 00 00 00 00
00000082  00 00 00 00 00 1A 01 11 04 90 00 00 19 00 00 D3 F9 03 00 FF FF 11 04 00 00 00   <--- entry for module 0x411 ???
0000009C  00 00 00 00 00 1A 01 4F 00 00 04 00 19 00 00 D3 F1 03 00 00 00 00 00 00 00 00
000000B6  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000000D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000000EA  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000104  00 00 00 00 00 46 03 FF 0F 07 00 80 37 03 00 00 00 00 00 80 37 03 00 00 4A 04
0000011E  00 80 37 03 00 00 94 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000138  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The entry for module 0x411 (???) points to ROM offset 0x3F9D3. That's module 0x0D. There is no entry for module 0x0D in the directory.

Is this a red herring, or has someone been meddling with the ROM?

Code:

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

0003F9D0           52 4F 59 4C 04 00 1E 00 0D 00 01 00 0A     ROYL.........
0003F9E0  9B 48 E9 30 30 30 31 30 30 30 30 00 00 00 00 00  ›Hé00010000.....
0003F9F0  00 00 01 30 31 2E 30 31 41 30 31 00 00 03 00 00  ...01.01A01.....
0003FA00  00 50 01 4E E6 57 54 D7 E1 00 01 FE FF 00 00 00  .P.NæWT×á..þÿ...
0003FA10  00 02 00 01 01 00 01 00 00 57 44 43 20 57 44 35  .........WDC WD5
0003FA20  30 30 30 42 55 43 54 2D 36 33 50 55 5A 59 30 20  000BUCT-63PUZY0
0003FA30  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0003FA40  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0003FA50  20 20 20 20 20 00 00 00 00 00 00 32 00 00 00 00
0003FA60  02 02 00

I can fix this, if you want to try.

Could you upload module 0x109? That should contain templates for the ROM resident ROYL modules.

[Core.iStores]

This is the ROM directory (mod 0x0B):

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19

00000000  52 4F 59 4C 04 00 1E 00 0B 00 01 00 73 11 CB ED 30 30 30 32 30 30 30 30 00 00
0000001A  00 00 00 00 09 1A 01 0A 00 3E 00 00 19 00 00 B2 FF 03 00 00 00 00 00 00 00 00
00000034  00 00 00 00 00 1A 01 0B 00 4F 01 00 19 00 00 63 FE 03 00 00 00 00 00 00 00 00
0000004E  00 00 00 00 00 1A 01 30 00 00 04 00 19 00 00 63 FA 03 00 00 00 00 00 00 00 00
00000068  00 00 00 00 00 1A 01 47 00 00 04 00 19 00 00 D3 F5 03 00 00 00 00 00 00 00 00
00000082  00 00 00 00 00 1A 01 11 04 90 00 00 19 00 00 D3 F9 03 00 FF FF 11 04 00 00 00   <--- entry for module 0x411 ???
0000009C  00 00 00 00 00 1A 01 4F 00 00 04 00 19 00 00 D3 F1 03 00 00 00 00 00 00 00 00
000000B6  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000000D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000000EA  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000104  00 00 00 00 00 46 03 FF 0F 07 00 80 37 03 00 00 00 00 00 80 37 03 00 00 4A 04
0000011E  00 80 37 03 00 00 94 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000138  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The entry for module 0x411 (???) points to ROM offset 0x3F9D3. That's module 0x0D. There is no entry for module 0x0D in the directory.

Is this a red herring, or has someone been meddling with the ROM?

Code:

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

0003F9D0           52 4F 59 4C 04 00 1E 00 0D 00 01 00 0A     ROYL.........
0003F9E0  9B 48 E9 30 30 30 31 30 30 30 30 00 00 00 00 00  ›Hé00010000.....
0003F9F0  00 00 01 30 31 2E 30 31 41 30 31 00 00 03 00 00  ...01.01A01.....
0003FA00  00 50 01 4E E6 57 54 D7 E1 00 01 FE FF 00 00 00  .P.NæWT×á..þÿ...
0003FA10  00 02 00 01 01 00 01 00 00 57 44 43 20 57 44 35  .........WDC WD5
0003FA20  30 30 30 42 55 43 54 2D 36 33 50 55 5A 59 30 20  000BUCT-63PUZY0
0003FA30  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0003FA40  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0003FA50  20 20 20 20 20 00 00 00 00 00 00 32 00 00 00 00
0003FA60  02 02 00

I can fix this, if you want to try.

Could you upload module 0x109? That should contain templates for the ROM resident ROYL modules.

yes please

Attachments

109.rar

(239.59 KiB) Downloaded 300 times

[fzabkar]

See attached repaired ROM.

Attachments

ROM_10-2DA_10-2DA_02-18_repaired.7z

(239.06 KiB) Downloaded 304 times

Last edited by fzabkar on August 6th, 2024, 16:48, edited 1 time in total.

[Core.iStores]

deleted

sorry but what did you mean please ?

[fzabkar]

deleted

sorry but what did you mean please ?

Sorry, I made a mistake. See my previous post (edited).

[fzabkar]

Is this mod 0x411 anomaly a hack that is implemented by your tool to block SA access???

[Core.iStores]

Is this mod 0x411 anomaly a hack that is implemented by your tool to block SA access???

i don't know what the previous DR person did with the ROM, but i had access to SA after uploading the loader and backed them up


by the way the issue still the same after writing your Repaired ROM, so i think the issue is with writing heads

[fzabkar]

See this tutorial:

Patching ROM module 0x0B/0x20B to block SA module access :
https://www.hddoracle.com/viewtopic.php?p=19705#p19705

It is evident that someone used a DR tool to block access to SA module 0x411. I have looked at other Zephyr resource dumps but cannot find this module. I'm wondering whether it exists in your drive, and if not, why would someone block it?

I don't know how this works, but here is a thread where someone is offering to block SA access (to modules 02 & 411) by editing the ROM:

https://forum.hddguru.com/viewtopic.php?f=11&t=44040

Can you upload module 0x109? This module contains a copy of the ROM.

[fzabkar]

Sorry, I just realised you have already uploaded 0x109.