[Success] b1's "Mac Mini Killer" with macOS Mojave: i7-8700 | Gigabyte Z370N | RX560 | 16GB RAM

[Rajkhand]

hi,

I am on the F13 BIOS on the Z370WIFI. I am not able to get the BIOS to identify the UEFI on the USB disk. I have used the EFI from the post #873 above.

I understand on page 88 there is some reference to some mysery Bootx64.efi which is no longer available for download (links are dead). I thought this was some version of https://github.com/datasone/grub-mod-setup_var, so I took the pain of recompiling the EFI from scratch, but in vain (still wont boot) to this EFI.

Can someone post a link to a working Bootx64.efi which enables the shell which enables the user to make the changes suggested in #505,

setup_var 0x5A4 0x0
setup_var 0x507 0x1

I am trying to install OC latest with BigSur...

I think you are doing something wrong as the EFI for OC 0.6.4 works perfectly with BIOS 13. In OC you don’t require the special bootx64.efi

 

[ghat]

I think you are doing something wrong as the EFI for OC 0.6.4 works perfectly with BIOS 13. In OC you don’t require the special bootx64.efi

Well... Yeah looks like it...

I did not create the folder EFI inside the EFI partition ...
problem was I was labeling the EFI partition as EFI so my system was mounting it as EFI on linux...

anyways after almost a day debugging I am finally booting the MacOS Install..

Update: after I start the install the progress bar goes to about 20% and the system keeps resetting itself...

Any hints, I am using the EFI from the former post #873, updated the MAC on the Config.plist file. I also installed it on a new USB stick, and still have the same problem...

I am using '001-86606 - 11.1 macOS Big Sur' and the bios settings from #777

I have tried this on '001-68446 - 10.15.7 macOS Catalina' as well but same thing, however the installer goes to like 45% or so before resetting itself...

My take is there is something fishy in the BIOS settings...
WOuld appreciate if someone with a successful X370N-WIFI+BigSur can reconfirm, what settings they are using after doing "load optimized defaults"

G

 

[Rajkhand]

Well... Yeah looks like it...

I did not create the folder EFI inside the EFI partition ...
problem was I was labeling the EFI partition as EFI so my system was mounting it as EFI on linux...

anyways after almost a day debugging I am finally booting the MacOS Install..

Update: after I start the install the progress bar goes to about 20% and the system keeps resetting itself...

Any hints, I am using the EFI from the former post #873, updated the MAC on the Config.plist file. I also installed it on a new USB stick, and still have the same problem...

I am using '001-86606 - 11.1 macOS Big Sur' and the bios settings from #777

I have tried this on '001-68446 - 10.15.7 macOS Catalina' as well but same thing, however the installer goes to like 45% or so before resetting itself...

My take is there is something fishy in the BIOS settings...
WOuld appreciate if someone with a successful X370N-WIFI+BigSur can reconfirm, what settings they are using after doing "load optimized defaults"

G

This is the best guide you can follow to solve your problems

Open Core Install Guide

 

[ghat]

This is the best guide you can follow to solve your problems

Open Core Install Guide

hi

I finally got Bigsur to install... Yeah....
But there are still some problems...
It did not install the bootloader to the EFI !,
I have a botched grub-efi Linux/Elementary OS on the same disk on a different partition...

I have fixed this by erasing(reformating) the EFI partition on the main disk, and cloning the Opencore from the USB down to this partition... Now BigSur loads by default with no issue.. I still have the "debug mode" Opencore, which I need to switchback to the release mode..

I also want to see how I can have Opencore load the ElementaryOS from the 3rd partition.

Also the wifi wont work...

I had this card, which worked for Mojave and before....

06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
Subsystem: Lenovo BCM4352 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at f7c00000 (64-bit, non-prefetchable) [size=32K]
Memory at f7a00000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 48-xx-yy-zz-aa-bb-cc-dd
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Kernel driver in use: wl
Kernel modules: bcma, wl

I believe this is a
"Broadcom BCM94352Z 802.11ac WIFI Card For Lenovo Y50-80 Y50-70 Touch 04X6020" which I purchased off ebay a couple of years ago.

 

[Rajkhand]

hi

I finally got Bigsur to install... Yeah....
But there are still some problems...
It did not install the bootloader to the EFI !,
I have a botched grub-efi Linux/Elementary OS on the same disk on a different partition...


Also the wifi wont work...

I had this card, which worked for Mojave and before....

send your EFI folder I have the same card and its working

 

[ghat]

