Contribute
Register

[GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

Status
Not open for further replies.
never use instant flash use bios flashing tool in UEFI bios screen with only a windows drive attached to do bios updates. Always use a clean flash drive with no other files to do bios updates, or you can have problems. Always download bios updates in windows not Mac side

dasboot5,
I'm not sure what "instant flash" is so I'm asking...on a Gigabyte board (GA-Z170X-UD5) are you suggesting to not use Q-Flash? Also, what do you mean by "only a windows drive attached?" The Hackintosh where we need to flash the BIOS does not have Windows installed. I do have a PC that I plan to use to download the BIOS update and create the USB for flashing the BIOS. Is using that USB what you mean by "having a Windows drive attached?"

Thank you in advance for clarifying.

Jim
 
Thanks a lot for this guide! These EFI entries which will be added with every macos update are driving me nuts. Nice that we have this possibility to remove entries using clover. My bios simply will freeze with all custom entries. It was not such a problem using emuvariable.efi, since those additional efi boot entries never were persistent here back then...
 
dasboot5,
I'm not sure what "instant flash" is so I'm asking...on a Gigabyte board (GA-Z170X-UD5) are you suggesting to not use Q-Flash? Also, what do you mean by "only a windows drive attached?" The Hackintosh where we need to flash the BIOS does not have Windows installed. I do have a PC that I plan to use to download the BIOS update and create the USB for flashing the BIOS. Is using that USB what you mean by "having a Windows drive attached?"

Thank you in advance for clarifying.

Jim
OK Here it is: You are using an Intel X86 machine which was designed for the Windows operating system and Linux primarily, but IT will Run, the Mac OS, with the use of Clover. There are many ways to update your bios depending on the Motherboard manufacturer, but bios code is specific and more complex now that we are using UEFI bioses. The Manufacturer decides what company's basic architecture their bios will customized on: The motherboard manufacturer then customizes this BIOS to suit its own hardware. For this reason, updated BIOSes are normally obtained directly from the motherboard manufacturer. Major BIOS vendors include American Megatrends (AMI), Insyde Software, Phoenix Technologies and Byosoft.
The newer UEFI bios code (updates) are specific to the motherboard and its revision number. The updating process can be done in the Windows OS when booted, using a flash drive and software utility from the manufacturer. This is not recommended. Flash drives used should be clean, not large in capacity, and formatted in FAT 32 and good quality and placed only in a backplane USB 2.0 port not USB 3.0 3.1C or an front panel port. Do not use NTFS or any other drive formatting. If you cannot get into the current bios, some boards have a special USB flash port on the backplane to correct this, still not recommended, unless you no other option, other than ordering an new flashed bios chip, from the motherboard company, or a service.

You should enter the bios determine what bios revision you are on, make sure the bios you are updating to will not cause problems with the Mac OS you are installing. Find the Q Flash utility or similar and Update. You do not need any drives attached for this procedure, Windows or Mac and this is recomended. However to check functionality a Windows drive is the only option, after an upgrade flash, using a utility like HWINFO64 to check your hardware and new bios revision, you can seethe new revsion in the bios screen but this does not check bootabilty and bios settings may be not correct for Mac or Windows bootablity after flashing to new revision. It recommended to rest bios to defaults and change settings back as needed for Mac bootability. You should write down what settings worked before flashing. Once you satisfied, reconnect you Mac OS drive or, start in installation process with UNIbeast or a Clover based installation flash using Mas OS installer through terminal.
All my machines are dual boot, so I just assume most are the same, but many here use only Mac OS which makes harder to check an new build's functionality before stating the Mac OS installation process.
 
GA-Z170X-UD5 BIOS Version F22 solves the multiple boot volume entries in bios for this board. FYI. I used my windows gigabyte tool to install.
 
If the deleted entries from the Clover BIOS are still present after reboot in the BIOS, how do we remove them here ?

I successfully deleted the non-HD entries following the mentioned steps but deleted ones are still present on reboot and doing it twice didn't changed anything.

I don't see any suggestion about that in the Guide.
 
If the deleted entries from the Clover BIOS are still present after reboot in the BIOS, how do we remove them here ?

I successfully deleted the non-HD entries following the mentioned steps but deleted ones are still present on reboot and doing it twice didn't changed anything.

I don't see any suggestion about that in the Guide.
The EmuVariableUEFI driver might prevent this from having any effect. Firmware will recreate appropriate entries at boot time, but you shouldn't have a long list pointing to the same /EFI/BOOT/BOOTX64.EFI instance.
 
The EmuVariableUEFI driver might prevent this from having any effect. Firmware will recreate appropriate entries at boot time, but you shouldn't have a long list pointing to the same /EFI/BOOT/BOOTX64.EFI instance.

Thank you for the suggestion, I'm trying to understand what I can do with that.

Also, nobody responded to my topic since my build stopped booting Sunday, would you mind telling me what's wrong with it ?
https://www.tonymacx86.com/threads/...-boot-after-working-for-a-while.246440/page-2

Thanks again :)
 
No, the Preboot volume is for booting.

I’m aware of that, however its that many of us have still this option after a successful / completed install. This is my situation after installing a Mojave beta. I’ve also read that others have had this occur after a ahigh Sierra install.

As such, I had assumed it was a left over remnant boot option.
 
Status
Not open for further replies.
Back
Top