Contribute
Register

[Guide] Asrock UEFI Boot Fix

Joined
Mar 31, 2014
Messages
6
Motherboard
Asrock z77 extreme 4 (Clover)
CPU
i5 3750k @ 4.2 Ghz
Graphics
Nvidia 560 ti OC
Mac
Classic Mac
Mobile Phone
Android
Great guide! Solved the issue.
On a clover update UEFI entry dissapeared , reinstalling wont fix the issue.

Happened to me on a z77 Extreme 4 motherboard.
 
Last edited:
Joined
Sep 11, 2017
Messages
13
Motherboard
Gigabyte GA-Z170-D3H
CPU
i7-6700
Graphics
GT 440
Mac
MacBook Pro
Mobile Phone
iOS
hello ...
I've a asrock h97m pro4 ... i've problem boot but i solved with BIOS upgrade and now boot start directly from ssd and stop at this point:

IMG_2508.JPG


if i start boot from pen drive multibeast all work correctly.

Asrock h97m pro4
i5 4460s
Kingston HyperX Fury 2x8Gb
Segate SSD 250 WDS250G1B0A

can anyone help me?
 
Joined
Sep 11, 2017
Messages
13
Motherboard
Gigabyte GA-Z170-D3H
CPU
i7-6700
Graphics
GT 440
Mac
MacBook Pro
Mobile Phone
iOS
i'm trying install ElCapitan, i tried with linux system in this guide but loading ElCapitan system still at same point.

2-loaded Optimized default
3-Vt-d disable
4-CFG-Lock is not present into BIOS
5-Secure mode is not present into BIOS
6-Set Os type is not present into BIOS
7-IO serial disabled
8-XHCI Handoff is not present
9-i tried with USB3 disabled an able
 
Joined
Oct 20, 2012
Messages
79
Motherboard
ASUS ROG Strix Z370-G
CPU
i7-8700K
Graphics
Vega 64
Mac
iMac, MacBook Pro
Mobile Phone
iOS
This small guide has been written to walk you through a possible fix to enable your Asrock motherboard to boot correctly using UEFI, primarily for the Clover bootloader. It should only be used if you have followed the recommended method for installing and booting using Clover, but your system refuses to boot without the Unibeast USB installer.

This issue was originally identified on certain Asrock motherboards, and has been tested on the Z87E-ITX. Since we are dealing with UEFI, there is no reason why it shouldn't work on other boards but has not been tested further.

An alternate method to this guide using Clover can be found here, courtesy of ctyler at post #38 of this thread.

The pre-requisites where this may work for you are :
:ch: You use an Asrock motherboard.

:ch: You have installed OSX using the recommended method.

:ch: You have installed the Clover bootloader.

:ch: Your computer won't boot from the system drive where you installed OSX and Clover.

If you can tick all four boxes above then read on. If not then you need to get your system installation to the point where you can tick all the boxes.

We are not aware of this happening on any other model of motherboard at this time. In the case of an Asrock motherboard, it appears to happen because of a poor/incomplete UEFI implementation. What this means is that the board does not boot properly, even though the Clover bootloader is correctly installed.

Important : The method we use here has proven to be non-destructive so far. No data has been lost, no fully installed system has disappeared. It doesn't mean that will always be the case. You are responsible for your data and keeping proper backups of your important stuff. Be smart and do that before you begin.

There are a number of considerations for this method - pay attention and read them carefully so you fully understand the implications:

1. Existing Methods. You should follow the existing guidance and make every effort to install your system the recommended way. We are primarily looking at Mac OS X El Capitan using the Clover bootloader. The recommended method can be found here.

2. Search The Forums. See if anyone else has built their system using the same motherboard as you. They may have already discovered the correct settings to enable booting from UEFI.

3. Reverting Changes. The changes described here can be reversed by doing a full UEFI bios reset. This is good in case you make a mistake; the downside of this is that you will then need to go back and change all your bios settings again. Most modern motherboards have the option to save your current settings to a profile, which can then be recalled. Make use of this.

