Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 1
  [ 14 posts ] 
  Previous topic | Next topic 
Author Message
gtd4242
 Post subject: Samsung / Seagate st1000lm024 Damaged ROM Recoverable?
PostPosted: April 14th, 2015, 10:51 
Offline

Joined: April 10th, 2007, 9:53
Posts: 335
I have a Samsung that came in. The drive does not power up. Powers up fine with an exact match parts drive PCB. I swapped the ROM, and the drive does not power up. I swap the parts drive ROM to the failed drive's PCB and it powers up, so it is definitely a ROM issue. The drive just stays in a BSY state though, which I would expect.

Any hints, or tips on anything that I can do to try and get this working through terminal? I work with Seagates quite a bit in terminal, but never Samsung variations. It appears the baud rate is different on these, and I'm assuming the commands are going to be different. Without the native ROM is it even possible to get the donor ROM to be compatible, or do you have to do a hot swap type procedure? Feel free to PM if you prefer. Thanks.
Top
 Profile  
 
fzabkar
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 14th, 2015, 11:51 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15529
Location: Australia
Can you provide a ROM dump? Could it be a FIPS corruption problem?

_________________
A backup a day keeps DR away.
Top
 Profile  
 
gtd4242
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 14th, 2015, 12:37 
Offline

Joined: April 10th, 2007, 9:53
Posts: 335
They said the drive had a voltage surge and then wouldn't spin up after that. I'm thinking it damaged the ROM.
Top
 Profile  
 
MindMergepk
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 14th, 2015, 12:39 
Offline
User avatar

Joined: December 8th, 2013, 4:48
Posts: 831
Location: Pakistan
@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

have seen some Samsung drives with ROM bug, not this model. thanks to pcimage for pointing those out.
you can adapt new PCB by writing 02 modules from working drive to patient drive by hot-swap.

what tools you have BTW ?

_________________
Data Recovery Pakistan
Top
 Profile  
 
fzabkar
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 14th, 2015, 16:38 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15529
Location: Australia
MindMergepk wrote:
@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643

_________________
A backup a day keeps DR away.
Top
 Profile  
 
fzabkar
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 14th, 2015, 16:46 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15529
Location: Australia
gtd4242 wrote:
They said the drive had a voltage surge and then wouldn't spin up after that. I'm thinking it damaged the ROM.

Measure the resistance between the chip's Vcc and Ground pins.

As for baud rates, etc ...

How to connect a terminal cable on a Samsung drive ?
http://www.hddoracle.com/viewtopic.php?f=116&t=189

If you can upload the contents of patient and donor ROMs, I can try to verify their checksums.

_________________
A backup a day keeps DR away.
Top
 Profile  
 
chinopk
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 15th, 2015, 9:34 
Offline

Joined: March 20th, 2010, 4:34
Posts: 256
Location: Turkey
deleted.. sorry

_________________
RAID/Server Recovery
Top
 Profile  
 
MindMergepk
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: April 15th, 2015, 9:53 
Offline
User avatar

Joined: December 8th, 2013, 4:48
Posts: 831
Location: Pakistan
fzabkar wrote:
MindMergepk wrote:
@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643


thank you, always an admirer of you :D

_________________
Data Recovery Pakistan
Top
 Profile  
 
nuwanddi
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 22nd, 2019, 10:05 
Offline

Joined: March 23rd, 2017, 1:36
Posts: 8
Location: SriLanka
hello everyone. this is the ROM from My HM500JJ Drive. Drive doesnt spin up with this ROM. i dont have a exact same donner. i have a HM320HJ with same board. so when i swap the board Drive spins up and stays busy, can someone help me to solve this case ?? i have MRT with me


Attachments:
W25X40_20190322_174315.zip [177.27 KiB]
Downloaded 372 times
Top
 Profile  
 
Mikippp
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 22nd, 2019, 12:20 
Offline

Joined: May 30th, 2005, 17:07
Posts: 528
Hi,

Mikippp


Attachments:
W25X40_20190322_174315_FIPS.zip [176.85 KiB]
Downloaded 370 times
Top
 Profile  
 
pcimage
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 22nd, 2019, 15:15 
Offline

Joined: November 29th, 2006, 10:08
Posts: 7843
Location: UK
Nothing in terminal?

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

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!
Top
 Profile  
 
fzabkar
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 22nd, 2019, 16:28 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15529
Location: Australia
According to my program ...

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

Found FIPS text string at 0x014362
Checksum for 0x0400 byte FIPS block = 0xCE80  - BAD
Checksum for 0x0800 byte FIPS block = 0x8337  - BAD
Checksum for 0x0C00 byte FIPS block = 0x4A34  - BAD
Checksum for 0x1000 byte FIPS block = 0x66E0  - BAD

Found FIPS text string at 0x0194BC
Checksum for 0x0400 byte FIPS block = 0xD568  - BAD
Checksum for 0x0800 byte FIPS block = 0x535F  - BAD
Checksum for 0x0C00 byte FIPS block = 0x9CE2  - BAD
Checksum for 0x1000 byte FIPS block = 0x26E4  - BAD

Found FIPS text string at 0x019CB8
Checksum for 0x0400 byte FIPS block = 0x8279  - BAD
Checksum for 0x0800 byte FIPS block = 0xC52D  - BAD
Checksum for 0x0C00 byte FIPS block = 0x5B54  - BAD
Checksum for 0x1000 byte FIPS block = 0x98EC  - BAD

Could not find a FIPS block with valid checksum

_________________
A backup a day keeps DR away.
Top
 Profile  
 
sin
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 21st, 2020, 18:30 
Offline

Joined: September 17th, 2016, 16:06
Posts: 431
Location: India
MindMergepk wrote:
fzabkar wrote:
MindMergepk wrote:
@ fzabkar Not sure but i think with FIPS corruption drive did spin up, right ?

No.

http://www.hddoracle.com/viewtopic.php?f=19&t=643


thank you, always an admirer of you :D


Count me in
--
Top
 Profile  
 
Amarbir[CDR-Labs]
 Post subject: Re: Samsung / Seagate st1000lm024 Damaged ROM Recoverable
PostPosted: March 23rd, 2020, 0:56 
Offline
User avatar

Joined: August 15th, 2006, 3:01
Posts: 3471
Location: CDRLabs @ Chandigarh [ India ]
Frank ,
Its Not The FIPS Always ,Sometimes the client changed the pcb without saying that to the DR lab ,In that case a terminal dump is imp to see if Heads are compatible or not ,Even that stage the hdd does not power up

_________________
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  Page 1 of 1
  [ 14 posts ] 

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 81 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:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group