macOS 10.14 Mojave on Unsupported Macs Thread

[KeithJohn]

Hi Guys, Can anyone help me get my wifi working again on Mac Pro 3.1, I was running Mojave okay on it and then my HD packed in, so got a new ssd and sorted the patcher again on my MacBook pro running Mojave, it all installed okay and I ran the post install as stated with both wifi patchers ticked, however my wifi card does not show at all, I am on ethernet only, is there anything else I can do?

Thanks in advance

Sorted, re-installed patcher, now okay

 

[TimothyR734]

Answering to myself:
What I`ve done:
1. Updated macOS to Mojave 10.14.6 using latest patcher.
2. Applied all recommended patches in Post Install
3. Booted in Single User Mode
4. Removed only AMDRadeonX3000.kext from /System/Library/Extensions/
5. DO NOT used "MacBook Pro dGPU disabler"
6. Applied both patches from BlueSky 1.1
7. DO NOT loaded AMDRadeonX3000.kext after login

Now I have everything working including brightness control, NightShift, Siri, sleep/wake, reboot, light scheme.

Looking forward to Catalina ;-)

Catalina with the light mode patch

 

[briguy007]

Oh, so there's no one out there on a MacPro3,1 running 10.14.6 with a Nvidia GTX 680 & video acceleration?

 

[KeithJohn]

Oh, so there's no one out there on a MacPro3,1 running 10.14.6 with a Nvidia GTX 680 & video acceleration?

I am running that card in my 3.1. Quick Time plays fine, can't help you with the other stuff though

 

[mirceac]

Hi, I've applied @dosdude1 Mojave patch for a Macbook Air 5.2, everything works OK, except for the integrated camera, the camera is listed in the SystemReport, the FaceTime discovers and activate it, the green LED turns ON, but no image is coming and Facetime says after a while that it's not able to receive any data.
Is this a known issue with Mojave on 2012 Macbook Airs, I've tried to dig trough this thread, but at 680 pages it's a bit too much.

Many thanks for your help-

 

[alphascorp]

Hi, I've applied @dosdude1 Mojave patch for a Macbook Air 5.2, everything works OK, except for the integrated camera, the camera is listed in the SystemReport, the FaceTime discovers and activate it, the green LED turns ON, but no image is coming and Facetime says after a while that it's not able to receive any data.
Is this a known issue with Mojave on 2012 Macbook Airs, I've tried to dig trough this thread, but at 680 pages it's a bit too much.

Many thanks for your help-

Hi @mirceac
It may be that after an installation or update iSight does not work. To fix it:
1- go to Applications -> Utilities and launch "Patch Updater.app"
2- Click "View installed Updates"
3- right click on "Legacy iSight / Webcam Patch" and choose "Re-install ..."
4- Reboot when asked
After the reboot iSight should work properly

 

[Flacko]

Oh, so there's no one out there on a MacPro3,1 running 10.14.6 with a Nvidia GTX 680 & video acceleration?

Hi, apologies for any delay. Have been occupied refurbishing cMP4.1>5.1 so cMP3.1 not been switched on for a while. Anyway, just fired it up and played some video clips including some 4k. No problems here. Using 10.14.6 patched with latest patcher. Quicktime v10.5 (935.5). I have included the PCI details for the card for comparison purposes. There have been previous reports of flashed cards not always linking at the full speed of 5 GT/s - they connect at 2.5 GT/s. However I am not sure this would cause stuttering. When you patched did you ensure legacy video cards was not ticked?

 

[mirceac]

Hi @mirceac
It may be that after an installation or update iSight does not work. To fix it:
1- go to Applications -> Utilities and launch "Patch Updater.app"
2- Click "View installed Updates"
3- right click on "Legacy iSight / Webcam Patch" and choose "Re-install ..."
4- Reboot when asked
After the reboot iSight should work properly

View attachment 852926

Thanks for the reply, but I don't have this patch for MacbookAir 5,2 , it doesn't show in the list

 

[mirceac]

Well, it's even written in the @dosdude1 site, a warning that the iSight cameras are a "hit and miss" situation. But I was hoping that I could force somehow the iSight update. that doesn't show at all .

The vendor and user ID of my camera are: 1452 and 34064, if some one has a camera with the same ID that works with mojave, I'll be glad to hear the details.

 

[mirceac]

Sorry, damaged brain , ignore the noise, the MacBook Air 5,2 is natively supported by Mojave, sorry for the noise, time to reinstall from scratch

 

[JoSch]

Oh, so there's no one out there on a MacPro3,1 running 10.14.6 with a Nvidia GTX 680 & video acceleration?

Me, too. FCPX works.

 

[GilDev]

Sadly no, I don't. It was a clean install so I'm pretty sure it's APFS on my SSD.
It's quite bad if I can't even boot on the patched install drive to make a clean install… I guess I can still boot on a vanilla High Sierra drive or over network but that's not the point.

Anyone please have any idea on why it won't boot on the patch install drive I've just made?
I booted up on macOS network recovery, did an internal disk check, got quite a lot of warnings (see attached pic) but it still won't boot on it.
Now I'm sure it's the jump from 10.14.3 to 10.14.6 (which I didn't ask for, it did a Windows-like auto update) which killed everything, and that my internal drive is in APFS.

Again, it shows the lines you can see in the second attached pic again and again while booting from the install drive.

Thanks!

 

[K two]

Hopefully someone can give me a little insight into what I am doing wrong. Trying to get Mojave on a early 2009 mac mini (3,1)
With DosDude1's tool. Keep getting stuck at the apple logo with a progress bar that never moves past 0% after selecting the flash drive.
Same flash drive was used with his tool to upgrade to High Sierra.
Have tried 2 other flash drives, 1 that was USB2.0 16gb and a second 32gb usb 3.0, doesn't matter always gets stuck at 0%
Have tried downloading Mojave several times both from official source (app store on my 2018 MBP) and using his tool
Have tried an older version of the tool just for giggles
Any ideas?

How are you formatting your USB sticks? HFS+ or APFS? Allowing the patcher to set up the USB installer has never falied for me. see #16987

 

[alphascorp]

Sorry, damaged brain , ignore the noise, the MacBook Air 5,2 is natively supported by Mojave, sorry for the noise, time to reinstall from scratch

Indeed Mojave is supported natively on MBA5,2 I did not see the machine you have, I had only focused on the installation with @dosdude1's Patcher

 

[avz]

Since I had a few point updates and 5-6 beta's installed on top of each other, I decided to do a clean install of the 10.14.6 on both MB5,1 and MBP9,2. All went great without any issues.

 

[eurasian]

When I listen a song (youtube, iTunes etc.), I hear a slight tac tac in the background, (with the headphones the sound is ok) does it happen to anyone?

 

[GilDev]

Little update from my problem (MacBookPro8,1 updating from 10.14.3 to 10.14.6 without asking): I was finally able to make a new install drive on the same MacBook Pro 13" early 2011 as mine running on Yosemite, downloading Mojave from the patcher’s menu. The previous installer drive that weren’t working were made with a 2015 MacBook Pro running High Sierra and a Mojave downloaded a while ago from the French Mac App Store.
So the new one booted fine, I was able to patch everything and sure enough, I’m now able to boot back on my internal drive. Thanks for the help, I’ll now keep my patched Mojave drive ready just in case things like that happen again.

 

[rmpbklyn]

Fun it was View attachment 852777

are you going to post note/blog of the process? i have 2011 mac mini, this gives me hope LOL

 

[briguy007]

Hi, apologies for any delay. Have been occupied refurbishing cMP4.1>5.1 so cMP3.1 not been switched on for a while. Anyway, just fired it up and played some video clips including some 4k. No problems here. Using 10.14.6 patched with latest patcher. Quicktime v10.5 (935.5). I have included the PCI details for the card for comparison purposes. There have been previous reports of flashed cards not always linking at the full speed of 5 GT/s - they connect at 2.5 GT/s. However I am not sure this would cause stuttering. When you patched did you ensure legacy video cards was not ticked?

View attachment 852928

Yup! Ensured not to install Legacy Video Card Support.

Yeah, so while it is a flashed Nvidia GeForce GTX 680, it shows the link speed @ 5.0 GT/s.

What's interesting is when I play a 4K H.264 video, like one captured from my iPhone 6S, the VTDecoderXPCService process jumps from anywhere between 200-400% CPU utilization. It's really trying to muscle through with software. Unfortunately, it can't keep up & drops frames along with audio.

It's frustrating because the Metal acceleration is working! The UI in Mojave is fluid & snappy.

Playing a single 1:41 second H.264 video caused 472x of the following QuickTime entries inside Console:
default 01:02:10.679148 -0700 QuickTime Player HALC_ProxyIOContext.cpp:1068:IOWorkLoop: HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload

 

[0134168]

Oh, so there's no one out there on a MacPro3,1 running 10.14.6 with a Nvidia GTX 680 & video acceleration?

 

[Flacko]

Yup! Ensured not to install Legacy Video Card Support.

Yeah, so while it is a flashed Nvidia GeForce GTX 680, it shows the link speed @ 5.0 GT/s.

What's interesting is when I play a 4K H.264 video, like one captured from my iPhone 6S, the VTDecoderXPCService process jumps from anywhere between 200-400% CPU utilization. It's really trying to muscle through with software. Unfortunately, it can't keep up & drops frames along with audio.

It's frustrating because the Metal acceleration is working! The UI in Mojave is fluid & snappy.

Playing a single 1:41 second H.264 video caused 472x of the following QuickTime entries inside Console:
default 01:02:10.679148 -0700 QuickTime Player HALC_ProxyIOContext.cpp:1068:IOWorkLoop: HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload

Well it looks like you are correct in that Quicktime in Mojave does not use hardware decoding. Made a 4K 60 Hz H264 video with iPhone X to replicate yours and tried it on the cMP3.1. Although it played smoothly on this system the VTDecoderXPCService ramped up to between 150-200% CPU (using only an HD monitor).
Out of interest I moved the file to my cMP5.1 with a Sapphire RX580. Playing the video again - worked smoothly but VTDecoderXPCService ramped up to 400% CPU with a higher resolution output (2560 x 1440 - I do not have a 4k monitor). So having an AMD card makes no difference to the CPU load.
I may be wrong but I believe the problem may lie with our older processors. Maybe Quicktime in Mojave is making use of the Intel QuickSync that our older CPUs do not have and is not using the GPUs. The software fallback method we are using works if your CPU can cope with the load otherwise there will be some stuttering at the high resolutions. What CPUs are you using? Not a solution but at least you know it is not just your system.
Edit: Just found this https://forums.macrumors.com/threads/hdr-4k-video-support-macos-vs-windows.2130924/. It seems my thoughts on the CPU might be on the right track - unfortunately.

 

[K two]

are you going to post note/blog of the process? i have 2011 mac mini, this gives me hope LOL

Make sure that Mini can run Mojave, some may have a non-compatible GPU, AMD Radeon HD 5xxx/6xxx series GPU.

D/L the latest patch tool, v.1.3.3 here: https://drive.google.com/file/d/1N-NiUo0brSoi6FLJQ_davaQh-U9eQdft/view

Follow these instructions. http://dosdude1.com/mojave/#instructions

Works so well, you'll smile.

 

[iAMmeStyle]

My iMac 27" i7 2.8GHz late 2009 with Mojave does not work with target display mode anymore. It was working fine in High Sierra. I think it's another known issue on Mojave unsupported Macs.

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

 

[netsrot39]

I've justed updated my 2009 iMac and Mac Mini to 10.14.6. As expected, it works pretty much flawlessly as it did with 10.14.5. However the hybrid transparency patch is kind of broken in comparison to 10.14.5 so it only works partially. (I usually install the updates with dosdude1's Patcher and then apply transutil.sh from macOS Patcher by @0403979) Does anyone know if @pkouame is still maintaining the project or if there are other options out there to enjoy Mojave in light mode? Thanks!

 

[iMac-Oldschool]

Hello @MacPeet
I also have iMac8,1 and I found the solution (without using Brightness Slider.app) here are the links to my previous message #15477 and #16717. I followed message #11156 from @dosdude1 but didn't work on iMac8,1.

For iMac8,1 only replace the file "DisplayServices.framework" contained in "/S/L/PrivateFrameworks" and repair permissions (maybe it works on machines other than iMac8,1 but I could not test)

1. Download the archive below and unzip it.
2. Search for "DisplayServices.framework" in /System/Library/PrivateFrameworks and Back it up.
3. Then replace "DisplayServices.framework" with the one contained in the archive you just unzipped.
4. open the Terminal and enters the following commands (to repair permissions):

sudo chmod -R 755 /System/Library/PrivateFrameworks/DisplayServices.framework
sudo chown -R 0:0 /System/Library/PrivateFrameworks/DisplayServices.framework

5. After reboot the brightness control works with F1/F2 keyboard keys

It works with .3 .4 .5 and .6 (not tested on .1 and .2)

Alphascorp,
Installed this today on my iMac8,1 and it works perfectly. Thanks for your efforts. Currently running
macOS 10.14.6 (18G87).