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

[b166ar]

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.

 

[inarush]

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 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 Flashdrive. Now you should see this command line.
5. Now enter

0x5A4 0x0

0x507 0x1

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

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.

@b166ar do you have to type any command before the hex codes, such as setup_var? Or you just need to type the codes?

 

[b166ar]

@b166ar do you have to type any command before the hex codes, such as setup_var? Or you just need to type the codes?

Oops, sorry. There is a command. I just edited my previous post.

 

[xmark]

Here is a simple step by step guide.

Great. Appreciate the simplification.

The boot64x.efi binary you link is the same as @themaxx32000 's which in turn is the same as the one jacyl4 links to in their blog (and is 6 years old). Wonder where it came from. Maybe from the clover dev people?

 

[b166ar]

Great. Appreciate the simplification.

The boot64x.efi binary you link is the same as @themaxx32000 's which in turn is the same as the one jacyl4 links to in their blog (and is 6 years old). Wonder where it came from. Maybe from the clover dev people?

View attachment 397008

I think it was made by @acidanthera, author of Lilu and WhateverGreen.

I found it here — https://github.com/acidanthera/AptioFixPkg

 

[xmark]

@acidanthera, author of Lilu and WhateverGreen

Yes it's the same binary. Looks good. I'll try the upgrade.

Thanks for finding.

EDIT: have updated to F12. Only comment I have is you get an error message (GUID does not match expected GUID), but can see the new values. I do recommend to double check the variables have correctly been set in the Grub shell (command setup_var 0x507 without an argument will show the current setting, same for setup_var 0x5A4). I somehow didn't set them first time and had to anxiously repeat after a hanging reboot.

Thanks heaps to @b166ar & @themaxx32000.

 

[endrus]

Yes it's the same binary. Looks good. I'll try the upgrade.

Thanks for finding.

EDIT: have updated to F12. Only comment I have is you get an error message (GUID does not match expected GUID), but can see the new values. I do recommend to double check the variables have correctly been set in the Grub shell (command setup_var 0x507 without an argument will show the current setting, same for setup_var 0x5A4). I somehow didn't set them first time and had to anxiously repeat after a hanging reboot.

Thanks heaps to @b166ar & @themaxx32000.

And one should NOT forget to save their settings upon returning to BIOS...

 

[endrus]

Is anyone using an android phone w/ Mojave 10.14.4?

On Mojave 10.14.3 my connection was perfectly configured and worked either USB3.0 or USB-C. Using the same USBports.kext. After the 10.14.4 upgrade the phone does not properly connects.

As you see from Hackintool screenshot Android is recognised (configured) however when I open Commander One only the flash partition (highlighted) is visible (with ABD tools, drivers etc) and not the internal user memory.

Any idea?

 

[littlecreature]

Is anyone using an android phone w/ Mojave 10.14.4?

Any idea?

Just tested Samsung phone with 10.14.4 and USB3.0 with CommanderOne and all seems normal to me. My phone doesn't have USB-C however. For reference, I do have USB debugging enabled on my phone. Sorry, I don't know more than that.

 

[xmark]

2 times in 2.5 days my machine has not woken from sleep. Am reverting to F10. Details here.