Open bol-van opened 7 years ago
Can you try again on the full image with the latest version of me_cleaner? In commit ba885fa9fce412436594bbd98c5a644c9c3dbf40 I've removed the NR >= 2 requirement
It worked. Image was modified. At offset 1000 I see only "$FPT", "FTPR". Others were removed. FIT v11 cant load image because from its point of view ME region is corrupted
I think FIT requires the EFFS partition since it stores many system-specific settings and won't work without it.
FIT v11.x cannot work without EFFS but older versions can.
No matter what, FIT should not be used after nuking the ME. The nuked region can be replaced either manually from the ME start & limit at Flash Descriptor or via UEFITool, provided that the size remains the same. To also save space from the removed modules, manual work is needed at the FD ME size first.
@bol-van I've just pushed a new commit (d8bf20d0f29d0add5606952d19414590dc18c113) in the testing_me11 branch which further reduces the amount of code in the Skylake (ME 11) images. Can you test it?
I've already widely tested it on my Skylake platform, it should be safe.
I successfully applied me_cleaner to B75 and Z87 OEM bios. Just to learn how it works on skylake I downloaded several bios images from newer motherboards and tried me_cleaner on them. Looks like it cant work with full bios images.
However it looks working on extracted ME region blob.
Then I tried to use FIT v11 to integrate ME image into full image. It checks integrity and rejects modified blob. I tried to 'dd' modified me to offset 0x1000 of full image but FIT also refused to open modified image. I'm wondering if its safe to flash this modified image ? If I have ME region not write locked will it be good to "fpt -me -f modified_me.bin" ?