macOS 10.14 Mojave on Unsupported Macs Thread

[Dong2016]

Hey Ppl (I try here)....

I've updated my Macbook Pro Retina 13" from 2015 from HS 10.13.6 to 10.14.1 and get some weird bugs in Console log - I did not get them from 10.13.6
And i have no idea what the issues is just i not having them in 10.13.6

Does somebody know the issues and fixes? (the quicklook issue come all the time)

See the attached picture below:


A practical problem I have now is: When my Macbook pro wakes up from sleep (with external monitor and BT keyboard and mouse) - I can not wake it up with my BT keyboard and mouse (clicking), I need to turn my computer screen up and down ..

 

[bova80]

upgraded my mid-2009 13" mbp (5,5) from high sierra to mojave and now my 32" monitor won't display at 2560x1600 like it was and it will randomly flicker every once and a while. anyone have a fix for that?

 

[joelw135]

But if you downloaded HybridMode-Public -master open the folder then files folder then 18B75 then patched apps if you want transparency the only 2 you need are CoreUIHybrid-18B75-Fat and HIToolboxMenubar-19B75-Fat drag those 2 to your desktop then right click on CoreUIHybrid-18B75-Fat rename it to CoreUI then right click on HIToolboxMenubar-18B75-Fat and rename it HIToolboxMenubar-18B75-Fat to HIToolbox. If you have an icon of your HDD/SSD on your desktop open it find system open it find library open it then scroll down to private frameworks open it then scroll until you find CoreUI framework then open it open the versions then A open it drag the coreUI to your documents so you have a backup of the original then replace it with the one on your desktop authenticate it then use to replace and password if asked. Then all the way out the scroll up until your find the frameworks folder open that find carbon frameworks then open it then frameworks open the HIToolbox framework drag the original to your documents then replace it with the one on your desktop close everything down reboot

Thanks.

 

[KNOKKi]

So I I have a iMac 8.1 running Mojave, but the sound is on max continuously independent from the slider position (slider in YouTube works well BTW) So Dosdude1 asked me whether I had installed the Volume Control Patch using Patch Updater. The point is now that I don't see how to to install this individual patch. If I use patch updater it updates automatically, but this doesn't help. In the overview which is generated automatically it says something like 'Volume slider patch Version 0'. Can anybody show me the way how to install the Volume Control Patch?! Thx for your help in advance!

 

[bova80]

upgraded my mid-2009 13" mbp (5,5) from high sierra to mojave and now my 32" monitor won't display at 2560x1600 like it was and it will randomly flicker every once and a while. anyone have a fix for that?

I resolved this by reinstalling the patches from my USB.

 

[smnbldwn]

I have just upgraded an iMac 9,1 using the patch tool, it is working fine except the screen is dark and the brightness control no longer works. I remember the same problem with High Sierra but it was fixed with via patch updater. Has anyone got any tips for this?

 

[tectxer22]

• Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).

Hey dosdude1 I found a work around for this if you put the theme as light then turn on reduce transparency it fixes the greying issue.

 

[smnbldwn]

I fixed the brightness issue using the brew install brightness command and setting brightness from the command line e.g. brightness 0.9

 

[sutheroot]

Alright, I see a lot of people updating to 10.14.1 or 10.14.2 but how are you all doing that? It seems to be claimed you just use the installer to patch the update but how? Updates are pushed out as PKG which the installer doesn't do. Normal, Public and Dev updates are all in PKG form. How are you all patching that to update?

I'll also add the the installer app from the app store seems to be 10.14.0 only. So not sure how people are grabbing higher then that.

 

[Larsvonhier]

Alright, I see a lot of people updating to 10.14.1 or 10.14.2 but how are you all doing that? It seems to be claimed you just use the installer to patch the update but how? Updates are pushed out as PKG which the installer doesn't do. Normal, Public and Dev updates are all in PKG form. How are you all patching that to update?

I'll also add the the installer app from the app store seems to be 10.14.0 only. So not sure how people are grabbing higher then that.

fetch the 1.2.3 version of dosdude1´s patcher and let it grab the full installer image 10.14.1 from Apple, install to USB and install that onto your Mac (overwrite existing 10.14.0 if you like, you won´t lose any user data there)!

 

[Sveto]

