macOS 10.14 Mojave on Unsupported Macs Thread

[alphascorp]

Just go and press check for updates. This will bring your red badge back in no time.

Hi @avz ,
Yes that's right, that's why I notified it in my message #17362
"FIXED MY ISSUE TEMPORARILY!"
"It works as long as I do not run update lookup with the software update system preferences even though I have already run (sudo softwareupdate - ignore "macOS Catalina" and sudo softwareupdate --list) before. "

In this case it is necessary to redo the manipulation with the terminal (which is not a real problem)

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier

defaults write com.apple.systempreferences AttentionPrefBundleIDs 0

killall Dock

That said, we do not launch a search for updates every day...

However, this does not block the search for automatic updates as I read with some solutions on the web

EDIT:
In order to permanently prevent the red badge from coming back after each update search (automatic and/or manual)
Just add the following line to others:

defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier

For simplicity execute all these commands at once by copying all this code and paste it into the Terminal:

sudo softwareupdate --ignore "macOS Catalina";
defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier;
defaults write com.apple.systempreferences AttentionPrefBundleIDs 0;
killall Dock;
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier;
softwareupdate --list

 

[vndbaccount]

So when I tried to install Mojave, I encoutered this error

An error occurred installing macOS, To use Apple diagnostic to check your Mac Hardware, shut down and press the power button and immediately hold the 'D' key until diagnostic begins

Doing so would result in a stop sign on screen.

I tried to look into /var/log/install.log, I see the what seems to be the most promising message

PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Core.pkg”." UserInfo={PKInstallPackageSHA256Digest=caa23785b424e73d2d597745365a9aa4266572a14c3f2053d1dfefae31582f10, NSLocalizedDescription=An error occurred while extracting files from the package “Core.pkg”., NSFilePath=/Volumes/.../.OSInstallSandboxPath/Root, NSURL=Core.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.Core, NSUnderlyingError=0x7fd7e5950420 {Error Domain=PKXARArchiveErrorDomain Code=101 "archive verify failed" UserInfo={NSURL=file:///System/Installation/Packages/Core.pkg#Payload, NSFileOwnerAccountID=99, NSFileHFSTypeCode=0, NSFileSystemFileNumber=52204, NSFileExtensionHidden=false, NSFileSystemNumber=16777224, NSFileSize=5312482703, NSFileGroupOwnerAccountID=99, NSFileOwnerAccountName=_unknown, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2019-10-12 07:47:19 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=_unknown, NSFileReferenceCount=1, NSFileModificationDate=2019-10-12 08:00:10 +0000, NSLocalizedDescription=archive verify failed}}} {

        NSFilePath = "/Volumes/LinhSetup/.OSInstallSandboxPath/Root";

        NSLocalizedDescription = "An error occurred while extracting files from the package \U201cCore.pkg\U201d.";

        NSURL = "Core.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution";

        NSUnderlyingError = "Error Domain=PKXARArchiveErrorDomain Code=101 \"archive verify failed\" UserInfo={NSURL=file:///System/Installation/Packages/Core.pkg#Payload, NSFileOwnerAccountID=99, NSFileHFSTypeCode=0, NSFileSystemFileNumber=52204, NSFileExtensionHidden=false, NSFileSystemNumber=16777224, NSFileSize=5312482703, NSFileGroupOwnerAccountID=99, NSFileOwnerAccountName=_unknown, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2019-10-12 07:47:19 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=_unknown, NSFileReferenceCount=1, NSFileModificationDate=2019-10-12 08:00:10 +0000, NSLocalizedDescription=archive verify failed}";

Thinking that is because the USB I used to boot is wrongly prepared, I run @dosdude1's tool again. The result is the same.

Currently, csrutil is deativated, I installed on a Mac OS Extended (Journaled) formated partitioned of Macbook Pro late 2008, previously have El Capitan.

Thank you

 

[Larsvonhier]

I’m running Lightroom Classic 8.x on a MacBookPro4,1 (512 MB VRAM) and on earlier versions the "Enhance Details" feature was working - but now at 8.4.1 - I get the following error:

