macOS 10.14 Mojave on Unsupported Macs Thread

[telepati]

It's all right, you are almost there, it is exactly your APFS Recovery path where the boot.efi is pointing is correct, just do this copy from your /System/Library/PrelinkedKernels/ folder ONLY the file prelinkedkernel into your /Volumes/Recovery/Your-random-numbers-letters/

then ONLY inside this path /Volumes/Recovery/Your-random-numbers-letters/ simply rename the fresh copied file from prelinkedkernel to immutablekernel, that's it.

After done booting with CMD+R and you will land to your APFS Recovery.
Keep in mind that from there you can't re-install Mojave, but only use the Utilities.

Little confused please dont be mad;

This is inside of my /Volumes/Recovery/Your-random-numbers-letters/ (As you see I already renamed those files)

And this is inside of my PrelinkedKernels Folder (Files are inside of the square I copied from random numbers folder and arrows show you must not delete which you said) I think probem is in this folder

 

[tchek]

OMG！can not make update on it?

I already made it

 

[jackluke]

Little confused please dont be mad;

This is inside of my /Volumes/Recovery/Your-random-numbers-letters/ (As you see I already renamed those files)

View attachment 799922

And this is inside of my PrelinkedKernels Folder (Files are inside of the square I copied from random numbers folder and arrows show you must not delete which you said) I think probem is in this folder

View attachment 799925

No, you have to don't touch your Prelinkedkernels Folder, BUT only copy from there the prelinkedkernel file into your /Volumes/Recovery/Random-numbers-letters/

then while inside your /Volumes/Recovery/Random-numbers-letters/
rename this prelinkedkernel into immutablekernel

that's all.

edit:
However there is no need to keep inside your Prelinkedkernels folder these files are not needed you can delete them:
prelinkedkernelbackup
immutablekernelbackup
PlatformSupportbackup.plist

BUT never delete "prelinkedkernel" file inside the /System/Library/Prelinkedkernels/
this is required to boot macOS.

 

[skiabox]

@jackluke : I am lost sir.
Can you explain to us what do you achieve with all these actions!
Thank you!

 

[jackluke]

@jackluke : I am lost sir.
Can you explain to us what do you achieve with all these actions!
Thank you!

Make bootable and workable the APFS Recovery with CMD+R on unsupported Mojave macs.

I know we have USB Installers, but it's just to make working a (mandatory) internal stock APFS partition.

 

[pippox0]

Just installed 10.14.1 ! Thanks a lot Dosdude

 

[antony34]

No !

oops.......
so, need keep on 10.14 as i have no extra drive to backup the data....

 

[skiabox]

The only solution I can think of until dosdude1 overcomes the problem with updating mojave only using clean install method is this thread : https://forums.macrumors.com/threads/migration-assistant-high-sierra-to-mojave.2143168/

Of course you will need an external disk drive bigger than your internal one!

 

[LuisN]

MacBook 5,2 - OTA Update - NO
Install over 10.14 - YES
MacBook 6,1 - OTA Update - NO
Install over 10.14 - YES
MacBook Pro 6,2 - OTA Update YES

 

[videotape74]

I was wondering if there has been any update to improving the font in Mojave...the fact that it is kind of blurry/unsharp? I am using a MBP 5,4 on 10.14.1

Thanks for any/all help!

 

[coasterOneEightThree]

Thank you dosdude1, for taking the time to get us all going again. My MacPro 3,1 is once again working perfectly.

Is your boot drive APFS or HFS+ formatted?

 

[telepati]

No, you have to don't touch your Prelinkedkernels Folder, BUT only copy from there the prelinkedkernel file into your /Volumes/Recovery/Random-numbers-letters/

then while inside your /Volumes/Recovery/Random-numbers-letters/
rename this prelinkedkernel into immutablekernel

that's all.

edit:
However there is no need to keep inside your Prelinkedkernels folder these files are not needed you can delete them:
prelinkedkernelbackup
immutablekernelbackup
PlatformSupportbackup.plist

BUT never delete "prelinkedkernel" file inside the /System/Library/Prelinkedkernels/
this is required to boot macOS.

Ok, I did and Recovery came. But its useless Magic Mouse and Keyboard are not working.

 

[joelw135]

I was wondering if there has been any update to improving the font in Mojave...the fact that it is kind of blurry/unsharp? I am using a MBP 5,4 on 10.14.1

Thanks for any/all help!

Yes having the same problem on a Mac Mini 3,1 really bad font display.

 

[Banglazed]

Installed Mojave on my old MBA 2011 and it works perfectly! The latest patcher v1.2.3 fixes the hang when trying to boot from the USB. It was a long process though.

 

[jackluke]

Ok, I did and Recovery came. But its useless Magic Mouse and Keyboard are not working.

View attachment 799933

It's because dosdude1 has probably embedded into its Mojave Patcher a new bluetooth patch that is not compatible with APFS Recovery (that essentially is a compressed BaseSystem.dmg expanded into the RAM), you have to use the stock Mojaves Bluetooth kexts, meanwhile try to use a USB keyboard/mouse and let me know.

 

[telepati]

It's because dosdude1 has probably embedded into its Mojave Patcher a new bluetooth patch that is not compatible with APFS Recovery, you have to use the stock Mojaves Bluetooth kexts, meanwhile try to use a USB keyboard/mouse and let me know.

