Full Support for Seagate LM Series
There are more and more Seagate hard drives with firmware lock. The so-called firmware lock is that the hard drives can get access to T-level, it can execute a few commands to view hard drives’ information, but can not execute critical operational terminal commands. Under this circumstance, writing and modifying commands could not be executed; what’s more, there will return the notice of “Diagnostic Port Locked” when trying to execute terminal commands. When there is such a notice, we can confirm that there is a firmware lock.
From the pic above, we can see that when there is a firmware lock, we can not get access to the data of system area nor user area.
Firmware lock is set by Seagate manufactures, in order to prevent hard drives’ refurbishing. However it will bring obstacles to data recovery work. A hard drive with a firmware lock can not execute most of the operational terminal commands, can not read system file, can not read out module list, can not recalculate translator, etc., all these will increase the complexity to get user data.
Firmware lock features:
1. Terminal commands can not be executed, there will return “Diagnostic Port Locked” notice.
2. No access to read system file, no access to load module list, no access to read modules, no access to read or write system area, no access to recalculate translator.
Currently, Seagate hard drives with firmware lock in the market mainly include DM series and LM series, etc.; In MRT software version 22.214.171.124, DM series can be fully supported. In paid software version of 126.96.36.199, firmware unlocking of LM series can be supported, but due to the 4k system area size, there will generate malfunction of memory buffer; although it can get access to system area after unlocking, but it can not read/write modules and system files just like DM series.
It is just because the hard drive can not read or write system files, so after the operation of recalculating translator, it will generate the malfunction of user sector access interruption due to some unnecessary defect entries in 0x35 system file in system area. This problem is a hard nut in data recovery industry. Once a “user sector access interruption” problem has been created, there is no way to repair. Previously, we can only try to backup system files to avoid and restore the hard drives to the status before recalculating the translator, but this method can not really solve and fix “user sector access interruption” malfunction.
Fortunately, in MRT latest software version 188.8.131.52, we solved the buffer problem. Now hard drives can normally execute all terminal commands, normally read and write modules, access system area normally, execute all factory operations normally.
Simply click one button to unlock:
Click ” Firmware unlock”
When it shows the notice of “Mrt Loader” in terminal interface, power off and on, then click “Exchange commands”
After the firmware lock was unlocked successfully, the software will automatically exchange commands. However, a manually click on “exchange commands” button is needed after power off and on.
After successfully exchanging commands, hard drive will be ready, we have full accesses to system area, to execute all terminal commands, to read and write modules, to recalculate translator.
What’s more, in our latest software version 184.108.40.206, we add the support of virtual start of new families of ID55（LM010），ID81（LM033, LM034）,ID87（LM028, LM030），ID8C(LM007, LM035、LM048), IDA5(LM035, LM048).
Virtual start is a new function released by MRT Lab in the year of 2017, which is a unique function among professional data recovery and disk repair tools. We can try to use virtual start to fix these mentioned LM series when they encounter the following problems:
(1) SA was formatted by mistake and the drive broke down. You can use virtual start function and write firmware back. As is known that it is not possible to recovery some Seagate drives if the firmware is formatted. Now the MRT Virtual Start is the only solution for this problem.
(2) The drive couldn’t operate any commands or enter T level. We used to use short circuit to solve it, which often fails. Now users can try Virtual Start. If succeeds, the drive will be able to enter T level.
(3) Fake readiness. The drive seems ready but can not operate any commands, the capacity is shown as 3.86GB, and users can not get access to user data. If Virtual Start succeeds, the drive will be truly ready.
Thanks for your support to MRT.
Please contact technical support if you have problem with this function.