macOS 10.14 Mojave on Unsupported Macs Thread

[pwm86]

Just to report: Mojave runs on
iMac9.1 /8GB/SSD1TB under APFS, without any problem.
Macbook Air 2011/i7/4GB/256GB (it was APFS already under High Sierra), without any problem.
Just waiting for macports to be updated.
Many thanks for the MacOS Mojave Patcher.

 

[flyinmac]

Just to report: Mojave runs on
iMac9.1 /8GB/SSD1TB under APFS, without any problem.
Macbook Air 2011/i7/4GB/256GB (it was APFS already under High Sierra), without any problem.
Just waiting for macports to be updated.
Many thanks for the MacOS Mojave Patcher.

Curious... would you by chance have the same 9,1 that I do?

Mine is the 20-inch Early 2009 iMac 9,1 with a core2duo 2.66 and the nVidia 9400m.

I’ve got the built-in iSight of course. And upgraded the memory to 8 GB.

I’m curious about whether the iSight has worked on my model for others. Also curious about light-mode graphics anomalies on my model.

Any other issues anyone has with Mojave on the same model I have?

 

[jackluke]

I installed Mojave in my Macbook 6,1 (suport High Sierra and APFS) and now I need boot on recovery mode but when press CMD+R the recovery partition is missing. Doesn't work recovery mode with Mojave (installed with Movaje patcher tool)?

Agree, this is not bordered only to the Mojave Patcher, but occurs also during supported macOS upgrades, sometimes recovery HD "brokens" itself, in past I had similar issue, and had necessity to make recovery partition available at startup manager (holding option at power-on). I found a safe method, however I need to search a bit between my files, I'll test it on Mojave and let you know (and to the others) later.

 

[lumos]

I have upgraded my MacPro 3,1 from High Sierra to Mojave.
The High Sierra FS was HFS+ with trimforce enable.
Later I converted it to APFS but now my Samsung EVO 850 Pro, does not have anymore the Trim Enabled (before, with High Sierra HFS+ was enabled).

Is this correct because APFS has its own trim function or I need to enable trim with a utility like Trime Ebabler https://cindori.org/trimenabler/?

Thanks

 

[yeiyei0891]

Agree, this is not bordered only to the Mojave Patcher, but occurs also during supported macOS upgrades, sometimes recovery HD "brokens" itself, in past I had similar issue, and had necessity to make recovery partition available at startup manager (holding option at power-on). I found a safe method, however I need to search a bit between my files, I'll test it on Mojave and let you know (and to the others) later.

I mean: recovery partition doesn't work anymore in Movaje on unsupported device?

In the web says:
If you have a machine that did NOT natively support High Sierra (and therefore cannot boot APFS volumes natively), please note the following:
-- If you use APFS, you will not have a bootable Recovery partition.
But my MacBook support High Sierra and APFS, then why Recovery Partition doesn't work?

 

[jackluke]

Please note this is valid only for HFS+ Mojave installation, for APFS Volumes it requires a deeper analysis.

Here is a method simple and effective to make "Mojave Recovery HD" available at startup manager (holding alt-option after power-on), little premise this method was probably used since OSX Lion when, not for nothing, the Recovery HD was introduced by apple.

From a booted system, launch Mojave Terminal and do the followings:

diskutil list
(locate your recovery partition labelled "Recovery HD" and its exactly diskXsY for example disk0s3)

sudo asr adjust -target /dev/diskXsY -settype "Apple_HFS"


you've done, after reboot, holding alt-option, your Recovery HD will be a bootable Volume.

edit:
for APFS Volumes is a bit tricky cause there is a new container and partitioning scheme has changed.
Anyone can take a look typing from Terminal simply: diskutil apfs list

 

[pwm86]

Curious... would you by chance have the same 9,1 that I do?

Mine is the 20-inch Early 2009 iMac 9,1 with a core2duo 2.66 and the nVidia 9400m.

I’ve got the built-in iSight of course. And upgraded the memory to 8 GB.

I’m curious about whether the iSight has worked on my model for others. Also curious about light-mode graphics anomalies on my model.

Any other issues anyone has with Mojave on the same model I have?

Early 24-inch 2009 iMac9./ core2duo 2.66/1 8GB/1TB SSD (Electra G3)/ NVIDIA GeForce 9400 256 MB graphics.
iSight works.

 

[yeiyei0891]

Please note this is valid only for HFS+ Mojave installation, for APFS Volumes it requires a deeper analysis.

Here is a method simple and effective to make "Mojave Recovery HD" available at startup manager (holding alt-option after power-on), little premise this method was probably used since OSX Lion when, not for nothing, the Recovery HD was introduced by apple.

