Why was the recovery mode connection blocked with recent clovers? in fact the connection in recovery is had only with the 5092 version

Switching form a config file which has SMBIOS>Memory>Modules to a config file without SMBIOS>Memory and booting will still inject the memory modules from first file.
The same thing happens when switching from a config file with more memory modules (eg: 2x16GB, slot:0+1) to a config file with fewer modules (eg: 1x32GB, slot:0). In this case it will inject 1x32+1x16GB

just tried the new Weg an still a black screen when booting on clover for second stage also tried boot args (agdpmod=pikera,vit9696) using either DP an HDMI ports with same results

Catalina 10.15.1, AptioMemoryFix, working NVRAM, latest Clover

CpuPM, SpeedStep, TurboBoost, Power Nap is OK

But why Hibernation 3 / 25 doesn't work on Catalina – I dunno.

If do not use fackcpuid，clover will unbootable

The latest release will not install on macOS 10.15.1, failing with the error "An unexpected error occurred while moving files to the final destination."

Log:
https://pastebin.com/LsSq9wnR

Excerpt:
Nov 2 15:19:20 #####s-iMac shove[1446]: [source=file] failed _RelinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/903C5760-622B-45B8-A2F1-5EAB219523B4.activeSandbox/Root/EFIROOTDIR/EFI/BOOT/BOOTX64.efi, /EFI/BOOT/BOOTX64.efi): Directory not empty

I've tried:
Disabling SIP
running sudo mount -uw /

E3-1230 v3 1150 Hasewell CPU, MSI ZH87 motherboard, HD7950 graphics card.

It can sleep or hibernate, but when wake up, cpu behaves working very slow.
The time of cpu is the problem.
I don't know how to fix it and almost tried every option on motherboard or clover but none of them working.

Thanks for helping.

I installed Clover r5097.
The folder that it creates in /EFI-Backups of the previous Clover release is called "r", not "r5070" which is the actual release name.

Also, it creates a file called ".empty" in the EFI/BOOT folder.

I know documentation is a lot to ask for from an open-source project of this scale... but at least a formal notice on the SourceForge site somewhere would be pretty helpful.

When I download a release from a website and all it has is a text file pointing me somewhere else (with no mention on the actual site), I am (and should be) immediately suspicious that something has been compromised.

A little bit of guidance goes a long way...

Dear,

I have a request, I noticed some changes on my new notebook, so clover can't detect my screen resolution and screen size.

I don't know if this is an issue, I tried to change gui settings and played around with csmvideodxe.efi
Without csmvideodxe external screens over dp not working.

Also I noticed that I run an opensuse installer the can grub detect right screen size and resolution.
Think clover is here for edp connected displays unable to detect the edid.
Running on lenovo yoga c940.

Clover is working only at the bottom of the screen I have a black unused area of 3 centimetres.
macOS run with internal screen only without framebuffer loading, or I need to use external screen and disconnect internal screen from mainboard.

best Regards

r5096 caused my system to be slow and it crashed 2 times today due to an unknown kernel panic while reaching to high memory usage. Had to revert to r5093 of this clover on the link below.

https://github.com/Dids/clover-builder/releases

For a while now, I'm having issues with Clover defaulting back to the Recovery partition as the default boot volume.

Strange thing is if a do an immediate reboot, Clover will remember the last disk, but if the computer has been running for a while, like to the next day, it will default to Recovery again.

Any idea were to start?

This is from my config.plist:

<dict> <key>Arguments</key> <string>dart=0 darkwake=0</string> <key>Debug</key> <false/> <key>DefaultVolume</key> <string>Hackintosh SSD</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <true/> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>Yes</string> </dict>

boot.log

I posted a ticket here: https://www.tonymacx86.com/threads/instant-reboot-after-upgrading-to-clover-5098-asus-prime-z370-a-8700k.287131

It seems the instant reboot is happening because AptioMemoryFix is missing. Any ideas why this was removed from the standard installation?

Honest not sure if i should be selecting the EFI partition or the "MacOS Installer" partition, but either one results in this error message:
Installation begin..
0:230:
execution error: My Path = /private/var/folders/6x/cgj9ntt53bjfkwtxct41m3800000gn/T/AppTranslocation/87D3CDD4-B8CC-495A-BB12-88A2DB533AFB/d/Clover.app/Contents/MacOS/Cloverhelper
Target volume: /Volumes/EFI
Error: target volume "/Volumes/EFI" is not writable. (1)

I have tried with the EFI partition mounted and unmounted

I'm on macOS Catalina 10.15 (19A602). I have not updated Clover since I switched to Catalina from Mojave. SIP is on and everything works fine otherwise. I have not had this problem before upgrading. When I open the installer Clover_v2.5k_r5098.pkg with right-click and open it goes through these states after interaction:



