macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

Seems for once like I'm the first to see a beta update (correct me if I'm wrong):

10.14.2 DP2 (18C38b)

Have you tried manual updating Mojave HFS from the full 10.14.1 InstallESD ?

Even if I guess there will be around 5 betas (from today other 3 betas remaining) on weekly basis for each minor upgrade, so for late November 10.14.2 final will be released. At this point I'd wait.

 

[TimothyR734]

Try to free up some space in your system disk. 7.74 GB free maybe not enough to uncompress and copy some files needed to build the installer

it is recommended that the usb stick is 16gb

 

[nekton1]

Many thanks for the more comprehensive list. This time it worked without the gpt error (screenshot).
So Mojave is installed on RAID0 successfully but diskutil shows it is still hfs (screenshot). If I run:

diskutil apfs convert disk4s2

Will it convert and boot OK? I am confused about your comment JHFS+ only in the second post

I am confused web3g by the following post. In your first post you said:

#10245
"Guys, It is running: Mojave 10.14.1 on RAID 0 and APFS file system, I followed some installation tips in the Brazilian forum (macmagazine) and it worked."

Now you are saying"

[doublepost=1541619969][/doublepost]

Many thanks for the more comprehensive list. This time it worked without the gpt error (screenshot).
So Mojave is installed on RAID0 successfully but diskutil shows it is still hfs (screenshot). If I run:

diskutil apfs convert disk4s2

Will it convert and boot OK? I am confused about your comment JHFS+ only in the second post

Seems not!

test$ diskutil apfs convert disk4s2

Converting the volume on disk4s2 to an APFS Volume on an APFS Container

Started APFS operation on disk4s2 Untitled

Converting HFS Volume to an APFS Container which will export one APFS Volume

The target is the Journaled HFS+ volume "Untitled" backed by the GPT partition disk4s2

The target is a macOS system disk

Exiting conversion operations with error code -69546

Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Tests-Mac-Pro:~ test$

I tried when booted from another disk and same message, so it seems not.

Mac-Pro:~ testnvme$ diskutil apfs convert disk4s2

Converting the volume on disk4s2 to an APFS Volume on an APFS Container

Started APFS operation on disk4s2 Untitled

Converting HFS Volume to an APFS Container which will export one APFS Volume

The target is the Journaled HFS+ volume "Untitled" backed by the GPT partition disk4s2

The target is a macOS system disk

Exiting conversion operations with error code -69546

Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Anyone know a workaround?

If not, maybe the post on page 410 that started this odyssey should be modified/deleted b/c it has been overtaken by changes made by Apple and is no longer 100% correct!

Mac-Pro:~ testnvme$

 

[scrub10rd]

You guys might find this interesting:
I have a Macbook5,2 with an SSD and Mojave is installed on an APFS partition. But its via software, not the hardware mod. However, I just got the update notification for 10.14.1 (currently on 10.14)

 

[Loyd-01a]

Just did an OTA to 10.14.2 DP2.
Thank you @dosdude1 and all !

 

[Reactorvisual]

Hello everyone,
I was unaware this thread existed until today. I installed a GTX 780m into my 2011 27 inch iMac in anticipation that 6970m wouldn't be supported in Mojave. I have booted Mojave with the GTX 780m installed, everything graphics related is functional. There is no audio natively or Airport without modifying kexts. I used AppleHDA and IO80211Family from 10.13.5. As usual there is no Backlight control or EFI boot screen.However doing this upgrade allows this iMac to drive a 4k display over one of the functional Thunderbolt ports.

View attachment 766059 View attachment 766060

what about the graphics acceleration in mojave? i installed same card and everything was lagging cause no drivers from nvidia or apple were available last chance I chacked.

 

[webg3]

I am confused web3g by the following post. In your first post you said:

#10245
"Guys, It is running: Mojave 10.14.1 on RAID 0 and APFS file system, I followed some installation tips in the Brazilian forum (macmagazine) and it worked."

Now you are saying"

At the beginning I tested it on APFS but you lose the updates because you will have to redo the process every time there is an update, so it is sensible to keep in HFS, but if you want to put it in APFS, follow that first post, go be created a hybrid (bootable sector in HFS and System in APFS)

 

[nekton1]

I thought Mojave updates NOW REQUIRE APFS, so it is possible this method to install on hfs+ RAID0 is a dead-end too.

At the beginning I tested it on APFS but you lose the updates because you will have to redo the process every time there is an update, so it is sensible to keep in HFS, but if you want to put it in APFS, follow that first post, go be created a hybrid (bootable sector in HFS and System in APFS)

 

[webg3]

I thought Mojave updates NOW REQUIRE APFS, so it is possible this method to install on hfs+ RAID0 is a dead-end too.

Not, by the dosdude1 patch it does not convert HFS + to APFS at the end, keeping Raid0 in HFS.

I do not know if it was clear.

To keep everything under control it is necessary not to convert to APFS.

Security updates will work normally, only in the large updates 10.14.2 we will have to recreate the pendrive, this is normal, you will not lose your data keep on HFS +

 

[steffend]

