Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

Posted (edited)

Odd question. Shouldn’t I be able to boot into EFI shell from Clover menu? I do not have that option currently (see below) I just updated to 5018 but the last version didn’t have that menu option either. What am I missing?

 

screenshot0.thumb.png.3b1e1597384243663445af891691e008.png

 

EDIT:

Okay, I'm a bonehead. In my attempt to have a "pristine" or "clean" EFI folder, I deleted the folder with the shell in it! Doh! It works now.

 

Edited by pkdesign
SOLUTION

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
8 minutes ago, pkdesign said:

Odd question. Shouldn’t I be able to boot into EFI shell from Clover menu? I do not have that option currently (see below) I just updated to 5018 but the last version didn’t have that menu option either. What am I missing?

 

I have it with 5028. Theme issue...? I've attached my 5028 if you wanna give it a try. 

 

screenshot4.png

Clover_v2.5k_r5028.zip

Edited by arsradu

Share this post


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

Of course!

I proposed you see this in log.

Yes found with any arguments. disk0s4, disk0s7

 

8 hours ago, Cyberdevs said:

@vector sigma

Sorry for the delay here's my log. I have one SSD and one HDD attached to the system and I made the Fusion Drive and I'm running Catalina at the moment.

 

Please let me know if there's anything else that you need me to do. :)

 

espfinder.plist.zip

thanks guys! @Cyberdevs in yours I've found something different, so I'm not sure if in Terminal the message was like 'ESP not found', anyway thanks to your log I'm pretty sure will be able in the next version.... version where the log will show me the result :-)

Share this post


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

thanks guys! @Cyberdevs in yours I've found something different, so I'm not sure if in Terminal the message was like 'ESP not found', anyway thanks to your log I'm pretty sure will be able in the next version.... version where the log will show me the result :-)

Sure thing man, I will check again and create another log when I get back home and see if it differs from the first log and if it was different I will let you know.

 

Cheers

Share this post


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

 

I have it with 5028. Theme issue...? I've attached my 5028 if you wanna give it a try. 

 

screenshot4.png

Clover_v2.5k_r5028.zip

Theme does nothing with Shell appearance, if tool_shell.png was missing from \icons; it'll use one from embedded. #cmiiw

Shell*.efi are provided on \tools, Scan=true under GUI should find them, or manually adding Custom entry for Tools.

Share this post


Link to post
Share on other sites
29 minutes ago, Badruzeus said:

Theme does nothing with Shell appearance, if tool_shell.png was missing from \icons; it'll use one from embedded. #cmiiw

Shell*.efi are provided on \tools, Scan=true under GUI should find them, or manually adding Custom entry for Tools.

 

I see... You can tell I'm not a theme expert. :))) Thanks for the info! I did not know that. Then I guess it could have been a bug with Clover....? Seems to be fixed now. Or at least in my case, it works fine

Share this post


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

thanks guys! @Cyberdevs in yours I've found something different, so I'm not sure if in Terminal the message was like 'ESP not found', anyway thanks to your log I'm pretty sure will be able in the next version.... version where the log will show me the result :-)

I tested the app once more and there is no message like you said "ESP not found". here is the new output and the Terminal's screenshot:

 

Screen Shot 2019-07-26 at 9.58.55 AM.png

espfinder.plist.zip

Share this post


Link to post
Share on other sites

hi @vector sigma

 

This line has disappeared from buildme script in repo. I don't understand why

 

#Create SRC folder
mkdir -p $HOME/src/edk2 && cd $HOME/src/edk2 && svn checkout https://svn.code.sf.net/p/cloverefiboot/code/ Clover

 

Share this post


Link to post
Share on other sites

anyone else on the x299 platform having issues with some of the later builds in clover? 5020 and 5028 forsure exhibit this sympton. i havent tested other "new" versions but it seems going back to 4979 resolves the issue.

 

 

seems somehow the boards bios, or nvram (sorry for my lack of knowledge) is getting corrupt.

Share this post


Link to post
Share on other sites
3 hours ago, Wackymac said:

anyone else on the x299 platform having issues with some of the later builds in clover? 5020 and 5028 forsure exhibit this sympton. i havent tested other "new" versions but it seems going back to 4979 resolves the issue.

 

 

seems somehow the boards bios, or nvram (sorry for my lack of knowledge) is getting corrupt.

Revision 5028 is for X299. 

Don't forget the difference between 4xxx and 5xxx. There is driver folder structure.

Share this post


Link to post
Share on other sites

@Slice I see a lot of people complaining about the drivers structure in 2.5k. And while I personally think the new structure makes a lot more sense than the old one, and while I think people will always complain about something, I also think that part of the problem is the fact that we never told them about those changes.

 