4. UEFI Boot Setting. If you haven't already done so, make sure your system is set to boot using UEFI instead of legacy. This is usually found in the boot settings of your bios. Be aware that most modern motherboards which use UEFI will show both UEFI and legacy boot options at the same time.

5. Linux & The Command Line. The way we do this is by using linux, working from the command line, using elevated privileges. If you are not comfortable with this then do not proceed. Elevated privileges mean you could easily cause damage to your otherwise shiny new OSX installation.

Finally, if your Clover install is hosed or incorrectly configured, this method will not fix it for you. This is about helping the motherboard UEFI to 'see' the Clover bootloader correctly; it does not fix a broken or incomplete Clover install.

So now you have read all that, what to do next ?

Follow these steps in order; do not deviate. Take your time and read the instructions very carefully.

Part 1 : What You Need

Our weapon of choice here is a good linux distribution. You are free to choose whichever you like, but you must make sure that it contains the package 'efibootmgr', and also that it contains an EFI kernel module. This module if often called 'efivars'.

The tested distribution at this time is Mint Linux. This is a modern, up-to-date distribution, and contains the package and module described above. It does not require a network connection, which some other distros may need. Follow this link to download the version I used successfully. The instructions in this guide assume you are using this distribution, other distributions may be slightly different.

You will need to create a bootable drive with the linux you downloaded. Since the download is a standard .iso image, you can simply burn it to a DVD drive, or create a USB drive from it. There are many tools available to create a USB installer; one example is 'UNetBootin' which has versions available for Windows, OSX or Linux.

Important : Make sure you do not overwrite your OSX Unibeast installer.

Part 2 : Boot The New Linux DVD/USB

Insert your new linux DVD or USB and boot your system from it. Press F11 or whichever key your system uses to get to the boot selection list. In the list you will see several entries, and the one you are looking for is UEFI and represents the drive containing your linux. Here is what mine looked like :

View attachment 154765

In this case, I wrote the linux iso image to DVD and booted from that.

Important : Only boot from the UEFI entry. Using non-UEFI means it will not work as expected.

It may seem odd that you have a UEFI entry for your removable drive with linux on it, but not for your system drive with the OSX installation. This is the quirk we are attempting to fix with this method.

Wait for the linux desktop to load. This may take a few minutes depending which medium you are booting from. As the desktop loads, you will see a login box on the screen. Don't enter anything here, the system will automatically log you in after a few seconds.

Part 3 : Change The Settings

Here is where we really get stuck in; once again, pay close attention.

At the bottom left of the linux desktop screen, next to the menu button you will see several small icons. Click on the icon for 'Terminal'. This will open a window similar to the 'Terminal' application in OSX.

View attachment 154766

Now type in the following commands and press Return :

Code:
sudo -s
The system has already given us elevated privileges, but doing this will save extra typing.

Code:
modprobe efivars
This tells linux to load the kernel module 'efivars'. This is needed so that linux can communicate with the UEFI system on your motherboard.

Code:
apt-get install efibootmgr
This tells the linux system to install the 'efibootmgr' package we need. It is already on the linux system but not installed by default.

You will see some text on screen as the package is installed. This is what your Terminal window should look like so far :

View attachment 154767

Code:
efibootmgr
This runs the efibootmgr program. You will see a list of drives in your system ; the exact output will vary. Here is what mine looked like :

View attachment 154768

In the list you can see I have a total of 3 drives listed. The first (Boot0001) is my SSD system drive, the second (Boot0002) is my DVD drive, the third (Boot0003) is also my DVD drive but as a UEFI device.

Each one has an ID of the format 'Boot00xx', and the boot order is shown relative to these. The currently booted drive is also shown as 'BootCurrent'; this confirms I have booted UEFI from the Optiarc DVD drive.

Code:
efibootmgr -c -L "Clover UEFI" -l "\EFI\CLOVER\CLOVERX64.EFI"
This instructs the system to create a new UEFI entry.

The first part in quotes, "Clover UEFI", is the label you are giving to the new UEFI entry. This can be any description you like, but must be enclosed in quotes.

