Please, help - I have 2 x ST2000DM001 drives - one is still fully working, the other one bricked/broke the usual way discussed in many threads here (I wish I knew those drives are so bad and basically prone to developing such Firmware defect).

So, on the still working drive I have no problem to access the terminal mode and get "F3 T>" prompt, i.e. I know for sure my RS232-to-TTL adapter and cable are good. However, on the broken drive, immediately after I get the "F3 T>" prompt it gets like disabled by the incoming messages and effectively I cannot get "F3 T>" prompt - please, see the attached screenshot - I marked with Red the moment when I get "F3 T>" prompt for a very short moment and then immediately it gets disabled.

I hope someone here can help me how exactly to get "F3 T>" prompt in such situation. Thank you!

OK, it turned out the solution is to short the so-called "read channel" - those are 2 points (technically VIAs) on the PCB and you short them during or after you see "Spin Up" massage on the terminal - it's a little bit tricky, but I can confirm it works - so basically you keep practicing until you get it right. Two very important notes:

* the 2 points on the PCB for ST2000DM001 drive that are the "read channel" and that you need to short you can see in this video:

https://www.youtube.com/watch?v=OEiEehGyvZU

it's in Russian and I don't understand Russian myself, that's why to avoid any confusion I also made Screenshot and I am attaching it to this post of the 2 points that need to be shorted

* It it very important to use Tweezers to short those 2 points - I don't know why, but Initially I solder 2 wires to those 2 points to make it easy for me to short them - but that messes up the work of the whole logic board - I guess the wires add some Capacitance or something like that and that makes the board not possible to power-on/start-up properly. So, the only way that works is to do it with Tweezers.

Now, I can get Terminal, but so far - no fix, because I have " MCMT PRI copy corrupt" I did:


and after that:

followed by: