[ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

Ok for Asus X299 ?

And I saw in UBU 1.70, a microcode 049 for 2066, but I did not find any info on this microcode, it’s not official ?

Thanks

.

UEFITool_NE_A51,UEFIFind_NE_A51,UEFIExtract_NE_A51

If someone uses UBU version 1.69 or lower, do not use the new UEFIFind NE A51. We changed the format of the command line.

So ,other versions is OK, except A51?
UEFIFind_NE_0.10.13 is OK?

A51 requires UBU batch script changes. You can use A50 for the current UBU versions.

Only UEFInd NE A51 a little "incompatible".
Old cmdline:

1
 
uefifind <agrs> <BIOS Image>
 

New cmdline:
1
 
uefifind <BIOS Image> <agrs>
 


Up

Thanks

I see several microcode updates for i7-7820x since the “official” Feb. spectre fix 43 - anyone have any idea about the differences or what’s going on?

cpu50654_platB7_ver0200004D_2018-05-15_PRD_205C031D
cpu50654_platB7_ver0200003E_2017-12-22_PRD_5D60B462
cpu50654_platB7_ver02000049_2018-03-27_PRD_DC30919B
cpu50654_platB7_ver02000043_2018-01-26_PRD_4840163E

@ tistou77
Latest for CPUID 50654 - 4D, but I, too, do not have any information.

@SoniX
Ok thanks, I’ll test with the 4D, but I do not see the 4D in UBU_v1_70_b2_Dev



Dowloand https://github.com/platomav/CPUMicrocodes
to Files\Intel\mCode\2066
Edit Files\Intel\mCode\MCUpdate.txt
#LGA2066
–> 50654 2066&lt;new file name>

The new microcode update batches are for this one:
https://www.intel.com/content/www/us/en/…l-sa-00115.html

But not only that, Spectre isn’t the only thing that is wrong on those processors, you’d get the usual stream of fixes/changes (many are related to SGX and other crap that is mostly ignored by the vast majority).

It’s for new microcode (4D) for Skylake-X, this link ?

Successfully updated my mCode ASRock Z170 Extreme4 BIOS to the brand new C6.
Used Biosversion 7.50, Ubu 1.70 b2 and MMTool 5.02.0024 (unpatched).

Thank you very much!

EDIT:
Now I tried the same for ASrock H87 Pro4 (AMI Aptio 4) with MMTool 5.0.0.7 and 5.02.0024 (patched version), but I always get:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
 
U - Update Preview Microcode
0 - Cancel
Choice:u
[Preparing for replacement]
Empty GUID: File replaced
Empty GUID: File replaced
mCode GUID: File replaced
[Replacement]
mCode FFS: reconstructVolume: no space left to insert VTF, need B50h (2896) byte(s) more
Error
Empty FFS: File replaced
Empty FFS: File replaced
Real _FIT_
Drücken Sie eine beliebige Taste . . .
 
1Should I use UBU v1.69.17.4 instead?

EDIT2: Successfully updated to Haswell mCode 25 with UBU v1.69.17.4 and MTool 5.0.0.7

EDIT by Fernando: Inserted UBU result put into a spoiler (to save space)

@Morku

Updating files in UBU 1.70b2 is done using UEFIReplace.
MMTool only extracts files and updates the OROM on Aptio 4.

Asrock H87 Pro4
The problem is the lack of free space.
Even if you return MMTool to version 1.70, then you will see such a message.

H87.JPG


UBU 1.69 updates only 1-2 microcodes. Version 1.70 updates all found microcodes.
Therefore, in order to update the microcodes in UBU 1.70 without problems, you need to disable the unnecessary microcodes.

h87vc.JPG


In next version UBU, I will add backup creation, which will be restored with such errors.

I have a problem with UBU 1.70-b2: I have successfully updated the micro code of BIOS 1301 (with micro code 0x02000035, which is older than the embedded one in that BIOS), then I successfully flashed my Asus Rampage VI Apex, but the system won’t boot (stuck with post code 55: “memory not installed”). When I flash the mobo with the original 1301 BIOS, my system boots and works perfectly.

Is it related to the fact that v1.70 updates all micro codes? Or did I miss something?

My system:
Asus Rampage VI Apex (Aptio V)
CPUID 50654 (Skylake-X)
Windows 10 x64
MMtools 5.02 Patched

I have found a little bug on UBU v1.70.b3-DEV

When executing at dos prompt, above Administrator: EUFI BIOS Updater v1.70 b2 DEV - bla bla says, not b3 but b2, a little mistake!

@karakarga :
As you may have realized, the latest UBU version 1.70.b3-DEV has not been released by SoniX. To make it as easy as possible for the users to get a complete UBU package with the latest components, I have replaced several UBU components of the v1.70 Beta 2 version by the meanwhile available newer ones and simply renamed the package to v1.70.b3 (to make clear, that it is not identical with v1.70.b2).
Since I would never touch Sonix’s UBU script, you got the “wrong” info about the UBU version.

Yes it is still v1.70.b2 available but it is indicated v1.70.b3 on the topic, bizarre