macOS 10.14 Mojave on Unsupported Macs Thread

[0403979]

Of course, I wanted to say in general I prefer doing these stuffs manually instead of using Shell scripts, or at least understand what it does in deep.

And if someone doesn't want any alterations on CoreBrightness could use also f.lux app

I haven't written I have created the patch, only I have patched manually that's all.

And I bet this file I uploaded will work on any Mojave release till to GM, hoping that someone can deny.
[doublepost=1531303270][/doublepost][doublepost=1531303218][/doublepost]

You are (as me) on Mojave beta 2 (18A314h), that's why the feature Dynamic Wallpaper based on local sunrise and sunset times doesn't work, someone reports that starting form Mojave beta 3 is working, while the patch you linked doesn't bring the real feature, it's simply "Change picture" every chosen hours/minutes with a chosen folder path that can be obtained since Mac OSX Leopard, the effect obtained visually is almost the same.

In beta 3 it works with dark mode but I don’t know the details.

 

[jackluke]

In beta 3 it works with dark mode but I don’t know the details.

I could download beta 3 too from a supported mac, but I don't need it, to me beta 2 is enough stable. Maybe I'll update on beta 5 if simnifically changed are made.

Dynamic Wallpaper based on current sunset/sunrise timezone, maybe requires also in System Pref / Security & Privacy the Location Services Enabled, but honestly from an unsupported mac with Mojave installed I would be a little worried of being constantly 24/7 geolocated by apple.

 

[leoborges]

