BIOSes from Intel have their own UEFI structure, as well as a digital signature.
@Sonix
Thanks for your reply. EMSISOFT does recognize a "false-positive" file detection and has done a specific update today.
After applying the update, automatically a proposal to un-quarantine the file is offered and a Yes reply does restaure the file at the original location. All is OK now.
And that structure is not supported by UEFITool? But phoenixtool can read/write that structure?
I was aware of the digital signature. Is that only enforced when performing a flash update through the normal flashing software? Or is that checked every time the BIOS is loaded?
@ gyrator
UBU uses MMTool and works only with BIOSes from AMI.
To work with BIOSes InsydeH2O, PhoenixSCT, Intel and others, they need their utilities. But I did not meet the utilities working on the command line.
Also, as far as I know, the digital signature in such BIOSes checks the integrity of the structure at the time the computer is started. Even if you modify the backup and use the programmer to flash it, you risk getting a brick.
@scotter77
Since UBU offers menu item for microcode file selection I tried to select (several) bin-files from Intel, AMD & VIA CPU: Microcode Repositories but nothing ever happened after I selected a file (not even returned back to menu).
Have you succeeded with UBU modifying BIOS file with microcode bin-file from Intel, AMD & VIA CPU: Microcode Repositories?
Oh that’s what I was afraid of. I haven’t finished my way through this monster thread but I was hoping it had a happy ending and someone figured out a way around that problem. What you’ve said makes me think it might just be impossible to mod the IRST OROM. Stuff that isn’t digitally signed (like microcode) is okay to mod but not the OROMs. Not the news I want to hear but better I find that out before I desolder my chip 
. I’ll keep reading but now I have less hope.
@ gyrator
Perhaps there is a solution. You need to find out who managed to solve this issue for Intel’s motherboard.
From what I’ve seen so far, the answer is nobody. People have updated microcode in the DX58SO bios, but apparently that part is not digitally signed. I haven’t seen anyone update an OROM. But like I said, I’ll keep reading the thread at MDL. Thank you. And thanks for your work on UBU even if it isn’t a help to me.
@mbk1969
yes Ive succeeded.
make sure the filename for the bin file matches the filename in the sel****.bat files in the Modules\mCode folder, rename it if not.
for Haswell example add
echo 23 Version 23 Date 20-11-2017 - Meltdown + Spectre Bios Fix
and further down the code add
if /I %ec%==23 (set mc2=1150\cpu000306C3_plat32_ver00000023_date20-11-2017.bin) && exit /b to my haswell sel1150.bat
@scotter77
Problem is you are talking about "2011v3" folder, but I need "2011" folder and looks like there is no bat-file for it in "mCode" folder.
Ok, I found that ffs-files inside "2011" folder are processed differently, so I can try to mimic the algorithm for bin-files in other subfolders
Update: So I was able to discover how UBU works with CPU microcode in bin-files, and to modify UBU bat-file accordingly, and to modify BIOS file, and to flash it to BIOS. So now I have HW support of BTI mitigation and mitigation enabled in Windows .
hi everyone, I have updated my bios using UBU and get some issues.
overall procedure:
1- download bios file from Asus site
2- remove capsule by UEFITool
3- remove some OROM:
|138|DpcDxe |399CF3A7-82C7-4D9B-9123-DB11842986D3|0040BFA4|0008B9|DRVR|
|139|ArpDxe |8DD91798-EE87-4F0E-8A84-3F998311F930|0040C85D|002F59|DRVR|
|140|SnpDxe |3DD7A87B-D5BD-44AF-986F-2E13DB5D274C|0040F7B6|0037F9|DRVR|
|141|MnpDxe |C30B94E3-C8F2-4AB0-91AB-FA8DF621B1C9|00412FAF|00A779|DRVR|
|142|UefiPxeBcDxe |0EF8A3B1-388A-4B62-8BE6-C7877D50AEDF|0041D728|00D025|DRVR|
|143|NetworkStackSet|0029DE6A-E024-4EB8-A91D-9F23AA1F4E92|0042A74D|000BB9|DRVR|
|144|TcpDxe |B1625D3C-9D2D-4E0D-B864-8A763EE4EC50|0042B306|00BB59|DRVR|
|145|Dhcp4Dxe |8DD9176E-EE87-4F0E-8A84-3F998311F930|00436E5F|006F1D|DRVR|
|146|Ip4ConfigDxe |8F9296EF-2880-4659-B857-915A8901BDC8|0043DD7C|0047C5|DRVR|
|147|Ip4Dxe |8F92960F-2880-4659-B857-915A8901BDC8|00442541|008BD9|DRVR|
|148|Mtftp4Dxe |61AFA223-8AC8-4440-9AB5-762B1BF05156|0044B11A|0056BD|DRVR|
|149|Udp4Dxe |10EE5462-B207-4A4F-ABD8-CB522ECAA3A4|004507D7|005719|DRVR|
|150|Dhcp6Dxe |8DD9176D-EE87-4F0E-8A84-3F998311F930|00455EF0|00689D|DRVR|
|151|Ip6Dxe |8F92960E-2880-4659-B857-915A8901BDC8|0045C78D|010459|DRVR|
|152|Mtftp6Dxe |61AFA251-8AC8-4440-9AB5-762B1BF05156|0046CBE6|00565D|DRVR|
|153|Udp6Dxe |10EE54AE-B207-4A4F-ABD8-CB522ECAA3A4|00472243|0053D9|DRVR|
4- update Intel RST(e) OROM and EFI SateDriver, LAN OROM PXE and EFI UNDI, Intel CPU Microcode to latest version.
then flashed new bios via AfuWin. until this level every thing work so good whitout any issues.
5- update Intel OROM VBIOS and EFI GOP DRIVER
after update this drive i cant access to bios setting and every time that i turn on my laptop i get black screen until windows boot screen will apear. I attache my original and moded bis files.
https://mega.nz/#!u8JEQJrC!-A7FuifF2xKWT…vQ6cOVka79oQyZk
please if you could help me. thanks
@rafigh89 :
Welcome to the Win-RAID Forum!
Since the other thread is reserved for SoniX’s announcements of new UBU versions or updates, I have moved your post into this “UBU Discussion” thread.
I am pretty sure, that you will get a reply to your report from SoniX or someone else, who knows more about this topic than me.
Regards
Dieter (alias Fernando)
@rafigh89
I am pretty sure UBU was created specially for desktop systems. Here is disclaimer in first page of UBU:
The UBU tool has been designed and optimized for the modification of Desktop mainboard BIOSes. According the feedback we got until now the usage of the tool with Desktop mainboard UEFI BIOSes is very safe.
Nevertheless it is possible, but only recommended for advanced users, to update some modules of a Mobile system BIOS (except the VGA ROM!) by using the UBU tool. For further details please read >this< post written by plutomaniac.
This could have something to do with the graphics vbios in case you boot in non uefi modus.
Boot UEFI modus is about Windows - whether it is installed to boot in UEFI mode. BIOS itself is UEFI. It has CSM but still it is UEFI always. And guy was talking about inability to enter BIOS setup.
Hallo a quick question.
when i replace broadwell and haswell microcodes in bios i need only this?
Check the Address in the FIT
Address 01 mCode + Size 01 mCode = Address 02 mCode
or also
Address 02 mCode + Size 02 mCode = Address 03 mCode
Or the size of haswell microcode dont matters?
@SoniX
Can I suggest a change in UBU.bat?
I did change UBU locally to be able to process bin-file with newest microcode for 2011 platform CPU (IB-E 4930). Option for selection of bin-file for 2011 platform doesn`t work with bin-files, because there is no code for bin-files - only code for pre-processed ffs-files. So I just brutally forced to get needed bin-file completely bypassing the code for 2011 platform microcode file selection and execution (and it worked normally).
It would be nice if manual selection of bin-file (menu item "m") with microcode was processed in same way for all processors.
@mbk1969
In UBU v1.70, for microcodes LGA2011, another mechanism will be implemented. Similarly for other platforms.
You can, in all versions, make changes for yourself.
@SoniX
I did. But for users who are not experienced with bat-files it will be impossible.
Anyway thank you for this work. I was greatly impressed by the things this bat-file can do, and by the clean syntax too. (Although nowadays I prefer PowerShell scripts since I am .Net programmer…)