Is it possible to know which exactly ME revision to use by looking at the chipset and CPU?
I have broken motherboard, BIOS is corrupted, I cannot read it, but I know which chipset and CPU are on board. Is it possible to know which ME to use based on those 2 chip on board?
For example I have:
SR2CE and it is Intel GL82CM236 chipset - Skylake
Intel® Pentium® Processor G4400T
From HP website for this PC when I extract ME Firmware update, there are these 2 types:
The HP FW update file (Usually for several same based models) will determine the sku on the motherboard and flash the correct one, LP is Low Power systems/tiny models/laptop etc… H is usually standard systems sff, mt models, you should try to identify the motherboard with more detail or try to dump the corrupted spi and check any details still visible.
By the way how did you correctly identified the HP ME FW SPxxxxxx package…since you dont know what machine you have???
Thank you both for your kind words. I’ll admit that I have decided to mostly stop doing this kind of updates myself in the near future (i.e. looking at “sources”, extracting, identifying new stuff, preparing, storing, packaging, posting etc.) and that’ll probably extend to MEA and MCE. It’s too much work, time (and mental) wise, and after 8 years of doing this, I’ll look into spending more time on other things. In time, I will help others who might want to pick up the mantle (at least for the sourcing/“crawling” part) by sharing some potentially useful places to look (from those which are still alive, even the HP FTP seems to be dead now). Anyway, wanted to share that now so that it doesn’t come as a “huge” surprise later on.
It makes perfect sense, I’d be tired of this after a few days, honestly, especially with the amount of silly quiestions you keep getting asked, some of them I have asked myself, lol.
Nah, we can all ignore questions if there’s no will, time or point to answer. That’s not the problem. The entire process to fetch, parse, store, post, update DB, fix/maintain tools, update repos etc is the amount of work I was mainly referring to. But thank you for your support and understanding either way!
If I had the knowledge I would definitely not mind doing all of the above, but given I can barely follow the very clear guides you posted…it would be a $h!t show :))
Depending on whether you use manufacturer UEFI/BIOS flash, then UEFI flash may / may not contain ME region.
Thus with full flash, if you perform CSME then UEFI (most likely as many flash routines force restart as part of the process), CSME is overwritten (not all images contain latest CSME as vendors have usually had the updates some time).
If the CSME is not included in the flash option then it’s possible to do what you suggest.
IIRC older MSI M-FLASH would show a diagram with BIOS or BIOS & ME. I use almost exclusively Gigabyte boards and QFLASH varies by chipset.
Easy way to find out is to drop your UEFI / BIOS image onto MEAnalyser, if there’s no ME region it will tell you.
@plutomaniac Just want to express my appreciation for your work! Got some 2 dozen machines quickly updated to latest ME firmware versions so a big thank you!
I’m looking for PCHC CMP v14.0.0.7002 but the RAR file doesn’t seem to be available on the MEGA download site…
Installing MEI Driver 2214.0.85.0 on Windows 11 produces yellow exclamation mark in Device Manager with Code 52 (digital signature verification problem). Previous version is without that symptom.
Is it just my (2) system(s), or am I missing something?