For everyone struggling with no brightness controls using a MacBook Pro with disabled AMD GPU:
I got brightness and sleep fully working in Mojave 10.14.1 by using the same trick as I always used since my dGPU has failed two years ago:
NVRAM trick to use Intel GPU as default without installing the application from the page, but instead copying all the AMD kexts to the System Root:
"MojaveInstall" is the USB drive created with the patcher tool.

sudo /Volumes/MojaveInstall/Applications/Utilities/macOS\ Post\ Install.app/Contents/Resources/legacyGPUPatch.sh "" /Volumes/MojaveInstall/Applications/Utilities/macOS\ Post\ Install.app/Contents/Resources

and afterwards following this guide.

If everything succeeds, the output of "kextstat |grep AMD" should look like this:

MacBook-Pro:~ Steffen$ kextstat |grep AMD
  136    2 0xffffff7f830a2000 0x122000   0x122000   com.apple.kext.AMDLegacySupport (1.6.6) B7ED5B85-C76E-33EF-BB44-33CA9D9042BB <124 13 12 8 6 5 3 1>
  153    0 0xffffff7f83263000 0x12e000   0x12e000   com.apple.kext.AMD6000Controller (1.6.6) 774DEC5B-95D1-3A18-B4D7-0469DAB59E23 <136 124 13 12 6 5 3 1>
  169    0 0xffffff7f83845000 0x22000    0x22000    com.apple.kext.AMDLegacyFramebuffer (1.6.6) C17741E6-97E9-3F0B-8EF8-533036EADFFD <136 124 13 12 8 6 5 3 1>
  189    0 0xffffff7f83a45000 0x568000   0x568000   com.apple.kext.AMDRadeonX3000 (1.6.6) 15040C17-BF99-32F1-85C5-7C0D409F1288 <188 175 124 13 8 6 5 3 1>

 

[cleopete]

That is a bad idea. The only officially walked-through way of installing 10.14.1 on unsupported machines is with a USB Stick, created by patcher 1.2.3. Doing it through OTA is like spitting on your own efforts and looking for trouble. Yet some insist on OTA and end up unable to boot, with white screens, or not being able to finish the update. Bad idea.
[doublepost=1541523860][/doublepost]

I can testify. Just did that and got stuck in an EFI boot loop. After running the post install patch and forcing a cache rebuild, I got the apple splash screen and the bar made it all the way to the end...and has been sitting there ever since.

Setting up a new USB stick now, hope it lets me install it again, otherwise I'm looking at a lot of app re-installs!

Pretty sure the OTAs worked fine with patched High Sierra? Oh well, lucky to be able to update this 9 year old laptop at all I guess!

 

[TimothyR734]

Successfully installed 10.14.2 beta 2 with hybridcoreUI 1.3

 

[esculapio1]

Thanks to dosdude1! Transition to 10.14.1 went great!
I did a clean install as I upgraded the SSD.

View attachment 802160

Hey avz, how your laptop working?. Does it feel sluggish or slow?. How are the graphics?
Thanks.

 

[nekton1]

Thanks for this.

Not, by the dosdude1 patch it does not convert HFS + to APFS at the end, keeping Raid0 in HFS.

I do not know if it was clear.

To keep everything under control it is necessary not to convert to APFS.

Security updates will work normally, only in the large updates 10.14.2 we will have to recreate the pendrive, this is normal, you will not lose your data keep on HFS +

 

[highvoltage12v]

what about the graphics acceleration in mojave? i installed same card and everything was lagging cause no drivers from nvidia or apple were available last chance I chacked.

Probably because when you ran the patcher you accidentally selected "video card patch". You cannot use the patched ioaccelerator2 kext with a supported card format or manually extracteinstall the correct kexts.

 

[DaniloGeekDude]

10.14.2 Beta 1 to 10.14.2 Beta 2 update

Successfully updated OTA and Mojave Patcher | MacOS Post Install.



Must have been hundreds of times that I attempted to updates of betas on my Mojave unsupported Macs. Failed several times but succeeded when I specifically followed the following steps.

1. System Preferences | Software Update, then click on "update now". (goes without saying ... must be on developers or public beta program)
2. It will reboot and then show "installing software update ...xx minutes remaining)
3. When finishing step 2, it will again reboot. Now the next step (4) is important.
4. Option-Key and boot to "Mojave Patcher" 1.2.3 thumb drive.
5. run MacOS Post Install. Check on "Force Rebuild Cache" and then reboot.
6. It will boot with the message "Finishing Update" on black screen.
7. Then you are done!

Hope these detailed steps are helpful.

 

[dharnidhar]

Hello. Just saw this so apologies for not responding promptly.

Saw on your screen shot that your Mac (what model is it?) is on public beta. My Macs are on the developer's seed program. But your public one should work. First of all, the boot drive where your Mojave is installed should be in APFS format. If it is in HFS, it will not work. Here's the straight forward steps I did to upgrade mine.

