@Sonix
I have tried to update µC from 7Ch to 84h with UBU Tool v1.9.15.1 with patched MMTool v5.2.0.24 for a Aptio V BIOS 1003 of ASUS ROG-MAXIMUS-X Hero mboard.
CPU is a coffee lake i7-8700K CPUID=906EA. I get these screens.
How do the µC update ? What exact options to enter ?
Are these screens correct ?
Option 7:
[[File:ROGmaximusXhero_µC_screen_option7.PNG|none|auto]]
Option 3:
[[File:ROGmaximusXhero_µC_screen_option3.PNG|none|auto]]
Option s:
[[File:ROGmaximusXhero_µC_screen_option_s.PNG|none|auto]]
Option m:
[[File:ROGmaximusXhero_µC_screen_option_m.PNG|none|auto]]
Because when I try to use UBU and patch an oROM it gives me this:
The MMTool window shows this:
Saving secure rom as unsigned
And then the UBU:
* Generate FFS Intel RAID Driver GUID 91B4D9C1-141C-4824-8D02-3C298E36EB3F …Ok!
* Update EFI Intel RAID Driver GUID 91B4D9C1-141C-4824-8D02-3C298E36EB3F …Error!
* Update OROM Intel RST Device ID 282a …Error!
@senso :
Have you done a look into the MMTool? There should be a message about the reason why the related module could not been updated (maybe not enough available space within the related BIOS Volume?).
Hey @SoniX
Any ideas about my issue???
Tried to flash F3b and same 700MHz problem.
The mod bios has only one microcode, the latest one for Skylake-X.
Suppose this microcode includes my 7980xe…
All it says is this:
Saving secure rom as unsigned
AMIBCP says the same and if I try to just change all the menus to USER it produces a BIOS image with 6MB instead of the original 3MB dump.
@Fernando
@SoniX
I have tried the option c in the 1.70 version, and this is the result:
EDIT by Fernando: Inserted pictures split, resized and reinserted to save space (can be enlarged by clicking onto them)
Try a different version of the microcode.
v1.69.15.1 - (mmt 5007) (asrock h97 pro4) sucesfull insert the haswell v24 ucode
all ok
v1.70 a12 Dev -(mmt 52024) (ASRock X99M) sucesfull insert the haswell/brodwell 3C/2A new ucode
- only possible the all two ucode update in same time if i choice one the another one erased
- HWiNFO or Aida64 cant show the upated ucode only show - sign
@Sonix
Tried v1.70 a12 Dev to mod µC for ASUS Z370 with CPUID=906EA
Used Options 5 → C → U → Enter → 5 again.
I do observe 12 cpuid detected before modding and only 8 detected after modded done.
Is it normal ?
Here are the screenshots (from left to right: Choice_5 > Choice_C > Choice_U > Choice_ENTER > Choice_5 after modded done):
[[File:Choice_5.PNG|none|auto]][[File:Choice_C.PNG|none|auto]][[File:Choice_U.PNG|none|auto]][[File:Choice_ENTER.PNG|none|auto]][[File:Choice_5_after_modded_µC.PNG|none|auto]]
EDIT by Fernando: Location of the inserted pictures customized (to save space)
@ 100PIER
Some of the microcodes are Engineering Samples. If you need them, then you can add them by editing MCUpdate.txt.
In fact, the procedure for updating the microcircuits is the same as in previous versions of UBU. Only now the necessary microcodes are written by the user independently.
From your screenshots I do not understand one thing, I do not see the restoration of the FIT dump.
If I understand correctly, then updating the microcode 0x00200043 leads to the problems described by you. Therefore, 2 options for action:
1 - in MCUpdate.txt, in the section ;2066 prescribe the microcode you need. Instead of what is, set the path and file name, opposite 50654 path\name.
2 - Provide BIOS with a microcode that does not create such a problem
@ Fernando
I have a suspicion that any version of MMTool 5.x.x.x spoils BIOSes from ASrock based on the x99. I do not have time to check on later versions of BIOS.
The problem is completely erased by FIT.
Hi again, @SoniX
Did what u said and this is the result:
Is it correct or is there a problem with fit mismatch???
Thanks again.
EDIT by Fernando: Inserted image resized and re-attached (to save space)
At you on a preview, that is before updating one, and after updating absolutely another.
The result should coincide with the preview.
I just included all the microcodes present in original bios.
If i didn´t edit the mcupdate.txt, the option c would only update the 50654 microcode.
This is the file with microcodes updated, can u check it to see if is correct???
https://mega.nz/#!Vi5z3JBR!2Vr7VoUWvVTjZ…TLH-tw0mBg_Azes
Thanks.
Does your processor belong to Engineering Samples?
If your processor has CPUID 50654, then it was sufficient to specify another file with a microcode version, for example 3C with the same CPUID.
My processor is retail, it should work with 43 microcode, if this includes 7980xe’s.
I also thought like u, 43 should be enough, but there is some kind of problem and cpu remains at 700MHz.
Could the modded efiflash have something to do with it??? It is 3.62 version, and original bios’s for Gigabyte x299 come with 3.65.
In regards to 3C version, there is a original bios from Gigabyte, F3b, which includes it. I am trying to use the new 43, as other mates are doing.
As far as I understand, 43 microcode is a beta version.
In general, everything is tested by testing, that is, comparing the work on different versions of microcodes.
Intel ordered to retire the 3A and 3C versions, so 43 should be better than those. That’s why I want to use it.
Could u mod the efiflash 3.65 to let flash modded bios’s???