All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 52 posts ]  Go to page Previous  1, 2, 3
Author Message
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 9:32 
Offline

Joined: December 5th, 2011, 5:38
Posts: 1626
Location: Italy
higgsboson wrote:
Hi Guys
Sorry for my ignorance. I have UDMA express but not done much work on ROM /electronics.
can you pls. let me know how can I read and transfer ROM from Seagate / WD drives without desoldering ROM physically ?
(patient PCB might be burned or have some issues).
Thank you in advance


You have a Ferrari but you have still not got the drive license!
:lol: :lol:

You can read the rom on board via eprom programmer that supports SPI flash rom + SOP8 to DIP clip adapter, but this doesn't work with all PCBs.
Also, it may not be possible to read rom on board via eprom if something is shorted on 5V power line.
On some board (example 100466725) you can read rom on board via eprom (if there isn't any short on +5V line) but you can't write it, in that case just write it via pc3000 on donor pcb by using serial binary mode.

WD PCBs are easy, you can read and write rom on board via eprom if:
1) there isn't any short circuit on +5V line.
2) ROM is on external SPI flash.

Of course it's not possible to work with eprom on WD pcb that have embedded rom in MCU.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI#MxP2J6ZNqXDcrX40I8MoQQ


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 16:02 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
@ROb, your ROM is divided in two halves which are, for the most part, copies of each other. There are a few minor differences. Some of these differences appear to be genuine while others appear to reflect an attempt to edit various parameters including the serial and model number.

Here are the two headers. Their 16-bit checksums are 0x0000.

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

00000000  A1 0A 00 00 E8 04 00 00 00 00 00 00 B8 B3 04 00  ¡...è.......¸³..
00000010  63 73 69 44 00 00 88 3E 48 47 00 00 20 FF FF FF  csiD..ˆ>HG.. ÿÿÿ

00040000  A1 0A 00 00 E8 04 00 00 00 00 00 00 97 BF 04 00  ¡...è.......—¿..
00040010  63 73 69 44 00 00 A9 32 48 47 00 00 20 FF FF FF  csiD..©2HG.. ÿÿÿ

Next follows an index of ROM modules. Each half of the ROM has an identical index.

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

00000020  16 48 00 00 15 50 00 00 0E 50 02 00 10 E0 04 00
00000030  06 00 00 02 04 10 84 02 05 20 86 02 03 38 D2 02
00000040  0B 38 EA 03 00 38 FB 03

Here is the structure of the ROM modules according to the index:

Code:
ID    Start Loc  Description
---------------------------------------------------------------------------------------
16    0x48       data
15    0x50       data/code -- differs from copy #2
0E    0x250      data
10    0x4E0      code
06    0x20000    Read Adaptive Parameters (RAP)
04    0x28410    Controller Adaptive Parameters (CAP) - serial number, model number, DOM
05    0x28620    Servo Adaptive Parameters (SAP)
03    0x2D238    code
0B    0x3EA38    data/code
00    0x3FB38    end of ROM modules in first half of ROM

16    0x40048    data
15    0x40050    data/code -- differs from copy #1
0E    0x40250    data
10    0x404E0    code
06    0x60000    Read Adaptive Parameters (RAP)
04    0x68410    Controller Adaptive Parameters (CAP) - serial number, model number, DOM
05    0x68620    Servo Adaptive Parameters (SAP)
03    0x6D238    code
0B    0x7EA38    data/code
00    0x7FB38    end of ROM modules in second half of ROM

Module #15 differs in each half of the ROM, but I believe these differences to be OK.

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

00000050  62 00 01 00 FF FF FF 7F 00 00 00 00 00 00 00 00  b...ÿÿÿ.........
00000060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000070  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000090  00 00 00 00 00 00 00 00 A0 00 02 00 FF FF FF 7F  ........ ...ÿÿÿ.

