Jump to content
ErmaC

Clover Problems and Solutions

3,007 posts in this topic

Recommended Posts

Advertisement

This MSR is supported by Conroe and Penryn. Don't know about Dothan if it is still suitable for Hackintosh.

It will be better to implement safe_readMSR as Apple do but it requires to catch interrupts from unknown instructions.

OK, I'll set the condition to not use this MSR on Pentium-M.

Share this post


Link to post
Share on other sites

Some changes I made in my Clover fork on github...

 

First is to support VirtualSMC.kext same as FakeSMC.kext with respect to InjectKexts=Detect.

Simple change to CheckForFakeSMC: https://github.com/RehabMan/Clover/commit/a12126299ba622290c7573e6200fadf3570dca24

 

Another is a critical fix for AcpiPatcher.c (broken somewhere between r4444 and r4658).

The bug: merged SSDTs (AutoMerge=true) are not being patched with patches in ACPI/DSDT/Patches.

These are the rules:

- any table that was merged (eg. replaced its original in the XSDT) via AutoMerge=true and correct naming shall be subject to ACPI/DSDT/Patches

- any add-on table (eg. added to the end of XSDT) because it could not be matched (naming/header) shall not be subject to ACPI/DSDT/Patches

 

The fix is here: https://github.com/RehabMan/Clover/commit/1b344368b9960904ad6e0eaf7ad0cd9500d60d85

 

Another change has to do with the installer defaults for drivers64/drivers64UEFI content.

For my build, decided it was better to set AptioMemoryFix, ApfsDriverLoader (and required AppleImageLoader), and AppleUiSupport (replaces many others) as default.

This one took me a couple of tries to get it completely right (misread XhciDxe as default... [only default for drivers64]):

https://github.com/RehabMan/Clover/commit/b81dd0cc7cadf826ef91ee29523a2cbfefd28814

https://github.com/RehabMan/Clover/commit/ca9576f33d5d2a186f9d32a11e12320eeaeb39cc

 

--

 

And another problem I noticed.  At first, I synced to latest svn, which at the time was r4672.

But there was a serious performance regression.  Navigating in the GUI is extremely laggy (less noticeable on a fast computer, but still noticeable).

So, I went back to r4658 before all the svg stuff was added.  No performance issue with r4658.

It appears the svg support causes a serious performance issue in the Clover GUI.

 

My current build is therefore based on svn r4658 until that performance regression is fixed in the svn Clover.

 

Share this post


Link to post
Share on other sites
10 hours ago, Slice said:

No, svg support is not currently used so it can't influence.

...

The performance regression is caused by one or more commits between r4658 and r4672.

I did not try to determine which (one or more) of the 14 is the cause.

Share this post


Link to post
Share on other sites
23 hours ago, Slice said:

No, svg support is not currently used so it can't influence.

About ACPI update I am on vacancy about 3 weeks so I propose someone else can commit. Sherlocks?

 

ACPI update was committed. 

since added AppleKeyFeeder as default, many users reported issues(GUI/Boot). can we consider to exclude AppleKeyFeeder from default(always checked when installing clover)?

Share this post


Link to post
Share on other sites
10 minutes ago, Sherlocks said:

 

ACPI update was committed. 

since added AppleKeyFeeder as default, many users reported issues(GUI/Boot). can we consider to exclude AppleKeyFeeder from default(always checked when installing clover)?

Causes issues with shell as well.

Share this post


Link to post
Share on other sites
35 minutes ago, Sherlocks said:

 

ACPI update was committed. 

since added AppleKeyFeeder as default, many users reported issues(GUI/Boot). can we consider to exclude AppleKeyFeeder from default(always checked when installing clover)?

Yes, it will be better all FV2 drivers to be not default.

Share this post


Link to post
Share on other sites
My keyboard is still not working on 4676 (if it was supposed to fix these issues)

 

Thanks

 

can you upload your uefi driver list both works and not work.

and try this

https://github.com/Dids/clover-builder/releases?after=v2.4k_r4667

r4664

r4665

 

we need to find commit that affected your keyboard

Share this post


Link to post
Share on other sites

Builds on github, nice!

I tried every build there, now 4677 and it seems to be working

The problem is the build on sf and my own build of 4676 (using latest xcode on hs and buildClover script)

The 4677 installer is weird, drivers in my efi folder were not selected and there s a new default hpfs driver.

What s the difference between this new driver and vboxHpfs?

Thanks

