macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

not working here, Mac mini Server (Mid 2011)

100% working, first you must have an APFS scheme over the entire hard disk, I mean an EFI FAT32 partition on disk0s1, an APFS container on disk0s2, then following an APFS scheme on disk1, so disk1s1 Mojave, disk1s2 Preboot, disk1s3 Recovery, disk1s4 VM, if you don't have this scheme of course it won't work. By the way this I described is a standard/default APFS scheme.

And most of all the APFS scheme must be untouched, if you attempted some repartitioning before, it won't work naturally.

 

[baronerosso]

[doublepost=1538765845][/doublepost]

This has been fixed, just install the latest update to the patch.

Solving with Time Machine resuming IO Bluetooth ext not patched and a nvram reset.

On Mac mini Server (Mid 2011) Macmini5,3 bluetooth is working perfectly without patch.

 

[Sveto]

You can't discount the impact of the end of Moore's law on all of this. The CPU performance increases have slowed so dramatically that their whole model was put at risk when the 5-6 year speed increases were halved. Apple has been forced to work around that at the margins with increases in GPU and SSD performance.

That's the perspective of a big corporation. The regular customers (read most of us) are screed by those corporations in every step of the way. So, if imposible to use my perfectly fine hardware dated a few years back with the latest macOS version, I can still go to Windows. It is fast, with a beautiful dark mode, which does perfect black backgrounds on white text (easy to read even from a distance) and blurred transparency on the sides, runs on all hardware and most of all there is a program for everything, which always works. Come to compare it, dark mode in apple is even inferior to windows 10 dark mode. Darn Apple.
[doublepost=1538766393][/doublepost]

To those who use Mojave on APFS file system, I have managed to "fix" the APFS Recovery Volume to make it bootable with CMD+R and mainly with USB input devices responsive, working wifi and everything else, just follow next steps, boot from a Mojave APFS Volume, launch Terminal and type:

diskutil apfs list
{locate your "APFS Recovery Volume" diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}

diskutil mount diskXs3
open /Volumes/Recovery

landing on Finder, double tap on the "random-numbers-letters" folder, once inside rename these files:

prelinkedkernel into prelinkedkernelbackup
immutablekernel into immutablekernelbackup
PlatformSupport.plist into PlatformSupportbackup

Don't close Finder yet, once you renamed those 3 files, press CMD+N, then from this new Finder Window press CMD+SHIFT+G (or use "Go to Folder"): /System/Library/PrelinkedKernels/

while inside this path copy the file prelinkedkernel into the previous Finder Window, exactly were you renamed those 3 files, lastly rename this fresh copied file from prelinkedkernel to immutablekernel

Now you have a working APFS Recovery Volume.

edit:
On APFS scheme the "APFS Recovery Volume" is always on the 3rd (hidden) partition.

Thank you very much

 

[jackluke]

@baronerosso I have read before your edited message, if you have APFS Container on disk1 and so APFS Recovery Volume on disk2s3, I guess to use the CMD+R recovery feature you should have the APFS container on disk0 , however if you don't have an HFS partition with another Recovery on disk1, it will work even on APFS container on disk2, disk3 and so on.

If you get Prohibitory Symbol holding CMD+R at power-on, probably your current Recovery (located on disk1s2 or disk1s3) points to the HFS file system one, for HFS Recovery see my previous post, you can mount your HFS Recovery from Mojave, once inside rename the PlatformSupport.plist to something as PlatformSupportbackup and overwrite the prelinkedkernel (without renaming into immutablekernel this is a requirement only for APFS), and you can boot from the HFS Recovery.

edit:
I don't remember exactly your message so probably the 50% of what I wrote now are foolishness.

 

[Doomsday4949]

after the latest patch I no longer have bluetooth does anyone know how to fix this

 

[lukiy]

Safe mode in your case seems a better clean way to do it (probably drops some extra extensions/frameworks), however do a couple of DiskUtility's First Aid on your disk and then try this very useful guide: https://support.apple.com/en-us/HT203538

Tried creating a new admin user under safe mode and.. nope nope nope, opening any 32 bit app just ends up with the icon keep bouncing

This is a really weird problem. I tried resetting the file permissions too, no luck.

And there is nothing whatsoever in Console.app log about this issue.

What could it be? I have a feeling this is due the unsupported machine. Maybe one of the kexts?

 

[dosdude1]

after the latest patch I no longer have bluetooth does anyone know how to fix this

What machine is it?

 

[Doomsday4949]

What machine is it?

Mac mini server mid 2011
was working fine until the patch forced me to reboot.

 

[0403979]

Removed.

 

[mifo2035]

