The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

[tahitianstud]

Hello, could someone with perfectly working Bluetooth with this setup post a screenshot of their Bluetooth System report ?

I am particularly interested in their firmware version

Thanks in advance

 

[Leesureone]

Similar , but mine auto reboots. HDD,SSD,NVMe, same.

If I rollback to 2411(this is a day older than 2401) from 2401 via AFUDOS, is it expected to still show 2401 as the current version?

I thought I successfully rolled back to 2411, but the BIOS shows 2401 still. Trying 0401 now.

Update: 0401 shows 2401 after too. Hopefully I’m doing something wrong.

There is a process described in this thread by Modmike on how to downgrade this boards bios, it’s not for the faint of heart, but version 2401 works so it’s really a non issue.

The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

@ModMike thank you so much for this great guide! I’ve decided to get the ATX version (ASUS Z390-F), since I already have a BCM94360CD PCIe card and I'm also able to install a Thunderbolt PCIe card in case I will need it. "For the moment“ I’ve took an i3-8100 because it will probably be...

www.tonymacx86.com

 

[kelmers]

There is a process described in this thread by Modmike on how to downgrade this boards bios, it’s not for the faint of heart, but version 2401 works so it’s really a non issue.

The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

@ModMike thank you so much for this great guide! I’ve decided to get the ATX version (ASUS Z390-F), since I already have a BCM94360CD PCIe card and I'm also able to install a Thunderbolt PCIe card in case I will need it. "For the moment“ I’ve took an i3-8100 because it will probably be...

www.tonymacx86.com

I'm running out of ideas.

My heart was not faint , so I attempted to tackle that few times yesterday and a few earlier this past weekend. MSDOS boot key, add the converted .cap file that only contains the body, saved as bios.rom, placed onto root of DOS key, with .bat. Boot with CSM on, let the DOS key do its thing, erase , flash , verify etc. Verify after power cycle, 2401 is still the current version. Switch CSM off, and then unsuccessfully try to install again.

At this point, I begin to question my memory selection, which I know is compatible with the board, but perhaps I overlooked it’s compatibility with OSX.
Ballistix sport 2666MHz 16-18-18-38 1.2

side note: When I try to boot the installer created with Unibeast(rather than the unibeast built installer with ModMike's IGPU EFI folder), I can't boot all the way to the installer. I haven't made any changes other than manually add -v during boot.

Backtraces for the storage driver seen at boot are attached, and the message seen before the unexpected reboot happens

 

[tahitianstud]

I did some research regarding to custom SSDT for USBInjectAll.kext. I succesfully created SSDT-UIAC.aml. This is what my SSDT-UIAC.dsl looks like. You can use it if you want as a template. But always check for validity in IORegistryExplorer.app.

// SSDT-UIAC.dsl

DefinitionBlock ("", "SSDT", 2, "hack", "_UIAC", 0)
{
    Device(UIAC)
    {
        Name(_HID, "UIA00000")

        // override XHC configuration to have only 9 ports
        Name(RMCF, Package()
        {
            "8086_a36d", Package()
            {
                "port-count", Buffer() { 26, 0, 0, 0 },
                "ports", Package()
                {
                    "HS03", Package() // HS USB3.1 rear bottom
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 3, 0, 0, 0 },
                    },
                    "HS04", Package() // HS USB3.1 rear top
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 4, 0, 0, 0 },
                    },
                    "HS05", Package() // HS USB2 rear bottom
                    {
                        "UsbConnector", 0,
                        "port", Buffer() { 5, 0, 0, 0 },
                    },
                    "HS06", Package() // HS USB2 rear top
                    {
                        "UsbConnector", 0,
                        "port", Buffer() { 6, 0, 0, 0 },
                    },
                    "HS07", Package() // HS USB3 rear bottom
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 7, 0, 0, 0 },
                    },
                    "HS08", Package() // HS USB3 rear top
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 8, 0, 0, 0 },
                    },
                    "HS09", Package() // HS USB3 front top
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 9, 0, 0, 0 },
                    },
                    "HS10", Package() // HS USB3 front bottom
                    {
                        "UsbConnector", 3,
                        "port", Buffer() { 10, 0, 0, 0 },
                    },
                    "HS14", Package() // bluetooth
                    {
                        "UsbConnector", 255,
                        "port", Buffer() { 14, 0, 0, 0 },
                    }
                }
            }
        })
    }
}

