I tried that version, It doesn’t work, I think I need to downgrade the BIOS to an older version
Using FIT and ME image from BIOS update files I cleaned the dump without needing to sign anything or generate any keys
So, can you explain if the ME is v12, why use FIT v15??? Or am i seeing it wrong???
Or is this another system clean???
EDIT: Oh…ok, that will be clear now for anyone who’s following the thread.
Yes I can explain, these are two different devices, the other device needs FIT v15 but I cant open it in FIT v15, I will downgrade the Bios to 2024 or 2023 and try again.
I unlocked the ME region using hidden BIOS config and flashed the ME binary extracted from the BIOS update package for that system and it bricked it, after restart it wont boot or even power on
so far I had success with two systems, one with ME 11 and the other with ME 12…
I bricked the one with ME 15
Do I need to change this setting? sometimes its changed automatically, other times its set to no emulation
Do I need to do -greset if I am not going to use ME/AMT?
When I used FIT 11,12 and 15 I got ME Region from CSME 11 dump, and CSE Region and ME Sub Partition from CSME 12 and 15 dumps, I never got CSTXE or TXE from any dump.
What does TXE/CSTXE do? is TXE/CSTXE a successor of ME/CSME?
Sir… the Intel CS(ME) has evolved… we can say that till 11 its easy to users to deal with, later ones have more sub-modules requiring more configuration.
Bear in mind that this a is a factory operation and never was minted to public domain or to be a end user manipulation, needless to say that many tools here shared on the forum is for sure not very appreciated by Intel/OEMs, so consider it a bonus as well the contribution of our dear member Platomav.
CS(TXE) is a different branch and specific platform target.
More info…Google is your “friend”
I figured it out, the ME region was either corrupted or infected, I swapped it using UEFI Tool 0.28 and a dump I found on the internet, then I cleaned ME using FIT without errors
Note: BIOS downgrade didn’t solve the issue as the ME region was either corrupted or infected
Note: FIT tool used is more recent version compared to the one used for the stock DUMP
Update: system didn’t boot after flashing, I had to restore original dump
I found a solution to the FIT error on the forum here
But when I follow the guide the outimage.bin shows configured on MEAnalyzer and when the system boots with ME disabled, the new dump shows initialized, is this the old data carried over or is this automatic greset?!
We dont know what you’re doing…what system, what ME FW version, what images used properly and what “garbage” is on a probably already corrupted fw.
The guidance won’t work to fix user mistakes, tests/experiences.
Point D4 of this guide has all the info needed.
it’s CSME15
Thank You Very Much for This.
Please share more Pictures, information or document like this.