@tistou77

I made some changes to the microcode update process.

@Sonix
the process to update the microcode with UBU, proceeds without error, just this problem at boot (the 4F error will be related to the DXE, I believe)
https://dlcdnets.asus.com/pub/ASUS/mb/LG...E-ASUS-1603.zip

The strange thing is that with old UBU version I was able to add/replace modules on 1603 bios, with UEFI Tool in order to not have any issues with MMTool using UBU.

Now, even replacing iRST efi module with Uefi Tool, MMTool reports a "firmware volume error". It's a very strange thing. No problems at all using Rampage V Extreme 3902 bios I modded again yesterday
in the same way.

I solved the problem of 4F error,
Unfortunately, the error 55 could be solved only by MMTool, since the UEFITool/UEFIReplace is not doing the Rebuild PEI volumes

We must look for a newer version of MMT than 5.2/

@SoniX

Thanks, how you solved the problem of 4F error ?

@tistou77

The current version of UBU makes replacing an empty (Dummy) file with another empty (Dummy) file with a new GUID.The next version of the UBU will change the GUID immediately in the BIOS file, without replacing the file itself.
That is, the structure of the DXE volume will not rebuild.

But this solves old problems, but does not solve new ones.

@SoniX

Ok thanks so much,
I'll wait for the next version of UBU to test

Thank to all staffs here, For my opinion Shamino and his teams locked microcode revision by update RC (Revision Check). If we trying to update microcode that newier than 0200004D directly by UBUTool you’ll get “ 4F CPU Check “ error when ASUS Flash back finished. By Sylar76 method the RC will check sized of bios file. If we consider 1603 original bios file size and 1503 or older there were a bit different. This was the new trick they’d play with us all.

If we could remove RC code above by next UBU, It will be very easy to use our existing UBUTools to modded next BIOS.

@tistou77
Try.
https://cloud.mail.ru/public/2o5x/SLk7oZ9ZU

@SoniX
Tried and it's good ;)

Does it work with latest cpu microcodes ? Which method has been used ? (MMTool I suppose).

With microcode 57

@Sylar76
You will not believe. MMIT 5.0.0.7.

But could I use the hex editing method extracting the microcode GUID file, replacing all needed cpu microcodes, fixing the _FIT_ problem, and then replacing it with MMIT 5.0.0.7 ?

MMTool 5.0.0.7 work with this bios and microcode (for open the bios and update microcode, not tested fo flash)