Jump to content
LonelyTV

MacOsX on the Surface Pro 3

194 posts in this topic

Recommended Posts

Update (23/02/15):

gkarg has gotten the Type Cover to work in Yosemite. I'm working on an updated tutorial that will cover installing 10.10 on the machine. But for now, here is the link the KEXT needed to get the Type Cover working.

 

Thank you Gkarg and everyone else for all of your hard work on getting this to work.

 

 

Type Cover 3 KEXT

 

 

----------------------------------------------------------

 

This is the current status of what is and what isn't working:

 

Type cover -> works

Touch screen -> in progress

Wi-Fi -> not working

Bluetooth -> not working

Sound -> works

Graphics -> works with QE/CI + HiDPI Mode with minor graphic glitches

SD Card -> works

USB 3.0 -> works

 

----------------------------------------------

 

Seeing as the Surface Pro 3 and Surface Pro 2 share similar hardware I made an attempt to install 10.9.2 on to it. Following JahStories' tutorial I was able to get the machine to boot into the installer.

However, because of the new screen it seemed to hang at a black screen. To fix this I had to adjust some of the flags given to Clover. 

 

Here is a fixed "config.plist" that will let the installer and OS boot past the black screen:

 

 Surface Pro 3 Clover Config.zip

 

I added to DSDT fixes: INTELGFX as well as GRAPHICS to the plist, changed the "Intel Injection" to true, changed the SMBIOS to a full Macbook Air SMBIOS, and removed the custom EDID since we have a new panel. 

 

Once in the OS the UI has some serious artifacts on the menu bar as well as the dock. I attribute this to the new screen and with time I'm sure we can figure out how to fix it. 

 

Here is the HEX for the EDID if you want to try out a custom EDID for the panel. I haven't had the chance to input it.

00FFFFFFFFFFFF004CA342350000000000170101951911780AEE95A3544C99260F505400000001010101010101010101010101010101785070A080A0295030203A00FEA9000000196A4070A080A0295030203A00FEA900000019000000FE0053414D53554E470A2020202020000000FE00313230514C30312D3030310A200069

This is just a start and I hope others will contribute so we can get it up and running.

Share this post


Link to post
Share on other sites
Advertisement

you can try to use a genericxhci kext to make the keyboard work...

 

Sadly, the two versions of the KEXT didn't work. I'll give it another go shortly.

Share this post


Link to post
Share on other sites

Hey, do you have a short guide of what you've done so far?

 

So far all I have done is trying to get the OS to install. In doing so I followed the first set of tutorials on the Surface Pro 2 thread (under the header: "Surface Pro 2 Gen Steps"). The only modifications I needed to do was to utilize the config.plist that I have posted above in place of the one the tutorial tells us to use. This got me into the installer and into the OS. 

 

I haven't had time to toy with anything else but as I said there isn't much left to try and fix. We need to get the Type Cover to work and iron out the graphical artifacts the screen has when in the OS. I'm thinking that the artifacts can be taken care of if we can get the right DSDT, any DSDT Modifications, as well as an adjusted conflg.plist. The type cover currently isn't working in Linux either so I'm suspecting it's due to a unsupported USB chipset. Something I'm sure that can be fixed with the right KEXT. 

Share this post


Link to post
Share on other sites

its still not ready for daily use...

 

but you can always test & try installing it as Lonelytv posted...

 

btw i find more interesting installing and fixing everything, than actually use my hackintoshes 

 

it's the insanely part :D

Share this post


Link to post
Share on other sites

I too have "artifacts" on the menu bar and dock, even on SP2. Maybe they are 4300U caused? I will post again about them on SFPro2 thread "soon".

 

 

By the way, AvastarFwLoader won't work on SP3, but the fix should be trivial (add a new personality for the new PCI IDs and mix in the new USB8897 firmware image from http://git.marvell.com/?p=mwifiex-firmware.git;a=tree;f=mrvl

 

I will try to build a version that should work on all Surface models, but as usual, it may be some time until my next freetime slot.

Share this post


Link to post
Share on other sites

