macOS 10.14 Mojave on Unsupported Macs Thread

[mrploppy]

Oh now I understand you are running Mojave in a unsupported MBP?

Came

Yup - that's what this forum is all about!

 

[amgff84]

Just to confirm the first time you run the latest security patch for Mojave and Mac freeze, did you run it from an USB stick or from your Download folder?

Thanks
Came

I ran the update from "other updates" in "software updates". See picture below. Under macOS Catalina Update will be another option of "other updates" in blue font. I think anyways... When you click on that option you will have two other updates, one is safari 14 and the other is the latest security update.

 

[amgff84]

Oh now I understand you are running Mojave in a unsupported MBP?

Came

Yes, absolutely! That's what this thread is all about.

 

[camelia]

Yes, absolutely! That's what this thread is all about.

???????

OK sooner or later I will be here at this moment my MBP are supported

Thank you

Camelia

 

[MTBnBeer]

I have successfully installed the security update 2020-005, also Safari is updated to 14.0.
I have an late 2009 iMac. The only issue I had was, right after the update and after I booted up the computer using the usb patch from dosdude, the computer would boot up fine and the patch updater app will notify of new patches to install, and will restart computer. But the computer did not restart on it's own, I had to manually select restart from the Apple menu, even then the restart hangs, I see a black screen, but the computer does not proceed to restart.
I forced shutdown the computer by holding the power button at back, after that I could restart the computer again, and from now on everything works fine.

I experienced the same "black screen + fail to restart" you detailed above. Thanks to your suggestion I cured this by holding my Early 2008 17" MBP power button down until it powered off... then powered it back on and it worked restarted fine. Installed DosDude1's Backlight Patch, rebooted again, macOS Mojave Patcher reinstalled an Ambient Light Sensor patch followed by a restart and it's running great again.

THANKS !!!

 

[alphascorp]

Hi all,
Mojave SecUpd2020.005 (18G6032) successfully installed on MBP5,3 and iMac8,1 a few days ago (After Distibution file modification)

Reapplied Postinstall with Force Cache rebuild at the first restart after update.
Like the other times, I replaced AppleGVA.framework (for videos fluidity), HIToolbox.framework (for dock menu shadows), SiriUI.framework and Siri.app (for waveform) and SoftwareUpdate.framework (to disable the Catalina upgrade proposal).
Everything works well

 

[FarmerBob]

. . .

With every update, refresh or Security Update in 10.14.6, I have issues restarting. If I push on the power button the machine shuts off immediately. That's a sign that it couldn't find what it needed to boot. I have to go into the Startup Manager, Select the particular OS Partition/Drive, although one pain, I have every partition with a special icon for its OS and also in Dark Mode the names of the drives are black as is the background. They are a pain sometimes to select. But the installs have started from there. Once up and running, I run Onyx on it and no issues from there on out. Have to run it in the same process for all the Security Updates also which get erased when you use the current 10.14.6 updater. It's a pain. But at least it works.

UPDATE (10/19/20):
From what I understand after reading the 2020-005, which I have yet to see, thread where they have discovered a problem with the order that you install Safari and 005. You only need to run 2020-004 or 005 before the latest Safari update and not have to worry about all the previous updates. My installer USB booted just fine, but once the screen came up it was not the same installer and it would not install on my machine. Curious. So I made a new installer with the DD1 1.3.7 Patcher and it installed like a dream and I have had no Security Updates needing to be installed.

 

[antaisce1]

No problems with the usual post install practice. Had to do it twice, though before the boot volume was properly found.

 

[avz]

Hi all,
Mojave SecUpd2020.005 (18G6032) successfully installed on MBP5,3 and iMac8,1 a few days ago (After Distibution file modification)
View attachment 960375
Reapplied Postinstall with Force Cache rebuild at the first restart after update.
Like the other times, I replaced AppleGVA.framework (for videos fluidity), HIToolbox.framework (for dock menu shadows), SiriUI.framework and Siri.app (for waveform) and SoftwareUpdate.framework (to disable the Catalina upgrade proposal).
Everything works well
View attachment 960376

Hi,
Would you be able to post your exact steps for Siri replacement?
Normal replacing(with chmod/chown after) did not seem to work for me. Thanks.

 

[K two]

Unsupp's are not seeing the bag'o'snakes seen on supported Macs after this most recent Apple Security Upchuck? ?

Safari 14.0 + Mojave 2020-005 Security Update Causing Major Problems!

Reports coming in from users who are starting to have major problems after installing the Mojave 2020-005 Security Update. Workarounds Inside

mrmacintosh.com

 

[alphascorp]

As @FarmerBob said (which I didn't specify in my previous post because for me it's routine...) after each security update I use Onyx, the excellent utility. Because this time again after the update (18G6032), after each start of my MBP 5.3 the "kernel_task" is constantly active between 20% and 50%. But after using Onyx, the activity of "kernel_task" is only 0.8%, 2 minutes after starting.

 

