m11 st5000lm - encryption lost ??

[Alandata Recovery]

Model : ST5000LM000-2AN170
Serial : WCJ3LM2H
Firmware : 0001
Capacity : 0 MB ()


I have this drive. Comes up and stays BSY.

Sounds great, heads doing constant rapid seeking.
It comes up with mcmt corrupt

techmode patched rom
backed up 1b, 28
348 wont read

Then I had to leave and left it for ace.
==================

COM transfer baud rate set to 460800
Rd Sys File: vol = 3, FID = 01B, Copy = 000...
Receiving file FILE_3_01B_0, length = 5210112
Rd Sys File: vol = 3, FID = 01B, Copy = 001...
Receiving file FILE_3_01B_1, length = 5210112
Rd Sys File: vol = 3, FID = 028, Copy = 000...
Receiving file FILE_3_028_0, length = 7806976
Rd Sys File: vol = 3, FID = 028, Copy = 001...
Receiving file FILE_3_028_1, length = 7806976
Rd Sys File: vol = 3, FID = 348, Copy = 000...
Root Sys File Rd Err!
Rd Sys File: vol = 3, FID = 348, Copy = 001...
Root Sys File Rd Err!

==============

Ace dialed in and made a new 348

They lost getting terminal and said I needed to short to get terminal

Then do cU10, repower and upload their 348 to ram.

I did all that but sectors look encrypted

======

ACE:

Checked this case via TeamViewer.
Unfortunately, lost a terminal access.
Please, short the reading channel on the PCB for getting stable terminal access.
Next step will be a MC reset by F3 T>/cU10 command,
repower the drive, send handshake command,
re-enter in utility for firmware recognization.
Then upload 348 system file from the profile folder into the RAM of drive.

=======

Here is terminal log:

FF3 T>/cU10

MCInitialize: Start: Host VBM Size (Bytes): 00000210 Metadata VBM Size (Bytes): MC Segments: 0000C30C
MCInitialize: MCMTBufferPtr->Header.MCMTHeader.MediaCacheDiscStateFlags = 0000000A
MCInitialize: MCMTBufferPtr->Header.MCMTHeader.MCStateFlagsDisc = 00000001
MCInitialize: MCStateFlags = 00000001

Set MCMT Version Current
[MCMTW_DSW] Written to Primary
[MCMTW_DSW] Written to Secondary
MCInitialize: Init complete:
F3 C>

========================

ACE says:

Guess, somebody specially spoiled firmware.

SED drives have a SED keys for getting decrypted data access.
It is 1D2 system file.
Here it is empty, rewritten.
In case if 1D2 is corrupted/damaged, it might be resurrected from 1D1 cache,
but it is also filled with zeros.

As a result 1D2 key can't be restorred for getting decrypted data access.

=====================

Ace says somebody cleared the SED key.

The only thing I wrote to the drive was the tech mode rom patch.

I did a resource BU once i got terminal

I wonder what could cause the sed keys to be lost.

Anybody experience this ?

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

www.alandata.com   www.alandataRecovery.com

[wayne horner]

i found a thread where the issue was solved by using the backup sed in the 1d1 sysfile.

ace says they tried that.

https://forum.hddguru.com/viewtopic.php?f=1&t=43339&mobile=desktop

Alandata Data Recovery -  (949)287-3282  

"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWRhq2GiTUEBzb46DYS6n_OuXmJHw7VSrOtaXMmvR%3DjgBg%40mail.gmail.com.

[wayne horner]

here is my 1d1 and 1d2

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

[pbzcbf...@gmail.com]

So where is Ace's attempted reconstruction of ID2? I can see how MRT was able to do it.

[Alandata Recovery]

Ace did not attempt a reconstruction. 

The said the cached copy in 1 was zeroed out 

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/078c78a5-4d70-4245-9008-874318a3b2c1n%40googlegroups.com.

[pbzcbf...@gmail.com]

I extracted 1D2 from 1D1 at offsets 0x22000 - 0x23FFF.

[pbzcbf...@gmail.com]

I believe the attached 1D2 module incorporates the "permanent unlock" hack that @gps31 was referring to at HDD Guru.

[Alandata Recovery]

thanks !

he will bring the drive back saturday and I will try it

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/7367e064-286c-46a6-8f9f-e41f5faaf91fn%40googlegroups.com.

--

[Alandata Recovery]

DUDE !

IT WORKED !

You beat ace!

WahoO!

Can I send you some reward?

[pbzcbf...@gmail.com]

I extracted 1D2 from 1D1 at offsets 0x22000 - 0x23FFF. This is MRT's method, as illustrated by @gps31 in that HDD Guru thread. Very, very simple. I think you guys call it a no-brainer. I can only imagine that Ace's tech support guy was either too inept or too proud (because it was a Chinese solution?).

BTW, this is the third time I've solved a problem after Ace failed. Two were trivial like this one. The other was difficult, but Ace's attempt was grossly inept. To me it seems that there is vast gulf between Ace's developers and their tech support people.

[juanvd...@gmail.com]

Is this similar to this video from DFL more or less at the end of the video clip they show how to disable the encryption ?

 

ST2000LM009 Unrecoverysectorcount retry error HDD Repair and Data Recovery Steps

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/13921886-7be0-41fe-9d49-b21c650963f4n%40googlegroups.com.

[pbzcbf...@gmail.com]

Related topic:

https://forum.hddguru.com/viewtopic.php?f=1&t=45589

0x1D2 can be carved out of sys file 0x227 at 0x1C5000 - 0x1DBFFF.
0x1D2 can also be carved out of sys file 0x1D1 at 0x22000 - 0x38FFF.
0x30A can be carved out of sys file 0x227 at 0x2F1000 - 0x2F1FFF.

The master and user ATA passwords are stored in 0x30A. They can also be carved out of 0x1D1 at 0x39000 - 0x3910F.

 

[Extreme Solutions Parthipan]

Not all drive have 227.

IF QB available for that particular model then only either 227 or 226 available

In order to make any change u should modify in 227 or 226 if QB enabled Drives

just modify in 1D2 will not take effect if QB enabled

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/0516fa4a-2fb7-478d-b756-b232a9f5a49bn%40googlegroups.com.