I have tested UBU v1.69.13 for ASUS Sabertooth X99 BIOS v3801 (Aptio 5) using the two MMTool variants:
TestX99 1) with MMTool v5.0.0.7 (14march2014) => perfect all is OK
TestX99 2) with MMTool v5.2.0.24 (31jan2018) get from the recommended link on the startpost => 2 problems: problem 1) security application does warm about GenFds.exe executable file : Missing Numerical Signature problem 2) Keyboard strange problems such as Numerical pad entries are wrong (when select touch 3 produce a 5, etc…) and enter touch command becomes ignored and we have to come back with the mouse to the screen menu to change from ungreyed to black and becomes ‘active’ again to accept the users command)
With mmtool 5.2 I successfully updated any module on my ASRock Z170 Extreme4 BIOS file. I used the original file, without patching it. With 5.0.0.7 I always got “file size exceeded”. I can’t give feedback for Aptio 4.
Good evening, first of all I’d like to thank you SoniX for your work. As Morku with the latest UBU version and mmtool 5.2 I have been able too update the modules of my Z170 Extreme 4 (I used as base the lastest beta bios). Did I get it right? The lastest mmtool version works well with the module update but not with microcodes? Could be the solution to use the old 5.0 version for microcodes and then change the file to update the modules? I have a question about Intel RST(e) OROM and EFI SataDriver, as I was saying I have been able to update the EFI IRST RAID for SATA from 14.6.0.2285 to 15.7.0.3054 but the OROM IRST RAID for SATA isn’t updated to v15.7 is this working as intended or have I done something wrong?
If this could be implemented into the UBU toolkit, it would be great!
The MMTool v5.2 will be able to correctly update the Option ROM modules of AMI Aptio V BIOSes, but this feature has not yet been implemented by SoniX into the UBU tool script. So your BIOS modding result was as intended by the current UBU version and you haven’t done any mistake.
1.69.14 - official, in this version, I fixed a couple of minor errors. 1.69_Crutch - this is a test version, not a public version. In this version, we solve the problem with wiping the data in FIT after using MMT5.2.
I have noticed that you have packaged UefiTool Version 0.22.1 in your Ubutool since Ubu 1.69.10 and want to warn you as you probably already know that UefiTool 0.22.1 has a major bug when it comes to replacing the body of certain rom modules. I discovered this late last night and was up till 2.00 AM trying to figure this out. I feel this is a very dangerous flaw that could compromise someone’s firmware if they’re not careful. I would advise everyone use ver 0.21.5 instead.
@Vasudev : Please stop posting into the UBU thread, which is reserved just for the announcements of new UBU versions. It is not funny for me to move all the wrongly posted contributions into the correct UBU Discussion thread (which is this one).
None of the UBU versions, which have been published here since February 2017, do contain any MMTool (due to AMI’s restrictions).
The latest UBU versions can be used with both MMTool v5 platform tools (v5.0.0.7 and v5.2.0.24), but the original (unpatched) v5.2.0.24 will only work with AMI Aptio V BIOSes.
@Fernando It seems not many were able to get their hands on MMTool 5.2 because of NDA. Man, I really thought it was a scam when somebody a link to community based MMtool. Well, I guess i must keep finding until I succeed.
@Fernando , I tested UBU v1.69.14-fixed version with MMTool v5.2.0.24 ‘patched’ for BIOS Aptio 4 and Aptio 5. All is working fine. Tested Aptio 4 BIOS: 2104 for ASUS P8Z77-V Deluxe Tested Aptio 5 BIOS: 3801 for ASUS SabertoothX99 So, i think now we can now forget MMTool v5.0 and do keep ‘v5.2.0.24 patched’ as a universal MMTool.