[alphascorp]

Hi,
Would you be able to post your exact steps for Siri replacement?
Normal replacing(with chmod/chown after) did not seem to work for me. Thanks.

Hi @avz
For the replacement of Siri.app I boot on an external SSD (clone of my internal disk) with this manipulation I am sure that Siri.app is no longer active and can be replaced (I prefer to do this than to kill the task), followed of course by:

sudo chmod -R 755 /System/Library/CorreServices/Siri.app

sudo chown -R 0:0 /System/Library/CorreServices/Siri.app

Hi @K two
I also read this article yesterday afternoon, but before installing each security update on my internal disk, as a precaution, I clone it on an external SSD on which I perform the update and test it for a day or two. And only if everything works well I update the internal disk.
So I tested during the whole weekend without any problem and I installed this update on the internal disk last night.
I agree with you, it seems that unsupported macs have less problems than others after this update.
However, last night I also installed the update on cMP 5.1 (after making a backup) without any problems, neither in installation nor in use (I worked with it all day long).
Some machines seem more "sensitive" than others.

 

[K two]

Hi @avz
For the replacement of Siri.app I boot on an external SSD (clone of my internal disk) with this manipulation I am sure that Siri.app is no longer active and can be replaced (I prefer to do this than to kill the task), followed of course by:

sudo chmod -R 755 /System/Library/CorreServices/Siri.app

sudo chown -R 0:0 /System/Library/CorreServices/Siri.app

Hi @K two
I also read this article yesterday afternoon, but before installing each security update on my internal disk, as a precaution, I clone it on an external SSD on which I perform the update and test it for a day or two. And only if everything works well I update the internal disk.
So I tested during the whole weekend without any problem and I installed this update on the internal disk last night.
I agree with you, it seems that unsupported macs have less problems than others after this update.
However, last night I also installed the update on cMP 5.1 (after making a backup) without any problems, neither in installation nor in use (I worked with it all day long).
Some machines seem more "sensitive" than others.

Running ONYX/Maintenance is essential after each Apple update of any type. Zero issues w/@dosdude1 Mojave installers since Chrome, Safari, Apple Mail and MSOffice is not used in any of our Mini3,1s, Macbook5,1 or iMac11,2 unsupps. 10.15.7 also runs flawlessly on all. The joy of multple partitions.

 

[amgff84]

As an update on my mid 2010 15". Mojave works well, even with the latest update. The exception is that my CPU temps are at 100 degrees Celsius since the update. Machine has new TIM so I know the heat transfer to the heatsink is good, also, this problem didn't present itself with the latest updates on High Sierra nor Mojave prior to this update. So Currently, my bottom case is cooling off the CPU apparently and I will be promptly switching back to High Sierra. I am not sure if this happens on my 17" i7 2010 MBP. Even with macsfancontrol the temps are high 80's at almost full speed.

 

[trinityblade]

Hi @nitramwin
I had the same problem with iMac8,1 but I solved it in my message #15477 page 620.
I followed message #11156 from @dosdude1 but it did not work.
I had the idea to replace only one file on the 3 of the archive bkltpatch10.14.2.zip
Only replace the file "DisplayServices.framework" contained in /S/L/PrivateFrameworks (and repaired the permissions)

sudo chmod -R 755 /Volumes/NameOfYourMojaveDisk/System/Library/PrivateFrameworks/DisplayServices.framework
sudo chown -R 0:0 /Volumes/NameOfYourMojaveDisk/System/Library/PrivateFrameworks/DisplayServices.framework
sudo kextcache -system-caches
sudo kextcache -system-prelinked-kernel

It works with .3 .4 .5 and .6

Try to run install.sh content in the attached archive with your iMac9,1

Just wanted to say thanks for this post. It helped me restore my brightness control on my mid 2009 iMac 9,1 running Catalina. These are the steps I took in case it helps anyone else:

1: Installing Dosdude01's patch in this post didn't work: https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-26927734
2: I then booted in to Dosdude01's High Sierra patcher and using the post install patches, I reinstalled only the backlight patch (which isn't there on the Catalina post install patcher). After rebooting this gave my some brightness functionality back (i.e pressing F14 and F15 would raise and lower brightness again, but it would keep defaulting back to the lowest brightness.
3: I then installed the attached archive in this post, rebooted, and brightness now works perfectly!

 

[Yebubbleman]

This may be an odd way to get to Mojave compatibility on an unsupported Mac, but does anyone know if a MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports), otherwise known as "MacBookPro16,3", is able to run Mojave? Site after site after site will go on about how it's essentially the same Mac (under the hood) as its predecessor [MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports), otherwise known as MacBookPro15,4]. Said predecessor was initially introduced with Mojave.

