macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

Looks like I made too much of a bold jump here (from 10.14.3 to 10.14.6 Beta).
For whatever reason it seems that this "combo" update did not actually do the Safari update, so now I am getting bombarded with this.

View attachment 838913

Surely it's a too high jump from .3 to .6 beta 1 especially for a Beta where the official Combo package hasn't been released officially by apple even if it's in sucatalog, and consider also that a manual update has some side effects versus an official pkg installer update, anyway I guess it could be fixable with next update to .6 PB2 .

edit: and you had also a .5 T2 Chip unwanted update applied, I guess
[doublepost=1558791214][/doublepost]

Huge thanks for helping me. This worked, i’m booted into Mojave, but system is unusable, gui looks like in safe mode. System very slow. What should i do next? Or i need to reinstall system anyway?

Without the Mojave USB Post-Install in the pocket it's not so agile, but to enable the non-metal acceleration you need to do this:

1) Download and apply this: non-metal OpenGL
but do NOT reboot/restart yet

2) You need to replace also CoreDisplay.framework from .3 but this can only be done from single user mode CMD+S if you replace it on-the-fly your system won't be more bootable
you can download it from CoreDisplay.framework.zip

3) You need to replace also the IOGraphicsFamily.kext , IONDRVSupport.kext, IOAccel*.kext with those from HighSierra and rebuild a kextcache with them you can download them from Mojave10145DualGpuFix.zip

What I can suggest is to rename the downloaded CoreDisplay.framework in CoreDisplay.framework2 and copy it in your Mojave /System/Library/Frameworks/

then from single user mode booting with CMD+S you can replace it in this way:

mount -uw /
cd /System/Library/Frameworks

ls CoreDisplay.*

(Checking that you have two CoreDisplay folders means you are in the right mount point)

mv CoreDisplay.framework CoreDisplay.backup
mv CoreDisplay.framework2 CoreDisplay.framework
exit


I know it's a long story doesn't worth it, better to re-download and make again a full Mojave Patcher.

 

[16v]

Question:

I got a logitech mk800 desktop set.
Unifying usb dongle.
Does it work with apple/mojave?

Cause i plugged in the dongle, and it told me to press a key on keyboard to detect it.
No response.
And also at this moment mouse isnt working.

Thx

 

[avz]

Surely it's a too high jump from .3 to .6 beta 1 especially for a Beta where the official Combo package hasn't been released officially by apple even if it's in sucatalog, and consider also that a manual update has some side effects versus an official pkg installer update, anyway I guess it could be fixable with next update to .6 PB2 .

Once again APFS local snapshots allowed me to go 10.14.3 - 10.14.6 Beta - 10.14.3 in about 20 min! At least I've learned something. Always install only officially released updates!

 

[upipes]

This should be the path where apple channels temporary downloads caches are stored: /private/var/folders/zz/

but if you already downloaded I guess at next reboot/power-on it will install itself without warning, anyway others have already installed this supplemental update and it doesn't destroy the unsupported Mac, only issue from what I read is that makes it slower in core processes with bad RAM management.

My zz folder only weights 3,4Mb... so it's not downloaded I guess. Still shows an update available, but I don't mind.
Let's see how's going to be this story shortly.

Thank you very much

 

[deeveedee]

Just updated my HackBookPro 5,1 (Thinkpad T61, Penryn T9300, Nvidia NVS 140m, 8GB DDR2) to Mojave 10.14.5 using DosDude's Mojave Patcher. I applied the 10.14.5 update directly (to 10.14.4) from the AppStore and then applied post install patches with DosDude's patched USB Installer before booting 10.14.5 for the first time. Not sure why, but I needed several attempts to boot the patched USB Installer before I got into the Mojave install GUI and could apply the post install patches. After the USB installer booted, patching was easy. Great job DosDude / all who made this possible!

 

[jackluke]

Once again APFS local snapshots allowed me to go 10.14.3 - 10.14.6 Beta - 10.14.3 in about 20 min! At least I've learned something. Always install only officially released updates!

Apart the unwanted Mojave .5 T2 Chip update on non-targeted machine, I guess that an OSX beta version "high jump" update is not contemplated by apple, I mean if you enroll in beta program on supported Mojave Mac, you can't jump directly from .3 to .6 beta (I've tested it), but first the Mojave's Software Update will offer an update to .5 then after its completion to .6 beta 1, so that's why I guess you had that SafariSync issue, I think manual "pkgutil expand" isn't the main cause of those side effects.

 

