[Guide] Transfer of specific Intel OROM VBIOS and GOP VBT settings by using Intel BMP tool

Hi Sonix ,
Can you give me a SkyLake 1020.bsf file? Thanks , I only have 1020.dat file.

@geekv

Unfortunately I do not have BSF for SKL versions 1009-1021
Sorry.

Thanks , I give up

VBIOS_and_BSF.7z where I can download it

@mofakkhar - At end of first post

Iā€™m working on eliminating PWM flicker for Xiaomi 13.3" 2017.
Iā€™ve succeed with BIOS legacy mode, where there is no more flickering.
However Iā€™m failing with UEFI native mode: after I edit GOP VBT, machine refuses to boot, so Iā€™m forced to revert back these changes.

Here are the steps:
1. Open firmware in UEFITool
2. Search for ā€œvbt skylakeā€ non-unicode text
3. For unknown reason, there are FOUR matches with LegacyVideoRom, and SIX matches with IntelGopVbt, while there are should be only ONE for each (checked with ROM for 2016 model Iā€™ve found on XDA)
4. For the above reason, Iā€™ve dumped all four sections (Raw section - Extract bodyā€¦)
5. Iā€™ve downloaded IBMP and scripts from SoniX
6. Iā€™ve looked at sections via hex editor: 3 of them have 1051 OROM version and 1 has 1050 OROM version. So iā€™ve used appropriate scripts from SoniX pack to edit all four of them, then adjusted PWM frequency for all modes in each file, and saved them
7. Replaced all four sections in UEFITool (Raw section - Replace bodyā€¦)
8. Flashed the ROM and everything is fine, there is no more screen flicker but only in BIOS mode. To make it work in UEFI mode Iā€™ve proceed with IntelGopVbt stuff
ā€¦
9. Iā€™ve repeated actions 1-7, but working with six IntelGopVbt sections instead of four LegacyVideoRom sections. Here is the first thing I donā€™t understand. What script should I use to modify them? Iā€™ve used 1051 script for all them, despite they say 1001 OROM version. Flashed the ROM and boom there is no display and looks like machine is not even POSTed. So Iā€™ve reverted back to previous ROM.

Please help!

original.zip (4.69 MB)

@SoniX - do you have any updates or script files to work with ValleyView orom/GOP? I really donā€™t need update probably but that would be OK too, main concern is a way to check and change if possible the default output fallback setting to only LVDS never VGA/other.
This maybe only possible in BIOS settings, not sure, but wanted to dig through the vBIOS too so I could be sure.
If you need BIOS to check out let me know and I will link, thanks! Working EFI GOP Driver ValleyView - 7.1.1005 / OROM VBIOS ValleyView - 1019

@Lost_N_BIOS

For ValleyView, almost nothing.It was also noted that versions 7.0, 7.1 and 7.2 are often not compatible. Therefore, I would not recommend doing similar updates with this GPU. No sense anyway.

Bummer, but thanks for the info @SoniX - I eventually found the old 3652 BSF/Dat file that you guys posted and discussed here a while back, and it opened OK with that, but I cannot be sure all settings are shown properly due to itā€™s not correct files for that really.
I didnā€™t need to update the file, only possibly change some of the defaulted settings. Can that be done with just the vBIOS itself, no updates just edit settings?


Figured out. Here are the new steps and modified bios (minimum brightness changed from 15 to 0 and PWM is changed from 220hz to 2000hz):
1. Opened firmware in UEFITool v0.25.1
2. Figured out that relevant sections are only DDE5BDB6-07F3-4CAD-A40C-52BAC366717D for LegacyVideoRom and CEDBA4B5-2184-496E-8764-D4BFB8FD0617 for IntelGopVbt
3. Used 1050 OROM script to edit both sections in IBMP
4. Adjusted only default mode (mode 3)

pwm.zip (4.76 MB)

.

Updated Collection Intel OROM in "VBIOS_and_BSF.7z":
- added OROM VBIOS+BSF
ā€“ Skylake/Kabylake/Coffeelake v1062

Hi, thanks for the guide.
Could you please let me know which Dev ID to choose? I thought sandy bridge would be 102, but I donā€™t have that option.
using a Asus P8Z68-V-PRO BIOS 3603

bios: https://drive.google.com/open?id=1mUsPqeā€¦lIM9qBtNhn1P7M6

gpuz capture.gif

gpuz capture.gif

gpuz capture.gif




dev ID capture.PNG





gpuz capture.gif




EDIT:
Issue resolved. I didnā€™t realise you could scroll to find more device IDs in MMTOOL . After realising I found my OROM VBIOS 8086,102
my OROM VBIOS was 2124 using the BSF-script file 2132 worked. VBIOS successfully updated, thanks.

Does anyone have BSF-script/dat for SNB-IVB 2126 - if not, is there a known one thatā€™s compatible to use, or all must be done one by one manually to update to 2158?
Never mind, I guess I am supposed to use 2132, correct?

@SoniX

Skylake/Kabylake/Coffeelake v1063

8086-0406 Intel Skylake-Kabylake VBIOS 9.0.1063.zip (39.1 KB)

@Pacman

Thank you.
Alas, WBT size has changed. I donā€™t have a suitable BSF.

Can anyone explain what is the purpose of the OROM VBIOS and BSF-script package? I donā€™t see any reference to this in post #1 other than the link to download it.

@kyriacos - see steps #3-9 of the guide, itā€™s used all through the process

@Lost_N_BIOS
In step 1) I have DevID: 1969,e091 8086,2822 and 8086,402.
Assuming that 8086,402 is the correct one, if I extract vbios.dat and open it in a hex editor, I get "BD 00" for Version VBT, "1038" for Version OROM and "5D 11" for Size VBT. Are these all the correct values?

@kyriacos - Yes, thatā€™s correct based on what I see in the included docx file - you can update to 1044