Rosewood family rom corrupted

66 views
Skip to first unread message

Abdur Rahim Sopon

unread,
Aug 19, 2026, 11:15:48 AM (6 days ago) Aug 19
to DataRecoveryCertification

Hello dear members,

We received an A5 2TB HDD with corrupted ROM data. The HDD was sent to us by another data recovery company, and they provided us with this ROM backup.

Is it possible to rebuild or repair the ROM data from this backup?

Any advice or suggestions would be greatly appreciated.


 
Case ID 11234.bin

compos mentis

unread,
Aug 19, 2026, 11:39:01 AM (6 days ago) Aug 19
to datarecovery...@googlegroups.com

I have had a quick look at the ROM and I cannot find any obvious problems. Do you have a terminal log?

  --
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/5b5e1b67-2da4-4f4e-8d9b-41ca91c485fan%40googlegroups.com.

Abdur Rahim Sopon

unread,
Aug 19, 2026, 11:40:56 AM (6 days ago) Aug 19
to datarecovery...@googlegroups.com

Flash boot code Digital Signature Verification failure!
0x0020
0x0020
0x0020
0x0020
0x0020
SEA5 Boot ROM 1.0 (9/18ï













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Abdur Rahim Sopon

unread,
Aug 19, 2026, 11:45:35 AM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
Cap info bad 
 ............................................... ROM INFO:

 ............................................... Flash Size:0x100000

 ............................................... RAP
 ............................................... # # #
 ............................................... Format Revision:0x208
 ............................................... Contents Revision:0x53050100
 ............................................... Fw Implementation Key:0x1E
 ............................................... RAP Check OK

 ............................................... CAP
 ............................................... # # #
 ............................................... Validation Key:0xFFFFFFFF
 ............................................... Fam ID:0xFF
 ............................................... Fam Member:0xFF
 ............................................... Head:FF
 ............................................... Date:ÿÿ-ÿÿ-ÿÿÿÿ
 ............................................... SN:ÿÿÿÿÿÿÿÿ
 ............................................... PCB PN:ÿÿÿÿÿÿÿÿÿÿÿÿ
 ............................................... WWN:FFFFFFFFFFFFFFFF
 ............................................... CAP Check OK

 ............................................... SAP
 ............................................... # # #
 ............................................... Addr:0x80000
 ............................................... Fam ID:0xA5
 ............................................... Fam Member:0x1
 ............................................... SN:WDZH0MPF
 ............................................... Servo FW rev Code:0x8973
 ............................................... RPO mode:0x5
 ............................................... SAP Check OK













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

compos mentis

unread,
Aug 19, 2026, 11:57:09 AM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
That happens when you transfer the ROM to another PCB, or when you write
an unlocked ROM to the original PCB.

Also, I now notice that the CAP module is empty.

Abdur Rahim Sopon

unread,
Aug 19, 2026, 12:15:41 PM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
yes we see this message when we swap pcb and unlock rom write back in new hdd MF after 2020.
But this HDD MF is from 2018.
I think this HDD issue stems from a ROM issue. 
 













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

--
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.

compos mentis

unread,
Aug 19, 2026, 12:30:02 PM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
Does the SAP S/N (WDZH0MPF) match the label?

Can you show us a photo of the label and the component side of the PCB?
I'd like to compare date codes.

I found this S/N in the extra space at the end of the ROM -- WES0N3XC. I
also found a copy of the SAP which does not match your actual SAP module.

compos mentis

unread,
Aug 19, 2026, 12:32:51 PM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
WES0N3XC is a Mobile HDD 1TB, Model Number ST1000LM035.

https://www.seagate.com/au/en/support/warranty-and-replacements/

compos mentis

unread,
Aug 19, 2026, 12:40:44 PM (6 days ago) Aug 19
to datarecovery...@googlegroups.com
Your Product
Mobile HDD 2TB
Model Number
ST2000LM007
SerialNumber
WDZH0MPF

Abdur Rahim Sopon

unread,
Aug 20, 2026, 6:34:59 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
Hello 

compos mentis

Yes, this is the original info from the HDD.
Is it possible to repair the ROM module using a donor ROM?













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

--
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.

compos mentis

unread,
Aug 20, 2026, 9:48:21 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
We would need to determine what the other shop did. To this end I would
need to see photos of the label and component side of PCB. You still
have not provided this.

The ROM has a digital signature. If the MCU has a security/encryption
key, and if the PCB has been replaced, then we would need to find a
donor PCB with the same firmware version, and then patch the patient's
adaptives into the donor ROM.

The result would be ...

  patient HDA

  donor PCB and donor MCU with donor's MCU key

  donor ROM with same code version as patient but with donor's digital
signature

  patient's adaptives

Your PCB has the donor's ROM with the donor's RAP and SAP in the "extra
space" at the end. We can only hope that the primary RAP and SAP are the
originals. The CAP is empty for some unknown reason.

We need to examine the PCB to see if there is any evidence of soldering.

I have attached the donor's SAP and partial RAP which were carved out of
extra space.
donor_adaptives.7z

Abdur Rahim Sopon

unread,
Aug 20, 2026, 10:09:37 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com



I found they solder only rom chip.  














Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685


--
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.
Message has been deleted
Message has been deleted

pbzcbf...@gmail.com

unread,
Aug 20, 2026, 10:48:15 AM (5 days ago) Aug 20
to DataRecoveryCertification
The firmware build dates in your ROM are as follows.


First half:

    2016-07-13  02:32:16

    2016-07-13  02:32:18

    2016-06-15  07:09:36

    2016-06-15  07:09:39


Second half:

    2016-08-03  07:16:37

    2016-08-03  07:16:39

    2016-06-15  07:09:36

    2016-06-15  07:09:39


That's a difference of 2 years. It may be that there were no updates in
2 years, but it does look suspicious.

Alandata Recovery

unread,
Aug 20, 2026, 10:49:16 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
Also you should compare serial number on lid 
With serial sticker on the body. 
They could mix up the lids.
Rom also has serial number of drive and pcb's serial number. 


Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

On Thu, Aug 20, 2026, 7:30 AM compos mentis <pbzcbf...@gmail.com> wrote:
The firmware build dates in your ROM are as follows.


First half:

     2016-07-1302:32:16

     2016-07-1302:32:18

     2016-06-1507:09:36

     2016-06-1507:09:39


Second half:

     2016-08-0307:16:37

     2016-08-0307:16:39

     2016-06-1507:09:36

     2016-06-1507:09:39



That's a difference of 2 years. It may be that there were no updates in
2 years, but it does look suspicious.

--
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.

compos mentis

unread,
Aug 20, 2026, 10:52:53 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com

The date codes are:

  SDRAM -- 828 -- week 28 of 2018

  MCU -- 1832 -- week 32 of 2018

  SMOOTH -- 833 -- week 33 of 2018

Show me the ROM and LABEL. Please.

Abdur Rahim Sopon

unread,
Aug 20, 2026, 11:50:54 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
image.png

image.png













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

--
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.

compos mentis

unread,
Aug 20, 2026, 11:56:23 AM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
The manufacture date is 13 Oct 2018

The date code on the ROM is 1820. That's week 20 of 2018, which is two
months earlier than the SDRAM. This looks suspicious.

compos mentis

unread,
Aug 20, 2026, 12:39:20 PM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
AFAICT, the PCB S/N should be stored in the CAP, but the CAP is empty.
Patient_adaptives.7z

pbzcbf...@gmail.com

unread,
Aug 20, 2026, 1:11:41 PM (5 days ago) Aug 20
to DataRecoveryCertification

I don't know if this is a red herring, but I'm finding firmware versions SDM2 and SBM3 in the first BOOTFW container.

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

00000000  01 1A 00 00 F8 07 00 00 00 00 00 00 9F 31 18 00  ....ø.......Ÿ1..
00000010  63 73 69 44 00 00 49 3E 1C B7 00 00 20 FF FF FF  csiD..I>.·.. ÿÿÿ
00000020  16 40 00 00 15 48 00 00 18 78 07 00 10 F0 07 00  .@...H...x...ð..
00000030  0E E8 0A 02 03 F8 0E 02 0B F8 A6 03 00 F8 B8 03  .è...ø...ø¦..ø¸.
00000040  00 00 00 00 A3 E2 00 00 64 00 01 00 FF FF FF 7F  ....£â..d...ÿÿÿ.
00000050  17 06 03 13 07 00 00 00 80 A5 FD 00 00 08 26 84  ........€¥ý...&„
00000060  28 00 16 00 1E 21 05 00 12 07 23 20 07 12 16 20  (....!....# ... 
00000070  04 00 10 06 68 00 16 00 53 44 4D 32 23 20 30 00  ....h...SDM2# 0.
00000080  00 00 00 01 00 00 00 00 21 00 01 00 00 00 E2 9A  ........!.....âš
00000090  A2 00 02 00 FF FF FF 7F FF FF FF FF FF FF FF FF  ¢...ÿÿÿ.ÿÿÿÿÿÿÿÿ


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

00006C00  53 54 33 5F 49 4E 56 41 4C 49 44 5F 50 46 4D 53  ST3_INVALID_PFMS
00006C10  54 32 30 30 30 4C 4D 30 30 37 2D 31 52 38 31 37  T2000LM007-1R817
00006C20  34 53 54 32 30 30 30 4C 4D 30 30 38 2D 31 52 38  4ST2000LM008-1R8
00006C30  47 37 34 53 54 31 35 30 30 4C 4D 30 31 32 2D 31  G74ST1500LM012-1
00006C40  52 38 31 37 47 53 54 31 35 30 30 4C 4D 30 31 32  R817GST1500LM012
00006C50  2D 31 52 38 47 37 47 53 54 31 30 30 30 4C 4D 30  -1R8G7GST1000LM0
00006C60  33 35 2D 31 52 4B 31 37 32 53 54 31 30 30 30 4C  35-1RK172ST1000L
00006C70  4D 30 33 36 2D 31 52 4B 47 37 32 53 54 37 35 30  M036-1RKG72ST750
00006C80  4C 4D 30 33 35 2D 31 52 4B 31 37 43 53 54 37 35  LM035-1RK17CST75
00006C90  30 4C 4D 30 33 35 2D 31 52 4B 47 37 43 53 54 35  0LM035-1RKG7CST5
00006CA0  30 30 4C 4D 30 33 30 2D 31 52 4B 31 37 44 00 00  00LM030-1RK17D..
00006CB0  53 42 4D 33 20 20 20 20 46 46 46 46 20 20 20 20  SBM3    FFFF    
00006CC0  53 42 4D 33 20 20 20 20 53 42 4D 33 20 20 20 20  SBM3    SBM3    


000069AC_File_01_unCPRS.7z

compos mentis

unread,
Aug 20, 2026, 1:30:14 PM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
When I search for SBM3 at HDDSurgery's firmware database, I get only 1TB
results.

When I search for ST2000LM007, I don't see any SBM3 firmware.

It seems to me that the ROM comes from an ST1000LM035 with SBM3
firmware, but the adaptives are from the patient. I assume that the PCB
is also the patient's PCB, with patient MCU, which would account for the
signature clash/error.

compos mentis

unread,
Aug 20, 2026, 3:48:02 PM (5 days ago) Aug 20
to datarecovery...@googlegroups.com
Do you see something like this in terminal (ST4000DM004-2U9104 example)?


SEA5 Boot ROM 1.0 (06/01/2017)

Copyright Seagate 2017-VM000

SBP3: Init HRK Failed 0x0107          <----- HRK = hardware root key

SBP3: Init HRK Failed: 0x010

pbzcbf...@gmail.com

unread,
Aug 20, 2026, 4:06:46 PM (5 days ago) Aug 20
to DataRecoveryCertification

Seagate 2TB Mobile ST2000LM007 PN:1R8174-570 FW:EB01 Site:TK FW:EB01 DOM:15NOV2022 PCB:100835923 REVB

Flash boot code Digital Signature Verification failure!
0x00000040
0x00020000
0x00000001
0x00000001
0x00000001

Flash boot code Digital Signature Verification failure!
0x00000020
0x00000020
0x00000020
0x00000020
0x00000020

SEA5 Boot ROM 1.0 (06/01/2017)
Copyright Seagate 2017-VM000

Abdur Rahim Sopon

unread,
Aug 21, 2026, 7:22:24 AM (4 days ago) Aug 21
to datarecovery...@googlegroups.com
But HDD sticker show information FW SDM2













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

--
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.

compos mentis

unread,
Aug 21, 2026, 8:57:11 AM (4 days ago) Aug 21
to datarecovery...@googlegroups.com
The ROM is from a 1TB donor, but the adaptives are from the 2TB patient.
That's the only thing that makes sense to me.

I would ask the other shop for the original ROM. Also ask them why the
CAP is empty.

If they don't comply, then you will need to buy a 2TB donor PCB with
SDM2 firmware that is compatible with the SA, and then transfer your
adaptives into the donor ROM.


Abdur Rahim Sopon

unread,
Aug 21, 2026, 9:10:07 AM (4 days ago) Aug 21
to datarecovery...@googlegroups.com
I asked; they said they read this backup under this condition which is lying i am sure of.
But somehow they messed up the original ROM, or they don't want to send me the untouched main ROM.

I have the same donor firmware and HDD













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

--
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.

pbzcbf...@gmail.com

unread,
Aug 21, 2026, 9:23:41 AM (4 days ago) Aug 21
to DataRecoveryCertification
Please upload the 2TB SDM2 donor ROM and I'll patch it for you.

Abdur Rahim Sopon

unread,
Aug 22, 2026, 9:22:28 AM (3 days ago) Aug 22
to datarecovery...@googlegroups.com
Donor ROM













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685



--
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.
SDM2 ROM-WDZ3W7W1-2009211505.bin
Message has been deleted

Abdur Rahim Sopon

unread,
Aug 22, 2026, 9:38:36 AM (3 days ago) Aug 22
to datarecovery...@googlegroups.com
I read and verified both. 
The second time, I did the same as you suggested: remove the device, reconnect, and read again, comparing it with the first one; the result was the same.













Best Regards

Abdur rahim sopon

Founder of Data Recovery BD™

WP/call:+8801912881685




Virus-free.www.avast.com

On Sat, Aug 22, 2026 at 7:23 PM compos mentis <pbzcbf...@gmail.com> wrote:
Your latest dump looks good. If you dump it again, and compare the two
latest dumps without error, then it should be OK. That's what I used to
do every time I dumped any memory device. I don't understand why people
don't do this.


--
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.

compos mentis

unread,
Aug 22, 2026, 9:39:48 AM (3 days ago) Aug 22
to datarecovery...@googlegroups.com
Donor ROM with Patient's RAP and SAP. This patched  ROM must be written
to the same donor PCB that was mated to the unpatched ROM.


On 22-Aug-26 11:22 PM, Abdur Rahim Sopon wrote:
> Donor ROM
>
>
SDM2 ROM-WDZ3W7W1-2009211505_patient_SAP_RAP.7z
Reply all
Reply to author
Forward
Message has been deleted
0 new messages