The second part in quotes, "\EFI\CLOVER\CLOVERX64.EFI" tells the UEFI system where to find the file it needs to start the UEFI boot process.

The flag in the middle of these 2 parts is a lower case L and not the number 1.

Important : Notice that we use back slashes in the second part, and not forward slashes. Make sure to get this right otherwise it won't work.

Here is the ouput :

View attachment 154769

You can see my new entry has been given an ID of 'Boot0000', and is currently at the bottom of the list. The system has correctly set its boot order, but we also want to move it to the top of the list.

Code:
efibootmgr -o 0000
This reaffirms the boot order for our new entry and puts it at the top of the boot list, which we will see when we reboot the computer.

The four digits we use in the command above represent the last four digits of the ID assigned to the drive.

The correctly configured list and boot order now looks like this :

View attachment 154770

That is the required changes now made.

A quick check in the bios boot order shows the changes have been successful :

View attachment 154771

You should now restart the computer and remove the linux boot DVD/USB. Once again press F11 or whatever key your system uses to display the list of devices.

Go ahead and select the new UEFI entry to boot from Clover.

You could also use something more descriptive. Here is another way I labelled it :

View attachment 154772

Whichever label we use when adding the new entry is whats shown in the bios boot list.

Nice touch huh ?

:thumbup:

Oops, I Might Have Messed Up With The Guide, What Do I Do Now ?

If your system does not boot as expected or you have got lost somewhere in the middle of the guide and not sure what to do next then simply reboot your system, go back into your bios and do a full bios reset, back to default settings. Any changes will then be wiped out and you can try again. Remember though to optimize your settings for OSX as usual.

The changes we have made with the guide will survive reboots, but will not survive a bios reset or bios upgrade.

Note this method will not fix every single Clover boot issue; if you find you can boot UEFI from the Unibeast installer but not your OSX system drive, this may work for you.

Let us know if this method helps you out !


:)
Thank you, my friend. Works flawless!
 
Joined
Oct 3, 2011
Messages
29
Motherboard
Asrock Z97 Extreme4
CPU
Intel Core i7 4790K @4.0Ghz
Graphics
Intel HD4600
Has anyone tried this method on OSX 10.14 Mojave?

Thank you very much for your guide @WonkeyDonkey !

I finally got my booting problem solved on my Mojave 10.14 installation.
My motherboard is an ASRock z97 Extreme 4 which has this booting directly from SSD problem since El Capitan installation.
The last time I used @ctyler post #4 and got it working. But I can't get it to work this time on Mojave.

https://www.tonymacx86.com/threads/anyone-with-asrock-z77-pro3-motherboard.176172/

Thank you @WonkeyDonkey and @ctyler !
 
Last edited:
Joined
Jun 7, 2013
Messages
4
Motherboard
ASRock Z77Extreme4
CPU
I5-3450
Graphics
GTX 650
Mac
iMac
Mobile Phone
Android
Thanks, it worked on z77extreme4. Since it was loaded from usb, its name also entered in the boot menu. How can this be avoided?
Sorry for my bad English, I am writing through Google translator.
 
Joined
Dec 24, 2015
Messages
2
Motherboard
ASRocks
CPU
i3 3240 3.4GHz
Graphics
ATI Radeon 6870
Mac
Classic Mac
Mobile Phone
OP, I owe you my life. For real, thank you so much. This is the only post that has helped me with this. I now have a 100% up and running Sierra system. You are for real amazing for figuring this lil trick out.
 
Joined
Oct 4, 2018
Messages
1
This small guide has been written to walk you through a possible fix to enable your Asrock motherboard to boot correctly using UEFI, primarily for the Clover bootloader. It should only be used if you have followed the recommended method for installing and booting using Clover, but your system refuses to boot without the Unibeast USB installer.

This issue was originally identified on certain Asrock motherboards, and has been tested on the Z87E-ITX. Since we are dealing with UEFI, there is no reason why it shouldn't work on other boards but has not been tested further.

