macOS 10.14 Mojave on Unsupported Macs Thread

[Czo]

I think you guys have convinced me that I need to give up on my old MBP. I can use Xcode 10 it looks like for another year with 10.13.x. That will tide me over until the next MBP refresh, hopefully with 10 nm Intel processors. The XC10 beta runs under 10.13.4 and macOS compatibility is usually maintained through release. The main problem with that is that backward compatibility often isn't very good, and running on less than the most current macOS is buggy with bugs that Apple never gets around to fixing.

It would have been tricky using a hacked version of Mojave with Xcode in any case since you have to face Apple's developer portal to enable code signing etc. Don't know how carefully Apple checks developer hardware. Wouldn't want to get my hands slapped or my license revoked.

For what it's worth, I wish Apple would legitimize the Hackintosh community with either an open source version of macOS or a licensed generic version. There's so much passion and skill going into this that it's a shame that Apple doesn't recognize its value. Good luck everyone.

Xcode run's fine from Hackintosh and also from unsupported Macs with Sierra (and any unsupported Mac in the past, because i'm used it on my iMac4,1 (to develop iOS Apps) with replaced a CPU and Firmware on 10.8.5 (officially 10.6 is the last on that Mac)). You can run Xcode 10 on 10.13 until next February (or March) because when iOS 11.3 come out, Xcode 9.3 raises it's requirements to 10.13 (same as with iOS 10.3 + Xcode 8.3 because it's now requires Sierra).

 

[BerenErchamion]

Thanks, Czo. That's good to know. My main reason for waiting is to take advantage of new 10 nm Intel processors. I hope Intel gets those out the door by next March time frame. But no telling when Apple will update MBP.

Seems like the main Mojave stumbling block is still OpenGL. I'll watch this thread for developments. Thanks again.

 

[jackluke]

Just to clarify, with hd3000 “partially supported” I meant capable of running MacOS GUI, manage Finder folders, launch Terminal, disk utility, dmg creation, pkg expander, safari simply browsing, for only testing purpose, not high-end graphics use, while regarding AMD 6000 series I thought was OpenGL 4.x ready so through a web driver supposed, my mistake.

I have pointed up previously that High Sierra is the best suite for the latter old supported macs.

I wanted to add regarding xcode, sometimes I take github sources and do some sideloading tests on my ipad, I noticed that ios app store users often prefer old libraries compatible apps, so for some xcodeproj can still copy into the xcode.app packages’s DeviceSupport subfolder the last ios folder with developerdiskimage.img and .signature if don’t need a total version update.

For example I have sideloaded a xcode project in xcode 9 beta to an ios 11.4 device, just adding in that path the missing “11.4 (15F5037c)“ folder with those two files inside.

Just a gag, after macos 10.15 and ios 13 merged in universal app store no more intel 10nm but arm only and 2020 is not so far.

 

[Starplayr]

