xtreger wrote on 2024-10-26, 22:16:

Hi, I have a GA-G31M-ES2L motherboard that has a useful Dual Bios feature. Unfortunately it also comes with a really ugly Dual B […]
Show full quote

Hi, I have a GA-G31M-ES2L motherboard that has a useful Dual Bios feature. Unfortunately it also comes with a really ugly Dual Bios logo on the POST screen, which I want to remove. May seem like a silly endeavor but it is the only thing standing between me and that nostalgic boot screen I remember from childhood.

I watched a nice video by Bits und Bolts on how to change the top right EPA logo, and I thought I could try something similar.

First step: backup up the current BIOS image. Uniflash doesn't work for my system (I don't think it supports it) - the Flash option itself is disabled, and its BIOS backup to file is incomplete. Next I tried Gigabyte's own @BIOS utility, and that output a 512 KB image which seems to be complete.

Running CBROM to display details of the original BIOS image gives this

Copy code to clipboard

1CBROM V2.20 (C)Phoenix Technologies, Ltd 2001 All Rights Reserved.
2
3              ********  ORIGBAK.BIN BIOS component ********
4
5 No. Item-Name         Original-Size   Compressed-Size Original-File-Name 
6================================================================================  0. System BIOS       20000h(128.00K)1493Fh(82.31K)tt.BIN
7  1. XGROUP CODE       0E610h(57.52K)0A279h(40.62K)awardext.rom
8  2. ACPI table        042D4h(16.71K)0195Bh(6.34K)ACPITBL.BIN
9  3. EPA LOGO          0168Ch(5.64K)0030Dh(0.76K)AwardBmp.bmp
10  4. GROUP ROM[18]     03560h(13.34K)023F7h(8.99K)ggroup.bin
11  5. GROUP ROM[20]     028C0h(10.19K)01E8Dh(7.64K)ffgroup.bin
12  6. YGROUP ROM        0C300h(48.75K)06748h(25.82K)awardeyt.rom
13  7. GROUP ROM[22]     0F630h(61.55K)006A9h(1.67K)tgroup.bin
14  8. GROUP ROM[23]     0F630h(61.55K)0015Bh(0.34K)t1group.bin
15  9. GROUP ROM[24]     0F630h(61.55K)0055Eh(1.34K)t2group.bin
16 10. GROUP ROM[ 0]     078C0h(30.19K)02D5Ah(11.34K)_EN_CODE.BIN
17 11. VGA ROM[1]        0C000h(48.00K)078C6h(30.19K)BLB_1471.DAT
18 12. Other(4069:0000)  07400h(29.00K)07433h(29.05K)MEMINIT.BIN
19 13. PCI ROM[A]        0A800h(42.00K)06479h(25.12K)AR8131.lom
20 14. LOGO1 ROM         00B64h(2.85K)00520h(1.28K)dbios.bmp
21 15. Other(4067:0000)  022ADh(8.67K)00BD6h(2.96K)PPMINIT.ROM
22 16. OEM0 CODE         03006h(12.01K)022A6h(8.66K)SBF.BIN
23
24  Total compress code space  = 66000h(408.00K)
25  Total compressed code size = 471B6h(284.43K)
26  Remain compress code space = 1EE4Ah(123.57K)
27
28                          ** Micro Code Information **
29Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID
30------------------+--------------------+--------------------+-------------------
31SLOT1  0A   0F32|  

Next I used "cbrom orig.bin /logo1 extract" to extract the EPA file (disguised as a bmp file) to disk. I used EPACoder 1.52 to convert it to a BMP, opened the BMP in paint, colored it all black, and then saved it. When I opened the modified BMP file in EPACoder, I got this: https://imgur.com/a/IEvDHlN ("Non-standard Image dimensions: "BiosLogo.bmp"! Load anyway?" -> OK -> Are you really sure? -> Yes)

