Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,529 posts in this topic

Recommended Posts

@FungFlex - what is your T420 model? do you have high-res or low-res monitor? if you have low-res don't use DualLink=1. which dsdt are using. one has Dual Link on and one doesn't.

Share this post


Link to post
Share on other sites
Advertisement

@tluck-

I'm creating the USB for the final Mavericks release using your latest guide on post #486, but the USB doesn't seem to be bootable...

Am I missing something?

 

Thanks,

aj

Share this post


Link to post
Share on other sites

{censored}. sorry all. I completely forgot to mention (and update the zip file) that I replaced VboxHFS-64.efi with HFSPlus.efi from here:

 

https://github.com/STLVNUB/CloverGrower/blob/master/Files/HFSPlus/x64/HFSPlus.efi

 

View Raw

 

as someone pointed out it seems to be able to read the install bundles better. and it does!

Share this post


Link to post
Share on other sites

Hi, the link for the bios does not work, it's maxed out. Can you attach it here?

Thanks,

AJ

 

the link appears to be broken again. could someone post a new one? thanks.

 

edit: nevermind, I found it had been reposted on the original forum in a different reply: http://forums.mydigitallife.info/archive/index.php/t-5866-p-120.html

Edited by Manwe150

Share this post


Link to post
Share on other sites

i can't get any osx to work with my t420 (type 4180-b95 has nvs 4200m) and I'm not sure where to start.

 

ive tired lion, mountain lion and mavericks. i preferably want mavericks but will start where i need to, i even tried pulling the HD out of a macbook and booting that

 

currently when i try to boot the usb installer for any version of the os i made (which worked on a real mac at least 10.7 and 10.9 did) it does what it did in this video

My t420 Video also if i back out of that black screen wight eh small dash if it lets me it goes back to clover but it is frozen most of the time

when i try to boot the lion from a real mac i get this version of Mac OS X is not supported on this platform

reason: 4180b95

but when i boot the recovery partition it goes to  a white screen with a beach ball after verbose mode but if i try with the -x flag it doesn't even try to boot it goes to saying i can't find the mach_kernel
id obviously prefer a fresh install by this or another guide but i seem to not have any luck with it


idea's?

thanks

Share this post


Link to post
Share on other sites

@anarchy99

 

i would turn off NVS for now.

 

Note: a vanilla mac installer needs FakeSMC - same for the HD from a real mac. these will not boot up unless you inject FakeSMC (and  VoodooPS2controller unless you have USB keyboard/mouse).

 

are you using the clover config from my zip for your EFI? what EFI drivers do you have installed. it acts like its not even reading the USB? canyou may need HFSplus.efi to boot from recoveryHD. 

Share this post


Link to post
Share on other sites

Using your clover config I was able to boot and install Mavericks YAY!!

I did have to disable the discete graphics :-(

So far audio seems to work, it sees ethernet but doesn't text any cabel and no wifi

 

I installed a Dell 1390 wireless card that I stripped out of an old hackintosh into the bottom mini PCI-E slots and it doesn't seem to detect at all

does anyone know how to get that working?

I read somewhere that someone said it was for msata and USB only, but the t420 hardware maintenance manual refers to it as 1070 PCI Express mini card for wireless WAN

If I could add rather use that  bottom slot then have to buy a mini PCI half card or whatever it's called for under the keyboard

@anarchy99

 

i would turn off NVS for now.

 

Note: a vanilla mac installer needs FakeSMC - same for the HD from a real mac. these will not boot up unless you inject FakeSMC (and  VoodooPS2controller unless you have USB keyboard/mouse).

 

are you using the clover config from my zip for your EFI? what EFI drivers do you have installed. it acts like its not even reading the USB? canyou may need HFSplus.efi to boot from recoveryHD. 

Share this post


Link to post
Share on other sites

@anarch99 - you will get ethernet if you installed the AppleIntelE1000e kext ... but wifi AFAIK is only works with modded bios and then you replace the intel wifi with the mini express card. the  bottom slots will not work for wifi. for wifi, i use a USB wifi.

Share this post


Link to post
Share on other sites

Ok all, well after some tricky issues I am back on Mavericks and able to boot but in only one of two scenarios:

 

1) Boot directly to Mac partition on UEFI Clover boot loader and deal with quadrant display issue

 

2) Boot off old formatted drive with Clover r1625 which fixes display and breaks sound

 

I am having a hell of a hard time customizing things. After I have installed Clover and I restart the computer should I still see the ESP partition? This consistently disappears the moment I restart my computer.  Additionally if I try to select the EFI partition on the Clover boot screen it just flashes.

 

