macOS 10.14 Mojave on Unsupported Macs Thread

[kautame]

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

Thank you, I've launched it, but it opens a window that says "Error. Could not find an EFI System Partitions on your machine". And in the main window, under "Available EFI System Partitions" there is nothing.

There's definitely something strange here. My disk is an APFS formatted SSD (from when I installed High Sierra with your Patch), and i booted from the EFI partition (it's the ONLY partition I have).

 

[dosdude1]

Thank you, I've launched it, but it opens a window that says "Error. Could not find an EFI System Partitions on your machine". And in the main window, under "Available EFI System Partitions" there is nothing.

There's definitely something strange here. My disk is an APFS formatted SSD (from when I installed High Sierra with your Patch), and i booted from the EFI partition (it's the ONLY partition I have).

Try this version.

 

[DaniloGeekDude]

Successfully Upgraded from 10.14.1 Final to 10.14.2 Beta 1 on my Mojave unsupported MBP5,3 (core 2 duo)

OTA (System Preferences | Software Update) and used mac OS Post Install from @dosdude1's Mojave Patcher app v1.2.3.



Special Thanks to @dosdude1 and the other awesome fellows credited on the OP. Thanks as well to @TimothyR734 for his always useful/relevant info and @pkouame for his hybrid patch.

 

[joelw135]

When I did my OTA update on the MacBook Pro 7,1 I patched and forced cache rebuild on first boot and it worked perfectly the first time. So next time I will try this with the Mac Mini 3,1.
[doublepost=1541272412][/doublepost]Question regarding Time Machine and APFS. I have SSD's with APFS file system, do I have to format the Time Machine SSD to APFS or it doesn't matter?

 

[pkouame]

Successfully Upgraded from 10.14.1 Final to 10.14.2 Beta 1 on my Mojave unsupported MBP5,3 (core 2 duo)

OTA (System Preferences | Software Update) and used mac OS Post Install from @dosdude1's Mojave Patcher app v1.2.3.

View attachment 801000

Special Thanks to @dosdude1 and the other awesome fellows credited on the OP. Thanks as well to @TimothyR734 for his always useful/relevant info and @pkouame for his hybrid patch.

Good to know that OTA system updates are working again. Thanks.

 

[AphoticD]

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.

After running these commands, the APFS volume now does not appear in the multi-boot selector. The only bootable volume is the USB installer.

I'm now thinking that perhaps I should reinstall High Sierra onto the SSD to see if this Mac can actually boot from a supported OS on an APFS volume - I previously had HS installed on a HFS+ HDD.

 

[jackluke]

After running these commands, the APFS volume now does not appear in the multi-boot selector. The only bootable volume is the USB installer.

I'm now thinking that perhaps I should reinstall High Sierra onto the SSD to see if this Mac can actually boot from a supported OS on an APFS volume - I previously had HS installed on a HFS+ HDD.

Yes installing HighSierra APFS natively would be a regular procedure, however I read that you had created manually the VM partition (required for the integrity of APFS Scheme/Container) perhaps that's why your APFS scheme doesn't work properly, the VM partition should be created naturally by APFS (format/conversion) in a clean way and automatically populated by the system.

Anyway before re-install HighSierra, try this last attempt, boot USB Installer open DiskUtility and do a couple of First Aid on your Mojave APFS Volume, then open Terminal and type:

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

diskutil apfs updatePreboot diskXs1

reboot and unplug the USB Installer.

Similar steps but without the bless command ("bless" seems almost deprecated on APFS) this time, and see what happens.

edit:
A couple of questions: During the Mojave Post-Install do you have used any APFS patch ? You should not use that.

And which kind of hard disk do you have inside? Spinning or SSD ? Some old spinning hard disks have compatibility issues with APFS file system that was introduced especially for the SSDs.

Infact by default apple on supported HighSierra Macs equipped with spinning disk, doesn't offer the chance to install it directly (or on-the-fly conversion) in APFS, but this must be done after manually by the user, forcing APFS conversion through Terminal commands.

 

[webg3]

View attachment 800967 View attachment 800968


View attachment 800967View attachment 800967



So Did I do it correctly?

apparently it is correct, I always first copy the file I want to replace to the same folder and then rename the main file with a bak or 10.14.1 at the end of the file name, example: AppKit.bak or AppKit_10.14.1 and then rename the file modified file (patched) to the original name, AppKit example.

If you have any problems, simply enter through the Recovery (USB Installer) and undo the changes.

It is best to always change the names and files by the terminal or keep it open, if you prefer to make the changes by graphical mode (with the system in full operation).

 

[gotcoding24]

Hi everyone,
I haven't been on this forum for a while, and am too lazy to read through the hundreds and thousands of posts.
Would anyone be able to help me with this problem?

Many thanks in advance!

 

[joelw135]

Hi everyone,
I haven't been on this forum for a while, and am too lazy to read through the hundreds and thousands of posts.
Would anyone be able to help me with this problem?

Many thanks in advance!

How is the SD drive or HD drive formatted, just use standard Mac format? Take the ' out of Mojave and try again. I had the problem, but if someone with greater knowledge please take over.

 

[LuisN]

When I did my OTA update on the MacBook Pro 7,1 I patched and forced cache rebuild on first boot and it worked perfectly the first time. So next time I will try this with the Mac Mini 3,1.
[doublepost=1541272412][/doublepost]Question regarding Time Machine and APFS. I have SSD's with APFS file system, do I have to format the Time Machine SSD to APFS or it doesn't matter?

DON'T. Time Machine only works with HFS

 

[joelw135]

DON'T. Time Machine only works with HFS

That is what I thought, but I have read conflicting articles. Some saying that if you have an SSD internal Mojave drive it is OK to format Time Machine as APFS. I will keep HFS, just to be sure, or unless I get better info.

 

[Skorpion24]

Both of you try this.

@jackluke @Skorpion24

Thanks I'll give it a try tomorrow, how do I apply that patch?

 

[dharnidhar]

Successfully Upgraded from 10.14.1 Final to 10.14.2 Beta 1 on my Mojave unsupported MBP5,3 (core 2 duo)

OTA (System Preferences | Software Update) and used mac OS Post Install from @dosdude1's Mojave Patcher app v1.2.3.

View attachment 801000

Special Thanks to @dosdude1 and the other awesome fellows credited on the OP. Thanks as well to @TimothyR734 for his always useful/relevant info and @pkouame for his hybrid patch.

Hi Danilo,

I am using the same patch version 1.2.3, but cannot upgrade tp beta 10.14.2 beta 1. Kindly let me know how you were able to get this patch. My mac is also enrolled in Apple Beta Software Program. Attached is the file if this helps.

Thank you very much for your help.

 

[Kevbasscat]

After Apple blacklisted my 9,1 iMac for not having metal and for having a c2d CPU, I realized they were just moving forward in technology. SO I purchased a refurb 2017 27" 5k iMac with a 2 TB fusion drive and a Radeon Pro 580. When I received it, it had High Sierra on it. Imagine my disappointment. IF they're going to blacklist me for not being able to run Mohave, then they better damn well ship they're products with Mohave on them. So I called Support. After 3 hours with a less than knowledgable support person, she told me she needed to file some B.S. report, and would not be back to me until late Tues afternoon, a full 4 days. So I went looking at the error logs. They say, Mohave cannot be loaded because of the spinner. So....wtf are they putting fusion drives into iMacs that will be stuck on HS for it's lifetime? I'm sure there is a workaround, but I EXPECT no issues when I buy a computer, not their B.S lame excuses, and putting me off. I ripped them two new ******s this morning, and demanded a another computer with Move installed by Apple, not me patching one! They couldn't even do that! I am about a ½" from going public with this, and proving to people Apple does not care about the mac any longer. They sure as he;; don't have any foresight nor did they even do their homework about these issues before releasing an OS that hobbles even macs that can receive this OS, and why the hell would they destroy the trust of their loyal customers, by their indifference and ignorance? I finally had enough today when I received the same uncaring response today from two other support people, one a senior advisor. So I demanded that I return this to the Apple store in Palm Desert, CA and they ship me a refurb with Mohave installed on it by Apple, as I acted in good faith, and they have not so far.

I have been faithful to Apple for over 20 years, all I ask is they be faithful as I have. I'm afraid you're all correct. Apple no longer cares for the mac. The real issue for me at least is, Apple had a way of making you fall in love with their products, because in my experience I had not one failure, in over 20 years. That is why Apple has such loyal customers, because we become emotionally attached to them. So it literally feels like they're intentionally hurting us. Yes, not everyone has this experience but many do, that's why the "Zealots." Don't argue with me, it's my experience, you haven't lived it.

Now, how do I put Mohave on this fusion machine? I'm just being smart and preparing for plan b. I'll dig up the error log and post it, but I've gotta a show to do, so in a few hours. I'm downloading 10.14.18. Is that the latest final?

 

[Sveto]

