Forum - RE: [Discussion] UBU Tool related Questions, Reports and Suggestions

Win-Raid Forum (Drivers - Firmware - Modding) � BIOS Modding � BIOS Modding Guides and Problems � [ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

Page 284 of 335 � Page 1 ... 279 280 281 282 283 284 285 286 287 288 ... 335 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#4246 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 9:23 am

Which additional information do you need from me, the I can give it to you.

This thread has been closed.

#4247 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 11:21 am

@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.

This thread has been closed.

#4248 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 3:53 pm (Last edited: Sat Jul 21, 2018 10:49 pm)

Zitat von SoniX im Beitrag #4245
If, when updating the microcode with UEFIReplace, you received such a message

then use the update with MMTool

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

(Z77 Extreme 4 2.90P beta BIOS)

This thread has been closed.

#4249 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 5:04 pm (Last edited: Sat Jul 21, 2018 7:02 pm)

Zitat
parseFile: invalid data checksum 5Ah, should be AAh

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

This thread has been closed.

#4250 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 6:01 pm (Last edited: Sat Jul 21, 2018 7:03 pm)

Zitat von SoniX im Beitrag #4249
Opem BIOS file in hex editor, find pattern header and replace 5A -> AA

How do we find the pattern header? I've replaced all 5A > AA and now the BIOS file is all messed up

This thread has been closed.

#4251 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 6:09 pm

Do not touch that 5A, because if your BIOS worked before with those it means that nothing was checking those checksums anyway.

This thread has been closed.

#4252 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 7:06 pm (Last edited: Sat Jul 21, 2018 8:58 pm)

Zitat von aiocr im Beitrag #4250
I've replaced all 5A > AA and now the BIOS file is all messed up

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.

This thread has been closed.

#4253 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 9:58 pm (Last edited: Sat Jul 21, 2018 10:47 pm)

Zitat von Varg87 im Beitrag #4248
Zitat von SoniX im Beitrag #4245
If, when updating the microcode with UEFIReplace, you received such a message

then use the update with MMTool
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 ;)

This thread has been closed.

#4254 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 10:12 pm

@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

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

This thread has been closed.

#4255 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 10:29 pm

@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

This thread has been closed.

#4256 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sat Jul 21, 2018 11:43 pm

@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.

This thread has been closed.

#4257 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sun Jul 22, 2018 8:53 pm

Zitat von Maghook im Beitrag #4253
Zitat von Varg87 im Beitrag #4248
Zitat von SoniX im Beitrag #4245
If, when updating the microcode with UEFIReplace, you received such a message

then use the update with MMTool
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.

This thread has been closed.

#4258 | RE: [Discussion] UBU Tool related Questions, Reports and Suggestions datum

Sun Jul 22, 2018 10:06 pm (Last edited: Sun Jul 22, 2018 10:07 pm)

I modded Hero VIII 3802 bios to current and used Asus flashback function

This thread has been closed.

#4259 | RE: UEFI BIOS Updater Update v1.70 b19 Dev fix datum

Tue Jul 24, 2018 1:45 am (Last edited: Tue Jul 24, 2018 2:30 am)

Zitat von mockingbird im Beitrag #4200
I'm trying to update an HP BIOS which is APTIO 4.

When I do the microcode update, it works, but it replaces all the microcodes with only the two microcodes it updates.

Any advice?

Thanks

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:

Zitat von plutomaniac im Beitrag CPU Microcode BIOS modding questions/problems
I did some searching at cpu world and basically

06A1-06A5 are Nahalem CPUID's --> useless for Z77
06A6 is only for mobile i7-2720QM SB ES/QS cpu --> useless for Z77
06A8 is only for some mobile IVB ES/QS cpus --> useless for Z77

So I will leave only 06A7_28 and 06A9_19

http://imagizer.imageshack.com/img661/1580/jiFOtC.png

Alternatively, this is done automatically by UBU (leaves only 06A7 and 06A9).

mockingbird has attached files to this post

JOS_820_test1.zip

This thread has been closed.

#4260 | RE: UEFI BIOS Updater Update v1.70 b19 Dev fix datum

Tue Jul 24, 2018 3:40 am

Hi SoniX!

This is normal?

This thread has been closed.

BIOS Company �

Page 284 of 335 � Page 1 ... 279 280 281 282 283 284 285 286 287 288 ... 335 Page �

Please enter a reason for warning.