Back on Mountain Lion my startup would be selecting EFI than my Mac drive and it worked great but no luck.

 

Finally, I’ve seen totally mixed answers on where I should find my product ID.  Using various methods it seems like my DisplayProductID is 738 but I’m not even sure that is the right number I should be renaming the OEM folder too? I've included below stuff I pull from when I did the ioreg -l:

"IODisplayEDID" = <00ffffffffffff0030e4e2020000000000140103801f11780a43459759578e28215054000000010101010101010101010101010101018025408060841a303020350036ae10000019000000000000000000000000000000000000000000fe004c4720446973706c61790a2020000000fe004c503134305744322d544c42310038

"DisplayProductID" = 738
"DisplayVendorID" = 12516
"IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e2"

To answer TLuck’s question, yes low res model with i5 2.49ghz

Share this post


Link to post
Share on other sites

@FungFlex - 

 

what DSDT are you using? if you are booting using the EFI i posted - there are 2 configs and matching DSDTs. since you are low-res, you should be using the Low-Res 4236Y33 version.  

 

the EDID shown above is consistent with the the High-Res version 1600x900 LCD

 

the EFI partition (ESP) is automatically mounted by a clover utility. this is convenience for you.

Share this post


Link to post
Share on other sites

@FungFlex - 

 

what DSDT are you using? if you are booting using the EFI i posted - there are 2 configs and matching DSDTs. since you are low-res, you should be using the Low-Res 4236Y33 version.  

 

the EDID shown above is consistent with the the High-Res version 1600x900 LCD

 

the EFI partition (ESP) is automatically mounted by a clover utility. this is convenience for you.

I am using the 33 version as I believe I have the low-res version. The EDID I ran was done while I was stuck in quadrant mode if that maybe explains why it would show the 1600x900 one. Not sure how to confirm to be honest, this computer barely ever ran windows :-)

 

I guess my confusion is, when I install Clover the parition named "EFI" appears (although only one time was it named "ESP") when that happens I drag your zip file contents into the Clover/Boot folders and when I restart the computer that "EFI" partition is gone. Is this normal?

Also, on the clover boot menu, if everything is installed correctly what do you select when booting up?

 

Finally, the folder I am supposed to rename is "4236Y33" correct? The question is, how do I know what to rename it properly? Where do I find the appropriate string?

Share this post


Link to post
Share on other sites

@FungFlex - 

 

use the console app to look at the clover boot.log - it will show you the productID.  or use the Clover Options Menu to get the Product ID - forget where exactly. thats the name of your OEM folder. should match whats on your label on the bottom of system.

 

there is a dsdt.aml in /EFI/Clover/ACPI/patched - this is for high-res - same as the one in OEM/4236AT9/ACPI/patched. thats why you are getting 4 panels. this dsdt has duallink=1 and injects a 1600x900 EDID. replace it with the low-res one. 

 

when you rename OEM/4326Y33 to match your ID, it will use the stuff in this folder vs the top level. 

 