I have it working now, a bit of a concern as I have no idea how this happened. I am testing now for Malware. I have a network monitor here, and it will alert me of any unauthorized use. Thanks for the help.

You have not been hacked and there is no malware in your mac. Sometimes certain settings get burnt-in and won't allow to change them. Also in previous versions. For example I have on 2 different macs, with different OS versions the Sharing set and running, but if I try to disable it and enable it again the OS freezes and won't allow it. Even UNIX is not perfect, you know.
In your case the DNS in gray is what comes from your router. It is impossible to change that in your mac, but you can hit the + and add a different DNS, than make sure it is saved. I checked and it does work on Mojave. By deleting prefs. you probably fixed a corrupt setting.

 

[bvxz0138]

I am currently running Mojave 10.14 and I am being prompted to install 10.14.1. I have a 2010 Mac mini and I was curious is I can install the update and then run the post patch updater without having to download the entire Mojave image and patch. Thanks!

 

[OGNerd]

Hi Danilo,

I am using the same patch version 1.2.3, but cannot upgrade tp beta 10.14.2 beta 1. Kindly let me know how you were able to get this patch. My mac is also enrolled in Apple Beta Software Program. Attached is the file if this helps.

Thank you very much for your help.

Is your 10.14.0 installation on an APFS formatted volume?

 

[Sveto]

After Apple blacklisted my 9,1 iMac for not having metal and for having a c2d CPU, I realized they were just moving forward in technology. SO I purchased a refurb 2017 27" 5k iMac with a 2 TB fusion drive and a Radeon Pro 580. When I received it, it had High Sierra on it. Imagine my disappointment. IF they're going to blacklist me for not being able to run Mohave, then they better damn well ship they're products with Mohave on them. So I called Support. After 3 hours with a less than knowledgable support person, she told me she needed to file some B.S. report, and would not be back to me until late Tues afternoon, a full 4 days. So I went looking at the error logs. They say, Mohave cannot be loaded because of the spinner. So....wtf are they putting fusion drives into iMacs that will be stuck on HS for it's lifetime? I'm sure there is a workaround, but I EXPECT no issues when I buy a computer, not their B.S lame excuses, and putting me off. I ripped them two new ******s this morning, and demanded a another computer with Move installed by Apple, not me patching one! They couldn't even do that! I am about a ½" from going public with this, and proving to people Apple does not care about the mac any longer. They sure as he;; don't have any foresight nor did they even do their homework about these issues before releasing an OS that hobbles even macs that can receive this OS, and why the hell would they destroy the trust of their loyal customers, by their indifference and ignorance? I finally had enough today when I received the same uncaring response today from two other support people, one a senior advisor. So I demanded that I return this to the Apple store in Palm Desert, CA and they ship me a refurb with Mohave installed on it by Apple, as I acted in good faith, and they have not so far.

I have been faithful to Apple for over 20 years, all I ask is they be faithful as I have. I'm afraid you're all correct. Apple no longer cares for the mac. The real issue for me at least is, Apple had a way of making you fall in love with their products, because in my experience I had not one failure, in over 20 years. That is why Apple has such loyal customers, because we become emotionally attached to them. So it literally feels like they're intentionally hurting us. Yes, not everyone has this experience but many do, that's why the "Zealots." Don't argue with me, it's my experience, you haven't lived it.

Now, how do I put Mohave on this fusion machine? I'm just being smart and preparing for plan b. I'll dig up the error log and post it, but I've gotta a show to do, so in a few hours. I'm downloading 10.14.18. Is that the latest final?

Apple never really cared for any customer! They only care for the shareholders and their constant demands for juicier profits. Good that you finally have seen the light, and soon there will be many more. One can fool few for some time, or many for a little while, but you can't fool everybody forever.

 

[kautame]

Try this version.

Thank you. This version works, BUT in the window, under "Available EFI System Partitions" now it shows me three partitions:

disk0s1
disk2s1
disk3s1

According to System Informations, the BSD name of my internal APFS SSD with Mojave is disk1s1 (Time Machine disk is disk2s2 and another external USB disk is disk3s2)
I don't understand why it shows me all the disks (the other disks don't have an EFI partition), but I suppose I have to bless disk0s1, and that's what I did, but the result is this message:

Error
"BOOTX64.EFI" could not be found in the selected ESP's "/EFI/BOOT" directory.

Ok, what's next?

EDIT: by the way, if my internal disk is disk1s1, what is disk0s1? I thought that if the EFI partition was disk0s1, my internal disk should be disk0s2, not disk1s1…

 