I've had to stop work on trying to get OS X to run on my device recently. I've been having some issues with LCDs and I will be on my third Surface Pro 3 next week. However, I did figure a few things out:

 

  • Sound does work when you use VoodooHDA and remove the AppleHDA kext. This is no surprise since it worked on the Surface Pro 2, I just never got around to working with it.

 

  • The graphic artifacts go away when you boot into OS X with a resolution lower than native. I found the "1600x1066" resolution to be close enough to native.. I don't know what causes the artifacts just yet, but the fix currently is to set the resolution to lower than native, and reboot. Changing it back to native WILL cause the artifacts to show up again. Also, the brightness is fixed and can not be changed, yet.

 

  • I still have had NO success with the type cover or touch screen. No amount of KEXT I throw at it I can not make the type cover work. The touch screen, on the other hand, uses the N-Trig DuoSense (DS-4196) digitizer which is currently unsupported by Touch-Base (VID: 1B96 PID: 0001). I did not get the chance to check the other drivers listed on the Touch-Base site, but I figure it will be a no go since the one in the Surface Pro 3 is listed as unsupported.
  • Bluetooth is the only thing I did not attempt to fix. I'm certain the fix on JahStories' tutorial will work... but I'm uncertain.

That is it for now. Hopefully we can figure this stuff out.

Share this post


Link to post
Share on other sites

Can you try switching color profiles. On my laptop with an HD4600 this sort of resolves the graphic artifacts.

Right you are! I tried the built in "sRGB IEC61966-2.1" and it eliminated nearly all of the graphical artifacts. The only ones I noticed on a reboot was on the desktop the two "hidden" files were garbled. I attribute this to the transparency they have. I'll test more shortly.

 

EDIT: Turns out it's not just the transparent files, I have two files and a folder on my desktop that become garbled when I reboot. I suspect it's just leftovers from the boot process before the device corrects the color profile. 

I've noticed with the type cover that the backlight turns off and then back on as if the device is trying to "initialize" it. I still don't know how to fix this, but it shouldn't be too hard. 

Share this post


Link to post
Share on other sites

Right you are! I tried the built in "sRGB IEC61966-2.1" and it eliminated nearly all of the graphical artifacts. The only ones I noticed on a reboot was on the desktop the two "hidden" files were garbled. I attribute this to the transparency they have. I'll test more shortly.

I've noticed with the type cover that the backlight turns off and then back on as if the device is trying to "initialize" it. I still don't know how to fix this, but it shouldn't be too hard. 

 

Great work you're doing on the Surface Pro 3. I'm looking forward to some awesome OSX support and you're one of the people putting in the work to make that happen. Why is wifi support impossible on these units? See I'm perfectly ok if we don't get touch support....OSX really doesn't have any support for it anyway.

Share this post


Link to post
Share on other sites

Great work you're doing on the Surface Pro 3. I'm looking forward to some awesome OSX support and you're one of the people putting in the work to make that happen. Why is wifi support impossible on these units? See I'm perfectly ok if we don't get touch support....OSX really doesn't have any support for it anyway.

OS X does not have Kernel Extensions, KEXT, that support Marvell’s Avastar 88W8897 or really any Avastar at that. Until either Apple or someone else writes a KEXT that supports it we are out of luck. In most cases you would just swap out the WiFi module for something that is compatible, but seeing as this is a SoC that is soldered onto the board we will have to make use of external dongles for it to work. I'm currently using the Edimax EW-7811Un USB dongle. 

Share this post


Link to post
Share on other sites

Any updates with the i7 model and the HD5000 graphics?

Unfortunately, I don't have an i7 Surface Pro 3 so I can't test it. If you have one you can follow the steps in the tutorial I've linked and use the config.plist I've attached to my first post to see if it works for you.

Share this post


Link to post
Share on other sites

Unfortunately, I don't have an i7 Surface Pro 3 so I can't test it. If you have one you can follow the steps in the tutorial I've linked and use the config.plist I've attached to my first post to see if it works for you.

I don't have any Macs that I can use to create a bootable usb drive though. 

Share this post


