Hi, i need help to update mine bios not update with integration microcode intel, and i have trying to use for a similary Motherboard, but there is security i think the name witting in .Cab (at 3 letters around not good) also the bios is refused i ahve an Z97 chipset! (2solutions i wait asus to keep out the new one bios or i create mine with your tuto)
4790K Z97-Pro-GAMER 2203 bios to update at Z97-PRO 3503 same version Ami 2.16.1240
Thx for best regards!
PS: Mine Dts key inexistents mac adress false into bios and No s/n Saved
Thx ,for all information on your Tuto Fernanado and coderush for utilies. Finally i have used and upgarde of mine bios since 2016 + upgraded cpu intel microcode last, and after checking spectre default are locked ! Now i need to wait a real new bios by asus certifcated but i m enjoy also Thx a lot and good continuation!
Ps: If i haven’t any information saved about mine motherboard (mac adress false no dts key no serial number),answer me plz if it’s important because i haven’t sticker on mine MB to know this information,and the support of mine MB are been a little lost!)
Best regards
@KOaL4 :
Welcome to the Win-RAID Forum!
1. If you have problems to get the modded BIOS successfully flashed, please look into the start post of >this< thread. This problem has nothing to do with the UBU tool and this thread.
2. What is a “Dts key” and what has it to do with the UBU tool?
Regards
Dieter (alias Fernando)
This is the key of identification of the motherboard same thing of Mac adress principe or the number serial of the motherboard !
Plz I need information i don’t have upagrade all information into mine new bios Rst Gbe Me and others , do you think it s really important !
I have only integrated the new Microcode intel for counter Spectre!
I m a player video game and i m root hacked again and again Scan ACk ddos spoof ip and other used, I search to prevent against mine Pirate(hacker team)!
[DoS attack: ACK Scan] from source: 13.91.60.30:443 Monday, June 04,2018 14:51:10
[DoS attack: ACK Scan] from source: 23.206.8.166:443 Monday, June 04,2018 14:49:09
This is an exemple !And all day 100 times by day !!! I m really boring of this … !
Maybe i do a new bios with all upgrade because i have read the me 9.1.37.1002 with last Mei prevent this Ping attack ddos (maybe) i have actually only the 9.1.25.1005!
Thx to have Answered Best Regards.
If you want to update the Intel Management Engine Firmware, you have to use the related Intel ME Firmware Update tool, which is part of the Intel CSME System Tools. You can get the matching one for your system >here<.
You cannot update the Intel ME Firmware by modifying the BIOS.
Thx for this,i know. I have updated the me, but before use Ubu to create a new bios also mine upadte have been reset ! 
Hi again! I m in work of minenew bios after using the last update bios i see mine CPu a litlle, i check on new bios in create mode using, And i see the code cup since 21.01.2018 also i have bad idea ,maybe i need to change information into Ubu 1.69 in folders by the last ??? no !
Thx for information !
It is not easy to understand what you mean.
The date Of Microcode intel Cpu data is 04.25.2018 and when i use Ubu tu update the microcode the date is 01.18.2018 around this (i think the microcode is the first version and this is not really good in cpu power and uselity! cpu306C3_plat32_ver00000024_2018-01-21_PRD_FCD4700E.bin and after dl the last microcode 06-3c-03 since 26.04.2018.
Thx for, i have checked the file into the last UBU version 1.70 dev B (same thing)
Ps: im not sure if i need to replace the file in 24 position on integrate this in 25th files !
I just went to integrate this cpu306C3_plat32_ver00000025_2018-04-25_PRD_FCD4700E.bin with the new file cpu microcode i’m going to try to launch Ubu (if maybe that s work), that s doesn’t work i have put a file instead the other to check the new cpu microcode,but it s not good (Sorry i m french and it s a little so complicate for me to understand UBU and Possibility of this and the good usefull of this !
Thx again !
Put that file in >> Files\intel\mCode\1150
Then modify MCUpdate.txt at UBU Folder root (may not be exact name of your version, not sure I have latest) >> UBU_v1_70_b1_Dev\Files\intel\mCode
At 1150 section, put full file name and location in place of the line for version #24. If name is same as above, after putting file in folder, edit the line for #24 with this instead so it points to your new file.
306C3 1150\cpu306C3_plat32_ver00000025_2018-04-25_PRD_FCD4700E.bin
The restart UBU and it will update and show as expected with new updated microcode.
@SoniX
I have an Asus AMD SABERTOOTH 990FX/GEN3 R2.0 mainboard. The bios microcode is seemingly inside CSMCORE file. All UBU versions can view, extract but can not update bios. Can you check the file for me? Is there anything to do?
https://www.asus.com/us/Motherboards/SAB…/HelpDesk_BIOS/
http://dlcdnet.asus.com/pub/ASUS/mb/Sock…9287.1528137288
Thank you…
@Fernando
I have an Asus AMD SABERTOOTH 990FX/GEN3 R2.0 mainboard. The bios microcode is seemingly inside CSMCORE file. All UBU versions can view, extract but can not update bios. Can you check the file for me? Is there anything to do? I have asked the same question to SoniX, waiting for reply.
https://www.asus.com/us/Motherboards/SAB…/HelpDesk_BIOS/
http://dlcdnet.asus.com/pub/ASUS/mb/Sock…9287.1528137288
Thank you…
@karakarga :
Your download link doesn’t work (message: “File not found.”). Maybe this is the reason why SoniX didn’t send you a reply.
@Fernando & @SoniX
Corrected the above link, probably after some time the given link is dying, for that reason I have added the download page either!
Filename of the latest bios file is: SABERTOOTH-990FX-GEN3-R20-ASUS-2501.zip
@karakarga :
The UBU tool is obviously not (yet) able to update the AMD CPU Microcode of your mainboard.
So you either have to wait for a new BIOS offered by ASUS or to modify the BIOS manually yourself.
If you should have further questions regarding the CPU Microocode update, please post them into the special CPU Microcode Sub-Forum.
Schade,
I have looked but did not manage to do it manually. If you can manually manage to do it, can you post it to me please?
That work (exercise) may be useful for updating UBU functions later time. “The UBU tool is obviously not (yet) able to update the AMD CPU Microcode of your mainboard.” Those modified bios’es may be uploaded to a known place by also adding hash values for others to download, I think!
(I personally downloaded the latest patched version of mmtool, did not do it by myself. No need to do things again and again…)
UBU tells:
7 - CPU MicroCode
View/Extract/Search
If UBU can not update the Microcode, there is no need to Extract and Search options in that case! → And if UBU can extract, than it has to update, wrong?
I already read the guide about “Update of the Intel iGPU VGA ROM (vBIOS)”, but I am not sure how to use these two files (EFI GOP Driver HSW-BDW 5.5.1040 and Intel Haswell-Broadwell VBIOS 5.5.1044). Any advice?
After updating the microcode for the MSI X299 SLI PLUS Bios 1A (https://ca.msi.com/Motherboard/support/X299-SLI-PLUS#down- bios) I get a modded Bios that looks ok with right microcode updates, but it doesn’t work (no boot - have to recover to unmodded version.)
UBU (latest version) gives the following messages when doing the microcode update:
…
[Preparing for replacement]
Empty GUID: parseFile: non-empty pad-file contents will be destroyed after volume modifications
File replaced
mCode GUID: parseFile: non-empty pad-file contents will be destroyed after volume modifications
rebase: can’t determine if TE image base is adjusted or not, rebased TE image may stop working
…
patchVtf: PEI Core entry point can’t be found in VTF. VTF not patched.
File replaced
[Replacement]
mCode FFS: rebase: can’t determine if TE image base is adjusted or not, rebasedTE image may stop working
rebase: can’t determine if TE image base is adjusted or not, rebased TE image may stop working
rebase: can’t determine if TE image base is adjusted or not, rebased TE image may stop working
…
(many more lines…)
Empty FFS: File replaced
Real FIT
01 mCode Offset - FFD00090 == FFD00090
mCode Size - 7C00
02 mCode Offset - FFD07C90 != FFD07090
Fixed - FFD07C90
mCode Size - 7400
03 mCode Offset - FFD0F090 != FFD1E890
Fixed - FFD0F090
mCode Size - 18000
04 mCode Offset - FFD27090 != FFD36890
Fixed - FFD27090
mCode Size - 17800
Backup FIT with Offset
MSI X299 Serirs
!!! Do not update the mCode using UBU. You will get a brick with POST code 06.