//EOF

After creating Remove the port limit patches in your .plist and keep USBInjectAll.kext.

Hello,

Just tried it and same result: the Bluetooth refuses to pair anything...

Oh well, I guess I'll just have to do without since everything else works perfectly

 

[Hackinjosh]

bluetooth also refuses to pair anything for me. it's the exact same problem described by dozens of users in this thread - bluetooth icon is there but does nothing. can't pair, can't find devices.

i bought the exact same hardware as listed in the OP except for the power supply and case. installed the DW1560 i got directly from dell. confirmed it's completely functional in windows. i read all 145 pages and spent 4 days trying everything suggested but sadly nothing works. i've reinstalled osx 15 times. looks like there's no definitive solution. there are so many conflicting answers. one guy even said he just deleted all the BRCM files and it started working. unfrotunately i am not that lucky. i tried all of it. all combinations of files in all possible locations. i guess i'll also have to do without it.

sadly, the quest for an "everything works" hackintosh solution continues.

 

[antiserum420]

bluetooth also refuses to pair anything for me. it's the exact same problem described by dozens of users in this thread - bluetooth icon is there but does nothing. can't pair, can't find devices.

i bought the exact same hardware as listed in the OP except for the power supply and case. installed the DW1560 i got directly from dell. confirmed it's completely functional in windows. i read all 145 pages and spent 4 days trying everything suggested but sadly nothing works. i've reinstalled osx 15 times. looks like there's no definitive solution. there are so many conflicting answers. one guy even said he just deleted all the BRCM files and it started working. unfrotunately i am not that lucky. i tried all of it. all combinations of files in all possible locations. i guess i'll also have to do without it.

sadly, the quest for an "everything works" hackintosh solution continues.

have you tried installing the required kexts in Library/Extensions with kextbeast:

- AirportBrcmFixup.kext
- BrcmPatchRAM2.kext
- BrcmFirmwareRepo.kext
- BrcmBluetoothInjector.kext

Have you also verified with command "kextstat" BrcmPatchRAM2.kext is loaded properly. The reason I could not pair with any device is because the required kexts where not loaded.

 

[joetgt1]

Maybe it's a stupid question, but, is this the system idle power consumption, or just the VGA ?
is that normal ? ty

 

[Leesureone]

Hello, could someone with perfectly working Bluetooth with this setup post a screenshot of their Bluetooth System report ?

I am particularly interested in their firmware version

Thanks in advance

Here's my Bluetooth System Report bud.

 

[Leesureone]

I'm running out of ideas.

My heart was not faint , so I attempted to tackle that few times yesterday and a few earlier this past weekend. MSDOS boot key, add the converted .cap file that only contains the body, saved as bios.rom, placed onto root of DOS key, with .bat. Boot with CSM on, let the DOS key do its thing, erase , flash , verify etc. Verify after power cycle, 2401 is still the current version. Switch CSM off, and then unsuccessfully try to install again.

At this point, I begin to question my memory selection, which I know is compatible with the board, but perhaps I overlooked it’s compatibility with OSX.
Ballistix sport 2666MHz 16-18-18-38 1.2

side note: When I try to boot the installer created with Unibeast(rather than the unibeast built installer with ModMike's IGPU EFI folder), I can't boot all the way to the installer. I haven't made any changes other than manually add -v during boot.

Backtraces for the storage driver seen at boot are attached, and the message seen before the unexpected reboot happens

I'm running out of ideas but I don't think it is your memory. The first screen shot looks like there is a problem with USB related to the Bios setting for USB Configuration > XHCI Hand Off > Enabled. Looks like it isn't enabled and causing that issue.

Beyond that I am totally guessing, try deleting VBoxHFS-64.efi from your USB Boot drive from EFI\Clover\drivers64UEFI folder. I don't use it. Like I said guessing now.

Beyond that google "Ola Hackintosh" and see the first hit. Can't really say anymore except its an alternate method

 

[tahitianstud]

Here's my Bluetooth System Report bud.

Thank you !

This is interesting and I was suspecting that maybe my hardware was different than the one that works but it seems that everything is the same EXCEPT "HCI revision" (mine was 0x1000, yours 0x1673) AND of course firmware version (mine shows c4096, which apparently means it is not getting patched correctly, yours shows c5747)

Can anybody with knowledge about HCI revision comment on the importance of this difference ?