@sr21

Zitat

---

paraseFile: invalid data checksum 5ah, should be AAh

---

If you modify the original BIOS image, then do not pay attention to such a message.

I have tested and got it to update the microcodes for my MSI X299 GAMING PRO CARBON AC

I used the PEI method rather than the DXE volume but I told it not to put the 1151 microcodes back in as I have 2066 CPU.

So -

╔═══════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟─┬─────┬────────────────┬────────┬──────────┬────┬───────┬────────┬────╢
║#│CPUID│ Platform ID │Revision│ Date │Type│ Size │ Offset │Last║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║1│50655│B7 (0,1,2,4,5,7)│300000D │2018-06-15│PRD │ 0xAC00│0xD00090│ No ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║2│50654│B7 (0,1,2,4,5,7)│200004D │2018-05-15│PRD │ 0x7C00│0xD0AC90│ No ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║3│506E8│ 22 (1,5) │ 34 │2016-07-10│PRD │0x17800│0xD12890│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║4│906E9│ 2A (1,3,5) │ 9A │2018-07-16│PRD │0x18000│0xD2A090│ No ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║5│50652│ 97 (0,1,2,4,7) │80000037│2017-05-02│PRE │ 0x7400│0xD42090│Yes ║
╚═╧═════╧════════════════╧════════╧══════════╧════╧═══════╧════════╧════╝

C - Create FFS with microcodes

P - Replacement in PEI volume

#Do not remove this file.
#This file is for updating microcodes for MSI x299.
#
#To avoid a possible error - "Error in Saving",
# set '#' at the beginning of the line that you turn off.
#

50655 2066\cpu50655_platB7_ver03000010_2018-11-16_PRD_7587C182.bin
50654 2066\cpu50654_platB7_ver0200005D_2019-03-07_PRD_2C268A86.bin
50652 2066\cpu50652_plat97_ver80000037_2017-05-02_PRE_1762DDF7.bin
#906E9 1151\cpu906E9_plat2A_ver000000B4_2019-04-01_PRD_DACDA920.bin
#506E8 1151\cpu506E8_plat22_ver00000034_2016-07-10_PRD_57D53E7A.bin

Save - Exit

╔══════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟─┬─────┬────────────────┬────────┬──────────┬────┬──────┬────────┬────╢
║#│CPUID│ Platform ID │Revision│ Date │Type│ Size │ Offset │Last║
╟─┼─────┼────────────────┼────────┼──────────┼────┼──────┼────────┼────╢
║1│50655│B7 (0,1,2,4,5,7)│3000010 │2018-11-16│PRD │0xB800│0xD00090│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼──────┼────────┼────╢
║2│50654│B7 (0,1,2,4,5,7)│200005D │2019-03-07│PRD │0x8000│0xD0B890│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼──────┼────────┼────╢
║3│50652│ 97 (0,1,2,4,7) │80000037│2017-05-02│PRE │0x7400│0xD13890│Yes ║
╚═╧═════╧════════════════╧════════╧══════════╧════╧══════╧════════╧════╝

Updated the BIOS on my secondary BIOS Chip -

AIDA64 -

CPUID Properties
CPUID Manufacturer GenuineIntel
CPUID CPU Name Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz
CPUID Revision 00050654h
IA Brand ID 00h (Unknown)
Platform ID 53h / MC 04h (LGA2066)
Microcode Update Revision 5Dh

Glad I did not have to go down the DXE Volume Route as heard it has some oddities :)

Zitat von thinking im Beitrag #99

---

@vuze4u
mmtool v5.0.0.7 for Aptio IV BIOS ,remamed as "mmtool_a4.exe"
mmtool v5.2.0.24 for Aptio V BIOS,renamed as "mmtool_a5.exe"
I have copied both two versions of MMTool to root of the UBU directory.

---

Also want to clarify something I read on page 4 that it is advised not to use a FPTW64 -d dump.bin into Ubutool?

If I understand correctly it is advised to use the stock and not use a backup dump file?

Thank you

Thank you for your question. I'm also confusing now. Because My motherboard is Z97 ,I operated according to the instructions in this thread:[Tool Guide+News] "UEFI BIOS Updater" (UBU)
Was I wrong before?

