• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

How to extract VBIOS from a bios update bin file - AMD HD 6770M - HP Pavilion dv6-6196ss

Status
Not open for further replies.

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#1
Hello. I wonder if some of you can help me to get my VBIOS extracted.

I've tried GPU-Z (Windows), DPCIManager(macOS) and using the PCI sysfs interface to dump the video bios rom (Ubuntu). It seems the ROM doesn't want to be read.

It's an AMD Radeon HD 6770M, device id 1002:6740, from an HP Pavilion dv6-6196ss laptop.

I've tried a different approach, to get VBIOS from a Bios update package (called sp55068.exe) using Universal Extractor and Radeon Bios Editor (Windows). The problem is that "Universal Extractor" reads only the first 64 KB and my VBIOS is 128KB long.

I attach here the BIOS (bin file extracted from sp55068.exe) that contains the VBIOS, the three VBIOS 64KB files I could get and some images showing the errors I'm facing: https://www116.zippyshare.com/v/SxYDuJL1/file.html

Thank you very much.
 
Joined
Oct 22, 2014
Messages
6,528 (4.38/day)
Likes
3,883
Location
Sunshine Coast
System Name Black Box
Processor Intel Xeon E5-2680 10c/20t 2.8GHz @ 3.0GHz
Motherboard Asrock X79 Extreme 11
Cooling Coolermaster 240 RGB A.I.O.
Memory G. Skill 16Gb (4x4Gb) 2133Mhz
Video Card(s) Nvidia GTX 710
Storage Sandisk X 400 256Gb
Display(s) AOC 22" Freesync 1m.s. 75Hz
Case Corsair 450D High Air Flow.
Audio Device(s) No need.
Power Supply FSP Aurum 650W
Software W10 Home Premium 64 bit
#2
Why do you want to extract it?
Your mGPU is most likely part of the system BIOS.
64kb sounds right for the file size as the rest should be empty space.
 

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#3
Why do you want to extract it?
Your mGPU is most likely part of the system BIOS.
64kb sounds right for the file size as the rest should be empty space.
I need it to get the connectors info so I can inject it to Clover to get MacOS High Sierra working on it. I need to patch what's called "AMD framebuffer" https://www.tonymacx86.com/threads/...ebuffers-for-high-sierra-using-clover.235409/

When I try to radeon_bios_decode the 64 KB file I don't get the connectors info, which has to be in the other 64 KB that are not read.
What GPU-Z says is "BiOS reading not supported on this device."

Thank you for helping.
 
Joined
Oct 22, 2014
Messages
6,528 (4.38/day)
Likes
3,883
Location
Sunshine Coast
System Name Black Box
Processor Intel Xeon E5-2680 10c/20t 2.8GHz @ 3.0GHz
Motherboard Asrock X79 Extreme 11
Cooling Coolermaster 240 RGB A.I.O.
Memory G. Skill 16Gb (4x4Gb) 2133Mhz
Video Card(s) Nvidia GTX 710
Storage Sandisk X 400 256Gb
Display(s) AOC 22" Freesync 1m.s. 75Hz
Case Corsair 450D High Air Flow.
Audio Device(s) No need.
Power Supply FSP Aurum 650W
Software W10 Home Premium 64 bit
#4
@eidairaman1 @MrGenius , and any others that have bios modifying experience.
your experienced input might be valuable here.
 
Joined
Jul 7, 2015
Messages
14 (0.01/day)
Likes
6
Location
County Tyrone
System Name Shinobi XL
Processor 3770K
Motherboard MSI Z77A-GD55
Cooling Arctic cooling freezer pro
Memory 16GB (4x4) Samsung EcoGreen 1600mhz
Video Card(s) MSI R9 280X 3GB
Storage Sammy 850 Pro 512GB
Display(s) Hanns.G HL272HPB
Case Bitfenix Shinobi XL
Audio Device(s) Asus D2x / Sound Blaster Z
Power Supply Hiper Type R 880w
Mouse MS optical 200
Keyboard Logitech G110
Software win 8.1 pro
#5
You could try phoenixtool/AWARDtool or UEFItool at least for old bios i know phoenix tool was able to extract the bios to a folder to allow for injection/extraction/modification i wont link to it, please google it - it requires manufacturer downloaded bios exe in most case it will extract from the executable file.
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
#6
Last I recalled, 7Zip or WinRAR were able to extract Executables down further, I dont know now...

By the way what is the reason why you are trying to update the GPU bios for? Since it is HP you can always contact their support team.
 

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#7
Last I recalled, 7Zip or WinRAR were able teso extract Executables down further, I dont know now...

By the way what is the reason why you are trying to update the GPU bios for? Since it is HP you can always contact their support team.
Hello, friends, for all your help, I'm very grateful.

Yes, with 7ZIP you can unzip the exe and get the bin file. That's what I did. Now I realized I extracted the bin using Phoenixtool (Award tool says my BIOS is not an Award).
The thing is that Phoenixtool extracted a lot of ROMs and it cut my 128KB ROM to 64 KB, so the other part has to be somewhere with another name.
I'm trying not to upgrade the VBIOS, but trying to have it to know some info, as which connectors it uses and how they are named, the order of them, and their memory position/offset. This is because I use the computer as a hackintosh, and I'd like to use the AMD GPU, and not only the HD3000 IGPU.

The process I'm trying to do is explained here https://www.tonymacx86.com/threads/...ebuffers-for-high-sierra-using-clover.235409/ and I need the VBIOS ROM to be able to do it.

I suppose that with an hexadecimal editor it's possible to see where the VBIOS begins (it first bit), then count 128 KB, cut them out, and create the ROM, but that's a suposition, because I'm not an hexa-editor expert. But maybe it's an easier way, another program that can get the 128 KB VBIOS in one step, so I don't need to learn how to hexa-edit, but I don't know, I'm very new on this.

Thank you all again,

Note: UEFITool says "UEFI Volumes not found".

I've tried to open the 01658.bin file and one of the 64 KB undecrypted files ...1194.ROM but i cannot find any 1194.ROM string in .bin
I suppose .bin is encrypted or whatever.
Screen Shot 2018-06-23 at 23.55.21.png
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
#8
Hello, friends, for all your help, I'm very grateful.

Yes, with 7ZIP you can unzip the exe and get the bin file. That's what I did. Now I realized I extracted the bin using Phoenixtool (Award tool says my BIOS is not an Award).
The thing is that Phoenixtool extracted a lot of ROMs and it cut my 128KB ROM to 64 KB, so the other part has to be somewhere with another name.
I'm trying not to upgrade the VBIOS, but trying to have it to know some info, as which connectors it uses and how they are named, the order of them, and their memory position/offset. This is because I use the computer as a hackintosh, and I'd like to use the AMD GPU, and not only the HD3000 IGPU.

The process I'm trying to do is explained here https://www.tonymacx86.com/threads/...ebuffers-for-high-sierra-using-clover.235409/ and I need the VBIOS ROM to be able to do it.

I suppose that with an hexadecimal editor it's possible to see where the VBIOS begins (it first bit), then count 128 KB, cut them out, and create the ROM, but that's a suposition, because I'm not an hexa-editor expert. But maybe it's an easier way, another program that can get the 128 KB VBIOS in one step, so I don't need to learn how to hexa-edit, but I don't know, I'm very new on this.

Thank you all again,

Note: UEFITool says "UEFI Volumes not found".

I've tried to open the 01658.bin file and one of the 64 KB undecrypted files ...1194.ROM but i cannot find any 1194.ROM string in .bin
I suppose .bin is encrypted or whatever.
View attachment 102936
Do you know how to change file extensions?
 
Joined
Feb 2, 2015
Messages
2,053 (1.48/day)
Likes
1,696
Location
On The Highway To Hell \m/
#9
I'm pretty well lost on this one. I can show you where the LVDS_Info table is in each of those ROMs. Which would relate to a "Laptop Monitor"(according to the link you provided). Other than that I have no clue. What I can tell you is those ROMs appear to be the correct size. As in they appear to contain the entire Legacy ROM image. And from looking at the GPU-Z screenshot your card is not UEFI compatible. If it were then they would need to be ~2x the size they are. To account for the size of the EFI ROM. Which is typically close to the same size as the Legacy ROM. Anyway, I think you're wrong to assume the vBIOS ROM(s? why are there even more than 1?) should be 128 KB. There is an HD 6770M non-UEFI example in the database that is 62 KB.

Here's LVDS_Info tables. Whether that helps you, or not, I wouldn't even know.
LVDS Info tables.PNG
 
Last edited:

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
#10
I'm pretty well lost on this one. I can show you where the LVDS_Info table is in each of those ROMs. Which would relate to a "Laptop Monitor"(according to the link you provided). Other than that I have no clue. What I can tell you is those ROMs appear to be the correct size. As in they appear to contain the entire Legacy ROM image. And from looking at the GPU-Z screenshot your card is not UEFI compatible. If it were then they would need to be ~2x the size they are. To account for the size of the EFI ROM. Which is typically close to the same size as the Legacy ROM. Anyway, I think you're wrong to assume the vBIOS ROM(s? why are there even more than 1?) should be 128 KB. There is an HD 6770M non-UEFI example in the database that is 62 KB.

Here's LVDS_Info tables. Whether that helps you, or not, I wouldn't even know.
View attachment 102947
He is using a mobo bios extractor tool which will not work for a video bios correctly and also if I recall correctly that half a vbios is filled with zeros anyway at least from what gpu-z does.

I think he needs to just change the extension from a .bin to a .rom
 
Joined
Feb 2, 2015
Messages
2,053 (1.48/day)
Likes
1,696
Location
On The Highway To Hell \m/
#11
The 01658.bin file he's talking about is the entire 4.44MB BIOS for his laptop. He extracted 3 vBIOS ROMs from it. One 63KB for Seymour XT, one 63KB for Whistler XT, and one 62KB for Whistler XT. Which, so far as I can tell, are all complete. If there was padding to make the file size 128KB it got deleted when he extracted them, because it's useless(and even if it wasn't padding, which I highly doubt, it was most likely still useless for his purposes). He thinks there might be more to the vBIOS ROMs because whatever stupid tool he's trying to use to get the framebuffer info won't work with them. I don't know why it wouldn't. What I am pretty(99.9%) sure about is, whatever he's looking for is in the ROMs he has. There's a small(.1%) chance I'm wrong though. IOW the tool is retarded(or PEBCAK).
 
Last edited:

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
#12
The 01658.bin file he's talking about is the entire 4.44MB BIOS for his laptop. He extracted 3 vBIOS ROMs from it. One 63KB for Seymour XT, one 63KB for Whistler XT, and one 62KB for Whistler XT. Which, so far as I can tell, are all complete. If there was padding to make the file size 128KB it got deleted when he extracted them, because it's useless(and even if it wasn't padding, which I highly doubt, it was most likely still useless for his purposes). He thinks there might be more to the vBIOS ROMs because whatever stupid tool he's trying to use to get the framebuffer info won't work with them. I don't know why it wouldn't. What I am pretty(99.9%) sure about is, whatever he's looking for is in the ROMs he has. There's a small(.1%) chance I'm wrong though. IOW the tool is retarded(or PEBCAK).
Hey man read what that file fixes.

https://support.hp.com/us-en/driver...es/5082212/model/5147025/swItemId/ob-100034-2
 

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#13
Do you know how to change file extensions?
Yes, I know how to do it.

Thank you.
The 01658.bin file he's talking about is the entire 4.44MB BIOS for his laptop. He extracted 3 vBIOS ROMs from it. One 63KB for Seymour XT, one 63KB for Whistler XT, and one 62KB for Whistler XT. Which, so far as I can tell, are all complete. If there was padding to make the file size 128KB it got deleted when he extracted them, because it's useless(and even if it wasn't padding, which I highly doubt, it was most likely still useless for his purposes). He thinks there might be more to the vBIOS ROMs because whatever stupid tool he's trying to use to get the framebuffer info won't work with them. I don't know why it wouldn't. What I am pretty(99.9%) sure about is, whatever he's looking for is in the ROMs he has. There's a small(.1%) chance I'm wrong though. IOW the tool is retarded(or PEBCAK).
Thank you. I thought vbios was larger than 64kb because of the message from rbe radeon bios editor. And because the radeon bios decode I'm using didn't find any connectors info. But my computer is for sure not uefi.
And I don't understand why there are 3 vBIOS ROMs.
And the stupid tool I'm using:) seems to work to everybody excepts me, dunno why. It's all very weird to me.
It should give me something like
Code:
ATOM BIOS Rom:
    SubsystemVendorID: 0x1545 SubsystemID: 0x7970
    IOBaseAddress: 0x0000
    Filename: SV2A01.001
    BIOS Bootup Message: TAHITI XT PCIE 3G/384B GDDR5 DLDVI-I/HDMI/2XMINI-DP 925E/1375M
PCI ID: 1002:6798

Connector at index 0
   Type [@offset 43422]: DisplayPort (10)
   Encoder [@offset 43426]: INTERNAL_UNIPHY2 (0x21)
   i2cid [@offset 43540]: 0x90, OSX senseid: 0x1
   HotPlugID: 5
Connector at index 1
   Type [@offset 43432]: DisplayPort (10)
   Encoder [@offset 43436]: INTERNAL_UNIPHY2 (0x21)
   i2cid [@offset 43567]: 0x91, OSX senseid: 0x2
   HotPlugID: 4
Connector at index 2
   Type [@offset 43442]: HDMI-A (11)
   Encoder [@offset 43446]: INTERNAL_UNIPHY1 (0x20)
   i2cid [@offset 43594]: 0x93, OSX senseid: 0x4
   HotPlugID: 1
Connector at index 3
   Type [@offset 43452]: DVI-I (2)
   Encoder [@offset 43456]: INTERNAL_UNIPHY (0x1e)
   i2cid [@offset 43631]: 0x95, OSX senseid: 0x6
   HotPlugID: 3
Connector at index 4
   Type [@offset 43462]: DVI-I (2)
   Encoder [@offset 43466]: INTERNAL_KLDSCP_DAC1 (0x15)
   i2cid [@offset 43631]: 0x95, OSX senseid: 0x6
   HotPlugID: 3
But it just give me a part, it finishes in the line

PCI ID: 1002:6798
 
Last edited:

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
#16
Thank you. Yes. Gpu-z says my gpu doesn't support reading. With ubuntu I get an input/output error, too. I think all of this is highly inusual, isn't it? It's crazy!
Ok, this video tells you to disable the device in device manager then get it
 

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#17
Ok, this video tells you to disable the device in device manager then get it
Aah! Sorry, I'm on the smartphone. I'll do that when at home and tell you what I get. Thank you veeery much:)

I'm pretty well lost on this one. I can show you where the LVDS_Info table is in each of those ROMs. Which would relate to a "Laptop Monitor"(according to the link you provided). Other than that I have no clue. What I can tell you is those ROMs appear to be the correct size. As in they appear to contain the entire Legacy ROM image. And from looking at the GPU-Z screenshot your card is not UEFI compatible. If it were then they would need to be ~2x the size they are. To account for the size of the EFI ROM. Which is typically close to the same size as the Legacy ROM. Anyway, I think you're wrong to assume the vBIOS ROM(s? why are there even more than 1?) should be 128 KB. There is an HD 6770M non-UEFI example in the database that is 62 KB.

Here's LVDS_Info tables. Whether that helps you, or not, I wouldn't even know.
View attachment 102947
Thank you for these tables, I'll appreciate the time you needed to do that, in this very moment I don't know what to do with that, but i'ts valuable for sure.

Ok, this video tells you to disable the device in device manager then get it
Hello, I did it as you stated, with Radeon disabled and I get the same message, GPU-Z cannot read the vBIOS.

What's more, I've used the Dell.HD6770M.1024.100929.rom (downloadable in techpowerup.com) and everything works as supposed:
Code:
MacBook-Air:vbios-macos-tools Apple$ ./radeon_bios_decode < Dell.HD6770M.1024.100929.rom
ATOM BIOS Rom:
    SubsystemVendorID: 0x1028 SubsystemID: 0x04a3
    IOBaseAddress: 0x0000
    Filename: BR038688.001
    BIOS Bootup Message:
Whistler GL XT C29202 MXM GDDR5 100e/300m 0.9V                          

PCI ID: 1002:6740
Connector at index 0
    Type [@offset 44928]: LVDS (7)
    Encoder [@offset 44932]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 45038]: 0x94, OSX senseid: 0x5
Connector at index 1
    Type [@offset 44938]: DisplayPort (10)
    Encoder [@offset 44942]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 45061]: 0x90, OSX senseid: 0x1
    HotPlugID: 1
Connector at index 2
    Type [@offset 44948]: DisplayPort (10)
    Encoder [@offset 44952]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 45088]: 0x91, OSX senseid: 0x2
    HotPlugID: 2
Connector at index 3
    Type [@offset 44958]: DisplayPort (10)
    Encoder [@offset 44962]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 45115]: 0x92, OSX senseid: 0x3
    HotPlugID: 3
Connector at index 4
    Type [@offset 44968]: VGA (1)
    Encoder [@offset 44972]: INTERNAL_KLDSCP_DAC1 (0x15)
    i2cid [@offset 45142]: 0x97, OSX senseid: 0x8
MacBook-Air:vbios-macos-tools Apple$ ./redsock_bios_decoder < Dell.HD6770M.1024.100929.rom
BR038688.001:

Whistler GL XT C29202 MXM GDDR5 100e/300m 0.9V                          

Subsystem Vendor ID: 1028
       Subsystem ID: 4a3
Object Header Structure Size: 332
Connector Object Table Offset: 48
Router Object Table Offset: 0
Encoder Object Table Offset: f3
Display Path Table Offset: 12
Connector Object Id [14] which is [LVDS]
    encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [5] which is [VGA]
    encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
but with my extracted with PhoenixTool vBIOS I just get this:

MacBook-Air:vbios-macos-tools Apple$ ./radeon_bios_decode < 9FD8F494-6E3F-4A04-A2B0-8DF7E9E01BF6_1194-ampliada.ROM
ATOM BIOS Rom:
SubsystemVendorID: 0x103c SubsystemID: 0x1656
IOBaseAddress: 0x0000
Filename: BR41116.001
BIOS Bootup Message:
HP/Flex Grant Whistler XT GDDR5 128Mx16 1GB

PCI ID: 1002:6740
MacBook-Air:vbios-macos-tools Apple$ ./redsock_bios_decoder < 9FD8F494-6E3F-4A04-A2B0-8DF7E9E01BF6_1194-ampliada.ROM
BR41116.001 :

HP/Flex Grant Whistler XT GDDR5 128Mx16 1GB

Subsystem Vendor ID: 103c
Subsystem ID: 1656
Object Header Structure Size: 30
Connector Object Table Offset: 16
Router Object Table Offset: 0
Encoder Object Table Offset: 1a
Display Path Table Offset: 12
I think I will tell you all "thank you", and I will abandon this, because it seems the tools to extract this GPU doesn't exist. It's so strange, I cannot find anybody complaining about this, everybody seems to be able to extract the vBIOS without troubles.

Following this guide "Using the PCI sysfs interface to dump the Video BIOS ROM" http://smackerelofopinion.blogspot.com/2011/07/using-pci-sysfs-interface-to-dump-video.html
I can see ubuntu thinks the video rom is 131072 bytes, that is, 128 KB, although it gives an input/output error and cannot be read. So weird!

EDIT: Improvements!

I could decrypt the 01658.bin thanks to this tutorial: https://vinafix.com/threads/hp-bios-decrypt-tool.27109/

Now I can open it with UEFITool! But I don't know how to find the vBIOS with this tool. Any ideas?
Screen Shot 2018-06-25 at 13.00.18.png

I attach the decrypted bin.

EDIT 2: I found the supposed vBIOS sections. Yes, they are what we had: 64 KB, extracting them as raw, I get the same.
Code:
MacBook-Air:vbios-macos-tools Apple$ ./radeon_bios_decode < d.raw
ATOM BIOS Rom:
    SubsystemVendorID: 0x103c SubsystemID: 0x1656
    IOBaseAddress: 0x0000
    Filename: BR040957.001
    BIOS Bootup Message:
HP/Flex Grant Seymour XT GDDR5 128Mx16 1GB                                 

PCI ID: 1002:6760
 

Attachments

Last edited:

oscarstv

New Member
Joined
Jun 23, 2018
Messages
8 (0.05/day)
Likes
0
#18
Aah! Sorry, I'm on the smartphone. I'll do that when at home and tell you what I get. Thank you veeery much:)


