Seagate Archive HDD Failure. No Crash, No Spin, Silent.

[NeedsPractice]

NeedsPractice,
What is the serial number of the disk, does it match this one?
SN....................... : Z84116C0
I looked at all your images, and this is the picture I get:
Segment: RAP
Parsing segment....... RAP
ВНИМАНИЕ! Контрольная сумма сегмента неверна!
ВНИМАНИЕ! Контрольная сумма сегмента по данным неверна!
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: CAP
Parsing segment....... CAP
ВНИМАНИЕ! Контрольная сумма сегмента неверна!
ВНИМАНИЕ! Контрольная сумма сегмента по данным неверна!
End parsing segment... CAP

But then they are still there:
CAP
###
<???>

RAP
###
Format revision.......... : 0x0104
Contents revision........ : 0x71060200
Number Sys Zones......... : 1
Number User Zones........ : 60
Heads count.............. : 12
FW Implementation Key.... : 0x1E

SAP
###
Addr 0................... : 0x0001C000
Addr 1................... : 0x80002400

Fam ID................... : 0x8B, (Lamarr)
Fam Member............... : 0x1
SN....................... : Z84116C0
Servo FW rev code........ : 0xD443
Max head................. : 11
Seek mode................ : A020
Flags.................... : 7A49
Head vendor.............. : default
RRO mode................. : 0005
Heads polarity........... : 00 00 00 00 00 00 00 00 00 00 00 00
Logical head map......... : 00 01 02 03 04 05 06 07 08 09 0A 0B

If the serial number matches, you can try to build a working image.

Yes, that serial number matches my hard drive. What does this mean? Where do I put that data?

I would love to enter that data somewhere and get this drive online and clone this thing. That is what I have been wanting this whole time. The last recovery place told me that they could rip the data off this drive worst case scenario "RAW" and rebuild the file structure. Or best case scenario connect the drive and bypass something and read the drive "as is" with file structure intact and just copying everything to another hard drive.

I thought we might be able to do this together. I don't mind paying for this however, I would have to think about paying over a $1,000 bucks. I just need a minute; but sending my drive out is a whole different story.

Recap:

