macOS 10.14 Mojave on Unsupported Macs Thread

[0403979]

Sorry for maybe "stupid question"....

If I disable on my Macbook Pro 8,2 15" AMD 6490 GPU Card by software.... that have effect in my two OS (High Sierra official & Mojave patched) or only in the OS where will execute the commands on Console mode and Recovery partition??

Regards

It will affect the entire machine and every operating system installed on it. Good news is that it’s easily reversible by resetting the PRAM or NVRAM.
[doublepost=1538915875][/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.

I also tried this and it failed.

 

[jackluke]

I also tried this and it failed.

I explained previously why, if you already had an HFS "Recovery HD" then APFS Recovery won't work, your current "CMD+R" points to another partition, while if you don't have HFS "Recovery HD" it means you have more than one hard disk, or you have created too many partitions into your APFS/HFS hard disk, the APFS Container/Scheme is very particular, CMD+R is associated (most probably) only to this scheme:

diskutil list

EFI disk0s1
APFS Container disk0s2
APFS Container Scheme disk1
APFS Volume disk1s1 (used for HighSierra or Mojave)
APFS Preboot disk1s2 (used for FileVault 2 encryption)
APFS Recovery disk1s3 (used for Recovery and CMD+R)
APFS VM disk1s4 (used for sleep image)

diskutil apfs list
shows the details of the current APFS scheme with their gpt UUID

 

[jackluke]

I have understood the reason for those who encountered issue on booting the APFS Recovery, they have their Mojaves encrypted (FileVault 2), so they meet "prohibitory sign" with CMD+R, a risky attempt to unlock this, booting from Mojave APFS launch Terminal and type:

diskutil apfs list

locate your "APFS Preboot" on diskXs2 (typically mounted on disk1s2)

diskutil mount diskXs2

open /Volumes/Preboot

once on Finder double click on "random-numbers-letters" folder and navigate into com.apple.installer folder renaming the PlatformSupport.plist into PlatformSupportbackup, then back to the "random-numbers-letters" folder and navigate through /System/Library/CoreServices/ and inside rename (another) PlatformSupport.plist into PlatformSupportbackup2

Even if I guess this will work, do this attempt only if you have an "empty" Mojave installation without any important files on it, and only if you can erase the disk in case it results unbootable after, or be sure to have a recent TimeMachine backup.

 

[0403979]

I have understood the reason for those who encountered issue on booting the APFS Recovery, they have their Mojaves encrypted (FileVault 2), so they meet "prohibitory sign" with CMD+R, a risky attempt to unlock this, booting from Mojave APFS launch Terminal and type:

diskutil apfs list

locate your "APFS Preboot" on diskXs2 (typically mounted on disk1s2)

diskutil mount diskXs2

open /Volumes/Preboot

once on Finder double click on "random-numbers-letters" folder and navigate into com.apple.installer folder renaming the PlatformSupport.plist into PlatformSupportbackup, then back to the "random-numbers-letters" folder and navigate through /System/Library/CoreServices/ and inside rename (another) PlatformSupport.plist into PlatformSupportbackup2

Even if I guess this will work, do this attempt only if you have an "empty" Mojave installation without any important files on it, and only if you can erase the disk in case it results unbootable after, or be sure to have a recent TimeMachine backup.

Will reinstalling Mojave fix this if it fails?

 

[jackluke]

Will reinstalling Mojave fix this if it fails?

Yes, it should not fail cause it doesn't touch any important boot system files, in the worst case you have to erase the disk first.

 

[0403979]

Yes, in the worst case you have to erase the disk first.

Alright. I’ll try this.

 

[jackluke]

Alright. I’ll try this.

It will work, my concern is only about FileVault 2 that may vary on different machines, anyway I am not 100% sure if that will bring "Internet Recovery" or "offline Recovery" into an unsupported "encrypted" machine, if you see the picture I've attached, avoid to use CMD+R on an unsupported Mojave mac that would not be safe even if could work renaming those PlatformSupport.plist files.

 

[0403979]

It will work, my concern is only about FileVault 2 that may vary on different machines, anyway I am not 100% sure if that will bring "Internet Recovery" or "offline Recovery" into an unsupported "encrypted" machine, if you see the picture I've attached, avoid to use CMD+R on an unsupported Mojave mac that would not be safe even if could work renaming those PlatformSupport.plist files.

I can’t find a com.apple.installer folder anywhere on either drive.

 

[jackluke]

I can’t find a com.apple.installer folder anywhere on either drive.

Weird, do you have all hidden files showed? In case you have hidden files and don't have this folder, rename only the other PlatformSupport.plist, I guess the second one is more important to "fix" the Recovery on FileVault2 Volume.

 

[0403979]

Weird, do you have all hidden files showed? In case you have hidden files and don't have this folder, rename only the other PlatformSupport.plist, I guess the second one is more important to "fix" the Recovery on FileVault2 Volume.

I have them showing and it’s not there. I removed the other file but I haven’t tried booting yet. Should I also modify the com.apple.boot.plist? Btw I have FileVault enabled.

 

[jackluke]

I have them showing and it’s not there. I removed the other file but I haven’t tried booting yet. Should I also modify the com.apple.boot.plist? Btw I have FileVault enabled.

No, leave com.apple.Boot.plist untouched.

 

[0403979]

No leave com.apple.Boot.plist untouched, it should be empty inside.

It isn’t. It has the default dmg open string.
[doublepost=1538928056][/doublepost]

No, leave com.apple.Boot.plist untouched.

Just tried with both platformsupport files gone, prelinkedkernel gone, and immutablekernel replaced with the patched prelinkedkerenel. Still a prohibitory sign.

 

[jackluke]

It isn’t. It has the default dmg open string.

Not sure but that should be a call for Internet Recovery, however leave it unmodified, and try a CMD+R+V (Recovery with verbose mode) and see what happens.

 

[0403979]

Not sure but that should be a call for Internet Recovery, however leave it unmodified, and try a CMD+R+V (Recovery with verbose mode) and see what happens.

It boots normally, verbose doesn’t work unless no other keys are pressed.

 

[jackluke]

Try to boot from the USB Mojave Installer Terminal and "force verbose mode on Recovery" typing:

csrutil disable
nvram boot-args="-no_compat_check -v"
reboot

Then after power-on hold CMD+R and post a picture to see where it stops exactly.

edit:
To return normal booting with apple logo again you have to do later:
nvram boot-args="-no_compat_check"

edit:
Another risky attempt could be replace the "com.apple.Boot.plist" inside the APFS Preboot with the one inside the APFS Recovery, but this is very risky, keep a backup of your current com.apple.Boot.plist into Preboot rename it into com.apple.Boot.backup

 

[yeiyei0891]

It will work, my concern is only about FileVault 2 that may vary on different machines, anyway I am not 100% sure if that will bring "Internet Recovery" or "offline Recovery" into an unsupported "encrypted" machine, if you see the picture I've attached, avoid to use CMD+R on an unsupported Mojave mac that would not be safe even if could work renaming those PlatformSupport.plist files.

The mouse and keyboard are still frozen when I enter the recocery mode in my MacBook.
I didn't find any solution for this.

 

[jackluke]

The mouse and keyboard are still frozen when I enter the recocery mode in my MacBook.
I didn't find any solution for this.

I have found a solution to that, follow this guide and they will work: Fix APFS Recovery on Mojave

in your specific case you have simply to use your Mojave /System/Library/PrelinkedKernels/prelinkedkernel file
copying it inside the /Volumes/Recovery/RandomNumbersLetters/
and lastly rename it inside /Volumes/Recovery/RandomNumbersLetters/ from prelinkedkernel into immutablekernel

 

[FlorisVN]

thx again dosdude1!

Great work !

iMac 27" 2011 working great, with upgraded GPU.
I only had to deselect the legacy video card patch, upgraded Nvidia GTX765M works perfect with Metal.

Great advice for all you 2011 , and probebly also 2010 and 2009 iMac users !
Upgrade your GPU, and problems solved for Mojave, aswell as unreliable AMD graphics cards in these series...

 

[m3lodq]

Hello

I try that and it resolved my problem with my Logitech Brio Webcam.

Thank you!

Hi! What did you do exactly? Did you replace all Mojave iousb kexts with the ones from High Sierra? I also need to get brio webcam working on Mojave.

 

[Elektronenhirn]

The best thing you can do to disable the dGPU on these systems is outlined in my post here. This is a permanent solution, and doesn't rely on NVRAM variables that could get erased, and doesn't require deleting any kexts from Mac OS.

So you haven't any fix for my missing screen brightness and the sleep problem?
I have to follow Wooser's guid?

 

[toufiqueimam]

Hi, The greyish weird shadow of mojave seems partially fixed on my mac (mbp early 2011, 13"). While in dark mode, I went to settings > general > sidebar icon size made large > Switch back to the light theme.

 

[dosdude1]

So you haven't any fix for my missing screen brightness and the sleep problem?
I have to follow Wooser's guid?

No... Performing this mod will restore full sleep mode capability, and using my new piece of hardware, you can get full backlight brightness control working again.

 

[jackluke]

Hi, The greyish weird shadow of mojave seems partially fixed on my mac (mbp early 2011, 13"). While in dark mode, I went to settings > general > sidebar icon size made large > Switch back to the light theme.

You are using Totalfinder, that's why it seems "fixed".
[doublepost=1538943906][/doublepost]

Hi! What did you do exactly? Did you replace all Mojave iousb kexts with the ones from High Sierra? I also need to get brio webcam working on Mojave.

Exactly, for safety replace all the 5 IOUSB*** kext from High Sierra. If you don't have them use these: 5 IOUSB kexts by @TimothyR734

 

[Pinarek]

= "0403979, Post: 26626807, Mitglied: 1133429"]
I tried installing 10.14.1 beta 2 on Wednesday. Everytime I tried the computer failed to boot afterwards, even after applying patches. I kept reinstalling and trying again but to no avail. Has anyone successfully gotten either version of 10.14.1 working?

Yes Julian I now have the problem (in my case anyway) found.
I have a Hackintosh HackBook, is a Medion Akoya P8610 but runs as an iMac 10.1 SMBIOS, other versions of SMBIOS, like MacBook 5.2 (most similar to the hardware) does not work.

Ok now for the update from 10.14 Final to 10.14.1 and 2.
Install .. after the 1st reboot then again from the USB stick dosdude1 Mojave Patcher run and just this time not my iMac10,1 but I just once on suspicion then iMac 12.2 selected. Then select the appropriate patches as always. And lo and behold, he then boats without problems and installed to end.

With the repeated attempt (out of curiosity), he then also with the selection iMac12,2 not continue .. then I just once iMac12,1 selected and lo and behold, he then boot after reboot and installed properly to the end.

Why is that so coincidental that it works?

Previously at Betas 10.14 (Beta1 through 11), there were no such issues.

Incidentally, with the wonderful tool of gengik84 (User in insanelymac forum) the MacOS_Updater (so you can install Mojave on HFS + synonymous now update the 10.14 to 10.14.1 and 10.14.2) I hang the tool times in the attachment with it. Therefore, APFS is no longer necessary on our Hackis and your original Macs.

 

[indigotheory]

I tried installing 10.14.1 beta 2 on Wednesday. Everytime I tried the computer failed to boot afterwards, even after applying patches. I kept reinstalling and trying again but to no avail. Has anyone successfully gotten either version of 10.14.1 working?

Same here on my Late 2008 Macbook, installed the update, rebooted and it hangs on the light coloured screen with the apple logo and loading bar. Rebooted into the usb drive and applied the patches again and checked to rebuild caches and still the same. Is there a fix or is it another complete reinstall?