Jump to content
MacPeet

[Guide] unsupported real MacPro works with Sierra (Example of real MacPro3,1)

38 posts in this topic

Recommended Posts

post-1358580-0-31849200-1466449875.png   post-1358580-0-90250100-1466449920_thumb.png

 

This guide makes an installation of macOS 10.12 Sierra on a real MacPro3,1 or other unsupported Mac's or Hackintosh's possible!

 

Edit: Update for GM post #9

 
What we need for this:
Atom.app or Atom Beta.App
Flat Package Editor.app (from /Developer/Applications/Utilities/PackageMaker.app/Contents/Resources/)
Download Install 10.12 Developer Preview.app
post-1358580-0-42344300-1466449824_thumb.png
 
In addition:
(All files are intended for MacPro3,1, possibly you have a grudge here your BoardID)
 
USB flash drive creation ( 8GB / Created flash drive with the BaseSystem.dmg method! does not work with the createinstallmedia method! ):
 
1. Restore BaseSystem.dmg from the InstallShield Developer 10.12 Preview.app out of your Program Files folder with the disk utility on the USB flash drive
 
2. Delete the simlink packages under "/Volumes/USB/System/Installation/"
 
3. Copy the original package folder from the Install 10.12 Developer Preview.app to "/Volumes/USB/System/Installation/"
 
3.1 optional: install Clover (only for Hackintosh and this Method)
 
4. Replace the InstallableMachines.plist in /Volumes/USB/System/Installation/Packages/ with from Archiv1.zip
 
5. Replace the PlatformSupport.plist in /Volumes/USB/System/Library/Core Services/ with from Archiv1.zip
 
6. Copy the OSInstall.mpkg from /Volumes/USB/System/Installation/Packages/ to the desktop
 
7. Open this by right-clicking the Flat Package Editor
post-1358580-0-85838300-1466483059_thumb.png
 
8. Delete the file "Distribution" and replace with file from Archiv1.zip
(Previously open possibly this file with Atom.app and edit your BoardID after)
post-1358580-0-66357000-1466449850_thumb.png
 
9. Replace now the OSInstall.mpkg in /Volumes/USB/System/Installation/Packages/ with the file from the desktop
 
10. Now you can start, the Mac reboots with pinned Alt key and select your USB flash drive. Make here the installation on a free selected by you partition. The installation starts, then the computer reboots.
 
11. While it is booting Alt hold, so it will not boot into fresh Sierra. Instead, choose your example Capitan and ride high order.
 
12. Go here now in the Finder to the fresh Sierra HDD in /Volumes/Sierra/System/Library/Core Services/ and replacing there the file "PlatformSupport.plist" from the Archiv2.zip
 
13. That's it, do restart in the fresh Sierra and let the installation run through to the end.
 
 
Credits/Sources
InsanelyMac
root86
Slice for the Clover Bootloader
Developers of Atom.app and Flat Package Editor.app
and all the others
 
have fun

Share this post


Link to post
Share on other sites
Advertisement

I can confirm this method works :thumbsup_anim:.

 

I use a MBP5,1 SMBIOS for my XPS M1530 laptop and added its board id (Mac-F42D86C8) to the InstallationCheck(prefix) section while removing MacBookPro5,1 from the nonSupportedModels section of the Distribution file.

 

Another workaround (possible in hacks but not on real Macs) is to temporarily change your SMBIOS to a supported model to allow installation on the hard drive eg  MacBook6,1 post#3.  Once the installer has completed putting all the OS files on the target partition for Sierra, you can boot into another OSX partition and change the SMBIOS back to MBP5,1 or whatever you normally use.  Note that as a minimum, your processor must support SSE4 - Penryn and newer Intel processors.

 

Attached files work to allow MBP5,1 definition for the installer.

MBP5,1.zip

Share this post


Link to post
Share on other sites

All I did was the following:

 

1. Remove drive from Mac Pro

 

2. Install Sierra straight from the App to Mac Pro's disk using your supported Mac/ hack

        - I used a USB3 to SATA3 adapter

        - If using a Mac can also be done with target disk if you have Thunderbolt to Firewire cable

        - If using a hack just plug it in internally

 

3. Modify PlatformSupport.plist to include Mac Pro's identifier and board ID

        - The one from El Cap is probably fine

 

