short points

[bel gharti]

hello  sir  can  anyone tell  me  short  points  for  this  seagate  PCB

[RecuperoDati299]

hello

you leave answers unanswered

so I am not pleased to help you again

regards

Ottieni BlueMail per Android

[RecuperoDati299]

it is one of the two couples highlighted in the attached picture

never had to short one of these boards

maybe it is better that you describe also the issue you are observing

Ottieni BlueMail per Android

Il giorno 19 apr 2026, alle ore 12:16, bel gharti <kbps...@gmail.com> ha scritto:

[bel gharti]

i  am  getting   these   information   in  terminal   its   busy    

Boot 0x0100M
VM0185
CV11    

SpinUp
TCC:001F


Trans
Rst 0x0100M
VM0185
CV11    
SAdd:0x0055DAFB
   NVCScram Saved HB Size:020A
    LD: MD_Alloc:00000078 HB_Alloc:0000 MD_Alloc:80380000 HB_Alloc:8032 FlashRestore MD_Saved:00000078 HB_Saved:00000000 MD_CRC:87A1
    PP: MD_Alloc:0000B400 HB_Alloc:0000 FlashRestore
PVTSize: 00002C00 CompSize: 00001C48 DeCompSize: 00002C00 MD_Saved:00001C48 HB_Saved:00000000 MD_CRC:962E
   WCD: MD_Alloc:00012000 HB_Alloc:02E6 FlashRestore...............................................................................................................................................................................................................................................................................................................................................................................................

 Failed power-on replay: 0x0053^z

--
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/02b5c226-c4c0-49c4-a536-421b5132256d%40gmail.com.

[RecuperoDati299]

1. Always the first step BEFORE powering on the drive (it has been powered on enough already)

- have you checked the heads?

2. if heads actuators are straight and heads sliders are glossy, then you can power it on

- how does it sound the drive after the spin up?

if the recalibration sounds "typical" well, try to get the F3> prompt

if I recall correctly, you can start pressing the Ctrl-z right after the power on until it prompts the string

"Rst 0x0100M"

then sit and wait

infact I don't recall any case for that board that required a pin shorting.

... but yes, it may always arrive a "first time'

Ottieni BlueMail per Android

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CALAci1%3Dk5Zy3oj1L%3DyS49HRgJ4nHjFEwKOvROUMsfMmPg_iHuA%40mail.gmail.com.

[bel gharti]

result

Boot 0x0100M
VM0185
CV11    

SpinUp

TCC:0021

Trans
Rst 0x0100M
VM0185
CV11    

SAdd:0x0055DAFB^z


(1Ah)-Serial Port Not Ready^z


(1Ah)-Serial Port Not Ready^z


(1Ah)-Serial Port Not Ready^z


(1Ah)-Serial Port Not Ready^z


(1Ah)-Serial Port Not Ready^z


(1Ah)-Serial Port Not Ready^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z

   NVCScram Saved HB Size:020A
    LD: MD_Alloc:00000078 HB_Alloc:0000 MD_Alloc:80380000 HB_Alloc:8032 FlashRestore MD_Saved:00000078 HB_Saved:00000000 MD_CRC:87A1
    PP: MD_Alloc:0000B400 HB_Alloc:0000 FlashRestore

PVTSize: 00002C00 CompSize: 00001C^z

48 DeCompSize: 00002C00 MD_Saved:00001C48 HB_Saved:00000000 MD_CRC:962E

   WCD: MD_Alloc:00012000 HB_Alloc:02E6 FlashRestore^z
^z
..........
......................................................................................................
..............................................................................................................................
.........^z
..............................................................................................................
............^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z


 Failed power-on replay: 0x0053^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z
^z

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/6bda1478-b646-495c-a8f8-d3315f54b50e%40gmail.com.

[RecuperoDati299]

obviously you have done the unlocking patch: did you?

Ottieni BlueMail per Android

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CALAci1mdSv9sBRw6h_wR5yReywzoEXCMzZa7apEv3vd1zFn4zw%40mail.gmail.com.

[bel gharti]

yes   i  have  unlock  rom  also   same    problem  i  found

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/7cc884c9-5791-498a-a787-3fac13ce7e71%40gmail.com.

