macOS 10.14 Mojave on Unsupported Macs Thread

[zdrmonster50]

hey! is it possible to run MacOS Mojave on PowerPC Macs?

 

[joelw135]

Has anyone run into Time Machine failing to complete a backup?

 

[PeterWan]

hey! is it possible to run MacOS Mojave on PowerPC Macs?

since MacOS 10.7 (Lion) MacOS does NO LONGER SUPPORT PowerPC Macs.

 

[dosdude1]

since MacOS 10.7 (Lion) MacOS does NO LONGER SUPPORT PowerPC Macs.

Not even, OS X 10.5 Leopard was the last version to support PowerPC.

 

[BookEmDanno]

@dosdude1 Have installed Mojave on my MacBook Air 4.2 (mid 2011) by a Mojave Patcher tool 1.2.2 a couple days ago with default patcher values for my MBA rig. Used my AirPods and another stuff. All works like a charm before patch updater installed first bluetooth patch (think it was version 0).
Tried to revert IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from patched USB drive with kext rebuild but no luck. Now patcher updated Bluetooth patch to version 2. Have same problem... What should I do now to have working bluetooth?
Waiting for next patch update and thank you for all your hard work!

My list of patches in attach

I have the same MBAir4,2 (on 10.14.1 beta 2) and did get a bluetooth version 2 update notice. Ran the patch, rebuild caches and rebooted. It's working fine for me.

Good luck to you in making it work.
[doublepost=1538799349][/doublepost]@dosdude1, can I go ahead and update the OP with the listing below to say "do not install" to "install at your own risk (or something to the effect that you can try but might not work on you unsupported mac)".
It did work work for me using your patch process.
macOS 10.14 Mojave on Unsupported Macs Thread


Let me know if it's appropriate and thanks for your patch app.

 

[Ludacrisvp]

com.apple.telemetry.plugin does not contain SSE4.2 instructions.

I see, I was obviously under the mistaken impression that it did and that was why there were issues.
What is it that makes this incompatible with the 3,1 / legacy platforms then?

 

[ASentientBot]

I see, I was obviously under the mistaken impression that it did and that was why there were issues.
What is it that makes this incompatible with the 3,1 / legacy platforms then?

I have no idea. But it's not SSE4.2, I'm almost certain. I wrote an AppleScript to scan each system file for SSE4.2 instructions. That file contains none.
[doublepost=1538802055][/doublepost]

hey! is it possible to run MacOS Mojave on PowerPC Macs?

Maybe in Qemu

 

[baronerosso]

@baronerosso I have read before your edited message, if you have APFS Container on disk1 and so APFS Recovery Volume on disk2s3, I guess to use the CMD+R recovery feature you should have the APFS container on disk0 , however if you don't have an HFS partition with another Recovery on disk1, it will work even on APFS container on disk2, disk3 and so on.

If you get Prohibitory Symbol holding CMD+R at power-on, probably your current Recovery (located on disk1s2 or disk1s3) points to the HFS file system one, for HFS Recovery see my previous post, you can mount your HFS Recovery from Mojave, once inside rename the PlatformSupport.plist to something as PlatformSupportbackup and overwrite the prelinkedkernel (without renaming into immutablekernel this is a requirement only for APFS), and you can boot from the HFS Recovery.

edit:
I don't remember exactly your message so probably the 50% of what I wrote now are foolishness.

well, no way.

It’s not important, I have the USB installer working fine.

These are my diskutil lists

I have APFS disk randomly on disk2 and disk1
I think, maybe is the BaseSystem.dmg vanilla inside the Recovery partition , not patched, who deny the boot.

 

[jackluke]

well, no way.

It’s not important, I have the USB installer working fine.

These are my diskutil lists

I have APFS disk randomly on disk2 and disk1
I think, maybe is the BaseSystem.dmg vanilla inside the Recovery partition , not patched, who deny the boot.

No, BaseSystem.dmg doesn't need to be patched the Mojave one works great, however you have an unusual APFS scheme, normally after the APFS Container disk0s2 should follow the APFS scheme on disk1sY , instead you have on disk2sY, but you have an HFS partition in the middle and two EFI partition, one on disk0s1 and another on disk1s1, because I suppose you have two hard disk inside your mac, anyway try open system preferences startup disk, select your Mojave APFS and click restart then try to press CMD+R, otherwise send a screenshot of your disk2s3 mounted opened on Finder, or simply try to unplug the disk1 that contains the HFS and the duplicate internal EFI.

 

[fintematic]

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.

Hi man, i tried to follow your tutorial, but after i mounted Recovery, when i wrote: open /Volumes/Recovery , it said open: command not found

 

[jackluke]

Hi man, i tried to follow your tutorial, but after i mounted Recovery, when i wrote: open /Volumes/Recovery , it said open: command not found

??? Try type this: /usr/bin/open /Volumes/Recovery

 

[fintematic]

??? Try type this: /usr/bin/open /Volumes/Recovery

It says:
/usr/bin/open: No such file or directory

 

[baronerosso]

No, BaseSystem.dmg doesn't need to be patched the Mojave one works great, however you have an unusual APFS scheme, normally after the APFS Container disk0s2 should follow the APFS scheme on disk1sY , instead you have on disk2sY, but you have an HFS partition in the middle and two EFI partition, one on disk0s1 and another on disk1s1, because I suppose you have two hard disk inside your mac, anyway try open system preferences startup disk, select your Mojave APFS and click restart then try to press CMD+R, otherwise send a screenshot of your disk2s3 mounted opened on Finder, or simply try to unplug the disk1 that contains the HFS and the duplicate internal EFI.