From a booted system, launch Mojave Terminal and do the followings:

diskutil list
(locate your recovery partition labelled "Recovery HD" and its exactly diskXsY for example disk0s3)

sudo asr adjust -target /dev/diskXsY -settype "Apple_HFS"


you've done, after reboot, holding alt-option, your Recovery HD, will be a bootable Volume.

Ok, but my Disk is APFS not HFS, this won't work.
With the command "diskutil list" I can see the Recovery Partition, it's there. But doesn't work when I press ALT in startup.

Then isn't possible Recovery Partition works with APFS?

 

[lumos]

Ok, but my Disk is APFS not HFS, this won't work.
With the command "diskutil list" I can see the Recovery Partition, it's there. But doesn't work when I press ALT in startup.

Then isn't possible Recovery Partition works with APFS?

I have installed Mojave in my MacPro 3,1 in HFS+ and after that I have converted it to APFS.
To make my recovery partition bootable, I have edited the /Volumes/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist inserting my MacPro string.
The partition recovery now boot without problems.

 

[jackluke]

Ok, but my Disk is APFS not HFS, this won't work.
With the command "diskutil list" I can see the Recovery Partition, it's there. But doesn't work when I press ALT in startup.

Then isn't possible Recovery Partition works with APFS?

At the moment on APFS no, but you could create from diskutility a new volume of 2 GB inside your APFS Mojave and restore into that 2 GB Volume a BaseSystem.dmg .

However the USB Mojave Patcher is alone an improved Recovery, so a Recovery HD is not needed in that case, and even on an SSD a Recovery is slow on booting, Recovery is a particular dmg process in RAM, so it's not so quicker booting from an SSD rather than booting from an USB Installer.

 

[yeiyei0891]

At the moment on APFS no, but you could create from diskutility a new volume of 2 GB inside your APFS Mojave and restore into that 2 GB Volume a BaseSystem.dmg .

However the USB Mojave Patcher is alone an improved Recovery, so a Recovery HD is not needed in that case, and even on an SSD a Recovery is slow on booting, Recovery is a particular dmg process in RAM, so it's not so quicker booting from an SSD vs an USB Installer.

I can't be always with a USB only for use Mojave Patcher.
[doublepost=1538407406][/doublepost]

I have installed Mojave in my MacPro 3,1 in HFS+ and after that I have converted it to APFS.
To make my recovery partition bootable, I have edited the /Volumes/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist inserting my MacPro string.
The partition recovery now boot without problems.

What is it that MacPro string?

 

[jackluke]

I can't be always with a USB only for use Mojave Patcher.
[doublepost=1538407406][/doublepost]
What is it that MacPro string?

to see your APFS Volumes "string" namely UUID, type from terminal: diskutil apfs list

edit:
No my mistake, probably @lumos meant the "Mac Model Machine string", however he could help better on this, his intuition is very good.

To get your "Mac Model string" type from Terminal:

ioreg -l | grep -i board-id

sysctl hw.model

 

[lumos]

to see your APFS Volumes "string" namely UUID, type from terminal: diskutil apfs list

edit:
No my mistake, probably @lumos meant the "Mac Model Machine string", however he could help better on this, his intuition is very good.

Yes, sorry for my bad description.

What I do (in my case for the MacPro:

Open Terminal

1.) diskutil list
2.) diskutil mount disk "name of the Recovery HD"
3.) sudo pico /Volumes/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist

First string group add:

<string>Mac-F42C88C8</string>

Second group add:

<string>MacPro3,1</string>


Search for your model string and add it.
After that, the Recovery Partition should work.

 

[yeiyei0891]

Yes, sorry for my bad description.

What I do (in my case for the MacPro:

Open Terminal

1.) diskutil list
2.) diskutil mount disk "name of the Recovery HD"
3.) sudo pico /Volumes/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist

First string group add:

<string>Mac-F42C88C8</string>

Second group add:

<string>MacPro3,1</string>


Search for your model string and add it.
After that, the Recovery Partition should work.

I have to add two lines? My MacBook is 6,1 model but the other number (Mac-F42C88C8) how can I see it?

 

[jackluke]

I have to add two lines? My MacBook is 6,1 model but the other number (Mac-F42C88C8) how can I see it?

From Terminal:
ioreg -l | grep -i board-id

 

[jackluke]

Yes, sorry for my bad description.

What I do (in my case for the MacPro:

Open Terminal

1.) diskutil list
2.) diskutil mount disk "name of the Recovery HD"
3.) sudo pico /Volumes/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist

First string group add:

<string>Mac-F42C88C8</string>

Second group add:

<string>MacPro3,1</string>


Search for your model string and add it.
After that, the Recovery Partition should work.

