Contribute
Register

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

Hi @CaseySJ, I'm Setting up a new config with i9-10850K. Unfortunately, the stock of the Z490's is low. It was impossible to buy a Vvision D. So I opted for a cheap ASRock Z490 Phantom Gaming 4. (Bought new for 90USD CA).

I wanted to ask you two things.
1. Since the mobo has the TB header, should I connect it ,or do I leave the jumper? (Let's talk about the flashed GC Titan Ridge V2.)

2. Does it make sense to buy the Z590 Vision D as soon as it is available while keeping the CPU, or which mobo would you recommend? I need an ATX because I have 2 PCIe cards in addition to the GPU.

The vision D (or other mobos with TB) would be ideal to use the GC Titan Ridge on hack and the integrated ports on Windows.


Thanks For your reply.
Hello @basett1,

Some answers and comments:
  • Most Thunderbolt devices do not require Thunderbolt Bus, so regular unflashed card should be used first. If it works well enough then there's no need to go further (i.e. no need to flash the firmware).
  • But if you do require Thunderbolt Bus, then please be aware of the various issues that arise (i.e. it may be necessary to warm-boot the system for Thunderbolt Bus to activate fully; sleep/wake issues may arise; etc.).
  • Because your motherboard has a THB_C Thunderbolt header, try connecting the GC-Titan Ridge to it. If the card works (i.e. Thunderbolt devices can connect and function) then keep the cable connected. But if there are some issues, you can also disconnect the cable from Thunderbolt header and use a jumper wire to connect the Top and Middle pins of the vertical J1 header on the back of the GC-Titan Ridge. That forces the card to power on.
  • Does it make sense to buy Z590 Vision D? Not necessarily. If your ASRock Z490 Phantom Gaming 4 works well with GC-Titan Ridge, then there's no reason to change. In general, however, the flashed on-board Thunderbolt controller on Z490 Vision D will be more reliable (but not perfect) than a flashed add-in-card.
 
If we had the DEBUG build of the driver/kext, we would be able to attach a debugger. However, maybe some experienced Macintosh programmers can chime in and let us know whether a release-mode binary can be attached to the Xcode debugger or any other debugger.
It's depending on release-mode settings during app export but in 99% of time debug info is disabled for release builds (better speed perf and less memory usage and all).
Reverse engineering may be the solution to add some break points to print some info in console.app for example.
 
Hi @CaseySJ,I build a new Hackintosh.

I have installed an MSI Thunderbolt M3 Thunderbolt 3 card (chip is JHL6540) on my MSI-B460m-MORTAR. Using the SSDT on your post on the latest BigSur system cannot activate the Thunderbolt bus. Here are the firmware of the card and DSDT on my board.

If you are free, please help me patch this firmware or SSDT.

thanks For your reply

View attachment 512220
Hello @Mace,

Attached ZIP contains three files:
  1. MSI-TB3-ALPINE-CASEYSJ-MOD1.bin
  2. SSDT-TB3-MSI-ALPINE.aml
  3. SSDT-DTPG.aml
File 1 is a modified Thunderbolt firmware. Please backup the original and flash this file. Also copy Files 2 and 3 into the OpenCore ACPI folder and add references to ACPI section of config.plist. Disable any previous Thunderbolt SSDT.

Then shutdown the system and flip power switch on PSU to OFF for 10 seconds and restart (COLD Start). Log into macOS and check IORegistryExplorer. Do you see Thunderbolt Bus? We can also check System Information --> Thunderbolt.
 

Attachments

  • MSI-ALPINE-RIDGE-TB3.zip
    295.7 KB · Views: 47
It's depending on release-mode settings during app export but in 99% of time debug info is disabled for release builds (better speed perf and less memory usage and all).
Reverse engineering may be the solution to add some break points to print some info in console.app for example.
Can break points be added to Release Mode binaries? Or will Xcode throw an error message saying that the binary is "hardened"?
 
Can break points be added to Release Mode binaries? Or will Xcode throw an error message saying that the binary is "hardened"?
Most of "hacked" "cracked" apps are made in this way soo ...

We need to "convert" binaries into the original written language, probably C/Objectif-C
modify It as we need,
compile it
This isn't easy task but here is a starting point
 
Every time I do reset NVRAM command at opencore picker, my serial number changes, and a new computer appears in my devices.
Is that normal? Or is there something wrong with my settings?
 

Attachments

  • Screen Shot 2021-03-14 at 2.41.16 PM.png
    Screen Shot 2021-03-14 at 2.41.16 PM.png
    8.2 KB · Views: 32
Every time I do reset NVRAM command at opencore picker, my serial number changes, and a new computer appears in my devices.
Is that normal? Or is there something wrong with my settings?
It is not normal
What you should do right now is logout from iCloud, and delete theses iMacs from iCloud lists with another Apple device.
 
It is not normal
What you should do right now is logout from iCloud, and delete theses iMacs from iCloud lists with another Apple device.
I do so every time it creates a new one.
Do you know what could possibly be wrong?
What files should I share to investigate this issue?
 
I do so every time it creates a new one.
Do you know what could possibly be wrong?
What files should I share to investigate this issue?
not heard of resetting nvram creates a new serial number?
 
I do so every time it creates a new one.
Do you know what could possibly be wrong?
What files should I share to investigate this issue?
Download HackinDROM.app
1. Take screenshot of this window
Screen Shot 2021-03-14 at 19.56.26.png


2. Mount your EFI partition,
Screen Shot 2021-03-14 at 19.57.01.png


Click on Archive icon to create an archive of your EFI partition into your Desktop.
Screen Shot 2021-03-14 at 19.57.17.png
Screen Shot 2021-03-14 at 19.59.21.png



Post (1) Screenshot and the archive (2)
 

Attachments

  • HackinDROM.zip
    2.9 MB · Views: 44
Back
Top