1-I thought I could swap the bios chip; I failed
2-Sent over to recovery place, they failed
3-Thought we could create a bios that would work (don't mind paying, just need to think about it)
4-Not sure if I want to send my hard drive out
5-Thinking about Professional Recovery Places
6-Starting to get harassed on forums
7-Feel bad, don't want to waste peoples time or be inconsiderate

I really do appreciate everyone's time, but I just thought this looks hopeless and there is no way any of this is going to work. I just need to decide if I am comfortable mailing this drive out to a professional data recovery place, when I just did that with a PCB Board and it was a disaster and they ruined my bios. Imagine if they had my whole hard drive?

Please do not feel that I am not grateful. I am.

[NeedsPractice]

Looks like I would need PC-3000. Don't have that. Like I said I'm not sure if I want to send this hard drive out at this time. I would need time to think about that.

https://www.data-medics.com/forum/rap-c ... t2074.html

[pepe]

you would not be any further with pc3k at this point.
Tomset, check the image carefully and you will see that a whole bunch of critical data is missing. Of course, pc3k parses it in some extent, but a large part of RAP is actually missing.

It is impossible to recreate that out of thin air, remotely, the drive is definitely needed.
That post you linked has no relation to your problem, head adaptives are frankly not the critical ones.

pepe

[NeedsPractice]

you would not be any further with pc3k at this point.
Tomset, check the image carefully and you will see that a whole bunch of critical data is missing. Of course, pc3k parses it in some extent, but a large part of RAP is actually missing.

It is impossible to recreate that out of thin air, remotely, the drive is definitely needed.
That post you linked has no relation to your problem, head adaptives are frankly not the critical ones.

pepe

Well I know this sounds insane, but if I could buy a PC3000 and pay you "Pepe" to code the correct information I would need to get this drive online (myself) so that I could clone it I would consider that. (if that is even possible) However, like I stated before I would have to consider if I want to mail this drive out at this time. (if the drive is required in hand in order to possibly code information to bring it to life for a low level recovery) I would have to consider that for another day.

[NeedsPractice]

Update:

I have a designated socket reader, I am going to take the bios of the pcb board and hook it up directly to the reader and see if I can get a reading/dump. Maybe the soldering is in the way. I will be careful.

[NeedsPractice]

you would not be any further with pc3k at this point.
Tomset, check the image carefully and you will see that a whole bunch of critical data is missing. Of course, pc3k parses it in some extent, but a large part of RAP is actually missing.

It is impossible to recreate that out of thin air, remotely, the drive is definitely needed.
That post you linked has no relation to your problem, head adaptives are frankly not the critical ones.

pepe

I think I am going to cry I might have the original bios information in its entirety. Check out these three dumps. I took the bios off the random pcb donor board and inserted directly into the socket reader. (we now have more data).

https://ufile.io/1iy3tz4k

https://ufile.io/jmcr7qql

https://ufile.io/99pry2ej

I flashed this rom to a random pcb board and the hard drive is still doing the same thing. However, this is good news right? I think you may have everything now! Does something need to be adjusted in the BIOS?

[Lardman]

Code:

WARNING!
ROM image contains crytical damaged objects
[SAP]



Parsing container segment....... Flash ROM image
WARNING! Segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: FLASH_PAD
Parsing segment....... FLASH_PAD
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
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
WARNING! Segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: FLASH_PAD
Parsing segment....... FLASH_PAD
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Access violation at address 069F92D8 in module 'PCSEAG~2.DLL'. Read of address 7FE55000

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

QNR Revisions:
Flash ROM image.......... : 1


CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0x8B (Lamarr)
Fam Member............... : 0x1
Head count............... : 12
Date..................... : 19 Apr 2017
SN....................... : Z84116C0
PCB SN................... : 0000C7374LYT
PCB PN................... :  100769666
WWN...................... : 5000C500A30EB2CD
MDL1..................... : ST8000AS0002-1NA17Z                     
MDL2..................... : ST8000AS0002                           
Capacity................. : 15628053168

RAP
###
Format revision.......... : 0x0104
Contents revision........ : 0x71060200
Number Sys Zones......... : 1
Number User Zones........ : 60
Heads count.............. : 12
FW Implementation Key.... : 0x1E

SAP
###
Addr 0................... : 0x0001C000
Addr 1................... : 0x80002400

Fam ID................... : 0x8B, (Lamarr)
Fam Member............... : 0x1
SN....................... : Z84116C0
Servo FW rev code........ : 0xD443
Max head................. : 11
Seek mode................ : A020
Flags.................... : 7A49
Head vendor.............. : default
RRO mode................. : 0005
Heads polarity........... : 00 00 00 00 00 00 00 00 00 00 00 00
Logical head map......... : 00 01 02 03 04 05 06 07 08 09 0A 0B

IAP
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFFFFFF
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

IAP 1
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFF6F8C
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

CODE info
#########
Bank 0
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559

Bank 1
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559




[NeedsPractice]

Code:

WARNING!
ROM image contains crytical damaged objects
[SAP]



Parsing container segment....... Flash ROM image
WARNING! Segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: FLASH_PAD
Parsing segment....... FLASH_PAD
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
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
WARNING! Segment header check sum is invalid!
Segment: GLOB_FLASH_DIR
Parsing segment....... GLOB_FLASH_DIR
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_0
Segment: SAP
Parsing segment....... SAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: FLASH_PAD
Parsing segment....... FLASH_PAD
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
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
End parsing container segment... BOOTFW_CONT_1
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: UDS_BFW
Parsing segment....... UDS_BFW
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Access violation at address 069F92D8 in module 'PCSEAG~2.DLL'. Read of address 7FE55000

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

QNR Revisions:
Flash ROM image.......... : 1


CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0x8B (Lamarr)
Fam Member............... : 0x1
Head count............... : 12
Date..................... : 19 Apr 2017
SN....................... : Z84116C0
PCB SN................... : 0000C7374LYT
PCB PN................... :  100769666
WWN...................... : 5000C500A30EB2CD
MDL1..................... : ST8000AS0002-1NA17Z                     
MDL2..................... : ST8000AS0002                           
Capacity................. : 15628053168

RAP
###
Format revision.......... : 0x0104
Contents revision........ : 0x71060200
Number Sys Zones......... : 1
Number User Zones........ : 60
Heads count.............. : 12
FW Implementation Key.... : 0x1E

SAP
###
Addr 0................... : 0x0001C000
Addr 1................... : 0x80002400

Fam ID................... : 0x8B, (Lamarr)
Fam Member............... : 0x1
SN....................... : Z84116C0
Servo FW rev code........ : 0xD443
Max head................. : 11
Seek mode................ : A020
Flags.................... : 7A49
Head vendor.............. : default
RRO mode................. : 0005
Heads polarity........... : 00 00 00 00 00 00 00 00 00 00 00 00
Logical head map......... : 00 01 02 03 04 05 06 07 08 09 0A 0B

IAP
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFFFFFF
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

IAP 1
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFF6F8C
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

CODE info
#########
Bank 0
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559

Bank 1
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559




That doesn't look good. File System? How did the ROM get critical damage objects?

[pepe]

Hello, this one should be working.

pepe

Attachments

20210512_133733_W25Q16DW.zip

(436.3 KiB) Downloaded 315 times

[pepe]

We could have got closer to this if you attached a terminal when i asked...

pepe

[NeedsPractice]

Hello, this one should be working.

pepe

Did you make some changes? you want me to flash that one you uploaded? Or are you saying the one I uploaded should be working?

[NeedsPractice]

We could have got closer to this if you attached a terminal when i asked...

pepe

I don't know how to do this? Do you still need this?

[Lardman]

Did you make some changes? you want me to flash that one you uploaded? Or are you saying the one I uploaded should be working?

Code:

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

QNR Revisions:
Flash ROM image.......... : 1


CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0x8B (Lamarr)
Fam Member............... : 0x1
Head count............... : 12
Date..................... : 19 Apr 2017
SN....................... : Z84116C0
PCB SN................... : 0000C7374LYT
PCB PN................... :  100769666
WWN...................... : 5000C500A30EB2CD
MDL1..................... : ST8000AS0002-1NA17Z                     
MDL2..................... : ST8000AS0002                           
Capacity................. : 15628053168

RAP
###
Format revision.......... : 0x0104
Contents revision........ : 0x71060200
Number Sys Zones......... : 1
Number User Zones........ : 60
Heads count.............. : 12
FW Implementation Key.... : 0x1E

SAP
###
Addr 0................... : 0x0001C000
Addr 1................... : 0x80002400

Fam ID................... : 0x8B, (Lamarr)
Fam Member............... : 0x1
SN....................... : Z84116C0
Servo FW rev code........ : 0xD443
Max head................. : 11
Seek mode................ : A020
Flags.................... : 7A49
Head vendor.............. : default
RRO mode................. : 0005
Heads polarity........... : 00 00 00 00 00 00 00 00 00 00 00 00
Logical head map......... : 00 01 02 03 04 05 06 07 08 09 0A 0B

IAP
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFFFFFF
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

IAP 1
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : FFFF6F8C
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

CODE info
#########
Bank 0
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559

Bank 1
ProdType................. : LAA10D0.ARD5
Controller FW Rev........ : 09221411
Customer Release......... : RT18
Changelist............... : 01105310
Build date / time........ : 22/09/2016 14:11:59
Package Global ID........ : 00391559
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA5N00
Pkg P/N.................. : 100809590
Servo FW................. : D444 / ---- / ---- / ----
Package Version.......... : LAA10D0.ARD5.AA5N00.RT18
Pkg CFW Ver.............. : LAA10D0.ARD5.01105310.00391559



Flash it back to the rom.

[Tomset]

pepe,
I did not make it in time. ))