@davidm71 - no matter what answer you get, and how you end up doing things, do not flash stock BIOS via FPT, unless you edit in your NVRAM volumes, and board specific details (serial, UUID, LAN MAC etc) or all will be lost.
I believe what you're referring to is a discussion SoniX and I were having, he mentioned sometimes it may be an issue to use FPT dump, due to FIT corrections, but I've never seen that myself so I say it's OK to use BIOS region dump with UBU
But that may not apply to all instances? BIOS that my thoughts do not apply to, where you can't use BIOS region with UBU, I've never seen myself but I also don't use UBU for actual edits all that often either.

Zitat von Lost_N_BIOS im Beitrag #111

---

@davidm71 - no matter what answer you get, and how you end up doing things, do not flash stock BIOS via FPT, unless you edit in your NVRAM volumes, and board specific details (serial, UUID, LAN MAC etc) or all will be lost.
I believe what you're referring to is a discussion SoniX and I were having, he mentioned sometimes it may be an issue to use FPT dump, due to FIT corrections, but I've never seen that myself so I say it's OK to use BIOS region dump with UBU
But that may not apply to all instances? BIOS that my thoughts do not apply to, where you can't use BIOS region with UBU, I've never seen myself but I also don't use UBU for actual edits all that often either.

---

You're welcome - SoniX was saying that sometimes, in some BIOS/instances, this can mess up the FIT Table. I've never seen that happen, only when changing microcodes manually or with UBU at times, which we (or UBU) correct the FIT table afterwards anyway when it's present.

You'll have to wait on SoniX to answer you on the rest of that about renaming or which to use for that board, I am not sure what's going on and have been waiting for all these recent changes with this or that MMTool version to get more "finalized" before downloading UBU again
I do all mods by hand, but I do use UBU tool often to find a modules UUID quickly, or to show users something information-wise (modules present, version etc). Still using UBU_v1_70_rc20_1 as of now.

Hello @Pacman! :))

Thank you very much.
I saw on the site, but I could not download it. Captcha is poorly selected.

Zitat von westlake im Beitrag #116

---

---

Hi all,

I tried latest UBU tool (1.73.1 and 1.73.2) to mod the latest official ASUS BIOS v3603 for the P8Z68-V-PRO (non-GEN3) board with new microcode and newer option ROM versions.

The result was: The full package (modding all option ROMs to newest offered by UBU) failed!

What worked was:
- updating Intel RST ROM to v13.1.0.2126 (although Fernando suggests keeping a 12.x version for the Z68 chipset generation, this is unfortunately not offered by UBU)
- updating Intel microcodes (esp. Sandy Bridge 206A7)
- updating Marvell ROMs (for the 6 Gbps SATA ports)
- keeping Intel Video BIOS at v2124 (which seems to be rather recent anyway)
- keeping JMicron ROM at v1.7.23 (eSATA ports; version is not too far behind the offered v1.08.01 and v1.07.28)
- keeping Intel GbE Boot ROM

When it failed, I could quickly see a full screen BIOS logo followed by a blinking cursor in the top left. Pressing any key at any time did not change anything. The boot device LED on the board stayed constantly lit (like it is during a normal boot). My last resort was a cheap CH341A-based flasher and flashtool under Linux which quickly restored the thankfully socketed BIOS chip (Winbond) to a working condition by just writing the official v3603 BIOS on it .

I am, however, unsure why it failed and I admit, that I didn't want to try every possible remaining combination. The two culprit ROMs in question (to me) are the JMicron 363 ROM and the Intel GbE Boot ROM.

The JMicron ROM seems to be the very first in the boot order. When I tried v1.08.1 I saw nothing on screen, v1.7.28 showed a message and even detected an attached disk, but booting didn't continue. So maybe updating the Intel GbE Boot ROM would perhaps be possible in addition, I deemed it not worthy as I don't do a PXE boot.

If any of the UBU devs is interested, I still have the failed modding attempts as files.

To all the others, this is a warning to not update every ROM offered! There was no other way except for using an EEPROM writer to restore the BIOS. All the CrashFree3 BIOS restore magic for failed flashes just did not work!

Cheers
weaker

@Fernando:

Zitat

---

The UBU tool doesn't offer any Intel RST RAID ROM module. You can choose the desired version yourself by putting the file into the related UBU subfolder.

---

OK, then I must have done that by myself upon preparation. Probably late at night
I read a lot before I tried and of course I read also the thread you linked.
Do you think it makes a noticeable difference between Intel RST 13.1 and the recommended 12.x version? So far, everything is solid and quick. And the pauses (probably due to SATA link power management) are also gone.