macOS 10.14 Mojave on Unsupported Macs Thread

[dosdude1]

Are you sure this is true for Mojave in particular? I found that attempting to force the dedicated GPU using the option in gfxCardStatus still results in the app and some parts of the system becoming non-responsive. Launching Photos which is known to trigger the dedicated GPU does the same.

Only the integrated GPU is identified in About This Mac where normally both would be, meaning the EFI variable is still set.

Actually, the dedicated GPU will only show in the About this Mac window when it is actively being used. Just because it's not showing there doesn't mean the NVRAM variable is still set. Is it highly recommended to remove all AMD kexts, then set the variable. GFXCardStatus hasn't worked properly since Sierra.

 

[Starplayr]

Wow, the failures are really that common? My 17" has yet to show any signs of GPU failure, but maybe it wouldn't be a bad idea to disable the dedicated GPU and just use the integrated Intel HD 3000 to avoid it reaching the same fate. I don't use the MacBook Pro for very demanding tasks.

I had a 15" MacBook Pro 2011 model, and it had its logic board replaced twice for a bad GPU. The second time it was fixed, I immediately sold it. Wasn't about to spend a third time with it.

2011 seemed to be an off year for Apple. I remember the 2010/2011 iMacs and Mac minis having drive sensors. 2012 models I believed they got rid of them. 2012 Mac minis rock. 2014 Apple started messing with the Mini product line and hasn't updated it since.
[doublepost=1529963017][/doublepost]

I’ve read everything about NVIDIA and Intel HD so far, but are there any news about ATI/AMD graphic cards? my 2010 iMac still has shabby Radeon 5750 HD Graphics and I knew from the start when I bought this machine that the graphics card will always hold it back.

So on so forth, keep up the amazing work you guys are doing here!

Well, for what its worth, the iMac can also become a Thunderbolt Monitor for a newer Mac. If it has a thunderbolt port, then it has Target Display Mode. It's kind of weird to setup and wish Apple had a better way to do it to turn it into an external display.

Here is my unsupported Equipment List:

27" iMac 2011 (running High Sierra Supported)
13" MacBook Pro 2009 (running High Sierra, dosdude1)
Mac Pro 8 Core 2008
Mac Pro Quad Core 2008

 

[redheeler]

Actually, the dedicated GPU will only show in the About this Mac window when it is actively being used. Just because it's not showing there doesn't mean the NVRAM variable is still set. Is it highly recommended to remove all AMD kexts, then set the variable.

I thought Apple had updated it in Sierra to always show both, but it seems you're right. Moved all the AMD kexts out of the Extensions folder and then set the variable, seems to be running solidly now on the integrated graphics. Only problem is that the brightness control no longer works.

Edit: I put all the AMD kexts back into the Extensions folder with the exception of AMDRadeonX3000.kext, and regained the ability to natively control the brightness. The non-responsive app issue doesn't seem to have come back.

Edit 2: Now installed and running stable on the MacBook Pro's internal SSD. I will be using it as the primary OS.

[doublepost=1529965148][/doublepost]Overall I'm happy running Mojave on this MBP with the dedicated GPU disabled, better to not have to worry about it failing. It's great that this Mac will get another year of current software, and the dark mode + other new features in Mojave.

I would still like to see AMD GPU acceleration for the 2010 / 2011 iMacs, however. I was not able to get it working on my Mid 2011 iMac using the AMD kexts from Sierra.

 

[testheit]

Got the exact same behavior which I described two or three pages ago with Mojave on a HFS+ partition (external USB drive, MBP5,1).
Why does the boot process got stuck at such a early state and why does adding LegacyUSBInjector.kext solve this issue?
What does the LegacyUSBInjector.kext do exactly?
And why does this cause later the kernel panic?
Any advice I could test or do next?

 

[dosdude1]

Got the exact same behavior which I described two or three pages ago with Mojave on a HFS+ partition (external USB drive, MBP5,1).
Why does the boot process got stuck at such a early state and why does adding LegacyUSBInjector.kext solve this issue?
What does the LegacyUSBInjector.kext do exactly?
And why does this cause later the kernel panic?
Any advice I could test or do next?

I'm currently working on C2D machines myself (got about 20 of them). So far I haven't made much progress.
[doublepost=1529967342][/doublepost]Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

 

[saudor]

I'm currently working on C2D machines myself (got about 20 of them). So far I haven't made much progress.
[doublepost=1529967342][/doublepost]Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

Thanks! i'll give it a shot on my macbook pro 2010 15 inch

 

[Starplayr]

Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

Thank you. I have one iSeries iMac i5 Processor, will give it a whirl.

 