[pbzcbf...@gmail.com]

You have some pending transactions in the NvCache area of the ROM. I believe these are the result of power loss data protection events. You need to initialise the NvCache.

I believe that the "Failed power-on replay" error refers to the firmware's failed attempts to replay the pending transactions.

Can you upload your ROM?

[pbzcbf...@gmail.com]

https://forum.hddguru.com/viewtopic.php?p=313355#p313355

[bel gharti]

here  is  rom

On Mon, Apr 20, 2026 at 7:30 AM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:

https://forum.hddguru.com/viewtopic.php?p=313355#p313355

--
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/1f9021db-0373-4faa-9251-6becb3716babn%40googlegroups.com.

[pbzcbf...@gmail.com]

These are the NvCache regions:

Offset(h) 00   02   04   06   08   0A   0C   0E

00180000  584E 7643 0532 461C C003 F200 0000 0000  XNvC.2F.À.ò.....
00180010  0000 0000 0000 6710 0000 0000 0000 0000  ......g.........
00180020  0000 0000 1800 0000 0A02 0204 5800 0002  ............X...
00180030  9824 0104 B8D8 0101 0000 0000 0000 0000  ˜$..¸Ø..........
00180040  0000 0000 0000 0000 0000 0000 0000 0000  ................
00180050  0000 0000 0000 0000                      ........


Offset(h) 00   02   04   06   08   0A   0C   0E

00180050                      2044 6154 0201 E640           DaT..æ@
00180060  0000 0100 5125 1200 3200 0100 0000 0000  ....Q%..2.......
00180070  0000 0000 0000 0000                      ........


Offset(h) 00   02   04   06   08   0A   0C   0E

00192490                      2044 6154 0401 97B3           DaT..—³
001924A0  0000 FFFF 2E96 6F00 481C 0000 0000 0000  ..ÿÿ.–o.H.......
001924B0  0000 0000 0000 0000 0C52 4C45 002C 0000  .........RLE.,..
001924C0  3C1C 0000                                <...


Offset(h) 00   02   04   06   08   0A   0C   0E

0019D8B0                      2044 6154 0101 ECDD           DaT..ìÝ
0019D8C0  0000 FFFF A187 7A00 7800 0000 0000 0000  ..ÿÿ¡‡z.x.......
0019D8D0  0000 0000 0000 0000 784E 764C 8C00 7A00  ........xNvLŒ.z.
0019D8E0  7A00 0304 0204 6E00 7803 0000 0000 0000  z.....n.x.......
0019D8F0  0000 0000 0000 0000 0000 0000 0404 0C00  ................
0019D900  6000 0000 0000 0000 0000 0000 0000 0000  `...............
0019D910  0000 0000 0000 0000 0000 0000 0000 0000  ................
0019D920  0000 0000 0000 0000 0000 0000 0000 0000  ................
0019D930  0000 0000 0000 0000 0000 0000 0000 0000  ................

0019D940  0000 0000 0000 0000 0000 0000 0000 0000  ................

As I understand it, the simplest solution is to find a working ROM and patch the area from 0x180000 to 0xFFFFFF from donor to patient. Your ROM has massive amounts of data in the first two DaT regions. In a good ROM these areas should be mostly clear, apart from the headers.

PC3000 parses the ROM, but not these areas.

[bel gharti]

hello  sir  can  you  patch  with  this  donor  rom

--
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/1bbb7788-af7f-4757-8e2f-687ec889ca7en%40googlegroups.com.

[pbzcbf...@gmail.com]

You can use a free hex editor:

https://mh-nexus.de/en/hxd/

[pbzcbf...@gmail.com]

I have been analysing the patient and donor NvCache regions. I have confirmed that the checksums and CRCs for the second and third DaT regions are correct for both ROMs. However, I have been unable to verify the CRC in the first DaT region of either ROM by applying the same method. I need to do more work on this.

The Russian blog talked about a corrupt NvCache, so perhaps that's a different scenario. It's too bad that the HDD Guru thread disappeared into PMs, because I think the same solution might apply in the OP's case.