Here, try new fparts again, I added specifically your chip ID
http://www.filedropper.com/newfparts

With your mod BIOS flashed, and it fails with new CPU. Put back in old CPU while that BIOS still there, and run dump the BIOS again.
Then check that dump with UEFITool, extract the ME region, and then open in FIT and see if that bit is set to yes, then you know your ME is flashed into the board.
Before you open to check ME from dump in FIT, make sure you delete all old files and logs settings etc from the FIT folder (only remaingint FIT.exe, newfiletmpl.xml, and vsccommn.bin) before you open the new ME Dump in FIT again to check setting is same as you set.

I didn't use the Xeon, it was with the Celeron. PC turn on and them off... on and off.

So i flash back to the bios that was working with FD unlocked. Still give me same error with the new fparts, don't know what is happening, DOS version works fine.

This is my current Meinfo:

Maybe try meinfowin, not x64 version, in windows.

If PC doesn't start with ME mod BIOS, with Celeron, then there is an issue with the ME and or ME+BIOS mod method.

Post here, link to the working BIOS you have now, and tell me the ME version you want included and I will do the mod and you can test that to see if same outcome or not.
Is that shown above, the ME version you want to modify 11.0.0.1180 H? If yes, OK, send BIOS you are using without ME mod and I will modify the ME and insert it.
Then you program to your BIOS with programmer, no flashing BIOS only programmer for now so you can be 100% sure everything you want is flashed onto the chip.

So mu current working BIOS is version 2.20 with FD unlocked, just like Meinfo shows above. Meinfowin show the same result as the 64 version. Here my current working spi.bin .

Maybe the flash rom is mislabeled or cheap knockoff? I saw some thread about that when looking up the number you gave.
Also, I see in MEInfo above, you have two flash roms on this board, or is that some error?
SPI Flash ID 1 EF4018
SPI Flash ID 2 Unknown

Maybe that is why some error with fparts.txt, since correction I made and then addition didn't help? Maybe @ plutomaniac can advise about that when he has little bit of time to check

I will do BIOS mod with ME tonight manually and then you can try, if it fails then either two things I can guess
1. This version ME is not valid for this type mod (May need older or newer)
2. This mod just doesn't work with this board/BIOS.

That is what is label on the chip. It is just one. I may be doing something wrong, i don't know, but windows version is giving me that error, DOS version on a USB boot drive it works fine. I think is this board/BIOS. I could try with the newer BIOS, ME version is 11.6 some like that.

I know, I was just saying when I looked it up I saw some talking about fake chips or labeled wrong knockoffs etc. Probably not the issue here, but mentioned in case it might be.

Try ME random version isn't going to help. We need to find from confirmed working boards that people did mod on, what exact versions of ME they used and why.
I'll get you test BIOS made tonight, maybe it will work better? Maybe I do one more thing you miss, or maybe I do differently and it works, we will see and hope it will work!

I update the BIOS for version 7.20 which has ME version 11.6.0.1126 and them change the setting Reserved to YES on FIT, flash the mod bios and now it boot with Celeron but no with the Xeon. With the Xeon it turn on for 1,2 sec and turn off try turn it on again it powers on and them off very fast.

Maybe not good ME version for this. Do you already have Xeon microcode in the BIOS too? I'll get you mod BIOS tonight when I get home

mCode is Revision C2 which i think is the newer for Skylake. But i don't think that the mCode could be a problem.

If microcode is not in the BIOS at all, yes that is major problem and will never work. I will check... it's there in stock BIOS C2-2017 as you said, so no issue there unless ES/Confidential CPU sample.
CPUID 506E3, but 2016 version 74 is in 2.20 BIOS, should be OK but can be updated, maybe later if get working, or maybe later to modify these test BIOS again to ensure old microcode is not stopping this from working.

From that first link thread you gave - Use the E3 V5 series CPU method on the H110 B150 Z170 motherboard.
He said tested Asrock ASRock B150M Pro4 Hyper BIOS 1.1 and 7.0, I checked 7.0 BIOS and ME included in that is 11.0.0.1191 which is close to first BIOS and ME you were using 11.0.0.1180, that you sent SPI dump from above In post #20

See here also, post #8, he (Different user @htpcfans ), says ME must be 11.0.xx or it doesn't work
Use the E3 V5 series CPU method on the H110 B150 Z170 motherboard.

I will modify this SPI Dump 2.20 you sent and original ME for #1 test, then I will use 11.0.0.1191 in same BIOS SPI Dump. - link posted below, please test as outlined below otherwise it may give false failure.

Then I will make second set of test BIOS for you 7.20 BIOS w/ 11.0.0.1191 and 11.0.0.1180 ME

@Fileko - here is all BIOS, and ME files I made for you. Please do not mix-match the plain ME regions with different BIOS versions, they are configured differently with each BIOS version.
So if using ME only I sent, keep them separate, ME from 2.20 folder only use with 2.20 BIOS, same for 7.20 ME only with 7.20 BIOS

Contains 4 BIOS and 4 ME Regions + Copy of your unlocked descriptor (FD). Don't forget, you need to correct your LAN MAC address in GbE as mentioned below
http://s000.tinyupload.com/index.php?fil...227292085156119

The 2 x modified 7.20 BIOS may not work, since I changed ME from 11.6 to 11.0, try those two last

After each BIOS Programming test, while you are programming the BIOS, unplug the motherboard power supply from the wall and remove the CMOS battery for 1+ minutes, while that is unplugged also press the power on button for the board/case a few times.
This is to drain all power from the board, and reset ME state. This must be done every time you reprogram or change ME at all, otherwise it can fail to boot due to ME state.
Sometimes removal of one memory stick to "change things up" can get boot going too if it still fails to start, always try that once too if boot fails after ME reset.
Normally, if not using a flash programmer you would want to use the fpt.exe -greset command every time after ME reprogram, but draining power like mentioned above while BIOS chip is off board will do same as long as power is fully drained for over one minute

Few questions, aside from all this BIOS. Are you sure your CPU works, it's tested on another board by you personally to confirm it actually works?
And, is this CPU ES/QC/Confidential, or retail CPU? This in regard to microcode, ES is different than retail (506E0/506E1) and they are not included in your latest BIOS by default (they are in older 2.20).
If CPU retail (Stepping SR2CP or SR2LF printed on CPU) then no problem, if it's ES (stepping QJ7A) then we need to add that microcode to BIOS, otherwise it would never boot on any board without that microcode.
If you are not sure, please post an image of your CPU so I can check label info on top.

Creating BIOS x 3 now, please refresh page if you are reading this and don't see download links above. It will take me some time, but keep refreshing to look back at this post, I will add links here.
I see LAN MAC Address in your original dump above is invalid 88:88:88:88:87:88 - sticker w/ correct info should be on LAN Port or on board maybe on 24pin or PCIE slot top/bottom side, or other board sticker.
You can edit via extract GbE region in UEFITool, edit correct on in with HEX, then reinsert in UEFITool and save image

Thanks for your support. Will test your BIOS later. I don't know if the Xeon work, i bought new, box sealed, but could be dead. Unfortunately i don't have a E3 V5 ready board to test. It's a retail CPU(SR2CP).

First test whit the 2.20 BIOS ME 1180. No boot PC keep restarting turn on fan spin for 1s and them off keep doing that.

Test two: Success! 2.20 BIOS ME 1191 boot with Celeron and Xeon E3 1270 v5. Now i have to see if BCLK OC will be possible. I wanna thank you, thank very much for your support, it was the ME version.