[Badruzeus]

Did we miss macOS Mojave 10.14 Public Beta that released by Apple on 25th June or it just has a same build number as Dev. Beta 2 (18A314h)?

 

[0403979]

I'm currently working on C2D machines myself (got about 20 of them). So far I haven't made much progress.
[doublepost=1529967342][/doublepost]Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

Is support for Core 2 Duo machines coming any time soon?

 

[weckart]

Did we miss macOS Mojave 10.14 Public Beta that released by Apple on 25th June or it just has a same build number as Dev. Beta 2 (18A314h)?

Did you read the article? It says Public Beta 1 is DP2. For some reason, Macrumors has skipped it, preferring to concentrate on the iOS beta.

 

[dosdude1]

Is support for Core 2 Duo machines coming any time soon?

It's completely unknown at this point... Depends on whether or not I can work out this kernel panic.

 

[0403979]

It's completely unknown at this point... Depends on whether or not I can work out this kernel panic.

Alright. I really appreciate all the effort you have put into this and I hope that someone can get everything working right eventually.

 

[nathansz]

Did you read the article? It says Public Beta 1 is DP2. For some reason, Macrumors has skipped it, preferring to concentrate on the iOS beta.

mojave public beta has not yet been released

 

[redheeler]

For some reason, Macrumors has skipped it, preferring to concentrate on the iOS beta.

They did report on it, but shortly afterward took the article down. The assumption was that Apple had released the MacOS and iOS public betas at the same time, but that turned out to not be the case.

Apple has not yet released a public beta of Mojave, according to the official website. I wouldn't be surprised if we see it tomorrow.
[doublepost=1529992603][/doublepost]

Thank you. I have one iSeries iMac i5 Processor, will give it a whirl.

Do let us know if you manage to get acceleration working on the AMD GPU.

 

[nekton1]

I'm giving it a try on an iMac from 2010 with a core i3.
Just about to try the Post-Install

BTW, it seems to need at least a 16 GB USB to make the USB booter/Installer

Thank you. I have one iSeries iMac i5 Processor, will give it a whirl.

 

[parrotgeek1]

looked at crash log from Stocks and found that it's crashing because CoreBrightness.framework. I think it does it because I installed that NightShift Patch by foxlet

foxlet's night shift patch replaces the entire corebrightness folder from 10.13 which is a recipe for disaster
[doublepost=1529993760][/doublepost]

Such a respected FORUM and the theme of cut-out brazen AMD cards from Mojave does not untwist!

wat.jpg

 

[nekton1]

Dosdude1

I tried it on a spare iMac 11,2 (core i3) with 8 GB of RAM running HS on an internal SSD.
The installer proceeded normally and I restarted and applied the default Post Install patches for the 11,2 and on reboot I see the infamous gray circle with bar.
The internal SSD was/is APFS formatted.
Any suggestions?

Thanks for you efforts.

R

I'm giving it a try on an iMac from 2010 with a core i3.
Just about to try the Post-Install

BTW, it seems to need at least a 16 GB USB to make the USB booter/Installer

[doublepost=1529995065][/doublepost]

Dosdude1

I tried it on a spare iMac 11,2 (core i3) with 8 GB of RAM running HS on an internal SSD.
The installer proceeded normally and I restarted and applied the default Post Install patches for the 11,2 and on reboot I see the infamous gray circle with bar.
The internal SSD was/is APFS formatted.
Any suggestions?

Thanks for your efforts.

PS. Done it twice over with same result each time.

R

[doublepost=1529997413][/doublepost]On third attempt, I erased the ssd first—it was still formatted APFS. Same thing happened; install seemed to go OK and post-install seemed to apply patches with forced cache rebuild but still boots to gray-barred circle.
I am happy to try anything you suggest that might help out.

 

[DaniloGeekDude]

SIP Disabled/Enabled

To fix my sound and graphics issues, I disabled SIP on an unsupported MBAir mid-2011 and then copied the following files from Sierra.

• AppleHDA*
• AppleIntelHD3000Graphics*
• AppleIntelSNB*

I restarted, and it fixed my sound and graphics issues.

I then re-enabled SIP, restarted and the issues came back. I disabled SIP again and issues are resolved again.

Anyone had the same experience? Is disabling SIP (system integrity protection) not recommended?

Thanks.

 

[howiest]

Is disabling SIP (system integrity protection) not recommended?.

I've had SIP disabled since El Capitan. Don't sweat it.

 

[DaniloGeekDude]

Did we miss macOS Mojave 10.14 Public Beta that released by Apple on 25th June or it just has a same build number as Dev. Beta 2 (18A314h)?

