Contribute
Register

[Solved] Clover will not boot last booted volume

Status
Not open for further replies.
In my experience the "LastVolume" parameter is simply ignored by all the different Clover versions I have tried so far. Value in NVRAM always has priority.
 
apfelwurm said:
In my experience the "LastVolume" parameter is simply ignored by all the different Clover versions I have tried so far. Value in NVRAM always has priority.
Click to expand...
How do I get around this?
 
Same problem :/
 
I fixed this problem by removing the BIOS Chip (v. 32xx) of my ASUS Z170 Pro Gaming and replacing it with a non Kaby Lake support BIOS (in my case v.1904 and v.2003) and now EVERYTHING is working properly. :)
Autoboot, iMessage, Appstore, full acceleration on my GTX 1070 etc. :)
 
Alright I may have a solution.

In my experimentation, I realized that my NVRAM still held values without the Emuvariableuefi-64.efi driver in Clover, which should mean my computer has actual NVRAM memory. My theory is that Emuvariableuefi-64.efi conflicts with the real NVRAM memory so just remove the Emuvariableuefi-64.efi because Mac will use then use the real NVRAM and everything will be fine.

To test if you have native NVRAM memory:

0. Make sure you have the most recent version of Clover (just in case, idk)

1. Copy out the Emuvariableuefi-64.efi out of your drivers64UEFI folder and place it somewhere else (where it won't be loaded). Reboot.

2. Open the terminal and run
Code: 
sudo nvram asdf=asdf

Double check it is in there by running
Code: 
sudo nvram -p | grep asdf
Reboot

3. Check if it is still there by running
Code: 
sudo nvram -p | grep asdf
again. If it is, you have actual NVRAM, you do not need Emuvariableuefi-64.efi.

Any luck?
 
Last edited:
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top