In the end, it shows the error "cannot install without ensuring the file system is read-write" and then quits.

Was previously using ver. 5045 and had this issue. Just updated to current stable release (5097) and the issue persists.

In Clover, for example when trying to manually add boot flags in the Options menu, the Shift key does nothing. I've tried two wired USB keyboards: Matias QuietKey Pro (Mac) and a Logitech K120 (Win).

Searching around I've seen similar reports on various forums but they date back several years and none look to be resolved.

With the following settings, the resulting USB has no EFI partition and is not bootable.
The EFI folder appears on the main data partition.

I have a Macbook Pro 13 2019 running Mojave

CLOVERX64.efi was compressed to 7z in release 5102, why not just attach an .efi or compress to zip?

As far as I've seen, Clover has an iso9660 driver. Is it possible to load / boot an iso CD/DVD image? I couldn't find anything on google / wiki.

the application cannot be run without making sure the file system is writable

On Catalina (OS X 10.15), Clover installer can't get read/write access

Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover

I have a freez on Scan entries. I figured out it's one of the 4 hdd that I have in raid0 in OS using SoftRaid software. It was working fine before update from r4xxx. What I'm doing: take off the data cable from that hdd, when clover gui is loaded I insert back the data cable and hit enter. So, once I'm on desktop the SoftRaid software shows me SMART status without any error on any of 4 hdds.
What can I provide guys to show you the problem? The problem with logs is that clover is freezed so have no idea what to do.
Thank you!

Clover won't install on my machine. Settings/components don't matter.

"caused an assertion to fail". I wonder if that has something to do with the ESP being the 2nd instead of 1st partition (blame Windoze for that one!) (windoze was already there, I originally installed high sierra on an old HDD but "restored" the partition onto my primary SSD with Disk Utility because it took ages to boot up)

There's an issue with this (and this), where it'll always use the newest tag, even if you're currently not on the latest tag.

For example, say you've checked out tags/5096. With tag 5097 being the latest, Clover would still be built with 5097 set as the revision/version.

Here's the current command and its output:

❯ git describe --tags $(git rev-list --tags --max-count=1)
5097

Now here's one potential way you could fix this:

❯ git describe --tags --abbrev=0                          
5096

This way it would always use the current tag, or the latest one up to the current commit, but never a newer one.

I installed a new NVMe Crucial 1TB via PCIe Adapter. Clover 2.5k_r5093 sees this disk only if formatted HFS+. I tried to clone a Catalina Installation to the NVMe, no success. I tried to install Catalina fresh, Clover sees the disk after the first step, the installation continues, on last reboot Clover does not see the NVMe again. I tried to install Mojave fresh, also the APFS isn't available in Clover. macOS Catalina sees the disk and it is usable, but not bootable if formatted APFS. Is there a solution to this problem?
preboot.log

config.plist.txt

I am reposting this issue because it was closed yesterday without any resolution. The original issue is here: #26

The latest release will not install on macOS 10.15.1, failing with the error "An unexpected error occurred while moving files to the final destination."

Log:
https://pastebin.com/LsSq9wnR

Excerpt:
Nov 2 15:19:20 #####s-iMac shove[1446]: [source=file] failed _RelinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/903C5760-622B-45B8-A2F1-5EAB219523B4.activeSandbox/Root/EFIROOTDIR/EFI/BOOT/BOOTX64.efi, /EFI/BOOT/BOOTX64.efi): Directory not empty

I've tried:
Disabling SIP
running sudo mount -uw /

What version that can be installed on mojave? I have try many version and show same error

Hello Slice! Can you please merge that issue with issue #35 ? Thank you!

I have a problem when clover freeze on Scan Entries. Sorry Sergey, was busy and I don't provided the log and you closed the Issue.
Attaching preboot log.
preboot.log.zip

Is the preboot log reset on every boot? If so you won't find anything there because to boot into the OS I need to de-attach the hdd that gives the problem to clover, wait Clover UI, attach the hdd and then hit enter....
Thanks!

As done by acidanthera for Opencore, they improved their documentation providing a PDF where they can group all knowledge spread across multiple forums and describe all the changes from commit to another

Is it possible an english (and/or Italian as could be done by vectorsigma72?) version for future releases of this previous guide in order for us to better understand? I'm referring to this document:
https://github.com/CloverHackyColor/CloverBootloader/releases/download/5097/Clover.of.Hacky.Color_5097_rus.pdf

It would also be perfect to have a "Differences.pdf" - if it's possible to maintain this guide up-to-date. I strongly believe that this project will benefit whether if is going to happen

Thank you

