read the first post and follow the tutorial or download the flash-ready fw you desire to update to (some people bake it and release it on station-drivers for example) and just flash that.
Help ME firmware, 16.0.10.1473
Alder Lake & Raptor Lake ME FW v16 update
New PHY ADP N firmware version 13.61.211.7254, since MEA r331
2 Likes
2 posts were merged into an existing topic: Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)
A post was merged into an existing topic: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
hello please other link
CSE ME 16.1.30.2255 Consumer H
PHY 13.62.211.7255 Production, Engineering ADP N
ME_Intel_v16.1.30.2255.zip (2.2 MB)
https://www.elevenforum.com/t/firmware-intel-me-h610-b660-h670-z690-b760-h770-z790.11362/
2 Likes
CSE ME 16.10.5.1583
PMC 161.2.00.1040 Production Independent H A ADP
PCHC 16.10.0.1012 Production Independent ADP
PHY 13.0.1.7083 Production, Engineering Independent S ADP
1610.zip (3.6 MB)
(Not sure what this is, but I don’t think it was mentioned yet?)
1 Like
This is 16.10 firmware from Intel W790 Xeon Sapphire Rapids plaform (LGA 4677).
As 16.50 firmware that I posted earlier, it is not supported by MEA and will not be added to its database, as Plutomaniac said. So i think there’s no need to post them.
I don’t have that archive, it was already added to DB, no chance i’ll post it again, I doubt you need a bunch of preproduction firmwares. If you need something specific from that list, just ask exactly what you need.
1 Like
True, there won’t be MEA support for these and also not included in the DB. However, I believe that it’s good to be posted/attached/kept somewhere in case someone wants to look/use at these firmware. Personally, I try to keep most of these new binaries in bulk (w/o any processing), just in case.
Good afternoon everyone!
Please help me find CSME System Tools 16.0.15.1735.
I will be very grateful.
hi .
my old bios backup gives an error on me analyzer.
“Error: Detected CSE Extension 0x16 with wrong Partition Hash at FTPR > FTPR.man!”
cs me version is 16.0.15.1662 anyone have you got , can you share?
Hello,
I am using a CLEVO NP70PNJ (NP5x_NP6x_NP7xPNK_PNH_PNJ).
The latest BIOS I found is version 12 with the following details:
BIOS Version: 1.07.12
KBC/EC Version: 1.07.07
ME FW Version: 16.1.25.1865
The problem is that even this latest ME firmware is vulnerable (CSME-Version-Detection-Tool). 
CLEVO, of course, does not respond to any messages and is not very responsive. 
Thanks to a user’s sharing on this forum, I found a more recent ME/FW update on Station-drivers.
I’m just very concerned about bricking a brand new PC, and I would like confirmation that upgrading from:
ME version 16.1.25.1865 to ME version 16.1.27.2192 as shown in the image below won’t cause any issues? (the difference between in yellow)
I’m asking because, based on the message at the beginning of this thread, it’s dangerous to change the ‘Version Control Number’ or, worse, to switch the PCHC from 16.0.x to 16.1.x , differente total bits size … 
And, most importantly, even if I make a backup with ‘fptw64.exe -ME -D actualFWME.bin’ , if I brick it with a bad flash, I won’t be able to flash back the backup since the PC won’t boot anymore. 
In summary, I need a specialist 
to confirm if it’s safe to flash the image above.
Thanks !
Edit: I see that if I perform a backup, I have “Initialized” in the File System State, which would be normal because it comes from an initialized system. Therefore, it is logical that the file to be flashed should be in File System State = “Configured” I suppose because DATA has been cleaned up. Note that all this speculations are based on what I understood from the second paragraph “A. About Engine Regions & Configuration” from the first post in this thread.
Vulnerable to what? Millions of people use computers with outdated ME firmware and who cares.
It’s unlikely that you’ll brick it with an update, but there’s always a chance that something won’t work correctly. It is only safe to use updates provided by your laptop manufacturer itself. If you are so concerned about ME vulnerabilities, maybe you should use a laptop with disabled ME.
Hello Anton35,
Thank you for your response.
It’s not really a concern about ME vulnerabilities that drives me to update the firmware; it’s more of a thorough, perfectionist approach. I completely agree with you that outdated ME firmware is probably widespread and not a significant issue for standard regular users like me.
However, the problem will be quickly resolved: I’m getting error 369: failed to verify the signature of OEM or RoT key manifest. For example: Error on update from Production to Pre-Production, which confirms that the easiest solution is indeed to use the updates provided by your laptop manufacturer itself as you suggest. It’s just that Clevo is not as reactive as Asus or Lenovo…
Edit: Currently testing this
Final try: a Frankenstein 
!
Don’t worry, if this attempt fails, I promise to continuing my experiments on my own and stop spamming this thread with my tests.
Well, edit above can’t seem to resolve the error, so I’m going to use the explanations from the first post at the beginning of this thread to create my own firmware.
This will be a change from those who ask without trying anything. I’m sharing.
What I’m doing here in case it can help someone.
1/ I Mfit.exe decompose an Original BIOS provided by my manufacturer and compare it to my own saved BIOS, which theoretically should be the same.
2/ I notice that ME Sub Partition.bin and CSE Region.bin are different between the BIOS I’m given and after it’s flashed.
3/ Thanks to the explanations by system at the beginning of this thread, I understand that the difference is normal because ME Sub Partition.bin is “Initialized” by the system after flashing its virgin “Configured” version.
4/ Still, thanks to the explanations by system at the beginning of this thread, I understand that I will need to create a Clean Firmware in “Configured” mode.
5/ CSE Region.bin is, therefore, different between the BIOS I download and its version that I flash on the system because the PC has “Initialized” this Region.
6/ By comparing the manufacturer’s BIOS with the available update★ for my configuration (LP Consumer (ADL) A1), I notice that I need to update:
(★) I would have preferred to build from scratch using each available piece from an MEA db from Anton35 , but the link is dead.
01) ME 16.1.27.2192
02) PMCP 160.1.0.1029
03) IOMP 36.6.0.0
04) NPHY 14.530.509.8258
05) TBTP 16.0.0.1901
06) PCHC 16.1.0.1014
7/ I launch Mfit.exe and follow the instructions from system at the beginning of this thread:
Select Intel(R) AlderLake P Chipset - FWUpdate
Flash Layout ➜ Ifwi: Intel(R) Me and Pmc Region 
Intel(R) ME Binary File
[ME Sub Partition.bin] = the new 01) from ME_16.1.27.2192_A0_Origin.bin
Flash Layout ➜ Ifwi: Intel(R) Me and Pmc Region PMC Binary File
[CsePlugin#PMC.bin] = the new 02) from ME_16.1.27.2192_A0_Origin.bin
Flash Layout ➜ Sub Partitions ➜ PCH Configuration Sub-Partition PCH Configuration File
[CsePlugin#PCHC.bin] = the new 06) from ME_16.1.27.2192_A0_Origin.bin
Flex IO ➜ TCSS Configuration NPHY Binary File
[CsePlugin#NPHY.bin] = the new 04) from ME_16.1.27.2192_A0_Origin.bin
Flex IO ➜ TCSS Configuration IO Manageability Engine Binary File
[CsePlugin#IOM.bin] = the new 03) from ME_16.1.27.2192_A0_Origin.bin
Flex IO ➜ TCSS Configuration Thunderbolt™/USB4™ Binary File
[CsePlugin#TBT.bin] = the new 05) from ME_16.1.27.2192_A0_Origin.bin
ISH (it’s not in the original BIOS, so I’m not putting it)
UTOK (they are identical, so I’m not touching them)
BONUS to try to counter the error 369 above:
Platform Protection ➜ Hash Key Configuration for Bootguard / ISH OEM Key Manifest Binary
[CsePlugin#OEM_KM.bin] = That of the original manufacturer’s BIOS
8/ I’m a bit afraid to flash this Frankenstein I’ve created, even though it’s actually just an ME_16.1.27.2192_A0 from here with an OEM_KM.bin from my original BIOS as a replacement.
.
EDIT ▶ 🎉 Did it! 👍
I created something with Mfit.exe by simply removing the OEM and ISH bin files to avoid signature issues like above.
But I’m not going to spam a another lengthy explanation that annoys everyone here about update Intel ME on Clevo that probably only affects a few people.
In fact, everything is in the first post.
For Clevo NP70PNJ Only and to update to:
FW Version : 16.1.27.2192 LP Consumer
PMC FW Version : 160.1.0.1029
IOM FW Version : 36.6.0.0000
NPHY FW Version : 14.530.509.8258
TBT FW Version : 16.0.0.1901
PCHC FW Version : 16.1.0.1014
Flash this :
FWUpdLcl64.exe -allowsv -f FWUpdate.bin
FWUpdate.bin ➯ WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
1 Like