I know that the rule of thumb is generally that a Mac can only run, at minimum, the OS that was current at the time of its introduction (which, in the case of the 2020 model would be 10.15.4). But there have been some notable exceptions where Macs that were similar enough to their predecessor were able to run their predecessor's initial OS release since they shared the same components. Does anyone know if this is the case with the MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports)/MacBookPro16,3? I'd go out and buy one tomorrow instantly if I thought it had a chance to run Mojave.

(Suffice it to say that I wouldn't be posing this question for either the MacBook Pro (16-inch, 2019) or the MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) as I know that, unlike the Two ports models of 13-inch MacBook Pro, these Macs contain hardware that there weren't drivers for in Mojave.)

 

[mrploppy]

Unsupp's are not seeing the bag'o'snakes seen on supported Macs after this most recent Apple Security Upchuck? ?

Safari 14.0 + Mojave 2020-005 Security Update Causing Major Problems!

Reports coming in from users who are starting to have major problems after installing the Mojave 2020-005 Security Update. Workarounds Inside

mrmacintosh.com

I'm following Mr Macintosh's analysis of this issue. He's added a section "How can I tell if my Mac is affected". Well, sure enough, if I run softwareupdate -l, I do indeed get the error he mentions. So I guess my Mac is affected. Of the list of problems he reports, I definitely see an increase memory usage by WindowServer and my fans ramp up sometimes when they didn't before. As for the others, I'm not inclined to try them to see if they fail.

As I mentioned before, I saw issues with a Safari component (some bookmarks sync issue) during the installation. Safari seems to be implicated in this problem, if you install 14.0 before the security update. I'm pretty sure I did that.

Having said all that, my Mac is otherwise perfectly usable so far. I guess it's worth keeping an eye on it in case Apple provide an update.

 

[trifero]

As I mentioned some posts before, I had the problem. Then I only run the Security Update and everything works right. Now I run "softwareupdate -l" and this is the out. So i´m gonna run again the Safari update. I will report later.

 

[trifero]

Yes. When installed in that order, in my Macbook Pro 17 2011 everything works right now.

 

[avz]

Yes. When installed in that order, in my Macbook Pro 17 2011 everything works right now.

View attachment 961121

I believe people with supported machines figured that the order in which you do the updates makes a difference. For example if you install Safari 14 first and then SU 2020-001 you will experience the same issues. So the issue is not specific to SU 2020-005.

 

[trifero]

I believe people with supported machines figured that the order in which you do the updates makes a difference. For example if you install Safari 14 first and then SU 2020-001 you will experience the same issues. So the issue is not specific to SU 2020-005.

We know. It´s the installing order.

macOS 10.14 Mojave on Unsupported Macs Thread

Multiples errors here. Macbook Pro 17" 2011, ,discrete GPU disabled. All of them about the CacheDeleteExtension. I suspect is due to Safari 14.

forums.macrumors.com

macOS 10.14 Mojave on Unsupported Macs Thread

Restored to the previous backup. This time I updated only the security update, not Safari 14. Reinstalled patches from @dosdude1 an now works like charm. No errors mesagges.

forums.macrumors.com

 

[borgo1971]

I'm wondering if it will be possible use the "unsupported Macs tools" to install Mojave to a fresh new MacBook Pro 16". Probably I need to take a new portable, because the GPU from my Early 2011 MBP is broken another time (and this time I won't spend money on it), so looking between used and refurbished MacBook Pro's, considering price, butterfly keyboard, etc... I guess best choice is to go to an Amazon warehouse deal and invest my bucks in a 16". But going to Catalina at this time can be very problematic for me now: I use various older software (32 bit and even 64bit) that seems won't work on Catalina.
I guess other people could have the same issue in future, so it will have a sense supporting here not only older Macs, but even some new Mac.
Hope that someone that have the necessary skills agrees with me.

 

[RK78]

Re. my recurring problems with updates at the 2010 Mini, as stated here, decided to install the 2020--005 manually directly at the HFS+ internal volume (HDD) in Safe Boot (removes the interference/conflicts maybe from third party programs), which appears to have made the difference. Much better now. Thinking of giving up completely on the APFS partition at the external, volume already wiped, for updates.

(Or perhaps would have gone much better booted to the APFS volume on HDD external - that volume used only for Security Updates - installed directly from Software Update in Safe Boot. But hadn't thought of that until things got completely munged. Not sure yet if I want to erase that partition completely or reclone back to the now erased, untitled volume. Hoping that manual installs going forward remain as reliable.)

 

[mrploppy]

I see Mr Macintosh is reporting that Apple have pulled both the Safari and security updates. I would imagine that we'll be seeing an update that'll fix things for those of us who have already installed them.

 

[amgff84]

I see Mr Macintosh is reporting that Apple have pulled both the Safari and security updates. I would imagine that we'll be seeing an update that'll fix things for those of us who have already installed them.

I think that it's effecting even the latest updates for High Sierra because now this thing is running running hot too after applying the latest update. I might as well go back to Mojave and ignore any updates until these reports stop.