@tistou77 - thanks for version info, I didn’t think to try older. Looks like it works OK in UBU with that one, except for that orom, you can do that in UEFITool last if needed.
Looks like @Sylar76 will sort the mod out for you, thanks!
Error with UBU and new bios 1603 Rampage VI Extreme (during OROM - Find and Extract)
bios 1603 Rampage VI Extreme
https://dlcdnets.asus.com/pub/ASUS/mb/LG…E-ASUS-1603.zip
MMTool v4.50.0.23 & v5.0.0.7 can open this file - work properly standalone don’t know
but UBU freezes at end of detection of OROM - Find and Extract with these MMTool versions
Workaround ?
@tistou77
Here is your requested modded bios.
https://drive.google.com/open?id=1W7A4bf…aKKejHXzJg_Shks
Thanks so much to @Sylar76 for sharing the bios
For information, I noticed that UBU works perfectly (last MMTool) with this bios already modified
Hi Sylar76,
how do you modified the Bios?
Are able to update the Asus Rampage VI Apex 1602 Bios too?
- Microcode 55
- EFI & ROM RST 17.0.0.3592
- EFI LAN 0.22 & Boot Agent CL 0.1.13
https://dlcdnets.asus.com/pub/ASUS/mb/LG…X-ASUS-1602.zip
greetings
karlram
@tistou77
I prefer the latest security patches.
Btw. +5° at idle, +5° at load and +5° power limit sounds like a shift in the measurement of the temperatue.
greetings
karlram
@javanse
It is better to use a replacement in the PEI volume.
A replacement in the DXE volume is a test version.
BIOS 1603 Rampage VI Extreme
There is the following solution.
1- Open BIOS ib UBU.
2 - Ignore the error from MMTool.
3 - We make at least one replacement, for example, IRST.
4 - Exit and Restart UBU
Error messages no longer exist.
Trying to modded APEX 1602 and EXTREME 1603 BIOS everything was OK on UBU.
However when use ASUS Flashback method to update completed.
R6E OLED screen displays " CODE : 4F CHECK CPU " within second "beef" sound and stalled.
Look like ASUS update RC 1.1.5 to block anyone modded their BIOS since 1602 and 1603 revision.
It prevent different microcode from 0200004D loaded. I used 02000055 for testing.
Trying SoniX advise above.
@Sylar76 Modded BIOS and my own modded BIOS did not pass update.
Still OLED Screen " CODE 4F CHECK CPU " second "beef" sound and stalled.
We must trying another method.@Sylar76 @Tistou77 @Sonix
According to R6E manual. ERROR CODE 4F ==> DXE IPL is started.
@tistou77
Asus Rampage VI Extreme X299 Bios 1603
I’m confused
Do the bios modded below work properly, partially or not at all ?
Tested or untested ?
https://rog.asus.com/forum/showthread.ph…age4#post747702
12-01-2018 12:54 PM #35
tistou77
For those who would like the bios 1603 with the microcode 49 (no problem of increased temperatures on the cores) and these modules updated
EFI IRST RAID for SATA - 17.0.0.3592
OROM IRST RAID for SATA - 17.0.0.3592
EFI Intel Gigabit UNDI - 0.0.22
OROM Intel Boot Agent CL - 0.1.13
https://drive.google.com/file/d/1W7A…XzJg_Shks/view
Same modules and microcode 55
https://drive.google.com/file/d/1jff…nvQHOAncr/view
Thanks,
biozzz
The bios modded of Sylar76 work properly, I use it 
Does Sylar76 > R6E_1603_TISTOU77 with microcode 55 work without R6E OLED screen errors ?
R6E.CAP CRC32 > AAAE7F40
Thanks !
Master Tistou77, Please Check Sylar76 modded BIOS microcode inside. There is 02000049 inside not 02000055
@Santa2017
Yes Sylar76 modded bios with microcode 49, and I modded a bios based on that of Sylar76 with the microcode 55
Please give me any suggestion. Look like we cannot use same method in the past to update MCU.
It won’t work. I already modded R6A,R6E with 02000055/RST17.0.0.3592/EFI 0.0.22/0.1.13 every module checked twice. I’d following SoniX adviced.
There still CODE 4F CHECK CPU. Did you mean we must update some module first then left the binary file once then modded other modules follow?
@Fernando @SoniX I updated my bios file with cpu microcodes replacement,in the final section I pressed U and the UBU Tool replaced all with “YES” so when I selected “0” and return in main menu it’s mean done? on the latest section UBU Tool asking me for “Rename file” then I pressed “1” and exit automatically closed. so now I can see my R4G.CAP in the UBU folder. Everything is done?