macOS 10.14 Mojave on Unsupported Macs Thread

[16v]

Yes, you don't need rom patcher, and I guess your SMC is ok, so you can install or convert your Mojave in APFS.

There are also standalone efi bootrom update for example: https://support.apple.com/kb/DL1499
but you don't need, you already have the latest update.

Here is the official database: https://support.apple.com/en-us/HT201518

Yes, this is what i used to compare.
And like i said i have the rom installed from early 2011 models, like you can see they differ in the name...

 

[jackluke]

Yes, this is what i used to compare.
And like i said i have the rom installed from early 2011 models, like you can see they differ in the name...

I think it's ok, then boot again from the USB Installer, open DiskUtility, highlight your drive and click the top-menu "Edit" and select "Convert to APFS...", when done, reboot and you will have an APFS drive w/o efforts.

 

[StrangeLoopy]

With deep thanks to dosdude1 and others, I was able to keep my early-2008 MacBook Pro running through High Sierra. I decided that 10 years was enough, and jumped ship to a new MBP, migrating successfully using the Time Machine from the old unit.

All is well, except I occasionally get Patch Updater popping up to say that "New patch updates are available for this model. (Night Shift Patch)", which I clearly don't need anymore. How do I stop this? Is there a way to remove Night Shift Patch so it isn't checked? Or can I just uninstall/delete Patch Updater from Applications/Utilities? (it's only for the "unsupported Macs" feature, right?)

Thanks for any help you can offer!

 

[viettanium]

i have a Mac mini 2011 with modded Fusion Drive, anyone confirm if this work?

 

[psu7276]

You probably need to re-apply Mojave Patcher.app (Post-Install) related to USB?

Thanks for the follow-up. I know they were checked on the first attempt but did as you recommended and all worked on trial drive. Also successfully installed on internal iMac drive.

Also, what is the purpose of the 14.3 supplemental that has been mentioned so many times? Is it necessary if computer is working fine?

 

[MTBnBeer]

What is the purpose of the 14.3 supplemental that has been mentioned so many times? Is it necessary if computer is working fine?

https://support.apple.com/en-us/HT209521

 

[Tucker28]

I have used this tool since it was first made for Sierra. I have never had a problem with it... until now. Installing Mojave on another Mac, and using the Mac that I already have it installed on to create the USB drive. (Old drive was mistakenly left behind when I moved.)

I have used 2 different USB drives, and they both do the same thing. They both give me failed to mount errors 75% of the time. When it doesn't give me the error and goes about its business, it instantly gets to ~5% done on its progress bar, but then it sits there and does nothing else. I can leave it all night and it'll still be at the same place in the morning.

I have also used two separate images of Mojave. Both the new 10.14.3 as well as the old 10.14.1 I still have on my archive drive. It does the same thing with both of them. I don't have a copy of the original 10.14.0 Mojave image or I would try to use an older version of the tool. I have also verified the download with the SHA1 hash and they match.

At this point, I'm lost. What can I try next?

 

[psu7276]

https://support.apple.com/en-us/HT209521

Thanks. I used the system download from the patcher and it appears that I already have this version.

 

[cecil444]

Has anyone tested the speed differences of running Mojave on a third-party SSD formatted HFS+ vs. APFS? I'm wondering which is faster, and if any speed differences are noticeable. I have a MacBook5,1 (aluminum unibody) running Mojave on a Crucial SSD formatted for HFS+, but am wondering if it's worth it to make the switch to APFS. Does anyone have any feedback or recommendation on this? Thanks

 

[Rappo]

Has anyone had problems with running Final Cut Pro (10.4.5) after the Mojave upgrade. I keep getting the "Graphics configuration not supported" error even though my graphics card is listed as being support.
Had no problems previously.
Have tried all the "fixes" that others have listed.
Any ideas?

 

[flyinmac]

One more success story. I finally decided to update to Mojave on my iMac (the one in my signature below).

Early 2009 20-inch iMac 9,1 w/ 8 GB of RAM. Otherwise, factory configuration.

I had previously been running it on the latest High Sierra version. And hadn’t had any problems at all. But this system is running my whole house, multi-room / multi-television entertainment system. The whole house’s sound system and theater system is dependent on its library (stored on an external drive).

So naturally, I decided to wait a bit before jumping into the Mojave update.

I downloaded the latest Mojave Patcher tool from Dosdude’s website. Used it to download the latest 10.14.3 installer (which included the latest security updates - I checked).

I then created the USB Mojave installation drive and booted the iMac and started the installation.

Everything went smooth. And my iSight camera works. I used the default iMac 9,1 scripts in the post-install routine. And added the recovery partition option and rebuild scripts options. And everything went smooth on the first try.

**Note: I did a full system backup of High Sierra prior to the update. Which I recommend everyone should do prior to any major changes (and on a regular basis if your data is important).

Great job on the tools Dosdude (and team of contributors). Appreciate the efforts and time invested to produce the tools.

Just dropping the note for anybody who might also be running an iMac 9,1 Early 2009 system. It worked fine on mine.

 

[avz]

I have used this tool since it was first made for Sierra. I have never had a problem with it... until now. Installing Mojave on another Mac, and using the Mac that I already have it installed on to create the USB drive. (Old drive was mistakenly left behind when I moved.)

I have used 2 different USB drives, and they both do the same thing. They both give me failed to mount errors 75% of the time. When it doesn't give me the error and goes about its business, it instantly gets to ~5% done on its progress bar, but then it sits there and does nothing else. I can leave it all night and it'll still be at the same place in the morning.

I have also used two separate images of Mojave. Both the new 10.14.3 as well as the old 10.14.1 I still have on my archive drive. It does the same thing with both of them. I don't have a copy of the original 10.14.0 Mojave image or I would try to use an older version of the tool. I have also verified the download with the SHA1 hash and they match.

At this point, I'm lost. What can I try next?

Try using different Mac OS to create USB drive(I used Snow Leopard on my external HDD). Mojave(atleast current version) does not seem to like creating patched USB drives.

 

[16v]

Has anyone tested the speed differences of running Mojave on a third-party SSD formatted HFS+ vs. APFS? I'm wondering which is faster, and if any speed differences are noticeable. I have a MacBook5,1 (aluminum unibody) running Mojave on a Crucial SSD formatted for HFS+, but am wondering if it's worth it to make the switch to APFS. Does anyone have any feedback or recommendation on this? Thanks

Not this but:

I have mbp 5.4 and my crucial ssd always had linkspeed 1.5 instead of 3.
Only when resetting pram it was has 3. But on next boot it had 1.5 again.

Apfs, softwars apfs patch.

I used the apfs rom patcher a few days ago, now it has always 3!

 

[avz]

Has anyone tested the speed differences of running Mojave on a third-party SSD formatted HFS+ vs. APFS? I'm wondering which is faster, and if any speed differences are noticeable. I have a MacBook5,1 (aluminum unibody) running Mojave on a Crucial SSD formatted for HFS+, but am wondering if it's worth it to make the switch to APFS. Does anyone have any feedback or recommendation on this? Thanks

My MacBook5,1 is running Mojave on a Kingston SSD formated for APFS. I found that it is working great for a light usage with only 2GB of RAM. Will you be able to test your HFS+ install with only 2GB of RAM?

 

[taranee]

With deep thanks to dosdude1 and others, I was able to keep my early-2008 MacBook Pro running through High Sierra. I decided that 10 years was enough, and jumped ship to a new MBP, migrating successfully using the Time Machine from the old unit.

All is well, except I occasionally get Patch Updater popping up to say that "New patch updates are available for this model. (Night Shift Patch)", which I clearly don't need anymore. How do I stop this? Is there a way to remove Night Shift Patch so it isn't checked? Or can I just uninstall/delete Patch Updater from Applications/Utilities? (it's only for the "unsupported Macs" feature, right?)

Thanks for any help you can offer!

if your new mac supports the 10,14 then you can just remove the patch updater and every thing related yes they are only for the unsupported macs. supported macs don't needs them

 

[16v]

My dvd is faulty. Mbp late 2011 13".
Can i use any 9.5mm slot in drive ir has it to be the same?
Thx

 

[MTBnBeer]

Thanks. I used the system download from the patcher and it appears that I already have this version.

You can easily verify the macOS Mojave 10.14.3 Supplemental Update has been installed from:

About This Mac
Software Update

You should see this:

... if the macOS Mojave 10.14.3 Supplemental Update IS installed. If not it will prompt you to install it which should NOT require re-running macOS Mojave Patcher.

 

[K two]

Has anyone tested the speed differences of running Mojave on a third-party SSD formatted HFS+ vs. APFS? I'm wondering which is faster, and if any speed differences are noticeable. I have a MacBook5,1 (aluminum unibody) running Mojave on a Crucial SSD formatted for HFS+, but am wondering if it's worth it to make the switch to APFS. Does anyone have any feedback or recommendation on this? Thanks

• I have had both Mojave HFS+ and APFS on the SSD in this Macbook5,1. The only real difference is CONVENIENCE. The Macbook can be kept up to date easily with the Software Update CP and Lockrattler without slogging around in the Terminal.

Functionally, performance is comparable for our uses. Recommend APFS without qualifications.

 

[AlexyFoxy]

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.

Hello,
I tried it and it not work for me, I wonder if you can help
I am on matchbook pro late 2011 13'

 

[jackluke]

Hello,
I tried it and it not work for me, I wonder if you can help
I am on matchbook pro late 2011 13'

Yes, you need to modify only the com.apple.Boot.plist inside your Recovery to pass the prohibitory logo, you can follow this other guide I did: APFS Recovery fix part 2
if you don't succeed report here the result from your Mojave Terminal: diskutil apfs list

 

[AlexyFoxy]

Yes, you need to modify only the com.apple.Boot.plist inside your Recovery to pass the prohibitory logo, you can follow this other guide I did: APFS Recovery fix part 2
if you don't succeed report here the result from your Mojave Terminal: diskutil apfs list

Thank for your concern, sadly it did not work, here is the screenshot:

 

[iRock1]

Yes, clean install is definitely the way to go in order to keep things simple and straightforward. I never bothered with an upgrade myself but it should work too as there is nothing against it in the first page of the thread. If you carefully follow the instructions you'll be running Mojave in no time.

The reason I asked is because the fact that your MacBook runs faster now may be due to you having deleted everything, instead of just upgrading OS.

 

[avz]

The reason I asked is because the fact that your MacBook runs faster now may be due to you having deleted everything, instead of just upgrading OS.

Very true. I relatively recently upgraded to SSD, so most of my installs are quite fresh. Maybe that is why I am doing great with only 2GB of RAM.

 

[Project Alice]

Is there anyway I can install OS updates from the pkg files? Back in 10.12 Sierra I was always able to do this. I ask because I am unable to install any updates with software update. I have been unable to do it ever since 10.13.4, on 4 different macs (Yes, failed updates since 10.13.4). I either get a hang on installing software update, or just installation failed. It always seems to work okay after, but your guess is as good as mine if the system was actually updated.

I would rather do this, but I get greeted with this message instead.

It seems the Mac OS install apps are not updated with these small security updates, like HS 2019-001, or the mojave supplemental, so reinstalling using the USB patcher still leaves me with needing to install updates, that always fail.

 

[jackluke]

Thank for your concern, sadly it did not work, here is the screenshot:
View attachment 822325

open Mojave Terminal and type:

diskutil mount disk2s3
open /Volumes/Recovery/5BFE9E7C-6366-4177-BB23-1DDB94605A12

replace inside this path from Finder the file I attached and modified for your partition scheme, reboot hold CMD+R and check.