macOS 10.14 Mojave on Unsupported Macs Thread

[DaniloGeekDude]

You need to use a usb thumb driver to install the patcher
[doublepost=1541210243][/doublepost]10.14.2 beta installed successfully on my mid 2009 iMac using patcher 1.2.3

@TimothyR734 , Can you please list the steps you did for successful upgrade to 10.14.2 Beta? OTA and Patch does not work for my Core 2 Duo MBP5,3. What is the processor for your mid 2009 iMac?

Thank You.

EDIT: I am in the Developer's Seed Program BTW. Did a software update check, and it did show that 10.14.2 Developer-Beta was available to download.

 

[Sveto]

Premise that I appreciate very much what @pkouame has done with his Hybrid Mode patch, and I hope he will continue to improve that, @ASentientBot you know I respect you, but let me argument my reasons:

1) Restoring a BaseSystem.dmg requires at least 2 GB of disk space, while stock APFS Recovery is less than 600 MB, and restoring a BaseSystem.dmg (especially the HS one) requires a re-partitioning altering a bit the APFS scheme/container transforming it into an hybrid HFS/APFS;

2) Every BaseSystem.dmg (USB Installers included) is an HFS partition, while the stock APFS Recovery is a native bootable APFS partition;

3) @Sveto stated that I'm doing wrong in typing posts about using intensively Terminal commands, but I see the "wise Sveto" doesn't told nothing about that using pkouame's patch is a bit complicated and invasive to apply through advanced Terminal commands and if done in wrong way it could make the system unbootable;

4) "John Doe" had fixed APFS Recovery, then "John Doe" decides to apply the pkouame's patch but does something wrong (not because of pkouame of course), so "John Doe"'s macOS will result unbootable, but booting back with CMD+R, from the APFS Recovery is fixable; and pkouame's patch is advisable to be applied through a Recovery;

5) @Balaur stated that he wants to patch less things possible on his main system, his thought is right and shareable by most, and I explain why:

- Recovery tools are always useful to troubleshooting in general the disks (and not only);
- Without using pkouame's patch, (thanks especially to @ASentientBot's earlier patches) almost everyone will have a perfect Mojave "dark mode";
- For the "light mode" reducing transparency/translucency is not a drama, I mean pkouame's patch doesn't bring more functionality to Mojave but only a better looking in "light mode", and (actually) cuts "top-menu" translucency into the "dark mode".

Oh.. boy @jackluke, I have never forbidden anything to anyone, dude. Please, read carefully my posts. I think I tend to write pretty clear. Don't look for aggression where it does not exist and maybe work a bit on the ego. Helping the others means to be able see from their perspective. I don't want to further repeat myself. It seems I won't get to you with any arguments. So if you find that Mojave is all about Recovery, be my guest and focus completely on Recovery. And since @pkouame's patch is just a simple repetition, just go slapping those terminal commands every time you boot, or make a script to do it for you at boot, whatever.

 

[imm0rtalz16_2006]

I have everything working perfect but it can't find/won't update to Mojave 10.14.1 I have and installed update patcher as well
[doublepost=1541219829][/doublepost]

@TimothyR734 , Can you please list the steps you did for successful upgrade to 10.14.2 Beta? OTA and Patch does not work for my Core 2 Duo MBP5,3. What is the processor for your mid 2009 iMac?

Thank You.

How did you get 10.14.2

 

[AphoticD]

Update on my MacBookPro8,1 a quick recap:

1. MBP not seeing APFS as a boot volume.
   
2. The MBP had never been upgraded past Lion. I installed an SSD and Mojave 10.14.1 (Unsupported) using the Patcher. Formatted the SSD as APFS, rebooted and the APFS volume does not appear at the Boot selector screen.
   

3. You need to have installed High Sierra on the system previously, so it's firmware is updated to support booting from APFS volumes. Otherwise, it won't detect the volume.

4. I created a High Sierra 10.13.6 (Supported) USB and installed onto the original HDD (HFS+). I ran all the latest security updates and allowed the firmware to update several times during the process.
5. I reinstalled the SSD which has Mojave 10.14.1 (Unsupported) installed (APFS) and the MBP refused to boot from it, showing the flashing system question mark.
6. I booted up from the High Sierra USB again and as per @jackluke , ran diskutil apfs updatePreboot disk1s1
7. After a reboot, the MBP can now see the volume as bootable, but instantly shows a circle with a line through it.

I mean probably something went wrong during your previous Mojave install, the VM partition was missing, you should had done other attempts before of re-installing all these legacy OSXs.

How would I go about adding the missing VM partition?

