macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

Btw, I didn't do a clean install but I just updated from El Capitan maybe this wasn't the right way and could have caused the issue.

No, I did clean install and I still have the same "issue", among 16 intervals of brightness available only 2-3 are working.

This should be related to some kind of incompatibility with AppleBacklight*.kext or maybe this AppleGraphicsControl.kext? AppleGraphicsPowerManagement.kext ?

But I am not sure.

 

[0403979]

No, I did clean install and I still have the same "issue", among 16 intervals of brightness available only 2-3 are working.

This should be related to some kind of incompatibility with AppleBacklight*.kext or maybe this AppleGraphicsControl.kext? AppleGraphicsPowerManagement.kext ?

But I am not sure.

Both of you try this.

@jackluke @Skorpion24

 

[Flacko]

Yes, also dosdude1 explained that, the Bluetooth kext have a strange behavior on different machines, anyway before re-installing try first to use the IOBluetooth*.kext inside the /USBMojaveInstaller/S/L/E/ replacing yours in your /S/L/E/ and see what happens.

BT now working in 14.1 whoopee! I will outline what I did as it may help those more knowledgeable than myself get to the bottom of this Mojave BT problem. I may have been just lucky.
Firstly, replacing IOBluetooth kexts with those from the usb did not work. Also trying the wifi patch did not have any affect. Wifi still ok though.
Wiped drive and installed fresh copy of 14.1. Had a quick look at the IOBluetooth kexts and they were now full versions 6.09. So different from 6.08 in Mojave 14.0. Replaced IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext with those from HS which worked for me in Mojave 14.0 (version 6.07). As before no BT in 14.1. Using show package contents I looked at the info.list for IOBluetoothFamily.kext and saw a reference to these kexts under OSBundleLibraries: IOACPIFamily, IOReportFamily and IOUSBHostFamily So I first replaced IOACPIFamily.kext with one from HS. Note both the Mojave and high Sierra versions were the same (1.4) but the file sizes were a little bit different. On restart bluetooth sprang to life. I now have full BT4.0 with continuity/handoff etc. Mouse and trackpad working normally. I shall now try to do this on my main system.

 

[jackluke]

BT now working in 14.1 whoopee! I will outline what I did as it may help those more knowledgeable than myself get to the bottom of this Mojave BT problem. I may have been just lucky.
Firstly, replacing IOBluetooth kexts with those from the usb did not work. Also trying the wifi patch did not have any affect. Wifi still ok though.
Wiped drive and installed fresh copy of 14.1. Had a quick look at the IOBluetooth kexts and they were now full versions 6.09. So different from 6.08 in Mojave 14.0. Replaced IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext with those from HS which worked for me in Mojave 14.0 (version 6.07). As before no BT in 14.1. Using show package contents I looked at the info.list for IOBluetoothFamily.kext and saw a reference to these kexts under OSBundleLibraries: IOACPIFamily, IOReportFamily and IOUSBHostFamily So I first replaced IOACPIFamily.kext with one from HS. Note both the Mojave and high Sierra versions were the same (1.4) but the file sizes were a little bit different. On restart bluetooth sprang to life. I now have full BT4.0 with continuity/handoff etc. Mouse and trackpad working normally. I shall now try to do this on my main system.

Well done, just to add a tip to this, a kext bundle can be also detected through Terminal:
kextlibs /System/Library/Extensions/IOBluetoothFamily.kext

Honestly I am a bit afraid of replacing a kext like "IOACPIFamily.kext" and in general any *ACPI*.kext, but @Flacko I really appreciate your good fix.
[doublepost=1541255944][/doublepost]

Both of you try this.

@jackluke @Skorpion24

Now I'm far from that machine, laptops are ok, will give a try next days.

 

[0403979]

Well done, just to add a tip to this, a kext bundle can be also detected through Terminal:
kextlibs /System/Library/Extensions/IOBluetoothFamily.kext

Honestly I am a bit afraid of replacing a kext like "IOACPIFamily.kext" and in general any *ACPI*.kext, but @Flacko I really appreciate your good fix.
[doublepost=1541255944][/doublepost]

Now I'm far from that machine, laptops are ok, will give a try next days.

