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 haven't figured out how to install from those update packages yet. As a side project I was hoping to figure out offline updates (like you used to be able to download combo updaters from the Apple website). If you modify a macOSUpd10.14.1.pkg's info file, you can get it to install... but it breaks the system, causing a KP at boot. Had to reinstall my OS.
Does anybody know how to install from those packages? I know it's a bit unrelated and not strictly necessary since we already have the software update patch, but it would be nice to be able to save each delta update.
Does anybody know how to install from those packages? I know it's a bit unrelated and not strictly necessary since we already have the software update patch, but it would be nice to be able to save each delta update.
I guess your main issue in updating depends from using still the HFS+ , while APFS is becoming mandatory to support future minor releases, however I've not yet installed but inspecting the macOSUpd10.14.1.pkg seems they changed the update structure scripts pre-post-install , so maybe some new fixes on the info file could be required.
Probably using a previous boot.efi or previous kernel file to continue support booting 10.14.1 beta from HFS+ is a good attempt.
edit:
Consider that all those who succeeded in updating to 10.14.1 beta are on Mojave APFS Volume.
OTA update means APFS, no escape.
Last edited:
Does anyone work on this graphic anomalies? I hate this black frame around the windows and this want to use the Light Menubar.
I have tried multiple times with OTA and APFS, I had to reinstall everytime. It never works.
Ok, I haven't tried yet to update on APFS macbook 2010, I'm avoiding beta steps, even if I really don't care, I could stay well 10.14.0 until 10.15 , however when 10.14.1 final release will roll out I'll do some tests too, meanwhile waiting for "who installed update on MBP 2010"'s feedback.
I'd not compare those who updated to 10.14.1 beta from machines equipped with i5/i7 cpus, because to me, apart the GPU, those are almost hardware/platform Mojave natively supported.
Last edited:
Yeah, you may be right. I'll try making a second partition (don't want to reinstall my primary OS again) and just directly extract/shove the package Payload over the root. Maybe that will work, even on HFS+. I really don't want to upgrade to APFS.
Worst case scenario, I can just fetch the whole 10.14.1 InstallESD when the public release comes out. I'm sure that'll install over the previous version like all the earlier betas did.
Thanks @jackluke, always insightful
This is good to know. Now perhaps experts in this thread can figure out how to create a full install instead of OTA update/upgrade for the beta versions.
Mahalo @DaniloGeekDude
[doublepost=1539880151][/doublepost]
Now I understand from the i5/i7 quote above why I COULD install 10.14.1 betas on my MBAir4,2 but FAILED on my MBP5,3.
Mahalo @jackluke
Yeah, you may be right. I'll try making a second partition (don't want to reinstall my primary OS again) and just directly extract/shove the package Payload over the root. Maybe that will work, even on HFS+. I really don't want to upgrade to APFS.
Worst case scenario, I can just fetch the whole 10.14.1 InstallESD when the public release comes out. I'm sure that'll install over the previous version like all the earlier betas did.
Thanks @jackluke, always insightful
You're welcome, I think so, when the full 10.14.1 final InstallESD will be released updating should work as before.
I believe too that expanding the pkg over the root could do the trick, once I installed through a Recovery Terminal or single user mode an OSX update, I used this command and it worked:
sudo installer -verbose -pkg /Volumes/Label/path/package.pkg -target /Volumes/MacOSLabel
This works for a regular OSInstall.mpkg but not the updaters -- they fail unless you remove a key requires-distribution-check="true"... but if you do remove it and run the installation, it wrecks the OS and makes it KP very early in the boot process. I'll play around with this for a little longer and report back.
By the way don't forget that the cap must be polarized (watch out where (+) belongs and where ground)
[doublepost=1539888235][/doublepost]
Thank you very much, as always your help comes in a pickle with nobody else to help.
I hope the announced October 30 event marks the release of a new MacMini, a new MBA and 10.14.1 as a full installer release.
Big deal. Any new hardware from apple is outdated out of the box. You can get a much better PC for less. Also with each and every new iteration of Mojave it will become harder for those like us who try to run it on unsupported machines.
And now let's go further in time. Within the next 3-4 iterations macOS will be unified with iOS and will turn your aging, by then, mac into a locked box with no installation, or expansion capabilities. All apps, data, fotos, books, music, videos, documents will be stored in the mighty "iCloud" and you will keep paying for everything again and again and again. Basically forever. Nothing is going to be really yours. If you run out of money you still have managed to instal the latest unsupported iOS 10.18 with nothing else on it. So you can pass your time looking at the screen and admiring how in the unsupported machines (which lack support for metal 5) the Dark-Purple-Brown appearance (very modern by then) will have a slight silver-red lining around the frames.
Once you see the reality for what it is, it is impossible to get excited by news coming from Apple.
@dosdude1
as you suggested I have reinstalled the nightshift patch and rebooted. 3 times. Does not work.
I have the option in the screen section and can activate it but nothing happens. I used nightshiftenabler.app on sierra before the upgrade and that worked.
Your patch does "activate" the menu but without function for my iMac 7.1 - nightshiftenabler.app does not work since high sierra.
Hope you can figure it out. Or tell me what I need to do. Thank you!
as you suggested I have reinstalled the nightshift patch and rebooted. 3 times. Does not work.
I have the option in the screen section and can activate it but nothing happens. I used nightshiftenabler.app on sierra before the upgrade and that worked.
Your patch does "activate" the menu but without function for my iMac 7.1 - nightshiftenabler.app does not work since high sierra.
Hope you can figure it out. Or tell me what I need to do. Thank you!
Should working fine on non-Retina Display (I guess).
More nightshift patches you use one after another less they work, try this, it is the same file already fixed to be copied manually inside your Mojave path: already patched Mojave CoreBrightness Night Shift
Best fix right now is turning on reduced transperancy under Accessibility Options.
I think this is similar to an official hack/fix to get older machines going under Leopard (way back when).
Web surfing I have found somewhere another trick, that since El Capitan is possible to make overall font smoother from terminal with:
defaults write NSGlobalDomain AppleFontSmoothing -integer x
x represents a value number 0,1,2,3,4 from 0 lighter font smoothing to 4 stronger font smoothing
to return Mojave default font just type:
defaults delete NSGlobalDomain AppleFontSmoothing
It might just be my imagination but I think this worked some what.
Hi my 12,2 iMac got the graphics card problems, and I try to erase and reinstall to high Sierra , I can’t install high Sierra it keeps error and tell me press d diagnoses please help
My Model number is iMac9,1 and I am using Unsupported Sierra dosdune1 method for a year. Even with this normally we cant download Mojave from Appstore its always given an error "This model iMac does not support new OS". But couple of minutes ago suddenly Mojave installer appeared on my application folder. What? How the hell this happened?
I opened AppStore for check and Mojave really looks installed. What the F?
I opened AppStore for check and Mojave really looks installed. What the F?
Is the same that: defaults -currentHost write -globalDomain AppleFontSmoothing -int x???
[doublepost=1539967380][/doublepost]
But, is someone working to fix this? Thanks
Essentially yes, should be another form to achieve the same environment variable.
And yes2, @pkouame is working on github to "fix" that giving a better appearance to the "light mode".
[doublepost=1539968131][/doublepost]
That's funny but don't install from there, use instead the Mojave Patcher to prepare an USB Installer from that path, the dosdude1 tool should recognize that path "Applications/Install macOS Mojave.app" to fetch the packages to be patched.
Off course thanks to warning. I just wondering can I update with the USB Installer cause I dont want to make clean install? is that possible update without formating with USB Installer?
Edit: I wacthed the video and that is possible thank you.
Last edited: