WD5000AZRX diagnostic evidence for HDD Guru thread 46336
https://forum.hddguru.com/viewtopic.php?f=1&t=46336

TARGET: WDC WD5000AZRX-00A8LB0, WD-WCC1U1920791, FW 01.01A01.
Salvaged from the owner's old PC. Files were collected on 2026-10-12 using
HDDSuperTool through a JMicron USB-SATA bridge (152d:0583).
This package was made from saved files only. No new drive commands were run.

CONTENTS / PROVENANCE
- target/: 402 saved module*.bin dumps plus separate mod01.bin and mod02.bin.
  Module IDs in filenames are hexadecimal. All 404 files match the saved
  original-target-SHA256SUMS. All 402 module files have ROYL headers and are
  non-empty. Header presence and hash agreement are NOT a firmware-validity
  or target-compatibility guarantee.
- logs/: historical Identify/SMART/self-test/dump and copy-read logs, unchanged.
  IMPORTANT: wd-smart.txt and wd-selftest.txt are earlier snapshots; the latter
  still shows a failed self-test. They are NOT fresh post-repair diagnostics.
- donor-WCC1U4970086/: same-model donor files, NOT target dumps. Donor 32.rpm
  and mod32_cleared.bin are byte-identical. The source folder is labeled
  explicitly so no donor can be mistaken for firmware read from the target.
- procedure-used/: the saved MOD32 manipulation and write scripts, included
  only to show the operation already performed. DO NOT run them as a repair
  instruction or interpret them as a drive-native RELO-clear command.
- original-target-SHA256SUMS: original source-folder manifest. Some listed files
  are deliberately excluded (email/forum drafts); use package-SHA256SUMS to
  verify THIS package.
- inventory.tsv: archive path, byte length and SHA256 of each payload file.
- package-SHA256SUMS: hashes for every member except this manifest itself.

KNOWN WRITE / RESULT (FROM THE PRIOR SESSION HANDOFF AND FORUM UPDATE)
The documented service-area write was donor MOD32. A power-cycle readback was
reported byte-identical, and the short self-test subsequently passed; all host
LBA reads/writes still aborted (ABRT). This archive does not itself contain the
later self-test output or a target MOD32 readback, so those claims are reported
history, not proven by the older logs included here.
ROM build 00650018 and SA overlays 00650019 were reported in the prior analysis.

MISSING EVIDENCE -- DO NOT SUBSTITUTE DONOR FILES
No target ROM dump or target module32.bin is present in the saved folder.
Target modules 0x148 and 0x4002 failed prepare-read and are absent too.
The head-1 physical-copy attempt returned zero geometry, crashed the tool
(divide-by-zero), and the drive disconnected. Its log is included. No data was
recovered by that attempt. No forced physical reads were repeated for packaging.

Privacy: the archive includes the target/donor serials and original tool logs.
Email/forum request drafts and unrelated files are excluded. No passwords,
credentials, user-data sectors, or session transcript are intentionally included.
Retain the untouched source backup. This is diagnostic evidence, not firmware
approved for flashing. Wait for a drive-specific, reviewed repair procedure.