[dosdude1]

Thank you. This version works, BUT in the window, under "Available EFI System Partitions" now it shows me three partitions:

disk0s1
disk2s1
disk3s1

According to System Informations, the BSD name of my internal APFS SSD with Mojave is disk1s1 (Time Machine disk is disk2s2 and another external USB disk is disk3s2)
I don't understand why it shows me all the disks (the other disks don't have an EFI partition), but I suppose I have to bless disk0s1, and that's what I did, but the result is this message:

Error
"BOOTX64.EFI" could not be found in the selected ESP's "/EFI/BOOT" directory.

Ok, what's next?

EDIT: by the way, if my internal disk is disk1s1, what is disk0s1? I thought that if the EFI partition was disk0s1, my internal disk should be disk0s2, not disk1s1…

If your Mojave APFS volume is on disk1, that indicates that your main disk is disk0... APFS makes a second "virtual" disk (AKA container), which is actually on disk0... Kind of strange. The fact that it doesn't detect a BOOTX64 file indicates that you most likely did not apply the APFS patch to that volume in the post-install tool. Try doing that, and see if that helps.

 

[kautame]

If your Mojave APFS volume is on disk1, then you'll need to bless disk1s1.

Yes, that's the problem. disk1s1 doesn't appear in the list.
[doublepost=1541310260][/doublepost]

If your Mojave APFS volume is on disk1, that indicates that your main disk is disk0... APFS makes a second "virtual" disk (AKA container), which is actually on disk0... Kind of strange. The fact that it doesn't detect a BOOTX64 file indicates that you most likely did not apply the APFS patch to that volume in the post-install tool.

I've applied the APFS patch (at least 3 or 4 times, when I was trying to fix this issue). I've applied the right post-install patches for my iMac (7,1), selecting my Mac from the list, and I'm sure that the APFS patch was selected (there were only 2 patches not selected: the recovery partition patch and the wifi patch).

Anyway, I'll try again.

 

[AphoticD]

Yes installing HighSierra APFS natively would be a regular procedure, however I read that you had created manually the VM partition (required for the integrity of APFS Scheme/Container) perhaps that's why your APFS scheme doesn't work properly, the VM partition should be created naturally by APFS (format/conversion) in a clean way and automatically populated by the system.

I chose to leave out the step for manually adding the VM volume on the most recent reinstall of Mojave 10.14.1 (Unsupported).

It appears that the formatting process in Disk Utility doesn't create the Preboot, Recovery and VM APFS volumes automatically, however the Mojave installer does the job of adding Preboot and Recovery. On my system, the VM volume is not added during installation and my only guess is that it will be added on first boot.

Anyway before re-install HighSierra, try this last attempt, boot USB Installer open DiskUtility and do a couple of First Aid on your Mojave APFS Volume, then open Terminal and type:

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

diskutil apfs updatePreboot diskXs1

reboot and unplug the USB Installer.

I ran Disk Utility First Aid separately on the device, the container and the Mojave volume, repeated by the updatePreboot (again). However, this results in the same no-boot behaviour again. ("Error loading kernel cache (0x7)" at boot time with -v boot).

edit:
A couple of questions: During the Mojave Post-Install do you have used any APFS patch ? You should not use that.

No, the APFS patch is disabled for MacBookPro8,1.

And which kind of hard disk do you have inside? Spinning or SSD ? Some old spinning hard disks have compatibility issues with APFS file system that was introduced especially for the SSDs.

It is an SSD.

I had installed High Sierra on a HDD (HFS+), then removed the HDD and dropped in the SSD (APFS), so maybe the Mac needs me to install High Sierra onto the SSD and then upgrade to Mojave? (instead of trying to install Mojave on a fresh system)

 

[Yipee2016]

Hello,

I read some posts and I want to be sure. I have a MacPro 3.1 and I have made a firmware update to support the APFS Boot. My Mac run (very well) with Mojave 10.14. I want to update it to 10.14.1 but the update is not in the software update. What can I do ?
Thanks

 

[L Caputo]

Hello,

I read some posts and I want to be sure. I have a MacPro 3.1 and I have made a firmware update to support the APFS Boot. My Mac run (very well) with Mojave 10.14. I want to update it to 10.14.1 but the update is not in the software update. What can I do ?
Thanks

download and then install from here, https://support.apple.com/en-gb/HT201295
are you sure your disk is APFS, only APFS will get updates via System Preferences> Software Update
system updates are no longer to be found in the App Store in Mojave.