st12000n exos - raid rom

Alandata Recovery

unread,

Dec 17, 2024, 10:00:54 PM12/17/24

to datarecoveryce.

this board has 2 roms 4m each in a raid

i read them in and the pc3k raided them together

i created a rom image with unlock tech mode enabled

now I need to derailed that back into 2 4m images to rite back to the roms

How do I do that?

thanks

--

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

www.alandata.com www.alandataRecovery.com

jol qwerr

unread,

Dec 18, 2024, 4:53:13 AM12/18/24

to datarecovery...@googlegroups.com

Its a simple a RAID 0?

Whats the BS?

Alandata Recovery

unread,

Dec 18, 2024, 11:54:11 AM12/18/24

to datarecovery...@googlegroups.com

There are 2 4m ROM

BS is b000

PC3k detects raid

And assemble into 8m stripe

Serial port is locked

So must use ROM reader

Used PC3k to patch for tech mode unlock enable.

But now need to rewrite the roms

Need to take 8m and reraid to 2 4m

Need a program that takes ROM image

And bs

And outputs 2 files

These chips are tiny

Had to buy an adapter to read them

On Wed, Dec 18, 2024, 1:53 AM jol qwerr <qjol...@gmail.com> wrote:

Its a simple a RAID 0?
Whats the BS?

--
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/CAKfZW8WTVMPq3W81BL9zsS4_KynPgM-nDkq6uOqGADcC0u-OUg%40mail.gmail.com.

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 12:49:39 PM12/18/24

to DataRecoveryCertification

This makes no sense. If PC3K assembles the RAID, then it should also disassemble it. Otherwise, a component programmer should be able to do it. However, nobody can help you if we can't see the dumps of each ROM and PC3K's RAID-ed version.

Alandata Recovery

unread,

Dec 18, 2024, 1:07:36 PM12/18/24

to datarecovery...@googlegroups.com

ok

UFS did it

Open the rom as disk image

then use decompose reverse raid tool

set custom stripe size in sectors = 1408

1408 ? .... weird....

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 1:17:05 PM12/18/24

to DataRecoveryCertification

This still seems odd. Assuming "4m" means 4 megabytes (32 Mbits), then that results in a non-integral number of stripes.

4 x 1024 x 1024 / 1408 = 2978.909

Alandata Recovery

unread,

Dec 18, 2024, 1:19:54 PM12/18/24

to datarecovery...@googlegroups.com

pc3k assembles

but I dont see reraid option

I think they expect you to write rom through serial port

but you cant...

maybe after I get techmode patch roms installed.....

here is edge chip strat

mid chip strt

pc3k has raid rom feature

loads this

rom info

=====================

Selected family......................... : C8, EvansBP
Model by ID............................. : <HDD ID NOT READ>

Loading default settings!
Use the options dialog to review and save utility settings.
Then press OK!

Family default settings loading!

Tech Key...
Operation aborted
WARNING! ROM RAID IS DETECTED! StripeSize = 0xB0000
WARNING! ROM RAID IS DETECTED! StripeSize = 0xB0000
WARNING! ROM RAID IS DETECTED! StripeSize = 0xB0000

Multipart flash image found. Reparsing...

Saving ROM to profile folder
File : C:\Program Files\ACE Lab\PC-3000\Bin\!Profiles\SgF3\CimarronBP\st12000n_BELN_exos\Data\ROM\ROM_ZRT1BELN_82E87C8D.bin
Parsing container segment....... Flash ROM image
Damaged container signature!
WARNING! QNR segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
WARNING! Segment whole space check sum is invalid!
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_0
Parsing container segment....... BOOTFW_CONT_0
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
FF filled section descriptor!
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
FF filled section descriptor!
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
FF filled section descriptor!
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SFW
End parsing container segment... BOOTFW_CONT_0
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_1
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
WARNING! Segment used space check sum is invalid!
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
End parsing container segment... BOOTFW_CONT_1
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
Segment: SAP
Parsing segment....... SAP
Parsing packed segment SAP
End parsing packed segment... SAP
End parsing segment... SAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
End parsing segment... UDS_BFW
End parsing container segment... Flash ROM image

Multipart flash image found. Reparsing...

Parsing multipart flash image....... Flash ROM image

Part 1...

Parsing container segment....... Flash ROM part 1
Damaged container signature!
WARNING! QNR segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
WARNING! Segment whole space check sum is invalid!
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_0
Parsing container segment....... BOOTFW_CONT_0
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
FF filled section descriptor!
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
FF filled section descriptor!
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
FF filled section descriptor!
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SFW
End parsing container segment... BOOTFW_CONT_0
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
End parsing segment... GLOB_FLASH_DIR
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_1
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
WARNING! Segment used space check sum is invalid!
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
End parsing container segment... BOOTFW_CONT_1
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
Segment: SAP
Parsing segment....... SAP
Parsing packed segment SAP
End parsing packed segment... SAP
End parsing segment... SAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
End parsing segment... UDS_BFW
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Empty container!
End parsing container segment... Flash ROM part 2

Part 3...

Parsing container segment....... Flash ROM part 3
Empty container!
End parsing container segment... Flash ROM part 3

Part 4...

Parsing container segment....... Flash ROM part 4
Empty container!
End parsing container segment... Flash ROM part 4

FLASH ROM bank: 0...
FLASH ROM Info
==============
Image size............... : 2097152

QNR Revisions:
Flash ROM part 1......... : 23
GLOB_FLASH_DIR........... : 23
BOOTFW_CONT_0............ : 0
GLOB_FLASH_DIR........... : 24
BOOTFW_CONT_1............ : 0

CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0xC8 (EvansBP)
Fam Member............... : 0x16
Head count............... : 12
Date..................... : 03 Feb 2024
SN....................... : ZRT1BELN
PCB SN................... : 0000R426D17R
PCB PN................... : 205807700
WWN...................... : 5000C500E861E13B
MDL1..................... : ST12000NM000J-2TY103
MDL2..................... : ST12000NM000J
Capacity................. : 23437770752

RAP
###
Format revision.......... : 0x5A4C
Contents revision........ : 0x4D41C8CF
Number Sys Zones......... : 0
Number User Zones........ : 0
Heads count.............. : 243
FW Implementation Key.... : 0x18

SAP
###
Addr 0................... : 0x00028300
Addr 1................... : 0x80000000
Addr 2................... : 0x44167C00
Addr 3................... : 0x0002E400

Fam ID................... : 0xC8 (EvansBP)
Fam Member............... : 0x9
SN....................... : ZRT1BELN
Servo FW rev code........ : 0xDD76
Max head................. : 11
Seek mode................ : 2280
Flags.................... : 0B49
Head vendor.............. : default
RRO mode................. : 0001
Heads polarity........... : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Logical head map......... : 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 11 11 11

IAP 1
###
ID, code................................ : 0x0C5E (PUIS ID data)
ID, Model............................... : ST12000NM000J-2TY103
ID, SN.................................. : ZRT1BELN
ID, WWN................................. : 5000C500E861E13B
ID, FW.................................. : SN04
PUIS.................................... : OFF
Active config........................... : B64DC680
Active config (M11 like)................ : FE8FB64D
NAND ROM cache flag, Kahuna like........ : 32AAC82E
NAND ROM cache flag, Rosewood like...... : A012F3BC

CODE tags
#########
Tag 1
Fam code................. : C8
Compat_Fam............... : 1F
Compat_Flag.............. : 21
Compat_Vrnt.............. : 10
HWCfg.................... : 0002
FactoryFlags............. : F1
CustFlags................ : 0C
Dld flg.................. : 04
SA Comp Flags............ : 03
Build date / time........ : 8/22/2022 2:57:00 PM

CODE info
#########
<???>

FLASH ROM bank: 1...
Servo-Symbol table is not found!
FLASH ROM Info
==============
Image size............... : 2097152

CAP
###
<???>

RAP
###
<???>

SAP
###
<???>

CODE tags
#########
<???>

CODE info
#########
<???>

FLASH ROM bank: 2...
Servo-Symbol table is not found!
FLASH ROM Info
==============
Image size............... : 2097152

CAP
###
<???>

RAP
###
<???>

SAP
###
<???>

CODE tags
#########
<???>

CODE info
#########
<???>

FLASH ROM bank: 3...
Servo-Symbol table is not found!
FLASH ROM Info
==============
Image size............... : 2097152

