@MeatWar I don’t think that bsb16 is looking for a clean ME region in the sense of this thread. The linked stock bios already contains a clean, properly configured, not- initialized ME region.
In the meaning of the github project of reduced ME functionality: Not much here- wrong forum to ask.
Hello! Does anyone have a clean CSE TXE 3.1.93.2965 and clean PMC 2021-12-16? I don’t see it in the archive. Thank you!
Hello, has anyone had this problem with a gigabyte ga-h55m-s2 that can help me?
Why not staying in the original thread?
You need to dump your own firmware (both chips) with a CH341 programmer, clean the ME configuration possibly make some changes to the flash descriptor to get proper region size and flash the firmware back- as described here
Hi, just would like to indicate, that with the help of this forum (and mainly this thread), I was able to succesfully enable ME on some dell optiplex 7050 micro with ME version 11.8.94.4494. For anyone else searching the steps for the optiplex 7050 micro model:
set the jumper on the board to service mode(see user manual for details). Else the next step will display an error with reading the SPI memory (ME region is locked for read and write on this model, when not in service mode)
boot into system(e.g. windows), and dump the firmware with FPTW64.exe -d full.bin (from CSME system tools v11 r46, that can be found in this forum)
check .bin with ME Analyzer for the needed clean ME .bin version, in my case 11.8.94.4494_COR_H
I found that version here, it seems not in the main repo, but is in the tread: Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15) - #6117 by bronxamigo thanks bronxamigo for the fixed version!
cleaned the firmware, following provided steps in this thread, enabled ME in FIT. I did got a question about bootguard while building, but that seems to not affect ME region (judging on what UEFITool tells me with its yellow lines)
build new firmware with FIT(no errors), and checked it with ME Analyzer and UEFITool if it was a valid image
uploaded it with FPTW64.exe -f firmware.bin
perform FPTW64.exe -greset, and windows went immediately into reset-shutdown
pulled power after shutdown, to remove the jumper for service mode, and turned on the PC
It took a little bit waiting, and a second time turning on the device, before it booted again(I was afraid I bricked it), but pressing F12 now shows the ME options.
Beware; with the jumper enabled for service mode, the ME option is not displayed when pressing F12! That might give the idea it did not work. but it shows only when the jumper is remover
Thanks a lot to all on this forum making this possible!!!
Some Dell machines often report TPM errors. Can I permanently remove it?
Does anyone have pointers how to update ME region within a BIOS file?
Bricked the laptop, using CH341A programmer to re flash the chip.
The ME version in the original latest BIOS is 12.0.40.1433. PCM version 300.2.11.1024. The ME update version that was flashed to the laptop prior to BIOS mods is 12.0.94.2380. PMC version 300.2.11.1025.
I’m assuming this is the reason the system refuses to turn on after programming the BIOS chip via CH341A? I did check numerous times to make sure the BIOS flashed matches the BIOS on the chip.
Prior to BIOS mods? If bios mods were flashed after ME update- why should ME be the culprit?
Otherwise impossible to answer with information given.
Clarification. When I performed the BIOS mods and encountered a bad flash, the ME version at that time was 12.0.94.2380. PMC version 300.2.11.1025.
Now, I’m trying to flash the BIOS chip with the original BIOS from the OEM via CH341A (I did not do a BIOS dump with ME region initially for my backup - hence resorting to a BIOS from OEM for this system). The ME version in this BIOS file from the OEM is 12.0.40.1433. PCM version 300.2.11.1024.
I suspect this is the reason I’m encountering POST issues. Thoughts?
If the bios file from the OEM is a properly configured and complete firmware image it should indeed work if flashed properly.
Since you confirmed a proper flash in your first post, the earlier versions of the ME region should be overwritten and thus no longer relevant.
Understood. I recall seeing somewhere that certain platforms retain ME versions in PCM. I was under impression if flashing a whole image with an earlier (but compatible) ME version onto machine that had a never ME revision, expect issues.
I don’t recall ME versions retained in PCM? Maybe you refer to certain values fused into PCH- but that’s not dependant on version but end of manufacturing?
What machine are we talking about / what bios did you flash with the programmer?
Yes, seems to be a complete image including EC in first padding in bios region.
Is it possible that 0x600000 to 0x620000 in the modded bios didn’t contain the EXfirmware?
What does the machine do now?
If I hold the power button as I plug the machine in, the power button LED will light up and softly blink few times before powering off. The machine will no longer do that until I perform a CMOS reset.
I’m sure the EC works fine, as it was charging the battery and stopped when the battery got full.
On MSI SIte is 10 laptop modles for this word “MS-16U1” so what is your model laptop?
There are also ME firmware update tools and EC.
MSI GP65 Leopard / GE65 Raider
EDIT: There you go… user confirmed info, thank you.
This is a GE65-9SF
Edit: Just used a different version of CH4A programmer to verify flash contents with original BIOS from MSI. Its a match. Drawing a blank…
Going to try full erase, verify blank, flash and verify again.
All I have from the machine as a backup is a bin file of the bios from FPT. Just contains the BIOS and nothing else. All other things such as ME are missing from the backup.
Wondering if there is some machine specific info in there that is missing. Not sure where to go from here…
I don’t really understand what you were trying to say? Was the content different (blanks / FFs?) or did it match and comparing was usesless- a blank?
But the only way to make sure that your flash was properly done is to read the chip again in a separate process, save the result with a different name and then compare this freshly read file to the original firmware intended to flash.
If the manufacturer provides a complete image, then normally that’s all you need.
You have identified the chip correctly?