All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 4:08 
Offline

Joined: November 7th, 2018, 4:02
Posts: 3
Location: Poland
Hello,

I am looking for a Rom to Samsung HM321HI ver. 2AJebq4
Does anyone have a working ROM?
I add the original rom from the PCB.

Regards,
Michael


Attachments:
samsung_oryginal.zip [177.41 KiB]
Downloaded 5 times
Top
 Profile  
 
 Post subject: Re: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 5:23 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 10944
Location: Australia
What error do you see in terminal?

Here is the output of my ROM analysis tool:

Code:
Verifying Samsung SpinPoint ROM:  samsung_oryginal.bin

Checksum of Boot Block header = 0xAE  - OK
Checksum of Boot Block (Actual/Expected) = 0x672C / 0x672C  - OK

Searching for FIPS block (expected checksum = 0x0000) ...

Found FIPS text string at 0x003000

Checksum for 0x0800 byte FIPS block = 0x0000  - OK

Possible 0x0800 byte FIPS block at address 0x003000

Searching for FLASHTBL ...

Found FLASHTBL text string at 0x004024
Parsing FLASHTBL at 0x004000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  00   FF         0 FFFFFFFF                    0            N/A
01  02   FF       320     4000 - 431F      FFF04000  B3 77   - BAD (Note 2)
02  08   FF       5DC     4320 - 48FB      FFF04320  55 55   - OK
03  00   FF     13EAC     4900 - 187AB            0  74 75   - BAD (Note 3)
04  01   FF      2B98    187B0 - 1B347        14D00  00 57   - BAD (Note 1)
05  00   FF       C70    187B4 - 19423      4000000  7A 7A   - OK
06  00   FF       228    19428 - 1964F      4005C00  F8 F8   - OK
07  00   FF     19A40    19654 - 33093     10000300  FE FE   - OK
08  01   FF     1B4B4    33098 - 4E54B     1002E300  00 BB   - BAD (Note 1)
09  00   FF      2A4C    3309C - 35AE7     18052300  9B 9B   - OK
0A  00   FF      12EC    35AEC - 36DD7     200164F0  97 97   - OK
0B  00   FF       1D8    36DDC - 36FB3     FFFE1000  92 92   - OK
0C  00   FF       DD0     1800 - 25CF      FFF01800  07 08   - BAD (Note 3)
0D  02   FF         0 FFFFFFFF             FFF04000            N/A
0E  08   FF         0 FFFFFFFF             FFF04320            N/A
0F  20   FF         0 FFFFFFFF             FFF01800            N/A
10  00   FF         0 FFFFFFFF             FFFC0000            N/A
11  00   FF         0 FFFFFFFF             200164F0            N/A

Searching for SERVOTBL ...

Found SERVOTBL text string at 0x037024
Parsing SERVOTBL at 0x037000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  02   FF       100    37000 - 370FF     FFF37000  17 68   - BAD (Note 2)
01  00   FF      8E58    37104 - 3FF5B            0  51 51   - OK
02  00   FF       814    3FF60 - 40773      4000100  18 18   - OK
03  00   FF       2A0    40778 - 40A17     FFFE1000  6F 6F   - OK
04  02   FF         0    36FFF             FFF37000            N/A


Size            - size of module in ROM expressed in bytes
ROM address     - absolute address range of module in ROM
RAMaddrs        - load point of module in RAM
Cksm (Exp/Act)  - Expected Checksum / Actual Checksum


Note 1:  The address range of affected module may conflict with another module,
          in which case this is probably a false negative.

Note 2:  If this module is the FLASHTBL or SERVOTBL, then this is most likely
          a false negative.

Note 3:  This may or may not be a genuinely BAD module. Examine the checksum
          of the first half of the ROM. If 0x0000, then module is probably OK,
          otherwise it may or may not be bad. Also examine the "adjusted"
          checksum, if applicable.

Note 4:  The address range of the module is outside the limits of the ROM.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 8:30 
Offline

Joined: November 7th, 2018, 4:02
Posts: 3
Location: Poland
Dear fzabkar,

I did not connect to the terminal. Drive does not spin.
I tried to copy the FIPS section from a working rom but it does not work.


Top
 Profile  
 
 Post subject: Re: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 9:50 
Offline

Joined: May 30th, 2005, 17:07
Posts: 460
Code:
  Information about dump
   Dump size............................... : 524288 bytes
   Firmware checksum....................... : Ok
   FIPS offset............................. : 0x00003000
   FIPS size............................... : 4096 bytes
   FIPS checksum........................... : Ok
   Firmware type........................... : Main Code
   Original name........................... : 2AJebq4M.143
   Platform Id............................. : 0x2B
   Head map................................ : 0, 1