Thanks

 

[Sveto]

Hybrid Mode update for 10.14.1

• v1.2 which supports 10.14.1 is out here
• Read the OP with screenshots, notes, docs and instructions carefully here
• Read the "Who This Is For" section to understand its features, shortcomings and trade-offs
• Post any issues in the repo

Hope this helps some of you.

Thank you very much for the fast update.

 

[imm0rtalz16_2006]

How do I do this for mojave patcher

 

[AphoticD]

How would I go about adding the missing VM partition?

NM, I was able to add the VM volume with;

diskutil apfs addVolume disk1 apfs VM -role V -mountpoint /private/var/vm

But it didn't help, the volume is still unbootable (line with circle through it). I'll have to recreate the Mojave USB and try installing again.

 

[dosdude1]

NM, I was able to add the VM volume with;

diskutil apfs addVolume disk1 apfs VM -role V -mountpoint /private/var/vm

But it didn't help, the volume is still unbootable (line with circle through it). I'll have to recreate the Mojave USB and try installing again.

Yeah, you'll need to do a re-install. Just ensure the system is on the latest BootROM version beforehand (if a firmware update was installed when install High Sierra, chances are it is). Also ensure you're fully erasing the drive as APFS, by clicking "View", and "Show All Devices" in Disk Utility, and from there selecting the root drive in the sidebar, and then selecting the Erase option.

 

[DaniloGeekDude]

How do I do this for mojave patcher

If you are updating from 10.14 to 10.14.1 GM, then here's the steps.

1. Download @dosdude1's Mojave Patcher 1.2.3 from his website
2. From his patcher app, run tools | download Mojave.
3. Create a USB (at least 16gb) boot drive.

His instructions are in his website. Good luck.

 

[TimothyR734]

@TimothyR734 , Can you please list the steps you did for successful upgrade to 10.14.2 Beta? OTA and Patch does not work for my Core 2 Duo MBP5,3. What is the processor for your mid 2009 iMac?

Thank You.

EDIT: I am in the Developer's Seed Program BTW. Did a software update check, and it did show that 10.14.2 Developer-Beta was available to download.

I am in the developers beta program too downloaded the update OTA then applied the patches with macOS Patcher 1.2.3

 

[Macbookprodude]

Has anyone gotten acceleration to work ?

 

[L Caputo]

H

Yeah, you'll need to do a re-install. Just ensure the system is on the latest BootROM version beforehand (if a firmware update was installed when install High Sierra, chances are it is). Also ensure you're fully erasing the drive as APFS, by clicking "View", and "Show All Devices" in Disk Utility, and from there selecting the root drive in the sidebar, and then selecting the Erase option.

I got a Mac Pro 3.1 new SSD formatted as APFS, installed High Sierra 10.13.6, did all the patches. When restarting will show the APFS verbose screen, but then boots to Sierra install on another disk.
If I remove other disks in Mac Pro leaving only the SSD it will then boot to High Sierra no problem.
Anything I can do to improve the situation, is this something others are facing.
Have done an SMC reset. No joy.

Thanks

 

[olad]

Does anyone else see there Network locked to DNS addresses, which can't be changed? I went to System Preferences>Network>Advanced>DNS and the minus was shaded out, and the plus allowed to enter DNS but it doesn't take.

Perhaps you didn't click the 'Apply' button... If you did, then it's another problem entirely.
[doublepost=1541233744][/doublepost]

Oh.. boy @jackluke, I have never forbidden anything to anyone, dude. Please, read carefully my posts. I think I tend to write pretty clear. Don't look for aggression where it does not exist and maybe work a bit on the ego. Helping the others means to be able see from their perspective. I don't want to further repeat myself. It seems I won't get to you with any arguments. So if you find that Mojave is all about Recovery, be my guest and focus completely on Recovery. And since @pkouame's patch is just a simple repetition, just go slapping those terminal commands every time you boot, or make a script to do it for you at boot, whatever.

@Sveto; @jackluke... hey guys, step back a little and let up. words like 'aggression' and 'ego' are unnecessary. Points have been made. No need to continue.

 

[jackluke]

NM, I was able to add the VM volume with;

diskutil apfs addVolume disk1 apfs VM -role V -mountpoint /private/var/vm

But it didn't help, the volume is still unbootable (line with circle through it). I'll have to recreate the Mojave USB and try installing again.

To avoid the "line with circle", just enforce your compatibility platform check, the most strong to override everything is booting from any USB macOS Installer (higher than El Capitan), open Terminal and type:
nvram boot-args="-no_compat_check"

 

[jackluke]

