Intel (Conv - Sec.) Trusted Execution Engine - Drivers, Firmware and Tools - Intel Management Engine - Win-Raid Forum
Intel (Conv - Sec.) Trusted Execution Engine - Drivers, Firmware and Tools - Intel Management Engine - Win-Raid Forum
el (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
HOSTED BY LEVEL1TECHS
Built into many Intel Chipset-based platforms is a small, low power computer subsystem called the Intel
Trusted Execution Engine (Intel TXE). This can perform various tasks while the system is booting, running
or sleeping. It operates independently from the main CPU, BIOS & OS but can interact with them if
needed. The TXE is responsible for many parts of an Intel-based system. Such functionality extends, but
it's not limited, to Platform Clocks Control (ICC), Thermal Monitoring, Fan Control, Power
Management, Overclocking, Silicon Workaround (resolves silicon bugs which would have otherwise
required a new cpu stepping), Identity Protection Technology, Boot Guard, Rapid Start Technology,
Sensor Hub Controller (ISHC), Wireless Display, PlayReady, Protected Video/Audio Path etc. Thus it is
essential for it to be operational in order for the platform to be working properly.
The evolution of Intel Trusted Execution Engine into a unified security co-processor, running x86 code
under a Minix-based Operating System. It was first introduced in 2015 with the release of Skylake
CPUs working alongside 100-series Sunrise Point Platform Controller Hub (PCH). The CSE hardware
can run Management Engine (ME) 11+, Trusted Execution Engine (TXE) 3+ or Server Platform Services
(SPS) 4+ firmware. So there are a total of three families of CSE-based firmware: CSME (CSE ME),
CSTXE (CSE TXE) and CSSPS (CSE SPS). The CSE hardware is also capable of running other types
of firmware such as Power Management Controller (PMC), Integrated Sensor Hub (ISH), Imaging Unit
(iUnit), Clear Audio Voice Speech (cAVS), Wireless Microcode (WCOD) etc.
Handles all Platform Controller Hub (PCH) power management related activities, running ARC code on
top of the CSE hardware. PMC administers power management functions of the PCH including
interfacing with other logic and controllers on the platform to perform power state transitions, configure,
manage and respond to wake events, aggregate and report latency tolerance information for devices and
peripherals connected to and integrated into the PCH etc. It was first introduced in 2018 with the release
of Coffee/Cannon Lake CPUs working alongside 300-series Cannon Point PCH.
Disclaimer:
All the software and firmware below comes only from official updates which were provided and
made public by various manufacturers! The System Tools are gathered and provided with the sole
purpose of helping people who are out of other viable solutions. Thus, they can be extremely helpful to
those who have major problems with their systems for which their manufacturer refuses to assist due to
indifference and/or system age.
Getting Started:
Intel (CS)TXE is a Hardware platform which runs Firmware, is monitored/configured by Tools and
interfaces with the user via Drivers. To get started, you need at the very least to know what
(CS)TXE firmware major and minor version your system is running. Such info can be retrieved in
various ways but you can use the free system information and diagnostics tool HWiNFO >
Motherboard > Intel ME/TXE > Intel ME/TXE Version. The format is Major.Minor, Build,
Hotfix. Once you determine the system's (CS)TXE firmware major and minor version, you can install the
latest Drivers from section A and update the (CS)TXE Firmware by following sequentially the relevant
steps at Section B using the required Tools from Section C.
The latest v4 DCH drivers are usable with CSTXE 3-4 systems running under Windows 10 >= 1709.
The latest v4 MSI drivers are usable with CSTXE 3-4 systems running under Windows 8, 10 <= 1703.
The latest v3 drivers are usable with CSTXE 3 systems running under Windows 7. The latest v2 drivers
are usable with TXE 2 systems running under Windows 7, 8, 10 or TXE 1 systems running under
Windows 10. The latest v1 drivers are usable with TXE 1 systems running under Windows 7, 8. In
order to check your current installed version, use Intel TXEInfo tool as instructed below.
Note: To extract the files below you need to use programs which support RAR5 compression!
These packages contain the Intel TXEI drivers with their respective software & system services. It is
advised to install these to enable all the Engine-related functionality. Since the Intel TXEI Drivers and
Software are OS version dependent, search and run "winver.exe" to determine your own.
Note: TXEI Drivers and Software v2028.4.0.1091 DCH package includes v1924.4.0.1062 TXEI
driver. TXEI Drivers and Software v2028.4.0.1091 MSI package includes v1924.4.0.1062 TXEI
driver. TXEI Drivers and Software v3.1.50.8289 package includes v3.0.0.1115 TXEI driver. TXEI
Drivers and Software v2.0.0.1094 package includes v2.0.0.1094 TXEI driver. TXEI Drivers and
Software v1.1.0.1064 package includes v1.1.0.1064 TXEI driver.
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 2/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
These packages contain only the Intel TXEI Drivers without any additional software or system services.
Installing these allows only very basic Engine-related functionality. Since the Intel TXEI Driver is OS
version dependent, search and run "winver.exe" to determine your own.
The SPI/BIOS chip firmware is divided into regions which control different aspects of an Intel-based
system. The mandatory regions are the Flash Descriptor (FD), the (Converged Security) Trusted
Execution Engine (CSTXE/TXE or Engine) and the BIOS. The FD controls read/write access
between the SPI/BIOS chip regions and holds certain system hardware settings. The (CS)TXE holds the
system's Engine firmware. For security reasons, the FD and Engine regions of the SPI/BIOS chip are
usually locked so that no read/write access is allowed via software means. Since the FD controls that
read/write access, it must be locked/protected so that it is not manually overwritten to allow unauthorized
access to the firmware regions of the system's SPI/BIOS chip. The Engine region at the system's
SPI/BIOS chip is also locked/protected due to the nature of the CSE/TXE co-processor, as explained at
the Introductions above.
Intel (CS)TXE or Engine firmware is mainly categorized based on its target Chipset Family (i.e. Bay
Trail, Apollo Lake, Gemini Lake etc), Type/SKU (i.e. 1.25MB MD, 1.375MB IT etc) and Version (i.e.
4.0.0.1245 = Major.Minor.Hotfix.Build). Be careful of what firmware your download relevant to your
system. To understand your exact Chipset Family, (CS)TXE Type/SKU and (CS)TXE Version, you can
usually run TXEInfo or TXEManuf tools with "-verbose" parameter. Otherwise, ME Analyzer can
show you all the relevant information, after loading your SPI/BIOS image (Flash Descriptor + Engine +
BIOS), when the latter is available. If a SPI/BIOS image is not available, run FWUpdate tool (when
available) with parameter "-save fw.bin" and load the resulting "fw.bin" image into ME Analyzer instead.
All the firmware below correspond to a specific Family which runs a specific (CS)TXE firmware
version (example: For systems running CSTXE v4).
The Type of each Engine/(CS)TXE firmware Region can be either Stock (RGN) or Extracted
(EXTR). Stock are clean/stock/unconfigured images provided by Intel to OEMs. Extracted are
dirty/extracted/configured images from various SPI/BIOS. The Engine firmware at the system's
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 3/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
SPI/BIOS chip is always EXTR, generated by the OEM after configuring the equivalent RGN with the
appropriate system settings.
The Engine Firmware Regions (RGN/EXTR) consist of two sections: CODE and DATA. CODE is the
actual Engine firmware whereas DATA is where all the system-specific settings are stored, as configured
by the OEM at the factory via Intel Flash Image Tool. The Engine firmware is not static as it holds
system-specific configuration and can additionally be configured by the Engine co-processor itself while
the system is running in order to provide the proper support and functionality. Any such changes are
written into the DATA section of the Engine Region and the firmware is considered Initialized. That means
that the DATA section can be in one of three states: Unconfigured, Configured or Initialized.
Unconfigured means that the Engine firmware image is the stock one Intel provides and not configured by
the OEM at all (RGN). Configured means that the OEM has applied model specific settings and the
Engine region is ready for deployment (EXTR). Initialized means that the Engine region comes from a
system which was already running and thus the Engine co-processor has further configured the DATA
section to suit that particular system better (system specific or dirty EXTR).
All (CS)TXE firmware are defined by a Security Version Number (SVN) like 1,2,3 etc which is used to
control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The SVN gets
incremented if there is a high or critical security fix that requires a Trusted Computing Base (TCB)
recovery operation, a significant event in the life cycle of the firmware which requires renewal of the
security signing keys in use. A downgrade to a lower SVN value via FWUpdate tool is prohibited
whereas an upgrade to the same or higher SVN is allowed. For example if your current firmware
has a SVN of 2, you can update to another firmware with SVN >= 2 (for example 3) but you cannot
downgrade to another firmware with SVN < 2 (for example 1). Trying to flash a firmware with lower
SVN will result in the error "The image provided is not supported by the platform" or similar. To view the
SVN value of any (CS)TXE firmware, you can use ME Analyzer tool.
All (CS)TXE firmware are defined by a Version Control Number (VCN) like 1,2,45,193 etc which is
used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The VCN
gets incremented if there is a security fix, a significant firmware change or a new feature addition. A
downgrade to a lower VCN value via FWUpdate tool is prohibited whereas an upgrade to the
same or higher VCN is allowed. For example if your current firmware has a VCN of 176, you can
update to another firmware with VCN >= 176 (for example 193) but you cannot downgrade to another
firmware with VCN < 176 (for example 174). Trying to flash a firmware with lower VCN will result in
the error "The image provided is not supported by the platform" or similar. To view the VCN value of any
(CS)TXE firmware, you can use ME Analyzer tool.
All (CS)TXE firmware are defined by a Production Version/Ready Status (PV) which can be either Yes
or No and is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool.
The PV status is set to Yes when a firmware is validated/ready for use at Production platforms, thus when
its status is Stable and not Beta, Alpha etc. An upgrade/downgrade from PV to non-PV firmware via
FWUpdate tool is prohibited whereas upgrades/downgrades to the same PV or from non-PV to
PV are allowed. For example if your current firmware has PV set to Yes, you can upgrade/downgrade
to another firmware with PV set to Yes but you cannot upgrade/downgrade to another firmware with PV
set to No. Trying to flash a firmware with incompatible PV will result in the error "The image provided is
not supported by the platform" or similar. To view the PV status of any (CS)TXE firmware, you can use
ME Analyzer tool.
TXE Firmware v1.0 is divided into two SKUs: Thin 1.25MB and Full 3MB. TXE Firmware v1.1 and
v1.2 have combined the two previous SKUs into a single 1.375MB SKU. TXE Firmware v2.0 has a
single 1.375MB SKU. CSTXE 3 has two SKUs based on Apollo Lake (APL) or Broxton (BXT)
platform. CSTXE 4 has only one SKU for Gemini Lake (GLK) platform. To determine your SKU, ME
Analyzer (by loading your SPI/BIOS image) or TXEInfo can help you sort most system specific details.
Engine Firmware Updating: There are two ways to upgrade or downgrade the Engine firmware, either
via Intel FWUpdate tool or manually.
The Intel FWUpdate tool is an official command line utility provided by Intel which uses the Engine
co-processor itself to upgrade/downgrade the TXE firmware quickly and easily. FWUpdate tool
requires that the Engine co-processor is operational and that its current Engine firmware
region is healthy at the system's SPI/BIOS chip. To check if the Engine itself as well as its current
firmware are healthy, you can use Intel TXEInfo and TXEManuf tools, as instructed below.
FWUpdate tool also requires that the SVN, VCN and PV are not violated. FWUpdate tool
does not require the user to have read/write access to the Engine firmware region of the
system's SPI/BIOS chip, as dictated by the Flash Descriptor region permissions. Moreover,
FWUpdate tool deals only with Engine CODE and does not require any prior Configuration
(DATA). It can thus work with either RGN or EXTR Engine Regions. The basic usage is FWUpdLcl
-f update_file_name.bin. You can see the entire supported parameters by displaying the utility's help
screen via FWUpdLcl -?. Note that the name of the file to be flashed via FWUpdate does not matter.
In the event in which the usage of Intel FWUpdate tool is not possible, you can try to
upgrade/downgrade the (CS)TXE firmware manually. Such cases include updating Converged
Security Trusted Execution Engine (CSTXE) firmware, downgrading to Engine firmware which violate
SVN, VCN or PV, repairing a corruption/problem etc. To upgrade/downgrade/repair manually, you
need first & foremost to have read/write access to the Engine firmware region of the system's
SPI/BIOS chip. To check if your FD is locked or to attempt to unlock it, follow the [Guide] Unlock
Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing. Once you have
read/write access to the Engine firmware region of your system's SPI/BIOS chip, you can use any
general purpose firmware flasher software such as Intel Flash Programming Tool, AMI AFU,
Flashrom etc, which directly reads/writes the system's SPI/BIOS chip firmware. Before flashing, you
must make sure that the Engine firmware region to be flashed back is Configured (EXTR) for your
specific system via Intel Flash Image Tool (FIT). In order to do that, follow the [Guide] Clean
Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization. Never flash RGN
or 3rd-party EXTR firmware to the Engine firmware region of the system's SPI/BIOS chip
without first configuring them for your specific system (EXTR) via FIT. Since general purpose
firmware software do not upgrade/downgrade/repair the Engine firmware region of the system's
SPI/BIOS chip via the Engine co-processor itself, they are usually not restricted by the SVN, VCN
and PV security measures. As long as you have read/write access to the Engine firmware region of the
system's SPI/BIOS chip and a DATA Configured (EXTR) Engine firmware image, they should
accomplish the desired action. Note however that some platforms have the current TCB SVN and/or
ARB SVN value permanently set/fused/burned in the Chipset so you cannot downgrade their
firmware with another which has lower TCB SVN and/or ARB SVN.
TXE 1 - 2 Updating:
Intel TXE v1 - v2 firmware can be updated easily & safely by using FWUpdate tool. Intel TXE v1.0
firmware (3MB & 1.25MB) can be upgraded to v1.1 or v1.2 firmware (1.375MB). However, the
upgrade process can not be done via FWUpdate tool. Read more at "Engine Firmware Updating"
above.
CSTXE 3 - 4 Updating:
Intel CSTXE v3 - v4 firmware do not have a FWUpdate tool. The CSTXE firmware updating is
normally left to OEMs only, via two possible methods: Download & Execute (DnX, rarely used) or
Capsule Update (normal SPI/BIOS image re-flash, most common). End-users who are looking to update
their CSTXE firmware must follow the [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE
Regions with Data Initialization, provided that they first have a full SPI/BIOS image from their OEM
or a system firmware dump. To be able to flash the updated SPI/BIOS image back (Capsule Update
method), you need to have read/read access to the system's SPI/BIOS chip firmware. Read more at
"Engine Firmware Updating" above.
CSTXE 4
For CSTXE v4
CSTXE 3.1
For CSTXE v3.0 - v3.1
CSTXE 3.2
For CSTXE v3.2
TXE 2.1 1.375MB
For TXE 1.375MB v2.1
TXE 2.0 1.375MB
For TXE 1.375MB v2.0
TXE 1.2 1.375MB M/D
For TXE 1.375MB M/D v1.2
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 6/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
The Intel (CS)TXE System Tools are used for creating, modifying, and writing binary image files,
manufacturing testing, Intel (CS)TXE setting information gathering and Intel (CS)TXE firmware
configuration and updating. These tools are not released to end-users but only to OEMs. The software
below comes only from official updates which were provided and made public by various OEMs.
Flash Image Tool: Creates and configures a complete SPI image file which includes regions such as
Flash Descriptor (FD), BIOS/UEFI, Intel (CS)TXE etc. The user can manipulate the completed SPI
image via a GUI and change the various chipset parameters to match the target hardware.
Flash Programming Tool: Used to program a complete SPI image into the SPI flash device(s). FPT
can program each region individually or it can program all of the regions with a single command. The user
can also use FPT to perform various functions such as view the contents of the flash on the screen, write
the contents of the flash to a log file, perform a binary file to flash comparison, write to a specific address
block, program fixed offset variables etc.
Manifest Extension Utility: Used to generate a 3rd party Independent Update Partitions (IUP) which
are compressed and signed by an external signing tool, such as OpenSSL. The signed contents may then
be stitched into a SPI/BIOS image using the Intel Flash Image Tool (FIT).
Notice: Avoid using the Windows builds of very old (CS)TXE System Tools which either retrieve info
(TXEInfo, TXEManuf, Flash Programming Tool) or modify the platform (FWUpdate, Flash
Programming Tool) as they may not work properly on newer operating system versions. When available,
it is advised to use either the DOS or EFI builds of said very old tools.
Notice: Avoid running the System Tools from paths which include non-English characters (i.e. Cyrillic,
Chinese, Arabic, Greek) as it may cause them to crash or behave unpredictably.
Those who are looking to update/downgrade their firmware should use TXEInfo, FWUpdate and
TXEManuf tools for status information, updating and functionality checking accordingly. The information
and instructions below apply to these three tools only and can be found inside the full Intel TXE System
Tools Packages.
TXEInfo: Shows (CS)TXE and IUP info and checks that the Engine co-processor is operating properly
on the software/firmware level. Make sure it doesn't report any errors. You can use "-verbose" parameter
to get status info in more detail. The "GBE Region does not exist" warning is normal for systems that don't
have an Intel GbE Controller, you can safely ignore it.
TXEManuf: Diagnostic tool which runs various manufacturing-line tests to ensure that the Engine co-
processor is operating properly on the hardware level. It should report a "TXEManuf Operation Passed"
or similar success message. You can use "-verbose" parameter to get diagnostic info in more detail.
FWUpdate: Used to effortlessly upgrade or downgrade the TXE 1 & 2 Engine firmware. Read more
about FWUpdate tool at Section B.
Note: To extract the files below you need to use programs which support RAR5 compression!
[Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
Request to unlock hidden options for tablet BIOS, this is a new model
Request for Modded Intel ME Firmware for Lenovo M900 with AMT Support
NEW! TXE v1.1 (1.375MB) Firmware from v1.1.0.1115 (VCN ~8) → v1.1.2.1120 (VCN 11)
NEW! TXEI Drivers & Software from v1.1.0.1113 → v1.1.2.1120 complete installer package
Updated TXEI Drivers v1.1.0.1064 (same driver from 01/2014, new security catalog from
09/2014)
Added at TXE System Tools v1.1: Intel TXE FW v1.1.2.1120 HF Release Communication
documentation
Updated at TXE System Tools v1.1: Bay Trail TXE Firmware Release Notes v1.1.0.1089 →
v1.1.2.1120 documentation
Updated at TXE System Tools v1.1: Bay Trail TXE FW Bring Up Guide v1.7 (02/2014) → v1.7
(09/2014) documentation
Updated at TXE System Tools v1.1: System Tools User Guide v1.3 (10/2013) → v1.4 (04/2014)
documentation
Updated at TXE System Tools v1.1: Flash Image Tool from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: Flash Manifest Generation Tool from v1.1.0.1089 →
v1.1.2.1120
Updated at TXE System Tools v1.1: Flash Programming Tool(Android) from v1.1.0.1089 →
v1.1.1.1120
Updated at TXE System Tools v1.1: Flash Programming Tool(EFI) from v1.1.0.1089 →
v1.1.1.1120
Updated at TXE System Tools v1.1: Flash Programming Tool(EFI32) from v1.1.0.1089 →
v1.1.1.1120
Updated at TXE System Tools v1.1: Flash Programming Tool(Windows) from v1.1.0.1089 →
v1.1.1.1120
Updated at TXE System Tools v1.1: Flash Programming Tool(Windows64) from v1.1.0.1089 →
v1.1.1.1120
Updated at TXE System Tools v1.1: FWUpdate(Android) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: FWUpdate(LocalEfi32) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: FWUpdate(LocalEfi64) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: FWUpdate(LocalWin32) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: FWUpdate(LocalWin64) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEInfo(Android) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEInfo(EFI) from v1.1.0.1113 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEInfo(EFI32) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEInfo(Windows) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEInfo(Windows64) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEManuf(Android) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEManuf(EFI) from v1.1.0.1089 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEManuf(EFI32) from v1.1.0.1113 → v1.1.1.1120
Updated at TXE System Tools v1.1: TXEManuf(Windows) from v1.1.0.1089 → v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(Windows64) from v1.1.0.1089 → v1.1.1.1120
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 9/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Note: I know the latest v1.0 firmware is v1.0.5.1120. If you can find it by aqcuiring a full package,
extracting it from a BIOS, using FWUpdate -save etc please share it here.
Hello
TXE 3MB firmware 1.0.5.1120 i have not tested as i don’t have the suitable HW.
Pacman, thank you very much for being the first to contribute in TXE and for keeping an eye out for such
firmware & drivers. It seems that it was extracted from a BIOS. Can you tell me which one? Such info
can be useful in order to check if they have also uploaded the equivalent full package or if I can find the
VCN number.
I cannot test these as well because I don’t have the hardware. If anyone has used the firmware, tools &
drivers successfully please let us know here.
NEW! Intel TXE1.0 Firmware 1.25MB from v1.0.4.1089 (VCN ~8) → v1.0.5.1120 (VCN ~8)
NEW! Intel TXE1.0 Firmware 3MB from v1.0.4.1090 (VCN ~8) → v1.0.5.1120 (VCN ~8)
Update:
So, I figured out how to determine the VCN when a TXE firmware is extracted from UEFI images:
I have found recently an Intel TXE Firmware 1.0.6.1120 in a HP BIOS, didn’t noted which one. Most
likely a 3MB one.
Also attached other older versions I have. Ignore the names for now, I will see if I can add a TXE
detection to my Extractor. With Igor’s script and your help, it shouldn’t be that hard. It seems you
already gone further than Igor:
NEW! Intel TXE1.0 Firmware 3MB from v1.0.5.1120 (VCN 11) → v1.0.6.1120 (VCN 11)
Lordkag, thank you for the newer FW. It’s funny, I found that version some hours before your post at HP
as well. But I couldn’t extract the damn BIOS image at all. Have you written your own scripts to extract
those after identifying the compression?
Anyway, this a 3MB SKU. Here are all the different HP packages with that version - maybe some other
has the 1.25MB variant. Can you please extract those as well?
http://h20564.www2.hp.com/hpsc/swd/publi…b-142261-1#tab2
http://h20564.www2.hp.com/hpsc/swd/publi…b-142260-1#tab2
http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_141216_1&#tab2 →
(Extracted, 3MB)
Now, to fix your extractor properly here are some usefull info:
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 12/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
That is: 135E0h for 1.25MB, 438E0h for 3MB & 67760h for 1.375MB SKUs respectively.
Once the $SKU is determined the size to extract is as follows (based on Intel bin size, anything larger is
useless FF padding):
Also, I have uploaded a new “collection” of TXE firmware. I have added some of my own older
firmware, corrected the names & sizes by adding or removing padding and correctly determined each
firmware’s SKU:
They are not compressed, but encrypted. One of the "features" HP is offering to customers is full lock-
down on their paid products. What I do is extract that .exe until I get to this folder:
Then I run InsydeFlash, which (after analysing the system) offers these options:
where you choose the folder to unpack the unencrypted content. If for some reason the flasher disables
the options (happens on newer versions), I use the attached older flasher and drop the file with .fd
extension. Anyway, all of the above links have a 3M firmware, with sp69922.exe offering a clean
firmware, which you might want to use instead of the one I uploaded.
I added TXE detection, by checking the size of modules (those starting with $MME). If it is 0x60, we
have ME, if it is 0x80 (0x60 + 0x20 reserved), we have TXE. I also added TXE variant detection, by
checking the start of first $MN2 section. If it is 0x13000 = 1.25M, 0x43000 = 3M, 0x67000 =
1.375M. If this fails, I will read the SKU and check the major.minor version: 67 5C FF 0D 03 43 and
1.0.x = 1.25MB, 67 5C FF 0D 03 43 and 1.1.x = 1.375MB, 67 5C FF 0D 05 43 = 3MB.
I don’t know about the size. The extraction happens before, at regions display, by analysing the
descriptor (thanks to CodeRush). Only if the region is smaller than 0x1FFFFF, I use 0x17D000 for
1.5MB. The detection happens later, at ME version display, so I don’t feel like using the detection twice.
Plus, if you look at 1.0.0.1055_1.25M, the last section should start at 0xAC000 and be 0x99000 in size,
reaching 0x145000. Even though only padding is after 0x140000 limit, it still cuts the original structure,
with possible complaints from the flasher. So, for now I leave this on hold.
Thanks for explaining the encrypted HP binaries and for the files.
The difference between sp70119/sp70118 & sp69922 is whether NFC is enabled or disabled. If you
enable/disable it at both the code will be identical (apart from 1,2 bytes at $FPT header -> useless). It
seems that every time you Build a TXE image at FITC, a version will be added at $FPT header where
it’s usually FF at Production images. I said a version because the weird thing is that sometimes that
version is wrong. For example at v1.0.5 & 1.0.6 images (extracted by FITC) it reports 1.0.4 at the
$FPT header (of course it’s correct at $MN2). I’ve seen this before regarding TXE. Maybe, 1.0.5 &
1.0.6 are based on 1.0.4 and this is kept somewhere for some reason. Or maybe it’s a bug. I will
reupload the "FF at $FPT" version (as I like to call it) here so that it’s "clean". I don’t know what’s the
deal with NFC being enabled & disabled, my guess is that FWUpdLcl won’t care either way.
lordkag:
Plus, if you look at 1.0.0.1055_1.25M, the last section should start at 0xAC000 and be 0x99000 in
size, reaching 0x145000.
I don’t understand, how do you check the size exactly? At $SKU for example it makes sense to me (04
00 00 00 or 4 * 3 = 12 or 0xC). According to Igor, the size of $MN2 is between 18 & 1B. So, at the
last $MN2 of 1.0.0.1055_1.25MB firmware that would be: FE 00 00 00 or 254 * 3 = 762 or 0x2FA.
Where am I wrong?
You mentioned something about 1.0.0.1055_1.25MB and the it’s size (regions getting cut-off even
though it’s just padding). Let me explain: I don’t think 1.0.0.1055 is a credible TXE firmware. If you
notice, all other (newer) 1.25MB firmware start the last $MN2 region at a different offset (0xA5000)
and do not contain extra data after the $MN2 size (as calculated above) in contrast to 1.0.0.1055
(0xAC000). I remember back at November when I first wrote this thread that TXE started differently.
Some old documentation (from the original 1.0.0.1050 package, can’t find it anymore unfortunately)
mentioned only one v1.0 firmware SKU and it wasn’t 1.25MB or 3MB. TXE kept changing at the
beginning so old firmware are not really credible. A perfect example of that is the fact that originally v1.1
firmware was supposed to be 3MB in size but with the first PV release (1.1.0.1089) that was changed to
1.375MB, a mixture between the Thin (1.25MB) and Major/Full (3MB) v1.0 SKUs. So for the exact
same reason, 1.1.0.1073 is not a credible TXE firmware. Here:
I also know that the versions & dates are completely messed up. For example:
Adding to the (already too much) confusion, firmwares 1.0.0.1058 & 1.0.2.1060 seemed to coexist at
some point for some reason. Even though the official 1.0.2.1060 has no mention of 1.0.0.1058 and the
1.0.0.1058 package does not mention 1.0.2.1060, at an early 1.0.2.1060 package we can see this:
On the other hand, all v1.1 dates make sense as far as I can see. Finally!
Generally: TXE has changed so much since the beginning (early 2013) and that makes it difficult to
understand it sometimes. Especially with no users reporting on whether the above are even working. I
was also wondering whether a special TXE is required for Bay Trail-T (Tablets) compared to Bay Trail-
M/D (Mobile/Desktop). That’s neither here nor there though so I guess I’ll find out at some point.
Sources (Kits & Documentation) containing 1.0.0.1058, 1.0.2.1060 (early), 1.0.2.1060 (release) &
1.1.0.1073: http://www.mediafire.com/download/sx3qbq…&_1.1.0.1073.7z
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 17/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Offset of sections:
I also noticed the date between 1.0.5.1120 and 1.0.6.1120. But your 1.0.0.1050 (3MB) is actually
1.0.2.1060 (3MB)
Say hello to TXE 2.0 Firmware, Tools & Drivers. These are for Braswell & Cherry Trail SoCs.
Updates:
Updates 05/06/2015:
Note: TXE 1.x firmware is different for Bay Trail Mobile/Desktop (BYT-M/D) and for Bay Trail
Tablet/IVI (BYT-I). All variants are now uploaded but 1.25MB BYT-I is not at the latest version of
1.0.6.1120. When I found it, it will be replaced.
Since there is no way to distinguish the two variants apart (BYT-M/D and BYT-I) via a tool such as ME
Analyzer: When you find a new firmware, try to mention from what SPI image (BIOS) it came as well or
which system. Preferably, attach the whole SPI/BIOS image for me to investigate.
Updates 08/06/2015:
Added Intel TXE FW Update Customer Communication v1.1.0.1113 (for page 12)
Updates 17/06/2015:
Thread:
Updated Intel FWUpdate Tool for TXE 2.0 Firmware from v2.0.0.2056 → v2.0.0.2060
Source:
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 20/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Update 29/06/2015:
* Updated Intel TXE 1.0 3MB Firmware BYT-I from v1.0.6.1120 → v1.0.7.1133
Update 09/07/2015:
NEW! Intel TXE 1.1 1.375MB Firmware BYT-M/D from v1.1.2.1120 → v1.1.3.1133
Source:
Hello
https://downloadcenter.intel.com/download/24892/
Updates 10/07/2015:
Updates 15/07/2015:
These are from 26/06 instead of 16/06 and include new compiled drivers of the same version with newer
digital signatures.
Updates 29/07/2015:
Updated Intel TXE 1.1 1.375MB Firmware BYT-M/D from v1.1.3.1133 → v1.1.4.1145
Updated Intel TXEI Drivers & Software from v1.1.2.1120 → v1.1.4.1145
Updated Intel TXEInfo Tool for TXE 1.1 Firmware from v1.1.1.1120 → v1.1.4.1145
Updated Intel TXEManuf Tool for TXE 1.1 Firmware from v1.1.1.1120 → v1.1.4.1145
Updated Intel FWUpdate Tool for TXE 1.1 Firmware from v1.1.1.1120 → v1.1.4.1145
Updated Bay Trail MD Intel TXE FW Release Notes from v1.1.2.1120 (09/2014) → v1.1.4.1145
(07/2015)
Added Intel TXE FW Release Customer Communication v1.1.4.1145 (07/2015)
Updates 30/07/2015:
Hi.
I successfully updated updated my baytrail tablet from 1.0.2.1060 3MB to 1.0.7.1133. I saw, that can it
be updated to 1.1, but i cannot find any tips how.
And another thing, ME FITC version is still old, how can i update that?
Thanks.
@ Jest:
FITC is a tool, you cannot “update it”. What ME Analyzer shows is the version of FITC that the OEM
used to modify the ME Region of your BIOS file. Nothing more, it’s just information.
You can upgrade to 1.1 firmware but not with FWUpdate. Only with FPT and only if your flash
descriptor is unlocked (error 26 should not be shown when running fptw64 -d SPI.bin for the latter to be
true).
@ Jest:
Yes, it’s locked. You could test the same with FPT but it doesn’t matter. The only way to upgrade now is
via an external programmer. It’s not worth all the trouble though. Unless you have programmer
knowledge, I suggest you just update to the latest 1.0 firmware. Normally it’s up to the OEM to do the
upgrade from 1.0 to 1.1 but that rarely happens.
I have Asrock Q1900M baytrail motherboard. Original came with TXE 1.0.2.1060 3MB and i did
update it to 1.0.7.1133. So i was curious if upgrade to 1.1 is possible.
TXEInfo shows
FW Capabilities: 0x20001040
Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.
If Error 26 shows, you have a locked flash descriptor. Only via a programmer can you upgrade from
v1.0 to v1.1 in such a case.
Updates 10/08/2015:
Just wanted to say that I was able to get my Lenovo laptop (has a Bay-Trail CPU) updated to the latest
firmware. It gave me a message about the OEM ID not being correct so I looked it up with TXEInfoWin
and then copied the OEM ID and used the command fwupdlcl64.exe -OEMID ID# -f TXE.bin
SimpleTech:
Just wanted to say that I was able to get my Lenovo laptop (has a Bay-Trail CPU) updated to the
latest firmware. It gave me a message about the OEM ID not being correct so I looked it up with
TXEInfoWin and then copied the OEM ID and used the command fwupdlcl64.exe -OEMID ID#
-f TXE.bin
Yes, that’s a common practice of Lenovo. ME Analyzer should show a note about the existence of such
an OEMID inside the BIOS (SPI) image. I’d like to verify it myself again, so can you tell me the model of
that Lenovo laptop?
Updates 26/08/2015:
Intel TXEInfo Tool for TXE 2.0 Firmware from v2.0.0.2073 → v2.0.0.2077
Intel TXEManuf Tool for TXE 2.0 Firmware from v2.0.0.2073 → v2.0.0.2077
* Intel FWUpdate Tool for TXE 2.0 Firmware from v2.0.0.2073 → v2.0.0.2077
Update 28/08/2015:
Can someone with a v1.1 system test if you can update to v1.2 firmware with FWUpdate tool?
plutomaniac:
Can someone with a v1.1 system test if you can update to v1.2 firmware with FWUpdate
tool?
I can’t, it complains about sku mismatch. I have an N2830 on a Toshiba which I think is BayTrail-M
I would like to try 1.1.4.1145 and see what that says but you seem to remove old versions.
I thought so. That’s what they did with v1.0 → v1.1 updating as well.
plutomaniac:
I thought so. That’s what they did with v1.0 –> v1.1 updating as well.
I can install that ok. I was on a really old version and was able to update to Intel TXE Firmware
v1.1.1.1130 (1.375MB BYT-I).rar & now 1.1.4.1145.
C:\Users\Password\Downloads>FWUpdLcl64.exe -f Production_VLV_SEC_REGION.bin
Warning: Do not exit the process or power off the machine before the firmware update process ends.
Sending the update image to FW for verification: [ COMPLETE ]
Error 8704: Firmware update operation not initiated due to a SKU mismatch
Whether it works or not is another matter, I got here because I don’t appear to have a TPM and all I
know about TXE comes from Wikipedia/google
"Intel TXT uses a Trusted Platform Module (TPM) and cryptographic techniques to provide
measurements of software and platform components so that system software as well as local and remote
management applications may use those measurements to make trust decisions"
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 30/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
My CPU isn’t listed in the baytrail md pdf, but I’m sure it is a baytrail m
7 Hardware and Software Compatibility • Intel® Pentium® N3510/ 3520 Processor • Intel® Celeron®
N2810/ 2820 Processor • Intel® Celeron® N2910/ 2920 Processor • Intel® Celeron® N2805/
N2806 Processor • Intel® Celeron® N2815 Processor
Intel says:
Intel TXT enabled BIOS, Authenticated Code Modules (ACM) created and signed by Intel inside the
BIOS, and Trusted Platform Modules (TPM) integrated onto the motherboard that provides securely-
generated cryptographic keys. This is a hardware-based mechanism that stores cryptographic keys and
other data related to Intel TXT within the platform. It also provides hardware support for the attestation
process to confirm the successful invocation of the Intel TXT environment. The attestation process uses
the TPM to establish mutual trust between parties regarding execution environment during runtime.
But TPM isn’t mentioned in my BIOS and Windows can’t find it, so it might be that I won’t actually be
able to use TXE even though device manager gives me a yellow warning sign if the driver isn’t installed.
It seems that everyone can update to everything in TXE (when being at the same minor version of
course). Maybe I’ll remove those BYT-MD and BYT-I firmware distinctions. I will upload 1.1.4.1145
again for all systems with v1.1 firmware. I guess, as before (v1.0 → v1.1), the only way to update is via
FPT + full TXE Region and not FWUpdate.
Intel TXT (Trusted Execution Technology) is not related to Intel TXE (Trusted Execution Engine). Similar
name but not related. Updating TXE does not give TPM capabilities.
plutomaniac:
Intel TXT (Trusted Execution Technology) is not related to Intel TXE (Trusted Execution Engine).
Similar name but not related. Updating TXE does not give TPM capabilities.
https://www.reddit.com/r/intel/comments/…d_do_i_need_it/
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 31/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
http://en.wikipedia.org/wiki/Trusted_Exe…Technology"
So TXE is a RISC cpu that does "security", like starlet on the wii.
plutomaniac:
Error 26: The host CPU does not have read access to the target flash area. To enable read access for
this operation you must modify the descriptor settings to give host access to this region.
It’s a lengthy process to do that. It requires read/write access to TXE Region which is usually locked for
security purposes. You can check if the flash descriptor is unlocked by running the commnd fptw64 -d
SPI.bin. If it reports Error 26 you have a locked flash descriptor and cannot perform that upgrade
without a hardware programmer and more advanced knowledge. If it dumps the whole SPI chip without
Error 26 then your flash descriptor is unlocked. In that case, you will have to use FITC to transfer all
settings from your current TXE firmware to the 1.2.0.1149 TXE Region and save a new 1.2.0.1149
image with your system’s settings (named for example TXE.bin). Then you can use fptw64 -f TXE.bin -
txe command to flash the new TXE region. All the FPT, FITC etc tools can be found at the System
Tools.
plutomaniac:
You can check if the flash descriptor is unlocked by running the commnd fptw64 -d SPI.bin. If it
reports Error 26 you have a locked flash descriptor and cannot perform that upgrade without a
hardware programmer and more advanced knowledge.
Yeah, it is locked. I have a programmer and some experience using it, but I’m not sure I need the stress.
What is TXE actually good for?
The only use interesting case I found for the predecessor (Intel ME) is remote kill.
https://recon.cx/2014/slides/Recon%202014%20Skochinsky.pdf
https://embedded.communities.intel.com/thread/7868
"Intel® Platform Trust Technology: Also referred as Intel® PTT, is Intel implementation of TCG TPM 2.0
specification in Intel® TXE FW"
No, you don’t have to do it. It’s not worth the trouble. Leave it at 1.1.4.1145, it’s just fine.
Also, ME is not a predecessor. It’s a different development tree for other systems.
plutomaniac:
No, you don’t have to do it. It’s not worth the trouble. Leave it at 1.1.4.1145, it’s just fine.
Also, ME is not a predecessor. It’s a different development tree for other systems.
I meant it came first and does a similar job. "In Bay Trail (Atom-based SoC), a new variation of ME is
used"
Is there any software that makes use of TXE that I might find useful?
Not that I know of. Especially TXE. It’s supposed to be hidden from the user, non intrusive. You have
updated firmware & drivers so you are good to go. Nothing more.
plutomaniac:
Just wanted to say that I was able to get my Lenovo laptop (has a Bay-Trail CPU) updated to
the latest firmware. It gave me a message about the OEM ID not being correct so I looked it
up with TXEInfoWin and then copied the OEM ID and used the command fwupdlcl64.exe -
OEMID ID# -f TXE.bin
Yes, that’s a common practice of Lenovo. ME Analyzer should show a note about the existence of such
an OEMID inside the BIOS (SPI) image. I’d like to verify it myself again, so can you tell me the model of
that Lenovo laptop?
plutomaniac:
Just wanted to say that I was able to get my Lenovo laptop (has a Bay-Trail CPU) updated to
the latest firmware. It gave me a message about the OEM ID not being correct so I looked it
up with TXEInfoWin and then copied the OEM ID and used the command fwupdlcl64.exe -
OEMID ID# -f TXE.bin
Yes, that’s a common practice of Lenovo. ME Analyzer should show a note about the existence of such
an OEMID inside the BIOS (SPI) image.
Could you put this info in ME Analyzer or on the start posting on how to achieve this (fwupdlcl64.exe -
OEMID ID# -f TXE.bin). Would be sad if such info is buried inside this thread
@ SimpleTech:
Lenovo: 4C656E6F-766F-0000-0000-000000000000
Lenovo: 00000406-0000-0000-0000-000000000000
Hello,
I’m trying to upgrade the firmware of a Asus T100TA (S) hybrid tablet with Windows 8.1 x32bit, I have
used ME Analyser and loaded the bios file (T100TASAS.213) but it returned error, so i do not know the
Intel TXE Firmware v1.0.x which two SKUs is: Thin 1.25MB or Full 3MB.
ASUS only provides the BIOS region for their mobile systems and not a full SPI (FD, BIOS, ME/TXE,
GbE etc). So MEA is telling you that it cannot find a ME firmware inside which makes sense.
You have a BayTrail-T system at v1.0 firmware. You can update to latter 1.0 firmware only under normal
circumstances.
To determine your SKU, make an Update image using FWUpdLcl -save TXE.bin command. Then drop
it into MEA. What does it report?
plutomaniac:
ASUS only provides the BIOS region for their mobile systems and not a full SPI (FD, BIOS,
ME/TXE, GbE etc). So MEA is telling you that it cannot find a ME firmware inside which makes
sense.
You have a BayTrail-T system at v1.0 firmware. You can update to latter 1.0 firmware only under
normal circumstances.
To determine your SKU, make an Update image using FWUpdLcl -save TXE.bin command. Then
drop it into MEA. What does it report?
plutomaniac:
@ SimpleTech:
Lenovo: 4C656E6F-766F-0000-0000-000000000000
Lenovo: 00000406-0000-0000-0000-000000000000
Crap, I’m in the process of selling off this notebook. Wish I could have saved the # for ya.
N6O7:
ASUS only provides the BIOS region for their mobile systems and not a full SPI (FD, BIOS,
ME/TXE, GbE etc). So MEA is telling you that it cannot find a ME firmware inside which
makes sense.
You have a BayTrail-T system at v1.0 firmware. You can update to latter 1.0 firmware only
under normal circumstances.
To determine your SKU, make an Update image using FWUpdLcl -save TXE.bin command.
Then drop it into MEA. What does it report?
Arrgh…those tools & commands only works when you’re on, with the Tablet!
My Z77 desktop computer gives results in "FWUpdLcl -save TXE.bin" with the bios of the
AsusT100TAS loaded (i’m working offline the tablet)…
I do not know if this TXE.bin is good in MEA or not, since it hasn’t run the command
"ME_Analyzer_Run.exe" on the tablet directly.
I’ll will report back when i will work on the tablet directly.
Thank you!
@ SimpleTech:
It’s ok. Not that important, support is already there either way.
@ N6O7:
I don’t understand. The Z77 system has nothing to do with TXE. The “TXE.bin” added at the end of the
command is just the file name. It could have been “file.bin” or anything else.
You need to download the FWUpdate v1.1 tool provided at the first post and run the -save command as
shown above. This has to be done at the Tablet. Like the TXEInfo picture you showed me before.
plutomaniac:
@ SimpleTech:
It’s ok. Not that important, support is already there either way.
@ N6O7:
I don’t understand. The Z77 system has nothing to do with TXE. The "TXE.bin" added at the end of
the command is just the file name. It could have been "file.bin" or anything else.
You need to download the FWUpdate v1.1 tool provided at the first post and run the -save
command as shown above. This has to be done at the Tablet. Like the TXEInfo picture you showed
me before.
Yeah, the first screenshot TXEInfo was direct on tablet…but i do not have the tablet at home now, only
at my Gfriend’s appartement.
I thought the run command could works on my Z77 Desktop with the Asus tablet bios!!
I’ve used on an Asus hybrid tablet the command FWUpdLcl -save TXE.bin to extract from the Bios file
the part that gives me the real SKU version of the Intel TXE firmware, Thank you Pluto for that tip!
It does show for Intel TXE Firmware v1.0.x a full Sku 3Mb
Guess now i’ve to grab this underneath to upgrade the tablet:
Thanks again!
Yes, exactly. You can update to the 3MB 1.0.7.1133 BYT-I image using FWUpdate tool. Afterwards,
run TXEInfo to see if everything is ok and also TXEManuf to verify health.
* Intel TXE 2.0 1.375MB Firmware v2.0.0.2077 from EXTR (dirty) → RGN (clean)
plutomaniac:
Yes, exactly. You can update to the 3MB 1.0.7.1133 BYT-I image using FWUpdate tool.
Afterwards, run TXEInfo to see if everything is ok and also TXEManuf to verify health.
Oky Doky…
TXE Info:
Hello
i was just wondering if there was a newer driver available for my thinkpad 8 tablet. the last bios update
updated the txe firmware, but the driver is still the same.
The latest driver (1.1.0.1064) can be found at the first post, section A1.
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 45/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
but isn’t that driver only for the 1.1.x firmware ? or is it downwards compatible with with the 1.0.x
firmware ?
No, v1 drivers are for all BayTrail systems whereas v2 drivers are for all Braswell/CherryTrail systems.
turns out that the 1.1.x driver package installs the same old driver.
and manually updating the firmware doesn’t seem to be possible as the thinkpad 8 isn’t unlocked, from
what i can tell.
There have only been 3 TXE 1.x driver releases since 2013:
At Device Manager > System Devices > Intel Trusted Execution Engine you should see the driver version
of 1.1.0.1064. That’s the latest, generally TXE very rarely has driver updates.
Any TXE 1.x system can be upgraded to latter minor releases so 1.0 → 1.1 → 1.2. However, the minor
version upgrade requires an unlocked flash descriptor and then custom work with Flash Image Tool and
Flash Programming Tool flashing. To detect is the flash descriptor is unlocked (almost never is on tablets)
you can run fptw -d spi.bin command via Flash Programming Tool. If you get Error 26 then you have a
locked flash descriptor and nothing more can be done via software solutions.
Where can I download: Intel TXE System Tools v1.0? Looking for a version of fptw.exe to work on my
baytrail tablet, but so far no luck with getting a proper version.
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 46/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Thanks in advance.
@ Arise:
Summary:
I made some major changes to how TXE 1.x is detected and categorized based on some recent findings.
Some firmware remained the same with a slight name change when others were wrong and got replaced
completely. In detail:
Note: The above firmware changes will be visible with MEA 1.4.x or later. It will be released in the near
future. The current version does not detect properly the M/D or I/T platform.
Hi,
@plutomaniac
I’ve updated the TXE fw of my stick (Meegopad T02) from 1.1.1.1130 -> 1.1.4.1145 without
problems, but the firmware in the first post for the IT SKU didn’t work (invalid or corrupted fw error),
so I tried the same fw from the post Intel Trusted Execution Engine: Drivers, Firmware & System
Tools (3) and it worked successfully.
I compared the checksum of the 1.1.4.1145 firmware from the link posted here, with the MD and the IT
from the first page and there’s no match.
Thanks!
@clio
Honestly, the difference between M/D and I/T same-version firmware is non-existent content-wise but
not check-wise. I have seen many people manually (programmer) flash M/D firmware on I/T platforms or
vice versa and it was working just fine. In general, TXE 1.x is such a big mess. Nothing like ME on that
regard.
Anyway, you need to update to the same firmware that your SPI/BIOS has, even if it’s “wrong” in theory.
If that’s what the OEM has flashed then that’s what you can update to. In your case:
So, from the first post you need Intel TXE 1.1 1.375MB Firmware v1.1.4.1145 BYT-M/D.
Hi @plutomaniac ,
Maybe I expressed myself wrong,
What I tried to say was:
I downloaded the 1.1.4.1145 from the first page, but when I tried to flash it, it gave me an “invalid or
corrupted fw error” so I downloaded the fw from the linked post and it worked.
So I verified the checksum of the 3 files and the 3 files are different so I’m guessing that the fw on the first
post is corrupted.
Edit: seems that the files are good and the eMMC is failing. Sorry
PD: ME Analyzer capture (In 1.3 the TXE is recognized as I/T and in 1.4 as M/D or am I wrong?)
clio:
Edit: seems that the files are good and the eMMC is failing. Sorry
That’s good. I was about to start smashing my head against a wall. Such an error would make no sense.
MEA v1.4.x or later is needed to see the major changes I made to TXE detection which is not yet
available. That’s the correct output:
MEA DB:
2.0.4.3098_1.375MB_PRD_RGN_6B019FD754326AA6D9D814BC43CA6C5B53A0CA1F_SHA
1
MEA:
1.0.9.1153_3MB_MD_PRD_RGN_034EC998D64100D4DD9AE25FA1C4568D4A3EAB9E_SHA
1
Note: Version Control Number (VCN) was increased to 14. No downgrade via FWUpdate possible
after updating.
MEA:
2.0.4.3100_1.375MB_PRD_RGN_521192D87B3BDB8066FE781DF30113073C9F3497_SHA1
MEA:
1.1.4.1148_1.375MB_IT_PRD_RGN_D0063651E2297EFE7820C882A0F90E6EACB807B5_SHA
1
MEA:
1.2.1.1161_1.375MB_MD_PRD_EXTR_3F1ABE9F9DB1BA208024EACA5A27807E379C3605_
SHA1
For Apollo Lake systems which come with TXE firmware v3.0
MEA:
3.0.0.1083_CON_BX_PRD_RGN_7C3D339ACE542A9B2BEEB24506FF95345EC092E3_SHA1
Note: Version Control Number (VCN) was increased to 15. No downgrade via FWUpdate possible
after updating.
MEA:
1.0.3.1164_3MB_IT_PRD_RGN_306FB567B168C64BFE28A9A18BA38339151838CB_SHA1
Note: Version Control Number (VCN) was increased to 6. No downgrade via FWUpdate possible
after updating.
MEA:
2.0.5.3105_1.375MB_PRD_RGN_9EBD187744F882AA57B704068F8E3D97327B2E58_SHA1
Thanks to Intel for the new firmware as well as Pacman for letting me know!
Dear plutomaniac,
I have a hardware programmer so I can play with different versions, etc… If you need me to try
something, I am here to help.
When I clean TXE bios, FITC version is other and I would like to try with same FITC version please.
http://www.mediafire.com/file/eo8nk60ni708w5y/BIOS.rar
Thank you!
@ razor_amd:
I do have 1.1.0.1089 FITC but it won’t change anything, the problem should not be there. You need to
clean the original system dump and not the stock decrypted SPI from HP. You didn’t mention what HP
model that is but you said notebook so I selected that at FITC to do some quick comparisons. Based on
your dump (Backup Beli main u56-w25q64fw), I created an equivalent SPI image with clean/configured
TXE. Additionally, I have disabled Anti-Theft (as the guide says, not the root of your problem though)
and disabled the Flash Descriptor protection so you can reflash the entire SPI from within an OS instead
of the programmer provided that a) the system boots and b) that’s needed for something else (like
upgrading from TXE 1.1 to 1.2 if you want). You can easily re-enable the write protection lock if you
desire so after all modifications and repairs are done. After flashing with the programmer, if the system
doesn’t start and since you cannot do that easily using an OS and Flash Programming Tool, try to reset
the TXE by removing any power (cable, batteries) for 1 minute or so.
The notebook model is also written in a bios file inside. It is HP 250 G3 notebook, bios ID is: 0220F.
Yes, I get that I need to clean TXE in a bios already in a notebook. But in a 99% cases, the notebook
won’t turn on with a bios already inside, it is somehow corrupted, etc, so I must either program a fresh
clean bios from manufacturer’s site or a dump from other same or similar notebook downloaded from
various forums.
For that reason I can’t always use that backup image from a notebook so I downloaded file:
BIOS_F18.bin. I tried to clean TXE in this file also but when it wouldn’t work, I deleted it. Then I only
changed notebook info and serial number and call it: BIOS_F18 za belog.bin and the notebook works
with it. The one thing I didn’t try is removing all the batteries, including the little one for bios for 1 minute
to reset TXE. I will try your cleaned TXE bios and see how it goes. Will let you know.
I have uploaded complete backup bios files from other notebook that works, untouched. In there is a
Main bios and EC bios of the same board. The other link is HP website, to download bios update for this
notebook model.
1
2
https://drive.google.com/file/d/0B04G7U5l329dZnBpcXptWUZ6bms/view?usp=sharing
http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=6732463&swItemId=ob
One more question I would like to ask you. When I download bios file from manufacturer's website, in
this case it is 0220F.bin (after decryption), is it already a clean ME/TXE one? I think it is, because it has
never been used before on a system and thus it doesn't have any data initialization in it. Please let me
know if I am wrong.
Well yes, it’s BIOS-related then. The TXE cleanup you and I did as well as FITC version used should
not be related. I cannot currently download the archive from google drive as the service is unresponsive
(probably related to that global DDOS attack that has been going on today). If you used another BIOS
and it now works, you may not need to do anything more.
And yes, in theory the TXE inside the stock HP SPI image should be clean+configured, meaning non-
initialized. I said “in theory” because not all OEMs care enough to do that. HP should be ok but some no
brand Chinese motherboards may come with initialized Engine firmware taken from another system.
That’s why I generally follow the guide regardless. It’s best to first try the one by the OEM and if not,
follow the cleanup process manually if you don’t trust their release.
No worries, I flashed the one I already prepared from another forum and the notebook is working for
now. Thank you very much for the info!
Thank you Pacman for the new firmware. Unfortunately, it seems Intel liked the crapfest that was TXE 1
and decided to extend it. This “newer” branch is older than the last 2.0 firmware we have. To me it seems
like a 2.0.4.3102 firmware which was especially/custom ordered or something and has a minor of 1
instead of 0. Or maybe an early 2.1 branch sample that later got abandoned. I don’t know what sort of
device came with such firmware but it’s 10 months old, older than 2.0.x and haven’t seen any such
branch all this time. I’ll put it at the repo and MEA but I advise people against updating to it. For the
aforementioned reasons and because Intel has started to become very annoying when it comes to SKU
confusion and firmware obfuscation, this 2.1 “branch” will not be at the first post.
Yes, the date caused me some confusion, but i thought i would post it anyway since i have not seen it
Before.
It is from an Asus device, don’t remember wich one, but if there is any need i can recheck the Asus
BIOSes i downloaded yesterday.
Hi @plutomaniac ,
I am having problems with the Flash Image Tool from the Intel TXE System Tools v2 r1 package. It is
not able to extract the regions on loading the BIOS image from a Gigabyte Brix 3150.
I’m probably doing something wrong but I have attached the BIOS file in case you would like to take
a look.
Thanks for the great tools and for all your work.
@plutomaniac ,
I have re-downloaded the tool and it works now, must have been a bad download.
It seems that Intel has two branches for TXE2 which follow the same SKU, Date and VCN. The details
of 2.0.5.3105 and 2.1.5.3105 prove that. Why, I don’t know. I’ve now added the 2.1 branch for
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 66/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
whoever currently has v2.1 firmware at his/her system. No change for MEA as that was implemented in
v1.6.8 two months ago. It would be interesting if someone could test “updating” from 2.0 to 2.1 via
FWUpdate which will probably not be allowed based on past TXE experiences.
Warning: Do not exit the process or power off the machine before the firmware update process
ends.
Sending the update image to FW for verification: [ COMPLETE ]
Error 8704: Firmware update operation not initiated due to a SKU mismatch
Intel TXEI Driver v3.0.0.1115 (Windows 8.x & Windows 10) INF
Intel TXEI Driver v3.0.0.1115 (Windows 7) INF
Intel TXEI Drivers & Software v3.0.12.1138
I have an Asus x540sa (Intel N3700), I regularly update my BIOS firmware but one day I saw in the
device manager that Intel Trusted Execution Engine did not start (Code 10)
STATUS_DEVICE_POWER_FAILURE, I talk to ASUS and they did not give me a reply so I used this
forum To update the firmware and correct the error, I did it and it worked perfectly. THANK YOU!
Yesterday a new BIOS update was released with the following description:
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 68/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
BIOS 304
Update TXE FW 2.0.2.2092
I apply the update but TXEInfo still shows the firmware installed by me (2.0.5.3109) and not the one that
would be supposed to be (2.0.2.2092), I attach an image, my question is: Is there any error in my system
or everything is correct ?
[[File:Captura de pantalla (4).png|none|auto]]
@plutomaniac
Hi Plutomaniac,
I am having problems with an X5 Z8350 mini PC, specifically with audio output and LAN and I thought
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 70/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Edit: I updated the firmware to 2.0.5.3109 and have the same situation (Invalid global FPF) but no error
is shown.
I see that you have read/write access to the TXE Region. To rule out TXE, follow the CleanUp Guide
with 2.0.5.3109_1.375MB_PRD_RGN and reflash. After the “fpt -greset”, try again with the latest
MEInfo and MEManuf.
@plutomaniac :
tried but something went wrong after the -greset command.
now something is badly corrupted and cannot access BIOS anymore while all TXE tools are not working
anymore.
Edit: after having reflashed the BIOS the tools are working again although I still cannot access the bios
Not being able to access the BIOS or similar issues have nothing to do with TXE. As long as you
followed the CleanUp guide and reflashed TXE firmware properly, everything else falls into
BIOS/system-specific category. Try a clear CMOS and keep the system off and without AC/battery
power for 1 minute or so. If that does not help, I suggest you reflash the latest SPI image (FD + ME +
BIOS etc) from the OEM.
Intel TXEI Driver v1731.4.0.1199 (Windows 8 & Windows 10) INF for manual installation
Intel TXEI v1731.4.0.1199 Drivers & Software
Note: TXEI v4 driver versions start with the year & week of release (example: 1731 → 31st week of
2017).
Hi!
First of all thank you for this amizing forum. I was able to upgrade nearly all of my devices to the latest
firmware (TXE and ME).
Only one Tablet/Slim Notebook is resiting all of my efforts for a firmwareupgrade. It’s is using an old 1.0
version and I’m a little bit concernd that it’s not safe.
Therefore I have some questions.
According to TXEInfoWin the “Local Firmware Upgrade” is disabled. In the BIOS-Menu I can’t find
anything regarding “TXE”. No “allow BIOS upgrade” or whatsoever. The only option which comes near
is “Secure Boot”.
Is the “local firmware upgradeability” somehow related to secure boot? So only a “credible” OS can
change the firmeware?
Is there a way to switch the “Local Firmware Upgrade” option in the TXE to enabled?
In the first post of this thread there is mentioned a “Upgradeability” for TXE 1.x to as high as 1.2 using
the FPT.
Is there a guide how to achieve this?
The device is quite old so there is no newer bios or any other support from the manufacturer. Only some
quite old device drivers.
wkr
ADT
@ a-dead-trousers:
It has nothing to do with Secure Boot. Local Firmware Update (FWUpdate) can be sometimes
disabled from the BIOS but that doesn’t mean that the OEM left the setting available for the users to
adjust. Either way, you cannot use FWUpdate to update TXE 1.0 firmware to 1.1 or 1.2. A custom
reflash of the entire TXE region (EXTR) was required for that generation. With FWUpdate you can
just update to the latest 1.0 firmware only. In your case, that option is disabled as well. If your system
happens to have read/write access to the TXE region of the SPI chip, you can upgrade via Flash
Programming Tool. Run “fptw -d spi.bin” command. Does it complete successfully or do you see
CPU/BIOS Access Error or similar? If it completes successfully, you can follow the CleanUp Guide
and at step 4 select the latest TXE 1.2 firmware. If it fails, you have no read/write access to the TXE
region. Maybe we can enable some potentially hidden BIOS option though which will allow temporary
read/write access there, provided that you can boot in an EFI shell. In that case, you can dump the
BIOS region only by “fptw -bios -d bios.bin” and then compress & attach it here.
Ok, thanks. I will try your suggestions next weekend when I’ve got some spare time (holidays and so on
)
@plutomaniac
Now I found some time. As you predicted the SPI chip is not accessible using Flash Programming Tool.
The command "fptw -d spi.bin" results in "Error 26: The host CPU does not have read access to the
target flash area. To enable read access for this operation you must modify the descriptor settings to give
host access to this region.". Therefore I tried to dump the bios with "fptw -bios -d bios.bin" and was able
to do so even without an EFI shell. I hope thats´s ok and nothing of value is missing.
The EFI shell is required for the next step (setup_var manipulation), if a hidden BIOS option exists and
actually works. I found a few interesting BIOS options which I assume are hidden from the menus.
We are interested in “TXE HMRFO” to allow Read/Write access to the TXE region and thus upgrade to
1.2 firmware. We are also interested in “TXE Firmware Update” which will allow FWUpdate usage, if
required.
Follow these steps but at step 3, change the variable to the one you want. For example “setup_var
0x170 0x01” to enable HMRFPO. You should then be able to dump the SPI chip.
No success.
Right after the reboot both values (0x170 and 0x171) are back to being 0x00 instead of 0x01.
I tried the command multiple times to confirm that it is set to 0x01 but after a reboot it’s back at 0x00.
Try the attached tool with command “/UnlockTXE”. If that works, it also has command
“EnableTXEFWU”.
Although quite scary (the pc suddenly shutting down) it worked and I was able to dump the SPI chip.
Then I followed your cleanup guide and I’ve got the outimage.bin but what to do with it? Your guide is
missing the “how to actually flash the new bios” part.
I tried with Flash Programming Tool but this gives me "Error 286: Unable to write data to flash with SPI
lock enabled."
To check this I tried to flash an older bios from the vendor (using InsydeFlash) but this also fails during
boot. So I think I have to enable one more small thing using BootMode or another tool.
So the tool works for your machine, good, you’re lucky. You can flash via Flash Programming Tool.
Command “fptw -f outimage.bin” followed by “fptw -greset” is enough in your case. As for SPI lock, it
is possible that “UnlockTXE” deals only with the TXE region of the SPI chip so, with only that option
enabled, one would have to prepare an Engine (TXE) region only image at the CleanUp Guide. Since I
see there are some other options at BootMode such as “EnableBIOSLock” and “InFactoryMode”, try
the former one, it will probably work afterwards.
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 76/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
A quick update:
I succeeded to disable the BIOS lock and to flash the new image. But now the laptop won’t boot
anymore, so I asume I did something TERRIBLY wrong. Currently I’m searching for a way to flash the
original BIOS without an actually working BIOS. The chip is soldered to the motherboard and the device
is quite old so I don’t want to go through the hassle of disasamble everything just to find out I made it
worse during the process.
I found a guide where it’s mentioned that you can use a FAT formatted USB drive containing the BIOS
and a special button combination to flash the bios in a kind of emergency mode. Unfortunately the guide
only mentions HP, Acer and Asus devices but not Lenovo. You don’t happen to know something about
Lenovo, do you?
From the test I made with that tool on Lenovo T410 laptop with all commands I try:
/InFactoryMode - Set machine in factory mode
/DisableBIOSLock - Disable BIOS Lock
/UnlockTXE - Set the Flash Descriptor Override strap
/EnableTXEFWU - Enable TXE FW local update
All comands are reported as SUCCESSFUL but it can’t disable ME lock region for me to be able to
program DESC unlocked or dump ME region.
Maybe you program BIOS with the full flash dump ME+GBE+BIOS… or with TXE firmware ?
@ a-dead-trousers:
Can you upload your original and modded dumps to see what possibly went wrong?
From some older Lenovo system with TXE firmware. It worked for a-dead-trousers (similar?) system
but it doesn’t mean anything for other models. Don’t get your hopes up, this is for specific cases.
@plutomaniac
Do you have something / know if it is possible to unlock flash descriptor for old Lenovo T410 without
external intervention to chips ?
thx
@plutomaniac
Here are my two files. Had to find a way to backup the harddrive first. Through USB to SATA bridge I
wasn’t able to read the GPT format.
The cleaned/updated SPI image (outimage.bin) is proper, you did everything correctly. So either
something went wrong during flashing or there’s some security measure in place. Since Intel BootGuard
was not a thing at Bay Trail systems, I don’t think it could be something else. Did the flashing complete
properly?
Have you tried removing all power from the machine (AC + Battery) for a few minutes (press the power
button a few times while the system is off)? If that does not help, try removing and re-inserting the
memory modules (make sure you put them back correctly) in case the problem is bad BIOS cache.
Flashing did not show any problems at all and everything you mentioned to solve the problem I already
did. Except removing the memory modules because they are also soldered to the motherboard. Even the
CMOS battery is soldered but at least not so well, so I was able to remove it. The system was without
any source of power for nearly half an hour and that didn’t help either. So I’m also convinced, that there
must be some sort of (hardware?) security measure. Anyway, thanks for the assurance that I didn’t do
something wrong (except of trying to change the firmware in the first place). At least I can stop doubting
myself and enjoy the christmas holidays.
It’s a shame that the machine no longer boots. No matter what, I wish you a Merry Christmas and happy
new year as well a-dead-trousers. Personally I don’t believe that your original though to update it was
misguided but I suppose you’re unlucky and stumbled upon some sort of Lenovo security measure or
flashing mishap. For now you should definitely enjoy the holidays but if you manage to resolve the issue
and possibly figure out what went wrong, please let us know so that the same thing won’t hopefully
happen to other people in the future.
Thank you for your kind words. I don’t think there is a point in doing that for multiple reasons. No matter
what, I would expect people to at least have a source link to the original forum thread.
TheGiolly:
There aren’t any in this thread because Intel no longer has a FWUpdate tool for CSTXE-based Atom
platforms (APL, GLK). The official update methods are either via OEM BIOS updates (Capsule) or
when the system is in Download & Execute (DNX) mode. Another issue is that CSTXE is usually
partially signed by the OEM and their RSA Public Key + Exponent hash is stored in the SoC (hardware,
FPF). So, on such images, you cannot update the CSTXE firmware without the OEM Private RSA Key
without the platform rejecting your new image. This is what I’ve understood but someone can correct me
if I’m wrong.
Hi! I’ve read the thread and made a conclusion that I can’t update TXE on my laptop by myself.
plutomaniac:
Intel no longer has a FWUpdate tool for CSTXE-based Atom platforms (APL, GLK)
Smartpol:
Hi! I’ve read the thread and made a conclusion that I can’t update TXE on my laptop by myself. I
can do it only by updating bios, if my laptop manufacturer provide me updated bios, isn’t it?
Usually yes, only if the OEM has an updated SPI/BIOS. But it can also depend, what laptop model are
we talking about?
plutomaniac:
Usually yes, only if the OEM has an updated SPI/BIOS. But it can also depend, what laptop model
are we talking about?
Laptop model is Jumper EzBook 3 Pro - cheap chinese laptop from aliexpress. I think, that I wouldn’t
have any BIOS updates from manufacturer (I try to request it, but no luck ). My aim is to eliminate
intel-SA-00086 vulnerability by updating/editing bios of my laptop. Is there any chance to get TXE
updated or disabled for my laptop?
@ xingyou12:
The FITC version does not matter as it’s the tool which adjusted the firmware settings.
@ Smartpol:
Do you have read/write access to the SPI/BIOS chip or a programmer which you can use? Please
compress & attach a SPI/BIOS image for that model to see if the OEM used signing.
plutomaniac
Hi! Thanks for quick reply! I can use AfuEfix64.efi (I successfully made BIOS update with /P and /B
keys for latest available BIOS, which I found at techtablets.com, but intel SA-00086 is still there ).
The image of that BIOS is here 09_30_17_BIOS.zip in zip. I have ch341a programmer, but doesn’t
sure, that it is compatible with my BIOS chip.
@ Smartpol:
The CSTXE firmware is signed but, in your specific case, not with an OEM key so hopefully I’ve
updated it with CSTXE 3.1.50.2222 and re-signed it properly. I cannot guarantee that it will work but I
think it will. So if you decide to test this, I suggest to make sure that you can recover via the programmer.
I tried to update BIOS in built-in UEFI shell using “AfuEfix64.efi 09_30_17_BIOS_fix.bin /P /B”
command as I did at previous update, every part of the updating process gave me ‘OK’ or ‘done’ result.
After turning my laptop off I tried to turn it on but there was only black screen with power led light on. I
think, that recover via the programmer is necessary but at first decide to try unplugging laptop battery.
After this I try to power it on several times with strange behavior of power led without any display activity
and viola! I got my laptop working with latest TXE firmware without intel SA-00086 vulnerability!
Amazing! Big thanks for your help, plutomaniac!
Oh that’s great, you’re the first person to have updated the CSTXE 3 firmware in this forum since 2016,
partially due to the fact that your SPI is not really signed. Yes, after reflashing the CSTXE firmware, the
system must be reset. You can either do it by running “fptw -greset” after the reflash or manually by
removing all power for 1 minute or so (AC + Battery, RTC is ok). Sometimes both are required and a
few power on attempts to kick start the system again. So you did great as your perseverance to power it
on proved that the signing worked.
By the way, aside from the updated CSTXE 3.1.50.2222 firmware which fixes INTEL-SA-00086, I
also updated the CPU Microcode in order to add hardware fixes for Spectre variant 2 vulnerability
(INTEL-SA-00088).
1. Thank you a lot for your offer. You can find a Paypal Donation button at my ME Analyzer or MC
Extractor readme files over at github.
2. Yes of course.
Thanks again, plutomaniac. I’ve just send you some support and thanks via paypal
Thank you very much Smartpol for your contribution. Enjoy your firmware-upgraded system!
Hi @plutomaniac
Can I ask you where did you find the CSTXE 3.1.50.2222 that you used to update that BIOS?
Thanks
@TheGiolly
At the Engine Firmware Repositories you can now find CSTXE 3 & 4 packs. I will also update the
Engine CleanUp Guide with CSTXE instructions so that the user can check if their firmware is OEM
signed. If it’s not signed, the procedure remains the same but if it is, the user will need to input the OEM
Private Key used during signing which of course is not public but the instructions will be there in case
someone has it.
Is there anyway to update CSTXE firmware without a backup bios? (if not is there anyway to backup a
laptop’s bios)
I have an Apollo lake laptop (Yepo 737A) that’s similar to the Jumper Ezbook in the previous post but
unfortunately I couldn’t find a bios online.
zyo:
Is there anyway to update CSTXE firmware without a backup bios? (if not is there anyway to
backup a laptop’s bios)
I have an Apollo lake laptop (Yepo 737A) that’s similar to the Jumper Ezbook in the previous post
but unfortunately I couldn’t find a bios online.
There is no way to update CSTXE firmware without BIOS image. So if you can’t find it online, you
should do BIOS backup to obtain it. If you can boot to built-in UEFI shell (as in Jumper), you can do
BIOS backup by AfuEfix64.efi utility with this command "AfuEfix64.efi backup.rom /O". More
information about it and your laptop you can find at Techtablets.com.
Thanks, I have backed up the firmware, can anyone help create an updated version?
https://nofile.io/f/d3dn2feEZ0T/backup.bin
@zyo
Your image is OEM signed. However, I have made an attempt to update the CSTXE firmware using a
new method. I cannot guarantee that it will work but I think it will. So if you decide to test this, I suggest
to make sure that you can recover via a programmer.
Thanks, I dont really have a programmer to recover in case this goes bad. I recall seeing someone at
techtablets flashing a Jumper Ezbook 3 pro bios onto a Yepo 737A laptop I wonder if it’s OEM signed
how they can do that without bricking…
From the two SPI images I’ve seen, the RSA Keys are different. The real question is whether these
OEMs actually closed Manufacturing Mode at their factory in order to commit the RSA Public Key Hash
at the Chipset hardware (FPF). Run “TXEInfo -verbose” and show me the results.
CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
SPI Flash Log: Not Present
Phase: BringUp
TXE File System Corrupted: No
PhaseStatus: UNKNOWN
FPF and TXE Config Status: Not committed
FW Capabilities value is 0x31109040
Feature enablement is 0x31109040
Platform type is 0x73FF0321
Intel(R) TXE code versions:
FW Capabilities 0x31109040
ManufacturingMode: Enabled
FPF and TXE Config Status: Not committed
Host Read Access to TXE Enabled
Host Write Access to TXE Enabled
End of Manufacturing Enable No
OEM Public Key Hash FPF Not set
(all FPF are Not set)
All of the above indicate that, although the SPI/BIOS image is signed, the signature was never
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 90/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
hardware(FPF)-committed by the OEM. So you can do whatever you want, even commit to FPF
yourself with your own key or whatever (why though?). You can thus follow the Engine CleanUp Guide
and at step 7, just remove the OEM Public Key Hash to disable Signing. The platform should accept that
change because the FPF are not committed. At the above fixed SPI I attached, I’ve updated the CSTXE
firmware to the latest 3.1.50.2238 as well the APL CPU Microcode for Spectre Variant 2 mitigation.
I’d like to emphasize that the above portray my own understanding of the situation. Although, to my
knowledge, nothing should be capable of blocking the update, the risk of flashing is always on the
modder.
Thanks for the explanation much appreciated, I will try flashing the bios tonight.
Just to clarify, is there anything I need to do prior to flashing? Do I just need to load the firmware onto a
USB drive and flash it using afuefix /p /b in EFI shell
Yes, you can flash it via AFU. After flashing, you may need to remove all power (AC + Battery, RTC is
ok) for 1 minute or so and in the meantime, press the power button 1-2 times as well. The system should
boot. If not, try to a few things like discussed here. Once it’s up, run Flash Programming Tool with
command “fptw -greset” for good measure and after the system reboot, everything should be updated
and operational.
That worked, the SA-00086 as well as Spectre are patched. Meltdown still remains, I thought the
Microcode update would have addressed that?
Only Spectre Variant 2 requires a microcode fix. Meltdown, Spectre Variant 1 and Spectre Variant 2 rely
on OS-based fixes.
Note: Added instructions on how you can update the CSTXE 3 & 4 firmware-based platforms (CSTXE
3 - 4 Updating).
Hi, plutomaniac. Can you take a look at this BIOS: Teclast F7 rom. It’s not OEM signed and can be
fixed against intel SA-00086 and 88 or not?
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 94/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
ME Analyzer told me, that there is OEM RSA Signature, but in previous case this signature was not a
problem.
Thanks, I’ll make a try. As I understand, this guide is about updating TXE Engine. And how about CPU
microcode updating - is there any guide for this process?
For solely IFWI based platforms like APL & GLK, updating the microcode is very easy and can be
done via Flash Image Tool, just look for the option after the Engine CleanUp Guide procedure, before
building the final image.
Thanks again, plutomaniac. I successfully made CSTXE 3 updated bios for my Teclast F7. But after fpt
-greset my notebook always booted to recovery tab in bios (never showed before). It boots normally
only after flashing updated bios again. Can’t say anything about reason of this strange behavior.
But I can’t find any options to microcode update:
plutomaniac:
just look for the option after the Engine CleanUp Guide
If you re-flashed a dumped BIOS region, it could lead to NVRAM corruption or similar. It’s best to take
the stock SPI image to avoid that. The CPU microcodes are found at Flash Layout > uCode Sub-
Partition. However, these are not CSTXE related.
First I flash modified BIOS with updated CSTXE engine in built-in uefi shell using "AfuEfix64.efi
updated_bios.rom /P /B", where updated_bios.rom was renamed outimage.bin, which I got by step-by-
step doing Engine CleanUp Guide. After this command I put next: "fpt.efi -greset". After that notebook
was rebooted to recovery tab in bios. BIOS also told me, that TXE engine version is N/A. When I exit
bios without saving anything, windows is booted without any issues. But every boot I begun with
recovery tab in bios, until I flash modified bios again in built-in uefi shell with "AfuEfix64.efi
updated_bios.rom /P /B" command. Then BIOS said, that TXE engine version is 3.1.50.2222 and no
recovery tab in BIOS now. Is now everything OK or not? How I can check NVRAM corruption? Intel
SA-00086 detection tool said me, that my system is updated and TXE engine version is the same
3.1.50.2222 as in BIOS.
This is AFU or BIOS-specific behavior, not CSTXE or CleanUp Guide related. If it works after these
steps then you are good to go.
I understand, that it’s not CSTXE or CleanUp Guide related. Thanks a lot for your explanation. It works
now and thanks again for these very useful guides and firmwares!
Is there someone with an Apollo Lake system to do some safe and quick tests? I’m fairly certain that
CSTXE 4 (GLK) tools are also compatible with CSTXE 3 (APL) systems. We can test this by running
TXEInfo -verbose and TXEManuf -verbose.
I want to thank you for your work, plutomaniac. I was able to resolve an issue that plagued my Asrock
N3050M since I bought it, just by updating its TXE firmware, by running fwupdate with the appropriate
RGN image. The system always froze when I rebooted it, after days or weeks of uptime. The Asrock
support failed to help me, they just blamed my unsupported OS (Debian). Thank you.
gpvecchi:
Yes but I don’t remember if FWUpdate tool can do that or if you need to do it manually via Flash
Programming Tool and a pre-configured TXE firmware via Flash Image Tool. You can try FWUpdate
and if it doesn’t allow that, you’ll know that it can only be done manually. By the way, I’m not sure what
the rational was, but v2.0 and v2.1 are different branches so it doesn’t mean that v2.1 is newer than v2.0,
just different in some way. For example, the current latest v2.0 is much newer than the current latest v2.1
that we have found. So, I don’t know. Personally I would stick to v2.0 firmware if my system has v2.0
out of the box.
I’m not sure. It could be an incompatibility between the old firmware and the newer MEInfo tool version.
Check the TXE status via “-fwsts” parameter. Run MEManuf as well.
I can confirm that i updated successfully a Greek laptop Innovator Aether Slim V141 (z8350) with insyde
bios uefi.
Txe version updated from 2.0.0.2075 to v2.0.5.3117.
can anyone say what this option actually does "Unsolicited Atttack Override PAVP" (enable/desable)
default=enabled
1 Like
new txe version 2 driver Intel Trusted Execution Engine Interface Braswell/Cherry Trail 2.0.5.3117
WHQL:
-https://we.tl/t-TgMq6LoA3T
The most time i found the laptop stuck with a black screen.
I resolved it with TXE EOP Message bios option from enabled to disabled.
1 Like
I have to admit i don’t understand how to put a recent TXE 4 firmware in a flashable file for my ASRock
J5005.
There is an existing BIOS online that updates the TXE https://www.asrock.com/mb/Intel/J5005-
ITX/index.de.asp#BIOS
I wonder if i overlooked a howto somewhere that explains how to update the TXE part of this file for
such a case?
Error 7: [SMIP Controller] Invalid Manifest Extension Utility path. Manifest Extension Utility path set to:
''
Error 6: [SMIP Controller] Failed to sign SMIP data.
Error 37: [Ifwi Actions] Failed to build SMIP data.
Error 19: [Ifwi Actions] Failed to prepare OEM SMIP data.
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 118/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
Error 12: [Ifwi Actions] Failed to prepare one or more IFWI components.
Error 15: Failed to build.
Failed to build!
Hello, I used Intel cstxe system tools V4 to clean up the me area and build me. How to solve the
problem
As reported 3 posts above a rebuild using Flash Iamge Tool 4 for my GLK with a different TXE moves
the offset of the µC.
This only happens if the TXE is a EXTR file. Putting in the different RGN versions does not change the
µC offset on rebuild.
I hope this observation is new and is of some help for something.
1 Like
thanks master
Notice that (CS)TXE seems to have been killed off by Intel and merged into (CS)ME. Modern
Atom based platforms now run CSME firmware (LKF - CSME 13.30, JSL - CSME 13.50, EHL
- CSME 15.40 etc). The current (CS)TXE platforms (BYT, CHT, BSW, APL, BXT, GLK)
remain as they are.
I successfully upgraded PiPO-X7s TXE 1.375MB M/D v1.1.1.1120 to TXE 1.375MB M/D
v1.1.5.1162. Using FWUpdLcl -f 1.1.5.1162_1.375MB_MD_PRD_RGN.bin command.
I can’t figure out. Can I upgrade to TXE 1.2 1.375MB M/D v1.2.1.1161. For sure you can’t upgrade
to TXE 2.0 1.375MB v2.0.5.3117!
Strange TXEI Driver v2.0.0.1094 (Windows 7, 8, 10) drivers don’t work on PiPO-X7s. I checked
.inf file and hardware ID is only available in Windows 10 section. Missing for Windows 7 and 8.1 (NT
6.1).
I have found working drivers TXE_Win_64_1.1.5.1162 (Intel® Trusted Execution Engine Interface
2014.01.12 1.1.0.1064) on Intel® Trusted Execution Engine (Intel® TXE) Driver for
DN2820FY, DE3815TY site.
Coool:
I checked .inf file and hardware ID is only available in Windows 10 section. Missing for Windows 7
and 8.1 (NT 6.1).
I have adjusted Section A for TXE 1 on old Windows OS. Thanks for the feedback.
Coool:
That doesn’t make sense. Please read Section C to understand what Flash Image Tool is.
As I understood Intel Flash Image Tool (FITC, FITc or FITC.exe) is tool which was used to flash
BIOS initially? But I updated TXE with FWUpdLcl (Intel Firmware Update Utility Version: 1.1.5.1162).
Why info wasn’t updated?
What is difference between TXE 1.375MB M/D and TXE 1.375MB I/T?
FIT is a tool, the tool used to build/configure the firmware. It is not something you update, ignore it. TXE
1.2 is technically compatible with 1.1 but it’s a different branch which existed for some reason on a very
small number of devices. M/D and I/T are different SKUs. You are up to date, nothing more to do.
Warning: Do not exit the process or power off the machine before the firmware update process ends.
Sending the update image to FW for verification: [ COMPLETE ]
Error 8704: Firmware update operation not initiated due to a SKU mismatch
Is it possible to upgrade with Intel Flash Programming Tool (fptw.exe). Only I don’t want to
corrupt TXE DATA Region (configuration stuff). Do I gain any benefit? Generally all TXE stuff is one
security concern :).
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 132/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
CSTXE 4 v4.0.32.1524
CSTXE 4 v4.0.40.1600
Hi Marvin, I restored the original post content because I wanted to emphasize my appreciation for
people who look out for newer firmware and report them here, no matter if this was already present at
the mega link from a few days ago. The latter won’t always be the case, so I needed to thank you for
helping out.
1 Like
Did anyone manage to successfully generate the Bios file for T100TA?
Follow the guide: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data
Initialization
2 Likes
╔═══════════════════════════════════════════╗
║ CH0063.CAP (1/1) ║
╟─────────────────────────────┬─────────────╢
║ Family │ CSE TXE ║
╟─────────────────────────────┼─────────────╢
║ Version │ 3.1.94.3086 ║
╟─────────────────────────────┼─────────────╢
║ Release │ Production ║
╟─────────────────────────────┼─────────────╢
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 137/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
║ Type │ Extracted ║
╟─────────────────────────────┼─────────────╢
║ Chipset Stepping │ B ║
╟─────────────────────────────┼─────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼─────────────╢
║ ARB Security Version Number │ 7 ║
╟─────────────────────────────┼─────────────╢
║ Version Control Number │ 112 ║
╟─────────────────────────────┼─────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼─────────────╢
║ OEM Configuration │ Yes ║
╟─────────────────────────────┼─────────────╢
║ Date │ 2023-01-02 ║
╟─────────────────────────────┼─────────────╢
║ File System State │ Configured ║
╟─────────────────────────────┼─────────────╢
║ Flash Image Tool │ 3.1.94.3107 ║
2 Likes
1 Like
Good evening,
First of all, hello to everyone, I found your site looking for information on the problem I have on a
Foxconn NanoPC with an Intel N3700 processor which gives me the error of the little yellow triangle
next to the Trusted Execution Engine Interface device.
The currently installed version is 2.0.0.1094.
Can you tell me where to download the right most updated version, which I hope will solve my problem?
Thank you
And what is reported by Windows about the state of the related device…?
2.0.2.2092
2.0.5.3117
I uninstalled the version in use, I tried to launch the installation again and it says “Platform not supported”
Then the latest for your hardware platform was the ones you had previously, the same in OP of this
thread. It means newer packages do not contain your hw device ID (TXE) in the inf driver list.
Unfortunately now I don’t even have the previous version, 2.0.0.1094. because I uninstalled it.
MeatWar:
EDIT: Oh you don’t read any info or topics… you just fetch, section A1 on FIRST POST of this thread
As I said before, I had uninstalled the driver, I also uninstalled the remaining part with Revo Uninstall,
downloaded the OP version, installed it, restarted the machine.
Now the little yellow error triangle no longer appears.
Thank you
3 Likes
https://w inraid.level1techs.com/t/intel-conv-sec-trusted-execution-engine-drivers-firmw are-and-tools/30730/print 140/144
4/25/25, 7:51 PM Intel (Conv.Sec.) Trusted Execution Engine: Drivers, Firmw are and Tools - Intel Management Engine - Win-Raid Forum
A post was merged into an existing topic: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE
Regions with Data Initialization
Hi to all, i find Flash image tool for server platform based on C621A, current version CSE SPS
v04.04.01.023. I have seen that someone here have this? but file was sended in PM
plutomaniac:
v4.0.20.1310
Okay… so I read the introduction, the Disclaimer, the Getting Started, the section A, the first two
paragraphs of section B (can’t follow along without tools from section C), I read all of section C… and I
feel properly lost. It’s a lot to take in, a lot of jargon I have not seen before. So I hope you don’t mind
me for asking for directions.
Who updates their “(CS)TXE Firmware by following sequentially the relevant steps at Section B using
the required Tools from Section C”? I mean what use case will call for firmware update of something as
vitally important as TXE obviously is?
Is it only if I want to update the TXE firmware that I need to “install the latest Drivers from section A”?
Are any of these drivers installed already OOTB by Windows? And do I need them if I only want to use
tools like the Flash Programming Tool (FPT) to interact with my (CS)TXE? Can I do that, without
installing special drivers for particular versions/generations/families of (CS)TXE/Engine and without
updating the TXE firmware? This is what I want to do. I want to use FPT to dump my firmware so can
examine or compare the contents of the NVRAM to another dump that I made with a programmer.
Should I use HWiNFO, or ME Analyzer, or TXEInfo to get the “Major.Minor” version number and other
details right? If HWiNFO (version 8.22) has reported that I have “Intel ME” version 11.8, does that
mean I have “(CS)TXE” version 11.8? And what “TXEI” driver version do I then need? (By the way,
what does “I” in “TXEI” stand for?)
Masato:
Who updates their “(CS)TXE Firmware by following sequentially the relevant steps at Section B
using the required Tools from Section C”? I mean what use case will call for firmware update of
something as vitally important as TXE obviously is?
You want to digest everything researched in years, in just a few days? Get real will you…
Learn and ask when working on something specific, eventually you will learn specific case by case, not
flooding the forum with questions that later you will ask again for sure, besides that you have a lot to read
sir, understood?
If you did, you would by now already noticed that CS ME is not the same FW engine as CS TXE…
differents aproaches, tools etc…
MeatWar:
Yes. But you missed the second part: “I mean what use case will call for firmware update of
something as vitally important as TXE obviously is?” In other words, for what purpose would
someone be doing this?
MeatWar:
You want to digest everything researched in years, in just a few days? Get real will you…
I don’t know what gave you that idea. This post is just an overview of different Intel firmware, tools,
drivers, etc. I have no expectation to understand it all, and I don’t need to.
MeatWar:
Learn and ask when working on something specific, eventually you will learn specific case by case,
not flooding the forum with questions that later you will ask again for sure, besides that you have a
lot to read sir, understood?
No, I don’t understand. Why can’t I ask questions about the learning material if I don’t understand
something? Why do I have to be working on something specific before I can ask a question?
I don’t mind the reading. On contrary, I read almost the whole thing, and then some replies too, so that I
would not need to “flood the forum with questions”. But if I don’t understand something, I like to ask for
a clarification and to strengthen my understanding of what I’m reading. Otherwise, I might as well just run
with my head first and learn from my own failure – like the majority of newcomers I would imagine –
rather than by reading what more knowledgeable people with experience write on the topic.
Masato:
It’s a lot to take in, a lot of jargon I have not seen before. So I hope you don’t mind me for asking
for directions.
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…
It covers “Intel ME” (and CSME) specifically, rather than “Intel TXE” (and CSTXE), and it includes the
system tools for Intel ME 11.8.
MeatWar:
If you did, you would by now already noticed that CS ME is not the same FW engine as CS
TXE…differents aproaches, tools etc…
I did notice. Thanks to Wikipedia. But you could have been more helpful in your reply if you had just
pointed me in the right direction by posting the link above.
Masato: