Contribute
Register

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

Loloflatsix said:
I updated the firmware to NVM18
When I reboot with SSDT-RP21 with the same DROM as on NVM18 :
- The Thunderbolt is OK on IOReg
- The USB C network can be hot pluggable and disconnected: the network is functional through it
- No more than before on AppleThunderboltHAL tree

Code: 
                               "ThunderboltDROM",
                                Buffer (0x77)
                                {
                                    /* 0000 */  0x88, 0x00, 0x11, 0x11, 0x11, 0x11, 0x11, 0x00,
                                    /* 0008 */  0x00, 0x1F, 0x40, 0xDF, 0x8A, 0x01, 0x58, 0x00,
                                    /* 0010 */  0x01, 0x00, 0x0D, 0x00, 0x01, 0x00, 0x08, 0x81,
                                    /* 0018 */  0x80, 0x02, 0x80, 0x00, 0x00, 0x00, 0x08, 0x82,
                                    /* 0020 */  0x90, 0x01, 0x80, 0x00, 0x00, 0x00, 0x08, 0x83,
                                    /* 0028 */  0x80, 0x04, 0x80, 0x01, 0x00, 0x00, 0x08, 0x84,
                                    /* 0030 */  0x90, 0x03, 0x80, 0x01, 0x00, 0x00, 0x02, 0x85,
                                    /* 0038 */  0x0B, 0x86, 0x20, 0x01, 0x00, 0x64, 0x00, 0x00,
                                    /* 0040 */  0x00, 0x00, 0x00, 0x03, 0x87, 0x80, 0x05, 0x88,
                                    /* 0048 */  0x50, 0x40, 0x00, 0x05, 0x89, 0x50, 0x00, 0x00,
                                    /* 0050 */  0x05, 0x8A, 0x50, 0x00, 0x00, 0x05, 0x8B, 0x50,
                                    /* 0058 */  0x40, 0x00, 0x0B, 0x01, 0x47, 0x49, 0x47, 0x41,
                                    /* 0060 */  0x42, 0x59, 0x54, 0x45, 0x00, 0x12, 0x02, 0x47,
                                    /* 0068 */  0x43, 0x2D, 0x41, 0x4C, 0x50, 0x49, 0x4E, 0x45,
                                    /* 0070 */  0x20, 0x52, 0x49, 0x44, 0x47, 0x45, 0x00    
                                },

View attachment 456214
Click to expand...

Confirms for me native updater won't work. Looking forward to the other method.

...as is. When you open the updater it creates a file name tbfirmware.bin. I'm willing to bet we could change the value before hitting OK to proceed. We can do this later but I wanted the info to exist somewhere before moving on.
 
Last edited:
NorthAmTransAm said:
Confirms for me native updater won't work. Looking forward to the other method.

...as is. When you open the updater it creates a file name tbfirmware.bin. I'm willing to bet we could change the value before hitting OK to proceed. We can do this later but I wanted the info to exist somewhere before moving on.
Click to expand...
Firmware Updaters may not work if even a single byte is modified. The actual firmware file from a vendor contains a lengthy digital signature near the end at offset 0x61000, in a section labeled SEC DGST that seems to mean SECurity DiGital SignaTure. Here is an example:

Capture d’écran 2020-03-21 à 19.11.01.png
 
Bobby22 said:
I will try to remove the Drivers (which I think I did not install at all) but the Fence-T919 is natively supported by windows without any driver so is that really working ?
1) I am experiencing some Bluetooth signal Loss in windows but not in Mac which may be related to some incompatibilities of the dual Wifi/BT card isn' it ? (All Intel drivers are up to date).
Is that worth it removing physically the Intel Wifi/BT card and only using the Fenvi on windows and Mac ?
Any others solutions on Windows to remove or cancel the Fenvi card ?
Click to expand...
Let's take a look at the Windows Hardware Manager window. Please open Hardware Manager, expand the section(s) related to WiFi, Network, and Bluetooth and post a screenshot. I would like to see if there are any devices with a "?" or other exception next to them.
2) Moreover, I am using a Bluetooth KeyBoard and a BlueTooth mouse. Is there any way to activate Bluetooth during the Boot to be able to select the Boot destination on BootClover Manager ?
Click to expand...
As far as I know, only Apple Magic Mouse and Apple Magic Keyboard will work in BIOS and Clover -- and only when using a Broadcom-based card such as Fenvi FV-T919.
 
CaseySJ said:
Firmware Updaters may not work if even a single byte is modified. The actual firmware file from a vendor contains a lengthy digital signature near the end at offset 0x61000, in a section labeled SEC DGST that seems to mean SECurity DiGital SignaTure. Here is an example:

View attachment 456218
Click to expand...
And suddenly so much more makes sense to me
 
CaseySJ said:
Firmware Updaters may not work if even a single byte is modified. The actual firmware file from a vendor contains a lengthy digital signature near the end at offset 0x61000, in a section labeled SEC DGST that seems to mean SECurity DiGital SignaTure. Here is an example:

View attachment 456218
Click to expand...
@CaseySJ,
Right ! But we could try an old Firmware Updater that is not deal with a SIG.
I think about Gigabyte FlashTBT (FIRMWARE GIGABYTE THUNDERBOLT FW UPDATE TOOL GA-Z170X-GAMING G1 B16.0201.1 for exemple) and other from 2016-2017 year.
 
In case it would be useful I attach here the ASUS-TBEX3-NVM18 extracted with the CH341A programmer :

Edit :
 

Attachments

  • ASUS-TBEX3-NVM18-V2.bin.zip
    287.5 KB · Views: 93
Last edited:
Elias64Fr said:
@CaseySJ,
Right ! But we could try an old Firmware Updater that is not deal with a SIG.
I think about Gigabyte FlashTBT (FIRMWARE GIGABYTE THUNDERBOLT FW UPDATE TOOL GA-Z170X-GAMING G1 B16.0201.1 for exemple) and other from 2016-2017 year.
Click to expand...
Or something like this tool :
  1. rename your BIN firmware file to chip2_Fw.dat
  2. Replace the current chip2_Fw.dat file already on directory (null file)
  3. Edit TbtFwUpdate.exe.config to adapt it to your controller :
    • <Chip srcFwName="chip2_Fw.dat" vid="8086" pid="15EB" targetNVMVersion="33" />
  4. and hope that is work under Windows :shifty:
Be CAREFULY by always having an external Programmer ready to flash back to Original firmware ;)
 

Attachments

  • TbtFwUpdate_1.0.0.15_release.zip
    259.1 KB · Views: 115
Elias64Fr said:
Or something like this tool :
  1. rename your BIN firmware file to chip2_Fw.dat
  2. Replace the current chip2_Fw.dat file already on directory (null file)
  3. Edit TbtFwUpdate.exe.config to adapt it to your controller :
    • <Chip srcFwName="chip2_Fw.dat" vid="8086" pid="15EB" targetNVMVersion="33" />
  4. and hope that is work under Windows :shifty:
Click to expand...

I'd like to confirm that the file tbfirmware.bin that is created once the application is opened is based off of chip1_fw.dat (or chip2) OR it's made to OEM.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top