Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,164 posts in this topic

Recommended Posts

@fdandy006 

 

i upgrade right on top of the current /EFI. The installer first will make a backup of the current stuff. it leaves the config files as is. and then will update (replace) the various .efi files. if your GUI only has blue dots - maybe the theme is missing? did you select/install the ThinkPad theme? i manually trim out (remove) any files/folders for 32bit. 

 

if you diff -r the current /EFI and the backup (previous) /EFI the different files list should show the Clover_install.txt and .efi files (BOOTx64.efi, CLOVERX64.efi and the drivers64UEFI folder files.

Share this post


Link to post
Share on other sites
Advertisement

@aj - I can post a new bundle. but not much has changed since I posted the bundle using Clover b1888. i tried a number things on Clover - tweaks to config.plist and and playing with dsdt... but sad to say nothing seems to make much difference. i still get random sleep/wake issues with PS2 going away. and i hit the mute/unmute total freeze thing 2 times. sorry to admit that i have no ideas... frankly i kinda gave up and now I just boot with Chameleon on a USB and then eject it until I restart.  

Share this post


Link to post
Share on other sites

@aj - I can post a new bundle. but not much has changed since I posted the bundle using Clover b1888. i tried a number things on Clover - tweaks to config.plist and and playing with dsdt... but sad to say nothing seems to make much difference. i still get random sleep/wake issues with PS2 going away. and i hit the mute/unmute total freeze thing 2 times. sorry to admit that i have no ideas... frankly i kinda gave up and now I just boot with Chameleon on a USB and then eject it until I restart.  

my preference lol : i prefer waiting for a real new pack lol

Share this post


Link to post
Share on other sites

Hi guys, good news.

Today I updated Rehab's VoodooPS2Controller (1.8.5), and guess what?

Sleep works great and PS2 works fine after wake!! 

Share this post


Link to post
Share on other sites

@aj - great minds.... i did the same - installed/updated voodoops2 and fakesmc from rehabman. the last clover challenge I am finding is a total system freeze when i push mute/unmute.  will continue to test and report.

Share this post


Link to post
Share on other sites

I've tried the installation on a T430 - but i get the same error like DirtyMetis,

"Error Loading Drivers " after selecting the OSX Installation.

 

If I try to use the old package like you've written, it fails to start to boot by the stick.

 

Any hints?

Share this post


Link to post
Share on other sites

@plan_b 

 

do you have a dsdt?

 

are which old package are you using? i take it you stuck in trying to get an installer to boot up to install OSX?

if you are trying to get the install working. you could try boot args -x PCIRootUID=1

 

or are you trying to boot up after the install?

do you have the basic kext installed? i.e. FakeSMC , ethernet, PS2. 


@ag6952563 (and others!)

 

 

as you mention VoodooPS2Controller v1.8.5 seems to fix the problem of loosing keyboard and trackpad after sleep. i did only a few tests in the last days but waking it up after sleeping for about an hour works. i updated to Clover b1928 and I will repost a new Clover bundle soon if it continues to work well.

 

changes since i posted 1888 are:

new FakeSMC

new VoodooPS2Controller

tweaks in DSDT

tweaks in config.plist (drop HPET table, boot arg darkwake=11, InjectClockID=false)

Share this post


Link to post
Share on other sites

I updated to latest clover 1928 and used rehabs voodoo - and yes it does resume from sleep better.

 

I have mixed results in going into sleep however - ie, sometimes sleep works well, sometimes it stays in fast flashing power button.

 

Shutdown is still mixed results too - sometimes powering all the way off, however sometimes fan still running - ie 'on'.

Share this post


Link to post
Share on other sites

new FakeSMC & new VoodooPS2Controller under 1928 sleep and wake ok here to as tluck.


 

Please write down your config in signature, it can help others to understand or to join this community with a working machine.

for example copy my signature and personalize it for your T4x0 config (type is under your computer on the sticker)

 

 

have a good sunday

Share this post


Link to post
Share on other sites

Updated and posted Clover pack (b1928) for T420 -- see post  #241 for information -  ESP/EFI pack with kexts. 

 

Notes issues observations:

  • Sleep/wake so far has not lost trackpad - have not had fast blinking lights. 
  • have not touched mute button on system - use bluetooth keyboard (or toolbar to control volume level) - mute could freeze system (works fine on chameleon)
  • sometimes shutdown does not power off box. osx shuts down but remains with black screen.

 

 

Key changes since 1888: 

  • updated FakeSMC.kext (thanks to RehabMan)
  • updated VoodooPS2Controller.kext (thanks to RehabMan) 
  • minor tweaks in DSDT
  • minor tweaks in config.plist (drop HPET table true, boot arg darkwake=11, InjectClockID=false)

Share this post


Link to post
Share on other sites

Hi,

maybe this is discussed already.

Why should I install the kexts to /S/L/E with clover. I thought this is the trick of clover to do that by injection.

 

Sorry for this question, but I am trying to get my 4174NEG running with no luck with 10.8.3 so far, by not installing the kexts to /S/L/E.

I would like to keep the installation clean. So, maybe I don't need to ask further questions concerning this, because of my approach.

 

Thanks a lot

Regards,

em

 

P.S.: My current problem seems to be connect with a not starting windows-server. I think this has something to do with my HD3000 graphics card.

 

Share this post


Link to post
Share on other sites

@emueler - sure you can have your custom kexts in your ESP partition.  clover will load ones from the ESP to complement your OS. Clover can also patch some of the kexts on the fly. if there are conflicts you may need to remove them. for example, AppleHDA will conflict so you may need to remove (or replace) the one in /S/L/E. personally i was interested in a disk that could boot with Clover and Chameleon without changes so i put the custom kexts in /S/L/E. some folks prefer to keep the mods etc on the ESP. so its largely a matter of personal style.

 

 

InjectKexts
<key>InjectKexts</key>
<true/>

Loads additional kexts from EFI/CLOVER/kexts/.../.

Disabled by default.

Requires FSInject.efi driver.

Share this post


Link to post
Share on other sites

 

Updated and posted Clover pack (b1928) for T420 -- see post  #241 for information -  ESP/EFI pack with kexts. 

 

Notes issues observations:

  • Sleep/wake so far has not lost trackpad - have not had fast blinking lights. 
  • have not touched mute button on system - use bluetooth keyboard (or toolbar to control volume level) - mute could freeze system (works fine on chameleon)
  • sometimes shutdown does not power off box. osx shuts down but remains with black screen.

 

 

Key changes since 1888: 

  • updated FakeSMC.kext (thanks to RehabMan)
  • updated VoodooPS2Controller.kext (thanks to RehabMan) 
  • minor tweaks in DSDT
  • minor tweaks in config.plist (drop HPET table true, boot arg darkwake=11, InjectClockID=false)

 

Awesome! Could you update the Chameleon pack with this stuff too? Thanks!

Share this post


Link to post
Share on other sites

hi guys...
nice works on clover for thinkpad :)

