Not for me (Z170 Deluxe)

I used an already modded bios...

Using a clean bios messes things up more!

@gpvecchi
Look carefully title, my screenshot. What sort of model? ;)

Attach your mod file, that something was wrong with him.

Added:
Check Boot Agents:
- Boot Agent CL - DevID 15b8
- Boot Agent GE - DevID 1539
Otherwise, one of the modules will not work.

The issue is with iGE: motherboard has 8086;1559 (as in MMTool) but 1559 is in DevID_List_iCL.txt list. So, if I replace it with the iGE module, UBU can't recognize it.
In attachment a bios build from scratch with all modules (VBIOS, 2x OROM, legacy IRST) replaced BUT the option 3 of UBU.
I'd say that solution is put 1559 in DevID_List_iGE.txt

That's right. DevID 1559 is Boot Agent CL and is not supported by new Boot Agent GE.
There are 2 variants of solutions.
1) Use old Boot Agent GE version 1.5.62 (E1562X3.LOM) + DevID 1559. This is correct and the old module supports the DevID.
2) For new Boot Agent GE 1.5.70 and above use a compatible DevID, eg 1539. That is, to replace the incompatible DeviD 1559 to a compatible 1539 or any of the list "DevID_List_iGE.txt". It will also be correct.

Edit:

You have a complete disaster!
Never use MMTool for replacement Tab "Option ROM" (GUID A032 ....)
We have already talked about this many times, that MMTool spoils this storage.

Now you'll update the BIOS.

Added:
@gpvecchi
Mod for Asus Z170-Deluxe, updated:
- OROM/EFI IRST 15.0.0.2606
- OROM VBIOS SKL 1043
- EFI GOP Driver 9.0.0.1048
- OROM Boot Agent CL 0.1.10 as DevID 15b8 - i219 Lan Chip
- OROM Boor Agent GE 1.5.79 as DevID 1539 instead of 1559 - i210/211 Lan Chip
- EFI Gigabit UNDI 0.0.13
- EFI PRO/1000 UNDI 7.1.07
- CPU mCode SKL 9E

so this is the command
NETWORK OROM

Search patterm "5043495286805915" for DevID 1559 (1539 use this id)
504349528680B815" for DevID 15B8

romhdr.exe -v 0x8086 -d 0x1539 -i IntlOromGE.LOM -o Lan1539.lom
romhdr.exe -v 0x8086 -d 0x15b8 -i IntlOromCL.LOM -o Lan15b8.lom

Then replace Lan1539.lom and Lan15b8.lom it into UEFITool.exe
Is this right.

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

@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
 

Realtek UEFI UNDI Driver v2.037

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.