Link to post
Share on other sites

Hi guys!

 

New to non-Apple products, owning a Surface Pro 3. Always used Mac since 10.3 Panther.

 

From what i have red, OSX for SP3 still lacks features such as the touschscreen, wifi, etc. Do you guys think that it will be ever be compatible with OSX (I know wifi will be difficult)?

 

Thanks!

Share this post


Link to post
Share on other sites

the surface pro 3 is already compatible with OS X, there are missing drivers yet, but the system boots...

its just a matter of time...

 

for ex. in Italy and in many other countries it's not out yet, just announced.

Share this post


Link to post
Share on other sites

New to insanelymac, but are you guys able to boot OS X on the SP3 with OS X installed on the microSD slot/card? I also want to confirm that Bluetooth is working on the SP3 with OS X.

Share this post


Link to post
Share on other sites

New to insanelymac, but are you guys able to boot OS X on the SP3 with OS X installed on the microSD slot/card? I also want to confirm that Bluetooth is working on the SP3 with OS X.

I haven't tried installing Os X on a MicroSD card so I can't say. I am able to boot it from the SSD. Bluetooth SHOULD work following the fix on JahStories' tutorial. I never had the chance to try it out though.

Share this post


Link to post
Share on other sites

Hello guys

 

I got my Surface Pro 3 a couple of weeks ago and decided to have a go at installing OS X on my device. Having learned that the touchscreen is N-Trig based and that touch-base doesn't currently provide driver support, I decided to contact them to see if we can work out a solution to get driver support for the Pro 3.

 

After a few email exchanges we found out that Microsoft had switched from using an USB HID interface to an I2C HID interface for the Pro 3. Since this is the case, unfortunately, developing a proper driver for the Pro 3 will be a lot more involved.

 

Due to the more involved process, touch-base would need to be loaned a Pro 3 for a couple of months to develop a proper driver. With that said, is there anyone willing to take the plunge? :lol:  :)

Share this post


Link to post
Share on other sites

I suppose it would ideally be someone from the UK lending their SP to avoid the overhead of shipping. I would consider it otherwise! It's too bad there is so much to be done to get up and running on SP3 compared to older versions. This was the first generation where i really liked the hardware. You actually get a 2nd USB port on the power adapter, not sure yet if it is for charging only though. 

 

I have modified my iPad to the point where it behaves a lot like a normal computer, with working BT trackpad and keyboard, mouse if needed, but otherwise trackpad buttons and slide area, universal display out to HDMI or VGA, USB to most devices via connection kit and USB hub, file system nav, upload/download anything, email attachments, torrents, basically anything you would expect to be able to do with a regular computer. But at the end of the day it's still iOS, it's no Mac OS, and the lack of Mac software is the biggest downside of all.

 

But with SP it's theoretically possible to get the ideal touchscreen Mac OS. I was already talking with touch-base about a driver for my HP All-in-One so maybe there's some value to them to have a device lent to them so they can develop a driver? I'm also looking at getting one of those really large touch screen displays and having a driver for Mac OS for that too would def. seal the deal. If I got three free drivers that would definitely be enough to consider lending an SP3 for a couple of months.

 

Hopefully touch-base is willing to make some kind of a deal so everyone wins, whether it was with me or someone living closer to them to avoid shipping issues.

Share this post


Link to post
Share on other sites

About the usb port on the power brick, it was already there since the first gen. , but it's only for charging...

 

I personally like the surface pro 3 a lot, but i don't think it could really be an ideal OS X touchscreen device,

we will get such thing only when Apple decides to; The Finder, the on-screen keyboard and most things needs a be correctly modified and restyled.

 

I think that this Sp3 is really too big, the old form factor is still better for me not only for it's size but it's design too.

 

Since there are some rumors about a 12.9inch iPad, i hope that Apple is not doing something big like that, it would just be a bad idea...

 

And right now the prices of the first gen° of surface pros dropped crazily, so maybe today its time to get a first gen° instead of a "new" bigger and yet not "optimized" Sp3

 

But this is just my opinion. 

 

:)