Mac mini server mid 2011
was working fine until the patch forced me to reboot.

I had the same issue on my MacMini Server (Mid 2011) used the information from an earlier post in this thread

//quote
Here @ThaRippa has fixed the issue with an almost identical wifi card as yours: fix Bluetooth 4.0 on Mojave

You have to take IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HighSierra and then replacing into your Mojave /System/Library/Extensions/ , after you have to launch Terminal and fix permissions:

sudo chmod -r 755 /S*/L*/E*
sudo chown -r 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot
//unquote

I had problems with chmod/chown in terminal but fixed permissions in Finder

 

[jackluke]

Tried creating a new admin user under safe mode and.. nope nope nope, opening any 32 bit app just ends up with the icon keep bouncing

This is a really weird problem. I tried resetting the file permissions too, no luck.

And there is nothing whatsoever in Console.app log about this issue.

What could it be? I have a feeling this is due the unsupported machine. Maybe one of the kexts?

Agree weird problem, however any time I open a 32bit app from Mojave I get a warning of incompatibility "app is not optimized", and that link me here: https://support.apple.com/en-us/HT208436

Yes, most probably is one (or more) of your extra kexts, boot in safe move and check the extensions loaded from System_Information--Software--Extensions and watch the "Loaded" tab set in order by "Yes", and check if you have also third party apps or usb dongles that installed third-party framework.
[doublepost=1538773865][/doublepost]

I had the same issue on my MacMini Server (Mid 2011) used the information from an earlier post in this thread

//quote
Here @ThaRippa has fixed the issue with an almost identical wifi card as yours: fix Bluetooth 4.0 on Mojave

You have to take IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HighSierra and then replacing into your Mojave /System/Library/Extensions/ , after you have to launch Terminal and fix permissions:

sudo chmod -r 755 /S*/L*/E*
sudo chown -r 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot
//unquote

I had problems with chmod/chown in terminal but fixed permissions in Finder

Yes my fault, it was the auto-correction or my wrong typing due to hurry, for chown/chmod you have to use the capital letter: -R not -r

edit:
No, I am not so wrong using lowercase "-r" infact I have tested right now from single user mode and the "Recursively" command works perfectly from there in copying/deleting/moving folders, so capital Letter "-R" is only needed for the multi-user logged-in Terminal. Anyway to avoid issues use the capital letter.

 

[Ludacrisvp]

I have also tried loading kexts through and sse4.2 emulator

If there is a SSE4.2 emulation available, would this allow for us to not have to remove the com.apple.telemetry.plugin that seems to cause panic from CPU hang during boot? While I'm not expecting to be fast enough to handle video i think it may help us in other ways avoid panics from various other unknown system level events that require SSE4.2 that we aren't aware of.

 

[vix2000]

I’m actually through to the installation now, but first 2 attempts loaded for about 30 minutes then I get the grey no entry sign. Just on third attempt with fingers crossed. Nightmare!!! Right through to installation complete please restart your computer - restarts to grey no entry sign aaaarrrrgggghhh

 

[jackluke]

If there is a SSE4.2 emulation available, would this allow for us to not have to remove the com.apple.telemetry.plugin that seems to cause panic from CPU hang during boot? While I'm not expecting to be fast enough to handle video i think it may help us in other ways avoid panics from various other unknown system level events that require SSE4.2 that we aren't aware of.

You know I've made many experiments on that a couple of months ago, I can assure that among 46 UserEventPlugins the only mandatory required to boot Mojave both from an unsupported and supported mac is only this one: com.apple.remoted.plugin

The others 45 are all trash-able, however you can use "com.apple.telemetry.plugin" from HighSierra 10.13.6 to avoid SSE4.2 uncovered behaviors.

 

[dosdude1]

I’m actually through to the installation now, but first 2 attempts loaded for about 30 minutes then I get the grey no entry sign. Just on third attempt with fingers crossed. Nightmare!!! Right through to installation complete please restart your computer - restarts to grey no entry sign aaaarrrrgggghhh

Did you run the post-install patches as instructed...?

 

[thegurgz]

To those who use Mojave on APFS file system, I have managed to "fix" the APFS Recovery Volume to make it bootable with CMD+R and mainly with USB input devices responsive, working wifi and everything else, just follow next steps, boot from a Mojave APFS Volume, launch Terminal and type:

diskutil apfs list
{locate your "APFS Recovery Volume" diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}

diskutil mount diskXs3
open /Volumes/Recovery

landing on Finder, double tap on the "random-numbers-letters" folder, once inside rename these files:

prelinkedkernel into prelinkedkernelbackup
immutablekernel into immutablekernelbackup
PlatformSupport.plist into PlatformSupportbackup

