I've done this about 50ish times, and never has a convert to APFS ever worked for me. I always have to convert to APFS, then run the full installer, THEN the patcher to install the patches. This will do an in-place upgrade which will preserve your files and settings. In all the times I've done it, I have never lost any data, just the time needed to run through the full installer.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I've done this about 50ish times, and never has a convert to APFS ever worked for me. I always have to convert to APFS, then run the full installer, THEN the patcher to install the patches. This will do an in-place upgrade which will preserve your files and settings. In all the times I've done it, I have never lost any data, just the time needed to run through the full installer.
He may have temporarily removed it or it because your iMac 11,1 doesn't boot APFS natively so I am asking about the APFS Firmware update patch that may be less risky the the APFS Rom Patcher and are you using the latest Mojave patcher which is 1.3.5
Maybe this is the the solution, there are so many ways to "Rome".
I'll try it out.
Thank You.
[automerge]1572908593[/automerge]
Does that mean, that after the described procedure you will be able to use your HFS backup on the created APFS partition?
Last edited:
Not from Time Machine or Disk Utility. You can restore an HFS to APFS via Carbon Copy Cloner. I'd suggest immediately making a backup once the machine is booting APFS normally and using that as your baseline going forward if you want to continue to use APFS.
You've done it 50 times successfully and it has never worked for you??? I might be wrong but there seems to be a bit of ambiguity.
this is the reply from Dosdude No need, just install High Sierra on the machine, or the official APFS firmware update package linked on the Catalina Patcher webpage
Did you read the entire post? On a working 10.14 HFS load, booting to a USB installer and converting to APFS after unmounting the partition works insofar as the process completes with no errors. But once you reboot, the machine will NOT boot on it’s own once converted to APFS. Simply performing an in-place upgrade from the USB patcher drive fixes whatever issue the conversion to APFS created, so you will now have an APFS formatted drive with all of your original data and settings intact.
- APFS BootROM Support: If you have a machine that supports High Sierra natively, you MUST ensure you have the latest version of the system's BootROM installed. If you have NOT previously installed High Sierra, you can download and install thispackage to install the latest BootROM version. When installing, ensure your system is plugged in to power, or the update will not be installed. this is taken from the macOS Catalina for unsupported Macs under Important info where the APFS Firmware update can be downloaded
I finally found the USB I used to install 10.14 and a restore from Time Machine is underway. Only 6 hours to go!
[automerge]1572920483[/automerge]
While I haven’t tried this, you may be able to do an upgrade install (ie don’t erase the drive) and recover. You will need the USB you used for the original install.Same for me (also MacBook 5.1)
(Except that I do not have a backup)
Last edited:
If your machine does not support APFS natively, of course it is not going to boot on it's own, this is expected and kind of a doh moment.
This is on machines that do support APFS booting. It’s a known issue at this point. Don’t believe me? Try to convert your working, booting HFS partition to APFS using disk utility. It will “successfully” convert you to APFS, but will no longer boot, even on machines *WITH* APFS support. Loading the APFS patch also does not fix the boot issue, only an over the top install leaving the data in place works, in my experience.
Just to make sure that we are on the same page, when I say "native APFS support", I mean native. I haven't tried it but I don't see how applying the APFS patch along with other patches and force cache rebuild would not make your system bootable. The only thing is that older systems for some reason require any bootable OS on HFS+volume attached at all times to your system while you are trying to boot a patched APFS volume. I never had any issues with that because I always multi boot my system and had HFS+ system attached at all times when dealing with patched APFS volumes.
Hi there!
Anyone having this problem where QuickTime Player 7 Pro does not open?
Log reads:
Termination Reason: DYLD, [0x2] Wrong architecture
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: no suitable image found. Did find:
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: stat() failed with errno=1
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture
Ran a DDG search and found out that SkyLight is the new CoreGraphicsServices framework. Does that ring a bell? I'm not sure where the issue lies, though.
The computer is a MacBook Pro 17" Late 2011 running 10.14.6 with the AMD Radeon deactivated since it crapped out years ago.
Thanks in advance!
Anyone having this problem where QuickTime Player 7 Pro does not open?
Log reads:
Termination Reason: DYLD, [0x2] Wrong architecture
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: no suitable image found. Did find:
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: stat() failed with errno=1
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture
Ran a DDG search and found out that SkyLight is the new CoreGraphicsServices framework. Does that ring a bell? I'm not sure where the issue lies, though.
The computer is a MacBook Pro 17" Late 2011 running 10.14.6 with the AMD Radeon deactivated since it crapped out years ago.
Thanks in advance!
Install the latest Legacy Video Card Patch, available through Patch Updater.
I have Mojave installed, not High Sierra, isn't it dangerous to install this OfficialAPFSFWUpdate? And what is it good for?
I updated to the latest security update via updater then patched the system but I ended up with various issues. One was that I could not configure certain things due to Intel video card. Mackbook Air 4.2 2011. renistalled previous Mojave with latest patcher. What is the best way to update to larest security patch please?
Thank you, that did it. The MacBook Pro gets stalled when trying to reboot or shutdown but it sorted it out anyway.
I am having a issue with my macpro3-1 it hung after the video card patch that came from the autoupdater. It had be flawless before. I had to reinstall dosdudes Mojave and now I get random reboots. I have search the system log and can find nothing on shutdown or cause.
Seeing that latest version Patch Updater is 1.3.5, while mine, created quite recently, 10/20, from directions at http://dosdude1.com/mojave/ is at v1.2.0. Have installed latest Legacy Video Card Patches from this (quite grateful for these, as prior to that dark mode was often showing unreadable black text on black text, among other dark mode issues, and now with light mode fully restored everything appears quite readable), and PU shows no new patches pending. Everything appears to be working properly.
Possible explanation for why I got this old version? Is it because of the Mac version patched, in my case, iMac 10,1?
Any problems or issues continuing to use this quite old version? Not seeing anything obvious, but is there any way to update to the 1.3.5, and should I if it is even possible?
Possible explanation for why I got this old version? Is it because of the Mac version patched, in my case, iMac 10,1?
Any problems or issues continuing to use this quite old version? Not seeing anything obvious, but is there any way to update to the 1.3.5, and should I if it is even possible?
Last edited:
AFAIK 1.2.0 doesn't support recent versions of Mojave. You should create a new usb installer with the latest patcher
That's what I would assume, just intuitively. However, just to be on the safe side, I already created a new USB Installer just last weekend, from which I successfully installed Mojave on a small, new partition, only as a test -- not the HFS+ and APFS volumes on other partitions already in use. (Also used that new usb installer to deal with after effects of Sec Update2019, and to install latest Video Card patches on those 2 main volumes.)
That new test partition with a new 10.14.6 also shows the Patch Updater.app at v1.2.0. Not sure where to go from here.
Last edited:
what the APFS Firmware does is make it so you can boot in APFS I don't know exactly what the APFS patch does but it does have scrolling text at boot up which is from the patch and goes quickly but if you can boot into macOS Mojave APFS then you don't need to apply the apfs patch from the post install I have actually installed the APFS Firmware patch and it does take awhile but no issues but nothing is guaranteed
[automerge]1572976307[/automerge]
the Lin to the newest Mojave patcher is on the first page of this thread
[automerge]1572976398[/automerge]
I believe you can click on skip this update from the patch updater or something close
[automerge]1572976501[/automerge]
You can reinstall macOS Mojave over your existing Mojave without losing you data or apps or settings then apply the post install patches and make sure you are using the latest macOS Mojave patcher 1.3.5