My guess is that the dimensions of the energy star EPA logo and the dual bios logo are different, and the EPACoder application has been hardcoded to check if the uploaded BMP's dimension matches the standard energy star logo's dimensions.
Anyways, I convert it back to EPA and saved it. Then I used CBROM to add it back to the BIOS image:

Copy code to clipboard

1>cbrom orig.bin /logo1 dbios.bmp
2CBROM V2.20 (C)Phoenix Technologies, Ltd 2001 All Rights Reserved.
3Adding dbios.bmp  2.0%

where I renamed the modded EPA file to "dbios.bmp" since that's the name the dual bios image file had in the original BIOS image.

The modded BIOS image gives following details in CBROM:

Copy code to clipboard

1CBROM V2.20 (C)Phoenix Technologies, Ltd 2001 All Rights Reserved.
2
3              ********      mod.bin BIOS component ********
4
5 No. Item-Name         Original-Size   Compressed-Size Original-File-Name 
6================================================================================  0. System BIOS       20000h(128.00K)1493Fh(82.31K)tt.BIN
7  1. XGROUP CODE       0E610h(57.52K)0A279h(40.62K)awardext.rom
8  2. ACPI table        042D4h(16.71K)0195Bh(6.34K)ACPITBL.BIN
9  3. EPA LOGO          0168Ch(5.64K)0030Dh(0.76K)AwardBmp.bmp
10  4. GROUP ROM[18]     03560h(13.34K)023F7h(8.99K)ggroup.bin
11  5. GROUP ROM[20]     028C0h(10.19K)01E8Dh(7.64K)ffgroup.bin
12  6. YGROUP ROM        0C300h(48.75K)06748h(25.82K)awardeyt.rom
13  7. GROUP ROM[22]     0F630h(61.55K)006A9h(1.67K)tgroup.bin
14  8. GROUP ROM[23]     0F630h(61.55K)0015Bh(0.34K)t1group.bin
15  9. GROUP ROM[24]     0F630h(61.55K)0055Eh(1.34K)t2group.bin
16 10. GROUP ROM[ 0]     078C0h(30.19K)02D5Ah(11.34K)_EN_CODE.BIN
17 11. VGA ROM[1]        0C000h(48.00K)078C6h(30.19K)BLB_1471.DAT
18 12. Other(4069:0000)  07400h(29.00K)07433h(29.05K)MEMINIT.BIN
19 13. PCI ROM[A]        0A800h(42.00K)06479h(25.12K)AR8131.lom
20 14. Other(4067:0000)  022ADh(8.67K)00BD6h(2.96K)PPMINIT.ROM
21 15. OEM0 CODE         03006h(12.01K)022A6h(8.66K)SBF.BIN
22 16. LOGO1 ROM         00B64h(2.85K)0005Eh(0.09K)dbios.bmp
23
24  Total compress code space  = 66000h(408.00K)
25  Total compressed code size = 46CF4h(283.24K)
26  Remain compress code space = 1F30Ch(124.76K)
27
28                          ** Micro Code Information **
29Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID
30------------------+--------------------+--------------------+-------------------
31SLOT1  0A   0F32|  

When I flash the original image to BIOS using Gigabyte's DOS flash utility, it goes normally and there are no issues. But when I flash the modded image to BIOS using the exact same procedure, I get this: https://imgur.com/s8VkGic ("MAIN BIOS CHECKSUM ERROR!")