An alternate method to this guide using Clover can be found here, courtesy of ctyler at post #38 of this thread.

The pre-requisites where this may work for you are :
:ch: You use an Asrock motherboard.​
:ch: You have installed OSX using the recommended method.​
:ch: You have installed the Clover bootloader.​
:ch: Your computer won't boot from the system drive where you installed OSX and Clover.​

If you can tick all four boxes above then read on. If not then you need to get your system installation to the point where you can tick all the boxes.

We are not aware of this happening on any other model of motherboard at this time. In the case of an Asrock motherboard, it appears to happen because of a poor/incomplete UEFI implementation. What this means is that the board does not boot properly, even though the Clover bootloader is correctly installed.

Important : The method we use here has proven to be non-destructive so far. No data has been lost, no fully installed system has disappeared. It doesn't mean that will always be the case. You are responsible for your data and keeping proper backups of your important stuff. Be smart and do that before you begin.

There are a number of considerations for this method - pay attention and read them carefully so you fully understand the implications:

1. Existing Methods. You should follow the existing guidance and make every effort to install your system the recommended way. We are primarily looking at Mac OS X El Capitan using the Clover bootloader. The recommended method can be found here.

2. Search The Forums. See if anyone else has built their system using the same motherboard as you. They may have already discovered the correct settings to enable booting from UEFI.

3. Reverting Changes. The changes described here can be reversed by doing a full UEFI bios reset. This is good in case you make a mistake; the downside of this is that you will then need to go back and change all your bios settings again. Most modern motherboards have the option to save your current settings to a profile, which can then be recalled. Make use of this.

4. UEFI Boot Setting. If you haven't already done so, make sure your system is set to boot using UEFI instead of legacy. This is usually found in the boot settings of your bios. Be aware that most modern motherboards which use UEFI will show both UEFI and legacy boot options at the same time.

5. Linux & The Command Line. The way we do this is by using linux, working from the command line, using elevated privileges. If you are not comfortable with this then do not proceed. Elevated privileges mean you could easily cause damage to your otherwise shiny new OSX installation.

Finally, if your Clover install is hosed or incorrectly configured, this method will not fix it for you. This is about helping the motherboard UEFI to 'see' the Clover bootloader correctly; it does not fix a broken or incomplete Clover install.

So now you have read all that, what to do next ?

Follow these steps in order; do not deviate. Take your time and read the instructions very carefully.

Part 1 : What You Need

Our weapon of choice here is a good linux distribution. You are free to choose whichever you like, but you must make sure that it contains the package 'efibootmgr', and also that it contains an EFI kernel module. This module if often called 'efivars'.

The tested distribution at this time is Mint Linux. This is a modern, up-to-date distribution, and contains the package and module described above. It does not require a network connection, which some other distros may need. Follow this link to download the version I used successfully. The instructions in this guide assume you are using this distribution, other distributions may be slightly different.

You will need to create a bootable drive with the linux you downloaded. Since the download is a standard .iso image, you can simply burn it to a DVD drive, or create a USB drive from it. There are many tools available to create a USB installer; one example is 'UNetBootin' which has versions available for Windows, OSX or Linux.

Important : Make sure you do not overwrite your OSX Unibeast installer.

Part 2 : Boot The New Linux DVD/USB

Insert your new linux DVD or USB and boot your system from it. Press F11 or whichever key your system uses to get to the boot selection list. In the list you will see several entries, and the one you are looking for is UEFI and represents the drive containing your linux. Here is what mine looked like :

View attachment 154765

In this case, I wrote the linux iso image to DVD and booted from that.

Important : Only boot from the UEFI entry. Using non-UEFI means it will not work as expected.

It may seem odd that you have a UEFI entry for your removable drive with linux on it, but not for your system drive with the OSX installation. This is the quirk we are attempting to fix with this method.

Wait for the linux desktop to load. This may take a few minutes depending which medium you are booting from. As the desktop loads, you will see a login box on the screen. Don't enter anything here, the system will automatically log you in after a few seconds.

