I had this same problem. The only fix was to delete the partitions, set the drive from UEFI based GPT to MBR. That was just to save the drive and for it to be usable. I had tried everything just like you. I suspect that MBR protection in a security program may have caused the problem. GPT doesn't require protection, yet there is still an MBR on the drive. I think some security programs may try to protect it, even though it's already protected. So if it's a no write problem for EUFI or something idk, but it leads EUFI to believe multiple mbrs exist. Fixing the problem with MS tools on a GPT drive was not possible for me, just like you. Causes me to wonder if you have the same problem, assuming you have a GPT drive. I you aren't EUFI/GPT I guess you can ignore the rest below. I think you are right anyway. Only reimaging finally worked for me.
Hate to admit it but after going through everything you have been through I had to reimage. Couldn't even do that successfully until all the partitions were removed and the drive set to from GPT to MBR. Image restores wouldn't boot either on the drive prior to that. The disk was useless to me until I tried that change on the empty drive with no partitions.
Think it has to do with the age of the native tools of Windows. Seems mbrfix and the rest aren't capable of fixing a problem on a GPT disk.
If you would like to see what kind of disk you have, there is a very good free program that you can use to change from GPT to MBR and so on. It's called Active Partition Manager and can be found here:
http://www.pcdisk.com/download.html
It's also on Major Geeks if you would rather get it there. It saved my bacon. I had already reinstalled even though I had good images, because the images wouldn't boot either...just like the failed OS boot. That made no sense to me, but I remembered that I had the same problem before, and I bought a new disk to use that time. That image worked. So, this time, I found Active Partition Manager and saw the drive was GPT and thought, "OK, probably the new drive that worked last time was MBR." I decided to use the ability in the partioning program to change from the native GPT to MBR. Then restored images booted again but only after I deleted all the partions and did the conversion. Just converting the black screen OS installation drive full of data from GPT to MBR meant the same black screen. Weird, especially since the images restore the drive to GPT.
I think you might have this same problem. Seriously, it was the exact last thing I was going to try. I guess you don't have a good image backup though from the sounds.