Mikippp


Attachments:
2AJebq4M_d43.zip [176.91 KiB]
Downloaded 7 times
Top
 Profile  
 
 Post subject: Re: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 10:26 
Offline

Joined: November 7th, 2018, 4:02
Posts: 3
Location: Poland
Dear Mikippp,

Your rom works. Thank you very much for your help.


Top
 Profile  
 
 Post subject: Re: Samsung ROM corrupted. Please Help.
PostPosted: November 7th, 2018, 14:49 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 10944
Location: Australia
ISTM that the FIPS size is 2048 bytes, not 4096.

Code:
Verifying Samsung SpinPoint ROM:  2AJebq4M_d43.bin

Checksum of Boot Block header = 0xAE  - OK
Checksum of Boot Block (Actual/Expected) = 0x672C / 0x672C  - OK

Searching for FIPS block (expected checksum = 0x0000) ...

Found FIPS text string at 0x003000
Checksum for 0x0400 byte FIPS block = 0x3A94  - BAD
Checksum for 0x0800 byte FIPS block = 0x0000  - OK
Checksum for 0x0C00 byte FIPS block = 0xFE00  - BAD
Checksum for 0x1000 byte FIPS block = 0xFC00  - BAD

Possible 0x0800 byte FIPS block at address 0x003000

Searching for FLASHTBL ...

Found FLASHTBL text string at 0x004024
Parsing FLASHTBL at 0x004000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  00   FF         0 FFFFFFFF                    0            N/A
01  02   FF       320     4000 - 431F      FFF04000  B3 77   - BAD (Note 2)
02  08   FF       5DC     4320 - 48FB      FFF04320  55 55   - OK
03  00   FF     13EAC     4900 - 187AB            0  74 74   - OK
04  01   FF      2B98    187B0 - 1B347        14D00  00 57   - BAD (Note 1)
05  00   FF       C70    187B4 - 19423      4000000  7A 7A   - OK
06  00   FF       228    19428 - 1964F      4005C00  F8 F8   - OK
07  00   FF     19A40    19654 - 33093     10000300  FE FE   - OK
08  01   FF     1B4B4    33098 - 4E54B     1002E300  00 BB   - BAD (Note 1)
09  00   FF      2A4C    3309C - 35AE7     18052300  9B 9B   - OK
0A  00   FF      12EC    35AEC - 36DD7     200164F0  97 97   - OK
0B  00   FF       1D8    36DDC - 36FB3     FFFE1000  92 92   - OK
0C  00   FF       DD0     1800 - 25CF      FFF01800  07 08   - BAD (Note 3)
0D  02   FF         0 FFFFFFFF             FFF04000            N/A
0E  08   FF         0 FFFFFFFF             FFF04320            N/A
0F  20   FF         0 FFFFFFFF             FFF01800            N/A
10  00   FF         0 FFFFFFFF             FFFC0000            N/A
11  00   FF         0 FFFFFFFF             200164F0            N/A

Searching for SERVOTBL ...

Found SERVOTBL text string at 0x037024
Parsing SERVOTBL at 0x037000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  02   FF       100    37000 - 370FF     FFF37000  17 68   - BAD (Note 2)
01  00   FF      8E58    37104 - 3FF5B            0  51 51   - OK
02  00   FF       814    3FF60 - 40773      4000100  18 18   - OK
03  00   FF       2A0    40778 - 40A17     FFFE1000  6F 6F   - OK
04  02   FF         0    36FFF             FFF37000            N/A

Size            - size of module in ROM expressed in bytes
ROM address     - absolute address range of module in ROM
RAMaddrs        - load point of module in RAM
Cksm (Exp/Act)  - Expected Checksum / Actual Checksum

Note 1:  The address range of affected module may conflict with another module,
          in which case this is probably a false negative.

Note 2:  If this module is the FLASHTBL or SERVOTBL, then this is most likely
          a false negative.

Note 3:  This may or may not be a genuinely BAD module. Examine the checksum
          of the first half of the ROM. If 0x0000, then module is probably OK,
          otherwise it may or may not be bad. Also examine the "adjusted"
          checksum, if applicable.

Note 4:  The address range of the module is outside the limits of the ROM.

_________________
A backup a day keeps DR away.


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot], Google Adsense [Bot], Majestic-12 [Bot] and 43 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