Yes, I have 2 physical disks, my Mac is a MacMini Server.

Try booting Recovery after startup disk selection in system preferences ... no way

this is my Recovery partition

 

[jackluke]

Does anyone know what the Telemetry plugin is used for? What data is Apple collecting with it?

I believe it handles with the "Security & Privacy" prefane --- "privacy" tab --- "Diagnostics & Usage" functions.
[doublepost=1538814553][/doublepost]

Yes, I have 2 physical disks, my Mac is a MacMini Server.

Try booting Recovery after startup disk selection in system preferences ... no way

this is my Recovery partition

It appears ok, could you try to boot holding CMD+V+R (a verbose mode Recovery) and see what's behind the prohibitory symbol ?

Anyway, try to copy also the prelinkedkernel (without renaming) inside your Recovery from your /Mojave/System/Library/PrelinkedKernels , even if only immutablekernel is tipically required for APFS Recovery.

 

[fintematic]

M

It says:
/usr/bin/open: No such file or directory

My error sorry
I don’t know why i was thinking to do these operations from usb drive with macOS installer...

 

[jackluke]

It says:
/usr/bin/open: No such file or directory

It seems you don't have the "open" unix command, try to copy from another macOS, you can use any, HighSierra or any.

 

[fintematic]

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 did all the steps, but when i reboot with CMD+R, i get prohibitory logo

 

[jackluke]

I did all the steps, but when i reboot with CMD+R, i get prohibitory logo

Try to follow the same advise I given to @baronerosso :

after power-on hold CMD+V+R (a verbose mode Recovery) and see what's behind the prohibitory symbol.

Or try to copy also the prelinkedkernel (without renaming) inside your Recovery from your /Mojave/System/Library/PrelinkedKernels , leaving also the immutablekernel (the renamed one) that is tipically only required for APFS Recovery.

 

[fintematic]

Try to follow the same advise I given to @baronerosso :

after power-on hold CMD+V+R (a verbose mode Recovery) and see what's behind the prohibitory symbol.

Or try to copy also the prelinkedkernel (without renaming) inside your Recovery from your /Mojave/System/Library/PrelinkedKernels , leaving also the immutablekernel (the renamed one) that is tipically only required for APFS Recovery.

also with prelinkedkernel i get prohibitory symbol. With CMD+V+R nothing is happening, it boot normally.

 

[jackluke]

also with prelinkedkernel i get prohibitory symbol. With CMD+V+R nothing is happening, it boot normally.

Then boot from USB Mojave Installer, open Terminal and type:
csrutil disable
nvram boot-args="-no_compat_check -v"
reboot

hold CMD+R, you should see a Recovery Verbose now, or with enough luck should boot the APFS Recovery.

 

[fintematic]

Then boot from USB Mojave Installer, open Terminal and type:
csrutil disable
nvram boot-args="-no_compat_check -v"
reboot

hold CMD+R, you should see a Recovery Verbose now, or with enough luck should boot the APFS Recovery.

I tried and this is what i get:

And now it boot in verbose mode, how can i return to normale boot?
Edit: i googled and found solution to normal boot

 

[jackluke]

I tried and this is what i get:

View attachment 792547

And now it boot in verbose mode, how can i return to normale boot?
Edit: i googled and found solution to normal boot

The file.DMG and boot.efi path are wrong (it's NOT the APFS Recovery), it seems to point to another partition as main Mojave disk or Preboot or whatever else, that's why you and @baronerosso are having issues on booting the APFS Recovery, I guess on the next Mojave update 10.14.1 or 10.14.2 it will be fixed automatically or by reinstalling Mojave, and then you have to repeat my early steps to "fix" the APFS Recovery editing those 3 files and so on.

I don't know yet how to correctly re-bless the APFS scheme, so only updating Mojave could fix it.

Yes, to boot normal apple logo mode, just drop "-v" from nvram-boot-args.

edit:
I guess your screenshot could represent a call for an "Internet Online Recovery" that will fail of course because of Mojave on unsupported mac, I bet a Mojave reinstallation or version update will auto fix that bringing back the "offline Recovery".

 

[fintematic]

The file.DMG and boot.efi path are wrong (it's NOT the APFS Recovery one), it seems to point to another partition as main Mojave disk or Preboot or whatever else, that's why you and @baronerosso are having issues on booting the APFS Recovery, I guess on the next Mojave update 10.14.1 or 10.14.2 it will be fixed automatically or by reinstalling Mojave, and then you have to repeat my early steps to "fix" the APFS Recovery editing those 3 files and so on.

I don't know yet how to correctly re-bless the APFS scheme, so only updating Mojave could fix it.

Yes, to boot normal apple logo mode, just drop "-v" from nvram-boot-args.

Ah ok, thank you man!

 

[0403979]

Patching recovery mode will not allow you to reinstall macOS. Only use the utilities.

 

[jackluke]

Patching recovery mode will not allow you to reinstall macOS. Only use the utilities.

Yes, mostly because the macOS recoveries do a check through Internet on machine before allow to download the Installer (again) into the disk, maybe this check is patchable too, but then would remain a non-patched Installer with dangerous firmware.pkg inside (and without Post-Install), so both the HFS and APFS Recovery are just for Utilities fun, anyway from a Recovery Terminal can do a lot of things, even a partial manual patching of Mojave.