Bios Mods -The Best BIOS Update and Modification Source

Disclaimer: I am not responsible for any damage caused by this guide, etc., use at your own risk.


Hello! I suppose you came here to find out how to change your ami aptio BIOS splash screen.   That is what the guide is about!

Well, let's keep going.


1) DL UEFITool_0.21.4_win (https://github.com/LongSoft/UEFITool/releases), run UEFITool.exe

2) Ctrl+O, select BIOS file you hopefully already have somewhere ready

3) Ctrl+F, select tab labeled "GUID", input 7BB28B99-61BB-11D5-9A5D-0090273FC14D

4) Double-click on the first of three listed "7BB28B99-61BB-11D5-9A5D-0090273FC14D"

5) Press on plus sign next to 7BB28B99-61BB-11D5-9A5D-0090273FC14D, then again on another

6) Right click on "Raw section" line, "Extract body..." and save

7) You can rename the .raw file to .jpg or whatever that works, irfanview works great on identifying the correct extension

8) Edit the image

9) Rename the image extension to .raw

10) Right click on "Raw section" line, "Replace body..." and select the .raw file

11) Ctrl+S to save the BIOS

12) Done!


Hopefully, the system will work and you will have modded splash screen! (For me it did work on X99UD3.F6 and now I have a pretty HL1 lambda logo instead of gigabyte blablabla :>)

Enjoy!

Hey! I also made a tutorial like you! But for Aptio 3.x and 4.x. You can check it out if you want! https://www.bios-mods.com/forum/Thread-C...trends-Inc. Mine is pretty straightforward (also works for clone motherboards like mine!)

Latest UEFITool A59 doesn't allows to "Replace body..." of a Raw section on Gigabyte Z690 AMI bios, the option is greyed out. Does anyone knows any solution, or an alternative way?

Also, Gigabyte @BIOS / FaceWizard doesn't works too, it's greyed out on Z690 bioses...(

(02-03-2022, 07:35 PM)UEFaye Wrote: [ -> ]Latest UEFITool A59 doesn't allows to "Replace body..."

Who said to use the latest? Follow the guide, download UEFITool 21.

I tried 2.1 first but it doesn't finds the GUID, seems like it doesn't read the BIOS image properly because it says: "parseVolume: unknown file system 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A" and "parseFile: non-empty pad-file contents will be destroyed after volume modifications"

(02-04-2022, 08:39 AM)UEFaye Wrote: [ -> ]seems like it doesn't read the BIOS image properly

No. It's alright.
Try searching for "FF D8 FF" bytes sequence coz it's .jpg files signature. Raw sections is what you are looking for. It is very likely that the first raw section in which this sequence is found is the logo location. There are usually more than one picture in the BIOS.

Obviously it doesn't finds anything, as long as old versions of UEFITool can't read half of Z690 BIOS image contents. However, the latest version of UEFITool that can read this image and where "replace body" option isn't greyed out - is 0.28.0, but after reflashing BIOS all i get is a black screen instead of the new splash screen. This is as far as i could get at the moment, by trying each and every version of UEFITool one by one.

(02-04-2022, 11:54 AM)UEFaye Wrote: [ -> ]old versions of UEFITool can't read half of Z690 BIOS image contents.

This is a good discovery. And I should have backed up my words first. Please accept my apologies.

(02-04-2022, 11:54 AM)UEFaye Wrote: [ -> ]after reflashing BIOS all i get is a black screen

Did you adjust the expected splash screen size in the header of a module?

Basically i extracted the original logo, slightly edited in photoshop and put it back into BIOS image, without any other adjustments in terms of size or color scheme or anything. Only changed the file extension from jpg to raw in order to let UEFITool recognize it

(02-04-2022, 12:29 PM)UEFaye Wrote: [ -> ]i extracted the original logo, slightly edited in photoshop and put it back into BIOS image, without any other adjustments in terms of size

Almost any change affect the size in bytes. More information = bigger size.

(02-04-2022, 12:29 PM)UEFaye Wrote: [ -> ]changed the file extension from jpg to raw in order to let UEFITool recognize it

It doesn't work like that.

Could you just create one of these so-called "requests" and let someone else do the work for you? :)