Jump to content
fusion71au

Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host

110 posts in this topic

Recommended Posts

Advertisement

Hi Guys,

 

Those having problems with the install hanging after DSMOS has arrived can try resetting/changing their vbox configuration:

 

To reset/remove a CPUID from your configuration:

1.  Shutdown all VirtualBox windows and the VirtualBox Program.

2.  Edit the <vmname>.vbox file (located in C:\Users\[username]\Virtualbox VMs\<vmname>\ folder) with WordPad and remove the lines that read like

        <CpuIdTree>
          <CpuIdLeaf id="1" eax="67301" ebx="1050624" ecx="10019837" edx="3219913727"/>
        </CpuIdTree>

Spoofing alternative Mac Models/SMBIOSes using VBoxManage.exe

1.  Shutdown all VirtualBox windows and the VirtualBox Program.

2.  Reset your DmiSystemProduct to null...

cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" ""

3.  Enter a different DmiSystemProduct eg spoofing a Macmini6,2 works with El Capitan running in VirtualBox on my laptop XPS M1530. 

VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

4.  You may or may not need to change the CPUID presented to your virtual machine (for my system, I did not need to enter a CPUID:  Try without the CPUID line, then with the line if there is a problem - see @clauden's post#21 above for some alternative CPUIDs).

 

 

 

post-846696-0-25326500-1457866269_thumb.png

post-846696-0-20871300-1457866292_thumb.png

post-846696-0-70235500-1457866317_thumb.png

 

 

Share this post


Link to post
Share on other sites

This did it, thank you.  Once I setup those commands I booted and it came up to a grey screen and errored out.  Then I remove the virualbox harddrive, recreated it and started it back it.  And it installed.  Thank you, again.

Share this post


Link to post
Share on other sites
Hello, all! :)

I followed all instructions from original post, but I have the same issue as fusion71au (distorted sound). I've tried on both my laptop (ALC269VB), also on a desktop pc (ALC662), but I have the same issue.

 

I've tried different stuff:

- AppleHDA Patcher (I don't think I'm quite sure how to use that; I dragged the config.plist from EFI partition, selected corresponding driver from desktop/laptop and that was it; copied then the config.plist to EFI; restart)

- El Capitan Post Install Scripts

 

Did you figure out how to fix it?

 

Thank you in advance for your attention :)

 

P.S. fusion7au can you delete some messages from your inbox so that you can be contacted?

Edited by Micky1979
Tonymac stuff not allowed

Share this post


Link to post
Share on other sites

Hi thanks a lot all is ok 

 

I install on ubuntu X64 and all is ok 

 

But just one problem

 

How can i do for use icloud ... 

 

I have a macbook pro so i wan't to use my icloud account

 

I try to install chameleon for active ethernetbuild on virtualbox but error

 

Do you have a solution 

 

Thanks a lot

Share this post


Link to post
Share on other sites

As first timer, considering trying this to do multiplatform development, I was hoping to understand the relationship between the the machine on which the .iso is created and the cpuid settings for the VM.

 

Is the iso somehow specific for the machine on which it is created? If so, does using Intel's MacCPUID application help with deciding what to settings to use for the VM?

 

Or are the CPUID settings determined by the capabilities of the host machine for the VM?

Share this post


Link to post
Share on other sites

I'm having trouble creating the .iso. When I run CECI.tool everything looks normal until the end when it says "hdiutil: convert failed - No space left on device"

 

I'm doing this from a VM on Virtualbox running Yosemite. Thanks all!

Share this post


Link to post
Share on other sites

Thank you, fusion71au. This is a wonderful solution. Everything goes well according the steps for me, until launching the virtual machine guest to start the OSX installation. After some outputs, installation program keep to print below message for ever.

 

The host is Win7 sp1 64, Guest is OS X 11.10 downloading from app store and creating iso on a Mac, Virtual Box version is 5.0.10.

 

I am a beginner to OS X, fusion71au or any guru else could help this ? Thank you!

 

post-1699091-0-06449200-1460220880_thumb.png

 

Share this post


Link to post
Share on other sites

 

Thank you, fusion71au. This is a wonderful solution. Everything goes well according the steps for me, until launching the virtual machine guest to start the OSX installation. After some outputs, installation program keep to print below message for ever.

 

