My motherboard is Asrock H55mle. And I follow the instruction in this thread.When I want to build the image in step12, it said "The SKU Type is Not set to an Ignition SKU but the ME regoin is Ignition FW. Please change the ME image file or the SKU Type and rebuild."
I used Intel ME System Tools v6 r2 & Intel ME System Tools v6 IGN r1. And The ME version is 6.0.50.1252_IGN_CC_PRD_RGN. What should I do?The dumped bios is ME 6.0.20.1185, SKU: ignition, platform: Ibex Peak. Please help me to figure it out. Thankyou!
*English is not my mother tongue; please excuse any errors on my part
Make sure you use the Intel ME System Tools v6 IGN package. Your system has ME 6 Ibex Peak (IP) Ignition firmware, not Cave/Colleto Creek (CC). So you need to use 6.0.30.1199_IGN_IP_PRD_RGN instead. At step 8, when you load the dumped SPI image into FITC, make sure you first select the SKU at the top to be H55. In this case (Ignition SKU), please ignore the Platform at the left which says “Cave Creek”, it will work just fine.
Thank you for your reply. But the problem still exists. In step 8, do I need to do this? "If you are working on ME 5 - 9 or TXE 1, go to Flash Image > ME/TXE Region > Configuration > Features Supported and set "Intel (R) Anti-Theft Technology Permanently Disabled? " to "Yes". Intel Anti-Theft Technology has been EOL since January 2015 and can cause issues if left activated nowadays."
And what does it mean? "Note: These two settings are set at the Flash Descriptor (first 4KB of SPI image) and not Engine Region. So for these to apply, you need to reflash the FD as well either by preparing a full SPI image (FD+ME+BIOS) or by flashing it manually via a tool such as Flash Programming Tool with -desc command."
How does the initial problem still exist? You now asked a different question. FITC will probably grey out Anti-Theft as it’s not supported at the Ignition SKU (first select H55 as we said). Generally, just do as the guide says and you’ll be ok.
I have followed the instruction but the problem still exists.I did chose H55 in step 8. And I also tried to choose H55 in step 5 & 8. Can anyone help me?Please.
I can’t remove the intel ME by using this method. Therefore, I use another method. I padded (0xFF) the entire 128KB ME Ignition region manually.
I am having this same issue. Keeps complaining about the SKU. I am using the Intel ME System Tools v6 IGN r1 tool and 6.0.20.1185_IGN_IP_PRD_RGN.bin. Tool is set to use Cave Creek and Intel Q57.
Any help would be appreciated. Thanks.
After some testing I have concluded that, when it comes to ME 6 Ignition firmware, FITc v6.0.50 is meant for Cave/Coleto Creek systems only (Ignition 6.0.50.xxxx) so not Ibex Peak (Ignition 6.0.xx). Thus, please use “Intel ME System Tools v6 1.5MB/5MB” instead. I will also change the names to address that change. Basically only systems with ME 6 Ignition 6.0.50 firmware (Cave/Coleto Creek PCH) must use FITc v6.0.50 from the (currently improperly named) Intel ME System Tools v6 IGN package. Thank you for the report hcf and X7JAY7X. 
As for the SKU, for some reason ASRock used Ignition firmware with H55 PCH (which normally runs 1.5MB) so that’s why FITc complains. Select P55 SKU (Ignition) instead and it will work just fine.
Thanks! That worked although comparing the two images after and before, only one byte has changed. Usually I see a lot of difference when I do an ME v7, v8, v9, etc. Is v6 different in that I shouldn’t see many changes after FITC?
Are you referring to the CleanUp Guide? For ME 4-6, the ME settings were kept at ConfigParams.txt file. The XML file was used for everything else (FD & FITC settings).
I used HxD just to compare the original and cleaned. I am only seeing one byte different. Comparing two images from a v7 for example, there are usually a ton of differences.
Can you attach the dump and the result of the CleanUp Guide for me to take a look?
Alright, you have an Apple system with ME 6 Ignition IBX. Basically the SPI does not need ME cleaning. Ignition firmware is extremely bare-bones so it is likely that it has no initialization data, at least not in this case. FITC does replace the ME region with the RGN but because the settings are the same and there is no initialization data, the end result is the same. The 1 byte difference you see is not even at the ME region but at the Flash Descriptor, thus irrelevant. If you want you can use the latest 6.0.30.1199_IGN_IBX_PRD_RGN during cleaning to update the firmware while keeping settings. Other than that, no ME cleaning is required.
Ok, thanks for the info. Much appreciated!