seagate barracuda 8HB ST8000DM004

[taengukim]

Is there a workaround for the ROM boot code lock??
Should I read after removing the chip??

[taengukim]

Is there a workaround for the ROM boot code lock??
Should I read after removing the chip??

Attachments

[taengukim]

Is there a workaround for the ROM boot code lock??
Should I read after removing the chip??

Attachments

[digisupport]

As it says in log " Use programmer for ROM reading" - You can not use PC3K ( for now )
Read ROM with external programmer. Patch ROM in PC3K and write it back again.
I prefer to read/write on board with a pogo clip.

[pepe]

- read rom several times and compare them
- make sure you read the full rom, ie not just the half of it with a bad config.

[taengukim]

As it says in log " Use programmer for ROM reading" - You can not use PC3K ( for now )
Read ROM with external programmer. Patch ROM in PC3K and write it back again.
I prefer to read/write on board with a pogo clip.

Thank you! so much!

[taengukim]

- read rom several times and compare them
- make sure you read the full rom, ie not just the half of it with a bad config.

How can I make the comparison accurate?

[digisupport]

- read rom several times and compare them
- make sure you read the full rom, ie not just the half of it with a bad config.

How can I make the comparison accurate?

Make sure you chose the correct chip in your programmer. Read and save several times and compare your dumps.
PC3K HexEdit, WinHex whatever you prefer will do fine. Also check ROM info when you load it in PC3K.

[pepe]

i would add TotalCommander as an option, it can do that OOB.

[taengukim]

You have completed the ROM patch.
However, the data is not visible.
What's the problem?
Upload both terminals and logs.
Everything seems normal on the log.
Just in case, I'm going to post ROM too.

Attachments

[pepe]

Try cloning the drive first then do logical recovery on the clone...

[taengukim]

<font style="vertical-align: inherit;"><font style="vertical-align: inherit;">먼저 드라이브를 복제한 다음 복제본에서 논리적 복구를 수행해 보세요.</font></font>

It looks like this.
The folder with E does not have data even when it is recovered, and the capacity is zero. In this case, is there no other way but to recover RAW?
Is it broken data?

Attachments

[northwind]

E = EFS encrypted, if I remember correctly.

[taengukim]

E = EFS encrypted, if I remember correctly.

Is it correct that the customer encrypted it?
The customer says he didn't encrypt anything, but does this even encrypt himself?