Share this post


Link to post
Share on other sites

New to insanelymac, but are you guys able to boot OS X on the SP3 with OS X installed on the microSD slot/card? I also want to confirm that Bluetooth is working on the SP3 with OS X.

 

can't answer for the SP3, but I am running OSX off the microSDXC on the SP2

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 fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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 
       
       
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By MaLd0n
      Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&amp;t=6771   Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Install Clover in USB stick UEFI mode https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace Folder CLOVER INSTALLATION.zip   --Install System and boot with USB STICK! --Install Clover in UEFI mode and replace with my folder  Mavericks / Yosemite CLOVER Mavericks-Yosemite.zip El Capitan / Sierra CLOVER El Capitan-Sierra.zip   --Reboot and activate video!   Bingo!   Now you need a fine tune! I prefer DSDT way, apply all patches in one file, many people prefer many SSDTs or Clover patches! If you need DSDT edit... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Post Ioreg, extract with Ioreg Explorer http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222606 -Run it, post files generate in your desktop http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=222609    --DSDT My DSDT DSDT.Asus Z97M-PLUS.zip   Patches  -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -EHCx -DARWIN -LPC -XHCI -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -HDMI -ALS0 -SHUTDOWN -LAN -PNLF --SSDT Generate your SSDT Power Management, use ssdtPRGen Piker-Alpha https://github.com/Piker-Alpha run in terminal curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh chmod +x ~/ssdtPRGen.sh sudo ~/ssdtPRGen.sh ssdtPRGen.command.zip
       
      --SSDT i74790K
      SSDT.i7 4790K.zip
       
      --IOREG
      iMac.ioreg.zip
       
      Clear NVRAM, Purge and Kextcache Olarila.command.zip   stock coolerand Rio 40º    --FakeSMC http://www.hwsensors.com/releases --Audio http://www.insanelymac.com/forum/topic/314406-voodoohda-289/ --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/304235-intelmausiethernetkext-for-intel-onboard-lan/   Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
    • By WarDoc
      This Post is for helping users with issue that come with Whatevergreen

      Feel free to join in and help users if you know your stuff
      also get the dev's of whatever green to join as well


      Whatevergreen has a few issues

      Multi-monitor Support is lacking as 2 monitors seems to be the limit for some even if the devs say it's not users say it's true

      Some Id's are wrong or missing (hence the nano and 390X not working)

      some GPU names are wrong ( which has been reported many times)

      FOR RYZEN OWNERS with Polaris :
      Modified kext:/S/L/E/AMD9510Controller.kext//Contents/Info.plistfrom:<key>IOPCIMatch</key><string>0x67EF1002</string>to:<key>IOPCIMatch</key><string>0x67FF1002</string> Updating clover to Clover_v2.4k_r4152 and using the config.plist here https://pastebin.com/TYiTEVcMwithbusratio=36 and npci=0x3000 ALSO THIS THREAD IS NOT FOR WHINING in anyway please do not post off topic if you don't like given support in this forum that's all you but majority of use need it.
       
      Source code: repository. FAQ and documentation: link.  
      a real SSDT example https://www.dropbox.com/sh/el66izg1lmk1jiu/AADCZUEjyQyiWWELlmzW2ix-a?dl=0 Credits to Pavo for the hard work of decoding the mess
      Boot argumentsAdd -raddbg to enable debug printing (available in DEBUG binaries).Add -radvesa to disable ATI/AMD video acceleration completely.Add -radoff to disable WhateverGreen.Add -radbeta to enable WhateverGreen on unsupported os versions (10.13 and below are enabled by default).Add -rad24 to enforce 24-bit display mode.Add -radlogo to patch boot logo distortion.Add -raddvi to enable DVI transmitter correction (required for 290X, 370, etc.)Add radpg=15 to disable several power-gating modes (see FAQ, required for 7xxx GPUs). If you Don't Want To use WEG or LILU clover 4297 has a new patch that fixes the same issues without kexts 
      You have to set in config.plist <key>Graphics</key> <dict> <key>RadeonDeInit</key> <true/>
×