Alright. I think I recommended this to someone before and it worked. You can search the thread and check.

 

[dharnidhar]

Hi friends, did anyone ran into issues when running Microsoft PowerPoint 2016 in slideshare (presentation) mode, it shows blank screen. When you run the same from Keynote, it works well. I am using late 2011 Macbook Pro machine, 8GB RAM.

 

[LuisN]

Yes, but I should be able to replace the ones I have with ones of my own. I my regular Mac not patched I have changed them many times. These settings are locked. Would you please check your settings and see if the minus on the bottom is not grayed out like mine.

UPDATE: I deleted all my network setting and flushed it. Then started from scratch and applied new DNS. I also blocked access to these DNS addresses. I will watch it as I have put FING on alert.

those are the addresses given to you by your ISP dhcp server, to replace those you must click "+" and write your own addresses. It worked like this since forever. As soon as you add your preferred ip addresses for your preferred servers they will disappear. YOU'RE NOT HACKED. ;-)

BEFORE:

AFTER:

[doublepost=1541258813][/doublepost]

Hi friends, did anyone ran into issues when running Microsoft PowerPoint 2016 in slideshare (presentation) mode, it shows blank screen. When you run the same from Keynote, it works well. I am using late 2011 Macbook Pro machine, 8GB RAM.

I had similar problems with Firefox and wvmware fusion where the main window showed blank. It disappeared after a clean install of Mojave. It only occurred after importing settings from High Sierra using Migration Assistant. Yes, I had to reinstall everything again :-(

 

[AphoticD]

To avoid the "line with circle", just enforce your compatibility platform check, the most strong to override everything is booting from any USB macOS Installer (higher than El Capitan), open Terminal and type:
nvram boot-args="-no_compat_check"

Thanks. I reformatted the SSD (APFS on GUID), ensuring the device was selected with the View menu "Show All Devices" option. I then reinstalled Mojave 10.14.1 with the Patcher. Upon reboot I get the circle with a line through it. I tried setting the boot-args as recommended and the result is still the same.

The volume is available in the boot selector now, but this appears to be as far as it gets.

 

[jackluke]

Thanks. I reformatted the SSD (APFS on GUID), ensuring the device was selected with the View menu "Show All Devices" option. I then reinstalled Mojave 10.14.1 with the Patcher. Upon reboot I get the circle with a line through it. I tried setting the boot-args as recommended and the result is still the same.

The volume is available in the boot selector now, but this appears to be as far as it gets.

Are you sure have you typed correctly the nvram command (with quotes, minus sign and underscores)?

Then boot again from the USB Installer, open Terminal and type:
nvram boot-args="-no_compat_check -v"

nvram -p (check that boot-args are stored on print screen)

Then from the "apple icon" upper-left open "Startup Disk" and target your Mojave APFS Volume and reboot.

After reboot you will not encounter more "line-circle" but a verbose screen, and post here a picture screen to help in further diagnostic.

edit:
<<ensuring the device was selected with the View menu "Show All Devices. Then reinstalled Mojave 10.14.1 with the Patcher.">> is a dosdude1 advise, not mine.

Not for nothing, in general I try everything to avoid a re-installation, I do prefer cloning than re-installing.

 

[LuisN]

Thanks. I reformatted the SSD (APFS on GUID), ensuring the device was selected with the View menu "Show All Devices" option. I then reinstalled Mojave 10.14.1 with the Patcher. Upon reboot I get the circle with a line through it. I tried setting the boot-args as recommended and the result is still the same.

The volume is available in the boot selector now, but this appears to be as far as it gets.

Did you boot a second time with the usb and applied the patches?

 

[TimothyR734]

Hi guys, I think I may have messed up here, I had 10.14 installed on my MB5,2 and I updated the drive to APFS but now It won't boot and all I get is a load of script running on the screen then it boots into the usb drive, anyone any idea?

If you haven't installed the APFS boot rom patch when you start you MacBook up hold down the option button and select EFI drive

 

[AphoticD]

Are you sure have you typed correctly the nvram command (with quotes, minus sign and underscores)?

Then boot again from the USB Installer, open Terminal and type:
nvram boot-args="-no_compat_check -v"

nvram -p (check that boot-args are stored on print screen)

Then from the "apple icon" upper-left open "Startup Disk" and target your Mojave APFS Volume and reboot.

After reboot you will not encounter more "line-circle" but a verbose screen, and post here a picture screen to help in further diagnostic.

Thanks for the quick response. nvram boot-args is set A OK.

Here's the verbose output showing where it stops.

 

[joelw135]

those are the addresses given to you by your ISP dhcp server, to replace those you must click "+" and write your own addresses. It worked like this since forever. As soon as you add your preferred ip addresses for your preferred servers they will disappear. YOU'RE NOT HACKED. ;-)

The problem I had was that trying to add the new DNS didn't work when apply was pressed. So I had to delete everything and then restore. I then was able to replace those placed by Xfinity. I thought I was hacked as 75.75.75.75 and 76.76.76.76 were recently affected by DNS poisoning.

 

[AphoticD]

Did you boot a second time with the usb and applied the patches?

I did. I also re-ran the patcher a second time after another reboot and forced the cache rebuild. still no luck.

 

[zrw2011]

Always apply the patch built for your release of Mojave. These are core framework patches and all these frameworks are highly inter-dependent. If you haven't run into problems so far, you will eventually. So please apply the latest cut as soon as possible. I state as much in the github repo docs and readme.

v1.2 simply brings it up to date with 10.14.1. No new features as of yet. We are feverishly working on new UI fixes and even better approaches. In the meantime, we hope these satisfy all Light Mode vibrancy lovers out there...

It's perfect as always.
I'm using Flat mode, it's very beautiful.

Thanks man

I tried replacing appkit framework files from the downloaded folder of "current" to the folder in system/library/frameworks/ and nothing happens what am I doing wrong?

 

[swamprock]

Installed 10.14.1 over 10.13.6 using the latest patch on my 13" Macbook Pro 5,5. I converted the drive to APFS first, the proceeded with the install, rebooting back into the patcher and installing the post-install patches. Had a stalled boot issue at first, where it stalled on the loading screen. Rebooting into the patch USB and clearing boot caches solved the issue, and everything seems to be running stable.

 

[pkouame]

I tried replacing appkit framework files from the downloaded folder of "current" to the folder in system/library/frameworks/ and nothing happens what am I doing wrong?

Unfortunately, not enough information to know exactly what you did. There are extensive docs in the repo on performing a manual installation and/or recovering. Very simple in fact once you understand the concept. I would start there, but in a nutshell: navigate within the framework - backup the old binary - copy the new one in-place - reboot. Of course, make sure you use the right files for your macOS release (v1.2 targets 18B75 - 10.14.1 only).
I you find this daunting, simply wait for an upcoming release with some bullet proofed installation scripts.
Good luck.

 

[dharnidhar]

those are the addresses given to you by your ISP dhcp server, to replace those you must click "+" and write your own addresses. It worked like this since forever. As soon as you add your preferred ip addresses for your preferred servers they will disappear. YOU'RE NOT HACKED. ;-)

BEFORE:
View attachment 800928
AFTER:
View attachment 800929
[doublepost=1541258813][/doublepost]
I had similar problems with Firefox and wvmware fusion where the main window showed blank. It disappeared after a clean install of Mojave. It only occurred after importing settings from High Sierra using Migration Assistant. Yes, I had to reinstall everything again :-(

I did not try a fresh installation, it was an upgrade from High Sierra. It was working well on High Sierra though without any problem.

 

[OGNerd]

Going bonkers in the nut..
Mac Pro 3.1 new SSD, trying to install Mojave, using Disk Utility on the patcher USB formatting disk as APFS.
Then install Mojave, boot to USB, apply patches including APFS patch, reboot.
Get the APFS verbose start up screen, goes to Apple screen and hey presto opens up on my Sierra drive every time.
So remove all other disks in the 3.1 and it will boot to the Mojave disk, put the other disks back in and same thing happens, looks like it is booting to Mojave but then boots to Sierra disk.

Any ideas otherwise going back to rubbing sticks together and eating things raw.

Do you have a machine that natively supports APFS? If so, set your 3,1 in target disk mode and install Mojave on it from the machine with native APFS support, apply the appropriate post-install patches (especially the APFS boot patch) from the natively supported machine. Return the 3,1 to normal mode, and you should then be able to Option-Key boot into Mojave on the 3,1. It appears that APFS firmware is required to properly install the boot patch on unsupported machines.

 

[jon8214]

If you haven't installed the APFS boot rom patch when you start you MacBook up hold down the option button and select EFI drive

Thanks, I did that, and it started into the OS and shows as an APFS drive, where can I get the APFS boot rom patch? I see from the first link its been removed by Dosdude.

Is that the only way to stop the text running on my MB when I start it up?

 

[zrw2011]

Unfortunately, not enough information to know exactly what you did. There are extensive docs in the repo on performing a manual installation and/or recovering. Very simple in fact once you understand the concept. I would start there, but in a nutshell: navigate within the framework - backup the old binary - copy the new one in-place - reboot. Of course, make sure you use the right files for your macOS release (v1.2 targets 18B75 - 10.14.1 only).
I you find this daunting, simply wait for an upcoming release with some bullet proofed installation scripts.
Good luck.

So Did I do it correctly?

 

[bmillz]

I was wondering if there has been any update to improving the font in Mojave...the fact that it is kind of blurry/unsharp? I am using a MBP 5,4 on 10.14.1

Thanks for any/all help!

Like someone else said, the beta version of Onyx has support for enabling the sub pixel antialiasing that Apple decided to disable by default on Mojave. If you are just interested in the code, copy and paste this into Terminal:

defaults write -g CGFontRenderingFontSmoothingDisabled -bool FALSE

I did this on all of my non-retina Macs, and text is WAY more readable now. Just remember to reboot or log out and log back in after you apply it.

 

[kautame]

Re-apply the post-install patch.

I have a strange problem: iMac 7,1 - Mojave 10.14.1 installed with version 1.2.3 of the Patcher (but it happened with 10.14.0 too):

at boot, after the chime, nothing happens: the screen is white, and stays so forever. But if I turn on the iMac with ALT-key pressed and select my internal disk (the only available), it boots. Every time. It's like it couldn't decide from what to boot, even if there is only a bootable disk available.
If I go to System Preferences and click on the "APFS Boot" panel, it immediately crashes System Preferences. This, too, happened also in 10.14.0. Is it related to my problem?

I've tried many times to re-apply the post-install patch without results.

What can I do?

 

[dosdude1]

I have a strange problem: iMac 7,1 - Mojave 10.14.1 installed with version 1.2.3 of the Patcher (but it happened with 10.14.0 too):

at boot, after the chime, nothing happens: the screen is white, and stays so forever. But if I turn on the iMac with ALT-key pressed and select my internal disk (the only available), it boots. Every time. It's like it couldn't decide from what to boot, even if there is only a bootable disk available.
If I go to System Preferences and click on the "APFS Boot" panel, it immediately crashes System Preferences. This, too, happened also in 10.14.0. Is it related to my problem?

I've tried many times to re-apply the post-install patch without results.

What can I do?

Download and run this tool to bless the ESP of your drive containing your Mojave APFS volume. Then, it should work fine.

 

[jackluke]

Thanks for the quick response. nvram boot-args is set A OK.

Here's the verbose output showing where it stops.

View attachment 800955

Your issue is a bit weird, from your picture the efiboot file path is wrong, it should be only \System\Library\CoreServices\boot.efi
the UUID pre-folders are only used on Preboot and Recovery, neither VM uses a UUID folder but only /private/var/vm/

So try this, boot into your USB Installer, open Terminal:

diskutil apfs list
(locate your APFS Mojave main Volume typically disk1s1 otherwise diskXs1)

diskutil mount diskXs1

bless --folder /Volumes/"Your Mojave Label"/System/Library/CoreServices --bootefi

diskutil apfs updatePreboot diskXs1

bless --folder /Volumes/"Your Mojave Label"/System/Library/CoreServices --bootefi
(yes type it before and after to enforce)

reboot

BUT after reboot this time hold and keep alt-option key to show the startup manager and see how many bootable Volume are available, highlight with the arrows (left-right) the Mojave one and press enter.