701590 ROM generate

19 views
Skip to first unread message

juanvd...@gmail.com

unread,
Mar 11, 2026, 7:10:51 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

I received this WD1600AAJS-08L7A0 with a dead PCB and the ROM is part of the MCU, the drive does not spin up at all. If I install a donor PCB then the drive spins with partial module access but no data access.

So before I swap the MCU to the donor drive, what modules do I need from the patient drive to generate a new ROM so that I can just write it back to the donor PCB..

 

 

juanvd...@gmail.com

unread,
Mar 11, 2026, 8:40:06 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

Just an update, I need to be very careful of what ROM I write to the donor PCB`s because I scrapped two already because of the wrong ROM for some reason.

I wrote a ROM that I received online with the same model and firmware version and it broke the donor PCB with no response. I connect another PCB, then the drive spins up with partial module access, very interesting when I tried to read mod 11 then the drive goes all nuts and switches off.

What I did see is that the patient PCB does have an IC12 as the other x3 donor drives does not have a IC12, only ROM in the MCU, but if I swap IC12 then it still boot from the MCU ROM not IC12 if I compare the WWN details.

With the WDROMv17.exe I can view the patient IC12 and all looks good and it extracted all ROM modules, I then decided to write all those modules back to the drive and on power reset nothing, another dead PCB.

 

I only have x2 boards left so is there a way to get the correct ROM on the donor PCB without MCU swap ?

George Yakobic

unread,
Mar 11, 2026, 8:51:23 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

For your WD1600AAJS PCB swap, you need to extract the complete ROM image from your original drive's MCU. This contains:

  • Head mapping data
  • Calibration parameters
  • Servo-track information
  • SMART data
  • Adaptive values

Your Options:

  1. Physical MCU Transfer (most reliable): Desolder the MCU from your patient PCB and install it on the donor PCB.

  2. ROM Extraction & Re-flashing: Use a ROM programmer (TL866II+, Xeltek, or dedicated HDD ROM clip programmer) to extract the ROM image from your original MCU, then write it to a compatible chip on the donor PCB.

  3. Serial Boot Mode: If the chip can't be removed, access UART pins and short the "magic" pins to force serial boot mode for firmware dumping.

Key Points:

  • Donor PCB firmware version must match your original drive
  • Verify MCU chip part numbers match
  • If extraction fails, you risk bricking the donor PCB

Since your drive already spins with partial module access on the donor PCB, you're close. The ROM transfer is the critical step.


--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/004e01dcb154%242d287e70%2487797b50%24%40gmail.com.

Luke Coughey

unread,
Mar 11, 2026, 9:12:28 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com
Since when can a ROM programmer interface with the MPU to extract the ROM & since when was the ROM from this series of WD totally unique that it cannot be replicated?

1. Why is the board dead? Might it be something that can be repaired?
2. If it is only the 12V line that is dead, can you still get to boot ROM mode on PC3K to save the ROM via terminal?
3. If you can get to the SA with a donor board, can you not read the backup ROM modules and write them to a donor board?
4. If you have access to the SA, find out the exact ROM version from the modules, find a ROM backup with a matching ROM version and write it to a donor board.

In this type of scenario, there should be zero need to transplant the MCU.

Luke Coughey
CEO
Recovery Force Inc

This e-mail is intended solely for the person or entity it is sent to and may contain confidential and/or privileged information.  Any review, dissemination, reproduction or other use of this e-mail by persons or entities other than the intended addressee is prohibited.  If you have received this e-mail in error, please contact the sender immediately and delete and destroy this message, all attached material and all electronic reference from all computing based devices.


juanvd...@gmail.com

unread,
Mar 11, 2026, 9:44:34 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

Thanks Luce just to update:

 

  1. I compared all voltage between patient and donor and they were all the same. 5v 12 and a 1.6v points
  2. If I go to boot mode it display 88i8846A2 interface with speed of 23040, but then it say internal ROM:NO and external ROM: NO
  3. I extracted the rom modules from the u12 ROM from the patient and wrote it all back onto the donor PCB but that resulted in a no-response board as well.
  4. Still busy with that.

pbzcbf...@gmail.com

unread,
Mar 11, 2026, 10:35:46 AM (yesterday) Mar 11
to DataRecoveryCertification
You need 0x102, 0x103, 0x104, 0x105, 0x106, 0x107, 0x109. I can rebuild the ROM for you if your tool can't do it.

On Wednesday, March 11, 2026 at 10:10:51 PM UTC+11 juanvd...@gmail.com wrote:

... what modules do I need from the patient drive to generate a new ROM so that I can just write it back to the donor PCB..

 

 

juanvd...@gmail.com

unread,
Mar 11, 2026, 11:02:19 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

This is the ROM read from IC12 on external reader, I then extracted the ROM modules.

When I write all those models to the donor PCB with the patient IC12 soldered on then the PCB is dead.

 

I believe the MCU is not 100% compatible and this is my issue

Patient : 88i8846E-TFJ2

Donor: 88i8846-TPJ2

 

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of pbzcbf...@gmail.com
Sent: Wednesday, 11 March 2026 16:36
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: Re: 701590 ROM generate

 

You need 0x102, 0x103, 0x104, 0x105, 0x106, 0x107, 0x109. I can rebuild the ROM for you if your tool can't do it.

On Wednesday, March 11, 2026 at 10:10:51PM UTC+11 juanvd...@gmail.com wrote:

... what modules do I need from the patient drive to generate a new ROM so that I can just write it back to the donor PCB..

 

 

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

New folder (3).rar

Desert Data Recovery

unread,
Mar 11, 2026, 11:09:06 AM (yesterday) Mar 11
to datarecovery...@googlegroups.com

pbzcbf...@gmail.com

unread,
Mar 11, 2026, 11:22:38 AM (yesterday) Mar 11
to DataRecoveryCertification
You need to recover the 0x10n modules from the SA, assuming you can't dump the internal ROM from the MCU.

pbzcbf...@gmail.com

unread,
Mar 11, 2026, 1:21:24 PM (yesterday) Mar 11
to DataRecoveryCertification
Measure the voltages at the pins of Q1 (near the SATA power connector). You should find +3.9V, +5V, +3.3V.

Measure the voltages at L1 and L2 (inductors near the SMOOTH IC).

Measure the voltage at the anode of diode D2 ( near the SMOOTH IC). This is the -5V supply for the preamp. It may briefly come up and then switch off within a second or two.
Reply all
Reply to author
Forward
0 new messages