Zitat von Lost_N_BIOS im Beitrag #430

---

@kevindd992002 - I updated CPU microcode for you, sounded like you wanted to but couldn't.

---

Zitat von Fernando im Beitrag #431

---

As far as I understood SoniX's last post the upcoming UBU version will contain the announced updated/corrected drvver.exe tool.

---

@SoniX , it looks like 1.75.0.1 has display bugs for the RAW GOP part:

https://imgur.com/z8vOqFa

Also, why does my BIOS have two RAW GOP VBT's listed there?

I also don't understand why you consider this BIOS a "mobile" BIOS when in reality this is for the ASRock J5005-ITX board which is desktop ITX board.

@Lost_N_BIOS

This BIOS I'm editing is the one you gave me with the updated ucode. In addition, I used UBU to update the GOP to 13.0.1018 (GLK) and updated the Network UNDI/Boot Agent. I should be able to flash this BIOS to my board without any issues, right? The BIOS update procedure for this board is kinda weird so I wanted to confirm with your first: https://www.asrock.com/support/BIOSIG.asp?cat=Windows10

running the latest ubu i found there are new entries :
1 - Disk Controller
EFI IRST RAID for SATA - 13.1.0.2126
OROM IRST RAID for SATA - 13.1.0.2126
2 - Video OnBoard
EFI GOP Driver IvyBridge - 3.0.1030
EFI GOP Driver SandyBridge - 2.0.1024
RAW GOP VBT SNB/IVB-MOBILE - 165 <----this one
RAW GOP VBT SNB/IVB-MOBILE - 165 <----and this one.
OROM VBIOS SNB-IVB - 2171
3 - Network
OROM Intel Boot Agent GE - 1.5.62
EFI Realtek UNDI - 2.049
OROM Realtek Boot Agent GE - 2.66


What are those RAW GOP VBT SNB/IVB-Mobile items (this is a desktop platform/mobo) ?? And could/should they be updated aswell ?? I have updated everything else to the latest without problems.

@kevindd992002 - I don't know, I can only vouch for the BIOS I made you, if you want me to check your BIOS after UBU mod to give my opinion you'll have to upload it for me to look at.
That update procedure just disables the ME and probably also at same time unlocks the FD so you can flash all regions at once, if you want you can unlock the FD in the BIOS you flash in, then you wont need to use that jumper anymore.
FD write in stock BIOS is NO, and ME Read/Write is NO, that's why you use this jumper, to unlock those temporarily and flash entire BIOS via FPT

@Lost_N_BIOS:
Here's the link to the BIOS I've modded: https://www.dropbox.com/s/c54m395l6xukxsl/GLKITX1.40?dl=0
How do I unlock the FD in this BIOS too? And unlocking that won't be dangerous at all?

@Fernando

That BIOS was modded by the UBU tool and I'm asking if it's safe to flash it on the ITX board that I have. How is that not on-topic? That is totally related to the UBU tool because it was used to mod the BIOS.

As for the topic title, I just made that up because it wouldn't let me post my reply without a title. So please ignore that, that's a very small issue here.

Any intervention in BIOS is a risk.
I give only tools that simplify some replacement procedures.
The partial solution is up to the user.

I totally understand that. But having others with experience take a look at the modded BIOS makes it more worry-free, at the very least.

How do i extract those RAW GOP VBT files from bios so that i can have a look at them myself ?


Nvermind, i got them seperat by running Ubu again. I wasn't thinking clearly.
Compared both raw gop vbt's , and they have 4 differences already. This is interesting.

Zitat von Fernando im Beitrag #445

---

@kevindd992002:

Zitat von kevindd992002 im Beitrag #442

---

That BIOS was modded by the UBU tool and I'm asking if it's safe to flash it on the ITX board that I have. How is that not on-topic? That is totally related to the UBU tool because it was used to mod the BIOS.

---

If you have serious doubts, that the UBU tool has executed a certain task with a certain BIOS correctly, you should ask SoniX to check it (the UBU modded BIOS should be attached or linked). Everything else may make other UBU users insecure regarding the reliability of the UBU tool and is in my eyes unfair to SoniX.

Zitat von kevindd992002 im Beitrag #440

---

@Lost_N_BIOS:
How do I unlock the FD in this BIOS too? And unlocking that won't be dangerous at all?

---

Please explain the relationship between your question and the topic of this thread.

Zitat von kevindd992002 im Beitrag #442

---

As for the topic title, I just made that up because it wouldn't let me post my reply without a title.

---

This doesn't happen, if you simply press the "Reply" button, when you want to refer to a certain post. If you change the title, all later directly replied posts will automaticly get the title you had chosen (unless the author edits the title manually to the source one).

---

@Fernando - I don't know, I just reply, unsure how the title says "Reply" maybe a bug?
I know I didn't waste my time to change it, but if it bugs you please feel free to edit it to whatever you want, I don't mind at all and I'm sure kevindd992002 doesn't either

@kevindd992002 - No, FD unlock is not dangerous if done correctly, please visit the Intel ME section of the forum to see how to unlock FD, there is a sticky.
BIOS Looks OK as far as I can tell, no immediately noticeable issue - But, I don't see anything updated vs stock BIOS, except the microcode (GOP/PXE = same/same stock), I think you uploaded wrong file at post 440?