ASUS Prime Z790-P (NON-WIFI) Bios dump and questions

[kinojk2]

Hi, Thanks for all you do here.

I have attached my 16MB dump.

EDIT2: All hardware working fine, I think I just need to update my linux booatloader and all gucci
EDIT:
I can get into bios now! I reflashed as instructed elsewhere. With a minimal POST (just 1 stick of ram , GPU, CPU, no drives) I have loaded into BIOS. I am about to reinstall my other hardware components now.

The clips are such a pain to use, soldering would be a great skill to have.

Thanks for the advice in other threads!

To answer my own question, I didn't need to reassemble the 8MB dump with 16, the 16MB dump was enough to get the HMI and add to the .cap with FD33.




--------------------------------------



Firstly, do I need to get windows keys from the 16MB? Or is it only the DMI? I have the DMI info from my 16MB dump, I am wondering if I even need to read the 8MB bios chip, which contains ME, as my DMI is on the 16MB. In other thread's instructions given for the WIFI version I didn't see any mention of windows keys. Do they come with the images I can create from the Asus .cap file? Therefore, in the mean time before I get the T48. Can I prepare the 16MB and 8Mb files I will write using a hexeditor. I have used FD44 tool to write the .cap as a bin and it has the right size, I can splice it using a hex editor, add my DMI to the 16MB. And that's it?

I could not read the 8MB, I bought a CH341A-Black and belatedly discovered the 5v fault, so I am now waiting on a T48 Mini-Pro. The clip was difficult for me when reading the 16MB, but I wonder if the 5V vault prevented me from succesfully reading the 8MB today. I understand these chips are quite rugged but I am not trying my luck and am waiting for the T48 before I try to write to these chips. I thought it was worth investing in this T48 instead of replace my motherboard on the off chance that the 8MB chip was damaged in trying to read with the CH-black

Thanks.


Explaining how I needed a bios reflash:

I was foolishly setting up Secure Boot for Linux (Dual booting with windows from separate drive) using custom keys. It seems I should have just used Shimlock... The guide I found explained how to create keys and sign my bootloader, even appending windows certs, but not how to actually go about finalising secure boot enabling. Long story short, I put my custom keys in the BIOS which replaced the factory keys, but then went into secure boot windows mode instead of leaving it in custom. This has bricked my computer.

To my knowledge, the secure boot keys exist on the 16MB bios chip, and yet they are invalid because they are keys+windows cert and my bios is expecting the windows keys. I might not have this all correct but this is my working theory.