Maybe...for important things that could potentially affect functionality, it would be best to have a message in the installer, to let the people know about those changes. A lot of things happen because of miscommunication. So....let's communicate. Efficiently.

 

Just my personal opinion, of course.

Share this post


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

Revision 5028 is for X299. 

Don't forget the difference between 4xxx and 5xxx. There is driver folder structure.

maybe you can help then?

when using aptiofix, (which has been working for around 2 years for me) ;

 

upon restart or shutdown from mac os, if i enter the bios and make a setting change, i can no longer boot from the efi partition (the bios wont see it)..

when booting windows it doesnt exhibit the same issue.

if i just shutdown or restart the machine as usual without making a change in the bios, it works fine.

When i add emuvariable and rc scripts (removing the use of the hardware nvram on the board) which is not something ive previously done, it works perfectly fine as well.

if i make bios changes and restart the machine (but never boot mac) i dont experience any issue.

The only way for me to be able to see the drive again and successfully boot the machine is to flash the bios.

 

it seems like upon shutdown of mac os. somehow it is doing something to my bios.

 

Do you have any ideas what may be going on? im ripping my hair out on this as the machine has been running fine for 2 years, until the other day it just randomly wouldn't see the boot drive anymore. (the only changes to the machine have been updating clover and all its drivers)

 

 

Share this post


Link to post
Share on other sites
5 minutes ago, fabiosun said:

@Wackymac

I am using 5024 version with my X299 rig without problems with Aptiofix (acidanthera) and VirtualSMC kext or fakesmc.kext

 

 

using fakesmc. i have a feeling maybe my mobo is bad... (the prime x299 deluxe from what i know has {censored} bios integrity)

Share this post


Link to post
Share on other sites
9 minutes ago, fabiosun said:

Asus has retired latest x299 bios for some failures..in my case 1001 version was bad..I do not know if similar problem is on yours ;)

 

didnt change anything with the bios until the issue started happening.

Share this post


Link to post
Share on other sites
Posted (edited)
10 hours ago, arsradu said:

@Slice I see a lot of people complaining about the drivers structure in 2.5k. And while I personally think the new structure makes a lot more sense than the old one, and while I think people will always complain about something, I also think that part of the problem is the fact that we never told them about those changes.

 

Maybe...for important things that could potentially affect functionality, it would be best to have a message in the installer, to let the people know about those changes. A lot of things happen because of miscommunication. So....let's communicate. Efficiently.

 

Just my personal opinion, of course.

Honestly I can't see the problem other than the user will be perplexed for a presence of a new directory called "drivers" and is not fully aware that now this is in use, but:

  1. Clover package migrate old drivers from new directory automatically only if the new path doesn't exist. So no one driver is lost.
  2. Old Clover are working because the installer didn't remove drivers64 nor drivers64UEFI
  3. New Clover still function with old directories structure if the new one is not found.
  4. Drivers installed by Clover overwrite old ones only if they exits in the Clover package, other user may have.. are untouched*.
  5. Third party programs used still place drivers in old directories??? Contact their developers, and told them to be a bit brainy Lol (joke) and update their app.
  6. Clover package didn't know if you made manual modifications such add drivers or delete drivers.

 

I see people claim for the missing AptioMemoryFix.efi after installing, but again, the installer didn't remove it, *unless the user have one of the MemoryFix drivers activated by an old installation or the user selected one of them where clearly is written "use only one of them". This happen only if you install a driver and then later you install another one manually, totally forgetting that the package remembers choices previously selected.  The same for SMCHelper, HFSPlus etc.

So the possible explanation is only one: users remove it voluntarily, dot. I've lost when or why them miss this.

 

What we can do is to write a README.txt inside the old drivers64 and drivers64UEFI.

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/26/2019 at 3:29 PM, Matgen84 said:

hi @vector sigma

 

This line has disappeared from buildme script in repo. I don't understand why

 


#Create SRC folder
mkdir -p $HOME/src/edk2 && cd $HOME/src/edk2 && svn checkout https://svn.code.sf.net/p/cloverefiboot/code/ Clover

 

Never was in. Think, "buildme" is inside Clover.... and if you have Clover... you don't need to checkout it :wink_anim:

 

 

Screenshot 2019-07-27 at 18.23.31.png

just cd into a directory called ..../"what you want"/edk2 and paste the above command in terminal... and you will be ready

Edited by vector sigma

Share this post


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

@Slice I see a lot of people complaining about the drivers structure in 2.5k. And while I personally think the new structure makes a lot more sense than the old one, and while I think people will always complain about something, I also think that part of the problem is the fact that we never told them about those changes.

 

