All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 7 posts ] 
Author Message
 Post subject: BIOS chip mix-up
PostPosted: October 31st, 2022, 9:29 
Offline

Joined: June 8th, 2018, 9:27
Posts: 7
Location: Amerika Birleşik Devletleri
Dear all,

I had someone transfer the BIOS chip to a donor board(2060-771961-001 rev A) but I suspect there was an error. I read the dump files with CH341A and one of the files contain the exact model of my drive. (WDC WD10JMVW-11AJGS1) The other contains the model of USB IC (INIC-3608)
I'd expect the one with INIC-3608 text string to be the U14 but I want to make sure before soldering.

Thanks.


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 1st, 2022, 3:56 
Offline

Joined: August 18th, 2010, 17:35
Posts: 3636
Location: Massachusetts, USA
No need to worry about U14

_________________
Hard Disk Drive, SSD, USB Drive and RAID Data Recovery Specialist in Massachusetts


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 1st, 2022, 4:26 
Offline

Joined: June 8th, 2018, 9:27
Posts: 7
Location: Amerika Birleşik Devletleri
The problem is I don't know which chip to not worry about. :D
Do you think the one with HDD model string is U12?


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 1st, 2022, 11:52 
Offline

Joined: June 8th, 2018, 9:27
Posts: 7
Location: Amerika Birleşik Devletleri
islamm3rouf wrote:
one of them will spin disk up
this is ROM

other one will not

try with no problem


Thank you. The disk spins now but not recognized through USB. Replacement PCB is rev B. My original was rev A. Are they interchangeable?


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 3rd, 2022, 6:05 
Offline

Joined: June 8th, 2018, 9:27
Posts: 7
Location: Amerika Birleşik Devletleri
This is the ROM content I got by usin fzabkar's tool. Do you think my problem is ROM related?

Code:
Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
-----  -- --   --   -----   -----   --------   ------ -----  ---------
    0  5A C1   02     100 -  2477      127F0     2376  2376  A1FE A1FE   OK
   20  01 5B   0C    2478 -  4C4C   88800000     27D4  27D4    4C   4C   OK
   40  02 D5   01    4C4D -  CFA9          0 c   AB1C  835C    A4   A4   OK
   60  03 A9   01    CFAA -  D6A2      1179C c    8C0   6F8    65   65   OK
   80  04 02   03    D6A3 -  D89B      80220 c    2B0   1F8    40   40   OK
   A0  05 CC   03    D89C -  DA90   10157200 c    318   1F4    57   57   OK
   C0  06 FB   01    DA91 - 24C49   90349A00 c  1EA38 171B8    77   77   OK
   E0  07 94   01   24C4A - 3DCCE   90006E30 c  236AC 19084    FB   FB   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FCD2

Active directory flag = 0x02

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x00045600  0x00000000
0x01  0x00045600  0x0005C800
0x02  0x00045600  0x000B9000
0x03  0x00045600  0x00115800

Verifying ROYL modules ...

ID          Size (bytes)         Address    Checksum
dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00019BAB             N/A
000A  OK     0000003E  00000200   0003F000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  OK     00000400  OK         0003F8D2   00000000  OK
0047  OK     00000400  OK         0003F4D2   00000000  OK
000D  OK     00000094  00000200   0003F03E   00000000  OK
004F  OK     00000400  OK         0003F0D2   00000000  OK

ROYL directory module 0x020B found at 0x3ECD2

Active directory flag = 0xFE

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x0002CA60  0x00000000
0x01  0x0002CA60  0x0005C800
0x02  0x0002CA60  0x000B9000
0x03  0x00000000  0x00000000
0x04  0x00000000  0x00000000
0x05  0x00000000  0x00000000
0x06  0x00000000  0x00000000
0x07  0x00000000  0x00000000

Verifying ROYL modules ...

ID          Size (bytes)         Address    Checksum
dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00000000             N/A
000A  OK     0000003E  00000200   0003E000   00000000  OK
000B  OK     00000169  00000200   0003FCD2   00000000  OK
020B  OK     00000169  00000200   0003ECD2   00000000  OK
0030  FFFF   00000400  01FFFE00   0003E8D2   FFFFFF00  BAD
0047  FFFF   00000400  01FFFE00   0003E4D2   FFFFFF00  BAD
000D  OK     00000094  00000200   0003E03E   00000000  OK
004F  OK     00000400  OK         0003E0D2   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_02\000Bmods and Flash_02\020Bmods

Active directory is 0x0B

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 4/4
Head map #1 = 0x0F / 0b00001111
Head map #2 = 0x00 / 0b00000000

DCM = | Q | G J N V D H E
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE209153191
Model Number = WDC WD10JMVW-11AJGS1                   
Serial Number =                     


Analysing active 0x4F module ...

ROM version = 0006000M

Analysing active 0x47 module ...

Preamp values
-----------
0  033B3217
1  033B5515
2  02393418
3  023B3419

Microjogs
-------
0  0000
1  0000
2  0000
3  0000

Head/Media DCM = NJ


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 3rd, 2022, 19:33 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15526
Location: Australia
The ROM seems OK. The "BAD" ROYL modules are in the inactive directory. All the modules in the active directory are good.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: BIOS chip mix-up
PostPosted: November 5th, 2022, 10:30 
Offline

Joined: August 18th, 2010, 17:35
Posts: 3636
Location: Massachusetts, USA
Rarely it is a problem with the ROM or PCB in general on that model drive.

The problems with that model typically are:
-disk surface degradation (bad sectors)
-many bad sectors accumulation trigger firmware problems
-mechanical - reading heads

If the drive is recognized with correct capacity, then you could try cloning with ddrescue or hddsuperclone. They are the best you could do with software based tools a DiY at home (if the drive clones slowly, as in taking weeks, then it has firmware or mechanical issues).

Specialists use more advanced hardware cloning tools.

_________________
Hard Disk Drive, SSD, USB Drive and RAID Data Recovery Specialist in Massachusetts


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

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