Installed successfully on macbookpro 8,3 (MacBook Pro 17" late 2011). First I used a torrent image to create install disk and got errors during the boot stage. Then I used dosdude1's tool to download the installation and everything went fine. Then I patched the kexts using macbookpro8,3 setting from dropdown and checked legacy video support. Then fixed permissions and restarted. Thanks for the patch!

 

[a.freemason]

On the mac book pro 13 (mid 2009) everything OK .... good graphics acceleration.
thank you .......

I do not know it seems to me that there is some variation on the background colors ..... at the "normal" screen level, in black having no references I think they are so .......

 

[skyfly555]

Hi, guys. Following your evolution through these 88 pages

I wonder, when you say:
"

• iMac Early-2008 to Late-2011 (No acceleration on machines with ATI/AMD GPUs)

"
If QE/CI can be achieved using the iGPU of the 1st gen Intel processors, in my case, I have an iMac 11,1 with an i5-580.
Thank you very much.

 

[Czo]

Hi, guys. Following your evolution through these 88 pages

I wonder, when you say:
"

• iMac Early-2008 to Late-2011 (No acceleration on machines with ATI/AMD GPUs)

"
If QE/CI can be achieved using the iGPU of the 1st gen Intel processors, in my case, I have an iMac 11,1 with an i5-580.
Thank you very much.

On iMacs, the LCD and the displayports on the back are hardwired to the deditaced GPU. Without the GPU, the iMacs can't output pictures.

But, MacVidCards working on a EFI compatible, MXM upgrade card.

 

[jackluke]

This is as far as I can get, any suggestions? The drive has been erased as APFS & connected via firewire, I did end up with a "BaseSystem.dmg"? Attached is a screenshot of error from the patch. The Mojave install is 5.63GB, v.14.0.12.

USB w/APFS started to install and STB, InstallESD not mounted. Did try with HFS+ with success, install to USB, long process, reboot to USB installer, even longer,(40+minutes) hangs at Apple logo progress bar complete, fans at hurricane speed, manual power down, let it cool and try again.

For whatever reason I can't get by Apple logo, the progress bar is complete, no panics, SUM I can run fsck- fy and comes back "the volume Untitled appears to be ok", /sbin/fsck -fy same results, no "File system was modified" type reboot, Apple logo and fans at full speed again. What's odd is that progress bar goes pretty fast until last 1/4 and slows to a crawl, progress bar complete, waited 30 minutes+ & manual power off as iMac is overheating. I booted into HS and got a warning that Power Heatsink & CPU Core 1 & 2 are overheating. ??

I don't understand you want to install Mojave on an external firewire hard disk?

Anyway, you first should create apart a Mojave usb installer with the patcher and be able to reach the GUI screen.
The external firewire hdd is the last of your thoughts.

First of all be sure that your External USB drive, either a 16 gb usb stick is not worned out, broken or damaged, I would advise to avoid cheap USB drives, instead maybe take a sealed USB 3.0 drive with a good balance of read/write speeds respectively of 80Mbps and 20Mbps (or higher).

After you are sure using an external usb flash drive in good health condition, try to download the most recent revision of Mojave Patcher and re-create the installer, then following online guides of apple according to your Mac type:

- Do a SMC reset
- Do a twice PRAM reset

I read that you are on an iMac so:

SMC RESET

• Shut down the computer.
• Unplug the computer's power cord from both the wall and computer.
• Wait 15 seconds.
• Attach the computers power cable.
• Wait another 5 seconds and press the power button to turn on the computer.

PRAM RESET

• Shut down the computer.
• Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously
• Turn on the computer.
• Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
• You encounter a black screen hearing a first chime sound then during first restart keep holding those keys.
  
• Hold the keys down until the computer restarts and you hear the startup sound for the second time.
• Release the keys.

After done try to boot the Mojave USB installer.

If following these tips you still fail, then you have a totally unsupported incompatible Video Card with Mojave installer or in rare cases it's an hardware failure.

 

[skyfly555]

On iMacs, the LCD and the displayports on the back are hardwired to the deditaced GPU. Without the GPU, the iMacs can't output pictures.

But, MacVidCards working on a EFI compatible, MXM upgrade card.

Thank you, @Czo, I didn't know that.

 

[sseg]

On the mac book pro 13 (mid 2009) everything OK .... good graphics acceleration.
thank you .......

I do not know it seems to me that there is some variation on the background colors ..... at the "normal" screen level, in black having no references I think they are so .......

How to enable graphics acceleration?

 

[a.freemason]

How to enable graphics acceleration?

in the patch 01b5 @dosdude1 has inserted the patch for the video card, it works quite well ......

 

[antibolo]

Congrats on your progress guys!

But I'm noticing that the Mac mini Mid-2010 (4,1) is still missing from the list? It has a GeForce 320M GPU. Shouldn't that work since there are now older nVidia GPUs working? Or is there another reason than the GPU?

 

[dosdude1]

No, this is not necessary. It's only required, if you don't boot with the -no_compat_check kernel flag.

The latest version of the post-install tool will add -no_compat_check to the boot.plist in the preboot volume as well when patching an APFS volume, so there is nothing to worry about there.

 

[0403979]

The latest version of the post-install tool will add -no_compat_check to the boot.plist in the preboot volume as well when patching an APFS volume, so there is nothing to worry about there.

Beta 5 is the latest?

 

[dosdude1]

Also, please do NOT use any current Night Shift patches on Mojave (unless it's a Core Brightness binary modified manually from Mojave). I am working on a dynamic binary patcher for this, preventing any chance of using an old binary. In the past, using old CoreBrightness binaries have caused the system to stop booting entirely.
[doublepost=1531322641][/doublepost]

Beta 5 is the latest?

Yes.
[doublepost=1531322720][/doublepost]

Congrats on your progress guys!

But I'm noticing that the Mac mini Mid-2010 (4,1) is still missing from the list? It has a GeForce 320M GPU. Shouldn't that work since there are now older nVidia GPUs working? Or is there another reason than the GPU?

Yes, it's compatible too, seems I just forgot to add it to the list.

 

[0403979]

Yes.

I used beta 5 but it still wouldn’t boot on my APFS volume. I replaced /Volumes/Preboot/System/Library/CoreServices/PlatformSupport.plist and then it booted just fine.

Some more info on this:
The PlatformSupport patch in the patcher already replaces the file on the main drive so it should just replace it on the Preboot drive as well for APFS Volumes.
[doublepost=1531323514][/doublepost]

No problem. I'm not writing this again though

Patch the installer
1. Get a copy of the install app and open Contents/SharedSupport/InstallESD.dmg
2. Copy the folder Packages somewhere you can edit
3. cd to the folder and pkgutil --expand OSInstall.mpkg Expanded
4. Open the folder Expanded and open Distribution in a text editor
5. Find the function installationCheck() and put return true; at the very beginning
6. Remove the text installsOS=true from the same file
7. pkgutil --flatten Expanded Patched.mpkg
You will now have an install file "Patched.mpkg" that you can double-click and install to a HFS+ partition.

Patch the installed system to boot
1. On the partition, copy boot.efi from /usr/standalone/i386/ to /System/Library/CoreServices
2. Open /Library/Preferences/SystemConfiguration/com.apple.Boot.plist in a text editor
3. Make Kernel Flags as <string>-v -no_compat_check keepsyms=1</string>
This will make the disk bootable, bypass the prohibitory symbol (\) and show symbols in kernel panic logs (If it panics, let it reboot and pick your High Sierra partition; it should automatically show the log in "your computer was restarted because of a problem" dialog once it boots.)

Fix the kernel panic on Penryn systems
Replace from High Sierra:
/System/Library/UserEventPlugins/com.apple.telemetry.plugin

Patch USB
Replace from High Sierra:
/System/Library/Extensions/IOUSBHostFamily.kext

Patch audio
Replace from High Sierra:
/System/Library/Extensions/AppleHDA.kext

Recognize the Tesla GPU
Copy from High Sierra:
NVDANV50HalTesla.kext
NVDAResmanTesla.kext
IONDRVSupport.kext
IOGraphicsFamily.kext
This allows changing the brightness and shows the correct display in About This Mac

Enable the framebuffer
Copy from High Sierra:
GeForceTesla.kext
GeForceGA.kext
Partial acceleration.

Enable full acceleration
Copy from High Sierra
GeForceTeslaGLDriver.bundle
GeForceTeslaVADriver.bundle
Right now, this causes a kernel panic on login. Edit: Hack-ish but functional workaround here.

Fix kext permissions
sudo chmod -R 755 /Volumes/Mojave/System/Library/Extensions
sudo chown -R root /Volumes/Mojave/System/Library/Extensions
Replacing "Mojave" with the name of your partition. This'll allow the system to automatically rebuild the prelinkedkernel when you boot from the Mojave volume (it'll reboot after doing so).


That took longer to write than I expected, haha. Hope that helps. It's good to have a consolidated list of patches so far anyways, I've been meaning to make a post like this for a bit.

Edit: Does someone want to link this on the wikipost or something? Maybe decrease the amount of redundant questions so we can focus on moving forward

Edit 2: This is only for MacBook6,1 and MacBook7,1 systems.

Better to change installsOS=true to installsOS=flase instead of deleting it.

 

[swamprock]

On the mac book pro 13 (mid 2009) everything OK .... good graphics acceleration.
thank you .......

I do not know it seems to me that there is some variation on the background colors ..... at the "normal" screen level, in black having no references I think they are so .......

Nice! I'll wait for the final release to install this on my machine (same as yours), but it's good to see that it's now running on these old MBPs

 

[jackluke]

Also, please do NOT use any current Night Shift patches on Mojave (unless it's a Core Brightness binary modified manually from Mojave). I am working on a dynamic binary patcher for this, preventing any chance of using an old binary. In the past, using old CoreBrightness binaries have caused the system to stop booting entirely.

I before attached one binary manually modified following pikeralpha's blog tips.
I am confident it could work on any Mojave release until the GM at least.

 

[redheeler]

On the mac book pro 13 (mid 2009) everything OK .... good graphics acceleration.
thank you .......

I do not know it seems to me that there is some variation on the background colors ..... at the "normal" screen level, in black having no references I think they are so .......

Nice to see Mojave is now stable on Core 2 Duo Macs. Tempted to try it on my MacBook (Mid 2010) using @ASentientBot's instructions and modified binary.

 

[0403979]

Nice to see Mojave is now stable on Core 2 Duo Macs. Tempted to try it on my MacBook (Mid 2010) using @ASentientBot's instructions and modified binary.

Use the patcher.

 

[dosdude1]

Nice to see Mojave is now stable on Core 2 Duo Macs. Tempted to try it on my MacBook (Mid 2010) using @ASentientBot's instructions and modified binary.

It should work just fine with the patcher as well.

 

[redheeler]

Use the patcher.

Is there any particular reason to use the patch tool instead of doing the patch myself? I didn't use the patch tool to install Mojave on my 2011 MacBook Pro, and hence I have a much better understanding of what needs to be done if something goes wrong with the install.

 

[0403979]

I used beta 5 but it still wouldn’t boot on my APFS volume. I replaced /Volumes/Preboot/System/Library/CoreServices/PlatformSupport.plist and then it booted just fine.

@dosdude1 Did you see that message?
[doublepost=1531325034][/doublepost]

Is there any particular reason to use the patch tool instead of doing the patch myself? I didn't need to use the patch tool to install Mojave on my 2011 MacBook Pro, and hence I have a much better understanding of what needs to be done if something goes wrong with the install.

Using the patcher tool is easier. That’s it.

 

[dosdude1]

Is there any particular reason to use the patch tool instead of doing the patch myself? I didn't use the patch tool to install Mojave on my 2011 MacBook Pro, and hence I have a much better understanding of what needs to be done if something goes wrong with the install.

I mean you can if you want... The tool just automates the whole process.
[doublepost=1531325304][/doublepost]

@dosdude1 Did you see that message?
[doublepost=1531325034][/doublepost]

Using the patcher tool is easier. That’s it.

Yes, I did. I'll look into it, as I definitely implemented patching Preboot. Not sure why it didn't work on your machine.

 

[0403979]

Yes, I did. I'll look into it, as I definitely implemented patching Preboot. Not sure why it didn't work on your machine.

Okay. Thank you. I had this issue on beta 4 as well which was why I was trying so many times to fix it yesterday.

 

[jackluke]

I want to share an interesting experiment, referred especially to Nvidia 320M owners.

When I observed the IOAccelerator framework behavior, I kept a backup of the one present in Mojave beta 1.

Comparing them I noticed that have mainly different sizes:

IOAccelerator unix exe from Mojave Beta 1 = 70 KB
IOAccelerator unix exe from Mojave Beta 2 = 158 KB

Well I have tried to replace and I noticed an overall better experience, no artifacts, no minimum glitches, and major reactivity in windows, folders and everything else.

Moreover a better characters contrast and transparency effects, bright colors, FaceTime is flowing better.

Sometimes I got some Finder folders autoclose, instead using the previous IOAccelerator from Mojave Beta 1, Finder is more quick and fluid and above all no more unwanted autoclosing windows.

I would suggest to try it, making a backup of your previous (more recent) one.


Here are the steps:

Locate your Mojave path: /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/
- Replace inside this subfolder the IOAccelerator unix exe with the one I have attached.

Trust me you will notice significative improvements, your C2D behaves like an Intel i5 Dual Core. Try to believe.