Macbook won't load OS. Reinstalling macOS and replacing the drive doesn't help. What to do?

Question

macbook

I have a MacBook Pro 13 "Mid 2012.
A year and a half ago I installed a Kingston v300 120Gb SSD on it. It
worked fine for half a year, then at some point it suddenly started to hang like hell (for example, loading the OS at startup 25-30min). Pulled out the SSD, checked through SSDLife, showed 100% health and many years of service.Next,
an interesting point - Ubuntu (Mint, Gnome, etc.) took off with a bang and worked on it.Mac OS X did not want to be put into any, then refusing to format the disk itself, then crashing during installation with an error something like "File system error". At the same time, in order to format an SSD in HFS +, you had to first format it in FAT32 (otherwise it would crash with a read \ write error of some random sector).
But with ordinary HDDs, it I was friends normally and the rest of the time I spent with WD Blue on 500Gb.
A week ago, when loading, he showed me a crossed-out folder. Googled - demolished the OS - installed a new one - the effect is the same. My first thought was that the HDD had died. Delivered new WD Blue on 160 Gb - the same effect. Moreover, showing the duration of the installation of 17 minutes, he set it for 1-1.5 hours.
The second thought is a "crooked" installation flash drive and I decided to install Ubuntu again, at least for a while, since the laptop is very necessary. But, even though she got up quickly and without problems, and I was given a Grub window at startup, my poppy also does not want to run it, giving an error:

error: attemt to read or write outside of disk 'hd0'.

and offering to press enikey.
The error crashes on both SSD and HDD.
Important points:
1. All SSDs and HDDs used are healthy, tested by SSDlife or HD Tune and installed Windows on them on other hardware (respectively, with normal flight).
2. Secure Erase was running on the SSD.
3. Memtest86 found no errors.
4. The built-in "Apple Hardware Functional Test" did not reveal any problems.
5. Resetting the battery and SMC did not help.
What could be the problem?
Did any controller fly or is it my crooked hands and am I missing something?

Answer 1

Probably a problem with the cable or controller