[avz]

Apart the unwanted Mojave .5 T2 Chip update on non-targeted machine, I guess that an OSX beta version "high jump" update is not contemplated by apple, I mean if you enroll in beta program on supported Mojave Mac, you can't jump directly from .3 to .6 beta (I've tested it), but first the Mojave's Software Update will offer an update to .5 then after its completion to .6 beta 1, so that's why I guess you had that SafariSync issue, I think manual "pkgutil expand" isn't the main cause of those side effects.

Agreed. I think that manual 'pkgutil expand" did work quite well but it is also possible that .5 T2 Chip update was somehow baked into that Combo update. I experienced the same out of control RAM usage that others have reported after the .5 T2 Chip supplemental update. I was completely sold by the "Combo" status of the update as it usually means all-inclusive, so I decided to give it a go. It is possible that when it comes to Betas, Combo means entirely different thing.

 

[honglong1976]

You are correct. Keep in mind that APFS ROM patcher is a risky business, especially for the machines with MCP79 chipset(your MBP).

It worked!

APFS ROM Patcher run. Took about 10 mins but worked ok.

Then I converted to APFS by booting from the USB stick with Mojave on.

1. Open Disk Utility

2. Click on the SSD volume, then click the Unmount button (this is the trick).

3. In the Edit menu, you can now select Convert to APFS...

4. Proceed and done

5. Rebooted and I am back in!

Thanks dosdude!

 

[Dannyy]

Surely it's a too high jump from .3 to .6 beta 1 especially for a Beta where the official Combo package hasn't been released officially by apple even if it's in sucatalog, and consider also that a manual update has some side effects versus an official pkg installer update, anyway I guess it could be fixable with next update to .6 PB2 .

edit: and you had also a .5 T2 Chip unwanted update applied, I guess
[doublepost=1558791214][/doublepost]

Without the Mojave USB Post-Install in the pocket it's not so agile, but to enable the non-metal acceleration you need to do this:

1) Download and apply this: non-metal OpenGL
but do NOT reboot/restart yet

2) You need to replace also CoreDisplay.framework from .3 but this can only be done from single user mode CMD+S if you replace it on-the-fly your system won't be more bootable
you can download it from CoreDisplay.framework.zip

3) You need to replace also the IOGraphicsFamily.kext , IONDRVSupport.kext, IOAccel*.kext with those from HighSierra and rebuild a kextcache with them you can download them from Mojave10145DualGpuFix.zip

What I can suggest is to rename the downloaded CoreDisplay.framework in CoreDisplay.framework2 and copy it in your Mojave /System/Library/Frameworks/

then from single user mode booting with CMD+S you can replace it in this way:

mount -uw /
cd /System/Library/Frameworks

ls CoreDisplay.*

(Checking that you have two CoreDisplay folders means you are in the right mount point)

mv CoreDisplay.framework CoreDisplay.backup
mv CoreDisplay.framework2 CoreDisplay.framework
exit


I know it's a long story doesn't worth it, better to re-download and make again a full Mojave Patcher.

Many thanks for help. Your instructions solved my problem, I booted into Mojave, GUI and system worked as it should, and I could end my job. There was only one problem that made me reinstall Mojave anyway, is overheating CPU. I had about 100 degrees Celsius, and fan speed 6200 rpm. At that moment, in activity monitor "kernel_task" used most of CPU. But that's doesn't matter anymore, I got to my house and reinstall system. Now everything works well. Thank you again.

 

[jackluke]

Many thanks for help. Your instructions solved my problem, I booted into Mojave, GUI and system worked as it should, and I could end my job. There was only one problem that made me reinstall Mojave anyway, is overheating CPU. I had about 100 degrees Celsius, and fan speed 6200 rpm. At that moment, in activity monitor "kernel_task" used most of CPU. But that's doesn't matter anymore, I got to my house and reinstall system. Now everything works well. Thank you again.

If you before used this zip package/script that I did specifically for dualGPUs 2010 machines
"Mojave10145DualGpuFix.zip", and you have launched the "command file" to install it with all the content of "Ext" folder, then I guess to settle down the intensive cpu usage you'd had followed that pdf I wrote inside, I mean replace also the "PrivateFramework" GPUWrangler.framework the same way of CoreDisplay, but only if you installed the entire zip package/script through the ".command" because GPUWrangler.framework is strictly dependent from AppleGraphicsControl.kext .