Oh.. boy @jackluke, I have never forbidden anything to anyone, dude. Please, read carefully my posts. I think I tend to write pretty clear. Don't look for aggression where it does not exist and maybe work a bit on the ego. Helping the others means to be able see from their perspective. I don't want to further repeat myself. It seems I won't get to you with any arguments. So if you find that Mojave is all about Recovery, be my guest and focus completely on Recovery. And since @pkouame's patch is just a simple repetition, just go slapping those terminal commands every time you boot, or make a script to do it for you at boot, whatever.

"Slapping" at every boot what ? The APFS Recovery fix once applied has the same durability of any minor/major upgrade, as on any macOS upgrade you have to re-do manual patching or Post-Install (and also re-do pkouame's patch) then together with the macOS upgrade the APFS Recovery is being updated to a new kernel so needs a re-do (following exactly the same procedure as I wrote earlier), that's it.

Sorry @olad, I can't help myself.

edit:
And answering to another your previous "challenge" reply, I have found a way to re-install macOS (only the last supported machine version ex. El Capitan or High Sierra) from the APFS Recovery on unsupported mac, but thanks to unsupporting replies I read, I think won't share that, I will keep only for personal use. Because APFS Recovery is useless.

 

[jon8214]

Hi guys, I think I may have messed up here, I had 10.14 installed on my MB5,2 and I updated the drive to APFS but now It won't boot and all I get is a load of script running on the screen then it boots into the usb drive, anyone any idea?

 

[Skorpion24]

Hello I managed to put Mojave with the dosdude tool on my 2009 24"iMac with Nvidia 120GT GPU, everything is fine except for the screen brightness, looks like it's not full dim when at the max setting and when changing the brightness it's like I got only 2 steps of dim instead every square doing a little more or less light.
What it can be? Drivers?

Btw, I didn't do a clean install but I just updated from El Capitan maybe this wasn't the right way and could have caused the issue.

 

[webg3]

Hybrid Mode update for 10.14.1

• v1.2 which supports 10.14.1 is out here
• Read the OP with screenshots, notes, docs and instructions carefully here
• Read the "Who This Is For" section to understand its features, shortcomings and trade-offs
• Post any issues in the repo

Hope this helps some of you.

It's perfect as always.
I'm using Flat mode, it's very beautiful.

Thanks man

 

[jackluke]

Or use Clover with the APFS UEFI driver.

Clover is an amazing bootloader but only to use on UEFI/BIOS PCs or at most inside a Mac's VirtualBox/VM , but absolutely not advisable on real Macs, it can seriously destroy the EFI/SMC Chips.

 

[ivankuraev]

@TimonCello your mbp is work? Read post #10054

 

[joelw135]

Perhaps you didn't click the 'Apply' button... If you did, then it's another problem entirely.

I am concerned that I was hacked, on both of my patched Mac's. I am unable to delete these DNS and add my own. The minus is grayed out.

 

[0403979]

I am concerned that I was hacked, on both of my patched Mac's. I am unable to delete these DNS and add my own. The minus is grayed out.

I think these are related to your internet, wifi, and ethernet. You must have at least one DNS server otherwise you won't be able to use the internet.

 

[joelw135]

I think these are related to your internet, wifi, and ethernet. You must have at least one DNS server otherwise you won't be able to use the internet.

Yes, but I should be able to replace the ones I have with ones of my own. I my regular Mac not patched I have changed them many times. These settings are locked. Would you please check your settings and see if the minus on the bottom is not grayed out like mine.

UPDATE: I deleted all my network setting and flushed it. Then started from scratch and applied new DNS. I also blocked access to these DNS addresses. I will watch it as I have put FING on alert.

 

[0403979]

Yes, but I should be able to replace the ones I have with ones of my own. I my regular Mac not patched I have changed them many times. These settings are locked. Would you please check your settings and see if the minus on the bottom is not grayed out like mine.

UPDATE: I deleted all my network setting and flushed it. Then started from scratch and applied new DNS. I also blocked access to these DNS addresses. I will watch it as I have put FING on alert.

I'm not familiar with these kinds of things. I can't help you unfortunately. I did turn off my WiFi and they all disappeared though.
[doublepost=1541251895][/doublepost]I'm planning on a new release of Update Installer soon. I have some ideas but I'd like to know if anyone has any feature requests?

 

[joelw135]

I'm not familiar with these kinds of things. I can't help you unfortunately. I did turn off my WiFi and they all disappeared though.
[doublepost=1541251895][/doublepost]I'm planning on a new release of Update Installer soon. I have some ideas but I'd like to know if anyone has any feature requests?

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.