Well got the Wireless to work right, I did not have the AirportBrcmFix earlier, the key here is to disable the other driver in the plist using MaxKernel, as mentioned in the READMe for the Kext for Big Sur.

Next,
1. I want to make sure all the USB ports in the front and back work
2. If possible get all of the Display-Port, HDMI0 and HDMI1 work
3. Get my Linux partition to boot in openCore/UEFI

Do folks (@Rajkhand) have all of these working ?

G

 

[Rajkhand]

Well got the Wireless to work right, I did not have the AirportBrcmFix earlier, the key here is to disable the other driver in the plist using MaxKernel, as mentioned in the READMe for the Kext for Big Sur.

Next,
1. I want to make sure all the USB ports in the front and back work
2. If possible get all of the Display-Port, HDMI0 and HDMI1 work
3. Get my Linux partition to boot in openCore/UEFI

Do folks (@Rajkhand) have all of these working ?

G

Good that you solved it because the problem was that with AirportBrcmFixup ver. 2.1.1 as told in the guide you could put brcmfx-driver=2 in your boot argument and it will work with Lilu 1.4.9, but NOT with ver. 2.1.2 and Lilu 1.5.0!!! It will mess up your boot process and Wifi & BT will not work.
It took me 2 day of trying out different things and I never assumed that the boot argument is not working in the latest 1.5.0 version to cut the story short the correct way is to use the following code

<key>Add</key>
        <array>
            <dict>
                <key>BundlePath</key>
                <string>Lilu.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/Lilu</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirportBrcmFixup</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string>19.9.9</string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

First entry should be lilu and then the rest and remove the boot arg. It solved all the problems and made it future proof.
Just search for creating USBports.kext using hackintool for USB
for HDMI to work use whatevergreen.kext and in your config.plist under DeviceProperties ->Add
PciRoot(0x0)/Pci(0x2,0x0) Class Dictionary under that
AAPL,ig-platform-id class Data value 0300913E
Your SystemProductName should be iMac19,1
For your 3rd point I have no solution but there has to be one if you search.

 

[ghat]

hi,
I have the USBPorts.kext, with the current setup the 4 port-set on the back, the USB-Type-C (3.0) and 2 ports on the front seem to work fine.. The 2-port-set which are next to the ethernet port are not being recognized... any hints/config/links etc to get this working ???

I have verified that both the HDMI ports work individually, and together... I have not been able to test the DisplayPort terminal yet as I don't have my cable handy...

Bluetooth is also now working..

 

[Rajkhand]

hi,
I have the USBPorts.kext, with the current setup the 4 port-set on the back, the USB-Type-C (3.0) and 2 ports on the front seem to work fine.. The 2-port-set which are next to the ethernet port are not being recognized... any hints/config/links etc to get this working ???

I have verified that both the HDMI ports work individually, and together... I have not been able to test the DisplayPort terminal yet as I don't have my cable handy...

Bluetooth is also now working..

You should have maximum of 15 ports defined. USB 3 ports count as 2 so you have already 6x2=12 ports defined. You should define hs10 defined as internal for BT to work so will make 13 ports you can define one more USB 3 port now to make it to 15 not 2. As per my memory the ports next to the Ethernet ports are port no 3&4 so define any one of them as USB 3 port.

 

[j0s3ph]

Good news guys! I've managed to boot with F12 bios. It is easier than you think. Here is a simple step by step guide.

1. Make a boot USB flash drive with your current EFI folder.
2. Download bootx64.efi and copy it to EFI/Boot/.
This is some kind of alternative bootloader that starts with the command line. Here we will modify hidden BIOS settings.

3. Update BIOS to F12 (only F12!)
4. Reboot and hold F12 to boot from your USB Flash drive. Now you should see this command line.
5. Now enter

setup_var 0x5A4 0x0

setup_var 0x507 0x1

Reboot from your primary drive. You Hack should boot normally. But don't forget to set up your BIOS settings.

Looks like we will need to do this every time after trigger «Reset to default settings» option in BIOS.

P.S. If you are interested in the details:

0x5A4 is CFG Lock option in BIOS
0x507 is System Time and Alarm Source option

This codes are not static and can be changed in future updates. You can use this guide to find this code for future versions of BIOS.

Bring this post back from the dead, anyone have the downloadable bootx64.efi command line file? My MB reset itself when I swapped cases and I need to downgrade to F12 and rerun the CFG Lock command so I can boot back into macOS.

Note, I dug through some of the posts after the post above, and found this link, I tested it and it doesn't seem to work, not sure if this is the exact one or a newer version.

EDIT: Never mind, found it in post #879