Jump to content

9 posts in this topic

Recommended Posts

Hi insanelymac and all users, i have been trying to update my hackintosh from Yosemite 10.10.5 to Mojave with a fresh install but haven't managed.

My question is:

is it possible to install Mojave on a old system like mines.


Assus p5k pro motherboard

LGA socket 775 intel Extreme x9650 cpu

GeeForce 8600 GT Graphics

Sata harddrive


I have Mojave install that i downloaded from the app store 6.03 size.

The problem i have ............

when i try and boot from the usb it does not boot at all, just a black screen with a cursor flicking top left screen, i have used Clover to make a bottable usb Mojave also i have used Mojave Patcher Tool for Unsupported Macs and still the same issue, i do have a bit of knowledge and not a complete newbie, im starting to think maybe Mojave is not possible to install on my machine due to old motherboard and i dont have much settings to play with regards to whats required in bios.


any help or advice would be much appreciated as i need this update badly as my old software wont upgrade on Yosemite and i don't have funds to buy a new machine.

Edited by smurff

Share this post

Link to post
Share on other sites

Yes, you can install recent macOS versions on that platform. However, that old nVidia card is obsolete for Mojave and you should consider replacing it by something more modern like an nVidia Kepler card (the only nVidia cards supported in Mojave) or an AMD model (GCN1.0 minimum).


C2D/C2Q platforms require a few adjustments/tricks to run Mojave:

1) the use of a Mojave-compatible SMBIOS (eg: iMac13,x) instead of good old iMac8,x/9,x/10,x that are unsupported

2) replacement of the telemetry plugin that causes KP and restart on non-SSE4.2 CPUs


See here for instance. You don't need to bother with the Mojave patcher tool.


Edited by Hervé

Share this post

Link to post
Share on other sites

Thank you InsanelyMacaholic thats why the installer wont start, i will give it another try in a mo and i will post my out come here.

Share this post

Link to post
Share on other sites
On 2/7/2019 at 4:42 PM, smurff said:

Thank you InsanelyMacaholic thats why the installer wont start, i will give it another try in a mo and i will post my out come here.

Post Update .... installed thanks herve, i used a legacy option and all went well, now i will try and fix kexts

Share this post

Link to post
Share on other sites

I counted my hens before they hatched .... its installed but not fully, im stuck on the last part where you input your language, my machine just restarts before that opens, i havent figured out how to copy the telemetry plugin.

I have 2 internall sata drive and the USB attached to the machine.

i press f8 to choose where to boot from.

i believe from looking at the location where the telemetry plugin should be placed is on the drive of new Mojave install

if i boot into my OS yosemite i dont see the hard drive where Mojave is installed, i can open clover configurator and mount the EFI folder and thats all i can do.


Do i open terminal after booting from my USB


I can live with updating the telemetry.plugin every update :)

Share this post

Link to post
Share on other sites

Im getting error using the -Rf command? Unkwon syntax


ive uploaded 2 pictures, one with -Rf command and one without, i dont get error if i dont use the -Rf command but as you see it says cant find file on USB, the name of the USB is USB when i formatted the USB, ive placed the telemetry plugin inside the USB in zip and also extracted.


im obviously not getting the location correct using the shell to copy, please advice me how thanks.



Edited by smurff

Share this post

Link to post
Share on other sites

OMG... What shell is this? Clover's?


Can't see how you can get it wrong if you follow the guidance I linked you to...



  1. copied the telemetry plugin to the root of your USB installer
  2. booted the USB installer
  3. opened up Terminal app

you're meant to copy the telemetry plugin using the following command and syntax:

cp -Rf /com.apple.telemetry.plugin /Volumes/<name of target Mojave partition>/System/Library/UserEventPlugins/

where <name of target Mojave partition> is the name you gave to your Mojave partition. It seems you're not doing that...

Edited by Hervé

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 Bikash
      I am trying to install macOS Mojave in my laptop but the is very slow.. I tried different methods and tutorials but all have same result.
      Install of High Sierra, Sierra and El capitan is fast and have no issue.
      hp notebook v5d75pa#acj
      Intel HD 4400
      4gb ram ddr3
    • By TorqueX86
      Hi guys,

      I'm at my wit's end. I really need a hand here.
      I found only one clover setup for my motherboard, and works absolutely flawlessly for Mojave.

      Today I added an Asus Thunderbolt EX3 card, and that won't even let me boot my Mojave installation.

      My config.plist in attachment. Let's solve at least the Thunderbolt issue for now.
      There are also other issues, but let's solve this one first.
      Asus WS Z390 PRO + i9 9900K
      32GB 3200
      Nvidia 2080Ti for Windows and AMD RX480 for MacOS.
      Samsung NVME 950PRO
    • By arsradu
      Hi guys,
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

      With that being said, I'll just move on to the actual tutorial.
      New (probably better) method.
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
      A simple Lilu plugin
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
      More info can be found in this post here.
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext (alongside Lilu.kext) and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
      For ATI GPUs (curtesy of @Cyberdevs' post here).
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
      For NVIDIA GPUs (tested on my old MSi GTX 650)
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
         For MSi motherboads (check out my motherboard details in the signature)
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
         For Gigabyte motherboards
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
      Thanks to @gjw for the tip.
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
    • By tlefko
      Now updated for 10.13.6+ Designed for i7 Skylake, QHD+, 256/8GB memory
      you may want to disable Configure BIOS settings for EFI Booting. Disable RAID, enable AHCI, virtualization, make sure VRAM is over 32. and you should be set. also disable secure boot and enable UEFI booting You should create an EFI folder onto the USB and copy the contents of the USB onto the drive Boot off the usb using external mouse/keyboard (if required) and follow the installer prompts boot off the MAC HDD NOTES
      You may want to remove the DSDT patches if you have an issue. and manually repatch. however if you have the same model it should not be an issue. POST INSTALL
      Copy the folders from the root of the USB onto the computer efi folder. NOTES
      Some sleep bugs Tested with 10.13.6, not with 10.14 DSDT patches may have an issues if not the same model, you can remove them if there is an issue. CREDITS
      @Rehabman @maz-1 @syscl @darkvoid SUPPORT
      feel free to ask questions / open answers, you can also check out my other repository covering a previous mac version for the same model for other files for that / information on this topic Files.zip
    • By eraser0
      Hi Happy new YEAR 
      My laptop doesn't sleep at all
      sometime it sleeps with darkwake=0,1,2 but leads to shutdown
      other arguments the screen just turns off and it keeps running 
      this is my conflig plist if anyone would help me