View attachment 866388
Hardware not supported. Graphics card with Metal support is required.

Is there any hope, to get this still working with a patch, or are we (with those older gfx-cards) just out of luck here?

You could add an eGPU via ExpressCard Slot (works even without connecting a screen, headless). Metal is then supported even on programs running on internal MacBook screen. See thread here and be sure to check page#1ff there also.
[automerge]1571044396[/automerge]
Anyone tried today´s "Security Update Developer Beta 2019-001-10.14.6" ?
I think it is new, but might have missed it for a couple of days as well.

 

[Larsvonhier]

Ok, just installed the Sec. Update 2019-001 beta on my 17" MacBook Pro 4,1 -> it results in build 18G1005 and is still benign in terms of patchability with latest @dosdude1 patcher. Works perfectly!
Side note: The old CFL backlight patches still do the job on this machine, so illumination of screen can be adjusted with function keys and stays permanent across boots.

 

[avz]

Up-to-date and secure! The system feels faster after the update.

 

[avz]

Just noticed that SiriUI.framework from the 10.14.3 does not seem to work anymore.

 

[Larsvonhier]

Just noticed that SiriUI.framework from the 10.14.3 does not seem to work anymore.

Hm. Have you tried SIRI-unpatched? Here it does not crash, but does not seem to listen to the mic either.
Just a blank grey notification with no soundwave animation.
(Will try on different machines also, currently due to Parallels Desktop the fans are whirring and that might additionally disturb the audio pickup).

 

[avz]

Hm. Have you tried SIRI-unpatched? Here it does not crash, but does not seem to listen to the mic either.
Just a blank grey notification with no soundwave animation.
(Will try on different machines also, currently due to Parallels Desktop the fans are whirring and that might additionally disturb the audio pickup).

Would you be able to upload the current 18G1005 SiriUI.framework(it should be only 10Mb)? Stupid me did not back up before the swap.

 

[Larsvonhier]

Checked again - without fan noise: Siri works oob, without patching now.
Here´s the framework file from 10.14.6 security update 2019-001 beta, hope it helps.

 

[avz]

Checked again - without fan noise: Siri works oob, without patching now.
Here´s the framework file from 10.14.6 security update 2019-001 beta, hope it helps.
View attachment 869545

Yes, thanks, it works. 10.14.3 framework was working so well with wave animation every time that I became complacent and never backed up the original. Something must have changed with the last couple of supplemental updates as I am pretty sure I still had the wave animation working up until very recently.

P.S. It is actually possible that SecUpd 2019-001 Beta messed something up, like they say, hey it is only Beta.

 

[avz]

I actually CMD-R into recovery and restored the APFS snapshot I took before applying the SecUpd 2019-001 Beta. And sure enough the wave animation is back! Something must be going on with the 2019-001 Beta update, hopefully everything will be back to normal in the final release.

 

[Kevbasscat]

I'm having issues after the supplemental update. I was on 10.14.4 that @ dosedude1 put on my 8,2 mbp after he did his Gmux fix for thhe dGPU, so using a PNY 16 Gb USB I built a 10.14.4 patcher, and verified it on my 18,3 iMac, and it worked. I put it in the 8,2 hit option at startup and only the HD shows up, then loads half way and gets stuck. So I built another 16 Gb USB with 10.14.4 on it, verified it on my 18,3, put it my 8,2 and same result, then another 16 Gb USB, same result. What am I doing wrong? This is a simple straight forward task it seems. @doseduse1 you have made this process so simple and easy I don't think even I could get this wrong, but maybe I did. Can Someone point to what I've done incorrectly please? I followed the steps to the letter. This happened at the same time the Google Keystone update issue arose, although I don't use Google Chrome, unless it comes with Mojave. Help please?

 

[martinbo66]

I have a HighRes MacBook Pro 8.2 - Late 2011 (with self created Fusion drive), with faulty dedicated GPU. So I disabled the GPU and use only the on-board GPU, as described here https://forums.macrumors.com/thread...fi-variable-fix.2037591/page-35#post-24956091. Works like a charm.

I would like to try Mojave, and since the dedicated GPU (AMD Radeon HD6750M) is faulty, this is an interesting option, since I need to disable the GPU anyway in order to run Mojave.

My question: I assume the Mojave-installation will overwrite the GPU-disablement?

Of course I can disable it again, but I had a lot of issues because it was almost impossible to disable SIP, as more MBP-owners experienced. The system did not allow Disabling SIP in Recovery Single User Mode <Cmd>+<r>+<s>. It seems that after High Sierra Update 10.13.6 <Cmd>+<r>+<s> just brings you into Single User Mode, and Single User Recovery Mode is not possible anymore.

 

[Larsvonhier]

I have a HighRes MacBook Pro 8.2 - Late 2011 (with self created Fusion drive), with faulty dedicated GPU. So I disabled the GPU and use only the on-board GPU, as described here https://forums.macrumors.com/thread...fi-variable-fix.2037591/page-35#post-24956091. Works like a charm.

I would like to try Mojave, and since the dedicated GPU (AMD Radeon HD6750M) is faulty, this is an interesting option, since I need to disable the GPU anyway in order to run Mojave.

My question: I assume the Mojave-installation will overwrite the GPU-disablement?

Of course I can disable it again, but I had a lot of issues because it was almost impossible to disable SIP, as more MBP-owners experienced. The system did not allow Disabling SIP in Recovery Single User Mode <Cmd>+<r>+<s>. It seems that after High Sierra Update 10.13.6 <Cmd>+<r>+<s> just brings you into Single User Mode, and Single User Recovery Mode is not possible anymore.

I found it to be a better, faster and easier way (at least on systems with initially garbled screens due to GPU failures) is to use rEFInd on a boot stick and toggle SIP from the tool included there.

 

[rotarypower101]

Can anyone help me solve a delayed mouse connection on a Mojave 10.14.6 MP3,1 ?



Every time I go to use the mouse it takes a very Long time to connect to the mouse before it becomes active.



Is there anyway to correct that?



I think I have the BROADCOM BCM94360CD card

Can anyone clarify what is necessary to fix the issue? From reading other posts it sounds like maybe a reinstall is the only thing that forces the kext to load properly, or going to a Higher Sierra version might be an alternative?

I Think this is a relevant post to the issue?

My mp3.1 has an updated BT/WiFi card like yours. For Mojave 14.0 to 14.3 the BT part of the card was never recognised. Replacing the following kexts IOBluetoothFamily.kext, IOBluetoothHIDDriver.kext, IOACPIFamily.kext with those from HS(13.6) always solved the problem. Mojave 14.4 and 14.5 recognise the card without any replacement kexts. I have found no speed issues with the later versions.

 

[Flacko]

Can anyone help me solve a delayed mouse connection on a Mojave 10.14.6 MP3,1 ?



Every time I go to use the mouse it takes a very Long time to connect to the mouse before it becomes active.



Is there anyway to correct that?



I think I have the BROADCOM BCM94360CD card

Can anyone clarify what is necessary to fix the issue? From reading other posts it sounds like maybe a reinstall is the only thing that forces the kext to load properly, or going to a Higher Sierra version might be an alternative?

I Think this is a relevant post to the issue?

The cMPs are notorious on having poor Bluetooth connections. The Bluetooth aerial is at the back of the machine and all that metal case can cause difficulties for the Bluetooth signal. It may therefore be worth checking this. How is your mouse if you place it near the back of the machine? If it seems better then a BT aerial extension may be a hardware fix you need. My cMP3.1 was ok but my cMP5.1 had a very intermittent Bluetooth connection to the mouse. I put in an aerial extension and connected an external aerial. BT mouse now perfect.

 

[rotarypower101]

The cMPs are notorious on having poor Bluetooth connections. The Bluetooth aerial is at the back of the machine and all that metal case can cause difficulties for the Bluetooth signal. It may therefore be worth checking this. How is your mouse if you place it near the back of the machine? If it seems better then a BT aerial extension may be a hardware fix you need. My cMP3.1 was ok but my cMP5.1 had a very intermittent Bluetooth connection to the mouse. I put in an aerial extension and connected an external aerial. BT mouse now perfect.

Thank you

It has always been "troublesome" for what I think are the reasons you say. This specific issue is a completely recent phenomena immediately after installing Mojave. If I go back to HS, it seems to work just fine.


Specifically it is on a magic mouse 2, which seems like a predominant keyword hit when searching.
I notice with a Microsoft sculpt mouse for CAD work (require a roller and aux buttons), and it generally connects and operate much faster than the MM2. But that is with limited observations, as it is not the typical mouse I start the day with, but seems worth mentioning.


I think I did the ipex connector check to make sure the proper one was used out of the 3 I think that were in there (and possibly mislabeled), a loooong time ago.


The issue is, I can see the curser, and the mouse will not become active until 5-10 seconds after it has been utilized. I am fairly certain the mouse is awake as I will move and click it before and during boot, and still have the same Long wait time before it is active in Mojave.


After that it is fine, connects and gives me no trouble as before on HS.


Is that description of a long wait time to activate a typical observation on Mojave and a 3,1 or any other platform for that matter to try and track down a cause and hopefully a solution?

 

[joevt]

It has always been "troublesome" for what I think are the reasons you say. This specific issue is a completely recent phenomena immediately after installing Mojave. If I go back to HS, it seems to work just fine.

I use an Apple Mighty Mouse and an Apple Wireless Keyboard that are more than 10 feet away from my MacPro3,1. The computer is placed on a shelf above the display with the side panel facing me.

 

[Flacko]

Thank you

It has always been "troublesome" for what I think are the reasons you say. This specific issue is a completely recent phenomena immediately after installing Mojave. If I go back to HS, it seems to work just fine.


Specifically it is on a magic mouse 2, which seems like a predominant keyword hit when searching.
I notice with a Microsoft sculpt mouse for CAD work (require a roller and aux buttons), and it generally connects and operate much faster than the MM2. But that is with limited observations, as it is not the typical mouse I start the day with, but seems worth mentioning.


I think I did the ipex connector check to make sure the proper one was used out of the 3 I think that were in there (and possibly mislabeled), a loooong time ago.


The issue is, I can see the curser, and the mouse will not become active until 5-10 seconds after it has been utilized. I am fairly certain the mouse is awake as I will move and click it before and during boot, and still have the same Long wait time before it is active in Mojave.


After that it is fine, connects and gives me no trouble as before on HS.


Is that description of a long wait time to activate a typical observation on Mojave and a 3,1 or any other platform for that matter to try and track down a cause and hopefully a solution?

Have a look at this thread - one of many about bluetooth issues with the cMP:

Mojave and Bluetooth Magic Mouse

Hi! I bought the osxwifi antenna kit whith completely solved the MM problem! https://www.osxwifi.com/product/mac-pro-bluetooth-antenna-kit-range-extender-external-antenna/

forums.macrumors.com

In my experience the Magic Mouse is especially sensitive to bluetooth signal strength. My trackpad was better but both improved with an external BT aerial. The correct terminal is j3 on the BCM94360CD and I used one of these to route the signal out of the back:

Premium Mini PCI UFL to SMA Female Connector Antenna WiFi Pigtail Cable IPX to SMA Extension - Black 60cm

Welcome to Prettyia! All goods are carefully selected and the prices are also optimal.Description: - SMA Bulkhead Female to IPX Ufl Female RF Coaxial Connector Pigtail Cable. - Plug Type: UFL Mini PCI to SMA Female (NO pin in center). - IPX UFL Terminal Block Connector for mini pci card. - Wide a...

www.amazon.co.uk

 

[Flacko]

I use an Apple Mighty Mouse and an Apple Wireless Keyboard that are more than 10 feet away from my MacPro3,1. The computer is placed on a shelf above the display with the side panel facing me.

