It is SoniX.
Please post them or send SoniX a PM.
Last time i PM’d him i got no reply.
Last time i PM’d him i got no reply.
It is SoniX.
Please post them or send SoniX a PM.
Last time i PM’d him i got no reply.
Sorry… I simply can not respond to all in PM.
@GlitchyHack
You may have to try to update the program.
If you need the source code utilities, you can find them on GitHub
-----
Ladies and gentlemen. My apologies, but I take time out for a while. Excuse me, but I also need to rest, at least a week.
Hello there, not exactly sure what you mean but this is what comes up with the stock BIOS as options. If I use this, the LAN options mentioned previously in BIOS disappear.
@error-id10t
Update LAN for those who use the boot OS on the LAN.
If you do not use this option to load the OS, then this update do not need.
Sorry… I simply can not respond to all in PM.
@GlitchyHack
You may have to try to update the program.
If you need the source code utilities, you can find them on GitHub
I wanted to say i recreated all three of those tools you use in your UBU into one tool. HexFind OROM Version find and efi option rom version find. It’s coded in c#. would you rather use one .exe file rather than three? if so when i finish this up i’ll send you it.
EDIT by Fernando: Quoted text shortened (to save space)
Thanks a lot lordkag! Every contribution to solve an issue is welcome and as i’m a IT tech and i love to try and test mods to see if they give some benefits, i’ll surely integrate your module and test it and i’ll report if it works as expected.
Have a nice week-end! 
Cheers,
KK
@lordkag
Hello lordkag! It’s me again to inform you that your LGA1155over.ffs worked well! 
Your thoughts about the microcodes that must be placed in reverse order, starting from higher CPUID is right.
Two friends of mine have modded their BIOSes of their respective Gigabyte Z77X motherboards that are different from mine and each others (e.g. 3 different models tested) and all went fine from the first boot after BIOS flash.
With previous LGA1155.ffs module coming from UBU 1.65/1.67 they were experiencing same issues as i indicated in my previous posts but now everything seems fine.
Thanks a lot from me and my friends for your collaboration and time that you deserved to check and solve this issue. 
@SoniX
Hello SoniX! The LGA1155over.ffs prepared by lordkag is safe for Gigabyte motherboards. Thank you and have a nice week-end!
Thank you. Ñ# utilities will require installed .NET framework, so it’s not an option.
@killkernel
Ok! Apparently GB that something is. I certainly will correct all modules have a future date and will follow a certain order. 
Problem with UBU 1.6.1 microcode updating (the first one that’s SB-E and IB-E). Can anyone confirm if it works or fails for them?
1) Extracted .CAP and placed in UBU folder
2) Started UBU.
3) Enter 8, seems to scan correctly.
4) Enter 1 and fail. The second window (MMtool) reports “file size exceeds the volume size”.
BIOS download: http://dlcdnet.asus.com/pub/ASUS/mb/LGA2…E-ASUS-0801.zip
Also a note for UBU developers - any chance of checking that spaces in filenames will work? I had a BIOS named “ASUS-X79-0701 (2014-02).CAP” and UBU fell over on the spaces in the filename until I renamed it. Shouldn’t be an issue, presumably some command or other needs quotes!
@ Stilez:
I just have tested it and had no problem with the update of the Intel RAID ROM and SataDriver modules to v12.9.0.2006.
Look here:
- An original BIOS name usually doesn’t contain any spaces.
2. If you want to flash a modded capsuled ASUS BOS (with the extension ".CAP"), you have to rename the BIOS file anyway, because the USB Flashback method requires a special BIOS name according to ASUS’ flashback rules. The ASUS tool named "BIOS Renamer" (look >here<) or the UBU tool itself will do it for you.
Thank you. Ñ# utilities will require installed .NET framework, so it’s not an option.
You do know windows Installs .net framework for you, and even comes preinstalled with windows right? My UEFI Download Tool program is 100% coded in c# and i don’t see anyone having issues.
That’s because windows update gives you the newest .net because a lot of applications use it not just mine i Mean a lot.
EDIT by Fernando: Unneeded quoted text deleted (to save space)
Which .NET Framework version and which Windows version do you mean?
Usage of .NET framework makes the program bound to Windows (I know about Mono and stuff but it doesn’t work as expected nearly 100% times), which is not a problem right now (because of MMTool usage, that is Windows-only app), but can become a problem later when MMTool will be replaced.
The main reason I’ve started UEFITool project was that PhoenixTool was closed-source Windows-only .NET 3.5 application. Yes, C# lets you write software quicker and don’t bother about memory leaks, but nothing comes without it’s price and having to download the whole .NET framework to use a very simple commandline utility - it’s a bit too much for me.
Fixed CPU microcode modules. Made in order from highest to lowest.
Edit:
Fixed in UBU 1.7.0
Even I Do not Know. I looked, there are so many modules that will be difficult oriented update. Leave until both output version.
ASPEED:
I focused on those modules that are in the BIOS from Asus P9D series.
Intel GOP:
Version 3.0.1020 has a small bug.
1
00 33 00 !2E! 00 30 00 00 00 31 00 30 00 32 00 30 00..... == 3.0.
!2E! - must be byte 0x00.
Quite possibly the same bug and 2.0.xxxx version. We can conclude the full version for the old format as 3.0.15.0019.
Added.
Zitat von SoniX im Beitrag #622
Added.
Where? Is there already a new UBU version available or is it a silent update of the v1.6.1?
Zitat von Fernando im Beitrag #623Zitat von SoniX im Beitrag #622Where? Is there already a new UBU version available or is it a silent update of the v1.6.1?
Added.
Oops! Sorry.
Added in 1.7.0. I think next week will lay out the release until I test.
Hello SoniX! Me and 2 friends of mine involved in CPU micro-code test have integrated your new module and updated our BIOSes of our Gigabyte Z77X motherboards and flashed them…
Everything was fine from the first boot after the flash! 
Cheers,
KK
@error-id10t
Are you saying you used the files I posted, by replacing the ones from UBU, but still get the same problem? Then either this new EFI driver is not for your board (not likely, since they should be compatible with multiple IDs), or another PEI/DXE file needs to be updated for full compatibility. This can only be done by manufacturers.
But as Sonix pointed, you should only care about this if you need Wake-On-Lan or Boot from Lan.
@lordkag
I want a clarification on version Intel GOP 3.0.1020. It’s not like a bug as I thought.
Just very strange division between the numbers. Here are 3 examples.
Version 3.0.15.1016 or 3.0.15.0.1016? (I did not understand.)
1
33 00 2E 00 30 00 00 00 31 00 35 00 00 00 00 00 31 00 30 00 31 00 36 00
3.0.1020
1
33 00 2E 00 30 00 00 00 31 00 30 00 32 00 30 00
3.0.1027
1
33 00 00 00 30 00 00 00 31 00 30 00 32 00 37 00
Note the position of the bytes 0x2E and 0x00 who must share major, minor, revision and build. As a result, there are difficulties to write code to properly display version.
@error-id10t
You mean that stitched Intel LAN version 6.2.08 in UEFI mode in the Setup section of UEFI LAN settings are not available? Example
Edit:
There is a suspicion that Intel LAN version 6.2.08 no one works. I'm waiting for the newer version 6.3.xx or version 6.1.xx will have to return