4. Plug drive back in and boot normally!

Share this post


Link to post
Share on other sites
Another workaround (possible in hacks but not on real Macs) is to temporarily change your SMBIOS to a supported model to allow installation on the hard drive eg  MacBook6,1 post#3.  Once the installer has completed putting all the OS files on the target partition for Sierra, you can boot into another OSX partition and change the SMBIOS back to MBP5,1 or whatever you normally use.

 

Hello fusion17au !

 

I've successfully installed Sierra on my Dell D830 laptop after replacing it's old T7700 C2Duo by a T9300. Everything's fine so far.

 

I changed the SMBios from MBP5,1 to MBP7,1 to perform installation. Then I tried to revert back to the old MBP5,1. The OS is happy with that but Clover is not !

 

When I use this SMBios, Clover won't boot because of :

Reason : Mac-F42D86C8 (which is the Board ID of the MBP5,1)

I need to change it in config.plist (and only this) to Mac-F222BEC8 (MBP7,1) so Clover accept to boot the system. Otherwise, no way.

 

This is not a big deal since it works fine using this workaround or by simply using the normal MBP7,1 SMBios but I would like to know if you experienced the same minor issue with yours and how you bypassed it ?

 

Also, I was a bit concern about how the change of a SMBios would impact on some aspects of the Power Management. In this case, I guess they're probably negligible but you know, just wondering :).

 

NB : This is only happens with Clover, not with Enoch. I guess it"s because the limitation is coded somewhere in the boot.efi that Clover reads when it loads OS X. Enoch does not care about that file so it won't complain :unsure:

 

Thanks

Share this post


Link to post
Share on other sites

Hi @polyzargone,

 

Thanks for the info. 

 

Actually, I use the Board-ID, MLB and ROM from a MBP6,2 for iMessage purposes (but MBP5,1 SMBIOS "ProductName") so I haven't noticed this anomaly.

 

AFAIK, power management depends on the SMBIOS "ProductName" chosen in Clover's config.plist and not the Board-ID so I think you should be OK continuing to use MBP7,1 Board-ID with MBP5,1 SMBIOS :).

 

PS

  • Did you replace PlatformSupport.plist in /Volumes/Sierra/System/Library/Core Services/ with one that contains your MBP5,1 board-id Mac-F42D86C8?
  • Some guys in this MacRumors thread reported bypassing the compatibility check by adding the -no_compat_check boot argument to /Library/Preferences/SystemConfiguration/com.apple.Boot.plist.

Share this post


Link to post
Share on other sites

OK, thanks for the insight about PM.

 

I didn't notice anything particular while using MBP7,1 so far so I guess it's just fine.

 

I'll keep using it so now I can say I've got a brand new Mac Hack for free ! :hysterical:

Share this post


Link to post
Share on other sites

my real MacPro3,1 now works with macOS Sierra GM 16A322

Update: my real MacPro3,1 now works with macOS Sierra 16A323

 

post-1358580-0-87203600-1474022154_thumb.png

 

help these tools: post-1358580-0-06039000-1474206288.gif

http://dosdude1.com/sierrapatch.html

http://dosdude1.com/sierraswupatch/

 

 

optional:

real MacPro3,1 and HD5770 - GPU-Powermanagement-Patch (only german): https://www.root86.com/blog/40/entry-55-how-to-natives-amd-gpu-powermanagement-einschalten-auf-macpro31-41/

Share this post


Link to post
Share on other sites

One question!

If I use Sierra Patch, work it on hackintosh based pc?

How I can boot it?

After to create usb I need to install clover into usb?

Please, I am little confused and newby about hackintosh, and sorry my little bad english :D

Share this post


Link to post
Share on other sites

Update to 10.12.1:

 

post-1358580-0-74362300-1477815050_thumb.png

 
Without dosdude stick, but installed as a direct update from the store.
Start AUSEnabler.app (see dosdude link) and change the catalog and the update is already displayed in the appstore.
Simply start and run.
There were no problems.
 
Update to 10.12.2 DP1 16C32e:
direct update from the store
no problems
 
Update to 10.12.2 DP2 16C41b:
direct update from the store
no problems
 
Update to 10.12.2 DP3 16C48b:
direct update from the store
no problems

Share this post


Link to post
Share on other sites

No, nothing is known to me.