I've updated the clover to 5096 before, and updated my mojave to catalina. Everything is good and no problem. I have updated to supplement version now 19A602.
I just got a notice that clover 5097 is released and it suggested me to update. So I download it from the Github.
When I try to install clover 5097, it said the installer is not compatible with this MacOS, and when I continue, it finally failed. I can still reboot from clover, but the clover control panel disappeared from the system preference. I also tried to install the clover 5096 again, the same error.

I guess reason is about the new system file protection in Catalina, but I don't know how to solve it and update my clover in future.

Any solution to this? Thanks

I have this old notebook hackintosh with legacy bios:

CPU Intel core 2 duo 2,53 ghz, GPU: NVidia Geforce 9800m GTS 1024MB, SRAM 6GB, SSD Samsung 860 EVO 1TB, macOS 10.13.6 High Sierra+Windows 10 64bit, Smbios MacBook Pro 7,1

it works with all previous version of clover since 5093 but with 5094 it doesn't start
It stop at the cursor in the left angle and never show the clover's gui

acidanthera/bugtracker#424

Clover can solve it?

acidanthera/OcSupportPkg#12

When installing Clover using option "Install Clover in the ESP" on the APFS Fusion drive it unable to find EFI system partition on the physical disk and install to the macOS partition. Same problem as in issue 519: [https://sourceforge.net/p/cloverefiboot/tickets/519/]

Output of diskutil list:

/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         511.9 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         1000.0 GB  disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.5 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Fusion Drive            600.1 GB   disk2s1
   2:                APFS Volume Preboot                 46.3 MB    disk2s2
   3:                APFS Volume Recovery                510.4 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4

Clover_Install_Log.txt

espfinder.plist.zip

I got same error as:
Dids/clover-builder#84

for clover 5098 & Catalina 15.1

I upgraded Clover from maybe 4722 (am unsure of specific version) to 5098 and now the machine won't boot. The computer's macOS version is 10.14.x (not 10.15). Clover menu appears, I select hard disk boot entry (or let it select based on timeout), bunch of EFI-related boot logs display, and process hangs after a row of +++++++++

I assume booting doesn't work off hard disk because I have old EFI drivers and kexts in place that are incompatible with the new 5098 version. I had overwritten my working rescue USB thumb drive, so I built a new one using Mojave 10.14 installer following the vanilla desktop guide. I am using the exact same thumb drive that I used for initial installation a few years ago; drive appears to work just fine. Booting from USB drive also results in errors or hang.

You can see in this image that, indeed, EFI/Clover are using the intended thumb drive device. Unfortunately, I can't ever seem to get a debug log created in EFI/CLOVER/misc.

Computer hardware is a Gigabyte GB-BXi3-5010. Even though BIOS settings were working, I updated settings to mirror recommendations for Haswell in vanilla guide.

Any suggestions?

Configuration for latest attempt: CLOVER.zip

On my two computers usb 3.0 cannot be used as a method to install osx, each version newer than 2.4k_r4813 breaks usb 3.0 (still waiting for root device). If you can start the installer using a usb 2.0 you can then install usbinjectall and the 3.0 ports will work. On my laptop however I don’t have usb 2.0 so i can’t proceed. I am writing this because I think that this is a clover issue because if I use 4813 it works but if I use another newer version it does not.
clover.zip

Checking out the branch 5101 and running a ./buildme command yields the following error:
Error compiling nasm-2.14.02 ! Checking the log:

/Users/sdhaene/Projects/CloverBootloader/toolchain/tools/logs/nasm.make.log.txt:

A number of linking errors occured:

...skipping...
make:       _main in nasm.o
*** [rdoff/rdf2bin] Error 1  "_symtabInsert", referenced from:

  "_src_free", referenced from:
      _processmodule in ldrdf.o
      _main in nasm.o
make:   "_globalbits", referenced from:
      _main in nasm.o
*** [rdoff/rdfdump] Error 1
      _main in ldrdf.o
  "_rdfloadseg", referenced from:
      _processmodule in ldrdf.o
      _main in ldrdf.o
  "_add_seglocation", referenced from:
      _main in ldrdf.o
  "_rdfnewheader", referenced from:
      _main in ldrdf.o
ld: symbol(s) not found for architecture x86_64
  "_nasm_free", referenced from:
      _main in ldrdf.o
  "_done_seglocations", referenced from:
      _main in ldrdf.o
clang: error:   "_rdfgetheaderrec", referenced from:
linker command failed with exit code 1 (use -v to see invocation)      _processmodule in ldrdf.o

      _main in ldrdf.o
  "_nasm_malloc", referenced from:
      _processmodule in ldrdf.o
      _main in ldrdf.o
      _loadmodule in ldrdf.o
  "_nasm_strdup", referenced from:
      _processmodule in ldrdf.o
      _main in ldrdf.o
      _loadmodule in ldrdf.o
  "_symtabFind", referenced from:
      _processmodule in ldrdf.o
      _main in ldrdf.o
  "_rdl_openmodule", referenced from:
      _main in ldrdf.o
  "_fwriteint32_t", referenced from:
      _main in ldrdf.o
ld: symbol(s) not found for architecture x86_64
make: *** [rdoff/rdflib] Error 1
clang: error: linker command failed with exit code 1 (use -v to see invocation)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [nasm] Error 1
make: *** [rdoff/ldrdf] Error 1

Also tried the commands ./buildme XCODE8 and ./buildme XCODE11 yield the same results.
Am I doing something wrong, or does the build fails under Catalina?
Using OSX 10.15.2, XCode 11.3 with the additional tools.

Apple clang version 11.0.0 (clang-1100.0.33.16)
Target: x86_64-apple-darwin19.2.0
Thread model: posix

Any help would be greatly appreciated.
nasm.make.log.txt

When booting a FileVault encrypted apfs volume it sits for a very long time (1-2 min) at an apple logo with black background before showing the FileVault password entry screen. This is a regression in Catalina beta 11 / final as it was working instantaneously on all versions of Mojave and Catalina beta 9 and prior. Verbose mode doesn't work at this stage in booting.
This doesn't happen when using OpenCore bootloader.

This happens with current Clover latest release build: 5096 and previous (verified on 5070 and onward).

Originally reported both on Reddit https://www.reddit.com/r/hackintosh/comments/d1m24i/extremely_slow_filevault_boot_on_catalina/

And on InsanelyMac
https://www.insanelymac.com/forum/topic/339035-pre-release-macos-catalina/?page=69&tab=comments#comment-2692344
https://www.insanelymac.com/forum/topic/339035-pre-release-macos-catalina/?page=69&tab=comments#comment-2692364

And can't be opened.

“Clover_v2.5k_r5089.pkg” can’t be opened because it is from an unidentified developer.

Dear SergeySlice,
do you have communication with cVad from Boot Disk Utility (aka BDU)?
Unfortunately, BDU stopped downloading releases after 5070, because You have migrated development to GitHub from sourceforge.net.
Could you help with the contacts of the BDU-utility developer to upgrade it to work with Clover on GitHub?
Thx a lot!

I am trying to understand the different parts that are playing together here.

• How much does clover rely on the underlying UEFI?
• What is rEFIt's role?
• What other dependencies are there?
• What does clover implement exaclty?

I would like to build kexec into something mac compatible from within linux but am struggeling understanding clovers parts.

Do not install NVRAM-Emu things when user select AptioMemoryFix.efi in installer

In UEFI it's all right, AptioMemoryFix uses NVRAM for it purposes.

I have all RC-scriprts, but duet doesnt remember LastBooted

I believe they should be under Recommended Drivers. I had to get them manually from their own project page here which I believe didn't use to be necessary.

I've installed Clover into a Catalina media image created on a thumb drive from Mojave; I've selected install only EFI and select dark theme.

From this point I just got a black screen, someone recommends to me install Lilu kext, and before of that I finally saw something which is this message:

And is stuck forever.

I have a laptop ASUS FX504GE, secure boot disabled, virtualization too, boot on EFI.

Summary
		Operating System
			Windows 10 Home Single Language 64-bit
		CPU
			Intel Core i7 @ 2.20GHz	47 �C
			Coffee Lake 14nm Technology
		RAM
			16,0GB
		Motherboard
			ASUSTeK COMPUTER INC. FX504GE (U3E1)
		Graphics
			Generic PnP Monitor (1920x1080@60Hz)
			Intel UHD Graphics 630 (ASUStek Computer Inc)
			4095MB NVIDIA GeForce GTX 1050 Ti (ASUStek Computer Inc)	43 �C
			ForceWare version: 436.15
			SLI Disabled
		Storage
			119GB Hitachi HFM128GDJTNG-8310A (Unknown (SSD))
			931GB TOSHIBA MQ01ABD100 (SATA )	29 �C
			28GB SanDisk Ultra Fit USB Device (USB )
		Optical Drives
			No optical disk drives detected
		Audio
			Realtek High Definition Audio

Hi – Thanks for creating Clover Bootloader!

I was just wondering what the best / safest was is to remove Clover Bootloader from my MacBook Pro?

I was creating a boot USB drive and accidentally set the install location as my HD instead of the USB drive.

I haven't rebooted the Mac yet, and was wondering what the best way is to remove it.

Thanks in advance!

Every time I boot windows from clover (efi) the trackpad pointer move very slowly so I have to suspend and restart or reinstalling the driver to get my trackpad working again.
I don’t know if this is a clover issue or mine, if it is me I am sorry
preboot.log