the Installer mounts the ESP on /Volumes/ESP. there is an option to have clover utility mount the ESP upon boot up. it mount it at /Volumes/EFI (these are installed optionally by the Clover .pkg installer. 

 

when you boot, select your OSX partition. 

Share this post


Link to post
Share on other sites

So happy I could kiss you! Although I'm probably not your type ;-)

 

Everything is working perfectly, I'm running Mavericks and everything is fully functional (sound and display! hooray!)  Only outstanding question is previously on 10.8 I booted with Kogen's custom clover build and it must have injected a different trackpad kext as I was previously able to do some 3 fingered gestures for mission control and switching between spaces. These seem to be broken, is that a 10.9 thing or should I pull a kext from his bundle?

 

Having some minor issues with iMessage but I haven't done anywhere near enough troubleshooting on my end to diagnose yet.

Share this post


Link to post
Share on other sites

Following the instructions for 10.9 install from post #486:

 

 

 

  • for 10.9 install USB
    1. Download from App Store (puts in /Applications
    2. Partition 8GB USB as GUID (use option menu to) - title the partition USB
    3. run this command:
      sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Mavericks.app —nointeraction
       
    4. manually mount ESP of USB and copy the clover EFI folder onto USB ESP (assuming the USB is disk2)
      mkdir /Volumes/ESP-USB
      mount -t msdos /dev/disk2s1 /Volumes/ESP-USB
       
    5. rename OEM OEM.NU for USB installer so it will use top level config.plist that will inject kexts
    6. Boot and install OSX!

 

When I boot into the installer I get the 4 quadrant screen deal. Searching around this same topic I saw to go into config.plist (in this case top-level) and set Dual Link to 0 which I have done but still get the split screens. I've tried booting into safe mode but it only causes an error and reboots before it even gets to the installer GUI. What else can I adjust? I'll try installing anyway since the fix will need to happen when I am done with the vanilla install as well.

 

Thanks,

 

Anthony

 

machine type - 4179W1F

Share this post


Link to post
Share on other sites

Following the instructions for 10.9 install from post #486:

 

 

When I boot into the installer I get the 4 quadrant screen deal. Searching around this same topic I saw to go into config.plist (in this case top-level) and set Dual Link to 0 which I have done but still get the split screens. I've tried booting into safe mode but it only causes an error and reboots before it even gets to the installer GUI. What else can I adjust? I'll try installing anyway since the fix will need to happen when I am done with the vanilla install as well.

 

Thanks,

 

Anthony

 

machine type - 4179W1F

 

For me the full install happened in "quadrant" mode. It wasn't until install was fully done and I installed clover and fixed the OEM folder that quadrant display was fixed. 

Share this post


Link to post
Share on other sites

I guess i need to augment the instructions for better handling of low-res LCD configurations. for non 1600x900 LCD, to fix this quadrant thing on your USB installer and HD (until you rename the OEM folder to say 4179W1F for example), copy the generic (low-res) dsdt.aml into use on the top level. When there is folder in OEM that matches your product ID, clover will that instead. the

 

cd to your mounted ESP location 

cp EFI/CLOVER/OEM/4236Y33/ACPI/patched/dsdt.aml EFI/CLOVER/ACPI/patched/dsdt.aml

Share this post


Link to post
Share on other sites

i get stuck

 

stuck on IOBluetoothHCIController Missing Bluetooth Controller Transport

 

upgrade on 10.9

Did you try either disabling Bluetooth in the BIOS, or in my case I use a USB bluetooth adapter as my model didn't have it built in, I simply removed it during install.

Share this post


Link to post
Share on other sites

I guess i need to augment the instructions for better handling of low-res LCD configurations. for non 1600x900 LCD, to fix this quadrant thing on your USB installer and HD (until you rename the OEM folder to say 4179W1F for example), copy the generic (low-res) dsdt.aml into use on the top level. When there is folder in OEM that matches your product ID, clover will that instead. the

 

cd to your mounted ESP location 

cp EFI/CLOVER/OEM/4236Y33/ACPI/patched/dsdt.aml EFI/CLOVER/ACPI/patched/dsdt.aml

 

Thanks! Got myself booted up with sound and network and best of all no quadrants. Haven't tried much else yet.

Share this post


Link to post
Share on other sites

Did you try either disabling Bluetooth in the BIOS, or in my case I use a USB bluetooth adapter as my model didn't have it built in, I simply removed it during install.

Yes...im already disabling bluetooth in BIOS.

Share this post


Link to post
Share on other sites

Updated...
Finally work with 10.9.. :) thanks tulk..for your tutorial.
 
@Tulk, how to read OEM/4xxxx folder in ESP in 10.9 ? cause if im rename OEM.NU to OEM, the configuration clover will read in directory OEM/config.plist and make not boot properly ( stuck on IOBluetooth )

iMessage, iCloud etc using apple ID, not work... :( how to solve this problem ?

 

Updated this morning Oct 31st

 

iMessage, iCloud etch using apple ID work !!!

To do this:

 

1 Remove all Network interfaces

2 Remove /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

3 Reboot

4 Readd your Network Interface.

Share this post


Link to post
Share on other sites

the point of the OEM folder is to have a configuration for the HD versus USB. i use the top-level for USB installer - set to Inject Kexts. I make the assumption you will put the custom kexts in /S/L/E and not need to inject them. So If you have a high-res LCD rename 4236AT9 to match your ProductID.

 

if you have low-res LCD, then rename 4236Y33 to match your ProductID.

Share this post


Link to post
Share on other sites

Thanks to Kogen Mantis, Tluck et al. I now have a fully functional 10.8.5 install. No bluetooth but replaced the wifi card. I have never been happier. Thanks

Share this post


Link to post
Share on other sites

bluetooth should be fixable by either replacing or editing:

 

BroadcomBluetoothHostControllerUSBTransport.kext (v4.1.7 with patched Info.plist from 10.8.5) - adds ProductID 8575 to make BT work! Put/replace one in /S/L/E/IOBluetoothFamily.kext/Contents/PlugIns

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 Abhiabhash
      I have a lenovo laptop with pentium 2020M 2.4ghz with 4gb ddr3 ram intel graphics and 500gb wd hdd i wanted to install hackintosh on my pentium for editing purposes beacuse windows sucks so can you please tell me how can i install it and which version should i install
    • 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?

×