@SoniX
can you please check this? [Discussion] UBU Tool related Questions, Reports and Suggestions (280)
Regarding MSI Z97.
So, all went well 
! I flashed the modified BIOS with fpt, although it said the bios was identical. So whats the next step? I would like to patch the Sata Controller, GOP,Network and the actual Haswell microcde. Can i use ubu now for that?
@Sylar76 I know you got it, but in case anyone needs the info later after finding our discussion, this helped me along - [GUIDE] AMI INTEL CPU Microcode Update Guide
and this post here on page 3 - [GUIDE] AMI INTEL CPU Microcode Update Guide (3)
@sgthawk - Good all went well! From what @SoniX said sounds like you can go ahead and modify the BIOS and reflash now. Maybe wait for him to confirm which/what method is OK, but I assume he meant once that BIOS tested OK you can go ahead and use UBU then reflash again.
I have updated with the UBU Tool my NIC Cards, and the NIC Intel i211 is now seen at the BIOS as an Intel PRO/1000 Network Connection. Is there a way to fix this, that it is seen again as an Intel i211? I have added also two screenshots of it. I used this version v1_70_b19_Dev_fix1 of the UBU Tool. In Windows is the Network Card correctly detected and in the BIOS Boot Order it is also correctly displayed.
@aiocr & @ALL
If, when updating the microcode with UEFIReplace, you received such a message
then use the update with MMTool
@Lost_N_BIOS
Do not quite understand what needs to be confirmed?
@hitman20
Provided little information.
Which additional information do you need from me, the I can give it to you.
@Lost_N_BIOS
Do not quite understand what needs to be confirmed?
Wanted to give some feedback, i flashed the modified bios with the updates by ubu, and flashed it again wit fpt, for me it was important to patch the microcode 25 for Haswell, again all went fine. I am happy now.
Thx for all the supporters who quickly helped me.
Do you mean without using UBU? Because if I select the MMTool option (A) the error is the same:
Choice:a
[Preparing for replacement]
Empty GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
patchVtf: PEI Core entry point can’t be found in VTF. VTF not patched.
File replaced
[Replacement]
mCode FFS: File replaced
mCode FFS: File replaced
Empty FFS: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
Obsolete format of the CS.
You need to fix it manually in any hex editor.
Opem BIOS file in hex editor, find pattern header and replace 5A → AA
Example
How do we find the pattern header? I’ve replaced all 5A > AA and now the BIOS file is all messed up
Do not touch that 5A, because if your BIOS worked before with those it means that nothing was checking those checksums anyway.
To change it is necessary only in one place, and not everywhere where there is…
In general, this is not a critical error and can be ignored.
Do you mean without using UBU? Because if I select the MMTool option (A) the error is the same:
Choice:a
[Preparing for replacement]
Empty GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
patchVtf: PEI Core entry point can’t be found in VTF. VTF not patched.
File replaced
[Replacement]
mCode FFS: File replaced
mCode FFS: File replaced
Empty FFS: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
I bricked a MSI Z77 GD 55 (Aptio IV) by modding and flashing the bios with UBU 1.70beta. I had no trouble modding it with 1.69 last few times but with 1.70 I also got these checksum errors mentioned above (Intel LAN, latest microcode)
Too bad I ignored these and flashed modded bios. Had a 3 week odyssee buying a FlashCat USB classic digging into this stuff and eventually could revive the board with it using JSPI1 with an external 3,3V power supply.
Had no trouble with Asus Z170 board with UBU1.70 but guess won’t do another try on the Z77 for the next time ahead
@SoniX - I was only referring to this post you made, that once he tested BIOS and it was working then he could go ahead and try to modify BIOS
[Discussion] UBU Tool related Questions, Reports and Suggestions (280)
@sgthawk - nothing more needed, only that you confirmed the initial BIOS SoniX posted was OK and working then you could go ahead and try modding BIOS which you already did and succeeded
@Maghook Wow, thanks for the report. I was about to flash my bios while updating it using UBU 1.70 but now i will forget about it, don’t want to brick mine as well. Might try with 1.69
@Lost_N_BIOS & @sgthawk
If you managed to flash BIOS and everything works, then go to the second stage. Update ONLY EFI/OROM and flush this mod.
If everything works, then proceed with updating the microcodes.
Do you mean without using UBU? Because if I select the MMTool option (A) the error is the same:
Choice:a
[Preparing for replacement]
Empty GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh
patchVtf: PEI Core entry point can’t be found in VTF. VTF not patched.
File replaced
[Replacement]
mCode FFS: File replaced
mCode FFS: File replaced
Empty FFS: parseFile: invalid data checksum 5Ah, should be AAh
File replaced
I bricked a MSI Z77 GD 55 (Aptio IV) by modding and flashing the bios with UBU 1.70beta. I had no trouble modding it with 1.69 last few times but with 1.70 I also got these checksum errors mentioned above (Intel LAN, latest microcode)
Too bad I ignored these and flashed modded bios. Had a 3 week odyssee buying a FlashCat USB classic digging into this stuff and eventually could revive the board with it using JSPI1 with an external 3,3V power supply.
Had no trouble with Asus Z170 board with UBU1.70 but guess won’t do another try on the Z77 for the next time ahead
Thanks for feedback. That’s my concern.
I replaced many modules and upgraded cpu microcodes and always everything went flawless with no errors. I don’t want to risk this time.
Can I ask you how you managed to flash the BIOS with an Asus Z170? I modified a Z170M-Plus BIOS with UBU but instant flash didn’t see it. Fortunately Asus released an updated BIOS with new microcodes a month ago.
I modded Hero VIII 3802 bios to current and used Asus flashback function
I’d like to update my post with more details to help everyone understand what I mean. My board is an HP H-JOSHUA-H61-uATX 1.00, and I’m trying to update the microcodes. Now so far I’ve ascertained the following:
-MMTool 5.0.0.24 Mod will not open the BIOS. It shows an error that it’s not Aptio V
-MMTool 5.0.0.7 opens the BIOS properly, and displays everything, but does not allow removing/adding microcodes
-MMTool 4.50.0.23 Opens the file but is missing the UEFI portion of it
Some errors I’ve encountered while trying different methods on UBUTool:
"Patch block size not known" (Option M1)
"invalid data checksum 5Ah, should be AAh" (all options)
Notice: Only the two new updated microcodes are present. All the other ones are no longer there.
Please see attached BIOS.
EDIT: Ok, I think this post explains it:
JOS_820_test1.zip (3.24 MB)
Hi SoniX!
This is normal?
