@Sonix
I observe 2 problems when using MMTool v5.2.0.24 instead of v5.0.0.7 when using UBU v1.69.12 for Aptio V BIOS v3801 of ASUS SabertoothX99
1) I get a signature missing alarm from my EMSISOFT security application:
2)The Enter press touch does seem not working when the screen large is selected. We have to reduce the screen to get effective the Enter button.
With MMTool v5.0.0.7 absolutely none problems for the same scenario.
Forgot. Sorry.
https://github.com/platomav/MCExtractor/…tag/v1.14.0-r55
With UBU 1.69.13 with the modded mmtool 5.2.024, no errors on Aptio 4 with my original un-modded z87ws bios who wasn’t working before ??? everything ok ??
thks
@coromonadalix :
It didn’t work for you previously, because you hadn’t updated the file UBU.bat (reference to a wrong hex code).
what tool should i use to patch the new mmtool?
I just used a hex editor and searched for each listed address and made the correction and saved.
Since the MMTool is write-protected, you have to get the required rights to be able to patch it.
@SoniX :
Meanwhile I have tested the UBU v1.69.13 with an Aptio 4 (ASUS P8Z68-V) and an Aptio 5 (ASRock Fatal1ty Z170 Prof. Gaming i7) BIOS. In both cases the UBU folder contained the patched MMTool v5.2.0.24.
Result: Everything went flawlessly.
Remark: The update of the Option ROMs seems to be not yet implemented for Aptio 5 BIOSes. When can we expect it?
@Fernando
Thank You for testing.
The OROM update on AptioV will be implemented in version 1.70.
But at the moment I’m worried about updating microcodes in fixed volumes on AptioV (x99/x299 and etc).
Version 5.0.0.7 displays a message that “Error in replacing file” and the update does not occur.
Version 5.2.0.24 gives out 2 other messages, but the update happens. It is necessary to check, if after updating all works without problems it is necessary to disconnect these messages.
Tried UBU v1.69.13 with patched MMTool v5.2.0.24 with an Aptio 4 (MSI Z77A-G43) v2.13 UEFI error: The input image is not Aptio V.
strangely enough got the same warning (using windows defender) but only on UBU_v1_70_a10_DEV\MCE.exe
v1_69_13 is unzipping without issues.
To exclude a wrongly patched MMTool, I have repeated what you tried by using the same BIOS.
Result: I got the same message.
Maybe there is another byte within the MMTool code, which has to be changed.
Using patched version 5.2.0.24 seems to butcher the FIT, the offsets get updated to wrong values, Version 5.0.0.7 updates them correctly. I attached a zip of the screenshots.
The images are of UBU, UEFITool Alpha, and MCExtractor screens. I also verified the offset updates by extracting the FIT table from the bios, using the regular version of UEFITool for both versions.
This is on a MSI Z170A M7 bios link is, here.
New_MMTool_Test.zip (89.1 KB)
Indeed, 5.2.0.24 overwrites FIT.
It is not critical, since microcodes are still read without using FIT. But still not good. 
Add:
Version 5.2 really corrects FIT and by the way is very correct.
Unfortunately, the problem occurs if you restore the "Empty" file.
What exactly is the "Empty" file anyway? UBU just removes it, then updates the codes, then restores it all by itself.
I think unpatched 5.2.0.24 also mangles FIT, I had to downgrade to 5.0.0.7 to get a flashable image.
At the moment there are 2 thoughts or throw everything or delete this “Empty” module…
Add:
Test on ASUS Rampage V
@Sonix
I have tested UBU v1.69.13 for ASUS P8Z77-V Deluxe BIOS v2104 (Aptio 4) using the two MMTool variants:
Test 1) with MMTool v5.0.0.7 (time stamp 14th march 2014) => perfect it is OK
Test 2) with MMTool v5.2.0.24 (time stamp 31th january 2018) => problems:
Moreover I observe the BIOS file has been erased from the UBU folder when test 2 did fail.
Nota: the input BIOS file used for test 2 was the output bios file from the test 1.