Intel (CS) ME, (CS) TXE, (CS) SPS, GSC, PMC, PCHC, PHY & OROM Firmware Repositories - Intel Management Engine - Win-Raid Forum
Intel (CS) ME, (CS) TXE, (CS) SPS, GSC, PMC, PCHC, PHY & OROM Firmware Repositories - Intel Management Engine - Win-Raid Forum
HOSTED BY LEVEL1TECHS
Note: To extract the files below you need to use programs which support RAR5 compression!
Collecting all available Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM
firmware is important for research on how the general technology works, for creating universal tools that
can help people understand what firmware they use, for developers with no Intel representative who want
to experiment on a given platform, for downgrading purposes etc.
All Intel Engine, Graphics, PMC, PCHC, PHY & OROM firmware at the repository have some
common attributes and are categorized based on them as follows:
Every Engine & Graphics firmware Version tag has a Major, Minor, Hotfix & Build number. Example:
ME 8.1.40.1416 has Major 8, Minor 1, Hotfix 40 and Build 1416.
Every PMC CNP+, PCHC, PHY & OROM firmware Version tag has only a Build number. Example:
PMC 300.2.11.1011 has Build 1011.
The SKU of each firmware, when applicable, depends on the platform generation and is usually
distinguished based on supported features (Consumer H/LP/N/V/1.5MB, Corporate H/LP/5MB
etc).
The Revision is the PCH stepping of a given platform generation and is used to further categorize CSE
& PMC firmware (C, D, B etc).
The Release of each firmware can be Production (PRD), Pre-Production (PRE) or ROM-Bypass
(BYP). You could see these as Stable, Debug & Alpha but there's more to it than that. Only
Production (PRD) Engine, Graphics, PMC, PCHC, PHY & OROM firmware based on
Production Chipset Steppings are included in these repositories.
The Type of each firmware can be Stock (RGN), Extracted (EXTR), Recovery (REC), Operational
(OPR) or Update (UPD). RGN are clean/stock/unconfigured images provided by Intel to OEMs.
EXTR(-Y/N) are dirty/extracted/configured images from various SPI/BIOS. REC & OPR are used
at (CS)SPS firmware. UPD are partial RGN/EXTR firmware regions which contain only ME CODE
without any DATA, used only by older Intel FWUpdate tool versions. To learn more, read Section B
of Intel (Converged Security) Management Engine: Drivers, Firmware and Tools.
There is a certain mentality which is followed in order to structure the Intel Engine, Graphics, PMC,
PCHC & PHY firmware repository properly:
CSME 15.40
CSME 15.0
CSME 14.5
CSME 14.1
CSME 14.0
CSME 13.50
CSME 13.30
CSME 13.0
CSME 12.0
CSME 11.22
CSME 11.21
CSME 11.20
CSME 11.12
CSME 11.11
CSME 11.10
CSME 11.8
CSME 11.7
CSME 11.6
CSME 11.5
CSME 11.0
ME 10.0
ME 9.5
ME 9.1
ME 9.0
ME 8
ME 7
ME 6
ME 5
ME 4
ME 3
ME 2
CSTXE 4.0
CSTXE 3.2
CSTXE 3.1
CSTXE 3.0
TXE 2
TXE 1
TXE 0
CSSPS 5
CSSPS 4
SPS 3
SPS 2
SPS 1
GSC DG2
GSC DG1
PMC MCC
PMC TGP
PMC CMP
PMC CMP-V
PMC JSP
PMC LKF
PMC ICP
PMC CNP
PMC WTL
PMC DG2
PMC DG1
PMC GLK
PMC BXT
PMC APL
PCHC MCC
PCHC TGP
PCHC CMP
PCHC CMP-V
PCHC JSP
PCHC LKF
PCHC ICP
PHY P TGP
PHY N TGP
PHY P CMP
PHY N ICP
PHY S LKF
PHY G DG2
PHY G DG1
OROM DG2
OROM DG1
7 Likes
X9dr7-ln4 intel me
Request for Modded Intel ME Firmware for Lenovo M900 with AMT Support
I have compared it with my collection and while I can say mine is smaller (pun is unavoidable), I had a
few images not present here. All are PRD and EXTR, from what I can tell.
@lordkag
Ha,ha …
I forgot to add this line yesterday: When it comes to Region (RGN) images, Stock ones are more
important. If I have the same version as RGN & EXTR, I will keep the RGN. ME Analyzer can
detect that as well.
Basically if I currently have an EXTR but I find a RGN, ME Analyzer will show it as an update and the
file will be replaced. So you might have more firmware, when ME Analyzer is out you can drag & drop
all of them and just press Enter continuously until you see the yellow warning of a “rare firmware”. Saves
so much time…
Regarding firmware: Thank you for the files, all of them are “new” except from 10.0.32.1000_1.5MB
which was already at the database.
1) I have a free account so I cannot do bulk download. What I like about Mediafire is that it has no
waiting time to download, fast download speeds (not like Mega of course), it allows me to re-name &
re-upload the same package without the link changing, I can view download count etc.
→ I read all the legal stuff over at their website now and didn’t notice any snooping policy. Can you
direct me to it?
→ Your files are not deleted individually based on last download but rather based on last log-in time. It’s
account and not file based. Here:
→ I obviously keep backups of everything I have at Mediafire, I don’t trust online services at all.
→ I would be deeply disappointing by Intel if they pursued this as “sketchy/illegal”. It would be a dick
move since all those files/tools/docs come from legit links all over the internet.
I have been thinking this for some time now. From now on I will try to add a Source link for everything I
find and upload (firmware, documentation, tools etc). Just like quid does at MDL.
2) Initially I was thinking about uploading all firmware in one folder or 11 folders based on major version
and keep all the .bin files visible and individually downloadable. However, that wouldn’t be practical since
I don’t think someone with a free account (no bulk/folder download) is going to manually download 470
firmware images. Then I thought about one ME and one TXE file but the ME one would still be a huge
upload every time. So, creating 11 compressed packages based on major version seemed like a good
compromise. I’m all in for ideas, have you thought of something more compelling?
Mediafire also has Drop Folders. I can set one up, give the link and then anyone can upload new files
there without registering, posting or anything. I had done it in the past for both ME & TXE threads but I
ended up removing them because noone used them. Only once did someone upload a file and it was a
2008 Intel vBIOS ROM, go figure…
I know the difference between PRD and PRE and how to tell them apart, but what about RGN vs
EXTR? One way will be to see the $FPT header and check for a version, but what is the method by
using your script? Check for an “Updated: Yes” message, check for the “FITC <…>” data in “Type: …”
field?
Mediafire doesn’t specifically writes that they will inspect your files, no one will. But I have sent someone
a few months ago some mp3 files, as a test for a software, packed in a rar file. They were deleted faster
than he had a chance to download them, which forced me to encrypt the file, because they actually
looked inside the archive and sent me a message that it was a copyrighted file, with a link on how to
legally purchase them. And it was only one or two, not like I have mass distributed them.
Ah yes, I just tested that option of folder download. Since it is Pro only, then the only option is the
current one, an archive for each main version. I doubt you will find a service that has fast, free, no wait
download, that would also let you download as a folder or individually.
Edited: Using a Drop Folder is not a good option. Some will just upload firmwares that are already
present, without reading the thread first. Others will probably upload what they think is the firmware, but
it can be the driver or anything else. While there may be some that will use this as a way to propagate
spam or malware.
$FPT header is for ME8 & up only. All previous firmware required manual observation by importing
stock RGN, immediately exporting via FITC and checking for stable/universal differences that pinpoint
FITC presence. That’s one reason why the repository is so useful to me. Here:
Personally If I want to upload something like that I add it to a rar file (store, not compressed) and add a
password. Safest solution to avoid file snooping. I’m not sure if Mega allows folder download, maybe.
Stable links are kind of important when you are maintaining threads such as ME,TXE with so many links
on them. Yes, I won’t deal with a Drop Folder. Leaned my lesson previously.
EDIT: Generally, as you will see when the source code is out, ME Analyzer is full of comments to assist
me and others understand how it works, what have I thought so far and how can it get better in the
future.
temroa:
Clean firmware means that it hasn’t been imported to FITC. Obviously, older firmware means older
firmware. You have the latest firmware & driver, nothing else to do.
can you tell me plutomaniac what is the extracted region and stock region and which should be chosen ?
thanks.
Hello
I found a SPS Firmware version that seems to be new (3.0.7.164) might be of interest to some people.
@Pacman
Thank you for the file, indeed I didn’t have it. I have attached below my “collection” of SPS firmware.
Keep in mind that it’s not a repository, the names are probably wrong, inconsistent etc.
Also, ME Analyzer r4 did not support SPS 1 firmware (shown incorrectly as ME 1 firmware). That was
added at r5. Attached below is the .exe for r6 (just replace your current exe). It’s not an official release
but I’m sure it will be useful to you.
Hello
Here is ME 10.0.33.1012_5MB
Note: ME Analyzer was also updated to 1.0.1 because the database is now a separate release. Check
section C of the ME Analyzer thread for more details. There is no announcement there because a) it’s
not important and b) users of the older 1.0.0 r1 have nothing to gain from downloading version 1.0.1 of
the tool. The latest database file (r7) is all that is needed.
Hello
Pacman:
Thank you for the report Pacman and yes, SPS firmware are accepted here as well. The 3 reps (SPS1-
3) are ready but I am not releasing them yet because of the little SPS knowledge I currently have.
Normally SPS needs to be built manually by combining Operational + Recovery so I’m still not sure
whether a Region is needed to be there. In the meantime, all contributions are welcome. More samples
help understand things better.
Note: From now on, the repositories will be updated less often to reduce post clatter and not waste time
packing, posting and uploading single files every day. I’ll try to keep the DB txt file for ME Analyzer
updated though.
In this file there is a new TXE Firmware. I’m not sure if it is 1.25MB or not, but it is for a new platform,
CherryView.
Hello lordkag,
Thank you for the report. I am aware of Braswell firmware. I took the liberty to remove the direct link
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 12/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
(for now) to keep the open source alive. Hope you won’t mind.
The structure of TXE 2.0 is exactly the same as 1.1 - nothing new like ME11 for Skylake-S. The $SKU
is identical between TXE 1.0 1.25MB , TXE 1.1 1.375MB and TXE 2.0 1.375MB.
Are you sure it is Braswell? Because from this link, I see that CherryView it is linked to Cherry Trail and
Broadwell. I know it is just Wiki and not Intel source, but I tend to believe it.
No worry about the link. Although, I don’t think they will block the access, if they didn’t do it by now.
Still, better to be safe. I am almost amazed that SD is posting links to Realtek site with the credentials in
plain text.
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 13/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
Without revealing too much source code, how can you tell it is 1.375MB, apart from the obvious
chronology?
lordkag:
Are you sure it is Braswell? Because from this link, I see that CherryView it is linked to Cherry
Trail and Broadwell. I know it is just Wiki and not Intel source, but I tend to believe it.
Braswell is the successor of Bay Trail M/D (Mobile/Desktop) whereas Cherry Trail is the successor of
Bay Trail T (Tablets). Can we identify from what type of device these SPI images came from?
lordkag:
No worry about the link. Although, I don’t think they will block the access, if they didn’t do it by
now. Still, better to be safe. I am almost amazed that SD is posting links to Realtek site with the
credentials in plain text.
Yes, indeed. The ME11 firmware & drivers were kind of obvious too. Well, I guess it’s best to poke the
beast as little as possible.
lordkag:
Without revealing too much source code, how can you tell it is 1.375MB, apart from the obvious
chronology?
Initially TXE 1.0 had two skus 3MB and 1.25MB. With 1.1 they decided to merge everything into one
sku at 1.375MB. As I said, 1.25MB and 1.375MB have the same SKU. The same applies to 2.0 as far
as I can see. Also, the size is clearly bigger that 1.25MB and almost the same as 1.375MB. It seems
logical.
You are right. I searched for the board corresponding to the file and while I couldn’t find it, I did found
Pentium N3700, which is Braswell CPU.
Using the latest versions of ME Analyzer + Database, I have looked at the ME Firmwares I have. This is
what was labelled as rare:
- 5.2.40.1037 was mistaken as 1.xx FW.
- 9.1.10.1005_1.5M update.ffs is not really a ME Firmware, but an update or such (there are 2 identical
DESC+ME_cut, in fact), found in Intel. I know that Gigabyte is also using this type of ME recovery, with
the descriptor and a small part of ME packed in a ffs. You probably already encountered this situation, so
I’m not saying that you should support it in any way, but it is always best to have all kinds of test samples.
- the rest of the files are normal ME Firmwares.
These are only the Firmwares that were already uncompressed. I still have others packed in exe or
archive, but chances are that you already have them. Still, I will make some time to compare them,
sooner or later.
1 Like
Thank you lordkag for the files and explanation. A lot of ME 5.x firmware were affected by the ME 1.x
bug. The new check will never fail again, I should have tested that before 1.1.0 release. Anyway,
5.2.40.1037 was already at the repository/database and the rest of ME6, ME7 & TXE1 were added to
the appropriate places. ME7 v1 and v2 were identical apart from the source system which was Q67 in
one file and C206 on the other. No worries about the other firmware which are compressed etc,
whenever you have time.
Regarding FFS image, it’s indeed something unique. It has 2x (FD + FPT + part of FTPR region). I’ve
no idea what it’s purpose but maybe it’s there to verify that the SPI ME image is the “proper” one based
on the Recovery. The FTPR region included has it’s own signed $MN2 header and if that’s the same with
SPI then the ME is untouched. Just an idea. Either way, based on the facts above (2 FPT & 2 FTPR), I
have added detection of such EFI FFS extracted images alongside other bug fixes at the latest ME
Analyzer v1.1.1 which can be found at it’s thread with database r12 included.
I have now finished comparing the remaining of the files. This is the content:
- 6.1.30.1074 from a file fw6_1_30_1074.exe, most likely this one.
- 6.2.20.1035 from a file fw6.2.20.1035.exe, probably from here.
- the other three from Station-Drivers packs, named as old.bin and saved before flashing.
Have you looked at Gigabyte type of recovery with the first 512KB of SPI in a ffs file? It is probably
present in all 9 series boards, with DESC+GbE+ME_Cut being stored in GUID 821D110C-D0A3-
4CF7-AEF3-E28088491704. Here is a sample file.
No I did not know about the Gigabyte FFS modules. I looked into them a little bit. They are always after
MERecoveryDxe module and as you said it’s GUID + first 512KB of SPI image meaning FD + GbE +
ME_cut. My previous theory regarding checking whether the SPI ME is untouched was clearly wrong.
Although it could be a thing for 1.5MB it’s not valid for 5MB extracted FFS modules. The FTPR region
of 5MB (first $MN2) starts well after the 512KB mark (even without the inclusion of FD & GbE before
it). So if you extract the FFS module of a ME 5MB SPI image, the resulting file will show nothing at ME
Analyzer as there is no $MN2 at the first 512 (-FD - GbE) kilobytes. I tested this on a Gigabyte B85
SPI image with ME 9.0 inside. GUID is the same of course. Apart from Gigabyte (GUID 821D110C-
D0A3-4CF7-AEF3-E28088491704), have you found other manufacturers with a similar module? From
where is the other module with the 2 FPT and the 2 FTPR for example?
Attached is a non-public release of ME Analyzer v1.1.2 with Gigabyte FFS Module support and DB r13
based on the firmware you provided above. I discovered today that surprisingly the repository has a
very-very small number of UPD images after ME7. For example, the ME 8.1.52.1496 UPD image was
created by my system today. I don’t even have the latest versions of 9.0, 9.1, 9.5 & 10.0. Never noticed
it until now.
It is for recovery purpose, but not really a trusted solution, be it 1.5MB or 5MB. Probably they count
more on the fact that this file has the Flash Descriptor and the FPT header of ME Firmware, just to
check the validity of SPI content, not a true recovery solution. As a proper recovery, we have Asrock
with its ME backup, just that they decided to go on the dark side and lock the user to a specific ME
version. But since Gigabyte already has Dual BIOS and unlocked descriptor, I don’t know the purpose
of this small file.
The other file comes from Intel most likely, since they use this special packaging in .BIO files. You can use
this link or this one to check for similar files. No other OEMs use this method. Asrock’s ME backup is
not part of this list, because it is a full ME, just the container it is different - ME region vs ffs file.
For the ME update files after 7.x, while it is not important for end users, it is rather difficult to gather these
images for repository. Without users saving their old firmware, is there any way to find them?
@Fernando
If I’m not mistaken you have a ME9.1 and ME10.0 system. Can you provide us with two UPD images
from those systems? You need FWUpdLcl -save command for this.
@lordkag
As you said, it’s a lot more likely that they use these for FPT comparison and not actual code. I know
about Intel bioses, I check their site with BIOS keyword often. How did you extract such an .ffs from
Intel .BIO images? I tried PhoenixTool and UEFIExtract but couldn’t get to it after a lot of searching.
Either way, I saw at the file you posted above that the GUID is the same as Gigabyte’s so that made ME
Analyzer integration a little easier. Attached below are the tested .ffs modules as well as ME Analyzer
v1.1.3 which now supports detection of Gigabyte, Intel and Unknown OEM MERecovery GUID. I also
fixed the ffs_warn error and bundled it with DB r14 which has a small name fix (more below). This is
how it looks like:
Regarding UPD images, since neither Intel nor OEMs release them after the ME7 days I thought that the
only way to get them was via FWUpdLcl -save command. However, after some small research I
discovered today that ME8, ME9.0 & ME9.5 can be cut after FTPR and create UPD images easily. As
we both know ME6 used a small $MN2 extra header to sign the UPD image so it’s not possible there
and ME7 can be cut easily after FTPR. I don’t know about ME9.1 and ME10.0 because I don’t have
an UPD image sample to test. It’s important to note that the cutting must be done after FTPR and not at
the first $MN2 section. This last detail is crucial for ME8 which has an $MN2-headed MDMV region
before FTPR.
EDIT: ME8 is kind of an exception, UPD images can be created manually but it’s kind of a hassle. You
have to cut after FTPR and add MDMV to the end as well.
I randomly opened firmware 9.1.0.1110 in the hex editor and saw this:
Seriously Clevo? This was found at their latest SPI image for W35xSSQ/W37xSS Series. How many
systems have they bricked for being careless, I wonder. Anyway, this extracted image turned out to be
EXTR after all so I updated the DB to r14 to address that. Obviously the previous firmware will show as
“rare” at ME Analyzer when loaded but it doesn’t matter if it’s corrupted. I have attached the fixed image
below for now.
EDIT: It won’t brick systems. The fash descriptor points to 0x1000 for ME starting offset so in theory
it’s ok. Not that it makes sense being there.
Having the same GUID as Gigabyte makes me think if that file is indeed from Intel. I know that it comes
from a BIOS file that uses the same packaging as Intel .BIO files, but which one? Anyway, for extraction
I used UEFIExtract using the wrapper UEFIExtract.bat/py from #Extractor.
That’s right, we discussed this before about ME update files, at that thread about signing a ME6 update
file. But wasn’t it a problem with such cutting? Don’t know if I’m imagining, but there is a little memory
bookmark that it is telling me there was a little difference between the cut and the actual ME update. Still,
will have to actually compare the files before making a statement.
You know, I actually looked at the Clevo screen for seconds, trying to figure out where the problem is. I
was almost about to ask you about it, then I saw the double header.
Yes the GUID is the same but the structure is different. That’s how ME Analyzer tells them apart. One
has GbE (Gigabyte) at 512KB whereas the other (Intel) does not (filled with padding where it should
have been) but everything is doubled at a size of 1MB. So it would seem like the Intel ffs is two times the
Gigabyte one minus GbE. Maybe GbE is missing because that SPI image came from a non-GbE system.
To test that we need to find a non-GbE Gigabyte BIOS. Shouldn’t be hard. If I’m right I’ll have to
rewrite that ME Analyzer code.
Regarding the cutting, are you referring to ME6? ME6 can be cut after FTPR again but they used an
extra $MN2 header of 4KB at the top which holds the signature and could only be created by some
special Intel tool that we don’t have. ME6 is a lost cause. Good news is that I finally found a “newer”
1.5MB UPD image recently (6.0.3 → 6.0.40). But everything else after that should be just fine. Apart
from ME7 which I already knew it could be cut and ME9.1 & ME10.0 for which I do now currently
have UPD samples, I tested ME8, ME9.0 and ME9.5. The resulting UPD images were identical with the
ones FWUpdate made with a slight size difference which is normal due to extra padding.
Ha-ha, yes. That’s why I added the red box you know! I’ve no idea how they did that and how they
haven’t realized that it can brick consumer systems. Maybe that’s why they don’t release BIOS updates
publicly, they know how often they mess up. They probably use hex editors to update the ME and that’s
how this happened.
If anyone has a 1.5MB system with ME9.1 or ME10.0, can you create an UPD image using FWUpdLcl
-save command?
If anyone has a 5MB system with ME8 or ME9.0 or ME9.1 or ME9.5 or ME10.0, can you create an
UPD image using FWUpdLcl -save command?
MERecovery FFS Modules: I was right, GbE exists only on systems that utilize an Intel Gigabit
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 20/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
Controller. It’s not something Gigabyte-specific as I initially thought. I also found such GUID modules
where their size was not enough to hold an $MN2 region and thus ME Analyzer did not report anything,
not even that they were FFS. So I had to rewrite some parts of the code. There is no more OEM-based
analysis (Intel or Gigabyte) and all irrelevant to FFS information is not shown (SVN/VCN, Region/UPD,
PRD/PRE/BYP etc). Now, regarding the MERecovery FFS Modules there are two methods of analysis
at ME Analyzer v1.1.4.
If $MN2 and GUID exists, the image is analysed to show Type, Version, Release & GUID:
If $MN2 is missing but the GUID exists, the image cannot be analyzed but the fact that it’s an FFS
MERecovery Module is shown via Release followed by the detected GUID:
The extracted FFS Modules obviously have the GUID header at the first 0x10 bytes and this is where
ME Analyzer only searches for it. Thus, there will be no false-positives with full SPI images where the
GUID can be found at some point inside the file’s contents.
Clevo MERecovery Feature: Turns out there is a hidden Aptio option which allows updating the ME
from inside the BIOS by loading an UPD/RGN (not sure about UPD) via USB like the regular BIOS
update. The SPI images that Clevo releases seem to include a double FPT header of it’s first 0x100
bytes for Recovery purposes in case of something goes wrong during the flash procedure. How it works,
why it’s only the first 0x100 etc I don’t know. The only difference between those first 0x100 bytes is the
inclusion of FITC version and a fixed FPT checksum for the latter.
Initially I mentioned that such SPI images could lead to bricks but after a more careful look I saw that
those 0x100 bytes are right before the start of the ME region as dictated by the Flash Descriptor limits.
For example F00 - FFF for the “recovery” $FPT (0x100) and 1000 + 17F000 for the actual ME
Region image. As far as cutting is concerned, I think Lordkag’s Extractor uses the Upper and Lower
Flash Descriptor limits to determine where the ME starts and ends and after that it’s cut to 1.5MB from
the regular 2MB full padded size. So this additional double $FPT header detection might not be required
for that utility.
Anyway, ME Analyzer v1.1.4 can now detect double (cut) FPT headers and automatically choose the
proper one which for the Clevo SPI images it’s the second.
ME 8.x-10.x UPD Cutting: My hypothesis that cutting after FTPR was right for ME 9 and up.
However, ME8 had the MDMV region before FTPR unlike it’s successors. So in order to create UPD
images you have to cut after FTPR and then manually add MDMV at the end of the resulting image. So
yes, it’s very much possible. Just kind of a hassle.
Based on the above, I manually made UPD images for 1.5MB ME9.0 and ME9.5 systems. Since I don’t
have UPD images from ME9.1 and ME10.0 systems, I cannot cut without making sure that everything
went properly based on a FWUpdLcl - made UPD sample images. Also, I don’t have any 5MB UPD
samples so those cannot be cut yet as well.
Ah, this is what you were saying with Gigabyte and GbE region. I didn’t realized it at the time, for I
would have said something. This is the reason Extractor is saving the GbE region as [Ven-Dev] Intel GbE
Lan Firmware [vers].bin, because it is Intel only. You can also find it in ME packs in Image Components
-> GbE. Besides, the Intel regions related code is from UEFITool, so if something is wrong you know
I see that you found that doubled ffs and others. I hope it wasn’t too much wasted time, we both learned
new things.
It is interesting that Clevo is placing this backup header inside the DESC region. I wonder if it is Intel idea
or their one, I also wonder what happens when there is a GbE region present.
My English failed me back there and now that I read it again, makes sense. I knew what GbE was even
though I don’t know specifics since I never had a system with Intel Gigabit (only JMicron, Atheros and
others). I have been seeing them inside the ME packages for quite some time now. I’ve always wondered
whether I should be keeping those but I haven’t researched such firmware and don’t know whether it’s
updated often, what versions are out there etc. I vaguely remember something like GbE 0.13 and 0.15 or
similar. Anyway, what I meant was: I thought that all the Gigabyte FFS Modules included the GbE section
even if they did not have an Intel GbE compatible controller. Obviously that was wrong and now that I
think about it, it never really made sense in the first place. Ha,ha…
Yeap, I think CodeRush is off the hook for now. No cardinal mistakes so far!
No it wasn’t a waste of time. We learned some new things and now any tools will be more feature-rich.
Regarding Clevo SPI images, why would there be an issue if GbE was present?
Regarding the Clevo matter, you can see that the recovery FPT header is not part of the ME region, but
rather of the previous one, which in the case of the sample you uploaded is Descriptor region. So, when a
Clevo system has a GbE region, where is this recovery FPT header placed: in the GbE fimware (which is
weird, to say the least) or in the Descriptor region, separated from the ME entirely?
And is this placement of a recovery FPT header in the descriptor an Intel thing or a Clevo thing?
@plutomaniac
Hello
ME FW 9.1.26.1006 5MB
http://www.station-drivers.com/index.php…26.1006-(5Mo)/
Note 1: Intel ME 11.0 Firmware Repository Pack was temporarily removed. When all 4 SKUs are
identifiable, it will be updated & uploaded again.
Note 2: Intel ME 9.6 Firmware Repository Pack was permanently removed. The 9.6.0.1038 firmware
can be found at the Other folder of ME 9.5 Pack.
Note 3: All UPD images from ME8 and up were permanently removed. ME Analyzer will be updated in
the future to ignore them if the RGN/EXTR is there.
ME 6.1.31.1075
http://cdgenp01.csd.toshiba.com/content/…TC00374300A.exe
Oh this is 1.5MB! Finally! We will be able to update to something latter than the ancient 6.0.40 version
that I had found some months back. It also includes the 5MB UPD image as well which will be added to
the repository only since we have a newer available. But it’s good news for ME6 1.5MB users. Not the
latest version but at least not ancient.
Hello
Hello
It seems like the link for Intel ME 9.5 Firmware Repository Pack r11 no longer available, could you
please upload it again? thanks
Thanks for the version update, but when I click the link, it says: The key you provided for file access was
invalid. This is usually caused because the file is no longer stored on MediaFire. This occurs when the file
is removed by the originating user or MediaFire. All other repository pack links work but only the Intel
ME 9.5 Firmware Repository Pack give me the error message.
@ ics:
Hello. I got two 7.1.80.1214 image here. Is it mean that the UPD one is better than the RGN one?
Which one should I flash with FWUpdLcl? Thank you.
@ bin456789:
ex58:
Because 9.0.50.xxxx was the predecessor of 9.1 firmware during Alpha and early Beta stages of
C610/X99 development. It has nothing to do with 9.0.31 or similar 9.0 firmware, it was a different
development branch based on Hotfix 50 (x.x.50.xxxx), now abandoned.
@ nikoZ:
Nothing important. That GUID usually stores another copy of the ME firmware either partially or fully for
recovery purposes. In the future, when MEA will be able to display multiple engine firmware inside SPI
images, that note won’t be there.
Thanks for info. I usually flash the latest ME FW available for my current platform.
Hello
All post-ME6 firmware are now correctly sized by adding or removing padding where needed:
ME 10.0, 9.5, 9.1, 9.0, 8.x, 7.x and TXE 1.x. Big thanks to Lordkag for the mesize, mext and
meupd functions of UEFIStrip.
Note: ME Analyzer v1.5.x and DB r49 or higher are required to correctly identify the fixed ME2
firmware names.
Hello
Thank you Pacman for both new firmware and bug report. From the filename and quick testing, it seems
that MEA is broken when it comes to SPS and UEFIStrip naming (no leading zeroes, no 0/1 type and
NaN shouldn’t be there).
mirza77:
Click the links at the first post, that simple. If Mediafire is blocked in your country, use a proxy or VPN.
Use WinRar or 7zip to extract.
@Pacman
Oops, sorry.
Here is 4.2.60.1060_AMT_PRD_RGN.bin
https://mega.nz/#!RzoXBITI!yAWUD_zY0mU9f…OtPm-TnW77rCQxs
SPI/ME dumps and those that get exported by the cleanup guide should always be reported as EXTR.
Was the original dump also shown as RGN when viewed in MEA? If yes, please upload the dumped ME
region as well to see if I can tweak MEA a little bit to detect it properly.
Yep, shows up as RGN. Here is the full one with all data.
https://mega.nz/#!A6QHwIQa!NXRNkXXzVK6JD…L2hIrS4Lvz3uptQ
Now that I think about it, you can’t have performed the cleanup guide with a clean/RGN 4.2.60 because
we don’t have such firmware. The last ME4 AMT RGN we have at the repositories which can be used
at the cleanup guide is 4.2.10.1023. In fact, the only difference between the two previous uploads are
some useless extra padding at the end of the region, nothing else. I do need to improve the EXTR
detection of ME4 firmware at MEA but other than that, in order for you to perform the cleanup guide you
need to use 4.2.10.1023_AMT_PRD_RGN and then update manually via FWUpdate.
I downloaded the latest RGN, ran the update and then downloaded the ME firmware. Then I did the
cleanup guide to remove the "data" settings. So did it not work?
You said “downloaded the RGN and run the update”. I assume you mean FWUpdate. Thing is, you
cannot use RGN/EXTR firmware at FWUpdate v4, only Update (UPD) images which are not the same.
So you must have updated the ME of your SPI chip via FWUpdate to 4.2.60 by flashing the UPD
image. So now you have a dirty/dumped (EXTR) 4.2.60 ME region. At step 4 of the cleanup guide you
need to select an RGN, how did you do that if we don’t have the RGN of 4.2.60? That’s what I’m
asking as it’s not possible to clean a 4.2.60 EXTR dump. The only possible thing to do is to take the
dumped 4.2.60 EXTR and clean it with 4.2.10 (or whatever the latest AMT_RGN is). That way you
flash back the cleaned+configured 4.2.10 which you can then update via FWUpdate if you like to 4.2.60
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 31/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
using the UPD image. If at that point you dump the ME region, that is not considered “clean” as the
system run at least once between flashing and dumping.
I kinda see what you’re saying in that its not a fresh RGN. I was going by what MEA said and file size.
I took the latest RGN dump (4.2.10.1023) and replaced the FF filled ME region via FPT. Then I used
FW update to flash 4.2.60 as you said. Following that I backup the ME region fully with FPT again
(~2.3MB) and then put it through intel flash tool to strip the settings/nvars/etc. It comes out the same size
as an RGN file and MEA recognized it as such. Before the larger dump was recognized as extracted.
First things first, ignore MEA until it is fixed to properly detect your dumped firmware as EXTR and not
RGN. I don’t understand the first sentence about your dump being 4.2.10 (thought it was 4.2.60) and
those FF replacements? I must be missing something, was your ME region filled with padding for some
reason? Since this has become way more confusing than it should be, I’ll build a hypothesis and the steps
that define it:
1) Your system currently has firmware 4.2.60 either from the manufacturer or because you used
FWUpdate some time in the past.
2) For some reason you want to follow the ME cleanup guide, which does not “remove/strip” settings but
transfers them after cleaning “dirt” (read Section A)
3) You dump your current SPI image with the dirty 4.2.60 ME region (EXTR, ignore MEA showing it as
RGN)
4) You follow the cleanup guide and at step 4 you need to pick the closest RGN firmware from the
repository
5) Since we don’t have the RGN for your SKU and version (AMT, 4.2.60) you must pick the closest
which is 4.2.10
6) The output of the guide produces a new SPI image based on your dump but with cleaned+configured
4.2.10 ME region
7) Flash that new SPI image back and now you have a system with a healthy 4.2.10 ME region
8) If you want to update to 4.2.60 you can use FWUpdate with the 4.2.60 UPD image from ME thread
9) Now your system has a healthy 4.2.60 ME region
My region was filled with padding, thats why fitcv4 was crashing on the backup. Me was disabled. So
you’re right, the dump should be EXTR.
plutomaniac:
Could this also be added to the start posting or to the ME FW Tools thread?
Hi. This is my first post here. Yesterday I encountered one of the rarest ME versions never seen before
(by myself). It comes from Apple Macbook Pro 13 with two Thunderbolt 3 ports (USB-C).
Computer was sold in Jan 2017. Sorry if I’m offtopic here but I’m really lost at this point as where I
can get a clean ME for this system. I searched the web and there’s no such version out there. At least,
I found nothing. The version is 11.0.12.1010. I can post extract here if you want to. It’s not clean,
obviously but maybe someone wants to have it. Interestingly the size is 1.2MB unlike other ME
supplied with Apple laptops. Anyone knows anything about this version?
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 33/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
@Sergioz
Hello and thank you for your report. The firmware I have found from Apple machines are 11.0.3.1000
and 11.0.12.1002 but not 11.0.12.1010. So please upload your dump for me to keep that firmware,
even if it’s not clean.
Sergioz:
That depends. In the past, Apple was using their own ME SKUs for their mobile systems (1.5MB, 5MB,
1.5MB Apple) but I don’t know if the same applies to their SKL (ME 11.x) based systems. Finding
Macbook users who can help figuring such things out is unfortunately very rare. Back to my "it depends"
statement:
If Apple is using a custom ME 11.x SKU then you can only update to latter versions of the same SKU
via FWUpdate (11.0.3.1000 –> 11.0.12.1002 –> 11.0.12.1010) and the firmware cannot be cleaned as
seen at the cleanup guide because we lack equivalent RGN variants which we will not find because only
Apple has them. In such case, one can take their official UEFI updates, extract the EXTR ME region
from within (should hopefully be Configured only, not Configured+Initialized - read section A of cleanup
guide) and use that as a "clean" firmware for reflash.
If Apple is not using a custom ME 11.x SKU then you can take any latter RGN from the repository and
follow the cleanup guide.
To test if Apple is using a different SKU, you can try updating to a normal ME 11.0 firmware via
FWUpdate and see if it works. However, make sure you can recover from bad flashes in such case via a
programmer.
@plutomaniac Hi. Thanks for such a detailed answer. I removed the serial, and locks from the dump.
Otherwise it’s completely working and verified dump for the following model: MBP 13 i5 2.0 Late-2016
Retina without touch bar. I flashed it successfully and it works 100%. I’d prefer you to have the whole
thing, so you can extract other data whether you need it. Let me know if this works for you. Feel free to
delete the attachment once you finished working with it.
Can someone point me in the general direction of what SPS image I will need for this:
@ Sergioz:
Thank you very much. Indeed posting the whole SPI image was a good idea, there was also an older
CPU microcode which we didn’t have at the database, aside from the ME firmware. I’ve now added the
latter to ME Analyzer. If you can recover from bad flashes and want to try if updating to newer 11.0
firmware works (to do the cleanup guide in such case) then you can follow the steps above (under
Windows though). Otherwise, I thank you again for your help.
@ tojoski:
For what purpose do you need a different SPS firmware? I don’t know what you need exactly, I was
never able to understand how the SPS versioning works. It’s not linear like ME and TXE firmware and
also we don’t have any SPS 2 tools to work with. It’s one of the reasons as to why MEA does not
support SPS firmware anymore.
plutomaniac:
For what purpose do you need a different SPS firmware? I don’t know what you need exactly, I
was never able to understand how the SPS versioning works. It’s not linear like ME and TXE
firmware and also we don’t have any SPS 2 tools to work with. It’s one of the reasons as to why
MEA does not support SPS firmware anymore.
@plutomaniac
I have been troubleshooting a restart / shutdown issue with this board on Windows 10, and I am at the
point where I am grasping for straws.
If you want to reflash the SPS firmware then you should see if you can read/write at the SPS region
(unlocked Flash Descriptor) by a motherboard jumper, BIOS option etc and use the one provided by the
OEM. This is not relevant to this thread though.
What’s the exact notebook model? ME 11.5 branch is dead and has been replaced by 11.6.
I do have the clean/RGN firmware for 11.5.0.1058 CON LP if you want to stay at 11.5, just know that it
has been replaced by 11.6.
This is from my own notebook. I just checked the file with ME Analyzer. If you need this bios to extract
ME let me know I can send to you…
Thank you razor_amd for your interest in ME Analyzer and for reporting new firmware. That firmware
has been found, please update MEA to the latest version.
Did I miss something or have all links to Intel SPS firmware repositories been removed? Is there a
possibility to get a link to the SPS 3.x repository?
SPS is given into two parts, Recovery and Operational. Flash Image Tool is required to build a full SPS
region out of these two. I don’t know how versions work (they are not linear like ME/TXE) but I could
upload them temporarily if you want. But not now, remind me in a week if you’re still interested.
Thanks a lot for your offer. I will remind you in about a week.
I found some examples of SPS firmware and could compare extracted region files to the OPR and REC
parts. All the rgn-files I viewed had a double (identical) operational section (MEA says "Dual OPR") and
one recovery section. But there were also differences in extracted OPR and REC sections even for the
same version, depending on manufacturer. And there are 4 other sections which seem to be specific to
vendor/board and SPS version.
Looking for ME 10.0.55.3000 with ROM Bypass preferably if anybody has one. Otherwise any ME
10.0.X.X with ROM Bypass.
Thanks in advance!
Don’t know if someone’s still collecting: SPS 3 3.01.03.043 can be found in this BIOS package. MEA
states it has multiple versions in it?
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 39/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
Xeon E5 V3/4
03.01.03.043 release
03.01.03.032 release
03.01.03.021 release
03.01.03.018 release
03.01.03.005 release
03.01.03.004 release
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 40/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
03.01.03.003 release
03.01.03.002 release
03.01.02.005 release
03.01.01.006 release
03.00.07.168 release
03.00.07.154 release
03.00.07.145 release
03.00.07.141 release
03.00.07.114 release
03.00.06.277 release
03.00.06.274 release
03.00.06.267 release
03.00.05.402 release
03.00.05.382 release
03.00.04.459 release
03.00.03.695 release
03.00.03.688 release
I do collect SPS firmware and that’s why MEA shows the green message when something not-in-db is
found. However I tend to ignore the .cap files from Intel because they are annoying/custom. I need to
manually create the OPR and REC from these so I don’t bother anymore. I don’t understand how SPS
versioning works, it’s not linear. Maybe the minor version signifies something.
(Why does MEA tell me the version is unknown when I let it check the cap- file but doesn’t say anything
when checking OPR- or REC- files?)
Hi, plutomaniac, if you have a sps tools, could you please upload it for public usage? That would very
helpfull for me, cause ME tools works incorrect with sps firmware.
Hello to all,
I received a notebook for repair, I got new cstxe file inside an old bios file and the ME analyzer told me
to report it here. Also I have downloaded and extracted new bios from manufacturer website so you
should have a clean one also. In rar file, there are both bios files.
https://www.mediafire.com/file/o1xv31d7n…_3.0.1.1105.rar
Hello razor_amd,
Thank you very much for your report and for using ME Analyzer. The dumped image is very interesting
and a little different from what I’ve seen so far. I’ll need to look into it and update MEA to work with it.
The image from the OEM is exactly what MEA expects. Do you know what model that is by any
chance?
Hello, I downloaded the Analyzer and it also told me to post here. I hope this aids in your effort to better
understand the ME.
Greetings!
Thank you for your report Swoosh and for using ME Analyzer.
It may be that the original bios from notebook was corrupt, so I downloaded fresh from their site. The
notebook is Acer Aspire ES1-132, motherboard is: da0zhpmb8f0 rev.f
Thank you razor_amd. I added support for that at ME Analyzer v1.34.0 a few days ago.
I am happy that I can help this community. I learned a lot from you and this forum. Thank you!
no extradition , error
Would it be possible to use a different compression scheme than RAR - preferably GZip? See
https://fedoraproject.org/wiki/Licensing:Unrar
@ tuanbacky:
Arlo_James_Barnes:
Would it be possible to use a different compression scheme than RAR - preferably GZip? See
https://fedoraproject.org/wiki/Licensing:Unrar
No. WinRar and 7z offer the best compression and the former is much faster than the latter while
consuming way less RAM. You can use 7zip to decompress RAR5 archives too.
Hi
I have a Asus X556UF with this info
Family: CSE ME
Version: 11.0.0.1180
Release: Production
Type: Region, Extracted
SKU: Consumer LP
Rev: C0
SVN: 1
VCN: 7
PDM: No
LBG: No
PV: Yes
Date: 2015-09-24
FIT Ver: 11.0.0.1180
FIT SKU: PCH-LP Premium U SKL
Size: 0x1BF000
Platform: SPT
Latest: No
And program dont do nothing, and same think with a new file for same model!
kalu:
And program dont do nothing, and same think with a new file for same model!
plutomaniac:
And program dont do nothing, and same think with a new file for same model!
kalu:
On Me analiser work fine… but on Intel Easy Clean Me, don’t make anything
kalu:
What is “Easy Clean Me”? That makes no sense. It certainly has nothing to do with MEA or the
Repositories thread, thus off-topic.
Hi.
The “Easy Clean ME” work with the repositories of this topic, heres the program Easy Clean ME
extrat the exe file to root of repositorie folder,one frist run it update DB file and localization of
repository… if not give him the location of repositories…
Peace.
I had no idea such a thing existed. I have nothing to do with it and I’m obviously not going to provide
support for it. It seems that the author has no notion of how Engine firmware is configured or cleaned.
The tool just replaces the Engine region with your input which is terrible to say the least. Just follow the
CleanUp Guide.
Hi,
Anyone know where to get the pre-production / ROM-bypass CSE images (asking in general, but I’m
specifically looking for Apollo Lake)?
I checked the Intel Easy Clean Me tool and it does not clean the ME but reset to default to every
portion. If I dump any file from completely working machine, it turned out the ME Region was reset to
default and the tool does not help at any thing.
It is just waste of time but one thing good is when some one need a raw region, that is a great tool to
reset the region to be able to use in other machines.
I have some files that cannot find in the repository files. I got lot of help here so need to return the help in
some way. There are some files I have to go through and upload them if I cannot find here.Should I just
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 48/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
I already have these but thank you for your contribution. Bulk/untouched is preferred. You can upload at
some file sharing site and share the link here.
Use previous version YPDM if you cannot find current, once settings transferred using guide it should be
OK and working.
@ wuzhiwei11:
Changing the CPU does not require a CSME firmware re-flash. The PDM erratum should also have
nothing to do with SSD issues. My guess is that you re-flashed a random SLM_LP EXTR CSME
firmware instead of following the CleanUp Guide on your own system’s dump. In that case, it’s a matter
of wrong CSME configuration. Attached is the latest CSME firmware region from the latest Apple EFI
for your system. Re-flash the CSME region via “fptw -me -rewrite -f
CSME_MB101_0163_B00_2018-06-26_07-55_D65FF99A.bin” followed by “fptw -greset” or use a
programmer to re-flash your dump with the CSME region “replaced as is” via UEFITool.
Thanks again!!!
(attached CPU photo)
Ah you are right, I forgot that it is a SoC. In that case you do indeed need to re-flash the CSME
firmware as well to remove old initialization data. Since Apple’s official EFI CSME firmware is
Configured and not Configured+Initialized, you can do what I said above. You don’t need to follow the
CleanUp Guide.
plutomaniac:
Ah you are right, I forgot that it is a SoC. In that case you do indeed need to re-flash the CSME
firmware as well to remove old initialization data. Since Apple’s official EFI CSME firmware is
Configured and not Configured+Initialized, you can do what I said above. You don’t need to follow
the CleanUp Guide.
Hello, I replaced it with the ME file you provided and it is completely normal. thank you for your help! ! !
Yes I know. I update the repos monthly but haven’t had the time this month so probably in a week.
Thanks, no big deal for me, I was only surprised to get to add something myself and always assumed
people found random ME and added to the thread/repo from deep dark hidden corners of the web
thank you
非常感谢你的整理归类。
[[File:QQ??20190403110739.png]]
@wosyuanxiao
Please send me a pm with a link so that I can verify what firmware that is.
Ah, that system is Pre-Production and runs PRE firmware, that’s why it’s not included in this thread. But
you’re right, that firmware was indeed not in MEA and reporting those which are not in the DB is always
very much wanted and appreciated as it helps understanding, research & further development. Thank you
very much for your contribution and for using MEA.
Where do I need to find this firmware? This BIOS is slow to turn on. I need to clean the ME firmware
area!
Ah you didn’t tell me that before, I thought you only wanted to report something which was not at the
DB. For cleaning, the proper thread is [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE
Regions with Data Initialization. No matter though as this is a Pre-Production system and we cannot
discuss it here. I’ll send a pm instead.
https://ftp.hp.com/pub/softpaq/sp96001-96500/sp96325.exe
Sorry if you already have this one. Mine analyzer is old, I will update ASAP. This download file from HP
website has multiple firmware inside.
Yes your MEA version & DB are really old. This is already found.
Hi there, the question is: can I update my Biostar’s Hi-Fi H170Z3 Ver. 5.x to latest 12.x ME fw ?
╔══════════════════════════════════════════╗
║ ME Analyzer v1.94.0 r172 ║
╚══════════════════════════════════════════╝
╔═════════════════════════════════════════════╗
║ H17BR508.BSS (1/1) ║
╟─────────────────────────┬───────────────────╢
║ Family │ CSE ME ║
╟─────────────────────────┼───────────────────╢
║ Version │ 11.8.50.3425 ║
╟─────────────────────────┼───────────────────╢
║ Release │ Production ║
╟─────────────────────────┼───────────────────╢
║ Type │ Region, Extracted ║
╟─────────────────────────┼───────────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────┼───────────────────╢
║ Chipset │ KBP/BSF-H A ║
║ │ SPT-H D ║
╟─────────────────────────┼───────────────────╢
║ Security Version Number │ 3 ║
╟─────────────────────────┼───────────────────╢
║ Version Control Number │ 275 ║
╟─────────────────────────┼───────────────────╢
║ Production Version │ Yes ║
╟─────────────────────────┼───────────────────╢
║ Lewisburg PCH Support │ No ║
╟─────────────────────────┼───────────────────╢
║ OEM RSA Signature │ No ║
╟─────────────────────────┼───────────────────╢
║ OEM Unlock Token │ No ║
╟─────────────────────────┼───────────────────╢
║ Date │ 2017-10-25 ║
╟─────────────────────────┼───────────────────╢
║ File System State │ Configured ║
╟─────────────────────────┼───────────────────╢
║ Size │ 0x1BF000 ║
╟─────────────────────────┼───────────────────╢
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 56/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
Thanks in advice !
forart.it:
Hi there, the question is: can I update my Biostar’s Hi-Fi H170Z3 Ver. 5.x to latest 12.x ME fw ?
Hi!
Does anyone know where are metadata blobs for modules (like bup.met, amt.met) in last versions of the
CSME 12.0 firmware?
yXww7EHj:
Does anyone know where are metadata blobs for modules (like bup.met, amt.met) in last versions of
the CSME 12.0 firmware?
Intel removed the Module Metadata (.met) at CSME >= 12.0.30 firmware. They remain only at OEM-
customizable LZMA compressed Modules like ish_bup or similar.
@plutomaniac
@ lost_N_bios
@ any one who can answer…
plutomaniac:
Intel removed the Module Metadata (.met) at CSME >= 12.0.30 firmware. They remain only at
OEM-customizable LZMA compressed Modules like ish_bup or similar.
yXww7EHj:
Metadata files were containing a lot of vital information to spawn processes in the system: entry
point, BSS size, MMIO ranges and so on. It can’t just disappear, there needs to be a new place for
such data structures. What do you think?
When 12.0.30 first appeared, I was mostly looking for the module hash and compressed size which are
vital for Huffman decompression and found a structure at RBEP > rbe and FTPR > pm modules which
contains some of the aforementioned info. I call it RBE_PM_Metadata at ME Analyzer and so far
I’ve been able to determine these fields:
The RBE Partition (RBEP) has metadata at its modules like "rbe". Once the RBEP RSA Signature and
Hash of module "rbe" are verified, it parses the RBE_PM_Metadata of "rbe" which includes, among
others, the metadata of FTPR > "pm". So once FTPR is loaded, it can use the RBE_PM_Metadata of its
"pm" module to get the metadata for the rest of the modules which are required for CSE operation.
Basically, "rbe" verifies (among a few others) "pm" and "pm" verifies the rest. Since there is no module
name field, in order to know which info corresponds to which module in FTPR, NFTP etc, the CSE
probably uses the (apparently) hard-coded DEV_IDs. This is what I’ve understood at this point.
@earthoo7 - sorry I don’t have any of the v2 SPS FW files, and no we don’t have a repo for those.
Method to cleanup is similar as what you find in ME/TXE guides, but you may need to change some stuff
manually too, check both side by side at each setting would be best way to do it manually.
Maybe once plutomaniac gets back he can find newer FW for you.
@plutomaniac
@Lost_N_BIOS
what stuff need to change bcoz fitc does not accept sps firmware?
pls describe if possible.
and is any universal method to edit bios logo for mostly support bios like 1 2 4 8 16mb bioses
how to find it & edit it manuallly with like uefitool?
thankyou
Hi how are you please can you help me i have macbook with courrpt bin
when i check get error https://ibb.co/9Gcc8yJ
and i can’t find the verion of my file
CSE ME
11.8.50.3425
hello!
@plutomaniac
My mobo is ASUS P8B-C-SAS-4L,and I find it’s SPS but not ME.The version is 02.02.00.42.
Would you had the repos of SPS?
Hi Team.
I have ME 11.7.0.3307, I guess it CON_LP_C_NPDM_PRD_EXTR in your classsification, from Voyo
I7 plus tablet, I download it with fpt from one device and tried to flash to another tablet with no luck. It’s
flashing but not working. From another side i can easy flash
11.8.55.3502_CON_LP_C_NPDM_PRD_EXTR.bin and it works but have couple issues.
Maybe it will be usefull for you, and even maybe you can help me flash it to another device.
https://dropmefiles.com/ppXfx
Restore the original firmware via fpt or programmer and then read Intel Management Engine:
Drivers, Firmware & System Tools to learn how to properly update the CSME firmware via
FWUpdate tool.
These "collections" take firmware from repos such as this thread, combine them with stuff from SD, leave
random names, dirty firmware etc. If you want help here then use whatever is found at the links of the first
post.
@plutomaniac
update guide regarding Server Platform Services Firmware Repository like
how to clean sps based firmware.
manually or any tool as fitc available for this.
if can manually please update guidelines.
thankyou for your fabulous work.
@ earthoo7
(CS)SPS is provided for reference/research or for people (usually with NDA) who already have tools.
Since finding (CS)SPS tools is nearly impossible and there are too many variants needed for each
platform, there will be no cleanup guide instructions and no Firmware & System Tools thread for
(CS)SPS.
SPS 5 seems to be new, too. (Just uploaded the region, SPS5 structure is not known to me):
lfb6:
SPS 5 seems to be new, too. (Just uploaded the region, SPS5 structure is not known to me):
Yes found it yesterday as well from SuperMicro. The structure is the same as CSME 12+.
Hello. Where i can get cse txe 3.0.1.1105 firmware or repository? Thanks!
kimballen:
No because it’s an Update image produced via FWUpdate tool and we already have the equivalent
firmware version in region form (RGN/EXTR). Thank you for the report either way.
@plutomaniac
found an old Repository 3.0.5.1125_AMT_PRD_EXTR in old dell bios which are not in mea database
i try to pulled out it with fitc.
after decomp found me region but it size are not accurate like other extracted Repository v3
is it okay?
if its okay, then why after drop it in mea shows some unneeded padding error.
is any other way to get it actuall size like other v3 extracted reposiatry?
my backup bios is healthy & working ok.
even i try it with other v3 RGN Repository for size confirmation
after change me region bios works okay like before but if again i decomp it with fitc its size same like old
Repository.
@earthoo7
Moved to the correct thread (repositories). There is nothing wrong with the firmware. I’ve added to the
next DB. It’s size is 0x19D000, as shown in MEA. Any extra data after that is checked and the user is
notified if they are useless removable padding.
please help me ?
CSE ME
12.0.47.1524
@ all:
The structure of the OP has changed. There are now 7 categories/families of Intel firmware and each
one links to a MEGA folder with all the included Repositories. There is a short content/repository
description under each main category/family. Every one of the current 64 repository archives has been
re-created and re-uploaded. This change will make it easier to maintain these repos at a reasonable
time frame. The goal is monthly updates. A similar approach might be used at the other Engine threads
in the near future.
Not a big thing, but I had to search a moment until I recognized that the heading was the link to the
repository. Could it be more intuitive to include the several items in the same link or have just the items
itself as link?
PHY P TGP
PHY P CMP
PHY S LKF
Or
PHY P TGP
PHY P CMP
PHY S LKF
(I’d prefer the second variant since it shows that all list items are part of the same link, but that might just
be valid for my browser…)
Nice helpful feedback. I fixed it (2nd option of course ). Thank you lfb6!
Hi, a very impressive job. Can you explain me which file should I use?
Exactly the same as shown by ME Analyzer. In my case: 11.0.0.1202_CON_H_D_PRD_RGN.bin,
right?
Is Major.Minor version must be the same or Major is enough.
I do see for example that the GT83VR 6RF has recent bios and recent ME FW releases 2017/2018
Then u can use a more recent FW image greater than 11.0 (11.1/2/3/4/5/6/7/8)
If the oem already has a bios with 11.8 for ex., then u can use the latest 11.8.86.3909.
EDIT: Explain that a bit more… i dont have or know that laptop/hw…
Is this dump the current on the motherboard? U changed motherboard… and that dump is from where?
U changed the PCH… but the base board and spi is the same… who soldered/repaired the mainboard?
U want to clean the ME, than use same major/minor version with that dump, good luck.
Hi, thanks for the quick reply. Yes, this is the GT83VR. I changed the SR2CE (GL82CM236) bridge
and now it boots with a black screen. I don’t know what the bios version is. I grabbed the dump and
checked ME Analyzer. Thought I’d clean the ME and it might work.
I need "CSME 12.0 repository r31" but download link got error. Can everyone help to fix this link ?
Plutomaniac updated the repositories 3 days ago, and yes, CSME12 doesn’t work. I assume he follows
these threads.
Mmm, weird. CSME 12.0 was working on my MEGA account but not externally at the public link. Re-
uploaded and seems to be working now, please verify. Also updated 13.50 and 15.0 today.
(Tried the 3 files posted today now and the files posted 3 days ago before last
post)
Greetings, any idea where did the TXE 0, 1, and 2 repositories go?
When going by the link I only see "CSTXE 4.0 CSTXE 3.2 CSTXE 3.1 CSTXE 3.0" in the folder.
Thank you,
yozas:
Greetings, any idea where did the TXE 0, 1, and 2 repositories go?
Some sort of weird MEGA issue, temporary I assume. The missing files seem to appear if you expand
that side-window on the left. Try that.
@plutomaniac Just a note for the link-colours of the downloads from the start post: when having a dark
theme, these links are almost unreadable.
Nothing too bad - I change to clear theme if I want to see them.
Thx!
1 Like
I know that everyone is quite busy, but I was wondering if there would be an update to the various
repositories in the not to distant future - the last update was back in early April. In particular I’m looking
for PHY TGP_N_15.107.135.5017_PRD which was included in the ME Analyzer r286 database but is
not yet part of the Mega repository.
Thanks!
1 Like
Hi, i need help to know about me with flash image tool, im editing a Dell M4800 Bios, but when i set Me
Region (5mb, but RGN Bin size is 9mb) in intel FIT tool… i chose the RGN BIN 9mb file, and i build
the image but the laptop doesn’t display image, anyways when i set the same ME Region but Bin size is
1.5MB (same file size as ME specified) the laptops works good, my question is
Is there a problem because the bin size is heavier than 5mb ?
NOTICE: the DELL M4800 have 2 chips, 8mb and 4mb, i think bios is distribuided on both chips.
My question is why it displays image with 1.5mb but no when i chose the 9mb file (5mb ME Region) and
it just keep rebooting?
NOTICE 2: Seems like the Dell m4800 don´t have any 1.5mb me region, just 5mb. (i noticed when i
extracted many EXE Files from dell BIOS Drivers, that allways have 5mb regions like 9mb ME Bin file)
I have an HPE ML30 gen9 server. When changing me, I made a mistake and did not back up the original
me
emphasized text,I asked for a backup from my friend, so I need SPS fit V4 version
because it needs to be modified. Can anyone provide it? Or help me modify it.Thank you!
屏幕截图 2022-06-10 211549|604x500
Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmware Repositories
- Special Topics / Intel Management Engine - Win-Raid Forum (level1techs.com)
1 Like
@link
Welcome to the Win-RAID Forum!
Since the Intel Management Engine has not much to do with the BIOS Region, I have moved your
request and the comment given by @MeatWar into the much better matching Sub-Forum and thread.
Good luck!
Dieter (alias Fernando)
Dear, Plutomaniac. I live in Ukraine and do not speak English. I ask you to help you choose a clean
region for the HP Pavilion G7, QUANTA 13, HAB BD82HM65, Model: G7-1236SG, Serial:
5CD145685Q, because HP does not save the firmware archives, I can not restore BIOS. BIOS is
located in two flashs: MX25L4005 and W25Q32BV.
@gleco1 There is no such thing like the one and only right clean ME region for your machine in these
repositories that simply can be chosen. The ME regions in the repositories need to be configured for the
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 74/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
If you suspect a corrupted ME or just think you would like to start with a clean ME- please follow this
guide to the letter:
[Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
Guide-How To: Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization Last
Updated: 2020-07-22 This guide is relevant to those who need to clean the DATA section of an
Engine (CSME, ME, CSTXE, TXE) Region, which is part of a dumped SPI/BIOS image, in order
to flash the latter on a different machine of the same OEM model. It is not meant as a guide on how
to completely transform a dumped Engine region into a stock Intel-provided one. Although the guide
can be used for that some…
Today updated my local copy of useful files. And found one I have but not exist in current repositories.
Not sure for what platform it is, but I downloaded 2021-03-06 file PMC LBG Repository r1.rar
I’m looking in a wrong place or it was accidently lost ? In this case - just attached it below.
PMC LBG Repository r1.rar (42.5 KB)
b1Ack:
I’m looking in a wrong place or it was accidently lost ? In this case - just attached it below.
WTL is LBG-R
1 Like
I have a problem with acer A514-54-33AP bios. The first problem is that the laptop does not turn on. I
try to clear ME[CSME System Tools v15.0 r15.ME ver 15.0.30.1776.PMC ver ,150.1.20.1038.
PCHC ver,15.0.0.1031]
normal laptop, but not detecting bootable hdd or NVME.
https://w inraid.level1techs.com/t/intel-cs-me-cs-txe-cs-sps-gsc-pmc-pchc-phy-orom-firmw are-repositories/30869/print 75/87
4/25/25, 7:01 PM Intel (CS)ME, (CS)TXE, (CS)SPS, GSC, PMC, PCHC, PHY & OROM Firmw are Repositories - Intel Management Engine - Win-Ra…
gradual flashing, the initial only clear ME .but not bootable detection.
2 added CLEAR PMC, the result is the same
3 plus PCHC Also the same
maybe from my mistake. please help with the solution
2 Likes
7 posts were merged into an existing topic: Intel (Converged Security) Management Engine:
Drivers, Firmware and Tools (16+)
I know that the pre-IME 16 systems are now legacy and there are fewer and fewer updates as well as
the moderators wishing to focus on other things, but it’s been over six months since the last batch of IME
firmware component updates (June 2022) to the repositories while there have been a number of ME
Analyzer updates over the same timeframe.
I was hoping that maybe there could be a couple more semiannual repository updates to match the
content of the ME Analyzer changes over the last six months and next year or so or pointers to some
other source for the repository binary file updates.
Thanks!
MEA recognizes CSE TXE 4.0.46.1924 but ME region is missing in repository (rev 19). Could you
include it?
2 Likes
Does anyone know where I can find a download of SPS ME System Tools (v4)? There are a few links
around the forum where random people have posted download links for them, but those are all dead :-/
3 Likes
hi Friend How are Friends Please I need 16X Flash Image Tool Please Uplode All 16X Flash image Tool
2 Likes
hello ! I looking for ME1 repository … I habe a 1.1.0.1089 bios to clean ME region , do you can tell me
where finf a repository for that, I only find from 2.0 to higher
thanks in advance !
The firmware repositories haven’t been updated in nine months and are missing a lot of the newer
updates - could anyone help me find the latest version of the PHY firmware
TGP_N_15.107.135.5018_PRD
Thanks!
The PHY repository have the 15.107.135.5017…(the one you requested in 2002) just doesnt contain
the one you want 5018, maybe we can forgive the owner of the share his “BAD” hard work and time
humm?
donmeek:
could anyone help me find the latest version of the PHY firmware TGP_N_15.107.135.5018_PRD
for MEA db
13.0.40.1594_CON_LP_D_PRD_RGN.rar (1.7 MB)
13.0.40.1594_CON_LP_D_PRE_RGN.rar (1.7 MB)
PMC_ICP_130.1.30.1051_LP_D_PRE.rar (62.7 KB)
2 Likes
for MEA db
15.0.10.1469_CON_LP_B_PRD_RGN.rar (1.7 MB)
15.0.10.1469_CON_LP_B_PRE_RGN.rar (1.7 MB)
PHY_TGP_N_11.224.247.0224_PRE.rar (27.7 KB)
8.0.4.1441_1.5MB_PRE_RGN.rar (939.1 KB)
6.1.0.1042_1.5MB_PRD_RGN.rar (499.7 KB)
6.1.0.1042_1.5MB_PRD_UPD.rar (499.0 KB)
4 Likes
for MEA db
2.0.5.3117_1.375MB_PRE_RGN.rar (833.5 KB)
2.1.5.3117_1.375MB_PRD_RGN.rar (825.5 KB)
2.1.5.3117_1.375MB_PRE_RGN.rar (825.5 KB)
6.1.1.1045_5MB_DT_PRD_RGN.rar (1.9 MB)
9.0.20.1447_5MB_PRE_RGN.rar (3.8 MB)
11.0.95.1006_COR_H_A_PRE_RGN.rar (3.7 MB)
11.8.50.3470_COR_H_DA_PRE_RGN.rar (4.0 MB)
11.8.50.3470_COR_LP_C_NPDM_PRE_RGN.rar (4.0 MB)
11.8.50.3470_COR_LP_C_YPDM_PRE_RGN.rar (4.0 MB)
11.8.92.4222_CON_H_DA_PRE_RGN.rar (1.3 MB)
11.8.92.4222_CON_LP_C_NPDM_PRE_RGN.rar (1.3 MB)
11.8.92.4222_CON_LP_C_YPDM_PRD.rar (1.3 MB)
11.8.92.4222_CON_LP_C_YPDM_PRE.rar (1.3 MB)
PCHC_TGP_15.0.0.1015_PRE.rar (1.5 KB)
3 Likes
hello, I encountered such a problem, I need to edit the PCIe Spread Settings parameter in the ME
region, using the ME Analyzer my version, but it turned out that I have SPS, and FIT opens with an error,
how can I edit this parameter, or how can I make a clean SPS region from the repository?
3 Likes
[Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
Why does the computer not recognize the hard drive when I use the above method?
1 Like
A post was merged into an existing topic: ME 11.8.60.3561_COR Support the use of 1151 Xeon
CPU on 100, 200 series motherboards.
Thank you @princepal ! Do you have the full SPI images instead of the CSE/ME regions?
Hello,
would like to know if possible to get Intel(CS)TXE Firmware Repository 3.1.93.2965
Thank you.
Hi all ME Analyser Tells me that my CSME firmware is not in the repository yet. I want to do my bit and
report it. Am in in the right place to do that?
“Note: This CSE ME firmware is not in the database! You can help this
project by sharing it at https://win-raid.com forum. Thank you”
Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)
Intel (Converged Security) Management Engine: Drivers, Firmware and Tools for (CS)ME 2-15
Last Updated: 2022-09-08 Intel Management Engine Introduction: Built into many Intel-based
platforms is a small, low power computer subsystem called the Intel Management Engine (Intel ME).
This can perform various tasks while the system is booting, running or sleeping. It operates
independently from the main CPU, BIOS and OS but can interact with them if needed. The ME is
responsible for many parts of a…
Intel (CS) Management Engine: Drivers, Firmware and Tools for (CS)ME 16+
Intel Converged Security Management Engine Drivers, Firmware and Tools CSME 16+ Last
Updated: 2022-09-10 Intel Management Engine Introduction: Built into many Intel-based platforms
is a small, low power computer subsystem called the Intel Management Engine (Intel ME). This can
perform various tasks while the system is booting, running or sleeping. It operates independently
from the main CPU, BIOS and OS but can interact with them if needed. The ME is responsible for
many parts of an In…
1 Like
TGP_150.2.00.1024_H_A_PRD_5FB31D03
TGP_N_15.118.199.0118_PRD_1F96A22F
The files in mega were expired,could you upload them on the forum?thanks~
I cannot successfully extract the archive files. Some of the files fails to extract. I used Winrar 7 it still
failed.
Blessedtech:
Point them
Maybe an error during download? 14 abd 14.1 unpack properly with 7-zip?!
1 Like
I have this file here! From a Thinkpad X200. It is not in the database.
I see the same version ME in the database. But running CMP i get different results.
The file is: ME 4.1.3.zip - Google Drive (Link because of forum restrictions)
1 Like
saberofblack:
I have this file here! From a Thinkpad X200. It is not in the database.
Well, that is a blast from the past, haha. Thanks for the report saberofblack