The best thing you can do is download the new 1.2.3 patcher, download the 10.14.1 from the same patcher and build the USB stick with 10.14.1.
After that you can try to use the OTA update. If, after the installation, you have some problems, like the Mac not booting or something, you can reboot from the 10.14.1 stick and just apply the post-install patches.

That is a bad idea. The only officially walked-through way of installing 10.14.1 on unsupported machines is with a USB Stick, created by patcher 1.2.3. Doing it through OTA is like spitting on your own efforts and looking for trouble. Yet some insist on OTA and end up unable to boot, with white screens, or not being able to finish the update. Bad idea.
[doublepost=1541523860][/doublepost]

Alright, I see a lot of people updating to 10.14.1 or 10.14.2 but how are you all doing that? It seems to be claimed you just use the installer to patch the update but how? Updates are pushed out as PKG which the installer doesn't do. Normal, Public and Dev updates are all in PKG form. How are you all patching that to update?

I'll also add the the installer app from the app store seems to be 10.14.0 only. So not sure how people are grabbing higher then that.

10.14.2beta came just 2 days after the official update to 10.14.1. Why on earth, instead of enjoying the just released 10.14.1, you would try to break your system and move to a beta, which has nothing of a value to daily use and most likely has introduced unforeseen bugs, or incompatibilities to your unsupported mac?

 

[CNiles38006]

I fixed the brightness issue using the brew install brightness command and setting brightness from the command line e.g. brightness 0.9

Thanks a lot for this tidbit, I was able to adjust my iMac brightness levels via Terminal after installing Homebrew, then following these commands.

Install Homebrew. (Bonus points for already having it installed)

Once that's all well and good, enter brew install brightness

Now, all you have to do is type in brightness <level> to change your laptop's brightness. Change level to your desired brightness on a scale of 0 to 1.

(example: enter brightness .27 for 27% brightness)

Some bonus tips:

• entering brightness -lv will print some detailed info about your display, as well as your brightness level.
• brightness -l will give you some information about your display, but considerably less than -lv. It still prints your current brightness.

 

[kautame]

That is a bad idea. The only officially walked-through way of installing 10.14.1 on unsupported machines is with a USB Stick, created by patcher 1.2.3. Doing it through OTA is like spitting on your own efforts and looking for trouble. Yet some insist on OTA and end up unable to boot, with white screens, or not being able to finish the update.

I was just saying that, before trying an OTA update, you should create a new USB stick with 10.14.1, in case something goes wrong. Because that's what I did: I updated my iMac 7,1 through OTA update and then re-applied the post-install patches, without any problems (besides the one I already had in 10.14, because my iMac was, and still is, unable to find a valid EFI partition by itself and I have to boot with Alt-key to select the - only - partition).
By the way, Dosdude himself said something similar here:

On APFS volumes, updating *should* work, but I'm not sure. Also not 100% sure if it works on HFS volumes either. Worst case, it can be installed by making a new installer volume with the latest patcher, and installing onto your volume.

 

[barcode_turk]

so each time when new update arrive we should do clean install ?

 

[timthomason]

so each time when new update arrive we should do clean install ?

I don't do a clean install, just use the patcher app and download the OS from it.

 

[sutheroot]

.

 

[jackluke]

I've tried the dosdude1's brightness fix on iMac (supported natively until El Capitan) but I get into my kextcache rebuilding this "issue":

kxld[com.apple.driver.AGDCBacklightControl]: The following symbols are unresolved for this kext:
kxld[com.apple.driver.AGDCBacklightControl]:     AppleBacklightParameterHandler::scaleBacklightTable(unsigned short, unsigned short, unsigned short*, IOService*)
kxld[com.apple.driver.AGDCBacklightControl]:     AppleBacklightParameterHandler::interpolatePanelTable(unsigned short const*, unsigned short, unsigned short, unsigned int, unsigned short*, unsigned short)
kxld[com.apple.driver.AGDCBacklightControl]:     AppleBacklightParameterHandler::loadScaledMobileBacklightTable(unsigned short, unsigned short**, unsigned short*)
Link failed (error code 5).
Prelink failed for com.apple.driver.AGDCBacklightControl; omitting from prelinked kernel.

Even if that issue occurred, apparently the brightness control sometimes works and I got the 16 intervals of brightness, but other times it gives only 2-3 as the Mojave stock kexts.

 