Your method is good but needs a little modification for an APFS disk, you have first to identify the main APFS container UUID that is the actually "folder" real name of "Recovery HD" (on APFS Container label is "Recovery"), however as I wrote before, you have to type from Terminal: diskutil apfs list

diskutil mount diskXsY (where the APFS recovery is for example disk0s3)

APFS container UUID needed for APFS Recovery is exactly the same of the diskXs1 (main APFS Mojave container) and it's a typical long string made by random numbers-letters

then the true "Mojave Recovery" path where use the pico command is this:

/Volumes/Recovery/YourAPFSmainUUID/PlatformSupport.plist

 

[ASentientBot]

To @jackluke and others. You can just delete PlatformSupport.plist. Adding keys to it is unnecessary (at least as of Mojave beta 2). I keep seeing people suggest this, and it is absolutely not needed. Try it. It works.

 

[jackluke]

To @jackluke and others. You can just delete PlatformSupport.plist. Adding keys to it is unnecessary (at least as of Mojave beta 2). I keep seeing people suggest this, and it is absolutely not needed. Try it. It works.

Agree, but probably to have CMD+R working at power-on with a Mojave APFS Container installation the PlatformSupport.plist presence could be needed, or maybe not, perhaps as you wrote deleting it in this scope could mean "all machines allowed to use CMD+R".

 

[TimothyR734]

Early 24-inch 2009 iMac9./ core2duo 2.66/1 8GB/1TB SSD (Electra G3)/ NVIDIA GeForce 9400 256 MB graphics.
iSight works.

Works on my iMac 9,1 you have to replace 5 kexts from HS to get iSight to work

 

[yeiyei0891]

From Terminal:
ioreg -l | grep -i board-id

Thanks, when I get home I'll try it.
[doublepost=1538422286][/doublepost]

To @jackluke and others. You can just delete PlatformSupport.plist. Adding keys to it is unnecessary (at least as of Mojave beta 2). I keep seeing people suggest this, and it is absolutely not needed. Try it. It works.

How can I delete this file? Where is it?

 

[Luckygreek]

Just a heads up to all considering the update to Mojave, although most here have already done so, (myself included) however here's an interesting layout of potential issues/non issues with Mojave & APFS, Bluetooth, Keyboards, end of OpenCL & OpenGL, Prioritizing external GPU's, end of non-App-Store Safari exts & plug-ins, FaceTime, recommended GC for 'old" MP's, unsupported Mac, as well as a host of other Pro's & Cons. It's a long read.
https://arstechnica.com/features/2018/09/macos-10-14-mojave-the-ars-technica-review/

 

[arqueox]

How can I fix this error? Any help, please?

md5: ./HIToolbox.framework/Versions/A/HIToolbox: No such file or directory

/Library/Developer/CommandLineTools/usr/bin/objdump: './HIToolbox.framework/Versions/A/HIToolbox': No such file or directory

Could not find: ./HIToolbox.framework/Versions/A/HIToolbox.

 

[TimothyR734]

How can I fix this error? Any help, please?

md5: ./HIToolbox.framework/Versions/A/HIToolbox: No such file or directory

/Library/Developer/CommandLineTools/usr/bin/objdump: './HIToolbox.framework/Versions/A/HIToolbox': No such file or directory

Could not find: ./HIToolbox.framework/Versions/A/HIToolbox.

/System/Library/Frameworks/Carbon.framework/Versions/Current/Frameworks/HIToolbox.framework/Versions/Current how did you find pkouameon GitHub do you have a cope of pkouame patched HIToolbox ?

 

[jackluke]

How can I fix this error? Any help, please?

md5: ./HIToolbox.framework/Versions/A/HIToolbox: No such file or directory

/Library/Developer/CommandLineTools/usr/bin/objdump: './HIToolbox.framework/Versions/A/HIToolbox': No such file or directory

Could not find: ./HIToolbox.framework/Versions/A/HIToolbox.

@TimothyR734 is right, but that path is a bit tricky, from Terminal:

cd /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/

(be careful typing from Terminal it's case-sensitive)

however you have to copy inside the stock Mojave HiToolbox

 

[arqueox]

/System/Library/Frameworks/Carbon.framework/Versions/Current/Frameworks/HIToolbox.framework/Versions/Current how did you find pkouameon GitHub do you have a cope of pkouame patched HIToolbox ?

@TimothyR734 is right, but that path is a bit tricky, from Terminal:

cd /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox/Versions/A/

(be careful typing from Terminal it's case-sensitive)

however you have to copy inside the stock Mojave HiToolbox

I don't get it... still :no such file or directory..

i have Xcode and command line installed. any thoughts?