What your doing wrong is the assumption that a MOD bios file is accepted and will pass on AMI/Gigabyte security measures against modified files/firmware…
If the Q-Flash embedded bios utility fails, you’ll have to use Q-Flash Plus button function with file on USB disk (Most likely method…), if still fails, an SPI programmer.
I do advise you to have a spare USB disk with an UNmodified official bios file for any recover nedded…
Do not recall seeing modern Gigabyte bios releases, that let us modify/hex edit bios code signature, like was previously possible on older mb hw models.
What your missing, is on the topics you posted, related to xCuri and terminatorul work, this is nothing to do with your issue on flashing a mod bios file, so the answers are there.
Again…???
Sir, the developer of the mod/tool does not have any support thread dedicated to his work here on the forum, do please post on his GitHub page, issues section.
@windowstweaking try to re-start the work with the stock latest bios or any bios version you use, insert the NvStrapsRebar dxe (v0.3 or v0.4-rc1) into the very last section of dxe driver in the volume, and then Q-Flash plus the bios as per what @MeatWar said, go to bios and set your settings and make sure resizable bar is enabled in bios, and then use NvStrapsRebar exe of the respective dxe version (for example, if you use v0.3 nvstraps rebar, use the exe for v0.3.), run the exe as admin, press E, and press S, then reboot.
For size limit, since it is written in hex, you could just convert GiB to Bytes, and put the Bytes value and convert it from Decimal to Hex. For example, i have a 3060Ti with 8GiB vram, so 8 Gibibytes = 8589934592 Bytes, and put in 8589934592 as decimal, and you’ll get 200000000 as a result, and to put it on rBar size limit, it should be 0x0000000200000000.