1. Update via OTA (System Preferences | Software Update).
2. It will take a while. What I did to speed things up myself is run this in terminal (sudo softwareupdate -da). Doing so will download initially the the update packages. You'll see when it is done downloading.
3. Then go again to OTA and click Update. It should promptly tell you to restart.
4. Will show that it restarted and display message "installing updates or something similar"
5. After it is done, boot to the Mojave Patcher USB drive, and run Mac OS Post Install. Make sure to click on "force cache rebuild" prior to rebooting.

That's it. Good luck. Let us know how it goes.

Hi Danilo,

My machine is MacBook Pro (Late 2011). Yes, my boot drive is in HFS format. I am using my machine as a primary source for my R&D and have lot of data in it. I will take backup and reinstall it hopefully over the weekend and post an update.

Thanks once again for all your support and cooperation. Have a great day.

 

[Larsvonhier]

10.14.2 Beta 1 to 10.14.2 Beta 2 update

Successfully updated OTA and Mojave Patcher | MacOS Post Install.

View attachment 802325

Must have been hundreds of times that I attempted to updates of betas on my Mojave unsupported Macs. Failed several times but succeeded when I specifically followed the following steps.

1. System Preferences | Software Update, then click on "update now". (goes without saying ... must be on developers or public beta program)
2. It will reboot and then show "installing software update ...xx minutes remaining)
3. When finishing step 2, it will again reboot. Now the next step (4) is important.
4. Option-Key and boot to "Mojave Patcher" 1.2.3 thumb drive.
5. run MacOS Post Install. Check on "Force Rebuild Cache" and then reboot.
6. It will boot with the message "Finishing Update" on black screen.
7. Then you are done!

Hope these detailed steps are helpful.

Thanks a lot! This really works like a charm.
As a precaution of avoiding missing the 1st reboot-time I permanently held down the ALT key (for boot selection) by means of something sticked between key caps, see photo ;-)
When returning with a fresh coffee, I was greeted by the boot selector as intended...

 

[InXone]

Try to free up some space in your system disk. 7.74 GB free maybe not enough to uncompress and copy some files needed to build the installer

This was the problem! Thank you!

 

[Rubik]

For anyone having problems on an iMac 10,1 (Late 2009):

I did the OTA update and ended up in a boot loop. I then tried booting my patched USB thumb drive with 10.14.0 on it to run the Post-Install stuff, but the boot process would always get stuck at the progress bar, which eventually reaches 100% without anything happening further. I think some users described the same behavior on their machines on this thread before.
I then downloaded 10.14.1 using Mojave Patcher 1.2.3 and created a new thumb drive. This time it booted fine and I was able to run Post-Install which fixed everything and I can boot the machine normally again.

 

[webg3]

Successfully installed 10.14.2 beta 2 with hybridcoreUI 1.3

Can you send me a print of Dark Mode?

Thank you

 

[Mrtoto]

Hello,

Thanks all the team and ppl in this project ! A great work.

My Macbook pro 2011 13' Working like a charm on 10.14 and now 10.14.1.

OTA didn't worked because I missed to push "alt" at the first reboot (maybe this info must be in the first page ?)
Thx to those who notified this.

 

[kautame]

He's using an eGPU setup, so flashing is not necessary. The boot screen will be displayed using the internal GPU.

Just to be sure (and I can't try by myself because I'm still waiting for my Kepler card to arrive), with a Mojave compatible eGpu do I still need to apply the legacy video card patch on a 7,1 iMac?

 

[olad]

Had a 2009 MacBook Pro, running 10.14.1 nicely thanks to the patcher.

Got a new(er) 2012 MacBook Pro, running stock 10.14.1.

Put the 2009 in target disk mode, connected to the 2012 via FireWire, used Migration Assistant to move accounts & data to the 2012.

Apparently Migration Assistant grabbed all, or at least some of, the patched files. I get the "SIP is enabled" error dialog at login, and video and other systems seem a bit wonky. Is there an uninstall script I can run, to get rid of any patch cruft on the 2012?

Why didn't you just use SuperDuper! to clone your 2009 MBP and transfer that to the 2012 MBP? If the newer machine is on SSD, you can convert to APFS if it not that already, and you shouldn't need dosdude1's patch anymore. More experienced people on this thread may differ, but this is a simple method I have used myself.

 

[dharnidhar]

Hi Danilo,

My machine is MacBook Pro (Late 2011). Yes, my boot drive is in HFS format. I am using my machine as a primary source for my R&D and have lot of data in it. I will take backup and reinstall it hopefully over the weekend and post an update.

Thanks once again for all your support and cooperation. Have a great day.

Hi

Hi Danilo,

My machine is MacBook Pro (Late 2011). Yes, my boot drive is in HFS format. I am using my machine as a primary source for my R&D and have lot of data in it. I will take backup and reinstall it hopefully over the weekend and post an update.

Thanks once again for all your support and cooperation. Have a great day.

Hello Danilo,

1. sudo softwareupdate -da does not show any update, cannot see 10.14.2.
2. I tried converting from HFS to apfs using diskutil apfs convert disk1 command via terminal.app, it returns the error message 'Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Attached us the snapshot for your perusal. Thank you.