@vuze4u - a link to stock BIOS or dump you are modifying would help, without that we can only guess. Also, note what version ME you are trying to put back in, so we can test the process and see if it's a bug, or something is wrong etc.

@Lost_N_BIOS - Hi i have included Stock OEM BIOS (target BIOS for modding), SPI dump from my board for reference and the modded BIOS (also serviced with UBU Tool) in attachment.

My mainboard is GA-Z77-D3H revision 1.0, the ME version on stock BIOS is very old and i'm replacing it to 8.1.70.1590_1.5MB_PRD_RGN.bin among with OEM ICC Profile etc migrated.

The modded BIOS with OEM settings verified fine with UBUTool, UEFITool, ME Analyzer. But one different show in UEFITool is the Flash Descriptor with ME and BIOS regions offset swapped and it's done by FIT:

-Modded-
ME region offset: 601000h
BIOS region offset: 1000h

-Stock OEM/SPI Dump/Other Modded BIOS from someone else-
ME region offset: 1000h
BIOS region offset: 200000h

Only the BIOS built with FIT can decompress properly (6MB BIOS Region and 1.4MB ME Region). All the stock/SPI/other 3rd party modded BIOS can't decomp right and i suspect it has something to do with that BIOS Region offset being at 200000. But i think it shouldn't be a problem for the system BIOS right?

--

@plutomaniac - Many thanks for the info, glad to hear UEFITool can extract the region correctly because i have zero knowledge on how to edit that offset, let along the method to do it.

Even with plutomaniac's advice I can't figure out how to fix that offset!? Maybe because it does not need fixed?!
line 40 = 00 00 00 00 01 00 00 06 01 06 ff 07 ff 1f 00 00 >> 0x44-46 = 01 00 00 = correct BIOS region offset per UEFITool and hex-view, due to however the file was modified incorrectly?

I tried 10 things, and stared at it and the stock BIOS for about 20 minutes, seems simple and it probably is, but I'm missing seeing something.
However, looking at the actual BIOS in hex, I think it's compiled wrong and you should start over, no matter what FD shows / how UEFITool parses things, the actual BIOS region code starts at 1000h in your mod BIOS.
Meaning, BIOS is actually above ME in UEFITool and that is correctly shown in UEIFTool due to how it's laid out in the BIOS you modified. I would start all over, making sure this doesn't happen, stock BIOS is not like that so this happened during something you did when modifying.
Probably whatever you did when you extracted region and replaced maybe, you put above ME. And reducing BIOS size (?) probably didn't help either.

@vuze4u - So, anyway, after all that, the simple way comes to mind. I took stock BIOS, extracted your modified BIOS region and modified ME region and replaced in stock BIOS, problem solved.
https://www.sendspace.com/file/6wudhy

@Lost_N_BIOS - Yeah the region offset thing is done by FIT and i couldn't figure a way to force build ME on top of BIOS, thought it may cause problem but couldn't be sure of myself, i tried edit .map file in the decompressed folder but after restarted FIT the .map file was regenerated, not reused.

So many thanks for the assist LOST_N_BIOS and this awesome detailed guide plutomaniac, going to test the ROM this weekend! :D

But that wasn't the issue plutomaniac, at least not the one I was stuck on for a bit and trying to solve I got what you said right away, no problem understanding that.
Check his mod BIOS, that's what threw me, trying to fix that based on what you said. BIOS region is physically above ME, starting at 1000h in hex ( and correct / same UEFITool BIOS region offset)
Changing what you mention would not fix his issue in that mod BIOS, you'll have to look at the BIOS in hex and UEFITool then you'll see what I mean.

As for stock, I think it was OK as it was, maybe helped cause the original issue, not sure, and could be corrected how you mentioned if that's what caused the ME/FITc issue initially, but that would need done before the mod not after due to the BIOS layout and what he did with size changes, region extract/insert etc.
It was a mess I've never seen before, but figured out how to fix later with region extract from his mod and insert into stock layout again.

I know I should have, but was initially trying to fix his mod since he did other changes too, so he wouldn't have to start over

I redid the entire ROM from scratch following plutomaniac's hex guide before load it to FIT, resulting difference in xml value is the RegionOrder:

Untouched stock rom decomp: <RegionOrder value="1234"/>
Hex fixed stock rom decomp: <RegionOrder value="2134"/>

That is what caused BIOS(region1) on top of ME(region2) before and i have no idea not editing the offset can cause that. This tiny fix can save unforeseen issues down the road for other bios modding, really dam the OEMs for not doing this. :|

-Edit- Flashed and did CMOS reset etc, USB mouse behaves little different maybe due to the new CPU microcode i inserted, but overall system is stable.

Good all is working now! I've never had that issue with Gigabyte BIOS, do they do that all the time Plutomaniac? If yes, why only now am I seeing this issue presented, only certain versions of FITc react badly with it, or maybe I just have not redid ME with FITc on enough Gigabyte BIOS to notice?

@Plutomaniac. I really appreciate your detail instruction on how to clean the ME region for the dummies like us to understand. I was having hard time getting the Mac files cleaned when the CSME and TXE came along with different layout and I had to read your instruction a few times until I understand it 100% before I touch the programs. If I did not, I am sure I will screw up big time.
Now I got the MAC firmware with no hassle or hoops to go back and forth like before and I greatly appreciate your time and efforts to post such long detail with illustrations to everyone's ease.
Kudo! to the guys like you and I hope many do the same to share their knowledge instead of being selfish and keeping all in them.

I will post a video illustration when I get time to do the screen recording and edit the video to efficiently explain. That way, many idiots like me will get to say "Awww. I did not know" lol.

I made a poor instruction video for many to be able to see how it really works. I am not a professional guide nor video producer so I tried my best, Took me a while to figure out how to record the screen and it still have issue. Here is the link for easy check. I made the video with ME 10 for Mac since that is all I am working all time.

https://youtu.be/aytG-V1SOZk

hi guys!
please help me clean Me file bios . HP probook X360 11 G1 EE thanks so much !!!

bios bin HP probook X360 11 G1 EE . https://www.mediafire.com/file/jnundn36x...ook_PC.bin/file