CAP
###
<???>

RAP
###
<???>

SAP
###
<???>

CODE tags
#########
<???>

CODE info
#########
<???>

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 1:59:49 PM12/18/24

to DataRecoveryCertification

It would help if you were to upload the .bins, but from your limited information it appears that the total size of the ROM code + adaptives is 0x160000 bytes.

number of stripes = capacity / stripe size = 0x160000 / (1408 x 0x200) = 2

It would appear that the first 0xB0000 bytes of each ROM are combined, but the rest may not RAID-ed. This means that you risk corruption if you allow UFS Explorer to unRaid the ROM image.

Did you compare the unRAIDed ROMs against their individual dumps?

t...@desertdatarecovery.com

unread,

Dec 18, 2024, 2:09:26 PM12/18/24

to datarecovery...@googlegroups.com

While I have not done one yet, here is the description from someone who has.

Read both chips, import both images into PC3K latest version and combine as RAID, patch combined ROM and then export as separate ROMs again. Then write back to chips and solder back to PCB.

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

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

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/903cc5ab-cba2-4ce7-aeaa-f01edb95ba76n%40googlegroups.com.

Alandata Recovery

unread,

Dec 18, 2024, 2:34:37 PM12/18/24

to datarecovery...@googlegroups.com

thanks tim

found it

its a new option in the write module - duh...

the ufs method didnt work....

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/00bf01db5180%24580ad410%2408207c30%24%40desertdatarecovery.com.

ROM_ZRT1BELN_82E87C8D_RAID_Part_0_tech_patch.txt

ROM_ZRT1BELN_82E87C8D_RAID_Part_1_tech_patch.txt

Alandata Recovery

unread,

Dec 18, 2024, 2:44:01 PM12/18/24

to datarecovery...@googlegroups.com

Thanks tim

found it

its a new option in the write module - duh...

the ufs method didnt work....

Only the first rom was altered

the first rom is the one closest to the edge not the middle

the second is the same as OG

On Wed, Dec 18, 2024 at 11:09 AM tim via DataRecoveryCertification <datarecovery...@googlegroups.com> wrote:

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/00bf01db5180%24580ad410%2408207c30%24%40desertdatarecovery.com.

wayne horner

unread,

Dec 18, 2024, 3:09:47 PM12/18/24

to datarecovery...@googlegroups.com

heres a google share

https://drive.google.com/drive/folders/1weXtRoQXnN3b_SlIFpwbZfgWJF8ia7uf?usp=sharing

Alandata Data Recovery - (949)287-3282

"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com www.AlanDataRecovery.com

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWT3dOnXW6OcDQiW3LRmY6xtC0n6zR7wGUZy2QYMoJsfxQ%40mail.gmail.com.

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 4:30:10 PM12/18/24

to DataRecoveryCertification

The area at offset 0x160000 appears to be a non-volatile cache for power loss data protection. It appears to be RAID-ed as a striped array with a stripe size of 0x100 bytes.

These are the "DaT" sections:

Offset(h) 00 04 08 0C

00160000 606E7643 A5CA28EA 33002A00 00000000 `nvC¥Ê(ê3.*..... nvC = nonvolatile cache
00160010 00000000 0000303F 00000000 00000000 ......0?........
00160020 00000000 11000000 0A020305 00000000 ................
00160030 60000002 80000403 A0040404 C0F40405 `...€... ...Àô..
00160040 E0440501 80000104 00000000 00000000 àD..€...........
00160050 00000000 00000000 00000000 00000000 ................
00160060 20446154 020961DD 00001800 C3800100 DaT..aÝ....Ã€..
00160070 40000000 00000000 00000000 00000000 @...............
00160080 646A9F3C 03000100 40000000 00000000 djŸ<....@.......
00160090 00000000 0000FFFF 10000000 00000000 ......ÿÿ........
001600A0 EEEEEEEE 00000000 10000000 10000100 îîîî............
001600B0 3153434D 00000000 00000000 00000000 1SCM............

Offset(h) 00 04 08 0C

