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!
Salve a tutti,
premetto di essere nuovo in questo mondo dell'hackintosh e, come avrete letto dal titolo, ho un problema molto strano al momento dell'installazione.
Creo la chiavetta usb, metto tutti i kext, driver eccetera da un vecchio MacBook Pro ma, quando la vado a mettere sul pc e provo a bootare, Clover non mi trova l'os. In alto c'è lo stemma di clover, in basso i settings ma dove dovrebbero esserci i SO non c'è nulla.
Nel pc avevo ssd e hardest per windows ma ho pensato di toglierli per non creare conflitti con un nuovo ssd da 120gb comprato apposta per il Mac OS.
La penna usb ho provato a farla in tutti i modi che ho trovato e che mi hanno consigliato: sia con Tino, sia con terminale scrivendo il codice. Ho usato clover per selezionare kext e drivers ma nulla.
Questa è la guida che ho seguito inizialmente https://hackintosher.com/builds/asrock-z370-extreme4-pro4-hackintosh-high-sierra-guide/
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!
Assemblato da me con le seguenti componenti tutte acquistate rispettando la lista compatibilità.
Usato poco, principalmente per qualche ora serale tornando a casa dal lavoro per video editing (fluido in 4K con Premiere Pro).
Mai un problema, sostituita pasta termica 2 mesi fa. Sempre tenuto in condizioni di pulizia interna. Vendo per cambio lavoro.