Thank you for these tables, I'll appreciate the time you needed to do that, in this very moment I don't know what to do with that, but i'ts valuable for sure.


Hello, I did it as you stated, with Radeon disabled and I get the same message, GPU-Z cannot read the vBIOS.

What's more, I've used the Dell.HD6770M.1024.100929.rom (downloadable in techpowerup.com) and everything works as supposed:
Code:
MacBook-Air:vbios-macos-tools Apple$ ./radeon_bios_decode < Dell.HD6770M.1024.100929.rom
ATOM BIOS Rom:
    SubsystemVendorID: 0x1028 SubsystemID: 0x04a3
    IOBaseAddress: 0x0000
    Filename: BR038688.001
    BIOS Bootup Message:
Whistler GL XT C29202 MXM GDDR5 100e/300m 0.9V                         

PCI ID: 1002:6740
Connector at index 0
    Type [@offset 44928]: LVDS (7)
    Encoder [@offset 44932]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 45038]: 0x94, OSX senseid: 0x5
Connector at index 1
    Type [@offset 44938]: DisplayPort (10)
    Encoder [@offset 44942]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 45061]: 0x90, OSX senseid: 0x1
    HotPlugID: 1
Connector at index 2
    Type [@offset 44948]: DisplayPort (10)
    Encoder [@offset 44952]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 45088]: 0x91, OSX senseid: 0x2
    HotPlugID: 2
Connector at index 3
    Type [@offset 44958]: DisplayPort (10)
    Encoder [@offset 44962]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 45115]: 0x92, OSX senseid: 0x3
    HotPlugID: 3
Connector at index 4
    Type [@offset 44968]: VGA (1)
    Encoder [@offset 44972]: INTERNAL_KLDSCP_DAC1 (0x15)
    i2cid [@offset 45142]: 0x97, OSX senseid: 0x8
MacBook-Air:vbios-macos-tools Apple$ ./redsock_bios_decoder < Dell.HD6770M.1024.100929.rom
BR038688.001:

Whistler GL XT C29202 MXM GDDR5 100e/300m 0.9V                         

Subsystem Vendor ID: 1028
       Subsystem ID: 4a3
Object Header Structure Size: 332
Connector Object Table Offset: 48
Router Object Table Offset: 0
Encoder Object Table Offset: f3
Display Path Table Offset: 12
Connector Object Id [14] which is [LVDS]
    encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true
Connector Object Id [19] which is [DISPLAY_PORT]
    encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [5] which is [VGA]
    encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
but with my extracted with PhoenixTool vBIOS I just get this:


I think I will tell you all "thank you", and I will abandon this, because it seems the tools to extract this GPU doesn't exist. It's so strange, I cannot find anybody complaining about this, everybody seems to be able to extract the vBIOS without troubles.

Following this guide "Using the PCI sysfs interface to dump the Video BIOS ROM" http://smackerelofopinion.blogspot.com/2011/07/using-pci-sysfs-interface-to-dump-video.html
I can see ubuntu thinks the video rom is 131072 bytes, that is, 128 KB, although it gives an input/output error and cannot be read. So weird!

EDIT: Improvements!

I could decrypt the 01658.bin thanks to this tutorial: https://vinafix.com/threads/hp-bios-decrypt-tool.27109/

Now I can open it with UEFITool! But I don't know how to find the vBIOS with this tool. Any ideas?
View attachment 103025

I attach the decrypted bin.

EDIT 2: I found the supposed vBIOS sections. Yes, they are what we had: 64 KB, extracting them as raw, I get the same.
Code:
MacBook-Air:vbios-macos-tools Apple$ ./radeon_bios_decode < d.raw
ATOM BIOS Rom:
    SubsystemVendorID: 0x103c SubsystemID: 0x1656
    IOBaseAddress: 0x0000
    Filename: BR040957.001
    BIOS Bootup Message:
HP/Flex Grant Seymour XT GDDR5 128Mx16 1GB                                

PCI ID: 1002:6760
Guys, please, close the thread, it's very weird, there are people saying that's something HP does like this just to avoid to do what I'm trying.
Thank you for all your help, I've learned a lot thanks to you, and now I can hexa-edit BIOS files :)
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
23,529 (5.65/day)
Likes
7,551
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
Status
Not open for further replies.
Top