Don't close Finder yet, once you renamed those 3 files, press CMD+N, then from this new Finder Window press CMD+SHIFT+G (or use "Go to Folder"): /System/Library/PrelinkedKernels/

while inside this path copy the file prelinkedkernel into the previous Finder Window, exactly were you renamed those 3 files, lastly rename this fresh copied file from prelinkedkernel to immutablekernel

Now you have a working APFS Recovery Volume.

Tried it and it worked like a charm. I don't really see the need for recovery partitions since you can't resintall the OS on an unsupported mac from a recovery partition, and the patched USB stick can do everything a recovery partition can do and install the OS. But thank you for creating this in case I don't have the USB around!

On APFS scheme the "APFS Recovery Volume" is always on the 3rd (hidden) partition.

I would not say "always". In my APFS container, the preboot was the 3rd partition, and the recovery partition was in 4. Not sure if I am just a special case, just an exception to your rule.

[doublepost=1538778294][/doublepost]Has anyone figured out how to install the Mojave 14.0.1 Beta 1 or 2?

 

[SpinThis!]

Hello,

I installed Mojave (macOS 10.14 (18A391)) successfully on my Mac Pro 3,1 with Dosdude1 patcher tool.
....
The only thing that doesn't work right now is the Brio Pro Webcam from Logitech. That webcam work well on the same mac pro with high sierra and also on a mac mini 2014 running Mojave.
...
Is there anyone who has tested this webcam on a Mac Pro 2008?

Yeh I have a 3,1 with a similar setup. Try the iSight patch... although it's intended for older iSight cameras, the patch got the c920 working again for me.

 

[vix2000]

Did you run the post-install patches as instructed...?

Note to self - read things properly!!! Would have saved myself hours. Thank you.

 

[BigSmileMan]

@dosdude1 Have installed Mojave on my MacBook Air 4.2 (mid 2011) by a Mojave Patcher tool 1.2.2 a couple days ago with default patcher values for my MBA rig. Used my AirPods and another stuff. All works like a charm before patch updater installed first bluetooth patch (think it was version 0).
Tried to revert IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from patched USB drive with kext rebuild but no luck. Now patcher updated Bluetooth patch to version 2. Have same problem... What should I do now to have working bluetooth?
Waiting for next patch update and thank you for all your hard work!

My list of patches in attach

 

[jackluke]

Tried it and it worked like a charm. I don't really see the need for recovery partitions since you can't resintall the OS on an unsupported mac from a recovery partition, and the patched USB stick can do everything a recovery partition can do and install the OS. But thank you for creating this in case I don't have the USB around!

I would not say "always". In my APFS container, the preboot was the 3rd partition, and the recovery partition was in 4. Not sure if I am just a special case, just an exception to your rule.
View attachment 792429
[doublepost=1538778294][/doublepost]Has anyone figured out how to install the Mojave 14.0.1 Beta 1 or 2?

I know probably you can't reinstall (or maybe yes since PlatformSupport.plist is renamed, but not advisable doing on unsupported mac), however it's a less than 600 MB partition, just for few things like Terminal, DiskUtility, TimeMachine, browsing Safari, I would say for the minimum wage is fine.

I guess that APFS Container Scheme in the 99% of cases is: Mojave diskXs1, Preboot diskXs2, Recovery diskXs3, VM diskXs4

1% is your case.

Anyway, thanks for your feedback.

 

[ExplorerExplorer]

After the latest patch I no longer have bluetooth. MacBook Pro 8.1 (Early 2011)

 

[VictoryHighway]

I have a MacPro 3,1 (Early 2008) and I have installed a copy of Mojave on a USB flash drive for testing. I've noticed that while booting or running Mojave, my computer's fans are always running full-tilt. When I reboot into High Sierra, the fan speed is based on CPU load. Any idea how to fix this?

 

[Ghasan Abusal]

@dosdude1 thanks for your effort you did a great job . will we have a fix for graphics anomalies soon ? At least a fix for the corners and borders issues in the dark mode . everything else just works fine.

 

[ASentientBot]

If there is a SSE4.2 emulation available, would this allow for us to not have to remove the com.apple.telemetry.plugin that seems to cause panic from CPU hang during boot? While I'm not expecting to be fast enough to handle video i think it may help us in other ways avoid panics from various other unknown system level events that require SSE4.2 that we aren't aware of.

com.apple.telemetry.plugin does not contain SSE4.2 instructions.

 

[Starplayr]

com.apple.telemetry.plugin does not contain SSE4.2 instructions.

Does anyone know what the Telemetry plugin is used for? What data is Apple collecting with it?