WD WD10PURZ-85U8XY0 - Won´t spin with original Bios

[grevan]

Hi guys,
WD10PURZ-85U8XY0 (PCB 2060-800006-001) won´t spin with original Bios.
Voltages seem fine.
I got this donor WD10PURZ, PCB 2060-800039-001, swapped bios with each other just to study behavior.
Patient Bios won´t power donor, but donor Bios does power patient.
Looks like Bios problem.

* By the way, i dont have the WD terminal, is it GND-RX-TX, top row (GND next SATA)?

Done a little research, looks like there are no unique rom modules on this family TrailXLB.

[grevan]

Is it possible to regenerate rom with donor resources, or any other one?

[fzabkar]

Is it a PUIS issue (Power Up In Standby)?

Can you upload a BIOS dump? I have a tool to check the BIOS segments.

[grevan]

Thanks, I dont believe is a PUIS issue, tried without the 3.3v and it's the same.
I will make a dump later today with an external reader.
Hdd is not recognized in MRT.
* Do you know what is the terminal order , is it GND-RX-TX, top row (GND next SATA)?

[fzabkar]

PUIS has nothing to do with the SATA power disable pin. It is a setting that is enabled/disabled by software, eg HDAT2. The PUIS flag byte resides in module 0x0D in ROM.

As for the order of the Tx/Rx/Gnd pins, I don't recall, but you have MRT ...

[grevan]

Yes, i was thinking about PWDIS, sorry.
I attached two dumps, one from the patient and the other from "donor".
Patient chip is Winbond 25q16jw, other Winbond 25Q20BW.
Thanks

Attachments

WD10PURZ ROM.zip

(1.99 MiB) Downloaded 5 times

[grevan]

By the way, is your "users.on.net" directory still on? Could not access it.
*** Got it from Wayback, thanks!

[grevan]

One question, do your programs need to be executed from 32bits Windows?

[fzabkar]

My software should run in a CMD window in 32-bit or 64-bit Windows.

Your ROM size is actually 0x40000 bytes, ie 256KB. Your dumps are 8 times too large.

Your patient ROM is not a WD ROM. It seems to be NVIDIA firmware.

Code:

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

00009400  55 AA 7F EB 4B 37 34 30 30 E9 4C 19 77 CC 56 49  Uª.ëK7400éL.wÌVI
00009410  44 45 4F 20 0D 00 00 00 70 01 33 16 00 00 49 42  DEO ....p.3...IB
00009420  4D 20 56 47 41 20 43 6F 6D 70 61 74 69 62 6C 65  M VGA Compatible
00009430  01 00 00 00 00 00 54 59 30 34 2F 31 33 2F 32 31  ......TY04/13/21
00009440  00 00 00 00 00 00 00 00 00 10 50 00 9F FD 00 00  ..........P.Ÿý..
00009450  E9 C1 25 90 50 4D 49 44 23 38 2D 38 00 00 00 A0  éÁ%.PMID#8-8... 
00009460  00 B0 00 B8 00 C0 00 4E 45 34 37 33 35 20 53 4B  .°.¸.À.NE4735 SK
00009470  55 20 31 31 30 20 56 47 41 20 42 49 4F 53 20 0D  U 110 VGA BIOS .
00009480  0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00009490  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000094A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000094B0  00 00 00 00 00 00 00 00 00 56 65 72 73 69 6F 6E  .........Version
000094C0  20 39 34 2E 30 36 2E 31 46 2E 30 30 2E 31 44 20   94.06.1F.00.1D
000094D0  0D 0A 00 43 6F 70 79 72 69 67 68 74 20 28 43 29  ...Copyright (C)
000094E0  20 31 39 39 36 2D 32 30 32 31 20 4E 56 49 44 49   1996-2021 NVIDI
000094F0  41 20 43 6F 72 70 2E 0D 0A 00 00 00 FF FF 00 00  A Corp......ÿÿ..
00009500  00 00 FF FF 47 50 55 20 42 6F 61 72 64 00 00 00  ..ÿÿGPU Board...
00009510  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00009520  00 00 00 00 00 00 00 43 68 69 70 20 52 65 76 20  .......Chip Rev

Last edited by fzabkar on May 30th, 2026, 17:34, edited 1 time in total.

[grevan]

Got your software to run, i think i was missing the ".bas" file.

[fzabkar]

The BAS file is FreeBasic source code. It is not required. You just need to run the EXE.

[grevan]

Ah, ok, but i managed to run it.
About the dumps, yes, strange, and they both have same size, the "donor" can be parsed on your utility.

[grevan]

Looks like someone changed the chip....
Story is, DVR hdd from computer repair shop, owner believes employee has been steeling some hardware and camera stopped recording.

[grevan]

Found a similar thread, maybe it´s possible to regenerate rom, same model and PCB.
https://forum.hddguru.com/viewtopic.php ... t=wd10purz

Anyideas?

[fzabkar]

Ah, ok, but i managed to run it.
About the dumps, yes, strange, and they both have same size, the "donor" can be parsed on your utility.

The donor is a 2Mbit chip (W25Q20BW = 256KB). The patient is a 16MBit chip (W25Q16JW = 2MB).

[fzabkar]

If you can reach the SA with your donor, get modules 0x109, 0x129, 0x130, assuming they exist. The latter two modules do not appear in the DIR module (0x01), so you need to use a special access method. Your MRT documentation should tell you how to do this (I don't know how).

You can then regenerate your ROM from 0x109 plus either of 0x129 or 0x130. I have written tools to do this, if MRT cannot.

[grevan]

Now i got the right size, reader was not recognizing well.

Attachments

WD10PURZ.zip

(629.35 KiB) Downloaded 4 times

[grevan]

Bios from a RTX 3060 6GB mobile, the guy swapped from this notebook graphic card. What a story. Do you think it matters if the bios capacity is different from the original? If it's bigger, maybe not?

[fzabkar]

I can't see why a larger ROM would be a problem, but I'm not a data recovery professional.

[grevan]

I'm new to MRT, got the card 2 months ago, studying a lot, so any help would be very welcome.
As i dont have the original bios chip, I think my line of action would be to solder the donor bios to patient board, try to read SA and reconstruct ROM. As you mentioned, I'll see if 0x129 or 0x130 can be obtained.
Any tips are welcome.
Thanks.