i tried to install ML on my T430 2349A17 using clover. i've sucessfully boot using usb with clover as bootloader.
i even sucessfully pass through the installation.

When installation process using usb completed, the system restart and went to clover GUI (from usb).
then i picked the ML at my SSD. it then hung on '++++++'.
9405629610_31216b7448.jpg

below is the debug.log on clover.
 

 

121:541  0:140  HDA Controller [8086:1E20] :: PciRoot(0x0)/Pci(0x1B,0x0) => detected codec: 10EC:0269, setting layout-id=269 (0x10D)
121:824  0:283  stringlength = 1844
121:918  0:094  CurrentMode: Width=1600 Height=900
122:013  0:094  FSInjection:, skipping kext injection (not requested)
122:202  0:189  OnSimpleFileSystem occured
122:310  0:107   - done!
122:431  0:121  Closing log
122:525  0:093  SetStartupDiskVolume ...
 Volume: 'MacOSHD', LoaderPath: '<null string>'

122:619  0:094   DevPath: MacOSHD
122:713  0:094   GUID = 929EAB34-3174-48B6-BB44-4E91FE433114
122:821  0:107   efi-boot-device: <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>929EAB34-3174-48B6-BB44-4E91FE433114</string></dict></dict></dict></array>
122:915  0:094  Starting boot.efi
123:014  0:099  Using load options 'boot.efi -v GraphicsEnabler=No PCIRootUID=0 slide=0 arch=x86_64 '

is there anything i can do to be able to continue my installation?

my clover version is v2_r1942.
 

 

Share this post


Link to post
Share on other sites

@gendalo76...

 