iClarified had this news item on public beta 1
http://www.iclarified.com/66319/apple-releases-first-public-beta-of-macos-mojave

But I think they jumped the gun on this. As it is a familiar term nowadays, may be "fake news".

 

[MacManMatt]

Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

I have a MacbookPro 8,2 Install went fine using your Mojave Patcher.

Rebooted of the USB again and ran the Post Install tools selecting MacbookPro 8,2 from the list and applied the patches.

I ticked the Force Cache Rebuild button then rebooted.

I'm straight away presented with:

*********************************************
This version of macOS is not supported on this Platform!
*********************************************
Reason: Mac-94245A3940C91C80

Not sure what I'm doing wrong.

 

[Morc]

I did that NightShift patch myself and iOSMac(UIKit) applications work and even Display section in Settings now opens instead of giving message that Display is broken

 

[G5-PowerLifter]

I had a 15" MacBook Pro 2011 model, and it had its logic board replaced twice for a bad GPU. The second time it was fixed, I immediately sold it. Wasn't about to spend a third time with it.

2011 seemed to be an off year for Apple. I remember the 2010/2011 iMacs and Mac minis having drive sensors. 2012 models I believed they got rid of them. 2012 Mac minis rock. 2014 Apple started messing with the Mini product line and hasn't updated it since.
[doublepost=1529963017][/doublepost]

Well, for what its worth, the iMac can also become a Thunderbolt Monitor for a newer Mac. If it has a thunderbolt port, then it has Target Display Mode. It's kind of weird to setup and wish Apple had a better way to do it to turn it into an external display.

Here is my unsupported Equipment List:

27" iMac 2011 (running High Sierra Supported)
13" MacBook Pro 2009 (running High Sierra, dosdude1)
Mac Pro 8 Core 2008
Mac Pro Quad Core 2008

Well having an intire computer unpurposely running just to have it as a display doesn't make much sense to me, also I don't a have a newer Mac neither the option to buy one, the 1st gen i7 in that thing is still going very strong, I'd rather turn it into a windows machine if I have to. I guess my iMac has to be be my main Mac for a while in the future

 

[DaniloGeekDude]

I'm currently working on C2D machines myself (got about 20 of them). So far I haven't made much progress.
[doublepost=1529967342][/doublepost]Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

Hello dosdude1,

Although I already successfully setup Mojave on an unsupported macbook's external SSD (originally installed on a supported Macbook), I wanted to try your method on your Mojave patcher app)
Please review the following steps to confirm I have it right.

1. Download Mojave via your patcher app into my external ssd.
2. Patch the "Install macOS Mojave Beta.app" file.
3. Use the external ssd referenced above to Startup.
4. Install Mojave beta.
5. Restart and do post install (and make sure I select the model of my targeted, unsupported macbook)
6. Attach my external ssd on my targeted macbook.
7. Restart and finish setup.

Note that steps 1 to 5 are done on the supported macbook. I explicitly mentioned these since I realize that I could only install Mojave on a supported system.

Please let me know. Thank you so much.

Best Regards.

 

[jackluke]

Hello dosdude1,

Although I already successfully setup Mojave on an unsupported macbook's external SSD (originally installed on a supported Macbook), I wanted to try your method on your Mojave patcher app)
Please review the following steps to confirm I have it right.

1. Download Mojave via your patcher app into my external ssd.
2. Patch the "Install macOS Mojave Beta.app" file.
3. Use the external ssd referenced above to Startup.
4. Install Mojave beta.
5. Restart and do post install (and make sure I select the model of my targeted, unsupported macbook)
6. Attach my external ssd on my targeted macbook.
7. Restart and finish setup.

Note that steps 1 to 5 are done on the supported macbook. I explicitly mentioned these since I realize that I could only install Mojave on a supported system.

Please let me know. Thank you so much.

Best Regards.

I guess almost all your steps are wrong, you should have downloaded before a "Install macOS Mojave Beta.app" from a supported Mac and copied it elsewhere rather than on your external ssd, then use the preliminary Mojave patcher (with no support to any c2d cpus clearly specified by the author), drag the "Install macOS Mojave Beta.app" and drop on the left side Mojave circle logo, while on the right side choose as destination your EMPTY external ssd, you have also a useful verbose during patching.
After patching done you have only to boot (holding option key after the power on) this usb external drive directly from your unsupported Mac and from there try to install and post install it through your machine.

Honestly I haven't tried it yet but I'd suggest you to use a 16 gb USB drive to patch the installer instead of an entire external ssd, or maybe split in partition the ssd, cause you will need to choose another disk to install it, I don't think you can install it in your external ssd if you are booting the installer from external ssd.