From my other tests using a previous GPUWrangler.framework seems to settle down cpu% temperature calming fans rpm.

edit:
those files I uploaded before (CoreDisplay included) belong to HighSierra 17G6030 , and I'll align them maybe on final 10.14.6 release with those more updated from HS 17G7024 that in an ideal time-line are much closer to the Mojave ones.

 

[jasoncarle]

I have really been considering putting my Mini back on High Sierra, but I can't help but remember how bad it was at using disk space... I would have to get a bigger SSD as well for the Mini, and I just ordered RAM. This old machine just isn't worth it because it's not my primary machine...

Decisions decisions.

 

[antibolo]

Keep in mind that while entering the FileVault EFI password the keyboard layout is ALWAYS the US one, no matter wether you have an AZERTY, QWERTZ or whatever keyboard layout. This might help. Thus if you set your password with a Z you might need to enter an Y for unlocking the EFI (QWERTZ). This gets even more funny with special keys. Consult your search engine regarding the mapping.

———————————————————

EDIT:
Well, just filed an issue with apple. I suggest you do so, too. – Issue #6095763

Also filed an issue for having the keyboard backlight while entering the password. – Issue #6095766

No I’m always QWERTY, and it doesn't hide your input when typing in the recovery key anyway so I know for sure it was entered correctly. And said recovery key works for unlocking the volume from the USB installer.

Kinda out of ideas on what to do next. Guess I’ll wipe again and go back to HFS+ which definitely worked last time. Sigh...

 

[Kevbasscat]

On my Mac Pro 3,1 on 10.14.5 patched with dosdude 1's patch, I got also the T2 Supplemental Update notice.

I refused to upgrade because I don't understand why its showing on a non related computer !!!!!!!!! Very strange ??????

You're smart, and you actually read what the updates are for. I have automatic updates turned off for that reason.

 

[DuncanGarp]

That didn't work either. Thanks for the suggestion.
[doublepost=1558759657][/doublepost]

Getting late. So I'll try another alternative tomorrow. Good night!

Still no luck. I guess I just have to wait for the final release of 10.14.6. Any speculation on when this will be out?

 

[TimothyR734]

1014,6 beta might be out next week that should override the supplemental

 

[Marty56]

Just updated my HackBookPro 5,1 (Thinkpad T61, Penryn T9300, Nvidia NVS 140m, 8GB DDR2) to Mojave 10.14.5 using DosDude's Mojave Patcher. I applied the 10.14.5 update directly (to 10.14.4) from the AppStore and then applied post install patches with DosDude's patched USB Installer before booting 10.14.5 for the first time. Not sure why, but I needed several attempts to boot the patched USB Installer before I got into the Mojave install GUI and could apply the post install patches. After the USB installer booted, patching was easy. Great job DosDude / all who made this possible!

same with my macbook pro 5.3. I already thought that I have bricked my mac.

 

[jasoncarle]

This just happened. Safari tech Preview appeared as a really odd desktop picture. Nothing else was affected and the computer was working properly, no hung programs. Manually changing the desktop picture switched it back to normal too. I have never seen this happen before though.

 

[Sedulous]

In case anyone else wants their unsupported Mac to avoid the T2 update, you can use terminal to ignore the update.

softwareupdate --ignore "MacBook Pro Supplemental Update"

 

[hvds]

In case anyone else wants their unsupported Mac to avoid the T2 update, you can use terminal to ignore the update.

softwareupdate --ignore "MacBook Pro Supplemental Update"

Indeed - thanks! Now I only see the 10.14.6b1 again.
[doublepost=1558852077][/doublepost]

If you before used this zip package/script that I did specifically for dualGPUs 2010 machines
"Mojave10145DualGpuFix.zip", and you have launched the "command file" to install it with all the content of "Ext" folder, then I guess to settle down the intensive cpu usage you'd had followed that pdf I wrote inside, I mean replace also the "PrivateFramework" GPUWrangler.framework the same way of CoreDisplay, but only if you installed the entire zip package/script through the ".command" because GPUWrangler.framework is strictly dependent from AppleGraphicsControl.kext .

From my other tests using a previous GPUWrangler.framework seems to settle down cpu% temperature calming fans rpm.

edit:
those files I uploaded before (CoreDisplay included) belong to HighSierra 17G6030 , and I'll align them maybe on final 10.14.6 release with those more updated from HS 17G7024 that in an ideal time-line are much closer to the Mojave ones.