Maybe...for important things that could potentially affect functionality, it would be best to have a message in the installer, to let the people know about those changes. A lot of things happen because of miscommunication. So....let's communicate. Efficiently.

 

Just my personal opinion, of course.

 

Well, it's much more than not explaining about the new directory structure.  There really ARE problems with version 5.  I have an Asus Z370 that will NOT boot on 5018, and yes, I did adjust the directory structure.

 

It's also a mistake, in my view, to not offer the AptioFix options for those of us who need it....a bad mistake!

Share this post


Link to post
Share on other sites
Posted (edited)

@meaganmargaret

every opinion is important, new clover support also old folders structure..so usually and for now I am changing only bootx64 and cloverx64 efi files..and all is fine, so no need to modify a "working" structure

 

 

Edited by fabiosun
typo

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, meaganmargaret said:

It's also a mistake, in my view, to not offer the AptioFix options for those of us who need it....a bad mistake!

Sorry Mrs but I lost where you file a bug about memory fix drivers included in Clover, and why your "AptioFix" disappear.

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
23 minutes ago, meaganmargaret said:

 

Well, it's much more than not explaining about the new directory structure.  There really ARE problems with version 5.  I have an Asus Z370 that will NOT boot on 5018, and yes, I did adjust the directory structure.

 

It's also a mistake, in my view, to not offer the AptioFix options for those of us who need it....a bad mistake!

 

The installer doesn't compile with AptioMemoryFix anymore, for reasons independent of Clover. Which is why it's been removed. Simple as that.


Also, there are plenty of AptioFix options in the current installer. Just use OsXAptioFix3Drv (comes with fixes for NVRAM, too). Would it help if someone renamed it to AptioMemoryFix? Cause AptioMemoryFix is nothing more than OsXAptioFixDrv, + some upgrades.

 

Also, you don't need to adjust anything manually... 

 

For the Z370 boot issue, make sure all the drivers are in the new directories, that you have at least one AptioFix driver, but not more than that, and that should be all. I think a verbose log might help to determine a potential kernel panic, if that's what's happening in your case.

Edited by arsradu

Share this post


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

Never was in. Think, "buildme" is inside Clover.... and if you have Clover... you don't need to checkout it :wink_anim:

 

I've made a mistake.

 

OK for 'svn checkout'. I've to use Buildme inside his directory, Right?

 

What about src folder

Share this post


Link to post
Share on other sites
Posted (edited)
7 hours ago, Matgen84 said:

OK for 'svn checkout'. I've to use Buildme inside his directory, Right?

Yes, just a double click with the mouse.

 

7 hours ago, Matgen84 said:

What about src folder

Can be any also "MyCoolDirectory" lol e.g.:

 

so create edk2 directory inside your cool directory:

mkdir -p ~/Desktop/MyCoolDirectory/edk2

then change directory:

cd ~/Desktop/MyCoolDirectory/edk2

then checkout Clover:

svn checkout https://svn.code.sf.net/p/cloverefiboot/code/ Clover

dowble click on:

~/Desktop/MyCoolDirectory/edk2/Clover/buildme

easy no?

 

EDIT

creating folders for Clover is advised to have no blank spaces in the middle of the directory name

Edited by vector sigma

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 MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • 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) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : 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
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By Alesss
      Good morning,
       
      I've the following pieces of hardware:
      - i7 6700K
      - GTX 1080
      - Asus Z170 Deluxe
      - NVME hard drives
       
      Yesterday I've successfully completed a High Sierra installation (I can't migrate to Mojave due to missing NVIDIA web drivers) but the system (even though it works correctly) seems to show a kernel panic at every shutdown/reboot.
       
      Please find the RunMe.app report attached.
       
      A couple of notes:
      - I've installed the audio kexts through the acidanthera AppleALC procedure
      - I've generated the SSDT with pikessdt script
      - Nvidia web drivers have been installed with the vulgo/webdriver.sh script that requires the WhateverGreen and the ngfxcompat=1 boot argument
      - AirportBrcmFixup.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext have been used to unlock the full potential of the integrated Wi-Fi card
      - I've tried to clean nvram and motherboard CMOS with no avail
      - I've tried to update Clover to the latest version but it always results in an unbootable system
       
      It's a pity because everything seems to work correctly (USB ports, graphics, Wifi card, Continuity and so on. I haven't tried sleep but I don't use it anyway ) but this crash is fairly annoying.
       
      Thank you very much,
      Alesss
       
      Send me Ales-iMac.zip
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×