Share this post


Link to post
Share on other sites
Builds on github, nice!

I tried every build there, now 4677 and it seems to be working

The problem is the build on sf and my own build of 4676 (using latest xcode on hs and buildClover script)

The 4677 installer is weird, drivers in my efi folder were not selected and there s a new default hpfs driver.

What s the difference between this new driver and vboxHpfs?

Thanks
r4677 is not good. try to use 4678 and cleanup your driver64uefi and use drivers like before. i don't know why issue happen after i committed it on r4677. when i test it, it worked. but strangely package of installation is randomly failed. i returned buildpkg on r4678. i don't have time now. i have to sleep for tommorow. hope someone need to fix this issue.

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
8 hours ago, Sherlocks said:

 

ACPI update was committed. 

 

Awesome.  Thanks.

 

And I see a few other fixes in that commit that look like a good idea also.

 

Except for perhaps the extra SaveMergedXsdtEntrySize (will review).  If that was added just for the possibility of memory leak, please realize there are a ton of memory leaks in the ACPI patching code (but really, these memory amounts are small, and the leaks are 'one-time' so really don't matter much).  Fixing all the leaks would require some time to review all the code very carefully.

Share this post


Link to post
Share on other sites
Awesome.  Thanks.

 

And I see a few other fixes in that commit that look like a good idea also.

 

Except for perhaps the extra SaveMergedXsdtEntrySize (will review).  If that was added just for the possibility of memory leak, please realize there are a ton of memory leaks in the ACPI patching code (but really, these memory amounts are small, and the leaks are 'one-time' so really don't matter much).  Fixing all the leaks would require some time to review all the code very carefully.

i don't touch acpipatcher.c. i took your acpipatcher.c from your github. is there something wrong?

 

EDIT1. any idea for r4677?

package randomly has fail. i don't know why issue happen

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

Share this post


Link to post
Share on other sites
I'll take a look tonight if you want. Can you tell me if FV drivers are needed somehow for the iso image?
thanks vector. i didn't see iso image part. also i first hear iso image related in FV2 drivers


나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
6 minutes ago, Sherlocks said:

thanks vector. i didn't see iso image part. also i first hear iso image related in FV2 drivers


나의 LG-F800S 의 Tapatalk에서 보냄
 

Yep, Usually if you have an encrypted volume and a virtual disk-file is inside that disk is already protected. But if you export that disk it lost its protection. Basically I'm asking if anyone cares about that... i.e. the iso image will not load FV drivers and your VM should not use this technology.

EDIT

I'm at Job and can't check if the .iso image generated usually had FV drivers

Edited by vector sigma

Share this post


Link to post
Share on other sites
Yep, Usually if you have an encrypted volume and a virtual disk-file is inside that disk is already protected. But if you export that disk it lost its protection. Basically I'm asking if anyone cares about that... i.e. the iso image will not load FV drivers and your VM should not use this technology.
EDIT
I'm at Job and can't check if the .iso image generated usually had FV drivers
if you consider or improve it, it's good. now i have to sleep for job tommorow. thank you for info

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
49 minutes ago, Sherlocks said:

i don't touch acpipatcher.c. i took your acpipatcher.c from your github. is there something wrong?

Going from memory, the diffs on sourceforge looked more than my diffs.  Maybe there were further downsteam changes, ... I will review when I have time.

Share this post


Link to post
Share on other sites
Going from memory, the diffs on sourceforge looked more than my diffs.  Maybe there were further downsteam changes, ... I will review when I have time.
seems your acpipatcher.c has downsteam parts compared to clover acpipatcher.c in github. because i took only latest acpipatcher.c file from your github. please check your file.

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
2 hours ago, Sherlocks said:

seems your acpipatcher.c has downsteam parts compared to clover acpipatcher.c in github. because i took only latest acpipatcher.c file from your github. please check your file.

나의 LG-F800S 의 Tapatalk에서 보냄
 

 

My changes were based on AcpiPatcher.c from r4658.  I didn't go further with my svn sync due to the performance issues in later builds.

But yeah, I'll check what you have in a bit...

Share this post


Link to post
Share on other sites
On 9/27/2018 at 9:34 AM, RehabMan said:

 

My changes were based on AcpiPatcher.c from r4658.  I didn't go further with my svn sync due to the performance issues in later builds.

But yeah, I'll check what you have in a bit...

 

I put the difference back to the original state of the clover again before applying your file.

https://sourceforge.net/p/cloverefiboot/code/4682/

There is a definite difference between your file and an existing clover file.

Because I commit your file as it is. And once again I have received your file and compared it with the acpipatcher file of r4674, but there are other parts in addition to the commit like r4682 in your github.

also between r4658 and r4674, there was no change for acpipatcher file. you can see a history of commits

 

Edited by Sherlocks

Share this post


Link to post
Share on other sites

@Slice @vector sigma @savvas @Zenith432

I'm committing on Windows
If i commit the postinstall file in Windows, when you receive the source from sf on a Mac, the postinstall file does not work(exec feature was lost)

 and you are currently experiencing a package problem.
Currently I can not commit on the Mac. Please commit the postinstall file in the AppleUiSupport folder inside the package folder templete folder to the file I uploaded now.

 

I discovered this problem while debugging. Other files have never had a problem before. This problem occurred when only the postinstall file was committed in Windows.

 

contents of postinstall are same like before, i don't know why this issue happen. just need to remove and commit postinstall again. 

just found that postinstall committed in windows has white icon, postinstall commited in mac has black icon.

 

AppleUiSupport.zip

 

EDIT

between r4684 and r4685, i tried to delete postinstall and commit it again. but still postinstall file has white icon.

postinstall file needs to be commit in mac os.

189974135_2018-09-306_01_06.png.87c24b39633ac4313e359570a3d4fa53.png

509648450_2018-09-306_01_54.png.0bb517335f3027dd5008d21c1302a051.png

 

Edited by Sherlocks

Share this post


Link to post
Share on other sites
12 hours ago, Sherlocks said:

@Slice @vector sigma @savvas @Zenith432

I'm committing on Windows
If i commit the postinstall file in Windows, when you receive the source from sf on a Mac, the postinstall file does not work(exec feature was lost)

 and you are currently experiencing a package problem.
Currently I can not commit on the Mac. Please commit the postinstall file in the AppleUiSupport folder inside the package folder templete folder to the file I uploaded now.

 

I discovered this problem while debugging. Other files have never had a problem before. This problem occurred when only the postinstall file was committed in Windows.

 

contents of postinstall are same like before, i don't know why this issue happen. just need to remove and commit postinstall again. 

just found that postinstall committed in windows has white icon, postinstall commited in mac has black icon.

 

AppleUiSupport.zip

 

EDIT

between r4684 and r4685, i tried to delete postinstall and commit it again. but still postinstall file has white icon.

postinstall file needs to be commit in mac os.

189974135_2018-09-306_01_06.png.87c24b39633ac4313e359570a3d4fa53.png

509648450_2018-09-306_01_54.png.0bb517335f3027dd5008d21c1302a051.png

 

Hi Sherlocks, in Windows probably the difference is in the carriage return/line feed ('\r' vs '\n') as line separator.

I'm going to fix it

Share this post


Link to post
Share on other sites
40 minutes ago, vector sigma said:

Hi Sherlocks, in Windows probably the difference is in the carriage return/line feed ('\r' vs '\n') as line separator.

I'm going to fix it

 

@vector sigma

still it's not unix version. very strange in r4686. package still is broken.

1456567135_2018-09-3011_19_56.png.d512748821651c6c1080c2f417aec775.png

895678690_2018-09-3011_20_01.png.9e50c4d940b747bb15f85cc08d4aca88.png

 

i attached AppleUiSupport.zip file above. this is unix version. but in sf, postinstall has white icon.

1251169730_2018-09-3011_21_26.png.6b6131bb544fe657e6c74fe5f7455d29.png

 

 

Edited by Sherlocks

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • 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
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      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 at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      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.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      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 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="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/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 Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By PixelLover
      I'm in the middle of my first hackintosh (High Sierra) on my ZenBook Pro UX501VW-US71 laptop using the Vanilla Install. I've tried using different config.plst files and I've gotten the furthest with RehabMan's own (linked here). It hangs at error message IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0.   Can anyone help me figure out what changes to make to the config.plst file for my specific laptop (which is where I assume the problem lies)   System Specs: Intel Skylake Core i7­-6700HQ 2.6 GHz Quad­core
      Intel® HD Graphics 530 Nvidia GTX 960M 2G 15.6" Touch IPS 4K Ultra­-HD display, 3840 x 2160 resolution   Kexts: AppleALC.kext FakeSMC.kext Lilu.kext USBInjectAll.kext WhateverGreen.kext  
    • 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





       

×