Forum - RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization

Page 27 of 28 � Page 1 ... 22 23 24 25 26 27 28 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#391 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 04, 2021 6:13 pm (Last edited: Sun Jul 04, 2021 6:15 pm)

Hi Guys,

Thank you for making this guide. My system is Asus R6EO and 9980XE. I use the latest CSME 11.12.86.1877

I decided to clean the dump SPI because ME Analyzer showed "Initialized" FSS.

So I followed the guide with care and I skipped step 7 and 13 as SMIP key hasn`t been shown in FIT.

When I created outimage.bin it was look good "configured" but after I flashed it became unconfigured. Did I missed something or make it wrong?

Please help!

Thanks,

ME Analyzer v1.220.0 r251 ║
╚═══════════════════════════════════════════╝

╔═══════════════════════════════════════════════╗
║ outimage.bin (1/1) ║
╟─────────────────────────────┬─────────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼─────────────────╢
║ Version │ 11.12.86.1877 ║
╟─────────────────────────────┼─────────────────╢
║ Release │ Production ║
╟─────────────────────────────┼─────────────────╢
║ Type │ Extracted ║
╟─────────────────────────────┼─────────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────────┼─────────────────╢
║ Chipset │ KBP/BSF/GCF-H A ║
╟─────────────────────────────┼─────────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼─────────────────╢
║ Version Control Number │ 301 ║
╟─────────────────────────────┼─────────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼─────────────────╢
║ Workstation Support │ No ║
╟─────────────────────────────┼─────────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼─────────────────╢
║ Date │ 2021-01-14 ║
╟─────────────────────────────┼─────────────────╢
║ File System State │ Configured ║
╟─────────────────────────────┼─────────────────╢
║ Size │ 0x1F0000 ║
╟─────────────────────────────┼─────────────────╢
║ Flash Image Tool │ 11.8.86.3877 ║
╟─────────────────────────────┼─────────────────╢
║ Latest │ Yes ║

ME Analyzer v1.220.0 r251 ║
╚═══════════════════════════════════════════╝

╔═════════════════════════════════════════════╗
║ fw.bin (1/1) ║
╟─────────────────────────────┬───────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼───────────────╢
║ Version │ 11.12.86.1877 ║
╟─────────────────────────────┼───────────────╢
║ Release │ Production ║
╟─────────────────────────────┼───────────────╢
║ Type │ Update ║
╟─────────────────────────────┼───────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────────┼───────────────╢
║ Chipset Stepping │ A ║
╟─────────────────────────────┼───────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼───────────────╢
║ Version Control Number │ 301 ║
╟─────────────────────────────┼───────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼───────────────╢
║ Workstation Support │ No ║
╟─────────────────────────────┼───────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼───────────────╢
║ Date │ 2021-01-14 ║
╟─────────────────────────────┼───────────────╢
║ File System State │ Unconfigured ║
╟─────────────────────────────┼───────────────╢
║ Chipset Support │ BSF/GCF ║
╟─────────────────────────────┼───────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧═══════════════╝

reply

#392 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 04, 2021 10:40 pm (Last edited: Sun Jul 04, 2021 10:54 pm)

Zitat von Etyo im Beitrag #391
When I created outimage.bin it was look good "configured" but after I flashed it became unconfigured. Did I missed something or make it wrong?

The 2nd MEA output shows that you loaded an Update (UPD) image type which is created via FWUpdate -save parameter. UPD images do not contain File System data so it makes sense to see "Unconfigured". If you were to dump the full SPI chip image again (flash programming tool, hardware programmer etc), you would see "Initialized", as expected.

reply

#393 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Mon Jul 05, 2021 1:38 am

Thanks Plutomaniac. You were right the 2nd output was created via FWupdate.

So I created another via FPT see below. That`s looking good isn`t it.

Many thanks.

ME Analyzer v1.220.0 r251 ║
╚═══════════════════════════════════════════╝

╔═══════════════════════════════════════════════╗
║ spi.bin (1/1) ║
╟─────────────────────────────┬─────────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼─────────────────╢
║ Version │ 11.12.86.1877 ║
╟─────────────────────────────┼─────────────────╢
║ Release │ Production ║
╟─────────────────────────────┼─────────────────╢
║ Type │ Extracted ║
╟─────────────────────────────┼─────────────────╢
║ SKU │ Consumer H ║
╟─────────────────────────────┼─────────────────╢
║ Chipset │ KBP/BSF/GCF-H A ║
╟─────────────────────────────┼─────────────────╢
║ TCB Security Version Number │ 3 ║
╟─────────────────────────────┼─────────────────╢
║ Version Control Number │ 301 ║
╟─────────────────────────────┼─────────────────╢
║ Production Ready │ Yes ║
╟─────────────────────────────┼─────────────────╢
║ Workstation Support │ No ║
╟─────────────────────────────┼─────────────────╢
║ OEM Configuration │ No ║
╟─────────────────────────────┼─────────────────╢
║ Date │ 2021-01-14 ║
╟─────────────────────────────┼─────────────────╢
║ File System State │ Initialized ║
╟─────────────────────────────┼─────────────────╢
║ Size │ 0x1F0000 ║
╟─────────────────────────────┼─────────────────╢
║ Flash Image Tool │ 11.11.60.1561 ║
╟─────────────────────────────┼─────────────────╢
║ Latest │ Yes ║
╚═════════════════════════════╧═════════════════╝

reply

#394 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Mon Jul 05, 2021 5:11 pm (Last edited: Mon Jul 05, 2021 5:12 pm)

Yes, looks proper. You can check the dumped firmware health by fully unpacking it via "-unp86 -bug86" parameters. If it completes successfully without pauses on red error messages, you're good. For the live firmware, use MEInfo and MEManuf tools, as explained at Intel (Converged Security) Management Engine: Drivers, Firmware and Tools.

reply

#395 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Mon Jul 05, 2021 11:24 pm (Last edited: Tue Jul 06, 2021 12:11 am)

Many thanks.

Are these "-unp86 -bug86" can be used with FPT or could you give example how to use it please?

Edit: In the meantime I figured it out these are for MEAnalyzer. Both are Ok without error. Sorry for my "stupid" question above. I`m new in this :).

