Leaderboard

If I am not mistaken, your EFI partition is never copied or cloned when using Carbon Copy Cloner or SuperDuper. You always have to build and copy/clone them manually.

Hi, I've created a new GUI agent application to assist Clover bootloader. Its name is "Clover.app". Made to run in 10.9 and newer. What it does (or should do)? Give prominent info about the current revision in use, the Boot Device (disk where Clover is) and the the config.plist used. Install Clover in UEFI and legacy mode with a new way to store preferences and with out a pain searching for the correct ESP. Prevent target like Catalina-Dati from another OS (and ruin it) or read-only volumes, as this is not allowed. Provide essential NVRAM management for most used things such Theme and sound used. Ability to search any (correctly formatted) ESP in the system and mount/open them. As well the ability to umount. Auto mount for the chosen ESP. Get rid of RC Scripts... Yes, no more, just a new daemon (CloverDaemonNew) written in Swift and controllable by the NVRAM. Dump the nvram in the ESP, boot device takes precedence, otherwise the first available Internal) EFI System Partition. Root partition as last resource. Easily read the boot log (and the daemon log.. w/o mess the System log). Checking for updates whithout installing preferences panes here and there: just one app. Themes Manager embedded which doesn't require git to be installed. About installing drivers Unlike the package you have more control about what you are installing: Selected drivers are just the mirror of what is it really present in your EFI/CLOVER/drivers folders, and in fact, checkboxes get activated only if the driver is really present. Unknown drivers, i.e. ones not included in the current installer, are listed as well. Of course the app will not be able to update drivers that doesn't own. Be aware that deselecting a driver means (unlike the pkg) to delete the driver! A back up is always made to ~/Desktop/CloverBackUp/ .. so you can handle the back up immediately by your self. Warning: old drivers64 and drivers64UEFI directories aren't taken into account, only new ones (drivers/UEFI and drivers/BIOS). For some time the package was updated to migrate old directory structure to a new one with also the renaming of drivers with the old -64 suffix (as Clover is 64-bit only for some time.. so no need to specify again and again). Clover bootloader Updates Updates are online, but will show up only if the online version is greater then installed one. Based on the update intervall you set in the GUI, otherwise monthly as default. Clover.app Updates When a new release will be published it will appear a window that will inform you about it. Based on the update intervall you set in the GUI, monthly as default otherwise. Testing Clover.app is in a Beta stage, and is going to be promoted as "stable". Update: installation of legacy Clover looks really good. (thanks to @Rodion2010 for testing the installation) Update: since v1.11 is now compatible with 10.9 Mavericks and newer. Tested in 10.9, 10.10, 10.11, 10.12, 10.14 and 10.15. As soon someone will test successfuly it in 10.13 the Beta stage will ends. But why waiting for a test in 10.13.. there are problems otherwise? No, no problems. The code is written in swift 5 (whith stable ABI) and I did not expect something different for the code I wrote, but the difference can reside in the Cocoa.framework shipped with the OS: starting in 10.10 Apple introduced some new stuff for the interfaces like dark mode, Visual effect views (with vibrancy appearance) and problems can reside because many Apple-bugs where introduced and only fixed later. For this some graphical issues can show up (like a dark background with a dark text where you are able to see nothing). In the mentioned OSes all is fine (or at least perfectable), so just High Sierra is missing .... FAQs How to find the correct partition to update/install Clover? When you select a disk, the one with the Clover image... is the partition where Clover started. Easy no? Why you can't see other disks under "Mount (ESP)"? Because there, the app show only ESPs (EFI System Partition) and if a disk did not show up here... it's because the partition you are looking for is not an EFI System Partition. Why you can't see all the partition you have in the Installer? Because to install Clover it's required a filesystem to be FAT16, FAT32, EXFAT or HFS. Other ones are simply not taken into account. Example: if your ESP is formmated with FAT16 filesystem, BIOS options will not get activate because Clover doesn't have boot secotors for the ol fat filesystem! Warning, FAT16 can be good for UEFI loading, but for example my firmware simply ignore it. FAT32 is higly recommended for ESP, you're warned. What Make filesystem read-write" does? It is irreversible? This function add an nvram key that the daemon can read when the system starts so that can made the filesystem writable, if isn't, by invoking "mount -uw /". As you know starting from 10.15 the root filesystem is read-only and this functionality can help if you want to write to the System partition, like the case if you want to disable the Bonjour Sleep proxy Client, or to dump the nvram in / using EmuVariableUefi.efi, or using kexts like HibernationFixUp. It is a permanent change? No, mount -u means update an already mounted file system, so disabling the functionality the filesystem will stay as per default. The change is applied at next start up. What does "Disable Sleep Proxy Client? If your computer wake itself from sleep each n hours it's probably due to the Bonjour service called "Sleep Proxy Client". If you don't want this to happen you may want to disable it. In 10.15+ this functionality require the filesystem to be writable to add a special argument to the mDNSResponder launch daemon. By disabling the checkbox the service get re-enabled as per default, but then will require a read-write filesystem, at least for the next reboot. Note: if the filesystem is not writable the daemon will try to make it read-write to do the modification even if "Make filesystem read-write" is turned off. CloverDaemonNew is a complete replacement for the RC Scripts? Yes. It does every things done by rc scripts but without installing additional scripts into the System directories. Warning: the CloverDaemonNew is not compatible with old rc scripts and for this reason, since v1.07, Clover.app remove them. For the same reason the package remove CloverDaemonNew if you install back the rc scripts (since commit d447228 of november 29 2019). Big thanks to @Sherlocks for helping me to make it work. Themes Since v1.15 Clover.app has a Theme Manager. Unlike CloverThemeManager.app git is not mandatory, and in fact it doesn't use it. The requirement it is a Github repository instead. The main repo for Clover.app is https://github.com/CloverHackyColor/CloverThemes but the app allow you to chose a fork by specifying the GitHub user name and the GitHub repository name: A requirement for users repository is that your will contains themes in the root of it, and not in a sub directory. After themes are indexed (if you ever run the Theme Manager) a list of all themes is listed below: (You can type anything you want, and auto completion is available) ..so you can switch the theme to use by set its name in NVRAM. This way Clover override what is set in the config.plist. Sound Since v1.13 (with Clover r5102+) Clover.app is able to handle the volume level and the device for the the start up sound: No sound? Ensure the volume is audible (100%) and the device it is really connected to speakers. Of course your theme must contains the sound file. How to install Clover in UEFI only? Simply by not selecting "CloverEFI" (which means legacy Clover) and without play with MBR/PBR (Master Boot Record/Partition Boot Record). "CloverEFI" it's replaced by "BIOS". How can you install Clover in legacy mode? Simply by selecting "CloverEFI" (which means legacy Clover). MBR/PBR (Master Boot Record/Partition Boot Record) must be enabled the first time to make your disk bootable, and when this happened once there is no need to install boot sectors again. "CloverEFI" it's replaced by "BIOS". "Alternative boot" means that the installer will installs more then one boot loader you can chose by pressing the relative number (boot3, boot5, boot6, boot7, boot9) while booting. To do that the installer use a special boot 1 sector that wait 2 seconds to wait you for a key to be pressed. kernel panic installing bootsectors to a hfs partition (Clover legacy) During my tests with Clover.app I run in to a kernel panic installing boot sectors in a hfs formatted pen drive (and I realize some users had already run into this problem with the pkg) . After studying the problem, the conclusion is that the hfs driver panics when the journaling is enabled, so Clover.app take the step to disable the journal just before the installation. Of course the app re enable it as soon sectors are installed. Will the package installer no longer be supported? No. The package is still supported, also because Clover.app doesn't support old OSes like 10.8, 10.7 etc. and older. However the pkg has reached some limits by installing on Catalina. Can the Clover updater coexist? Yes, but why? With the package you have to install Clover to update them (in all partitions you have) to get access to it. With Clover.app you need only one app for all, ok, unless you have really old OSes. The Clover preferences panel? The idea is that you have every things you need by make Clover.app run at login. In how many languages it is translated? Actually in English (me) Italian (me) Russian (Slice) Portoguese (artur_pt) Korean (Sherlocks) German (Mork vom Ork) Simplified Chinese (Steve Zheng) Indonesian (Badruzeus) Serbian (crusher) French (Ellybz) But it can be translated in any language supported by macOS, so just start translating the en.strings and post the file here. Or make a pull request at github. Is it open source? Of course yes! Changes committed at github. How to compile? Xcode 11+ and swift 5+ both required. buildme do it for you. Last Release here