Attachments

[Lardman]

pepe,

+1

Still a checksum error in pc3k though. A.M.P.G.

[NeedsPractice]

Yes, fzabkar did it! by the time I read this I was already hex editing the difference and programing one of my donor board roms. I can't believe this. This is what I wanted to do so bad, I did not want to send my drive out and here I am copying my files. Truly Amazing.

fzabkar, has been with me the whole way. so patient and so kind. truly amazing person. I do wish to pay him some how for his efforts.

However,

thank you everyone as well:

Pepe
Tomset
Lardman

I do not mind paying some for your efforts if you would like to let me know somehow someway.

[Lardman]

fzabkar, has been with me the whole way. so patient and so kind. truly amazing person. I do wish to pay him some how for his efforts.

Do as he's told you on tomshardware and now make a BACKUP ! He's unlikely to take any beer tokens I'm sure he always appreciates the offers.

It's nice not to be left with DR blueballs for a change.

[NeedsPractice]

fzabkar, has been with me the whole way. so patient and so kind. truly amazing person. I do wish to pay him some how for his efforts.

Do as he's told you on tomshardware and now make a BACKUP ! He's unlikely to take any beer tokens I'm sure he always appreciates the offers.

It's nice not to be left with DR blueballs for a change.

Well please let me know how to repay him somehow someway, this is truly amazing, I am still copying files right now. This means so much to me.

I don't mind giving out bear tokens or whatever, just let me know what I can do and I will try to do it.

Thank you all so very much.

[grevan]

Found your topic on tomshardware. Great job by fzakbar.
Never heard of that Seagate ROM checker software before, always learning.
Cheers

[NeedsPractice]

fzabkar said:
I found the problem. There is a stuck bit at this location:

Code:

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

00025C10 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00
^^

When I change the 8 to a 0, the CRC becomes 0x0000.

F3RomExplorer is happy with the edit. If you can reprogram your ROM after making the change, then hopefully you will recover your data.

I use HxD (freeware hex editor).

https://forums.tomshardware.com/threads ... 6.3699522/

FZABKAR

OH MY GOODNESS! YOU ARE AMAZING! YOU DID IT! PRAISE GOD! YOU ARE A SAINT!

2.82 TB - 3,106,287,262,945 BYTES - 748,329 FILES, 57,259 FOLDERS

TAKING (1) DAY TO COPY! IT'S COPYING RIGHT NOW!

YOU HAVE NO IDEA WHAT THIS MEANS TO ME! THIS WAS MY MAIN BACKUP DRIVE THAT I BACKED EVERYTHING UP TO RIGHT BEFORE IT DIED. I WAS MOVING STUFF AROUND AND PICKED THIS DRIVE TO BACKUP STUFF TOO. I WAS GOING TO ORGANIZE EVERYTHING WHEN I PLUGGED IT IN AND ALL OF A SUDDEN IT WAS GONE.

THIS IS INCREDIBLE!