Jump to content
fantomas1

Apple unveils "macOS Sierra"

408 posts in this topic

Recommended Posts

Advertisement

Working on my Asus H97M-E/CSM mobo. Problem is how to install Apps not downloaded from App Store as the option "Install from anywhere" is no longer available. Any workaround?

Share this post


Link to post
Share on other sites

Anyone here could test the old AppleHDA Patcher

I made a small change in the script bcc9 for
to support 10.12.

I got this , (ALC892

EDIT : I got sound using  AppleALC.kext from page 8 but no Mic

Number found where operator expected at ./patch-hda.pl line 147, near "0x11d4198b"
	(Missing semicolon on previous line?)
syntax error at ./patch-hda.pl line 147, near "0x11d4198b"
Execution of ./patch-hda.pl aborted due to compilation errors.
Copying README file
Creating zip file
Done.

Share this post


Link to post
Share on other sites

 

I got this , (ALC892

EDIT : I got sound using  AppleALC.kext from page 8 but no Mic

Number found where operator expected at ./patch-hda.pl line 147, near "0x11d4198b"
	(Missing semicolon on previous line?)
syntax error at ./patch-hda.pl line 147, near "0x11d4198b"
Execution of ./patch-hda.pl aborted due to compilation errors.
Copying README file
Creating zip file
Done.

@Mirone you are missing comma at line 146 

post-1425204-0-41615400-1466069543_thumb.png

so i added and updated your app AppleHDAPatcher.zip

 

@ham4ever try this 

Share this post


Link to post
Share on other sites

@Mirone you are missing comma at line 146 

attachicon.gifScreen Shot 2016-06-16 at 3.01.37 PM.png

so i added and updated your app attachicon.gifAppleHDAPatcher.zip

 

@ham4ever try this 

but I figured it out yesterday but was already late at night,
why I did check the ID's
in binary of AppleHDA using a Hex editor
on windows ({censored}) program.

Share this post


Link to post
Share on other sites

 

but I figured it out yesterday but was already late at night,
why I did check the ID's
in binary of AppleHDA using a Hex editor
on windows ({censored}) program.

 

that's why i hate windows 

i can confirm that binary patching is doing good as required , i check in using HexFiend ..

Share this post


Link to post
Share on other sites

that's why i hate windows 

i can confirm that binary patching is doing good as required , i check in using HexFiend ..

you come to test the old AppleHDA Patcher?
an update of the new version made by me and Micky this
for coming.

Share this post


Link to post
Share on other sites

Here it is guys, a working VoodooPS2Controller kext, RM patched it yesterday for Sierra as it seems, I'm using it atm (still need to use it on a clean OS as the AppleSmartTouchpad did some stuff, but it works). 

VoodooPS2Controller.kext.zip

 

https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads

Check here

Share this post


Link to post
Share on other sites

New VoodooPS2 works well. No more panic and no more jumpy mouse pointer with the other kext. Nice job RehabMan :)

 

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

Share this post


Link to post
Share on other sites

New VoodooPS2 works well. No more panic and no more jumpy mouse pointer with the other kext. Nice job RehabMan :)

 

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

I can confirm that too!

Share this post


Link to post
Share on other sites

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

 

And now that we're slowing checking things off the list, is there a fix for the garbled bootscreen with HD4000? The old IOGraphicsFamily patch isn't working here for Sierra.

Share this post


Link to post
Share on other sites

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

Mostly, but I think they mostly made it for their devices, I dont think apple would let this pass by even on DP1 release, so it should be on our part (maybe apple is making devices limitations now, locking the OS even more?)

 

Anyway, I found that the driver that I built from RM sources have a problem (bug?): I cannot make key combination that involves numbers (like Screenshot combination keys) and it outputs a letter for some reason.

 

---later this day---

 

Guys, why can't I rebuild caches on this thing! I need CodecCommander to work!

Share this post


Link to post
Share on other sites

Seems the Trackpad prefpane is broken in Sierra because it still doesn't load. In the Console there seems to be a conflict between it and the Mouse one.