Just discovered this on the web and i just wanted to give a heads up about this cash grab and if something can be done about this: https://www.macrumors.com/2020/06/13/opencore-hackintosh/ https://opencore.computer/ They are ruining opencore's name and damaging acidenthera's work and the hackintosh community. This is wrong, so wrong... @Download-Fritz @Andrey1970 @vit9696 Edit: Acidenthera's response:

Following in the footsteps of Psystar, a new company called "OpenCore Computer" this week launched a commercial Hackintosh computer called the "Velociraptor," which is a violation of Apple's end-user license agreement or EULA for macOS. More at the link https://www.macrumors.com/2020/06/13/opencore-hackintosh/

Fantastic response!

Love this part, i'll give this idea to my weed dealer:

I also clone with ccc and then i reinstall vanilla clover in the esp of the cloned disk just to be sure. Then i copy the proper efi folder.

@Sherlocks, @Slice, сheck please.Disable RTC wake scheduling.plist.zip

CCC acctually appeared to have created a hidden EFI sized type partion, or maybe it was there from a previous hackintosh install, but it was empty so I dumped my EFI folder in there. As you say though, something wasn't copied or created in the correct way by CCC, eitherway its a learning experience and now I know the correct way so thanks guys.

Reboot machine, at the boot menu press space bar and click on Clean/Clear NVRAM, the machine will reboot, quickly press the delete key to into the BIOS. Once in the BIOS go to where you set which disk to boot from and set Opencore as the boot disk and disable the named disk Catalina is on save and reboot and all should be ok.

That is correct - a lot of people using ccc unwittingly thinks by cloning a drive using this app it copies everything, it does not to my knowledge copy the EFI Partition.

@jimborae Read my above comment. He has been a thorn in the side of everyone on this board at some point. And a horse's ass (or arse for my brit friends.)

And there is a new driver version coming, i will upload it after i finish with some code polishing and some long term testing, probably by the end of this mounth, stay updated for more info

Hello, Confirmed following configuration is fully functional (sleep/wake/sound/network/video) OS: OS X Sierra 10.12.3 Mainboard: P5GC-MX/1333 (https://www.asus.com/Motherboards/P5GCMX1333/specifications/) BIOS: Latest available from ASUS (https://www.asus.com/Motherboards/P5GCMX1333/HelpDesk_Download/) CPU: E8500 RAM: 2GB HDD: WD 160GB (IDE) Video: GeForce 9500 Bootloader: Clover Support files: config.zip DSDT.zip sierra_kexts.zip NOTE: content of the files goes to /Volume/EFI/EFI/CLOVER/{.,ACPI,kexts} (Sierra was not touched -- no alternation of any kind) by osx151212

Not directly on-topic for this thread, but also pertinent to why we're here at all: Dunno if you guys have read this yet. https://www.macrumors.com/2020/06/13/opencore-hackintosh/ Definitely got me a bit miffed.