The host is Win7 sp1 64, Guest is OS X 11.10 downloading from app store and creating iso on a Mac, Virtual Box version is 5.0.10.

 

I am a beginner to OS X, fusion71au or any guru else could help this ? Thank you!

 

 

 

This is because the "Orable VM Virtual Box Manager" program was not closed when I ran "patching El Capitan vbox configuration file with DMI Settings" commands. When running patching commands, not only El_Capitan VM client but also "Orable VM Virtual Box Manager" program should be closed.

Share this post


Link to post
Share on other sites

UPDATE: Fixed! Read description below to find out what kind of problem did I have and read EDIT 2 with a fix (sort of).

 

Hey there, fusiou71au!

 

I'm fairly new here, but I tried following your guide step-by-step and I managed to get some results! The system is working, but...

 

I'm having weird crashes. They seem to be random, but I found out they occur mostly during "new" operations, like opening a new window, launching a project (in xcode), trying to launch simulator, or even starting to scroll in the window. In most cases I'm not receiving any error messages, just a black screen with console prompt. Or like the screen attached. After a minute, the login screen appears and everything is rolled back to the moment before the crash and I can continue my work, but the crashes are often and I'd rather not work with them.

 

I've prepared the ISO couple of days ago, with El Capitan on version 10.11.4. The same issues seem to be happening to my friend that installed from the same ISO.

 

Is it an issue with the way I prepared the ISO? I did it on my hackintosh yosemite virtual machine (from a guide I found on google) if it matters. If you'd like to get a hand on the ISO in talks, I can PM it to you (I'd rather not give it to public).

 

Or maybe it is not an issue with installation (or preparation), but with my configuration? I think I followed every step here.

 

EDIT: Also another file, with some more error logs that - unfortunatelly - do not give me any hints on where to go any further.

 

EDIT2: I think I might have fixed the issue. It was simply a matter of reinstalling the system with different virtualbox settings. For reference, I'm on

Intel i5 6400

Geforce GTX 970

8GB ram DDR4

 

And virtualbox flags I used:

cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro8,2"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
VBoxManage setextradata "El_Capitan" "VBoxInternal2/EfiGopMode" 3
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc."
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B"

post-1704209-0-29655700-1461275963_thumb.png

post-1704209-0-45909900-1461277369_thumb.png

Share this post


Link to post
Share on other sites

So, I ran through this last night, and it seemed to install fine. I'm able to get in to OS X and do OS X type things, however, I noticed one odd issue. When looking at System Profiler, It's showing I only have 3MB of VRAM, when I set it up to have 128MB (and hope to tweak it further to allow 512). Anyone have any thoughts on this? Thanks!

Share this post


Link to post
Share on other sites

Hi,

 

i am trying to run El Capitan on an Intel Xeon E3-1231 v3 Haswell with 4x3,4 Ghz and an ASRock Fatal1ty H97 Performance Board with 8GB Ram.

I just used this config:

 

VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac14,2"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-27ADBB7B4CEE8E61"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal©AppleComputerInc"
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1

 

But after Installation i set a User and Password but if i enter the Password in the login screen i get a black screen and then back again the login screen??

 

Can someone help me with this?

 

Cu kami

Share this post


Link to post
Share on other sites

Thanks for the great guide! I got this working working on a Lenovo W520.

 

However, it is rather slow. My W520 is running on a Sandy Bridge Intel Core i7 2820QM with 8BG of ram. I followed the tutorial to the T, so I didn't have to spoof or change anything. During the initial installation, I was watching the output, and there were some errors there, but it installed all the way.

 

My question is, is there anyway to speed it up. It's just laggy, and takes a while to open things, and search for things on the web. Is this normal running El Capitan in virtual box?

 

Thanks again for the tutorial. This is pretty sweet!

Share this post


Link to post
Share on other sites

Hi, I am trying to set custom video mode for ElCapitan running in VirtualBox as a gues (host machine is Ubuntu Linux - by the way, the whole setup is working great).

 

I am trying to set CustomVideoMode as to 1920x1800.

 