00040050  62 00 01 00 FF FF FF 7F 17 06 03 13 C0 00 00 00  b...ÿÿÿ.....À...
00040060  80 4F 00 00 00 28 11 04 00 00 08 00 0B 21 02 00  €O...(.......!..
00040070  18 04 44 12 04 18 11 20 08 00 00 00 00 00 00 00  ..D.... ........
00040080  00 00 00 00 44 12 00 00 00 00 00 00 00 00 00 00  ....D...........
00040090  00 00 00 00 00 00 00 00 A0 00 02 00 FF FF FF 7F  ........ ...ÿÿÿ.

The corruption appears to be in the CAP and SAP modules. There are no differences in any other modules.

Here is the only difference in the SAP copies:

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

00028650        36 59 44 30 53 39 35 34                      6YD0S954

00068650        35 59 44 36 33 58 51 44                      5YD63XQD

Here are the CAP modules:

S/N = 5YD03XQD, Model = ST2000DL001-9VT156, DOM = 06102011

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

00028410  00 00 08 00 00 34 04 40 20 00 00 00 35 59 44 30  .....4.@ ...5YD0
00028420  33 58 51 44 30 30 30 30 4B 32 31 30 34 38 30 37  3XQD0000K2104807
00028430  FF FF FF FF FF FF FF FF FF FF 06 01 50 00 C5 00  ÿÿÿÿÿÿÿÿÿÿ..P.Å.
00028440  44 35 68 BC 4F 02 FF FF FF FF FF FF FF FF FF FF  D5h¼O.ÿÿÿÿÿÿÿÿÿÿ
........
000284E0  FF FF FF FF FF FF FF FF 30 36 31 30 32 30 31 31  ÿÿÿÿÿÿÿÿ06102011
000284F0  03 FF FF FF FF FF FF FF FF FE 00 00 53 54 32 30  .ÿÿÿÿÿÿÿÿþ..ST20
00028500  30 30 44 4C 30 30 31 2D 39 56 54 31 35 36 20 20  00DL001-9VT156 
00028510  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                 
00028520  20 20 20 20 53 54 32 30 30 30 44 4C 30 30 31 2D      ST2000DL001-
00028530  39 56 54 31 35 36 20 20 20 20 20 20 20 20 20 20  9VT156         
00028540  20 20 20 20 20 20 20 20 20 20 20 20 B0 88 E0 E8              °ˆàè
00028550  FF FF FF FF 00 02 FF FF FF FF FF FF FF FF FF FF  ÿÿÿÿ..ÿÿÿÿÿÿÿÿÿÿ
........
00028610  FF FF FF FF FF FF FF FF EF 81 00 00 00 00 00 00  ÿÿÿÿÿÿÿÿï.......

S/N = 6YD0S954, Model = ST2000DL003-9VT166, DOM = 06052011

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

00068410  00 00 08 00 00 34 04 40 20 00 00 00 36 59 44 30  .....4.@ ...6YD0
00068420  53 39 35 34 30 30 30 30 4B 31 34 37 4C 4D 39 30  S9540000K147LM90
00068430  FF FF FF FF FF FF FF FF FF FF 06 01 50 00 C5 00  ÿÿÿÿÿÿÿÿÿÿ..P.Å.
00068440  37 97 6B A6 4F 02 FF FF FF FF FF FF FF FF FF FF  7—k¦O.ÿÿÿÿÿÿÿÿÿÿ
........
000684E0  FF FF FF FF FF FF FF FF 30 36 30 35 32 30 31 31  ÿÿÿÿÿÿÿÿ06052011
000684F0  03 FF FF FF FF FF FF FF FF FE 00 00 53 54 32 30  .ÿÿÿÿÿÿÿÿþ..ST20
00068500  30 30 44 4C 30 30 33 2D 39 56 54 31 36 36 20 20  00DL003-9VT166 
00068510  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                 
00068520  20 20 20 20 53 54 32 30 30 30 44 4C 30 30 33 2D      ST2000DL003-
00068530  39 56 54 31 36 36 20 20 20 20 20 20 20 20 20 20  9VT166         
00068540  20 20 20 20 20 20 20 20 20 20 20 20 B0 88 E0 E8              °ˆàè
00068550  FF FF FF FF 00 02 FF FF FF FF FF FF FF FF FF FF  ÿÿÿÿ..ÿÿÿÿÿÿÿÿÿÿ
........
00068610  FF FF FF FF FF FF FF FF EF 81 00 00 00 00 00 00  ÿÿÿÿÿÿÿÿï.......

ISTM that the solution is to repair the SAP and CAP and then recalculate checksums, if necessary.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 17:25 
Offline

Joined: October 3rd, 2005, 0:40
Posts: 4311
Location: Hungary
in case the adaptives itself were replaced and serial changed, it will be though to recover, but not impossible. I did not have time to check your rom checksums so far though...

_________________
Adatmentés - Data recovery


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 17:53 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
It looks to me as if the ROM contains a copy of the existing adaptives. The editing was sloppy. I suspect that the person who did this probably has no knowledge of checksums, so a simple text edit and a CAP patch might be all that is required.

BTW, there are 3 serial numbers -- 6YD0S954 or 5YD63XQD or 5YD03XQD. Only one can be correct.

It might help if ROb were to tell us the history of this drive.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 21:07 
Offline

Joined: October 3rd, 2005, 0:40
Posts: 4311
Location: Hungary
the question is what's on the label :)

_________________
Adatmentés - Data recovery


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 2nd, 2016, 21:53 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
http://support.seagate.com/customer/en- ... dation.jsp

    6YD0S954
    9VT166-570
    OEM

    5YD63XQD
    9VT156-570
    Out of Warranty

    5YD03XQD
    "Warranty could not be determined. Please check the serial ..."

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 3rd, 2016, 4:05 
Offline

Joined: November 29th, 2006, 10:08
Posts: 7843
Location: UK
fzabkar wrote:
http://support.seagate.com/customer/en-US/warranty_validation.jsp

    6YD0S954
    9VT166-570
    OEM

    5YD63XQD
    9VT156-570
    Out of Warranty

    5YD03XQD
    "Warranty could not be determined. Please check the serial ..."


Which would indicate "5YD03XQD" is a non-existent s/n and is a purposely altered "5YD63XQD" :-(

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 3rd, 2016, 5:39 
Offline

Joined: October 3rd, 2005, 0:40
Posts: 4311
Location: Hungary
the question is still wether the adaptives are native or they have been replaced by some foreign stuff and SN altered...

_________________
Adatmentés - Data recovery


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 3rd, 2016, 7:00 
Offline

Joined: April 16th, 2008, 4:50
Posts: 264
The Sr. No. on the drive sticker is 5YD63XQD and sticker is not tampered with even the side sticker is same

Thanks


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 3rd, 2016, 8:59 
Offline

Joined: October 3rd, 2005, 0:40
Posts: 4311
Location: Hungary
got bad news for you.

the crc of SAP 1st copy is OK, and it has the foreign serial number. Since the only difference between the 2 copies is the serial number, I have a good reason to suppose SAP is not native.
If so, there are 4 options:
1: you or the client try to get the native adaptives from the place the drive was before
2: if the first one fails, i can rebuild adaptives for this model with a good chance but it costs an arm and a leg,
3: you try to rebuild it, it will take a long time if u ever succeed (i have no information about anybody being capable of doing it so far),
4: client acknowledges the facts and give up on the recovery.

pepe

_________________
Adatmentés - Data recovery


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: March 3rd, 2016, 9:52 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Maybe some "DR lab" received a drive with a damaged ROM, then proceeded to "adapt" a donor PCB by hacking the drive ID and leaving the donor adaptives untouched. This would mean that the RAP was non-native as well.

Could we see a photo of the label (DOM) and a detailed photo of the component side of the PCB? Perhaps the IC date codes will tell us something. That said, the CAP DOM values are very close.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: ST2000DM001 corrupt ROM
PostPosted: January 18th, 2018, 23:49 
Offline
User avatar

Joined: August 15th, 2006, 3:01
Posts: 3464
Location: CDRLabs @ Chandigarh [ India ]
Seriously ,
MRT Users Beware i Just Ordered a MRT Ultra Card Few Days Ago And They Shipped a Ver 1.0 Programmer That Was Long Discarded By Them Thinking Its Going To a Third Work Country "India " . Every Person Who Has Purchased The MRT Ultra/Express Tool Should Please Check And Get In Touch With MRT Sales Team That is Shipping Ver 1 Of The ROM Programmer Dated 2012 With New Tools

PS : Shame on You Guys

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 52 posts ]  Go to page Previous  1, 2, 3

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot], Google Adsense [Bot] and 61 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group