001A0080 20446154 03018740 00000000 93240200 DaT..‡@....“$..
001A0090 60010000 00000000 00000000 00000000 `...............
001A00A0 00000000 00000000 00000000 00000000 ................
001A00B0 FFFFFFFF FFFFFFFF 00000000 00000000 ÿÿÿÿÿÿÿÿ........
001A00C0 00000000 00000000 00000000 00000000 ................
........
001A01F0 00000000 00000000 00000000 00000000 ................

Offset(h) 00 04 08 0C

001A04A0 20446154 040108DA 0000FFFF DD731700 DaT...Ú..ÿÿÝs..
001A04B0 80180000 00000000 00000000 00000000 €...............
001A04C0 0C524C45 C42A0C00 74180000 FFFFFFFF .RLEÄ*..t...ÿÿÿÿ

Offset(h) 00 04 08 0C

001AF4C0 20446154 05018A52 0000FFFF 84D01D00 DaT..ŠR..ÿÿ„Ð..
001AF4D0 50430000 00000000 00000000 00000000 PC..............
001AF4E0 02FFFFFF 18000000 00000000 00000000 .ÿÿÿ............
001AF4F0 00000000 00000000 00000000 00000000 ................
001AF500 04FFFFFF 00020000 0A00010F 004E432F .ÿÿÿ.........NC/
001AF510 8EBE0300 00000303 005E5D00 00000000 Ž¾.......^].....
001AF520 00000432 0064642E 00000000 00000533 ...2.dd........3
001AF530 00646400 00000000 0000070F 00413CBD .dd..........A<½
001AF540 882E0000 00000932 0064643D 00000000 ˆ......2.dd=....
001AF550 00000A13 00646400 00000000 00000C32 .....dd........2
001AF560 0064641D 00000000 0000120B 00646400 .dd..........dd.
001AF570 00000000 0000B832 00646400 00000000 ......¸2.dd.....
001AF580 0000BB32 00646400 00000000 0000BC32 ..»2.dd.......¼2
<lots more data>
001B37D0 00000000 00000000 07FFFFFF 18000000 .........ÿÿÿ....
001B37E0 5F06CDAB 01000000 9B5137FC 01000000 _.Í«....›Q7ü....
001B37F0 00000000 00000000 0BFFFFFF 18000000 .........ÿÿÿ....
001B3800 B4021900 00000000 BC021C00 00000000 ´.......¼.......
001B3810 DA022800 00000000 0CFFFFFF 04000000 Ú.(......ÿÿÿ....
001B3820 00000000 FFFFFFFF FFFFFFFF FFFFFFFF ....ÿÿÿÿÿÿÿÿÿÿÿÿ

Offset(h) 00 04 08 0C

001B44E0 20446154 0101E6DF 0000FFFF 1A85EF00 DaT..æß..ÿÿ.…ï.
001B44F0 90000000 00000000 00000000 00000000 ................
001B4500 904E764C 00000000 30003000 03050000 .NvL....0.0.....
001B4510 02040A00 03000000 00000000 00000000 ................
001B4520 00000000 00000000 03040A00 00000000 ................
001B4530 00000000 00000000 00000000 00000000 ................
001B4540 04040401 27000000 00000000 00000000 ....'...........
001B4550 00000000 00000000 0504C800 B9000000 ..........È.¹...
001B4560 00000000 00000000 00000000 00000000 ................
001B4570 00000000 00000000 00000000 00000000 ................
001B4580 00000000 00000000 00000000 00000000 ................
001B4590 FFFFFFFF FFFFFFFF FFFFFFFF F0002201 ÿÿÿÿÿÿÿÿÿÿÿÿð.".
001B45A0 54018601 B801EA01 1C024E02 8002B202 T.†.¸.ê...N.€.².
001B45B0 E4021603 48037A03 AC03DE03 10044204 ä...H.z.¬.Þ...B.
001B45C0 7404A604 D8040A05 3C056E05 A005D205 t.¦.Ø...<.n. .Ò.
001B45D0 04063606 68069A06 CC06FE06 30076207 ..6.h.š.Ì.þ.0.b.
001B45E0 9407C607 F8072A08 5C088E08 C008F208 ”.Æ.ø.*.\.Ž.À.ò.
001B45F0 24095609 8809BA09 EC091E0A 500A820A $.V.ˆ.º.ì...P.‚.
001B4600 B40AE60A 180B4A0B 7C0BAE0B E00B120C ´.æ...J.|.®.à...
001B4610 440C760C A80CDA0C 0C0D3E0D 700DA20D D.v.¨.Ú...>.p.¢.
001B4620 D40D060E 380E6A0E FFFFFFFF FFFFFFFF Ô...8.j.ÿÿÿÿÿÿÿÿ

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 4:39:39 PM12/18/24

to DataRecoveryCertification

Example of 0x100-byte stripes in the large DaT section:

full ROM

Offset(h) 00 04 08 0C

001AF600 00000000 0000C823 00646400 00000000 ......È#.dd.....
001AF610 0000F000 00646422 000000EE ED2EF100 ..ð..dd"...îí.ñ.
001AF620 0064FD3B B2FAF400 0000F200 0064FD5B .dý;²úô...ò..dý[
001AF630 F6290600 00000000 00000000 00000000 ö)..............
001AF640 00000000 00000000 00000000 00000000 ................
001AF650 00000000 00000000 00000000 00000000 ................
001AF660 00000000 00000000 00000000 00000000 ................
001AF670 00008200 3702007B 03000100 01FF020D ..‚.7..{.....ÿ..
001AF680 04000000 00000000 00000500 4FA10000 ............O¡..
001AF690 03030303 03030303 03000000 00000000 ................
001AF6A0 00010000 00000000 00000000 A7000000 ............§...
001AF6B0 7D26B6E7 33000000 00000000 01001A00 }&¶ç3...........
001AF6C0 3BB2FAF4 00000000 9A972A06 00000000 ;²úô....š—*.....
001AF6D0 00000000 00000000 01000100 00000000 ................
001AF6E0 8E080000 01000000 00000000 00000000 Ž...............
001AF6F0 03000000 00000302 00000000 00000000 ................

001AF700 00001419 00000044 05000000 C8400000 .......D....È@..
001AF710 4E4C4D54 02032000 80010000 00000000 NLMT.. .€.......
001AF720 40010000 88010000 60010000 90210000 @...ˆ...`....!..
001AF730 FFFF0000 98310000 80010100 80010000 ÿÿ..˜1..€...€...
001AF740 0000037C 574C4550 30348106 0064003D ...|WLEP04...d.=
001AF750 28022600 01000000 0061FFFF 0000151F (.&......aÿÿ....
001AF760 00000000 062A9772 00000000 F4FAB23B .....*—r....ôú²;
001AF770 00000000 00000000 000004E7 20203033 ...........ç 03
001AF780 00000000 00093DD6 00000000 0042217B ......=Ö.....B!{
001AF790 00000000 00006E01 00000000 0011BEA1 ......n.......¾¡
001AF7A0 00000000 00000000 00000000 00000000 ................
001AF7B0 00000000 00000000 00000000 00000000 ................
001AF7C0 006103FC 811A003D 004EB001 00000002 .a.ü...=.N°.....
001AF7D0 00000000 00000002 00000000 00000000 ................
001AF7E0 00000000 00000000 00180000 00000000 ................
001AF7F0 00000000 00000000 00000000 30340000 ............04..

EDGE ROM

Offset(h) 00 04 08 0C

000D7B00 00000000 0000C823 00646400 00000000 ......È#.dd.....
000D7B10 0000F000 00646422 000000EE ED2EF100 ..ð..dd"...îí.ñ.
000D7B20 0064FD3B B2FAF400 0000F200 0064FD5B .dý;²úô...ò..dý[
000D7B30 F6290600 00000000 00000000 00000000 ö)..............
000D7B40 00000000 00000000 00000000 00000000 ................
000D7B50 00000000 00000000 00000000 00000000 ................
000D7B60 00000000 00000000 00000000 00000000 ................
000D7B70 00008200 3702007B 03000100 01FF020D ..‚.7..{.....ÿ..
000D7B80 04000000 00000000 00000500 4FA10000 ............O¡..
000D7B90 03030303 03030303 03000000 00000000 ................
000D7BA0 00010000 00000000 00000000 A7000000 ............§...
000D7BB0 7D26B6E7 33000000 00000000 01001A00 }&¶ç3...........
000D7BC0 3BB2FAF4 00000000 9A972A06 00000000 ;²úô....š—*.....
000D7BD0 00000000 00000000 01000100 00000000 ................
000D7BE0 8E080000 01000000 00000000 00000000 Ž...............
000D7BF0 03000000 00000302 00000000 00000000 ................
000D7C00 08034600 00000000 00013CEB 1500009B ..F.......<ë...›

MID ROM

Offset(h) 00 04 08 0C

000D7B00 00001419 00000044 05000000 C8400000 .......D....È@..
000D7B10 4E4C4D54 02032000 80010000 00000000 NLMT.. .€.......
000D7B20 40010000 88010000 60010000 90210000 @...ˆ...`....!..
000D7B30 FFFF0000 98310000 80010100 80010000 ÿÿ..˜1..€...€...
000D7B40 0000037C 574C4550 30348106 0064003D ...|WLEP04...d.=
000D7B50 28022600 01000000 0061FFFF 0000151F (.&......aÿÿ....
000D7B60 00000000 062A9772 00000000 F4FAB23B .....*—r....ôú²;
000D7B70 00000000 00000000 000004E7 20203033 ...........ç 03
000D7B80 00000000 00093DD6 00000000 0042217B ......=Ö.....B!{
000D7B90 00000000 00006E01 00000000 0011BEA1 ......n.......¾¡
000D7BA0 00000000 00000000 00000000 00000000 ................
000D7BB0 00000000 00000000 00000000 00000000 ................
000D7BC0 006103FC 811A003D 004EB001 00000002 .a.ü...=.N°.....
000D7BD0 00000000 00000002 00000000 00000000 ................
000D7BE0 00000000 00000000 00180000 00000000 ................
000D7BF0 00000000 00000000 00000000 30340000 ............04..

Alandata Recovery

unread,

Dec 18, 2024, 5:08:49 PM12/18/24

to datarecovery...@googlegroups.com

interesting

ufs only reraids in sectors

it cant do 0x100

ace lists stripe size as b0000

so is there another stripe going on ... inside ?

--

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/58c7a8c1-2475-4bdf-86ac-3e24676e3694n%40googlegroups.com.

pbzcbf...@gmail.com

unread,

Dec 18, 2024, 5:14:42 PM12/18/24

to DataRecoveryCertification

Yes, there are two RAIDs. The code/adaptive section consists of two 0xB000-byte stripes, whereas the NVCache consists of 0x100-byte stripes. That's half a sector per stripe, ie each sector is striped across both ROMs. That makes sense since that would be the fastest way to save the contents of DRAM to NVC during a power loss event.

Alandata Recovery

unread,

Dec 19, 2024, 9:51:17 PM12/19/24

to datarecovery...@googlegroups.com

wrote the patched rom back to the drive and it unlocks.

Gets ID, but it got that with the bare board.

comes ready

read resources

Model : ST12000NM000J-2TY103
Serial : ZRT1BELN
Firmware : SN04
Capacity : 12 TB (23 437 770 752)

heres a interesting startup message - it shows pressure measurement

========

Boot0x0100MEPSN04SN04
Trans
Tech Unlock Handshake: 0x5F0A5F46
Reply:
Rst0x0100MEPSN04SN04
TCC:001D

Pressure: 703mBars

PartialPressure: 684.37mBars

SmoothedPartialPressure: 0.00mBars

(P)SATAReset

TCC:001DPressure:703mBarsPartialPressure:684.37mBarsSmoothedPartialPressure:N/A

========

ANybody know if these readings are good?

0 mbars seems not good

Heres the ^L

====================

LPower=
HPower
TCC:001A Pressure:696 mBars PartialPressure:684.36 mBars SmoothedPartialPressure: 685.67 mBars Req=0038 Status=0001ACTIVE
F3 T>
EvansBP CMR mDRAM BP08 SATA.JanusMC.R1.2.SBP3
Product FamilyId: C8, MemberId: 16, VendorID: SEAGATE
HDA SN: ZRT1BELN, RPM: 7202, Wedges: 1A0, Heads: C, OrigHeads: 12, ActiveHdMap: 0FFF, Lbas: 0000AEB80000, PreampType: 83 30
Bits/Symbol: C, Symbols/UserSector: CC9, Symbols/SystemSector: CC8 HostBlocks: 0x8, HostSectorSize: 0x200, SystemSectorSize: 0x1000
PCBA SN: 0000R426D17R, Controller: JANUS_MC_R1_1_2_SATA(3112), Channel: Unknown, PowerAsic: Unknown Rev 00, BufferBytes: 10000000
SF ID: EF 60, SF Part Size: 1000, Flash Used: 580
Package Version: EPAEA18BD.SDN1.EPSN04.SN04 , Package P/N: 204522700, Package Global ID: 00489010,
Package Build Date: 08/22/2022, Package Build Time: 15:00:15, Package CFW Version: EPAEA18BD.SDN1.EPSN04.02531708.00489010.SN04 ,
Package SFW1 Version: BD57, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----, Package SFW5 Version: ----, Package SFW6 Version: ----
Controller FW Rev: 08221500, CustomerRel: SN04, Changelist: 02531708, ProdType: EPAEA18.SDN1QC, Date: 08/22/2022, Time: 150015, UserId: 00489010
Servo FW Rev: BD57
Parallelism Identity: Single
TCG IV Version: a4.00
Package BPN: 84
RAP FW Implementation Key: 25, Format Rev: 0005, Contents Rev: 49 09 20 00
Active BFW Container: 1
4K Sys Area: 1
TOTAL TTR = 00007087
Features:
- IOEDC enabled
- IOECC enabled
- DERP enabled v. 7.00.0000000000000000
- LTTC-UDR2 compiled off
- SuperParity 2.5 enabled
- Humidity Sensor disabled
- Media Cache Partition enabled
- Torn Write Protection enabled
- SweepSeek 2.0
- SubRelease:0
- Critical Event Log v. 1
- FAFH 44.0 enabled
- EWP:1
- DRAM Mirror:1
- MiniZones Serpentine Media Layout
- HAMR Features 00
- FwSRN:0002 SfwSRN:0002 CID:01
ASCII Diag mode

F3 T>/7

F3 7>X

Factory x10 Head 00 ReaderA Res 0FB9 ReaderB Res 0F23
Factory x10 Head 01 ReaderA Res 0EB8 ReaderB Res 0D3D
Factory x10 Head 02 ReaderA Res 109A ReaderB Res 1131
Factory x10 Head 03 ReaderA Res 0E3D ReaderB Res 0BB8
Factory x10 Head 04 ReaderA Res 11BF ReaderB Res 1451
Factory x10 Head 05 ReaderA Res 102E ReaderB Res 157C
Factory x10 Head 06 ReaderA Res 0EC3 ReaderB Res 13DC
Factory x10 Head 07 ReaderA Res 0F63 ReaderB Res 0E2C
Factory x10 Head 08 ReaderA Res 12CA ReaderB Res 157D
Factory x10 Head 09 ReaderA Res 0E84 ReaderB Res 0FD5
Factory x10 Head 0A ReaderA Res 15E5 ReaderB Res 127F
Factory x10 Head 0B ReaderA Res 0FD2 ReaderB Res 10B0
Current Head 00 ReaderA Res 018F ReaderB Res 0180
Current Head 01 ReaderA Res 0175 ReaderB Res 0150
Current Head 02 ReaderA Res 01A8 ReaderB Res 01B5
Current Head 03 ReaderA Res 0168 ReaderB Res 0128
Current Head 04 ReaderA Res 01CB ReaderB Res 0208
Current Head 05 ReaderA Res 019C ReaderB Res 021D
Current Head 06 ReaderA Res 0175 ReaderB Res 0205
Current Head 07 ReaderA Res 018A ReaderB Res 0166
Current Head 08 ReaderA Res 01DE ReaderB Res 0223
Current Head 09 ReaderA Res 0170 ReaderB Res 0194
Current Head 0A ReaderA Res 022A ReaderB Res 01DA
Current Head 0B ReaderA Res 018B ReaderB Res 01A4

F3 7>

================================

cant read data

and it gets led-bd

when i try to print plist

--
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/2b76c55e-6b34-4bfc-a10c-2bdd088ff42an%40googlegroups.com.

Alandata Recovery

unread,

Dec 19, 2024, 10:22:56 PM12/19/24

to datarecovery...@googlegroups.com

look at this head map

pbzcbf...@gmail.com

unread,

Dec 19, 2024, 10:27:22 PM12/19/24

to DataRecoveryCertification

https://www.data-medics.com/forum/threads/seagate-exos-x16-st16000nm001g.3647/

TCC:0014 Humidity:0.0% Pressure:683 mBars PartialPressure:684.32 mBars EMCDataErr:00000000 Req=0038 Status=0001ACTIVE
F3 T>
Diagnostic Port Locked

pbzcbf...@gmail.com

unread,

Dec 19, 2024, 10:29:37 PM12/19/24

to DataRecoveryCertification

HDA SN: ZRT1BELN, RPM: 7202, Wedges: 1A0, Heads: C, OrigHeads: 12, ActiveHdMap: 0FFF

Alandata Recovery

unread,

Dec 20, 2024, 1:40:14 PM12/20/24

to datarecovery...@googlegroups.com

ace dialed in and this is what they could do

I tried to write he rom and I got bootcode locked message

Hello Wayne,

Looks like an issue with Head 11, it is not reading anywhere, as a result Heads can't pass internal Heads test for proer reading in common UDMA mode,
The rest Heads are able to read thru an Active utiltiy and looks like Translation is correct, files working properly.
I've launched the process of sectors map building process for user files/folders.
After that be possible to start the reading process of those sectors.
Reading is not very fast thru an Active utility, but stable. Unfortuantely now we haven't solution for to be able to read in common UDMA mode... issue is know but solution is under researching.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/71c799a8-e2d0-4307-aa51-245c13c8173cn%40googlegroups.com.

Data Recovery Guru

unread,

Dec 20, 2024, 1:44:47 PM12/20/24

to datarecovery...@googlegroups.com

Thanks.

What programmer socket adapter did you use to read the ROMs, please? Have a link?

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWT%2Bi_uGdrqcTTtY10zD2-nyCRi5wpBee9ZvBvqzd15wEg%40mail.gmail.com.

Alandata Recovery

unread,

Dec 20, 2024, 2:40:21 PM12/20/24

to datarecovery...@googlegroups.com

worked great

https://xgecu.myshopify.com/products/xgecu-qfn8-wson8-uson8-dfn8-2x3-4x3-or-4x4-ic-socket-universal-adapter-for-spi-nand-nor-flash-with-high-end-spring-probe?variant=43868745171123

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAHoXmqnoE3a2LWS4rwZsvQG5NZG-XACRHGx%2BpuV0gkQZDUxXvQ%40mail.gmail.com.

Data Recovery Guru

unread,

Dec 20, 2024, 2:40:54 PM12/20/24

to datarecovery...@googlegroups.com

Much appreciated.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWRS2nKkC9Nb_VaxVQuDpteUHiYN4eQvaFm3h1U_%2Bummkg%40mail.gmail.com.

Alandata Recovery

unread,

Dec 20, 2024, 2:59:36 PM12/20/24

to datarecovery...@googlegroups.com

only the edge-most chip was needed for the techmode patch.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAHoXmq%3D_m%3DAJwcnm27kES0foCyDKdaPx0naFaJCY3Pxb0X_%2BWw%40mail.gmail.com.

pbzcbf...@gmail.com

unread,

Dec 25, 2024, 5:09:12 PM12/25/24

to DataRecoveryCertification

Doesn't PC3000 complain if the second half of the RAID-ed ROM code/adaptives section is missing? If so, could you just fill everything past offset 0xB0000 with zeros, or could you paste the contents from a donor ROM?

pbzcbf...@gmail.com

unread,

Dec 28, 2024, 2:46:52 AM12/28/24

to DataRecoveryCertification

DFL now have a special pogo-pin PCB for reading these ROMs:

https://www.youtube.com/watch?v=v5EzsTehIvs

Alandata Recovery

unread,

Dec 28, 2024, 11:42:11 AM12/28/24

to datarecovery...@googlegroups.com

The dfl device is a pogo pin reader that bolts to the specific seagate board.

Seagate changes the board designs frequently so a bummer about this is that it's probably not going to work with very many models.

--

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/be4a9450-48a3-4509-afcd-571580f5b6c0n%40googlegroups.com.

Reply all

Reply to author

Forward