I am not sure exactly what is going on, I have tried this over weeks multiple times, and bricked a whole motherboard already; BIOS chip got fried on that one.
I got a replacement motherboard, and still trying to patch ReBar into my system (I really need to use my A770 GPU to its fullest for some projects) but I keep soft bricking it (Can recover with a USB and rcv file).
Here is my process:
Unlock FD by jumping service pins
Dump BIOS region
Modify RebarDXE.ffs into BIOS dump using UEFITool (Old Engine; An error about non-uefi data in free volume space)
Patch using UEFITools (apparently my BIOS doesn’t need patches according to the tool)
Using FPTW64 to flash BIOS region
Reboot after successful flash
Unfortunately after the reboot the system bricks and won’t POST. I am attaching my settings below.
I am suspecting it might have something to do with BootGuard? Is there a way to bypass this?
Attaching a screenshot of a “succesful” flash below. I would be so extremely grateful to anyone who can help me out with this/point me in the right direction. It has been a month since I have been trying to figure this out, and I have already bricked a motherboard and BIOS chip (not recoverable with CH341a as there was a short somewhere)
I can also upload my BIOS & patched .bin files for anyone to go over
Run MEInfo then look for Measured and Verified boot, if that’s value enabled on FPF(PCH) level = X﹏X .
Is there a way to bypass this?
Yes, if both Measured and Verified are enabled only on ME, perform a clean dump with the boot guard set to profile 0. Otherwise, replacing the PCH with a clean one is the only option.
@karfel I see what you mean now, I think this stuff about AMI hash mismatch preventing boot might be it. Also shows up with Boot Guard keys. UEFITool NE does not let me insert after in that volume like the previous UEFITool did.
sadly, there’s nothing we can do to make a mod for this bios, except that you can probably still update Microcode, ME FW, and fix Non-UEFI Data (if it come in the original dump before making mod) as long as it’s outside cyan/red area.
Thank you for your continued assitance, it is much appreciated!
So the volume with the dxe drivers, and rebar inclusion is coming up as green as you can see in the screenshot. This specific version of UEFITools NE does not let me insert after. I have uploaded my BIOS original, as well as modified dumps here for you to check out (unfortunately winraid was not letting me upload here) https://www.mediafire.com/file/dj2cyzizqzhmqgz/bios.zip/file
UEFITool NE supposed used to be only for viewing inside the bios that help modder to extract module, Intel Boot Guard coverage, manual editing in Hex Editor (Hex View), etc.
I think you got the wrong idea lol, when i mention cyan/red area is literally mean you couldn’t edit it with other method like MMTool, UEFITool, Hex Editor the result after mod will always brick (sorry my english is still piece of crap lmao XD).
anyway here , i already update only for 50654 there’s limitation, 1 of the microcode should be deleted (doesn’t have more space for newer microcode 5056 and 5057).
Note: non-uefi_fix.bin only used it if you can recover with external programmer, it’s my first time encounter Non-UEFI Data without header (last time i fix it when the body size exceed to Volume free space).