[jhowarth]

so each time when new update arrive we should do clean install ?

Folks seem to confuse the concept of an upgrade installation using a usb installer created from the current full installer and the current Mojave patcher with a clean install (which is totally unnecessary).

 

[Jack Ryan]

You need to use a usb thumb driver to install the patcher
[doublepost=1541210243][/doublepost]10.14.2 beta installed successfully on my mid 2009 iMac using patcher 1.2.3

Have you installed 10.14.1 without any issues? I have an iMac 27” late 2009 and I’m not sure for upgrading.
Thanks

 

[InsightsIE]

Hi everyone,
I was just wondering if the iMac mid 2011 (12, 1) with 6750M can run Mojave? The sticky post says no but there's a video online of it running with normal bugs as described.

Did anyone else upgrade their 2011 iMac, what was the result? Thanks.

 

[Hughmac]

10.14.1 install OTA failed on my iMac 11.2 even after patching, so I used patcher 1.2.3 to download the full version and reinstall over the top.
After patching everything worked except wifi (Atheros 9280) even with wifi patch applied - no hardware detected, although I still had wifi networks found on the startup screen where you choose boot device.

So, I'm currently restoring a backup of 10.14.0 from my CCC drive

Cheers

Hugh

So, just as a note of caution, whilst trying to restore my Carbon Copy of 10.14.0 back to my defective 10.14.1 upgrade I had two kernel panics / restarts.
I had just upgraded CCC to the latest version 5.1.6, but reverting to 5.1.5 has so far resulted in no KPs.
May be just a coincidence of course

Cheers

Hugh

 

[TimothyR734]

I fixed the brightness issue using the brew install brightness command and setting brightness from the command line e.g. brightness 0.9

another way is to download the brightness slider from the App Store its free
[doublepost=1541538532][/doublepost]

That is a bad idea. The only officially walked-through way of installing 10.14.1 on unsupported machines is with a USB Stick, created by patcher 1.2.3. Doing it through OTA is like spitting on your own efforts and looking for trouble. Yet some insist on OTA and end up unable to boot, with white screens, or not being able to finish the update. Bad idea.
[doublepost=1541523860][/doublepost]
10.14.2beta came just 2 days after the official update to 10.14.1. Why on earth, instead of enjoying the just released 10.14.1, you would try to break your system and move to a beta, which has nothing of a value to daily use and most likely has introduced unforeseen bugs, or incompatibilities to your unsupported mac?

I downoaded 10.14.2 beta OTA and patched with macOS patcher 1.2.3 no issues

 

[CNiles38006]

delete

 

[fnascimento]

Hello, I have a question. In Hackintosh installations I heard that any generated application developed for IOS / Mac when shipped to the Apple Store they are not approved, because they are generated in Mac Hackintosh, I would like to know if anyone knows if this same problem can occur with this installation on devices that are not compatible with Mac Os Mojave?

Am I in Version 10.14.0 to go to version 10.14.1 just by doing a clean install?
Thank you

 

[Charles Butcher]

My 10.14.1 MBA11 can't display the handwrittern notes created on my iPhone. It tries to load but crashed the Notes app on macOS.

Try to use and replace in Mojave an /HighSierra/System/Library/PrivateFrameworks/PencilKit.framework that should not use the Metal API Kit. And if after still crashes, try copying and launching Notes.app from High Sierra, I am not sure if Notes.app has been evolved on Mojave but it doesn't seem they introduced new features to it.

I found the same (Mac mini 2011), so I took jackluke's advice and swapped PencilKit.framework for the High Sierra version. However, Notes.app then wouldn't launch:

Dyld Error Message:
symbol '_OBJC_CLASS_$_PKTextAttachmentDrawingView' not found, expected in '/System/Library/PrivateFrameworks/PencilKit.framework/Versions/A/PencilKit', needed by '/Applications/Notes.app/Contents/MacOS/Notes'​

So I took Notes 4.5 from High Sierra (the Mojave version is 4.6). This runs fine, but handwritten notes don't display – they show up with a placeholder icon.

This is not a big deal for me, since I don't use handwritten notes, but it's worth noting as the only problem I've seen since upgrading to Mojave. Anything else we can try?