not sure about how you are installing OSX. you will need to have some kexts injected/loaded... the message you show usually is when you have all the custom kexts installed already - not for installation, when i install a fresh OS. i have FakeSMC.kext and VoodooPS2Controller injected installed in /EFI/CLOVER/kexts/10.8..

the boot args i use are:

-v slide=0 WithKexts NoCaches

 

update:

 

seems that was the old way... looks like you specify

InjectKexts
<key>InjectKexts</key>
<true/>

Loads additional kexts from EFI/CLOVER/kexts/.../.

Disabled by default.

Requires FSInject.efi driver.

NoCaches
<key>NoCaches</key>
<false/>

Use if a recreation of system caches is needed, for example after the installation of new drivers. In contrast to ignoring caches, kext patches will be applied in this case.

It makes no sense to leave this paramater permanently in the configuration file. Instead, chooseBoot ... without caches in the OS option menu by pressing O after having selected the OS entry.

Requires FSInject.efi driver.

 

without a dsdt.aml installed, I set PCIRootUID=1 in config.plist 

also wonder why you have GraphicsEnabler=No as a boot  arg?

 

if you take a look at the bundle i posted, the /EFI/CLOVER/config.plist may help you get going.

 

good luck

Share this post


Link to post
Share on other sites

@gendalo76...

 

not sure about how you are installing OSX. you will need to have some kexts injected/loaded... the message you show usually is when you have all the custom kexts installed already - not for installation, when i install a fresh OS. i have FakeSMC.kext and VoodooPS2Controller injected installed in /EFI/CLOVER/kexts/10.8..

....

without a dsdt.aml installed, I set PCIRootUID=1 in config.plist 

also wonder why you have GraphicsEnabler=No as a boot  arg?

 

if you take a look at the bundle i posted, the /EFI/CLOVER/config.plist may help you get going.

 

good luck

hi tluck,

 thanks so much... i finally made it to boot into my sdd plugged-into usb port.

 what i did is boot with '-v PCIRootUID=0 slice=0 InjectKexts NoChaces'

 i did put GraphicEnabler=No because when i install to this SSD, i sucessfully did it with that boot flags. that's also the case when i use chameleon.

 no i put injectkexts and nochaces into config.plist.

 

 but when i put SSD into my ultrabay, the installation won't boot and wrote many error regarding unable to read many .kext.

 i tried to change PCIRootUID from 0 to 1, even delete it, but still has the same error.

 any idea with how to solve this? before i tried to reinstall with ssd put in its bracket/ultrabay.

 

i tried to clean-up my extra folder (for myHack) and clean some kext in SLE that showing error message in log (AppleRTC.kext and AppleSmartBatteryManager.kext).

I had Patched_10.7_AppleRTC.kext and AppleSmartBatteryManager.kext at my kext/10.8 in clover.

then updated to 10.8.4. my system working ok. 

then move my ssd to ultra bay sucessfully (previously on USB). don't know why now it works. :D

 

i'll share my configuration on different reply to keep it clean and edited as i have progress.

 

thanks tluck.

Share this post


Link to post
Share on other sites

hi friends,

 i wanna share my T430 configuration with clover.

 T430 info:

  Intel HD4000 only, 1600x900 screen resolution.

  board version: 2349-A17. (corrected from my previous post, not 2439-A17)

  BIOS version: 1.16 (G1ET41WW)

    I flashed the bios to remove wifi card restriction, so i can install Broadcomm card.

  RAM: 16GB, SSD Sandisk Extreme 256MB.

  audio chip: ALC269
 Clover version: r1942

 my clover folder can be found here.