I don't understand what's going wrong. The changing compressed size of the logo1 EPA file shouldn't be an issue I think, since even in Bits und Bolts' video, his EPA logo file size changes (compare https://youtu.be/t2MsCUewvNk? si=5zG6BQ8vSP6afdDw&t=406 vs. https://youtu.be/t2MsCUewvNk?si=hKvq2TIw0nCMPXI6&t=424).

Anyone has any idea on how to solve this thing and finally get rid of that dual bios logo? Thanks

ive got the same board and personally i wouldnt mess with the bios for two reasons, one its dual bios and two they're soldered to the board, if you screw up and brick the board you would have to get a flasher and a adapter clip to re-flash, also ive heard that flashing chips onboard can be problematic due to voltages, meaning you might have to de-solder both to re-flash.

anyway the checksum error is prob because the main bios you modified and just flashed the checksum now doesnt match the original on the backup chip, i think the only way around that is if you havent already updated to the latest bios, modify that one and flash it as the checksum for a different bios will be different so shouldnt have a checksum error, if you are already on the latest bios flash it with an earlier version, then modify the latest bios and flash that, since its dual bios i'm guessing it should flash both chips at the same time unless you're flashing the same bios and theres a checksum difference, if not flash the same bios twice when changing just to be sure both chips are flashed the same.

as i said i wont risk it unless a bios chip can be easily removed and flashed in another board, so do this at your own risk! and cross your fingers it doesnt screw up.

DudeFace wrote on 2024-10-27, 00:32:

ive got the same board and personally i wouldnt mess with the bios for two reasons, one its dual bios and two they're soldered to the board, if you screw up and brick the board you would have to get a flasher and a adapter clip to re-flash, also ive heard that flashing chips onboard can be problematic due to voltages, meaning you might have to de-solder both to re-flash.

anyway the checksum error is prob because the main bios you modified and just flashed the checksum now doesnt match the original on the backup chip, i think the only way around that is if you havent already updated to the latest bios, modify that one and flash it as the checksum for a different bios will be different so shouldnt have a checksum error, if you are already on the latest bios flash it with an earlier version, then modify the latest bios and flash that, since its dual bios i'm guessing it should flash both chips at the same time unless you're flashing the same bios and theres a checksum difference, if not flash the same bios twice when changing just to be sure both chips are flashed the same.

as i said i wont risk it unless a bios chip can be easily removed and flashed in another board, so do this at your own risk! and cross your fingers it doesnt screw up.

Yes! It worked flawlessly. I downloaded the BIOS file of the latest BIOS version from Gigabyte's website, modified it with the edited logo file and used Qflash. The dreaded dual bios logo is now gone! Thanks a lot

A follow-up question - there's a long line in the BIOS starting with "Main Processor: " which eats into the logo on cold boot. Is there any way of getting rid of that line or modifying it, by any chance?

Why didn't you just remove the second big "logo" picture with "cbrom orig.bin /logo1 release" instead of bothering to make it black and injecting back into the bios dump-file?

xtreger wrote on 2024-10-27, 10:26:

A follow-up question - there's a long line in the BIOS starting with "Main Processor: " which eats into the logo on cold boot. Is there any way of getting rid of that line or modifying it, by any chance?

For Award BIOS 6.00PG try MODBIN6 under DOS. I think there's also windows version.

xtreger wrote on 2024-10-27, 10:26:

Yes! It worked flawlessly. I downloaded the BIOS file of the latest BIOS version from Gigabyte's website, modified it with the e […]
Show full quote

DudeFace wrote on 2024-10-27, 00:32:

ive got the same board and personally i wouldnt mess with the bios for two reasons, one its dual bios and two they're soldered to the board, if you screw up and brick the board you would have to get a flasher and a adapter clip to re-flash, also ive heard that flashing chips onboard can be problematic due to voltages, meaning you might have to de-solder both to re-flash.

anyway the checksum error is prob because the main bios you modified and just flashed the checksum now doesnt match the original on the backup chip, i think the only way around that is if you havent already updated to the latest bios, modify that one and flash it as the checksum for a different bios will be different so shouldnt have a checksum error, if you are already on the latest bios flash it with an earlier version, then modify the latest bios and flash that, since its dual bios i'm guessing it should flash both chips at the same time unless you're flashing the same bios and theres a checksum difference, if not flash the same bios twice when changing just to be sure both chips are flashed the same.

as i said i wont risk it unless a bios chip can be easily removed and flashed in another board, so do this at your own risk! and cross your fingers it doesnt screw up.

Yes! It worked flawlessly. I downloaded the BIOS file of the latest BIOS version from Gigabyte's website, modified it with the edited logo file and used Qflash. The dreaded dual bios logo is now gone! Thanks a lot

A follow-up question - there's a long line in the BIOS starting with "Main Processor: " which eats into the logo on cold boot. Is there any way of getting rid of that line or modifying it, by any chance?

nice glad it worked, as for the other problem not to sure myself but i think i've seen other people with the same issue, heres mine, does the same

you may be able to change "main processor" to just "cpu" or just delete it altogether, as analogue programmer said try modbin6, there is a windows version but i've only used it for microcode or unlocking bios features, i forget now, been a while.

analog_programmer wrote on 2024-10-27, 12:05:

Why didn't you just remove the second big "logo" picture with "cbrom orig.bin /logo1 release" instead of bothering to make it black and injecting back into the bios dump-file?

xtreger wrote on 2024-10-27, 10:26:

A follow-up question - there's a long line in the BIOS starting with "Main Processor: " which eats into the logo on cold boot. Is there any way of getting rid of that line or modifying it, by any chance?

For Award BIOS 6.00PG try MODBIN6 under DOS. I think there's also windows version.

That's a good point, and that did occur to me, but earlier I wasn't sure exactly what checksum error meant. I thought that it meant that there was some kind of check whether all the original files injected into the BIOS were present, and I thought removing logo1 altogether would fail the checksum.

After DudeFace's clarification and what you said, it's clear that it's easier to just "release" logo1 and flash that.

Regarding MODBIN, I've had a look at it once but I'm not at all sure which options I could use to remove or modify that "Main Processor" line. If you know, could you guide me on that, please?

xtreger wrote on 2024-10-27, 12:30:

That's a good point, and that did occur to me, but earlier I wasn't sure exactly what checksum error meant. I thought that it me […]
Show full quote

analog_programmer wrote on 2024-10-27, 12:05:

Why didn't you just remove the second big "logo" picture with "cbrom orig.bin /logo1 release" instead of bothering to make it black and injecting back into the bios dump-file?

xtreger wrote on 2024-10-27, 10:26:

A follow-up question - there's a long line in the BIOS starting with "Main Processor: " which eats into the logo on cold boot. Is there any way of getting rid of that line or modifying it, by any chance?

For Award BIOS 6.00PG try MODBIN6 under DOS. I think there's also windows version.

That's a good point, and that did occur to me, but earlier I wasn't sure exactly what checksum error meant. I thought that it meant that there was some kind of check whether all the original files injected into the BIOS were present, and I thought removing logo1 altogether would fail the checksum.

After DudeFace's clarification and what you said, it's clear that it's easier to just "release" logo1 and flash that.

Regarding MODBIN, I've had a look at it once but I'm not at all sure which options I could use to remove or modify that "Main Processor" line. If you know, could you guide me on that, please?

i just had a look with modbin6, as far as i can see you can only rename the menus/option in the bios, not on the post screen, i think that will be a bit more involved, im sure i remember seeing a thread on here where someone did mod the post screen text/change logo, so you may have to have a search, also this may be a good read
https://rayer.g6.cz/romos/romose.htm

rayer is a regular on here so he may be able to point you in the right direction, if all else fails you may have to switch to another cpu with a shorter name.🤣

DudeFace wrote on 2024-10-27, 12:19:

you may be able to change "main processor" to just "cpu" or just delete it altogether, as analogue programmer said try modbin6, there is a windows version but i've only used it for microcode or unlocking bios features, i forget now, been a while.

That would be an easy mod. You would need CBROM 2.15 to extract the string table:

1cbrom215.exe romfile.bin /group extract

and confirm the file name by pressing enter, then find the "Main Processor : " in _EN_CODE.BIN and replace it with "CPU : " and a NUL (0x00) byte - just don't move anything around in the file (so the string becomes something like "CPU : <00>ocessor : <00>", where <00> is the NUL byte) so you won't have to recalculate offsets and rebuild directories. Then put the updated file back into the image:

1cbrom215.exe romfile.bin /group _EN_CODE.BIN

Update(2024-10-30): OP told me that this method results in a corrupted file. Probably it needs a different CBROM version. Do not proceed unless you have a recovery strategy available such as having an EEPROM programmer, hotswap or the bootblock recovery pin shorting trick.

kmeaw wrote on 2024-10-29, 13:18:

That would be an easy mod. You would need CBROM 2.15 to extract the string table: […]
Show full quote

That would be an easy mod. You would need CBROM 2.15 to extract the string table:

Copy code to clipboard

1cbrom215.exe romfile.bin /group extract

and confirm the file name by pressing enter, then find the "Main Processor : " in _EN_CODE.BIN and replace it with "CPU : " and a NUL (0x00) byte - just don't move anything around in the file (so the string becomes something like "CPU : <00>ocessor : <00>", where <00> is the NUL byte) so you won't have to recalculate offsets and rebuild directories. Then put the updated file back into the image:

Copy code to clipboard

1cbrom215.exe romfile.bin /group _EN_CODE.BIN

This is a very clever solution. But wouldn't it be a problem if this edited and reinjected "_EN_CODE.BIN" module becomes the last one in the BIOS structure?

analog_programmer wrote on 2024-10-29, 18:51:

This is a very clever solution. But wouldn't it be a problem if this edited and reinjected "_EN_CODE.BIN" module becomes the last one in the BIOS structure?

No, it would not matter - the decompressor routine will find it by the "load" segment address of 4029.

kmeaw wrote on 2024-10-29, 13:18:

That would be an easy mod. You would need CBROM 2.15 to extract the string table: […]
Show full quote

DudeFace wrote on 2024-10-27, 12:19:

you may be able to change "main processor" to just "cpu" or just delete it altogether, as analogue programmer said try modbin6, there is a windows version but i've only used it for microcode or unlocking bios features, i forget now, been a while.

That would be an easy mod. You would need CBROM 2.15 to extract the string table:

Copy code to clipboard

1cbrom215.exe romfile.bin /group extract

and confirm the file name by pressing enter, then find the "Main Processor : " in _EN_CODE.BIN and replace it with "CPU : " and a NUL (0x00) byte - just don't move anything around in the file (so the string becomes something like "CPU : <00>ocessor : <00>", where <00> is the NUL byte) so you won't have to recalculate offsets and rebuild directories. Then put the updated file back into the image:

Copy code to clipboard

1cbrom215.exe romfile.bin /group _EN_CODE.BIN

sounds straight forward enough, though its been a few years since i've messed with bios, just checked my hdd and looks like i've got .bats setup for cbrom195 for extracting EN_CODE.BIN, not sure wtf i was doing with it as i only remember updating/extracting microcode, pretty sure i had to use cbrom198 and cbrom215 as well depending on whether i was releasing/updating or extracting files as one of the versions was corrupting the bios, i was also having problems doing it on win7 so had to switch to 98 or xp, if it can all be done with cbrom215 that makes it a lot simpler, OP will probably have to have a good read up on how to do this, i spent a few weeks messing with bios back in 2021, and i've already forgotten how i did everything.🤣

So I tried this procedure: just modifying a single character in "Main Processor : " - character 'f' instead of character 'c'. This causes the checksum failure + autorecovery from backup BIOS.

It's kind of strange. Using the same CBROM version (2.20), I had extracted the existing dual bios logo, then made it all black (except one small part that I left out by mistake) and then repackaged it into the BIOS image using that same CBROM version. And this actually worked - I could see the changed DBIOS logo on the POST screen now (the small part of the image, which I'd missed to make black, was still visible). So I think that CBROM 2.20 works for Award 6.00.

The confusing thing is, why isn't this exact same procedure (with the same CBROM v2.20) working for GROUP[0], i.e. _EN_CODE.BIN? Is there anything special about this GROUP[0] component that special handling is needed? Based on what kmeaw said, its position in the BIOS structure shouldn't matter. So then I'm not sure what's so special about _EN_CODE.BIN / GROUP[0] ...