Thank you. You reference fptw64.exe; Is FWUpdLcl64.exe also ok? I notice that it has fewer options in the older version that is the one which works with my system, particularly, it lacks the -d options and region-specific suboptions.
So, with the SERVICE_MODE jumper removed, DEVMGMT again shows the Management Engine Interface #1 (I’m glad I wasn’t just losing my mind!), and the v11 FWUpdLcl64.exe -SAVE option seems to have worked.
I got “STATUS: restore point operation success.”
And I have the file as specified in the -SAVE option, 4,968,448 bytes.
MEAnalyzer on this dumped file gives:
╔═══════════════════════════════════════════╗
║ ME Analyzer v1.307.0 r366 ║
╚═══════════════════════════════════════════╝
╔════════════════════════════════════════════╗
║ MonsterOrigFW.bin (1/1) ║
╟─────────────────────────────┬──────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼──────────────╢
║ Version │ 11.8.97.4739 ║
╟─────────────────────────────┼──────────────╢
║ Release │ Production ║
╟─────────────────────────────┼──────────────╢
║ Type │ Update ║
╟─────────────────────────────┼──────────────╢
║ SKU │ Corporate H ║
╟─────────────────────────────┼──────────────╢
║ Chipset Stepping │ D, A ║
╟─────────────────────────────┼──────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼──────────────╢
║ Version Control Number │ 343 ║
╟─────────────────────────────┼──────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼──────────────╢
║ Workstation Support │ No ║
╟─────────────────────────────┼──────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼──────────────╢
║ Date │ 2024-08-25 ║
╟─────────────────────────────┼──────────────╢
║ File System State │ Unconfigured ║
╟─────────────────────────────┼──────────────╢
║ Chipset Support │ SPT/KBP ║
╚═════════════════════════════╧══════════════╝
Reading further through the “Clean” guide, I downloaded the 11.8 repository; MEA shows me v11.8.97.4739; the latest number in the 11.8 repository is a little older - 11.8.92.4249, with two variants, _CON_H_DA_PRD_RGN, or COR_H_DA_PRD_RGN; from the Clean guide’s text, I think I understand that this slightly older version, with the PRD matching Production and COR matching Corporate H, though the information output by MEA is a little bit different in the Chipset information (MEA says of my dumped firmware “Chipset Stepping” “D, A” whereas MEA says of the slightly older firmware from the repository “Chipset” “KBP/BSF/GCF-H A SPT-H D”; the date is two years older than my dumped firmware; the version control number is 331 vs 343. I notice a comment in the thread Intel (Conv.Sec.) Management Engine: Drivers, Firmware and Tools (2-15) that “A downgrade to a lower VCN value via FWUpdate tool is prohibited”.
Is it okay to continue? Or must I find a more exact repository version to match the 11.8.97… of what is currently in my T3620’s firmware?
The Guide then says to run ftoolc.exe; I find instead mfit.exe, which I think is the new name of the same Flash Image Tool? That opens a program that calls itself “Intel Modular Flash Image Tool”. (Version information MFitCore version 1.1.0, MFitTool version 16.1.25.2901).
Hm. But. I dragged and dropped the file that I dumped from my T3620 with FWUpdLcl64.exe -SAVE, and the Intel Modular Flash Image Tool complains:
“Import failed
The file ‘MyOriginalFirmware.bin’ is not recognized as a valid input.”
If, instead of dragging and dropping the file, I click the Decompose option, I get a different error:
“Decompose failed
Exception: Decompose ‘C:/path/to/MyOriginalFirmware.bin’ image failed.
Details: Corrupted buffer detected.
Details: Could not find decompose metadata in image…”
I hope that I’m not providing too much step-by-step detail of how I’ve gotten to here, and you can help me get past the mfit can’t-decompose problem.
thank you again,
-Jay