Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.
Open Cloud Clover Editor
Cloud Clover Editor Wiki
Cloud Clover Editor Sources
Supports Clover EFI, Ozmosis, Chameleon, OpenCore
GUI and Text Editor Mode
Officially supported browsers
Microsoft Edge 14+
Opera Mobile 12+
Chrome for Android 75+
Firefox for Android 67+
mackie100 - took some ideas from his app
Clover EFI dev team
Eric Slivka - new serial number
Virtual1 - new serial number
cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more
Micky1979 - Clover flying editor (Discontinued)
crusher. - Help with the ACPI Loader Mode flag
Download-Fritz - Help with the ACPI Loader Mode flag
Pavo - Ozmosis fields and values
stehor - Ozmosis fields and values
Sherlocks - General help and support
gujiangjiang - General help and support
Please let me know if i forgot you!
I'm trying to boot MacOS on a Chromebook without UEFI.
I'm stuck at getting the bootloader (Chameleon/Clover) to work.
My setup / context:
I have an Acer Chromebook Spin 13.
2 x USB-C
1 x USB-A 3.0
No USB A 2.0 (I've read that Clover has problems with USB 3.0)
There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS.
Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related.
This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options.
If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.
What I've tried so far:
Only selected setting was "Install chameleon on the chosen path", rest was unselected.
1 - Install chameleon first without restoring the basesystem:
> boot0: GPT
> boot0: done
(hangs; pressing power button once shuts down
Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
2 - Install Chameleon after restoring the base system:
> boot0: GPT
> boot0: GPT
> boot0: doneboot1: /boot <- Exactly like that, no line break in between
(hangs; pressing power button once shuts down)
I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
I tried multiple settings and configurations, but all of them boiled down to either one of these.
1 - Doesn't do anything, just hangs at "Booting from usb..."
2 - Boots into the blue/grey mode as shown in the attached images.
According to MrChromebox, this could be an old Tianocore DUET
It doesn't detect anything (cpu frequency, ram, partitions or disks)
I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
A few questions that came up:
Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer?
What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET
Where does it come from? Clover? The mainboard itself?
Why does the blue/grey thing not detect my processor frequency or any partitions/drives?
Can I use some sort of DUET bootloader to chainload Clover?
If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
Buongiorno, ho da poco messo a posto quasi tutto sulla mia prima configurazione hackintosh che va benissimo. In questi giorni è apparso l'aggiornamento di sicurezza di High Sierra come da titolo e me lo ha scaricato ma prima di partire con l'installazione vorrei avere delle delucidazioni riguardo agli aggiornamenti in generale soprattutto ai minor, per ora non ho bisogno di aggiornare a Mojave.
Si corrono dei rischi ad eseguire aggiornamenti di questo tipo (sicurezza come in questo caso) o ad esempio a versioni piu nuove dello stesso sistema MacOS? Se sì quali sono e come si prevengono?
Non vorrei ritrovarmi a dover re installare tutto formattando il disco partendo da zero. Qualche tempo fa ad mio amico succedeva che il disco veniva crittografato con "Filevault" e diventava inaccessibile, questo dopo un minor update, al che ha dovuto ricominciare da 0. Cos'è il Filevault? Potrebbe capitare questo anche a me? Vorrei sapere tutto prima di andare a fare delle minchiate.
Grazie in anticipo a chi vorrà e avrà la pazienza aiutarmi.