Hello , Today I rx a WDC WD10TMVW-11ZSMS5_01.01A01_WD-WXL1E61LPWN2_00550005_1372_256 as a USB 3 drive which spun perfectly but did not detect.
Changed the usb board to equivalent SATA with standard procedures and drive got DRD DSC over sata, showed full capacity and ID when auto get details were clicked.
Scanned the drive and it began the process smoothly. The USB 3 had JMS538S so encryption was already suspected.
When I explored the sectors in HEX, the data looked encrypted. All res backup was done one by one and so far things were smooth and fast.
To make sure, I usually connect it to my DDI and do a head map and a media test, it reveals firstly the heads are ok and secondly on imaging the drive, if there is no mbr, mft,idx,media etc etc
loading up at the MFT area, I consider it encrypted for sure.
Explored the module 25 to see if it had the keys and the keys were certainly there.
It has been my little observation which may be true and equally untrue for cases that encrypting drives usually have a SA lock and this drive was not having any SA locks.
I had also seen that the data fails to decrypt if the SA is kept unlocked. So had an idea that problem was revolving around 02 itself.
Tried to lock the SA with marvell but still over the JSM bridge I have, it failed to give any data. All the blocks appeared as unreadable /yellows in DDI.
So finally i gazed around 8032 and made 02 out of it, matched the lengths and patched it.
Drive successfully gave all data decrypted over the USB bridge that I have.
Here are the attached modules. On comparing the 02 backup from 8032 and the original 02 itself, there are so many changes that i see in HxD.
I humbly request you to please comment on how to tackle such cases if there are more ways to solve.
- 02 and 02 made from 8032.rar
- (1.84 KiB) Downloaded 322 times