[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[CaseySJ]

Right you are! Will fix all the DROM micro-guides soon.

 

[Inqnuam]

Right you are! Will fix all the DROM micro-guides soon.

We can also add a link here like this, isn't better?

 

[CaseySJ]

We can also add a link here like this, isn't better?
View attachment 483541

Agreed.

Update: A link was there already, but to an earlier post that introduced HackinDROM. It has been replaced by a direct link.

 

[clichequiche]

Why dont you use F9g #22,669?

As a first timer, "install that [beta] version at your own risk" scared me off. Also the TweakTown link was a dead end/removed post. Thought it'd be best to use official firmware

EDIT: I see your link leads to a working version

 

[Inqnuam]

As a first timer, "install that [beta] version at your own risk" scared me off. Also the TweakTown link was a dead end/removed post. Thought it'd be best to use official firmware

EDIT: I see your link leads to a working version

F9g is pretty stable, most of us using this version

 

[CaseySJ]

Hi all! Trying to unlock MSR 0xE2 and, for me, Reply 2 is from a Setup variable that is 7 bytes long, not 9. Is this a big deal? BIOS v F9b.

This is okay; no problem if it says 7 bytes instead of 9. The change will still be made to Reply 1.

 

[clichequiche]

This is okay; no problem if it says 7 bytes instead of 9. The change will still be made to Reply 1.

F9g is pretty stable, most of us using this version

Thanks all. Will try out F9g as it seems the easier route

 

[wormz30]

ok so onto board number two (I have two builds i'm working on that are almost identical...) but board number two gives me completely different checksums... how do i fix that?

 

[CaseySJ]

ok so onto board number two (I have two builds i'm working on that are almost identical...) but board number two gives me completely different checksums... how do i fix that?

Nothing to fix because checksums will be different between boards. We have to ensure that checksums are the same for each board when the firmware is read 3 times in a row. We should also run “strings” command on the files to make sure that they contain some readable text.

 

[wormz30]

Nothing to fix because checksums will be different between boards. We have to ensure that checksums are the same for each board when the firmware is read 3 times in a row. We should also run “strings” command on the files to make sure that they contain some readable text.

I understand. What I meant was on this second board, I read the chip 3 times and the checksums showed 3 different values. What do I need to do to fix this?