Exactly.
If done correctly, we will see:
thanks that is what i though.
got a question can we extract the OROM VBIOS SKL 1043 in your bios using MMTool.exe and just replace it using UEFITool.exe for all the asus z170 deluxe boards.
it seems like alot for work to do all that editing for the vbios for every new bios when we have video cards.
@SoniX :
Thanks, but I haven’t updated modules using MMtool: I used it to find the GUID, then I replaced the LAN modules with UEFITool choosing them from Modules folder of UBU.
EDIT by Fernando: Unneeded fully quoted post removed and replaced by the direct address (to save space)
Thank you very much for this wonderful tool 
I am currently trying to mod a bios for X99 rampage v extreme but can not get UBU to update Boot Agent to 0.1.10 from 0.1.6, I have been searching constantly for the file to manually update. Currently I’m looking through MMTool and trying to see if I can extract the boot agent but I also don’t know the proper GUID for the 0.1.10 , any help will be appreciated, sorry for posting in here about this.
I think this script to make it easier update Boot Agent CL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
@echo off
pushd %~dp0
cls
set fbios=%1
if not defined fbios echo Not File BIOS && pause && exit
set sdl=Modules\LAN
set mmt=start /b /min /wait mmtool %fbios% /e /l
rem Search and Extract current OROM Boot Agent CL
rem Using text “Boot Agent CL” as HEX
for /f "tokens=1,2" %%a in ('uefifind body list 426F6F74204167656E7420434C %fbios%') do (
if %%a==A0327FE0-1FDA-4E5B-905D-B510C45A61D0 (
echo Found Boot Agent CL && echo Found Boot Agent CL>>_#Info_CL.txt
echo GUID %%a && echo GUID %%a>>_#Info_CL.txt
echo SubGUID %%b && echo SubGUID %%b>>_#Info_CL.txt
%mmt% _CurLanCL.lom %%a %%b
)
)
rem Search DevID and Generate new OROM CL
if exist _CurLanCL.lom for /f "eol=; tokens=1,2" %%d in (%sdl%\DevID_List_iCL.txt) do (
hexfind 504349528680%%d _CurLanCL.lom>nul && echo Found DevID %%e && echo Found DevID %%e>>_#Info_CL.txt && %sdl%\romhdr -v 0x8086 -d 0x%%e -i %sdl%\IntlOromCL.LOM -o _New_CL_%%e.lom
)
pause
The appropriate GUID for search in UEFITool see the file _#Info_CL.txt
Start format "<script> <File BIOS>" from folder UBU.
@SoniX
Intel Skylake-Kabylake GOP 9.0.1049
MCE will be released today, MEA tomorrow.
9.0.1049.rar (33.2 KB)
I noticed that in recent times, many users commits a gross error when updating OROM LAN Intel, on BIOS Aptio 5.
I want to remind you that all the files * .LOM, which are located in the “Modules\LAN” folder, the default Device ID FFFF. And they can not be used as it is, an exception only for Realtek.
I have repeatedly pointed out how to make the correct Device ID, but zero sense.
Therefore, starting from version 1.60, UBU will create the necessary files. The basis of the script is taken from >here<.
In UBU, in a LAN update section for BIOS Aptio 5, will be the new item to create the necessary files.
With latest version 1.60 it creates duplicated efi gop driver in the list when updating, but after closing and reopening ubu, it appears correctly once time.
Attach BIOS file.
I also got the double GOP message as well as this error message;
Could Not Find D:\UBU_v1_60\tmp\igop_A0327FE0-1FDA-4E5B-905D-B510C45A61D0 380B6B4F-1454-41F2-A6D3-61D1333E8CB4.tmp
Although the GOP driver was successfully updated.
BIOS Link
Let’s see.
Added:
Got it. It displays the old and the new GOP after the upgrade. Old is not removed from the TMP folder.
I’ll fix it. Thank you for the information.
@ SoniX:
At 1150 ucode, I have added cpu00040671_plat22_ver00000015_date#04-03-2016 which is not the latest (16 is) but was missing from UBU. 
Modules.rar (12.4 KB)
I’m trying to update the IRST OROM and EFI to 15.0.0.2606 but only the EFI gets updated, is this normal?
Yes, if the BIOS on Aptio 5 platform.
@SoniX
Intel Skylake-Kabylake GOP 9.0.1051
Intel Skylake GOP Addon SKL_1001_VBT207_GOP9.0.1051
8086-0406 Intel Skylake-Kabylake VBIOS 9.0.1045 (new with proper SignOn Message as far as I can see)
cpu000906E9_plat22_ver00000034_date10-07-2016 (KBL H/S)
Don’t forget this before new release. 
9.0.1045_9.0.1051_MC.rar (164 KB)
@Fernando
From topic to topic. We need your wise counsel.
Currently, UBU offers a choice of several versions of IRST
What do you think, probably need to remove some versions as "not optimal", and the remaining complement comment?
If so, what version, in your opinion, can be removed?
I think that the issue like this comment:
1
2
3
4
5
2
3
4
5
1 - 11.xxxxxx - Optimal for 6-series
2 - 13.xxxxxx - Optimal for 7-series
....
etc
I think that this version will deliver on many issues.
@SoniX
cpu000306C3_plat32_ver00000021 Date: 10-05-2016
cpu000306C3_plat32_ver00000021_date#10-05-2016.zip (22.2 KB)
@SoniX.
According to my experience with different Intel RAID systems you can remove the following Intel RAID BIOS modules from the UBU tool: v11.6.0.1702, v13.5.0.2164 and v15.0.0.2371.
If you want to add some special comments to the offered Intel RAID module versions, I would do it in this way (provided, that there is enough space within the related lines):
1
2
3
4
5
6
2
3
4
5
6
1 - Update to v11.2.0.1527 only OROM (the best for 6-/7-Series)
2 - Update to v12.9.0.2006 (good for 6-Series)
3 - Update to v13.1.0.2126 (good for 7-Series and X79)
4 - Update to v13.2.2.2224/13.2.0.2134 (good for 8-/9-/100-Series)
5 - Update to v14.8.2.2397 (good for 8-/9-Series and X99)
6 - Update to v15.0.0.2606 (only for 100-/200-Series)
By the way:
Since I have now an ASRock Z170 mainboard, I have tried to do some benchmark tests using the Intel RST drivers v11.2.0.1006, v12.9.4.1000 and v13.2.4.1000.
This is what the UBU tool shows regarding the Intel RAID modules with the original BIOS:
And this is what the UBU tool shows after having downgraded the Intel RAID ROM/EFI modules to v11.2.0.1527 (manually done with the AMI Aptio V MMTool) resp. v12.9.0.2006 (done by the UBU tool:
As you can see, both Intel RAID modules have been downgraded successfully, but now the BIOS contains 2 different Intel RAID ROM modules, the stock version v14.6.0.2285 and the v11.2.0.1527.
When I open the modded BIOS by using the Aptio V MMTool, I can easily find the Intel RAID ROM v11.2.0.1006 (it is on the same place, where the v14.6.0.2285 was), but I cannot find the other Intel RAID ROM v14.6.0.2285, which seems still to be present within the BIOS.
Do you know where it is and how is it possible, that the stock OROM remains within the BIOS although it had been successfully replaced by another version?
The related modded BIOS is attached.
Z17PGI72.rar (7.39 MB)