I dont have USB keyboard/mouse I have just Apple Keyboard and Magic Mouse

is there any way to hide APFS boot.log?

 

[jackluke]

I dont have USB keyboard/mouse I have just Apple Keyboard and Magic Mouse

is there any way to hide APFS boot.log?

I don't use the APFS patch (I have native APFS) so I don't have boot.log and I don't know how it works.


Meanwhile about fixing Bluetooth devices into the APFS Recovery try this:

Boot normally Mojave then open as you already know your /Volumes/Recovery/Random-numbers-letters/

delete the immutablekernel inside

now keeping this finder window opened, plug and open the USB Mojave Installer and navigate into the USB path /System/Library/Prelinkedkernels/

copy the prelinkedkernel from the USB Mojave Installer into your /Volumes/Recovery/Random-numbers-letters/

while inside /Volumes/Recovery/Random-numbers-letters/ rename this fresh copied file from prelinkedkernel to immutablekernel

reboot with CMD+R now bluetooth devices on APFS Recovery should work.

 

[telepati]

I don't use the APFS patch (I have native APFS) so I don't have boot.log and I don't know how it works.


Meanwhile about fixing Bluetooth devices into the APFS Recovery try this:

Boot normally Mojave then open as you already know your /Volumes/Recovery/Random-numbers-letters/

delete the immutablekernel inside

now keeping this finder window opened, plug and open the USB Mojave Patcher and navigate into the USB path /System/Library/Prelinkedkernels/

copy the prelinkedkernel from the USB Mojave Patcher into your /Volumes/Recovery/Random-numbers-letters/

while inside /Volumes/Recovery/Random-numbers-letters/ rename this fresh copied file from prelinkedkernel to immutablekernel

reboot with CMD+R now bluetooth devices on APFS Recovery should work.

You mean MacOS Mojave Patcher or USB installer which I create with MacOS Mojave Patcher v1.2.3?

 

[dosdude1]

Ok, I did and Recovery came. But its useless Magic Mouse and Keyboard are not working.

View attachment 799933

Recovery is useless even when it does work right, especially on unsupported machines. Just use your patched USB installer, it can do anything the dumb Recovery Partition can.

 

[jackluke]

You mean MacOS Mojave Patcher or USB installer which I create with MacOS Mojave Patcher v1.2.3?

USB Installer.
[doublepost=1541003358][/doublepost]

Recovery is useless even when it does work right, especially on unsupported machines. Just use your patched USB installer, it can do anything the dumb Recovery Partition can.

Agree, but on any APFS scheme/container is mandatory to have the APFS Recovery, it's just a plus emergency partition (CMD+R) where you can use always useful standard Utilities (DiskUtility, TimeMachine, Terminal and few other) saving a bit of USB power.

That said your USB Mojave Installer is also an ultra-improved Recovery.

You included too the "Recovery HD HFS patch".

 

[telepati]

@jackluke is it APFS working without APFS patch? HOW? 'cause I really want to get rid of APFS boot.log.

 

[jackluke]

@jackluke is it APFS working without APFS patch? HOW? 'cause I really want to get rid of APFS boot.log.

No, APFS patch is required on unsupported mac to support any APFS feature and Mojave updates.
[doublepost=1541004775][/doublepost]

MacBook 5,2 - OTA Update - NO
Install over 10.14 - YES
MacBook 6,1 - OTA Update - NO
Install over 10.14 - YES
MacBook Pro 6,2 - OTA Update YES

Core2Duo

Core2Duo

i5/i7

OTA worked cause, as I stated earlier, any legacy mac equipped with i5/i7 to me is almost Mojave natively supported, only Metal missing.

 

[dosdude1]

@jackluke is it APFS working without APFS patch? HOW? 'cause I really want to get rid of APFS boot.log.

The only way to get rid of it is to patch your system with APFS ROM Patcher, which can be a bit risky.

 

[Macschrauber]

Since 14.1 my Mac Pro 3.1 does not boot from Mojave until I use the boot picker (alt-key on cold start)

Just a freezing white screen, no stop sign. EFI GPU is in.

-no_compat_check and -v is set as boot-args

Zapping pram wont help, setting startup disk via control panal neither.

I am not exactly sure if that happened before as I almost always chose the boot picker.

I've tested another patched Mojave installation I had on an external USB SSD Drive. Booted without problems, reinstalled 14.1 over it, booted nicely.

Got the idea to use Mojave's Disk Utility to repair the internal disk containing the 14.1 installation with this -white-screen-dont-boot-bug-but-with-boot-picker-ok behaviour. And that solved the problem. Repaired disk and partitions. That disk has a few test installations with Sierra and High Sierra.

 

[coasterOneEightThree]

@dosdude1:

I can't do the update to 10.14.1 at this moment. My Mac Pro 3.1 has a patched ROM for native APFS support.

Tried via system update = boot loop

Patched this system with the post install app of 1.2.2 = stop sign

Updated a recovered backup with Mojave patcher 1.2.3 and a full 10.14.1 installer from a USB drive (with post install afterwards, of course) = stop sign.

On post install the caches always were cleared automatically, I didn't force them to clear.

What could be done to update successfully? No clean installation, please ...