works:

  - got 1600x900 resolution since the first installation

    sometimes when booting, in log-in screen show stretched/scrambled screen, shown only white.

    this is also happening when i use chameleon. simply shutdown with power button and boot again.

  - detected as macbook air 5,2 (13" mid 2012) with 16GB (3 slots ???, 1 empty), 

    manually set to MacbookPro9.2 and some setting to SMBIOS part in config.plist

      VRAM for HD4000 detected as 384MB. prior update to 10.8.4 (10.8), it was detected as 512MB.

  - wifi ok. 

  - usb3 port, accepts usb2 eksternal harddisk (WD element) and  works on Hi-Speed. 
      accepts usb3 external harddisk (WD my book essential) and works on superspeed.

  - bluetooth is working not OOTB (BCM20702A0). need to edit a kext. 

     follow instruction on this site. my product-id a bit different with the one on the site. 
     i can connect my magic trackpad to thinkpad.

  - front camera works ootb.

  - imessage, able to login and set which account should be used. but not yet tested to send and received message.

    not working.

  - icloud is wokring. I can sign-in and syncronize my notes and contacts, even registering the laptop for 'find my mac'.

  - trim enabled. (using kext patching in config.plist)

  - sleep works.

       - tried to make it sleep with closing the lid. then waking-up with opening the lid.

            keyboard and touchpad working.

         no eksternal harddisk connected prior sleep.

       - tried to make it sleep with fn+F4. then waking-up with fn.

            keyboard and touchpad working.

         attached usb3 eksternal harddisk prior sleep is not reconnected when woke up.

  - battery is working. use Rehabman's AppleSmartBatteryManager.kext.

     i need to patch my initial dsdt to make it works based on this link.

  - sound is working. not perfect, but enough for me.

     use VoodooHDA ver 2.8.4, just install, no need to touch its pref pane.

     works with internal speaker and headphone. when plugging headphone jack, need to switch manually at OSX's sounds setting.

not working yet:

  - icloud, unable to login.

  - imessage won't let me sign-in. registration failed.

  - battery is not detected using internal batterai icon, but with istat menu, shown when charged. 

      but only show nan%.

  - audio. 

 

anyone has appleHDA patch for T430??  :D


Trying to attempt this on my T530, but running into problems when trying to boot off the USB with Clover - I'll get the initial boot menu, select the option to boot from the usb, and be prompted with the following screen:

install_zpsa04c8484.jpg

This is after attempting the "boot in safe mode" from the right click menu in Clover - previous attempts would lock up at the "root device uuid is..." prompt.

I've managed to get ML installed previously using the ##### method, but would much rather go the UEFI route with a clean install. I can boot into the previous ML installation with the Clover usb if I select the safe mode option, but otherwise it gets aways into loading drivers and then reboots.

Any suggestions?

i have same problem during my installation.

i replace VboxHFS.efi to HFSPlus64.efi.

it solved my problem.


@Kogen,

you don't need to desolder the chip. just use SOIC clip and hardware flash programmer. the chip is located below touchpad.
if you have the same bios version as mine,1.16 (G1ET41WW), then you can get the nonwhitelist BIOS here.
i share my tools and the process on another forum. you can get the link on the last reply on previous link (bios).
 

Try again using my older custom package from post #117 and report back.

 

BTW: I guess I'll be switching from T420 to T430 soon. Right now I have both machines to decide witch one to sell. The T430 is a stronger model (i7) with optimus graphic card that I've always wanted to play with in OSX. To bad I still have very little time lately to do some serious hackintoshing, but I can report this about the new T430:

- I can boot successfully with older clover r1229 (I didn't had the time to investigate why Clover newer releases wont boot)

- USB3 works excellent OOB (booting from 32GB USB3 pen-driver - super fast)

- the NVIDIA NVS 5400M - works with graphic enabler (I have black screen with HD4000)

- too bad the whitelist bios can't be flashed to this device (no WiFI swapping for broadcome model) and I don't want to solder the eprom and flash it outside using phoenix flasher. - Can you guys suggest USB wifi that works OOB?

- T430 boots clover in full resolution (1600x900 and looks gorgeous) so I guess I'll update the ThinkPad theme background for high res in free time :)

Share this post


Link to post
Share on other sites

@gendalo76 :

your config (config.plist, ACPI folder, kexts folder)

shoud be in /efi/clover/oem/2437A17

 

SystemProductName should be renamed to 2437A17

happy to see T430 (great config) is ok now.

for icloud, iMessage have a look here

Share this post


Link to post
Share on other sites

@gendalo76

 

excellent update on your progress. a few notes:

 

you will not need patched_10.7 _AppleRTC.kext as Clover will patch the standard version.

you may be able to use the AppleHDA.kext i put in my bundle as i think 430 uses the same codec/chip.

if so, then you need to add custom dsdt.aml which defines the audio capability. clover can do a pretty good job on patching the DSDT but a few things are missing/messed up. (i provide the source dsdt.dsl with comments the ACPI/patched folder in the zip -  search tjl for what i changed. (thanks to manwe150 who did a lot of the early work to make things happen!) 

 

i use rollback AppleACPIPlatform + VoodooBattery for battery. i am not sure about AppleSmartBattery - i think it needs some fancy dsdt mods. note: sleep works better with this rollback ACPI kext too.

Share this post


Link to post
Share on other sites

@gendalo76 :

your config (config.plist, ACPI folder, kexts folder)

shoud be in /efi/clover/oem/2437A17

 

SystemProductName should be renamed to 2437A17

happy to see T430 (great config) is ok now.

for icloud, iMessage have a look here

thanks Tetonne.

i'l move to OEM folder as suggested.

i'll report with icloud and imessage later on.

@gendalo76

 

excellent update on your progress. a few notes:

 

you will not need patched_10.7 _AppleRTC.kext as Clover will patch the standard version.

you may be able to use the AppleHDA.kext i put in my bundle as i think 430 uses the same codec/chip.

if so, then you need to add custom dsdt.aml which defines the audio capability. clover can do a pretty good job on patching the DSDT but a few things are missing/messed up. (i provide the source dsdt.dsl with comments the ACPI/patched folder in the zip -  search tjl for what i changed. (thanks to manwe150 who did a lot of the early work to make things happen!) 

 

i use rollback AppleACPIPlatform + VoodooBattery for battery. i am not sure about AppleSmartBattery - i think it needs some fancy dsdt mods. note: sleep works better with this rollback ACPI kext too.

thank tluck.

i'll try you suggestion and back with report.

Share this post


Link to post
Share on other sites

 Hi all,

 

Just preparing my T420 so that I can follow through this guide and hopefully contribute some of my findings too.

 

However first thing's first - I bought a Dell WLAN card to replace the stock wireless card so that I could get Wireless support in OS X. To make this work obviously you need to flash the BIOS with a non-whitelist BIOS. So I downloaded the version 1.43 version one from the first post in this thread.

 

Now everything went as planned - I updated with the stock 1.43 BIOS image, rebooted, then flashed with the NWL file and rebooted. I haven't replaced the WLAN card yet but I have noticed that on boot the screen stays black for longer and I get a POST beep code (4 beeps, pause, 4 more beeps). I thought that I had somehow bricked the laptop but it proceeds to then POST and boot perfectly normally. I've tried resetting the BIOS to defaults but the beep codes persist. It's not the end of the world - but I like things neat and tidy and it bugs me that this hasn't worked quite right.

 

Is there something I've missed or done wrong? Any help appreciated.

 

Thanks!

 

Share this post


Link to post
Share on other sites

 Hi all,

 

Just preparing my T420 so that I can follow through this guide and hopefully contribute some of my findings too.

 

However first thing's first - I bought a Dell WLAN card to replace the stock wireless card so that I could get Wireless support in OS X. To make this work obviously you need to flash the BIOS with a non-whitelist BIOS. So I downloaded the version 1.43 version one from the first post in this thread.

 

Now everything went as planned - I updated with the stock 1.43 BIOS image, rebooted, then flashed with the NWL file and rebooted. I haven't replaced the WLAN card yet but I have noticed that on boot the screen stays black for longer and I get a POST beep code (4 beeps, pause, 4 more beeps). I thought that I had somehow bricked the laptop but it proceeds to then POST and boot perfectly normally. I've tried resetting the BIOS to defaults but the beep codes persist. It's not the end of the world - but I like things neat and tidy and it bugs me that this hasn't worked quite right.

 

Is there something I've missed or done wrong? Any help appreciated.

 

Thanks!

Were you on 1.43 before you flashed 1.43 whitelisted? If not, that's probably the problem. Not sure on how to go about fixing it though.

 

Edit: Sorry i just reread it and you were. No clue what's wrong, sorry.

Share this post


Link to post
Share on other sites

Finally got my display port VGA adapter but it doesn't seem to work when I use it on the Laptop (Left hand side).  How do I check the SNBGraphicsFB.kext.  When I show packages I don't see a config.plist?

Share this post


Link to post
Share on other sites

@fdandy006

 

the config.plist I put in the OEM folder (see my uploaded) will make clover patch the 4th buffer of the AppleIntelSNBGraphicsFB.kext to be VGA. the kext in EFI/CLOVER/kexts/10.8-SLE is permanently edited in the same way. make sure you do your testing with your laptop undocked. if you attach to the VGA port on the left side you will need sleep/wake or restart with the cable plugged in to see the VGA device. i had trouble with some devices (like projectors) so i use a DisplayPort to VGA adapter which is a bit more automatic and consistent in device detection.

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 cvad
      Small tool to download, compile and build the latest Clover X64 package,
      possible include HFSPlus-64.efi.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
      Clover_Builder.app.v1.2.0.zip
    • 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 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 fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fantomas1
      -----------------------------
      Mise à jour 12/07/2018
      -----------------------------
       
      La sortie de macOS 10.14 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       

       
      -----------------------------
      Mise à jour 09/06/2017
       
      -----------------------------
       
      La sortie de macOS 10.13 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       
       
       
      -----------------------------
      Mise à jour 15/06/2016
      -----------------------------
       
      Une petite mise à jour du topic pour confirmer le bon fonctionnement du patch à la volé de Clover (r3561) avec macOS Sierra.
       

       
       
       
      -----------------------------
      Mise à jour 24/08/2015
      -----------------------------
       
      ok, très bien,
       
      comme pour la HD6770, la nouvelle méthode du patch à la volé est de nouveau fonctionnel et avec les dernières versions de Clover.
       
      pour ma part, je suis sur El Capitan DB7 et Clover r3259
       

       
       
      par contre, je suis toujours obligé de m’aider de l’astuce avec FakeSMC pour que mes kexts soient toujours chargés, mais au moins cela marche.   
       
       
       
       
      et pour config.plist, cela donne ça :
       

       
       
      ceci est juste un exemple avec ma HD4830, il va de soi que vous devez mettre Device-ID de votre carte graphique !!!
       
       
       
       
       
      Salut à tou(te)s
       
      Comme certain(e)s le savent, les cartes graphiques dites "Exotiques" ne sont pas supportés par le système d'exploitation d'Apple.
      En sus d'ajouter l'identifient de la carte graphique (Device ID) dans l'Info.plist du ou des kexts concernés, il faut aussi interagir sur la partie "binaire" du kext par le biais du "patching".
       
      Dans notre cas, les cartes graphiques exotiques sont les cartes AMD (anciennement ATI) de la série HD 48xx, et plus précisément les HD 4830, HD4850, HD4870x2 et HD4890.*
       
      Donc le but est de faire fonctionner ces cartes graphiques de manière stable et fluide en activant QE_CI, chose nécessaire pour en profiter pleinement du système d'exploitation.
       
      * Juste avant de commencer, vous l'avez peut-être remarqué, la HD4870 n'est pas sur la liste suscitée et pour cause c'est que cette carte graphique est nativement supportée par le système d'exploitation d'Apple. Son Device ID est 0x94401002 que vous pouvez trouvé dans l'Info.plist des kexts concernés et c'est celui-ci que nous allons utiliser afin de le remplacer par le Device ID de notre carte graphique.
       
      ** Ce tuto est fait pour fonctionner sous OS X Mavericks, mais il doit fonctionner aussi avec les autres. La seule chose différente c'est l'adresse binaire à patcher.    
       
       
      Très bien, comme le titre le suggère, nous allons voir comment faire reconnaître ces cartes graphiques sous Clover et obtenir par la même un QE_CI activé et parfaitement fonctionnelle.
       
      Je vais utiliser ma Sapphire HD4830 512 MB GDDR3 PCI-E (comme cobaye    ) pour ce test et qui a pour Device ID 0x944c1002.
       
      Pour que ce test réussisse, nous allons donc utiliser ces 2 kexts, à savoir AMD4800Controller.kext (pour la partie QE) et ATIRadeonX2000.kext (pour la partie CI) et allons ajouter notre Device ID dans l'Info.plist. via le tweak "KernelAndKextPatches"
       
      Donc les valeurs à entrer dans notre config.plist sont celle-ci :
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>     </array> Comme vous pouvez le voir, la clé "InfoPlistPatch" sert à injecter notre Device ID "uniquement" dans Info.plist, sans y toucher à la partie "binaire" de nos kexts. La clé "Find" a pour fonction de trouver le Device ID que l'on veut remplacer par le notre en utilisant la clé "Replace".
       
      Très bien, maintenant comme nous l'avons dit au début de ce tutoriel, ajouter notre Device ID n'est pas suffisant pour faire fonctionner pleinement notre carte graphique, il faut encore interagir sur la partie "binaire" de nos kexts. Dans notre cas, il va falloir agir uniquement sur un kext, çàd sur ATIRadeonX2000.kext et plus particulièrement sur ATIRadeonX2000.kext/Contents/MacOS/ATIRadeonX2000
       
      Et pour cela, nous allons faire comme ceci :
      <key>KextsToPatch</key> <array> <dict>     <key>Name</key>     <string>ATIRadeonX2000</string>     <key>Find</key>     <data>0F8394010000</data>     <key>Replace</key>     <data>909090909090</data> </dict> </array> Là nous pouvons voir que la clé "InfoPlistPatch" n'est pas utilisée et donc ces valeurs n'auront aucun effet sur l'Info.plist mais agiront uniquement au niveau de la partie "binaire". 
       
      Et voici les valeurs en leur forme complète que vous devrez ajouter dans votre config.plist
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>Find</key>             <data>0F8394010000</data>             <key>Replace</key>             <data>909090909090</data>        </dict>     </array> Très bien, maintenant il ne nous reste plus qu'à autoriser l'injection des kexts, sans quoi le patch ne fonctionnera pas. Et nous allons le faire via le tweak "InjectKexts" comme ceci :
      <key>SystemParameters</key> --> clé principale <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key> --> sous clé       <string>Yes</string> </dict>  
       
      Si certain(e)s d'entre vous préfèrent utiliser le logiciel "Clover Configurator" pour plus de facilité, voici comment entrer ces valeurs :
       
      Allez sur l'onglet "Kernel And Kext Patches" et faites comme ceci :
       
       
       
      *Ne faites pas attention sur le majuscule/minuscule, cela ne fait aucune différence
       
       
      Et pour injecter les kexts, aller sur l'onglet "System Parameters" et mettez l'option Inject Kexts sur Yes comme ceci :
       

       
       
      Voilà, vous n'avez plus qu'à enregistrer les ajustements, redémarrer votre pc et apprécier le résultat.
       
       
      MAIS ... seulement voilà ... il y a un problème ... 
       
      Quoi ? 
       
      Initialement, les kexts ne sont pas présents dans le kernelcache à cause de "OSBundleRequired=Safe Boot" (ils ne sont pas chargés en local par défaut mais en mode sans échec) et donc le patchage "à la volé" (on the fly) ne fonctionnera pas.
       
      Donc quoi, tout ça pour rien ?
       
      Non, bien-sûr, voici l'astuce pour remédier à cela :
       
      Dans un premier temps, il vous faut booter l'OS sans kernelcache. Si vous utiliser Clover Configurator, il vous suffit juste de cocher l'option "No Caches" dans l'onglet "System and Parameters" ou bien vous le faites directement dans votre config.plist :
      <key>SystemParameters</key> <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key>       <string>Yes</string>       <key>NoCaches</key>       <true/> </dict> Ceci aura donc pour effet de bloquer kernelcache et obliger boot.efi de charger le kernel et les kexts séparément. Clover et FSInject vont ensuite intercepter tous les chargements des kexts par boot.efi et changer "OSBundleRequired=Safe Boot" en "OSBundleRequired=Root" à la volé (on the fly) et forceront boot .efi à charger les kexts. Et ensuite dans un second temps, Clover va patcher l'Info.plist de ces deux kexts et la partie binaire de ATIRadeonX2000, kernel va les charger et ils seront rattachés à votre carte graphique.
       
      Une fois ceci fait (donc les kexts utilisés), il vous suffit de faire sudo touch /System/Library/Extensions. Ceci créera un nouveau kernelcache qui cette fois-ci contiendra vos kexts utilisés. Ensuite il ne vous reste plus qu'à redémarrer normalement (en décochant l'option No Caches dans Clover Configurator) et le patch fonctionnera à merveille.
       
       
      Oui, mais ... là aussi ...
       
      Quoi encore ?
       
      Seulement voilà, pour une raison ou une autre, il peut arriver que kernelcache se reconstruit tout seul et le patch "à la volé" ne fonctionne plus.
       
      Alors je fais quoi moi en attendant ?
       
      L'astuce la plus efficace pour le moment est d'injecter les infos de vos kexts à l'intérieur de l'Info.plist de FakeSMC.kext comme des IOKitPersonalities additionnels.
       
      ????Kézako????
       
      Ces infos vous les trouverez dans l'Info.plist de ces 2 kexts, sous IOKitPersonalities. Les voici :
       
      Pour AMD4800Controller.kext
      <key>Controller</key> <dict>         <key>ATY,Cardinal</key>         <dict>                 <key>aty_config</key>                 <dict>                         <key>CFG_NO_PP</key>                         <true/>                 </dict>          </dict>          <key>CFBundleIdentifier</key>          <string>com.apple.kext.AMD4800Controller</string>          <key>IOClass</key>          <string>AMD4800Controller</string>          <key>IOMatchCategory</key>          <string>IOFramebuffer</string>          <key>IOName</key>          <string>AMD4800Controller</string>          <key>IOPCIMatch</key>          <string>0x94401002 0x944a1002</string>          <key>IOProbeScore</key>          <integer>65050</integer>          <key>IOProviderClass</key>          <string>IOPCIDevice</string>         <key>aty_config</key>          <dict>                 <key>CFG_NO_PP</key>                  <false/>                  <key>CFG_PAA</key>                  <integer>0</integer>                  <key>CFG_USE_USCN</key>                  <false/>          </dict>          <key>aty_properties</key>          <dict>                  <key>PP_GFXClockGatingEnabled</key>                  <integer>1</integer>          </dict> </dict> Et pour ATIRadeonX2000.kext
      <key>ATIRadeonX2000</key> <dict>         <key>ATIEnableWideBlitSupport</key>         <true/> <key>ATIUseTearingWideBlit</key> <false/> <key>CFBundleIdentifier</key> <string>com.apple.ATIRadeonX2000</string> <key>GpuDebugPolicy</key> <integer>0</integer> <key>IOCFPlugInTypes</key> <dict> <key>ACCF0000-0000-0000-0000-000a2789904e</key> <string>ATIRadeonX2000GA.plugin</string> </dict> <key>IOClass</key> <string>ATIRadeonX2000</string> <key>IODVDBundleName</key> <string>ATIRadeonX2000VADriver</string> <key>IOKitDebug</key> <integer>0</integer> <key>IOMatchCategory</key> <string>IOAccelerator</string> <key>IOPCIMatch</key> <string>0x94001002 0x94011002 0x94021002 0x94031002 0x95811002 0x95831002 0x95881002 0x94c81002 0x94c91002 0x95001002 0x95011002 0x95051002 0x95071002 0x95041002 0x95061002 0x95981002 0x94881002 0x95991002 0x95911002 0x95931002 0x94401002 0x94421002 0x944A1002 0x945A1002 0x94901002 0x949E1002 0x94801002 0x95401002 0x95411002 0x954E1002 0x954F1002 0x95521002 0x95531002 0x94a01002</string> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>8.24.11</string> <key>IOVARendererID</key> <integer>16908288</integer> <key>sensor-properties</key> <array> <dict> <key>device_type</key> <data> Z3B1LXNlbnNvcg== </data> <key>location</key> <string>GPU</string> <key>name</key> <string>gpu-sensor</string> <key>polling-period</key> <data> AAAAAQAAAAA= </data> <key>reg</key> <data> AAAAAg== </data> <key>sample-period</key> <data> AAAAAACYmAA= </data> <key>sensor-id</key> <data> AAAABg== </data> <key>version</key> <data> AAAAAg== </data> <key>zone</key> <data> AAAAAg== </data> </dict> </array </dict>  
      Et voici donc l'Info.plist de FakeSMC.kext dans son intégrité, vous pouvez jeter un oeil, histoire de voir à quoi cela ressemble :
       
      FakeSMC_Info.plist.zip
       
      Et pour les moins casse-têtes, voici FakeSMC.kext modifié que j'utilise pour charger les 2 kexts :
       
      FakeSMC.kext.zip
       
       
      Voilà, avec ceci, vous n'aurez plus besoin de savoir si oui ou non les kexts sont dans le kernelcache.
       
       
      Crédits attribués à :
       
      netkas  pour son incontournable QE_CI Exotic patch (même s'il n'importe plus son support)
       
      Slice  & co. pour leur bébé nommé Clover
       
      dmazar  pour son astuce avec FakeSMC.kext   (pour plus d'info, voir ici)
       
      duffs (rarement ici, plus sur le site de netkas) pour son astuce de comment patcher la partie binaire avec Clover, ce fût lors de la sortie de OS X Mavericks DP1
       
      nyolc8  pour le support de QE_CI Exotic patch pour Mavericks
       
      fantomas1  pour ......... pour ... quoi déjà ? Ah ben non ... non ... pour rien ...
    • By Slice
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
       
×