Part 3 : Change The Settings

Here is where we really get stuck in; once again, pay close attention.

At the bottom left of the linux desktop screen, next to the menu button you will see several small icons. Click on the icon for 'Terminal'. This will open a window similar to the 'Terminal' application in OSX.

View attachment 154766

Now type in the following commands and press Return :

Code:
sudo -s
The system has already given us elevated privileges, but doing this will save extra typing.

Code:
modprobe efivars
This tells linux to load the kernel module 'efivars'. This is needed so that linux can communicate with the UEFI system on your motherboard.

Code:
apt-get install efibootmgr
This tells the linux system to install the 'efibootmgr' package we need. It is already on the linux system but not installed by default.

You will see some text on screen as the package is installed. This is what your Terminal window should look like so far :

View attachment 154767

Code:
efibootmgr
This runs the efibootmgr program. You will see a list of drives in your system ; the exact output will vary. Here is what mine looked like :

View attachment 154768

In the list you can see I have a total of 3 drives listed. The first (Boot0001) is my SSD system drive, the second (Boot0002) is my DVD drive, the third (Boot0003) is also my DVD drive but as a UEFI device.

Each one has an ID of the format 'Boot00xx', and the boot order is shown relative to these. The currently booted drive is also shown as 'BootCurrent'; this confirms I have booted UEFI from the Optiarc DVD drive.

Code:
efibootmgr -c -L "Clover UEFI" -l "\EFI\CLOVER\CLOVERX64.EFI"
This instructs the system to create a new UEFI entry.

The first part in quotes, "Clover UEFI", is the label you are giving to the new UEFI entry. This can be any description you like, but must be enclosed in quotes.

The second part in quotes, "\EFI\CLOVER\CLOVERX64.EFI" tells the UEFI system where to find the file it needs to start the UEFI boot process.

The flag in the middle of these 2 parts is a lower case L and not the number 1.

Important : Notice that we use back slashes in the second part, and not forward slashes. Make sure to get this right otherwise it won't work.

Here is the ouput :

View attachment 154769

You can see my new entry has been given an ID of 'Boot0000', and is currently at the bottom of the list. The system has correctly set its boot order, but we also want to move it to the top of the list.

Code:
efibootmgr -o 0000
This reaffirms the boot order for our new entry and puts it at the top of the boot list, which we will see when we reboot the computer.

The four digits we use in the command above represent the last four digits of the ID assigned to the drive.

The correctly configured list and boot order now looks like this :

View attachment 154770

That is the required changes now made.

A quick check in the bios boot order shows the changes have been successful :

View attachment 154771

You should now restart the computer and remove the linux boot DVD/USB. Once again press F11 or whatever key your system uses to display the list of devices.

Go ahead and select the new UEFI entry to boot from Clover.

You could also use something more descriptive. Here is another way I labelled it :

View attachment 154772

Whichever label we use when adding the new entry is whats shown in the bios boot list.

Nice touch huh ?

:thumbup:

Oops, I Might Have Messed Up With The Guide, What Do I Do Now ?

If your system does not boot as expected or you have got lost somewhere in the middle of the guide and not sure what to do next then simply reboot your system, go back into your bios and do a full bios reset, back to default settings. Any changes will then be wiped out and you can try again. Remember though to optimize your settings for OSX as usual.

The changes we have made with the guide will survive reboots, but will not survive a bios reset or bios upgrade.

Note this method will not fix every single Clover boot issue; if you find you can boot UEFI from the Unibeast installer but not your OSX system drive, this may work for you.

Let us know if this method helps you out !


:)
Thank a lot pro.
 
Joined
Jan 23, 2011
Messages
21
Motherboard
GA-Z97N-WIFI
CPU
G3258
Graphics
GTX 760 2047 MB
Mac
MacBook Pro, Mac mini
Mobile Phone
Android
Dear WonkeyDonkey. You sir/madam are a brilliant genius! Saved me after hours and days of trying to figure out this issue. I have currently have pulled out all my hair and am bald. You are GOD!!!!!
 
Top