Anyway. Thanks for your help again.

reply

#396 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Tue Jul 06, 2021 1:23 am

No you're right, I should have mentioned these are for MEA. Either way, everything is fine now. Enjoy your cleaned system. :)

reply

#397 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 12:03 am (Last edited: Sun Jul 18, 2021 12:05 am)

@plutomaniac sorry to disturb, I reflashed my SPI chip with a programmer, as I messed up things. I used a clean extracted bios file from manufaturer (added MAC, UDID and serial), now the ME region results as Initialized and not Configured.
I don't have the dump of the chip...
Is this correct or not?

reply

#398 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 1:04 am

If you want to clean the Engine firmware for some reason, follow the guide. As the guide says, you should see Configured at the output image.

reply

#399 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 11:31 am

@plutomaniac I don't get. If I download BIOS from official site do I need to clean it? Or clean procedure is only for dumped BIOSes from board by myslef?
And another couple of question. Official Gigabyte BIOS have issue preventing update IME (you describe it to fix some bit). Do I need to fix it in official downloaded BIOS?
And I mod my BIOS to replace IME v7 to IME v8 with manual from tweaktownforum (I can't post urls srill). I don't get do I need to update it to IME v9 or upper?

reply

#400 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 4:03 pm (Last edited: Sun Jul 18, 2021 4:05 pm)

The problem to follow this guide, is that I need a dumped image of SPI chip, and I don't have it, just the one downloaded from manufacturer website...

reply

#401 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 4:21 pm (Last edited: Sun Jul 18, 2021 4:45 pm)

Why do u need the original dump... u have kept ur original data as u said before, so if already have introduced in the flashed bios the original data, u star working with current bios and a new dump.

EDIT: Hey m8...forget the old data and chill out (U have already backed up with FD44 didnt u?), take this as if u bought an used board and u have to repair it. So u do now have a flashed bios and a working system, so make a new dump ans start from here...
wots ur stress about it? Didnt u recover yesterday with the CH341 and with an stock extracted UEFItool Intel image and with the inserted original data (UUID, SN etc...), if im not seeing this correctly plz explain in wot point u r now.

fpt -greset or a total shutdown for a cold boot, board power as to be drain out. If state still persists wait for Plutomaniac opinion, this is field, i only have some general knowledge.

Donations via PAYPAL / REVOLUT, if u think the guy deserves it, else to the Win-Raid community on the bottom of the page, as it deserves for all the gathered information.

reply

#402 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Sun Jul 18, 2021 4:30 pm (Last edited: Mon Jul 19, 2021 12:18 pm)

There's something that's obscure to me: I esxtracted a configured ME Region from CAP file, checked and it's Configured; unlocked descriptor and downgraded with extracted ME Region, -greset, system reboots, dump the ME Region, checked and it's Initialized.
This drives me crazy.

reply

#403 | RE: [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization datum

Fri Jul 23, 2021 9:48 am

OEM public key hash, how do I clean the me firmware? Intel's latest 11th generation chipset, the tool I use is flash image tool_ V15, according to your post, I didn't find the SMIP option! I can't do the next step, please give me some advice.