[QUOTE="after macos 10.15 and ios 13 merged in universal app store no more intel 10nm but arm only and 2020 is not so far.[/QUOTE]

This is not true, at WWDC 2018, Apple stated they have no intention on Merging iOS with macOS. They will offer an easier method to port iOS Apps to macOS, but they will still use macOS controls.

Apple has switched platforms in the past but the larger they get, the harder is to make architecture changes without disrupting the entire food chain. Even if Apple starts making their own chips for its desktops, I don't think they will be ARM based; most like x86_64 based but just with an Apple Logo on the chips and their design.

Quite frankly, if Apple required me to toss out my Mac Pro hardware, I'll probably just use Windows 10 which is supported on Mac Pros and run the tools in a VM which currently works. Will see what the future brings us. If Mojave can't run on my 2008 Mac Pro, I still have one 2012 Mac mini, quad core and its still a beast when it comes to software development. I recently got some 2008 Mac Pros for next to nothing and they run faster than my Mac mini does. So, naturally I'd like to use them full time for future iOS and Mac software development. I'll upgrade to a 2009/2010/2012 Mac Pro if I have to. All of my hardware excluding the RAM will move forward.

 

[jackluke]

[QUOTE="after macos 10.15 and ios 13 merged in universal app store no more intel 10nm but arm only and 2020 is not so far.

This is not true, at WWDC 2018, Apple stated they have no intention on Merging iOS with macOS. They will offer an easier method to port iOS Apps to macOS, but they will still use macOS controls.

Apple has switched platforms in the past but the larger they get, the harder is to make architecture changes without disrupting the entire food chain. Even if Apple starts making their own chips for its desktops, I don't think they will be ARM based; most like x86_64 based but just with an Apple Logo on the chips and their design.

Quite frankly, if Apple required me to toss out my Mac Pro hardware, I'll probably just use Windows 10 which is supported on Mac Pros and run the tools in a VM which currently works. Don't know about the future.[/QUOTE]

You haven’t quoted “just a gag” but it’s fine.

 

[Starplayr]

ok. has anyone gotten the GUI (accelerated or non-accelerated) to work on a Mac Pro 2008. And if so, which Kexts are you modifying to get it to work.

The farthest I have gotten was to the Arrow with the gray new user screen. Then it reboots. I have not tried a system that was cloned from a working Mac yet. Just wanted to know if anyone has gotten farther on the 2008 model.

I did get Mojave's Mac OS X Installer to boot up (and install from it) and the next time I get it to do that, I may look at its system and see if it reveals anything because that Mac OS X installer should be running an slim version of Mojave and that may give some more clues.

Just wondering if any other 2008 Mac Pro users have gotten done so far.

 

[jackluke]

ok. has anyone gotten the GUI (accelerated or non-accelerated) to work on a Mac Pro 2008. And if so, which Kexts are you modifying to get it to work.

The farthest I have gotten was to the Arrow with the gray new user screen. Then it reboots. I have not tried a system that was cloned from a working Mac yet. Just wanted to know if anyone has gotten farther on the 2008 model.

I did get Mojave's Mac OS X Installer to boot up (and install from it) and the next time I get it to do that, I may look at its system and see if it reveals anything because that Mac OS X installer should be running an slim version of Mojave and that may give some more clues.

Just wondering if any other 2008 Mac Pro users have gotten done so far.

Had a similar issue with a unibody Macbook 2010, if you can boot a Mojave installer right after the power on from a partition or usb external then it’s like a half way slim Mojave, I suppose there is some kext or service that kills all processes resulting in reboot, but I am afraid that is due to a missing or invalid EFI firmware update check, as I said if fixed this then you could boot GUI even without a GPU kext just like the slim Mojave installer.

You could try to use all the Extensions folder of the installer instead of the installed S/L/E Mojave, and see what happens, or better try to boot holding shift key at boot targeting Mojave disk, because safe mode sounds like an installer emergency extensions loaded. This is my opinion.

 

[Starplayr]

The challenge in this thread I guess is also to successful install Mojave beta 1 directly on an unsupported mac but this implies a risky EFI firmware update, so that’s why is preferrable to install it from a supported mac or inside a virtual machine supported mac and then cloning elsewhere.

This is not recommended, I was a able to install Mojave natively by modifying the System Information using Clover v2 on a 2008 Mac Pro. Unfortunately, I switched my system from a quad core to and eight core and I have not been able to redo the System Information that is reliable again. I also wiped out my previous Clover boot partition. I may trace my steps back on the quad core model and see what works and what doesn't. When I had it emulating a Mac mini 2012, I was able to install it natively. What it did was download and run the installer, it created the install disk and then I was able to boot up Mojave's Mac OS X Installer from Clover 2 using the same 2012 Mac mini settings. But it must have been beginners luck as I get lots of unsupported CPU errors at the end of a verbose boot now. So using Clover v2 on a real unsupported Mac is not recommended. That said, it is possible to "hack" a boot loader and get the system thinking its a different Mac. The default clover setting does this as an iMac10,1 and that config works but it's not enough to run the installer natively. Using Clover is an interesting experiment and I actually like the boot loader. You can use it with your native config installed as a Real Mac matching your System info with it and use it for additional boot arguments, oodles of settings, and basically run it properly. Its multi boot features are very nice.

 

[BookEmDanno]

what work HD 3000 Graphics? I copied this kexts for high Sierra, but it loading in black screen. How you fix it?

Try installing the hd3000 bundle and plugin files as well. See my original post screen shot for all the files needed (if missing). Install location is on /System/Library/Extension.

Good luck.

BTW, what is your Mac's model that you are trying Mojave on?
[doublepost=1529356185][/doublepost]

Does anyone know if I can format an external SSD in APFS with Mojave?

If you don't mind erasing the contents of the SSD, you can use Disk Utility to do so. It should show a dropdown selection that includes all available formats.

 

[jackluke]

This is not recommended, I was a able to install Mojave natively by modifying the System Information using Clover v2 on a 2008 Mac Pro. Unfortunately, I switched my system from a quad core to and eight core and I have not been able to redo the System Information that is reliable again. My only guess currently is the quad Core had more latitude but that is only a guess at this time. I also wiped out my previous Clover boot partition. I may trace my steps back on the quad core model and see what works and what doesn't. When I had it emulating a Mac mini 2012, I was able to install it natively. What it did was download and run the installer, it created the install disk and then I was able to boot up Mojave's Mac OS X Installer from Clover 2 using the same 2012 Mac mini settings. But it must have been beginners luck as I get lots of unsupported CPU errors at the end of a verbose boot now. So using Clover v2 on a real unsupported Mac is not recommended. That said, it is possible to "hack" a boot loader and get the system thinking its a different Mac. The default clover setting does this as an iMac10,1 and that config works but it's not enough to run the installer natively. Using Clover is an interesting experiment and I actually like the boot loader. You can use it as a Mac Pro 3,1 with it and use it for additional boot arguments and basically run it properly. And its multi boot features are very nice.

You are very brave to use Clover on a real mac, have to admit with Clover bootloader you can do everything, but be careful, I suggest in config.plist to not use too many patches you risk to corrupt the firmware.scap, anyway with Clover there are more chances to boot Mojave from an unsupported mac, I think you are one of earliest to successfully boot a Mojave installer directly from an unsupported mac. Maybe I will attempt too on a sacrifying old macbook.

No matter cpu unsupported with Clover you can boot it regardless the error, I advice you to don’t use the Clover pkg it’s risky on a real mac, maybe safer to mount ESP partition and copy manually the Clover folder into the EFI folder mounted.

Advice for everyone, unless you are very expert and know what are doing, don’t use Clover on real mac, neither mount ESP, very very dangerous.

 

[Starplayr]

For what it's worth, I wish Apple would legitimize the Hackintosh community with either an open source version of macOS or a licensed generic version. There's so much passion and skill going into this that it's a shame that Apple doesn't recognize its value. Good luck everyone.

Apple tried licensing macOS before OS X and it nearly lost its ass doing so. When Steve took over, it nixed all the third party hardware manufacturers and Apple stopped licensing Mac OS 8 and 9.

What Apple should do is have a 10 year plan for all of its hardware. They make the hardware. They write the OS. If Microsoft can support stuff for like 15 years, Apple should do at least 10. Heck make it 15, even if it does not have all the features give them at least an @home version.

I think most of us invested in Mac hardware for 10-20 years and the speeds are not getting any faster and their built in video cards pale in comparison to what PCIe cards can do today. So Apple needs to step up and support its own systems longer much longer. And if they showed up some love maybe we'll show some back and buy another Mac every once in awhile.

Now look at the Mac Pro 6,1. It's 2013 tech sold as 2018 tech today. Apple is screwing those customers.

Support real hardware longer. True Mac fans today are not buying brand new Macs. The rich might, but I'm not.
[doublepost=1529359559][/doublepost]

You are very brave to use Clover on a real mac, have to admit with Clover bootloader you can do everything, but be careful, I suggest in config.plist to not use too many patches you risk to corrupt the firmware.scap, anyway with Clover there are more chances to boot Mojave from an unsupported mac, I think you are one of earliest to successfully boot a Mojave installer directly from an unsupported mac. Maybe I will attempt too on a sacrifying old macbook.

No matter cpu unsupported with Clover you can boot it regardless the error, I advice you to don’t use the Clover pkg it’s risky on a real mac, maybe safer to mount ESP partition and copy manually the Clover folder into the EFI folder mounted.

Advice for everyone, unless you are very expert and know what are doing, don’t use Clover on real mac, neither mount ESP, very very dangerous.

Right, so far on my Eight core the SMBIOS setting seem to be really picky. Both my Quad Core 2.8 Ghz 2008 Mac Pro and my Eight Core 3.2 Ghz 2008 Mac Pro were given to me cheap. So if I tear one up its not a huge loss. My changes are minimal. It's weird that the default config of clover's iMac setting and firmware work out of the box. So does the Mac Pro 3,1 settings. Mac Pro 5,1 settings the Eight core reboots with after unsupported CPU messages on the 8-core. Going to go back to the Quad and try to perfect some magic there and see if it was beginners luck.

I've been looking for ways to do the same thing without using Clover. I found you can change the Computer name like "MacBook Pro (Retina, 15-inch, Mid 2014) to something else in a .plist file. I have not found where that can be changed in the System Report of if you can change via .plist if the store will see it or not. Clover when it works does a great job changing those values out and the downloader and store will think you are on a real system. And its install disk is bootable. Could also try making a boot disk from the installer from the command line.

Update:

Okay, I figured out what "patches" I needed to get a Mac Pro 3,1 to mimic any Mac under the sun using Clover v2. I am currently have it set to Mac Pro (Late 2013) Mac Pro 6,1. How it Did it was, do a very basic install of Clover v2 on an GUID Partition, preferably one that you can blow up. Mine is a super old ATA drive that I keep in the spare bay. This is great place to put a bootloader disk. After realizing the default config.plist for in the Clover folder booted up and did its thing as an iMac. I then just duplicated and modified that file using Clover Configurator (Global Edition) and only change the SMBIOS to that Mac that you want to be like. Now there are several ACPI flags that clover sets automatically, simply leave all that stuff alone and your Mac Pro 3,1 can now be a Mac Pro 5,1 6,1 Mac mini etc etc. Will try the same config.plist on my Eight Core and see if it does the same thing. Now there may be a flag that we need for Mojave. My next step is to redownload Mojave , reinstall and possibly clone its installer disk when it makes one to capture its base system to see if anything can be learned from it. And also I will install High Sierra without any patches and see how it goes too. I am hoping to uncover something great. I'm actually gonna work with High Sierra first for a bit to see what I can learn along the way and might make it easier to get Mojave running on the Mac Pro 3,1 there after.

 

[iphone2g&3gfan]

I don't know. I think, this is the "feature", that any dual GPU MBP owner seeing (switching between GPU's). The dGPU renders it's framebuffer to IGP's framebuffer.

Believe it or not, that's not how the MBP works. That would be correct for Nvidia optimus on windows laptops, where the nvidia gpu has no display outputs and it just copies the framebuffer to the IGP.

MacBook pro's use a dedicated chip called the 'gMux' that can ACTUALLY SWITCH THE LVDS/DP ON THE FLY. I know this because the screen flickers and the colors flicker for a millisecond when they switch on macOS, and on linux, I know this because at the GRUB bootloader I can write to certain memory addresses to activate the nvidia or intel EXCLUSIVELY, without any framebuffer tricks. The nvidia also drives the displayport output on linux when switched to in GRUB, and it doesn't in macOS.

I also know this on linux because I can do 'xrandr' and see the nvidia gt 330m and the intel arrandale (for my 2010) and each one has lvds outputs, and when I switch between them in grub, the LVDS output that's active changes.

Since the newer macbook pros use the same gMux chip, we just need to worry about getting the individual cards' kexts loaded. macOS will take care of the rest for us!
[doublepost=1529369010][/doublepost]

NO! Intel HD 3000 and AMD 6000 series can't support Metal. So Metal and Metal based app's can't be used with Macs that contains anything, that older than Intel HD4000, AMD GCN, nVidia Fermi.

Mac's with thunderbolt can use eGPU's but that can't help with Macs with dedicated GPU's (like MacBook Pro's and iMacs and some Mac Minis). On that machines, the eGPU can only display the picture on the screen connected to eGPU (i have a thunderbolt - PCI-E box). On Mac's with Intel GPU only, the picture can be display on internal screen too (tested on 13" MBP from 2011 in High Sierra). But, on that 13" MBP, under Mojave the eGPU works only with external screen. I think, the "framecopy" feature requires a fully working accelerated Intel HD graphics (because, this works fine with a retina 2015 MBP with the same box and with the same eGPU).

For the iMacs without thunderbolt, those all have a standard mini pcie airport card (AR9380) and you can just use a cheap mini-pcie to pcie riser. Some mac minis have the standard mini pcie airport, I think the newer ones have the proprietary connector but that connector does have a pinout which I posted a few posts ago.
[doublepost=1529369324][/doublepost]

ok. has anyone gotten the GUI (accelerated or non-accelerated) to work on a Mac Pro 2008. And if so, which Kexts are you modifying to get it to work.

The farthest I have gotten was to the Arrow with the gray new user screen. Then it reboots. I have not tried a system that was cloned from a working Mac yet. Just wanted to know if anyone has gotten farther on the 2008 model.

I did get Mojave's Mac OS X Installer to boot up (and install from it) and the next time I get it to do that, I may look at its system and see if it reveals anything because that Mac OS X installer should be running an slim version of Mojave and that may give some more clues.

Just wondering if any other 2008 Mac Pro users have gotten done so far.

Just throw in a native metal card (Radeon HD 7xxx+/Nvidia Kepler). DONT get a maxwell or pascal card yet since the only nvidia arch supported by the stock kexts is kepler. While 6xx and 7xx ARE kepler, some of the lower end cards are rebadged Fermis, which you should avoid AT ALL COSTS.

https://en.wikipedia.org/wiki/GeForce_600_series
https://en.wikipedia.org/wiki/GeForce_700_series

Go to the table at the bottom and make sure the "Code name" starts with "GK". If it starts with anything NOT GK like GF or GM, then do not buy that card. if that card has multiple revisions, some of which are kepler and some are not, avoid that card to avoid getting lucky and getting a fermi or maxawell.

 

[FNH15]

As an owner of a 2011 27 inch iMac, I want to thank all the people on this forum who are diligently trying to get 10.14 to install on unsupported Macs. What can I contribute to the effort? I have a valid developer account, a machine where Mojave is officially supported (the rBMP in my sig), and a bit of time on my hands .

 

[Starplayr]

Update:

Okay, I figured out what "patches" I needed to get a Mac Pro 3,1 to mimic any Mac under the sun using Clover v2. I am currently have it set to Mac Pro (Late 2013) Mac Pro 6,1. How it Did it was, do a very basic install of Clover v2 on an GUID Partition, preferably one that you can blow up. Mine is a super old ATA drive that I keep in the spare bay. This is great place to put a bootloader disk. After realizing the default config.plist for in the Clover folder booted up and did its thing as an iMac. I then just duplicated and modified that file using Clover Configurator (Global Edition) and only change the SMBIOS to that Mac that you want to be like. Now there are several ACPI flags that clover sets automatically, simply leave all that stuff alone and your Mac Pro 3,1 can now be a Mac Pro 5,1 6,1 Mac mini etc etc. Will try the same config.plist on my Eight Core and see if it does the same thing. Now there may be a flag that we need for Mojave. My next step is to redownload Mojave , reinstall and possibly clone its installer disk when it makes one to capture its base system to see if anything can be learned from it. And also I will install High Sierra without any patches and see how it goes too. I am hoping to uncover something great. I'm actually gonna work with High Sierra first for a bit to see what I can learn along the way and might make it easier to get Mojave running on the Mac Pro 3,1 there after.

I was able to install High Sierra on an Eight Core Mac Pro 3,1 without installing any physical patches on the system. Using only Clover v2 boot loader on a separate partition to install High Sierra. The installer ran (used the installer from DosDude1's setup which is really an unmatched installer until you run some patches on it). Then I loaded its emergency drive, unmatched. worked. Next booted into the unpatched High Sierra 10.13.5 and no issues. Next will be trying out the High Sierra Beta 10.13.6 Beta 2 and also Mojave Beta 10.14 as well on this system. That's really some good progress. And hoping to get Mojave running soon on this same system. I think my video card might be causing the reboot on Mojave, so I can try some other cards that I have on hand to get it to boot from scratch.

Installing a from scratch High Sierra on another Mac and then on both Mac Pro 3,1 systems will move on to a Mojave install.

By switching Clover v2 to the Mac Mini Late 2014, I was able to get full video acceleration in High Sierra with NVIDIA's drivers. Still no patches. Mac Pro 6,1 and Mac Pro 5,1 configs would not output video or would reboot. Using a fresh EFI Boot loader.

Going to download Mojave and cross some fingers.

 

[Starplayr]

I am able to boot up the recovery 10.14 partition with Clover. so it’s generic boot loaders work there with my video card. did a complete install with Clover of 10.14. The beta has two additional preboot hidden partitions. One is for file vault and the other if for an installer. The installer one crashes. The file vault one does boot.still getting a crash at the arrow. Happy to get the recovery petition to boot up. Seems to be video driver or I need to pick another Mac config.

 

[volodi]

Try installing the hd3000 bundle and plugin files as well. See my original post screen shot for all the files needed (if missing). Install location is on /System/Library/Extension.

Good luck.

BTW, what is your Mac's model that you are trying Mojave on?

It MacBook Air 13 Mid 2011, i copythe hd3000 bundle and plugin files in /System/Library/Extensions

 

[jackluke]

I am able to boot up the recovery 10.14 partition with Clover. so it’s generic boot loaders work there with my video card. did a complete install with Clover of 10.14. The beta has two additional preboot hidden partitions. One is for file vault and the other if for an installer. The installer one crashes. The file vault one does boot.still getting a crash at the arrow. Happy to get the recovery petition to boot up. Seems to be video driver or I need to pick another Mac config.

The recovery partition is just like the installer from them you can do almost the same things, rather I’d say an usb installer (I mean with Basesystem.dmg expanded on it) is far better is more customizable, while the recovery is hidden and has preboot dmg very locked and not easy to match signature if also able to modify the dmg inside.

While Preboot partition also used to boot main macOS was introduced since High Sierra and it needs to support booting to an APFS volume.

 

[BookEmDanno]

It MacBook Air 13 Mid 2011, i copythe hd3000 bundle and plugin files in /System/Library/Extensions

So is it working out for you now (as far as graphics and sound are concerned) ?

 

[jackluke]

I was able to install High Sierra on an Eight Core Mac Pro 3,1 without installing any physical patches on the system. Using only Clover v2 boot loader on a separate partition to install High Sierra. The installer ran (used the installer from DosDude1's setup which is really an unmatched installer until you run some patches on it). Then I loaded its emergency drive, unmatched. worked. Next booted into the unpatched High Sierra 10.13.5 and no issues. Next will be trying out the High Sierra Beta 10.13.6 Beta 2 and also Mojave Beta 10.14 as well on this system. That's really some good progress. And hoping to get Mojave running soon on this same system. I think my video card might be causing the reboot on Mojave, so I can try some other cards that I have on hand to get it to boot from scratch.

Installing a from scratch High Sierra on another Mac and then on both Mac Pro 3,1 systems will move on to a Mojave install.

By switching Clover v2 to the Mac Mini Late 2014, I was able to get full video acceleration in High Sierra with NVIDIA's drivers. Still no patches. Mac Pro 6,1 and Mac Pro 5,1 configs would not output video or would reboot. Using a fresh EFI Boot loader.

Going to download Mojave and cross some fingers.

You have put Clover on another mac? Again, you are very very brave and maybe a bit lucky.

I have to discourage the others to do it, Mac boot chime sound is everything for a mac, if you play too much with Clover you risk to hear no more that funny sound.

 

[stormxeron]

I have to discourage the others to do it, Mac boot chime sound is everything for a mac, if you play too much with Clover you risk to hear no more that funny sound.

Haha. I always liked that sound, but my internal speakers are damaged so its not exciting for me anymore.
Does anybody know how to permanently disable that sound?..without Clover(ie. mess)

 

[jackluke]

Haha. I always liked that sound, but my internal speakers are damaged so its not exciting for me anymore.
Does anybody know how to permanently disable that sound?..without Clover(ie. mess)

Apart power off a mac setting on Mute volume, from terminal could give:
sudo nvram SystemAudioVolume=%80

While this to restore default sound:
sudo nvram -d SystemAudioVolume

But I repeat startup chime is useful, I remember an old MBA with faulty RAM, without speaker’s beeps I thinked was the battery or weak magsafe cable.

 

[Starplayr]

You have put Clover on another mac? Again, you are very very brave and maybe a bit lucky.

I have to discourage the others to do it, Mac boot chime sound is everything for a mac, if you play too much with Clover you risk to hear no more that funny sound.

Yes. I don't recommend doing this. I do have High Sierra 10.13.5 fully functioning with Clover (and just using clover to get it to run, no patched ktexts, etc). Was able to install Mojave via clover. I was not able to get it install disk to mount within HS, as I wanted to inspect it. Will try making a USB installer later. I think there is a way to mount the recovery partition. I am able to boot APFS via Clover. And am able to try different builtin SMBIOS settings with Clover Configurator (whatever its actually called). The system still stops when it gets to the initial new Mac login gray screen and arrow. Have not been able to safe boot it yet. verbose works, I get some ACPI errors that I don't get in High Sierra. My video card is a Titan X Maxwell, so that is probably my issue. Will try HS Web drivers and see if I can get those to load. Will also try my AMD Radeon 7xxx card and my stock Nvidia card to see if I can at least get into the system.

I am really happy having an unpatched High Sierra running. The only thing I have to deal with are Nvidia drivers. I think the same should. be achievable when the Mojave 10.14 GM comes out. Clover also has tons of cool themes!

The Clover I am using is pretty generic which is allowing me to reproduce stuff easily and your suggestions have helped.

Does anyone know if Nvidia releases beta drivers for macOS betas?

Running Clover on only 2008 Mac Pros. Main reason I started trying this is I have having EFI boot issues with Windows on this model and then it lead to, hey maybe we can get High Sierra and Mojave to boot this way. It's sorta promising.

 

[Adamscomputerrepair]

In this thread, advancements in running macOS 10.14 (Mojave) on unsupported systems will be discussed.​

June 6: There is still an OpenGL renderer, it's just intentionally disabled. we're trying to enable it.

June 7: The crash on MacPro3,1 is not caused by lack of SSE4.2 (because Mojave works on Hackintosh core 2 duos). But we don't know what it is caused by.

June 8: With replaced IOAcceleratorFamily2.kext from 10.13.5, all of the required AMD and Intel kexts can be loaded! Thanks to Czo for finding this.

June 18: I haven't had time to work on this for a while, sorry. The 2 people we asked for help seem to think that this project is stupid and unlikely to work and won't help us. There is some good news though, we got the Nvidia kexts to load. But there is still no acceleration.

June 19: After experimenting a bit trying to resolve the USB issues on MCP79/89 and older systems, I have come to the conclusion that Apple must have changed something major. Adding AppleUSBOHCI and AppleUSBOHCIPCI kexts from 10.13 causes an instant kernel panic on the older systems. Replacing EHCI and EHCIPCI kexts with 10.13 ones causes an instant kernel panic on all machines.

AMD GPUs won't work on MacPro3,1/Xserve2,1 until there is a SSE4.2 emulator, for technical reasons.

A possibility for some computers is a Thunderbolt external GPU.
This needs to be investigated more, and requires kext patches.

These facts leave the compatibility list as theoretically (with a Metal capable GPU, or HD Graphics whose kexts do load): This list is now inaccurate because of the AMD news above

• Xserve 2008 (if we can fix the crash; Nvidia GPUs only until SSE4.2 emulator made)
• Xserve 2009
• Mac Pro 2008 (if we can fix the crash; Nvidia GPUs only until SSE4.2 emulator made)
• Mac Pro 2009
• iMac Mid-Late 2011 (Thunderbolt GPU only)
• MacBook Air Mid 2011
• MacBook Pro i5/i7 Mid 2010-Late 2011 (only the ones with HD Graphics or Thunderbolt GPU, 320M/330M won't work, see above for why)
• Mac Mini Mid 2011 (only the ones with HD Graphics, or Thunderbolt GPU, not AMD; see above for why)

The following unsupported models are Thunderbolt capable:

• MacBook Pro (Early/Late 2011)
• MacBook Air (Mid 2011)
• Mac mini (Mid 2011)
• iMac (Mid 2011)

Yet a third possibility is to upgrade the MXM slot GPU on 2008-2011 (and maybe 2007 with an upgraded CPU?) iMacs. This has not been investigated yet.

Moderator Note:

Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.

Note: the person who is editing this post is (mostly) @parrotgeek1, not @dosdude1.

Listen I'd love to help but I only have a MacBook 5,2 with the GeForce 9400m. I honestly doubt it would work considering how old that graphics card really is.

 

[retta283]

Is there any hope of it working on 2007-2009 iMacs?

 

[Starplayr]

Apart power off a mac setting on Mute volume, from terminal could give:
sudo nvram SystemAudioVolume=%80

While this to restore default sound:
sudo nvram -d SystemAudioVolume

But I repeat startup chime is useful, I remember an old MBA with faulty RAM, without speaker’s beeps I thinked was the battery or weak magsafe cable.

zapping the PRAM at boot often restores the startup chime.

Cmd-Opt-P-R wait for chime then let go, unless you want to Zap it twice.