Initially it said that it was for PCH-H and I wrote a reply telling them that they are wrong. Even the filename says Consumer LP (not H). When it comes to ME I suggest you check this thread for updates or if Station Drivers finds something first, check if it was uploaded by Pacman. He knows the difference between H and LP and wouldn't confuse them.

I am more surprised by the fact that FWUpdate allowed you to continue with the flashing. So your system was operational, flashed 1191 LP with FWUpdate and then bricked? If yes, I wonder if Intel does any basic testing before releasing these tools. That would be the third important FWUpdate bug we have discovered.

In order to restore the previous chip you can do a "hot swap" as it's called. Boot the system from a working chip, have the flasher ready, remove the good chip and replace with the corrupted on the fly, flash on the corrupted chip and you are good to go. Two working chips. Note though that in order to replace the ME region your flash descriptor must be unlocked, otherwise a cheap external programmer is the best way to repair the corrupted chip.

Lovely, so FWUpdate doesn't perform that basic check. I will add a warning at my thread to hopefully avoid such an incident in the feature. Who knows, even I might one day accidentally upload an LP instead of H and end up bricking a bunch of people's systems.

Well search google for the best way to do a "hot swap" and whether it's not really a good method. I know it works but maybe it can cause a short circuit indeed on some cases. Sorry, no experience other than the one time I did it for me years ago.

The SPI chip has some regions inside (Descriptor, ME, BIOS, GbE etc). The Descriptor controls the read/write access to/from regions. In contrast to BIOS, the ME is usually not allowed to be overwritten or tampered with. If the other regions don't have access to it the descriptor is "locked". Any software flashers (some exceptions apply such as FWUpdate, certain in-BIOS flashers etc) rely on the descriptor so only if it is unlocked are you able to rewrite/replace the ME region. To check quickly if it's locked you can run Flash Programming Tool with the command fptw64 -d spi.bin. If it reports Error 26, it's locked. Otherwise, unlocked. But of course that requires an operational system.