Zitat von ex58 im Beitrag #3569

---

SoniX posted new 1.69.14 and "1.69_Crutch" (with MMTool 5.02).......

---

@SoniX,

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.

See here: [GUIDE] AMI INTEL CPU Microcode Update Guide (6)

Thank you.

UEFITool 0.22.3/NE A46
and UEFIExtract/Dump/Patch

Is MMtool 5.2 shipped with latest UBU tool OR can i use older 5.0.0.7 w/o any issues?

@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.

@100PIER
regarding the Aptio 4:
what about the _FIT_ problem using MMTool v5.2.0.24 (or did you just skip the microcode update part?).

The problem with _FIT_, when executing MMT 5.2, only on A5, on A4 I did not notice such a problem.

@nikey22

I have tested the microcode update for the Aptio 5 and it is working fine. ("3A"->"3B"). Broadwell-E CPU (Core i7-5930K).

For the Aptio 4 I have tried to mod to the best current microcode "19" I already have. IvyBridge-DT CPU (Core i7-3770K).
I get no problem:
[[File:µC19_Ivy_part1.PNG|none|auto]]

What exact problem do you have observed ?

Hello,
can someone please provide the checksum of the patched v5.2.0.24 mmtool?

Thank you.

@ 100PIER
If you use MMT5.0.0.07, then there will be no problems. The version does not fix _FIT_.
Version MMT5.2.0.24, according to my tests, does not affect FIT_ on Aptio4, but makes corrections to Aptio5.
It is important to monitor the address correction table in _PIT_.
If the first line is a solid 0xFFFFFFFF, then _FIT_ is corrupted, and such a file is flawed.
We are now trying to implement the algorithm for correcting the corrupted FIT_ after applying MMT5.2, in the versions "1.69.Crutch".

@ greg.chalk
[Discussion] UBU Tool related Questions, Reports and Suggestions (235)

Edit:
Typo "PIT" -> FIT
Sorry.

@SoniX

I have seen this post, but because it says original, I thought it's not the patched one.
Thank you for your help!