If you’re lucky, you might even find one of these. As previously advised, I use FIT. I can’t spoil anything as I just feed it and share.
2 Likes
@westlake If you run those files through MEA again it’ll show you the CSME and the still included/ not removed IUPd. Check for the given length and search in a hex editor for the IUP name, mostly PCHC and PHY.
They should always start at 0x*00. Just delete the given length. MEA should now show just the CSME.
Had this for the first time for CSME 14, too. Maybe the tools are getting too old?
I’m not interested enough in this topic to bother with it. Pluto hadn’t said they were problematic, so I assumed they were suitable. I don’t mind if others share it, perhaps in a more digestible form. You’re dealing with it anyway, so I’ll get out of your way.
That wasn’t at all the meaning! I have little time to search, so I’d appreciate it very much if you could post your results as before 
1 Like
As correctly stated, some FIT versions behave weirdly/badly. This thing with IUPs being left behind after grabbing the region file from the “decomp” folder (but not referenced at $FPT anymore - clearly a FIT bug) has existed at FIT 14 and 15 I believe (definitely 15). And FIT 15 is additionally very weird with what SKU you select at the top before loading something into it. We can’t do anything about these behaviors/bugs.
Again, as correctly stated, it is a matter of manually cleaning those uncharted/leftover IUPs to have a cleaner final image to use as base for stitching with IUPs.
Another thing with CSME 15 (I think not 14 or older but don’t remember anymore) is the “FITC” partition which holds the configuration (thus MEA shows Configured vs Unconfigured). That one can be cleaned manually by replacing its contents with FF and modifying the $FPT header to remove the FITC partition size but not offset (otherwise FIT 15 crashes for whatever reason).
In general, these are boring crap that have to be done in order to keep as clean EXTR firmware as possible (when we find those which already come stitched with IUP and/or configuration from OEM).
6 Likes
CSE_ME_11.12.97.2614_ConH_KBP_BSF_GCF-H_A_RGN.zip (1.3 MB)
CSE_ME_11.12.97.2614_CorH_KBP_BSF_GCF-H_A_RGN.zip (4.2 MB)
4 Likes
I think I figured out what the reason is, FIT 15.0.23.1706 you’re using is too old for decomposing these ME-updates
1 Like
11.22.97.2675_COR_H_BA_PRD_RGN_C3059875.rar (3.9 MB)
12.0.96.2562_CON_LP_C_PRD_EXTR_D0649D1B.rar (1.6 MB)
If I understand correctly, the problem is only with the 15 series files (too old FIT), right?
2 Likes
FIT 15 is the worst for sure and no, it used to happen with older FIT 15 versions which were on par with the (then) equivalent CSME firmware, so it’s a general FIT 15 issue which persisted. Don’t know if Intel fixed those in newer versions, but somehow I doubt it.
1 Like
Could you share which vendor’s BIOS is 12.0.96.2562_CON_H_BA_PRD_EXTR.rar? Dell? Lenovo? HP?
can I flash it on asus Z170-A ?
thanks.
Some packs of newer tools (only FWUpdLcl + MEInfo for EFI/Linux64/Win32/64) with a bit older FW’s:
ME_Update_Tools_11.12.96.2549.rar (9.1 MB)
ME_Update_Tools_11.22.96.2610.rar (7.6 MB)
ME_Update_Tools_12.0.95.2495.rar (8.5 MB)
3 Likes
Would these work for updating 11.8 firmware?
THESE??? Guessing wizards now???
If SKU is 10.8 based, these are the ones to use, not 11.x ramdom.