@sgthawk
This BIOS can not be changed! Open the file in any UEFITool and you will understand everything.
Add:
@sgthawk
Please send imfo from "MEInfo".and info "meinfo -FWSTS"
Look how active BootGuard is
Sorry to hear this 
was looking forward to implement spectre protection myself, since gigabyte will do nothing for an old product.
I don’t understand your second sentence, I am not an native english speaker.
Can you clarify this or by any chance explain in german?
@SoniX - Does that mean @vander BIOS can’t be manually edited either, with MMtool or hex or even UEFITool for ucode?
I could do it for him manually if you think those errors can maybe be normal/expected since stock BIOS has them already. I didn’t try mod, but I checked the BIOS to see what you all were talking about and I see the errors in UEFITool.
Here got it.
How does this info help?
@vander
In UBU, support for AMD microcode and AGESA is not planned.
You need to look for messages about how to replace everything manually.
@Lost_N_BIOS
Yes, everything is done manually.
[Discussion] UBU Tool related Questions, Reports and Suggestions (278)
It turns out that it is, ASRock changed protection.
What needs to be done to bypass the new protection? Are other brands following?
@SoniX - can I edit @sgthawk BIOS for him manually too? @sgthawk - If SoniX says yes OK to manually mod, what do you need modified?
@vander - here is BIOS with update microcodes - flash from DOS using EFIFlash, if invalid ID or Image use /X switch after file name
https://www.sendspace.com/file/7sis10
My MSI 970A-G43 PLUS sais on CPU-Z that I have AGESA 1.5.0.7. Since I don’t found this version on the web, do you need to include on your tool?
@sgthawk
Ok. In BIOS there is BootGuard, it is configured, but according to information from MEInfo is not enabled.
Therefore, first try to flash BIOS with fix.
If you can flash this BIOS and everything works, you can try to replace the files.
fix_BG_e7920ims.rar (5.95 MB)
THe integrated bios flash called mflash wont let me flash it, because it does not recognize it.
@sgthawk
Such BIOSes, after fixes, are not flashedwith the standard method.
Is used either a programmer or for example a FPT.
Mine is ASUS-PRIME-X299-A
i did these as the reference told
5 - CPU MicroCode
C - Create FFS with MicroCodes
A - Used MMTool - Asus x299 or if previous option makes a brick.
at last he gave me the “X299A.CAP” but i can’t flash bios in ASUS USB BIOS Flashback
https://dlsvr04.asus.com/pub/ASUS/mb/LGA…A-ASUS-1401.zip
I sincerely appreciate!
“PRIME-X299-A-ASUS-1401” link
https://dlsvr04.asus.com/pub/ASUS/mb/LGA…A-ASUS-1401.zip
Here we go :
https://drive.google.com/file/d/1LuNerW9…iew?usp=sharing
I’ve updated only cpu microcodes. You should be able now to flash it via USB Bios Flashback method.
hi @ Sylar76
Thanks for your kinds! i’ll try it tomorrow in my office
Hello
I saw on this page this microcode cpu50654_platB7_ver0200004A_2018-03-28_PRD_F98D6178 (older than the cpu50654_platB7_ver0200004D_2018-05-15_PRD_205C031D but maybe it does not have the “bug” of the TJ Max )
Someone will have the .bin file ?
I do not know how to get it
Hello,
when I try to update the microcode on an Asrock Z77 Extreme 4 I get the following error:
Previously UBU always worked fine. I also tried with “A” option using MMTool but I got the same error.
Tried almost everything without success. I saw that another user on this thread had the same error message with a Z77 Pro4. What’s the problem?
is that considered an error? i got the same messages
I’m trying to update an HP BIOS which is APTIO 4.
When I do the microcode update, it works, but it replaces all the microcodes with only the two microcodes it updates.
Any advice?
Thanks