Thanks jackluke.

That reminded me of re-applying your Mojave10145DualGpuFix after I had re-installed 10.14.5 with dodsude 1.3.2 patcher. For my Arduino purposes I've added AppleUSBACM.kext (from 10.13.6) to the Ext folder. The .command is really convenient for "post-post-install" patching.

(MBP5,2 17" 2.8GHz mid 2009, APFS ROM patch applied, Samsung SSD 860 EVO with APFS.)

BTW I removed some debris from early (many years ago) VirtualBox attempts. Now the output after kextcache -i is clean.

 

[avz]

In case anyone else wants their unsupported Mac to avoid the T2 update, you can use terminal to ignore the update.

softwareupdate --ignore "MacBook Pro Supplemental Update"

This is great! Does it ever gets more intuitive than that?
[doublepost=1558852568][/doublepost]

This just happened. Safari tech Preview appeared as a really odd desktop picture. Nothing else was affected and the computer was working properly, no hung programs. Manually changing the desktop picture switched it back to normal too. I have never seen this happen before though.

I have experienced Safari Technology Preview 12.2 crashes when closing tabs on Mojave and High Sierra. It might actually related to the AdGuard for Safari. Not sure if its relates to your issue though.

 

[Rastafabi]

No I’m always QWERTY, and it doesn't hide your input when typing in the recovery key anyway so I know for sure it was entered correctly. And said recovery key works for unlocking the volume from the USB installer.

Kinda out of ideas on what to do next. Guess I’ll wipe again and go back to HFS+ which definitely worked last time. Sigh...

Qwerty US or another one? With others you'd have the same special character mapping issue.
Of course you have input! Just a different one, which you'd not be able to determine as it's displayed as asterisks. And of course it would work in the macOS UI - either the system or the Recovery HD - as by then the legit keyboard layout would have been loaded.
Else you probably should just stay with APFS anyway, which has several benefits, but just not use FileVault.

 

[jackluke]

This is great! Does it ever gets more intuitive than that?
[doublepost=1558852568][/doublepost]

I have experienced Safari Technology Preview 12.2 crashes when closing tabs on Mojave and High Sierra. It might actually related to the AdGuard for Safari. Not sure if its relates to your issue though.

Agree, it was very logical (if I knew), and during this T2 Chip update period I had also verified a couple of times from Terminal:

man softwareupdate

And how I made to don't notice it from this clear obvious apple guide I don't explain, maybe I scrolled too fast the unix manual and so I ignored the "ignore" natural feature.

Now I have a doubt: if someone from a Mojave HFS Installation, through Terminal force to --download a Mojave OTA Update, and then force to --install it, the OTA update process does convert the HFS Volume without warning directly to APFS ?

Because if keeps it in HFS that would be great.

     -d | --download
                 Each update specified by args is downloaded but not
                 installed. The values of args are the same as for the
                 --install command. Updates downloaded with --download can be
                 subsequently installed with --install, or through the App
                 Store (as long as they remain applicable to your system).
                 Updates are downloaded to /Library/Updates, but are not
                 designed to be installed by double-clicking the packages in
                 that directory: always use --install or the App Store to
                 actually perform the install.

     --ignore identifier ...
                 Manages the per-machine list of ignored updates. The
                 identifier is the first part of the item name (before the
                 dash and version number) that is shown by --list.  See
                 EXAMPLES.

     --reset-ignored
                 Clears the per-machine list of ignored updates.

 

[jackluke]

My zz folder only weights 3,4Mb... so it's not downloaded I guess. Still shows an update available, but I don't mind.
Let's see how's going to be this story shortly.

Thank you very much

I wasn't been accurate, the official OTA Mojave Updates downloaded folder is this: /Library/Updates/

 

[hal90088]

In case anyone else wants their unsupported Mac to avoid the T2 update, you can use terminal to ignore the update.

softwareupdate --ignore "MacBook Pro Supplemental Update"

In supported apple machines this update doesn't appears. Only in the Macbook Pro with the T2 Chip. So I think that this update can't be applied on our unsupported computers.

It seems that this line of code is easy to add to the patch of mojave. I think that @dosdude1 may considder to add it in the patch.

I tried the line of code and it works perfectly.

 

[honglong1976]

One more question. I now have an APFS formatted drive and flashed macbook pro firmware.

is it safe to update the OS through OS X or still need to be done by USB?

thanks for your help