macOS 10.14 Mojave on Unsupported Macs Thread

[Larsvonhier]

You can't download it from the App Store onto an unsupported Mac. The App Store blocks the download with an error message, i.e., "this version cannot be installed on your computer" or words to that effect.

Has the Patcher been updated to download 14.0.22 yet?

yes you can - on an unsupported Mac running beta Mojave - the download button in the App Store redirects to the system settings update panel and downloads the installer.
You cannot run the unpatched installer, but create a patched USB stick

 

[skiabox]

Hello guys.
I have a macbook pro 17 inch mid 2010 model (with ssd) and I am using an external monitor.
Is it worth it to upgrade to Mojave with this patch or it is too risky considering that I am a professional software developer and I want a working machine 24 hours per day?
Thank you!

 

[jackluke]

Now I’m testing installing on an external drive conected to a iMac late 2009. If everything goes ok, I’ll install it on the main HD.
Thanks.

Be sure when you intend to upgrade your main HDD that you have at least 25 gb free, because I have almost saturated my main HDD free space and even on any minor upgrade I need to delete everytime the sleepimage (8 gb) before I can actually download the update-packages and then launching the update process.

It's the same old story, when you have a macOS Installer USB-ready it will require almost twice of its space to install over an existing volume partition, because the installation takes place in two phases: expanding all the core packages into internal HDD temporary folder, then from those temporary folder the real installation overwriting begins, so to avoid the upgrade could fail in the middle, I would advise to have for any update at least 25 gb free internal (or more) before proceed.

 

[brkr1]

I've just upgraded to latest Mojave on my Macbook Pro 15 Mid 2009 (5,3) and everything works!

Just a question: I have a Sandisk SSD (APFS) on a caddy and I'd like to know if I can enable TRIM on it and if so, how.

 

[Jack Ryan]

Be sure when you intend to upgrade your main HDD that you have at least 20 gb free, because I have almost saturated my main HDD free space and even on any minor upgrade I need to delete everytime the sleepimage (8 gb) before I can actually download the update-packages and then launching the update process.

It's the same old story, when you have a macOS Installer USB-ready it will require almost twice of its space to install over an existing volume partition, because the installation takes place in two phases: expanding all the core packages into internal HDD temporary folder, then from those temporary folder the real installation overwriting begins, so to avoid the upgrade could fail in the middle, I would advise to have for any update at least 20 gb free internal (or more) before proceed.

I have 200 Gb free. Thanks for your warning.

 

[jackluke]

I have 200 Gb free. Thanks for your warning.

On 200 gb I tipically have at least 3 OSs installed (Bootcamp included), that's why I'm short of space.

 

[Kal-037]

Also one quick inquiry... if I download and install this patch/installer... will Ibe able to still download updates like I regularly have been?
Thanks ever so much for any assistance.

 

[stevekr]

I've just upgraded to latest Mojave on my Macbook Pro 15 Mid 2009 (5,3) and everything works!

Just a question: I have a Sandisk SSD (APFS) on a caddy and I'd like to know if I can enable TRIM on it and if so, how.

1. Always back up when making any changes to your system’s hardware configuration
2. Open Spotlight (the magnifying glass in the upper right corner), type ‘Terminal’, press Enter
3. Copy and Paste the following command: sudo trimforce enable
4. Choose ‘Yes’ for all prompts, and your system will reboot shortly

 

[webg3]

Ok, probably the offset changes on almost any minor version upgrade, but the major unix exec change occurred starting from Mojave beta 4 (dosdude1 discovered that first), after that version you can use an already fixed CoreBrightness, it won't give any issue on any machine.

edit:
you forgotten to remind to those who want to do CoreBrightness patch themselves they need to download and install the Xcode Command Line Tools, without them you can't complete the most important part: codesigning the unix binary.

Terminal:
xcode-select --install

(It was already there, it's the first thing.)

 

[DaniloGeekDude]

Finally got the "final" release of Mojave 10.14 (build 18A391) on 2 of my un-supported Macs.
One thing I noticed is that Time Machine Backups are now listed by device name and not hostname for example.

View attachment 788434

So instead of MojaveHostName, it is listed as MacBook Pro. I have several dated backups under each device.
No big deal. Anyone else notice this?

Thanks.

My Bad
I forgot to update the hostnames under System Preferences | Sharing before backing them up.
It was a long and exhausting day yesterday. But I'm happy the Final release of Mojave is now running on my unsupported macs. These sandboxes are now running Mojave exclusively.

Thanks @dosdude1, the ones mentioned on the OP and everyone else who contributed to the discussion on this thread.
[doublepost=1537877064][/doublepost]

It's because after a Mojave upgrade the local hostnames reflect the mac model type, so before backup next time change first the hostname as you want go through System Preferences - Sharing prefpane, edit computer name and leave unchecked "Use dynamic global hostname". This is done on-the-fly.

edit:
There are also Terminal ways to do that:
sudo hostname Hostname-you-want (where the spaces are made through "hyphen-minus" symbol)
hostname
or
sudo scutil --set LocalHostName hostname-you-want
scutil --get LocalHostName

but they require a restart before applying globally.

Thanks @jackluke for your reply, contribution and your patched Corebrightness.
[doublepost=1537877337][/doublepost]

So I understand them not supporting every iMac, MacBook, or MacPro, and wanting/requiring a better graphics card and firmware so to handle certain updates better, but why in the heck would the dynamic theme need an extra GPU boost?
I got the 2nd highest spec of the iMac Mid 2011, Sandy Bridge Processor, upgraded graphics card, SSD, etc etc... if this Metal stuff really a big deal? *Forgive my ignorance, for the past 6 months I've finally started learning the complicated work, taking apart, and fixing Macs, (I have worked with iOS for the last 10 years, so this is still pretty fresh to me.) lol.




Kallum.
[doublepost=1537865113][/doublepost]
So did you just follow the steps in the first post to achieve that? I REALLY want this update but I have a Mid 2011 iMac that doesn't support "Metal"?
Any information on how you did it, would be great. Apologies if I'm a nuisance. *eek.

Yes I did follow the steps outlined in the OP. And you are not a nuisance at all - sometimes I think that I am one myself but the folks in here are very helpful and patient.

 

[ASentientBot]

Surtout n'oublie pas d'executer le post-install!

Never figured out the loss of admin issue. Did you? happened to me a few times too...

Only seems to happen when you install over the previous OS rather than using Software Update. The fix is simple enough though, just go in single-user mode and rm /var/db/.AppleSetupDone, and make a new user account in the setup assistant. From there you can make your old account an administrator again. At least that's how I do it. I'm sure there is a Terminal command to directly grant admin privileges too.
[doublepost=1537877963][/doublepost]

Hey guys, i installed mojave on Macbook mid-2010, and it works very well; just the isight camera doesn't work well, isight is slowly with some glitch. There is a fix for this?

EDIT: I searched in the thread and i found this:


@ASentientBot Does isight camera work perfectly without glitch for you? If yes, can you explain me how to do?

I didn't notice this in beta ~4 when I found the fix but you're 100% right. It's super laggy now and I don't know why. I'll look into it. Seems related to a Console error about "CMIOHardware". Perhaps something else needs to be replaced from HS too. Sorry for not seeing this before, I don't use iSight camera much at all.

Edit: Looks like the root cause may be CoreMediaIO.framework but I don't particularly want to risk replacing that from HS. I'll mess around with it when I get home from school, maybe. But a fix might not be a simple kext replacement this time.

 

[webg3]

I guess he used both, to fix "dark sidebar" finder you need this on page 279 (hybrid transparency), meanwhile I've discovered another way to fix only light mode "dark sidebar" into a solid whiter color (a bit more than the previous I did), unluckily I'm not still capable to allow transparency into that zone, but for the second method I'd wait first pkouame hybrid patch public release, then maybe could be combined.

in dark mode no correction needed, only in light mode.

 

[oscarodas]

Strange, my macbook pro (2009) shows transparency in dark mode.

Yours is a macbook, we have iMac 27 (2011) AMD Card.

 

[jackluke]

in dark mode no correction needed, only in light mode.

I know, to have a white opaque finder menu bar (and sidebars) the price to pay is also opaque black ones, but when you are in dark mode you can easily revert to transparency from the script or disabling "reduce transparency" checkbox from Accessibility prefpane.

I guess there is a misunderstanding, with "dark sidebar" I meant the "dark grey finder app sidebar" in light mode, I wasn't referring to dark mode, that is perfectly working as is.

 

[kapocius]

Terminal:
xcode-select --install

nm /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness|grep _ModelMinVersion


000xxxxx: 0900 0000 0100 0000 0d00 0000 0600 0000 ................

000xxxxx: 0500 0000 0600 0000 0800 0000 ............

MacBookPro9,x
iMac13,x
Macmini6,x
MacBookAir5,x
MacPro6,x
MacBook8,x


xxd -s 0xXXXXX-l 28 /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness

iHex open /CoreBrightness.framework/CoreBrightness

find: 0900 0000 0100 0000 0d00 0000 0600 0000
replace: 0700 0000 0100 0000 0d00 0000 0600 0000

save and close

replace CoreBrightness to /CoreBrightness.framework/CoreBrightness

and replace /S*/L*/PrivateFrameworks/CoreBrightness.framework

sudo codesign -f -s - /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness

sudo codesign -f -s - /S*/L*/PrivateFrameworks/CoreBrightness.framework

reboot "MacBook Pro 2010"

working

credits: https://pikeralpha.wordpress.com

View attachment 788408

I get this error:

MacBook-Pro:~ YOUNGTIMER$ nm /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness|grep _ModelMinVersion

0000000000044260 s _ModelMinVersionBLR

0000000000044280 s _ModelMinVersionHarmony

MacBook-Pro:~ YOUNGTIMER$

MacBook-Pro:~ YOUNGTIMER$ xxd -s 0x44260-l 28 /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness

xxd: 28: No such file or directory

 

[gLer]

Guys, help! Just ran the patched Mojave installer on my 2011 iMac and on reboot I get a click click and a grey screen with a no entry sign. Holding Alt to enable startup disk switching doesn’t work either. No MacOS startup sound either.

What happened!?

 

[jackluke]

I get this error:

MacBook-Pro:~ YOUNGTIMER$ nm /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness|grep _ModelMinVersion

0000000000044260 s _ModelMinVersionBLR

0000000000044280 s _ModelMinVersionHarmony

MacBook-Pro:~ YOUNGTIMER$

MacBook-Pro:~ YOUNGTIMER$ xxd -s 0x44260-l 28 /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness

xxd: 28: No such file or directory

The correct path is:

/S*/L*/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness

However to avoid signature issues you could use my already patched Corebrightness: Here link

 

[Starplayr]

yes you can - on an unsupported Mac running beta Mojave - the download button in the App Store redirects to the system settings update panel and downloads the installer.
You cannot run the unpatched installer, but create a patched USB stick

He may be referring to behavior from high Sierra. In Mojave from pre release, it’s possible to download the installer and use dosdude1’s patcher the rest of the way.

 

[jackluke]

Guys, help! Just ran the patched Mojave installer on my 2011 iMac and on reboot I get a click click and a grey screen with a no entry sign. Holding Alt to enable startup disk switching doesn’t work either. No MacOS startup sound either.

What happened!?

Probably bluetooth keyboard unpaired at power-on, or batteries in discharge, try with a usb keyboard to hold "option-alt" at startup, then boot again from USB Mojave Installer , launch Terminal from there and type:
nvram boot-args="-no_compat_check"
reboot

 

[Sevenfeet]

OK, I finally successfully got Mojave to boot externally on my Mac 3,1 with a firewire connection via a new APFS partition I created for the sake of testing. Everything seems to be working and my crusty Nvidia GTX 8800 card is still functioning with acceleration in this application. Next step is to do an "upgrade" of High Sierra to Mojave from a copy of my boot volume to see how that works (also on the same external Firewire connection). Doing a clean install would be better but that's a lot of work for my configuration.

I'm going to hold off upgrading my other Mac 3,1 doing server duty since going to Mojave will end a couple of key services I need running on OS X Server. I'm going to have to migrate to a different DNS and VPN server than the one that Apple provides.

 

[Starplayr]

Also one quick inquiry... if I download and install this patch/installer... will Ibe able to still download updates like I regularly have been?
Thanks ever so much for any assistance.

download yes. Install, possibly but may have to reapply patches and in that case for most stuff, download full installer and apply on top unless you don’t know what a later installer we’ll break. Keep a Dosdude1 patch disk handy and keep that periodically up to date. Many times an installer may not return if it checks for a supported system or if it does it could break something. You never know.
[doublepost=1537881519][/doublepost]

Hello guys.
I have a macbook pro 17 inch mid 2010 model (with ssd) and I am using an external monitor.
Is it worth it to upgrade to Mojave with this patch or it is too risky considering that I am a professional software developer and I want a working machine 24 hours per day?
Thank you!

Probably not worth the risk on something that earns you $.

 

[Tekka]

Hi All,

I see an issue not mentioned anywhere (I admit I didn't read the 309 pages )
I have a iMac 12.2 (2011, HD6970m). And after successful installation + patching I observe 2 things:
1) Login screen is SUPER slow, I manage to log in, but everything is super slow
2) The windows are reacting weirdly when I move them. The content stay where it is, the windows moves (so content is misaligned) and to refresh the content, I need to switch to another window. Then immediately the content is refreshed.

And globally everything seems slugish... Is it all linked to the Radeon I m using ? is there a way to disable GPU acceleration or reduce artifacts?

Thanks in advance for your help

 

[Sevenfeet]

Hi All,

I see an issue not mentioned anywhere (I admit I didn't read the 309 pages )
I have a iMac 12.2 (2011, HD6970m). And after successful installation + patching I observe 2 things:
1) Login screen is SUPER slow, I manage to log in, but everything is super slow
2) The windows are reacting weirdly when I move them. The content stay where it is, the windows moves (so content is misaligned) and to refresh the content, I need to switch to another window. Then immediately the content is refreshed.

And globally everything seems slugish... Is it all linked to the Radeon I m using ? is there a way to disable GPU acceleration or reduce artifacts?

Thanks in advance for your help

You have an AMD video card. The Mojave patching effort here hasn't figured out how to get AMD video acceleration working on all cards.

 

[Pressure]

Installed the final release of Mojave on the 2010 Mac Pro tonight with the Radeon HD 7950. Has anyone tried the Radeon RX 580? or RX Vega 56?

Running VEGA Frontier Edition for what it's worth. No issues, except the fan stays at 2.000 RPM unless I run an 4K HEVC video and pause it. Then it goes down to ~750RPM.

 

[ColdnFrosty]

Installed and running well on a Mac mini 5,1.

However, I am seeing some graphic anomalies on the Apple News app: