Contribute
Register

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

Please... Help adapting IOReg Path in Tbolt3 aml.

/PC03@0/AppleACPIPCI/BR3B@1/IOPP/SL0A@0/IOPP/pci-bridge@0/IOPP/pci8086,15eb@0
 

Attachments

  • SSDT-TBOLT3-X299_J.aml
    2.2 KB · Views: 66
  • Mac Pro_Juantrix.ioreg
    13.5 MB · Views: 72
Hi @CaseySJ, I'm having an issue when trying to log in to the App Store.
View attachment 466722

I'm attaching IOReg dump and my EFI folder with serials removed. Would you mind please taking a look?
Hello @nifranza,

This is usually due to an iCloud or AppleID issue. Some suggestions:
  • Check if your macOS serial number is not already in use. Click here and copy/paste your serial number from About this Mac. If you see a red ERROR message then you're GOOD.
  • Sign out of App Store. From the Store menu, select Sign Out. Then sign in. If that does not help, then sign out of App Store and iCloud. Reboot. Sign back in.
 
Last edited:
@CaseySJ
Not getting expected output still..
Will look into the breadboard like @iRamon (great post btw, I didn't see it as I'm just looking at the flashing tuts.)
but just trying again as I feel I'm pretty close to getting it to read. Tried to run 3 separate tests and save the .bin IMG_1259.jpg

EDIT: Oh hang on.. I may have done it already looking back at the tutorial..
Should I Flash?? Aghh.. here we go
 
OK. Here are my aml and extensions folder pix as well as the EFI.
View attachment 466736
View attachment 466737
Please try this:
  • Temporarily remove the Radeon Boost patches:
    • CLOVER/ACPI/patched/SSDT-RX 5700 XT-Version 1.0.aml
    • CLOVER/kexts/Other/dAGPM.kext
  • Delete the duplicate kext:
    • CLOVER/kexts/10.14/SmallTreeIntel82576.kext
  • Use the attached config.plist. Backup the original file.
 

Attachments

  • config.plist
    10.7 KB · Views: 87
@CaseySJ Completely off-topic: do you know, whether the Synology E10G18-T1 works (OOB, if possible) with OS X? I've read that it has the AQC107 chip, just not sure, if it sports the AQC107"s", or the normal one. If it works oob, it could be flashed with the Apple FW
 
Hi,
I probably asked this in the past, but can't find it anymore.
Is there a way to create a SSDT for PCI Information injection instead of using the Clover -> Devices -> Arbitrary injection ?
Sure, we can use SSDT to inject device properties. Probably the best way to learn this is by example. Have a look at KGP's X299 repository on GitHub (click here).

Most (not all) of the files below are used only to inject device properties. We can use Hackintool --> PCIe to determine the IOReg path of various devices in our system.

Screen Shot 2020-05-03 at 4.29.44 AM.png
 
@CaseySJ
Not getting expected output still..
Will look into the breadboard like @iRamon (great post btw, I didn't see it as I'm just looking at the flashing tuts.)
but just trying again as I feel I'm pretty close to getting it to read. Tried to run 3 separate tests and save the .binView attachment 466780

EDIT: Oh hang on.. I may have done it already looking back at the tutorial..
Should I Flash?? Aghh.. here we go
Seems like you are already reading the chip successfully @ziggenpuss!

Verify that checksums of test1.bin, test2.bin and test3.bin are identical:
Code:
shasum test*.bin

If they are identical, your clip is attached properly are you are succesfully and consistently reading the chip correctly.
KEEP these testx.bin files, they are your backup of the original firmware!

When three checksums match, then move on to the write command to flash the patched firmware.bin.

If flashing is successfull (message with VERIFIED), make sure to do three read commands again (use different filenames, so you don't overwrite your original backup files!!). Verify that the checksums are identical again using shasum *.bin command. If the checksums of those three reads match with the checksum of the patched firmware .bin file, celebrate! Because then you have succesfully patched your Thunderbolt firmware.

I've listed the commands and output of my succesfull flash in the spoiler below. Hope that makes it easier to follow the flashing procedure and recognize desired outputs.
Rich (BB code):
$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r test-connection-ATX-NoPSU-VCC.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadOriginalROM-01-ATX-PSU-NoVCC-BrightWhite.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadOriginalROM-02-ATX-PSU-NoVCC-BrightWhite.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadOriginalROM-03-ATX-PSU-NoVCC-BrightWhite.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ shasum *.bin
8a07244b1f6ea08643eb144e5dd520e50babef7e  ReadOriginalROM-01-ATX-PSU-NoVCC-BrightWhite.bin
8a07244b1f6ea08643eb144e5dd520e50babef7e  ReadOriginalROM-02-ATX-PSU-NoVCC-BrightWhite.bin
8a07244b1f6ea08643eb144e5dd520e50babef7e  ReadOriginalROM-03-ATX-PSU-NoVCC-BrightWhite.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  tb-firmware-original.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  tb-firmware-patched.bin
8a07244b1f6ea08643eb144e5dd520e50babef7e  test-connection-ATX-NoPSU-VCC.bin
NOTE: all ReadOriginalROM checksums above are identical

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w tb-firmware-patched.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadPatchedROM-01.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadPatchedROM-02.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -r ReadPatchedROM-03.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

$ shasum ReadPatched*.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  ReadPatchedROM-01.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  ReadPatchedROM-02.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  ReadPatchedROM-03.bin
NOTE: all ReadPatchedROM checksums above are identical, and match checksum of tb-firmware-patched.bin

Good luck, hope you will be succesfull!
 
Last edited:
Please... Help adapting IOReg Path in Tbolt3 aml.

/PC03@0/AppleACPIPCI/BR3B@1/IOPP/SL0A@0/IOPP/pci-bridge@0/IOPP/pci8086,15eb@0
Please copy both of the attached SSDTs to CLOVER/ACPI/patched. Reboot and check IORegistry again.
 

Attachments

  • SSDT-TBOLT3-X299_J.aml
    2.2 KB · Views: 68
  • SSDT-DTPG.aml
    100 bytes · Views: 73
@CaseySJ
Not getting expected output still..
Will look into the breadboard like @iRamon (great post btw, I didn't see it as I'm just looking at the flashing tuts.)
but just trying again as I feel I'm pretty close to getting it to read. Tried to run 3 separate tests and save the .binView attachment 466780

EDIT: Oh hang on.. I may have done it already looking back at the tutorial..
Should I Flash?? Aghh.. here we go
Seems like you are already reading the chip successfully @ziggenpuss!

Verify that checksums of test1.bin, test2.bin and test3.bin are identical:
Code:
shasum test*.bin

If they are identical, your clip is attached properly are you are succesfully and consistently reading the chip correctly.
KEEP these testx.bin files, they are your backup of the original firmware!

When three checksums match, then move on to the write command to flash the patched firmware.bin.

If flashing is successfull (message with VERIFIED), make sure to do three read commands again (use different filenames, so you don't overwrite your original backup files!!). Verify that the checksums are identical again using shasum command. If the checksums match, celebrate! Because then you have succesfully patched your Thunderbolt firmware.

Good luck, hope you will be succesfull!
@ziggenpuss,

Yes you're ready to flash! But please verify checksums as mentioned by @iRamon and also type strings test1.bin. If you see a bunch of strings -- even if they look meaningless -- then you're good to go.
 
Could you please tell me how to clean up so many ICONS after I complete the installation according to the steps? Also, I installed win10 before I installed the MAC, but I can't get in now. Is there anything wrong?
 

Attachments

  • 79174E39-C62B-4175-BC28-FFEC8635A8B2.jpeg
    79174E39-C62B-4175-BC28-FFEC8635A8B2.jpeg
    348.4 KB · Views: 62
Back
Top