My cMP3.1 is like yours. Seems to work ok. Other cMPs like my cMP5.1 have the issue. Luck of the draw on how good the internal aerial is! Mojave seems to make the problem worse for some unknown reason. Also USB 3 cards known to cause interference problems at 2.4 GHz as they sit right next to the internal aerial.

 

[Larsvonhier]

Today´s Security Update 2019-001 beta 2 still works fine with all patches (and even CFL backlight control on MBP4,1). Current build number is 18G1007.

 

[rotarypower101]

Have a look at this thread - one of many about bluetooth issues with the cMP:

Mojave and Bluetooth Magic Mouse

Hi! I bought the osxwifi antenna kit whith completely solved the MM problem! https://www.osxwifi.com/product/mac-pro-bluetooth-antenna-kit-range-extender-external-antenna/

forums.macrumors.com

In my experience the Magic Mouse is especially sensitive to bluetooth signal strength. My trackpad was better but both improved with an external BT aerial. The correct terminal is j3 on the BCM94360CD and I used one of these to route the signal out of the back:

Premium Mini PCI UFL to SMA Female Connector Antenna WiFi Pigtail Cable IPX to SMA Extension - Black 60cm

Welcome to Prettyia! All goods are carefully selected and the prices are also optimal.Description: - SMA Bulkhead Female to IPX Ufl Female RF Coaxial Connector Pigtail Cable. - Plug Type: UFL Mini PCI to SMA Female (NO pin in center). - IPX UFL Terminal Block Connector for mini pci card. - Wide a...

www.amazon.co.uk

Thank you for the information and what I think is validation something has changed.

I have 2.4ghz equipment around, maybe I will do a little testing and see if I can come up with a external antenna that helps the issue. I think I even have a .UFL to SMA pigtail in NIB.

If you know, do people usually have more luck with a patch antenna or omni directional or just a external linear does the job?

>The correct terminal is j3 on the BCM94360CD and I used one of these to route the signal out of the back:

Thank you for calling out the plug explicitly!

Do you recall anything about the MP3,1 and "mislabeled" .UFL connectors?
IIRC it was a bit ambiguous as to which on board antennas were intended for which service.

Thank you for taking the time to help 🙂

 

[Flacko]

Thank you for the information and what I think is validation something has changed.

I have 2.4ghz equipment around, maybe I will do a little testing and see if I can come up with a external antenna that helps the issue. I think I even have a .UFL to SMA pigtail in NIB.

If you know, do people usually have more luck with a patch antenna or omni directional or just a external linear does the job?

>The correct terminal is j3 on the BCM94360CD and I used one of these to route the signal out of the back:

Thank you for calling out the plug explicitly!

Do you recall anything about the MP3,1 and "mislabeled" .UFL connectors?
IIRC it was a bit ambiguous as to which on board antennas were intended for which service.

Thank you for taking the time to help 🙂

Test the mouse with it very close to the back of your machine. If it improves then external aerial is the fix.

Yes, there were some issues with cMP3.1 aerial leads being mislabelled. I believe this was only on a few machines. Anyway, if you go for an external aerial then connect it to J3 as the order of the other aerials is not critical. This will override any mislabelled leads if you happen to have one of the cMP affected.

Once you have an external connection then any 2.4GHz extension aerial will work. I am using one for a mobile phone device and have it taped under my desk - works a treat.

If you need more help/info then start a new conversation with me as this is a bit off topic for this thread now.

 

[jhowarth]

On my MacPro 3,1 with GTX680, applying today's security update resulted in the machine restarting at the very end of the progress bar with the machine crashed unexpectedly splash screen on reboot. Booting from the usb installer created with Mojave Patcher 1.3.3 and re-applying the patches eliminated that boot problem and now the system reports the version as 18G1007 as expected.

 

[Syncretic]

My SSE 4.2 emulator (MouSSE), which enables the Mac Pro 3,1 to run the AMD Metal drivers, is finally going public. See this post for details.