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
Yes you can, and you should save also 3,5 GB of disk space doing that.
I don't use that patch so I don't know the ghost "EFI Boot" from which depend.
From what I see, you should copy the Payload's Content over your root Mojave Volume, I mean all the Payload Content must overwrite your root directories, but if you are booting from your Mojave Volume I doubt you can copy everything over it, the current volume is mounted and locked by many processes, so I guess you should do that booting from another Volume or from an USB Installer.
Last edited:
I deleted the files created this morning when I started this. Then started again and the system went into a loop and I am reinstalling Mojave. So I am not sure if I should try it again before I restore using Time Machine.
Just reinstall and try the commands again, something must have just gone wrong with your specific case.
[doublepost=1540660218][/doublepost]
Nope, I did it while booted.
The script is adjusted correctly, before you missed into the "copy part" the /Payload/ path, that's why them haven't upgraded, now should be fine, however I still have a doubt that doing booting from the current Mojave 100% of the files won't be overwritten. I'd have done from another unlocked Volume, it should work anyway.
That is a known glitch but only a cosmetic one. From within the Startup Disk panel, the APFS volumes only appear once as expected.
@joelw135 from your previous picture (this APFS scheme diskutil), I saw you have a regular APFS scheme, that's it should be to anyone, could you try this typing from Mojave Terminal:
sudo nvram boot-args="-no_compat_check -v"
then reboot and after the power-on chime hold and keep CMD+R , and post a picture of what you see at screen, it's a verbose diagnostic part for the APFS Recovery so I can inspect why don't work to others.
After you took the picture reboot to your Mojave and don't worry you will have all verbose lines, it's normal to return standard apple logo progress bar type this from Terminal:
sudo nvram boot-args="-no_compat_check"
sudo nvram boot-args="-no_compat_check -v"
then reboot and after the power-on chime hold and keep CMD+R , and post a picture of what you see at screen, it's a verbose diagnostic part for the APFS Recovery so I can inspect why don't work to others.
After you took the picture reboot to your Mojave and don't worry you will have all verbose lines, it's normal to return standard apple logo progress bar type this from Terminal:
sudo nvram boot-args="-no_compat_check"
Last edited:
Wow, almost exactly what I suggested!
I never got around to trying it. Now I maybe will. Good work!How to Install 10.14.1 without Installing a Firmware Update
To skip firmware updates on 10.14.1, you can chose to manually copy the files over from the package to your drive. This can be done with these commands.
pkgutil --expand-full /Path/macOSUpd10.14.1.pkg /Path/macOSUpd10.14.1
yes | sudo cp -rf /Path/macOSUpd10.14.1/Payload/ /
Run those commands separately and replace /Path/ and be sure to patch after running the commands. The update can be downloaded from here.
To skip firmware updates on 10.14.1, you can chose to manually copy the files over from the package to your drive. This can be done with these commands.
pkgutil --expand-full /Path/macOSUpd10.14.1.pkg /Path/macOSUpd10.14.1
yes | sudo cp -rf /Path/macOSUpd10.14.1/Payload/ /
Run those commands separately and replace /Path/ and be sure to patch after running the commands. The update can be downloaded from here.
Last edited:
On my Mac Mini 3,1 the commands worked on the clean install I am going to attempt it on the MacBook Pro 7,1 once the OS is installed. Thank you for holding my hand during this update. It is very much appreciated.
You're welcome, this should work so I'll probably add all of it to a script. Downloading and installing.
That would make it much easier for future. if you are doing it soon I will be able to test on the MacBook Pro as it is still running restore from Time Machine.
Ok lemme hurry up with it, I can do this quicker if I skip the download thing, I'll do that for now, might add it later or make it seperate. It's pretty easier for packages tho. This will require sudo and SIP off.
I feel that overwriting / on a booted system is a bad idea. This might explain some of the unpredictable results that others got.
You might want to encourage booting from a ≤ HS partition and then installing to the Mojave partition.
The steps are correct but I meant only the "copy part" needed /Payload/ as copy source, as you re-written now it should be:
pkgutil --expand-full /Path/macOSUpd10.14.1.pkg /Path/macOSUpd10.14.1/Payload
yes | sudo cp -rf /Path/macOSUpd10.14.1/Payload/Payload/ /Volumes/MojaveLabel/
[doublepost=1540667679][/doublepost]
Probably that's why it worked updating 10.14.1 beta 5, since the Volume is partially locked some core system files can't be overwritten I guess neither with "sudo" and so previous versions (unix core binaries and frameworks mainly) are kept, then I guess that is an "incomplete working" update. However when full installESD will be available things should return as always.
Last edited:
Well . it did work for me on my Mac Mini using what Julian gave me the second time with payload in the command.
I know it worked, but on a newer post he re-wrote adding another /Payload/ folder as destination path for expanding packages, so to copy from that need to re-add the /Payload/Payload/ as copy source path.