In OS X I disabled System Integrity Protection (see guide here: http://anadoxin.org/blog/disabling-system-integrity-protection-from-guest-el-capitan-under-virtualbox-5.html)

 

After that I was able to edit file: /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

 

It looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Graphics Mode</key>
        <string>1920x1080x32</string>

        <key>Kernel Flags</key>
        <string>"Graphics Mode"="1920x1080x32"</string>
</dict>
</plist>

Shut down the virtual machine and invoke the following command in Ubuntu host:

VBoxManage setextradata "El_Capitan" "CustomVideoMode1" "1920x1080x32"

After booting the virtual machine with OS X, custom video mode is not working... any idea what is wrong?

Share this post


Link to post
Share on other sites

The problem is that you need a functioning Mac in order to create the install media. What if you do not have one? Is there a way to create install media using just a Windows PC?

 

Sent from my SM-T810 using Tapatalk

Share this post


Link to post
Share on other sites

I dont think so. Anyway, you need iStore access to download El Capitan install App. So yes, I am pretty sure having a Mac is a must.

Share this post


Link to post
Share on other sites

I'm having trouble creating the .iso. When I run CECI.tool everything looks normal until the end when it says "hdiutil: convert failed - No space left on device"

 

I'm doing this from a VM on Virtualbox running Yosemite. Thanks all!

 

That simply means that your VirtualBox partition for OS X is too small.

 

You have to either resize the partition (but I don't know how to resize OS X partition after disk resize) or create another larger hard disk and add it to your Yosemite VM, then format the disk under OS X and clone the system to the new disk with Carbon Copy Cloner.

 After that you'll have to swap the first hard disk with the new one and you should have enough room to work with.

 

 Something else, for the resolution problem I tried the VBoxManage setextradata "OS X VM" "VBoxInternal2/EfiGopMode" N (Where N can be one of 0,1,2,3,4,5), but didn't work for me.

 

 Until I tried the same line but without quotes arround VBoxInternal2/EfiGopMode and assuring that capitalization was respected and this time it worked.

Share this post


Link to post
Share on other sites

For me VBoxManage setextradata "OS X VM" "VBoxInternal2/EfiGopMode" N works fine, but custom resolution (for widescreen) is not working, However, it seems there is a problem with ElCapitan, because VmWare has similar problems.

Share this post


Link to post
Share on other sites

Hi,

 

anyone here how can help me with my login problem? I described it in Post #39.

 

Thanks a lot.

 

Cu kami

Share this post


Link to post
Share on other sites

Hi,

 

anyone here how can help me with my login problem? I described it in Post #39.

 

Thanks a lot.

 

Cu kami

Hi Kami

 

If your problem looks similarly to the one I described in post #37 then you should simply follow my suggestions in that post.

 

Briefly speaking: try different configurations and reinstall your machine. It helped me.

 

 

The problem is that you need a functioning Mac in order to create the install media. What if you do not have one? Is there a way to create install media using just a Windows PC?

 

Sent from my SM-T810 using Tapatalk

 

I've created such media for me and my friends from school, if mega is still working, this will be the link with it:

 

https://mega.nz/#!WxtDHa7I!USd5qmnEParmZKR_MLzP0p11-Xje_lJZ4-BbUOQQwOE

 

PS. Don't abuse, I'd rather keep this working at least until next semester.

 

Share this post


Link to post
Share on other sites

hi,

 

tried the howto step by step... but my VM got into state "stuck" ... the log is attached here: https://bpaste.net/show/6ddc19b5c448

 

my setup is bit more complicated... running Freenas ; virtualbox inside the jail ... and then VM for osx... any idea? is it possible to make it work in such an environment?

 

 

thank you!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Teress
      In this Hackintosh tutorial I'm covering all aspects of Dual Boot Windows and macOS. How to avoid problems, best settings, Pros and Cons.
       
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By tbianco
      Ho comprato da poco un Acer Aspire 5750G e girando su internet ho trovato la cartella efi che garantiva quasi tutto funzionante perfino il wifi (https://github.com/zipippino/HighSierraAspire5750G).
      Allora felicissimo installo macOS e a parte incappare in errori stupidi, riesco a fare tutto, ma quando sono riuscito ad installare clover Legacy e sostituendo la roba con la 'mia' efi clover si avvia ma macOS no, semplicemente non carica (si nota anche pk la spia dell'hdd che dice se è in attivitá è spenta.
      Qualcuno può aiutarmi?
    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not get iMessage to work properly. It worked precisely once, on my first installation attempt. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - if you can get NVRAM/PRAM working properly on this hardware, please do edit the config as you see fit.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

×