Post output of console that shows this 'conflict'...

 

It may be time to create a special prefpane...

I tried moving the Mouse prefpane out of it's folder (and deleting the prefpane cache) and the Trackpad pane still doesn't load. The warning is gone from the Console though. Guess they'll fix it later, assuming it's a bug and not something to do with our trackpads. I wonder if it's broken on Macs as well?

It could be they removed support for the old trackpad prefpane, as it seems they plan on removing support for older Macs in this release...

Share this post


Link to post
Share on other sites

Anyway, I found that the driver that I built from RM sources have a problem (bug?): I cannot make key combination that involves numbers (like Screenshot combination keys) and it outputs a letter for some reason.

My guess is you're pressing number keys along with the ALT key, and you have the debug version installed.

 

It is not a bug.. it is a feature (it is for typing ADB codes directly for testing). Install Release kext.

Hey my IDT92HD87B1.zip not works :(

If you're patching 0x11d4198b, you need to zero out codec 0x11d4198a.

Share this post


Link to post
Share on other sites

My guess is you're pressing number keys along with the ALT key, and you have the debug version installed.

 

It is not a bug.. it is a feature (it is for typing ADB codes directly for testing). Install Release kext.

 

If you're patching 0x11d4198b, you need to zero out codec 0x11d4198a.

Woah! totally forgot that, but I'm building it from source, I only get the Debug version for some reason, What should I do to get the Release one?

 

EDIT: Just checked your Bitbucket, a new version has been released!

Share this post


Link to post
Share on other sites

Post output of console that shows this 'conflict'...

Jun 16 13:35:54 Sammy System Preferences[402]: objc[402]: Class AssetQuery is implemented in both /System/Library/PreferencePanes/Trackpad.prefPane/Contents/MacOS/Trackpad (0x109460090) and /System/Library/PreferencePanes/Mouse.prefPane/Contents/MacOS/Mouse (0x107b41310). One of the two will be used. Which one is undefined.
Jun 16 13:35:54 Sammy System Preferences[402]: objc[402]: Class BTDeviceManager is implemented in both /System/Library/PreferencePanes/Trackpad.prefPane/Contents/MacOS/Trackpad (0x109460770) and /System/Library/PreferencePanes/Mouse.prefPane/Contents/MacOS/Mouse (0x107b41720). One of the two will be used. Which one is undefined.

Share this post


Link to post
Share on other sites

Yes.

I want to confirm something: The volume buttons work on 10.11 but not on 10.12, I'm using the latest kext you provided on both. Can you check that up?

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 plasticworld
      After a long run, I successfully upgraded High Sierra to mojave 10.14 on an intel 5 series chipset MotherBoard.
       
      MotherBoard: H55ms2
      RAM: 6GB
      GPU1: Saphire AMD RX 460
      GPU2: Nvidia 8400GS
      Storage: 500 GB HDD WD Green.
       
      The requirement:
      1) macOS pre mojave.
      2) macOS mojave installer from Apple store.
      3) Empty partition or USB to upgrade from.
      4) Un-mout all unused dmgs.
      5) GPT/GUID HDD.
       
      HOWOT:
      1) Prepare an empty partition or USB with at least 6 GB.
      2) Format the partition or USB with GUID partition table and HFS+ partition with a name BootablePartition.
      3) Go to /Application/Install macOS Mojave.app.
      4) Show Package Contents.
      5) Go to Contents/SharedSupport you will find BaseSystem.dmg.
      6) Double click on BaseSystem.dmg to mount.
      7) From Disk Utilty click on your partition or the USB that you prepared from number (2).
      8) Click on restore, and chose OS X Base System (BaseSystem.dmg image), then restore it to that partition or USB.
      9) After restoring rename the partition back to BootablePartition.
      9) Run this command:
      rm -rfv /Volumes/BootablePartition/System/Installation/Packages 10) Create a new folder instead of the broken link and name it Packages, run this command:
      mkdir -v /Volumes/BootablePartition/System/Installation/Packages 11) Go back to /Application/Install macOS Mojave.app and repeat number 2.
      12) Go to Contents/SharedSupport you will find InstallESD.dmg.
      13) Mount InstallESD.dmg.
      14) Run this command:
      cp -v /Volumes/InstallESD/Packages/OSInstall.mpkg /Volumes/BootablePartition/System/Installation/Packages/ 15) Download the latest clover from https://sourceforge.net/projects/cloverefiboot/
      16) Install clover on your USB BootablePartition or in a different USB to boot from it. delete all your CLOVER/kext/10.xx and keep others, make sure you don't have any extra kext rather than FakeSMC.kext in the other folder.
      in my case I used FakeSMC.kext and my lan kext RealtekRTL8111.kext.
      17) known Problems in my build: 
      If I updated directly from the apple store the installer in clover will boot with a cross circle sign.
      The FIX is to add this to Clover KextToPatch Thanks to @sunKi http://www.insanelymac.com/forum/topic/327488-macos-high-sierra-final-release-is-out-17a365/page-10?do=findComment&comment=2505086 this fix is still working for me in mojave.
      <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>fix IO error ICH10 for 10.13, credit SunKi</string> <key>Disabled</key> <false/> <key>Find</key> <data> RYX2D5XCiciD4P5mhcl4D4TSdQs= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> iciD4P5mhckPmMFBCMyQkJCQdQs= </data> </dict> <dict> <key>Comment</key> <string>fix hotplug ICH10 for 10.13, credit SunKi</string> <key>Disabled</key> <false/> <key>Find</key> <data> icglQGACAD1AIAAAdQyB4b9///+Ji1EBAAA= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> kJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJA= </data> </dict> <dict> <key>Comment</key> <string>External icons patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> 18) make sure you have apfs.efi copy it from /Volumes/BootablePartition/usr/standalone/i386/apfs.efi to your EFI/CLOVER/drivers64/ and EFI/CLOVER/drivers64UEFI/.
      19) SMBIOS mac model that I use is iMac13,2.
      20) Go to /Application/Install macOS Mojave.app click on it and chose to install to your macOS Mojave partition.
      21) Reboot.
      22) From clover chose BootablePartion.
      23) If everything is okie BootablePartition will boot to install macOS mojave, wait wait wait till it finish it might take to 1 hour just wait it will reach the auto reboot soon .
      24) Boot to your old macOS Hight Sierra that will be your mojave partition now and enjoy.
       
      POST Install:
      1) audio: 
      a) Download Lilu.kext and AppleALC.kext or build them from source (which I did).
      b) place them in your /EFI/CLOVER/kext/others/
      c) add your audio layout in clover/Devices dict options in my case it's ALC888B which has the layout of 1:
      <key>Audio</key> <dict> <key>Inject</key> <string>1</string> </dict> d) I had to add beta args to clover/Boot dict, argument (-lilubeta -alcbeta):
       
      <key>Arguments</key> <string>-lilubeta -alcbeta</string> 2) Add number 14 KextsToPath array to your clover as well.

      Anything else is working for me I didn't need any extra clover kext so far, I tried whatevergreen.kext to fire up my rx 460 without the helper card but no success, So I am just sticking with booting from Nvidia as a first GPU from my motherboard configuration then swap the cables after choosing my macOS partion from clover.
       
      After upgrading my HFS+ High Sierra partition converted to APFS, no know problem so far.

      Happy build and more info about the partitioning method with a more detailed instructions in this post that I used to update my Sierra to High Sierra
       
      Special thanks to crazybirdy, sunKi and all of you out there that make this happens.
    • By NoEnd
      Hi team,
       
      I have tried to update to security update 2019-001 multiple time with no luck, today I've booted the update with -verbose and attached videos shows the details.
       
      Appreciate your help
       
      Thanks
      Untitled.mov
    • By JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
    • 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 fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider) New!
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
×