Change to better CPU with Sierra Support (SSE4).
 
 
Update to 10.12.2 DP Beta 4 16C53a:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.2 16C67:
direct update from the store via AUSEnablerProduction
no problems, works
 
Update to 10.12.3 DP Beta 1 16D12b:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.3 DP Beta 2 16D17a:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.3 DP Beta 4 16D30a:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.3 16D32:
direct update from the store via AUSEnablerProduction
no problems, works
 
Update to 10.12.4 DP Beta 1 16E144f:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.4 DP Beta 2 16E154a:
direct update from the store via AUSEnablerSeed
no problems, works

Share this post


Link to post
Share on other sites

Update to 10.12.4 DP Beta 3 16E163f:

direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.4 DP Beta 6 16E189a:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.4 DP Beta 7 16E191a:
direct update from the store via AUSEnablerSeed
no problems, works
 
Update to 10.12.4 DP Beta 8 16E192b:
direct update from the store via AUSEnablerSeed
no problems, works

Share this post


Link to post
Share on other sites

Greetings, I have just received an 8-core 2,8GHz MacPro3,1 with 6GB ram and 8800GT but *without* a hard disk so whatever I do I have to start from square one.

Which method should I follow so eventually I have a MacPro3,1 running Sierra? Start with ElCap?

Share this post


Link to post
Share on other sites

And the story goes on. Also HighSierra works with some tricks with the unsupported Mac -> MacPro3,1. Everything without dosdude created, pure handwork.

 

post-1358580-0-71447400-1498399683_thumb.png   post-1358580-0-55617300-1498399705_thumb.png

Share this post


Link to post
Share on other sites

I upgraded my real MacPro 2008 from the ATI to Nvidia 8800 graphics card few years ago, is there any power management tricks needed for this graphics card?  Do you think there may be some incompatibility for apps running on this hardware with Sierra such as Logic or Final Cut etc etc?  I never upgraded from 10.9 since I have Maya, Cinema Studio 4d , adobe after effects and so on because I was not sure if any OS upgrades may break my current setup.

Share this post


Link to post
Share on other sites

I can confirm this method works :thumbsup_anim:.

 

I use a MBP5,1 SMBIOS for my XPS M1530 laptop and added its board id (Mac-F42D86C8) to the InstallationCheck(prefix) section while removing MacBookPro5,1 from the nonSupportedModels section of the Distribution file.

 

Another workaround (possible in hacks but not on real Macs) is to temporarily change your SMBIOS to a supported model to allow installation on the hard drive eg  MacBook6,1 post#3.  Once the installer has completed putting all the OS files on the target partition for Sierra, you can boot into another OSX partition and change the SMBIOS back to MBP5,1 or whatever you normally use.  Note that as a minimum, your processor must support SSE4 - Penryn and newer Intel processors.

 

Attached files work to allow MBP5,1 definition for the installer.

 

 

I can actually start the install of Osx 10.12.5 for my Quad Core 2 Duo with MacPro3,1 as you suggest change the smbios system definition to one that is supported. In my case when I try MacPro4,1 I get a kernel panic from AppleTyMCEDriver and found a clover patch for this but it doesn't seem to work on the installer.  If I choose iMac12,1 or 13,1 I can get to the installer desktop my my USB ports are all dead even with Rehabman USBInjectAll injector kext.   My only other way is to install on a supported mac make modifications for my Gigabyte board GA-G41m-ES2L  v3 and delete that driver or try the patch after the install, then insert the drive back.

 

Any other thoughts are welcome.

 

Thanks!

Share this post


Link to post
Share on other sites

@oSxFr33k,

 

Can you boot the installer in safe mode with MacPro4,1 SMBIOS?

 

Maybe create the installer by the "restore BaseSystem.dmg method", remove AppleTyMCEDriver from the installer's /S/L/E and rebuild kernelcache as described in this thread for the El Capitan Installer (should still work for Sierra).

 

Good Luck!

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 Badruzeus
      "The all-new 2019 version of the graphic design software suite is compatible with not only Windows but also Mac, complete with support for Dark Mode on macOS Mojave and the Touch Bar on the latest MacBook Pro models, providing quick access to layout settings, text controls, and more." ~ macrumors
       
      More details: https://www.coreldraw.com/en/product/coreldraw/mac/
    • 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





       

×