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
After having success in the past creating bootable installers for both Mojave and Catalina I was surprised today when I tried to create two new bootable installers for Mojave and Catalina using dosdudes Mojave and Catalina patcher apps.
Creating the installers results in an error while copying and patching the InstallESD.dmg.
Plenty of hard drive space, good quality USB (SanDisk), tried creating the installers on two copies of Mojave and one copy of Sierra.
Anyone else experiencing issues creating installers for these systems, its been a long time since I last tried so I was quite taken aback that trying both failed in the same area.
Thanks.
Creating the installers results in an error while copying and patching the InstallESD.dmg.
Plenty of hard drive space, good quality USB (SanDisk), tried creating the installers on two copies of Mojave and one copy of Sierra.
Anyone else experiencing issues creating installers for these systems, its been a long time since I last tried so I was quite taken aback that trying both failed in the same area.
Thanks.
Hi, try to format/rename the USB (MacOS Extended Journaled- GUID) pendrive as "OS X Base System" and redo the Installer creation.
Hi guys,
I have the MacBook Pro late 2011 17" with graphics AMD Radeon 6770M 1Gb and Intel HD X3000
I´ve tried for several weeks and several solutions to upgrade my macos 10.13.6 (High Sierra) to 10.14.6 (Mojave)
I´ve tried also the solution from dosdude1 and all the solutions didn´t work
I like to know how are the instructions to upgrade to Mojave 10.14.6
Can anyone help me?
Thanks people
I have the MacBook Pro late 2011 17" with graphics AMD Radeon 6770M 1Gb and Intel HD X3000
I´ve tried for several weeks and several solutions to upgrade my macos 10.13.6 (High Sierra) to 10.14.6 (Mojave)
I´ve tried also the solution from dosdude1 and all the solutions didn´t work
I like to know how are the instructions to upgrade to Mojave 10.14.6
Can anyone help me?
Thanks people
Last edited:
Hi @shotboy,
I have MBP 2011 15in w/AMD as well. My AMD is shot, and so I sent the MBP off to DosDude1 to bypass, and now it only uses Intel HD3000.
I am running Mojave on it now, and had no issues just following dosdude1's instruction pages. (Making an installer thumb-drive, and booting from it and installing from it.) In fact, I've tried Catalina, Big Sur, and Monterey on it as well, but with the HD3000 Mojave is the best compromise right now. (I have not checked lately to see if there has been any real progress for those other macOS with legacy (HD3000) GPU...but Mojave is pretty much rock-solid for me, and if you didn't know it was officially "unsupported" you wouldn't know from using it....)
I did have to disable SIP first, but I have been running my MBP 2011 since about 2017 with SIP disabled....even w/High Sierra, as I had had to do the FW work-around previouslyfor my AMD GPU that died, prior to sending it off to dosdude1 to do the HW bypass.
Can you elaborate on why/(Where in the process) it isn't working for you? It is difficult to help without more detail as to where the process it's failing for you...
I have MBP 2011 15in w/AMD as well. My AMD is shot, and so I sent the MBP off to DosDude1 to bypass, and now it only uses Intel HD3000.
I am running Mojave on it now, and had no issues just following dosdude1's instruction pages. (Making an installer thumb-drive, and booting from it and installing from it.) In fact, I've tried Catalina, Big Sur, and Monterey on it as well, but with the HD3000 Mojave is the best compromise right now. (I have not checked lately to see if there has been any real progress for those other macOS with legacy (HD3000) GPU...but Mojave is pretty much rock-solid for me, and if you didn't know it was officially "unsupported" you wouldn't know from using it....)
I did have to disable SIP first, but I have been running my MBP 2011 since about 2017 with SIP disabled....even w/High Sierra, as I had had to do the FW work-around previouslyfor my AMD GPU that died, prior to sending it off to dosdude1 to do the HW bypass.
Can you elaborate on why/(Where in the process) it isn't working for you? It is difficult to help without more detail as to where the process it's failing for you...
Hi @Finbarr Cnaipe
I follow your sugestion at Mar 11, 2019 Macbook Pro Early 2011, 8,2 03/11/2019 in the post: https://forums.macrumors.com/threads/macos-10-14-mojave-on-unsupported-macs-thread.2121473/page-507
and also the sugestion of luispuerto.net and it didn´t work
After reboot appears in verbose mode a long message: "......... this version of MacOs is not supported in this Platform"
After this I don´t know what to do
Is there other way by software to install Mojave in this MacBook Pro?
The only way to install the Mojave on my laptop must be a Hardware bypass?
I follow your sugestion at Mar 11, 2019 Macbook Pro Early 2011, 8,2 03/11/2019 in the post: https://forums.macrumors.com/threads/macos-10-14-mojave-on-unsupported-macs-thread.2121473/page-507
and also the sugestion of luispuerto.net and it didn´t work
After reboot appears in verbose mode a long message: "......... this version of MacOs is not supported in this Platform"
After this I don´t know what to do
Is there other way by software to install Mojave in this MacBook Pro?
The only way to install the Mojave on my laptop must be a Hardware bypass?
Last edited:
I think I know the problem....
Did you create your flash boot drive installer with the dosdude1 patcher tool? (Including using the dosdude1 tool to download the Mojave version from Apple and then using that download version via dosdude1's tool to create your flash boot drive installer?) It sounds like you are installing regular macOS Mojave flash boot drive installer, and not from the dosdude patch version created flash drive which disables the hardware checks.
Aside from the basics, my 03/2019 post earlier was about disabling the AMD 6000 with the EFI method as well as adding Continuity. Those two things are unrelated to the basic dosdude1 patcher installing a working macOS Mojave on the MBP....which is the part where you seem to be stuck. You're getting the unsupported OS/platform message, which seems to indicate you haven't gotten the dosdude1 flash drive to install/patch correctly.
If you still need to disable AMD GPU, you can do that...but if it were me, I would work on getting Mojave installed and working first (via dosdude flash drive creator), unless your AMD GPU is hosed and you need to fix that first in order to have a functioning display. If that is the case, you can just follow the method to enter the disable parmeter in EFI. As long as you don't reset the PRAM it will stick, allowing you to work with the machine until you can get all the other stuff done. Then you could look at the Luispuerto stuff to optimize. (If you are really stuck, you could ignore the advice to skip the dosdude1 GPU SW disabler, and just use that.)
[Oh, and I would make sure to be on the latest EFI Firmware version for your MBP. I upgraded mine last year because i missed it previously. The only way to do it on my MBP 2011 was to clean the drive, install High Sierra, run the OS, and then let Apple download and install all the latest High Sierra patches. In that process, one of the patches upgraded my EFI firmware to the latest version. Then I cleaned the drive again and did a clean Mojave install using the dosdude1 created Mojave installer flash drive. Finally, I should mention that I moved my MBP 2011 to APFS many years ago when I upgraded the HD to a SATA SSD....I've never looked back and it works great on my MBP 2011. If you have upgraded to a SSD for your main boot drive, I would highly recommend to format it as APFS...provided your EFI supports it. If not, I believe dosdude1 also has a patcher for that as well...although you can brick your MBP if you mess up the ROM flash....so please be careful.]
As I mentioned, sometime shortly after that 03/2019 post, I sent my MBP off to dosdude1 to permanently disable my AMD GPU in hardware. So I don't need to monkey with the EFI/Software AMD GPU disable any more. For Continuity, I'm not really using it, and also I switched to using LiLu and the ContinuityFix Kext method.
(At the time (2019), my MBP 2011 was my main travel/work notebook. Since then, I've upgraded to a 2020 16in i9 MBP as well as a 13in 2021 i7-quadcore MBP. I'm pretty much fully running Monterey now on those. So the 2011 MBP is now relegated to sitting in a docking station in my home-office-lab as a headless test device (via Apple Remote desktop/screensharing). It's running great w/Mojave, but I just don't have a core use for it anymore...it is just for testing these days...
See if the attached helps... It is the PDF I created in the summer of 2019 about my endeavors getting my MBP 2011 to run Mojave....
Last edited:
I have 2 SSD Samsung EVO 870 with APFS since the beginning for security and install them macos with a clean drive. One is configure with the latest macos 10.13.6 and I made all the updates and patches for High Sierra .It´s running as an external drive. The other SSD with APFS is to install Mojave and is running inside in the MBP 2011. The EFI support APFS because my High Sierra is run with it
Also I think that I have the latest ROM version of my MBP 2011 (ROM version 87.0.0.0 and SMC 1.70f6) because in some year Apple has changed the Versions Syntax of their ROM´s: before starting with MBPXXX.XXXX.XXX and now starting with XXX.X.X.X.X https://developer.apple.com/forums/thread/110339
Until know I only use the dosdude1 patcher 1.3.7 to download the Mojave version via dosdude1´s (Unless there is another Mojave version), create the flash boot drive installer with this Mojave version
After that I´ve been stuck with the unsupported OS/platform message by using the method of dosdude1
Is there any more recent dosdude1 patcher or other Mojave version?
Then I follow your post on 03/2019 until the Continuity Alternative Method:
One thing: what do you mean about the “latest CAT BETA “?
After that I´ve been stuck again with the unsupported OS/platform message
Must I also make the Continuity Alternative Method: ? And where can I find (or download) the Lilu.kext & BT4LEContinuityFixup.kext?
To disable SMC and reset pram/nvram I use the terminal from the flash boot drive installer or boot from High sierra external drive and make the changes with terminal inside /Volumes/MojaveSSD/.....
I can´t do the changes with Cmd+r+s Single User Recovery because the MBP 2011 stuck in the unsupported OS/platform message
Also I think that I have the latest ROM version of my MBP 2011 (ROM version 87.0.0.0 and SMC 1.70f6) because in some year Apple has changed the Versions Syntax of their ROM´s: before starting with MBPXXX.XXXX.XXX and now starting with XXX.X.X.X.X https://developer.apple.com/forums/thread/110339
Until know I only use the dosdude1 patcher 1.3.7 to download the Mojave version via dosdude1´s (Unless there is another Mojave version), create the flash boot drive installer with this Mojave version
After that I´ve been stuck with the unsupported OS/platform message by using the method of dosdude1
Is there any more recent dosdude1 patcher or other Mojave version?
Then I follow your post on 03/2019 until the Continuity Alternative Method:
One thing: what do you mean about the “latest CAT BETA “?
After that I´ve been stuck again with the unsupported OS/platform message
Must I also make the Continuity Alternative Method: ? And where can I find (or download) the Lilu.kext & BT4LEContinuityFixup.kext?
To disable SMC and reset pram/nvram I use the terminal from the flash boot drive installer or boot from High sierra external drive and make the changes with terminal inside /Volumes/MojaveSSD/.....
I can´t do the changes with Cmd+r+s Single User Recovery because the MBP 2011 stuck in the unsupported OS/platform message
Last edited:
Hi @shotboy,
Couple of things:
- yes, that is the same EFI FW rev I upgraded to, and AFAIK is the latest
- I'd worry about Continuity later, after getting Mojave installed and working.
- At the time (2019) CAT Beta was separate download from non-beta download. Don't know if that is still true today in 2022.
-
So to confirm:
1.) You created Mojave install flash thumb-drive using dosdude1 Mojave installer
2.) You've disconnected the external SSD
3.) You may need to erase the internal SSD so it is blank/fresh.
I would do this step first, but you can also do it prior to installing Mojave from the dosdude flash drive, after booting from the flash drive and then running disk utilities.
4.) At this point, the only drives connected are dosdude1 Mojave Install flash drive and internal blank SSD.
5.) Unless you've corrupted your EFI, at this point there is no reason to see any "unsupported platform" message. There is nothing "unsupported" connected, so no reason for that message. Only thing I can think of is that perhaps it is a PRAM/SMC issue, which should be able to be fixed by resetting both...
6.) Reset/clear PRAM and SMC (See apple support pages..)
Code:
As always you have to reset SMC
(https://support.apple.com/en-us/HT201295)
and PRAM/NVRAM (https://support.apple.com/en-us/HT204063)
before you do anything else.
SMC: shutdown, unplug everything except power,
now hold leftShift + Ctrl + Opt/Alt + Power for about 10sec and release at the same time.
PRAM/NVRAM: with the power cord on, power on and immediately before the
chime hold "cmd + Opt/Alt + P + R" at the same time and keep holding down until you hear the
chime for the second time.
Try to do the following step just right after, so you donʼt let the computer to
load —and fail.7.) Run EFI fix from terminal for disable GPU if needed.
boot into recovery single user mode by holding: cmd + R + S . When finish to load, you run
Code:
$ csrutil disable # to disable SIP
$ nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 # to disable the dGPU on boot.
$ nvram boot-args="-v" # Load in verbose mode
$ reboot8.) Make sure You've disabled SIP (see above - boot from flash drive -> terminal "csrutil disable")
9.) Next, You reboot MBP from dosdude1 Mojave install thumb flash drive. (hold down "opt" key while booting, select dosdude1 flash drive to boot. If you do not see the flash drive, then it is not created correctly). At this point, the state of PRAM and SMC should be cleared, and the dGPU disabled, but the MBP in otherwise "virgin" state, ready to use dosdude1 flash drive installer to install macOS Mojave for unsupported Macs.
10.) You open disk utilities from dosdude1 drive and reformat MBP internal SSD to new blank APFS. You may need to reformat to macOS journaled first, then immediately go to format as new APFS....in any case, I'd recommend an APFS partition and name it something like "MBP2011 HD".
11.) You exit disk utilities and run MacOS installer from dosdude1 installer thumb flash drive, installing to MBP internal SSD.
12.) Here is the part I can't remember....but: If MBP reboots at this point, do not reboot to to MBP internal SSD...reboot back to dosdude1 installer flash drive (holding down "opt" key during boot and making sure to pick the dosdude1 installer flash drive), and run dosdude1 patcher, selecting your MBP internal SSD to patch, and picking your MBP model for all the correct patch selections...when finished make sure to clear kext caches option, THEN reboot to macOS Mojave on SSD.
13.) Once successful, dosdude1 patcher will also be installed into macOS Mojave on your SSD, and will likely tell you there are new updates. Do those updates and reboot. Repeat as necessary until dosdude1 patcher says everything is up-to-date.
Hope this helps.
Finny
Last edited:
It Works !!! Thanks !!!
Now I know what went wrong.
The problem was the sequential steps. Before install Mojave, must reset/clear SMC NVRAM/PRAM, disable SIP and discrete GPU. After that install, reboot and install the patchers more the model MBP. Next reboot et voilá.
In the several places I didn´t find this order to install Mojave. Only found separated parts or instructions
After some automatic updates from Apple .... the MBP went to a black screen ....
What kind of updates must I use? Block updates from the Apple ?
The macos 10.14.6 can enable and run the discrete GPU AMD 6770M in this MBP 2011 with accelaration? What are the commands or software to run it (discrete GPU)?
Catalina macos can be install with the same steps and also run the GPU?
Now I know what went wrong.
The problem was the sequential steps. Before install Mojave, must reset/clear SMC NVRAM/PRAM, disable SIP and discrete GPU. After that install, reboot and install the patchers more the model MBP. Next reboot et voilá.
In the several places I didn´t find this order to install Mojave. Only found separated parts or instructions
After some automatic updates from Apple .... the MBP went to a black screen ....
What kind of updates must I use? Block updates from the Apple ?
The macos 10.14.6 can enable and run the discrete GPU AMD 6770M in this MBP 2011 with accelaration? What are the commands or software to run it (discrete GPU)?
Catalina macos can be install with the same steps and also run the GPU?
Last edited:
Hi @shotboy,
Glad it worked for you. I had suspected that the something was out-of-order in your steps to install... Glad I could help!
OK...now, for Apple Updates, I have found it necessary to:
1.) Allow Apple updates to occur as appropriate.
2.) After updates installed, do not reboot into macOS.
3.) Reboot to dosdude Flash thumb-drive installer, and re-apply the dosdude1 patches. (don't forget to also clear kext cache at end again).
4.) Then Reboot back to macOS.
I have found it to still be OK even in cases where I forgot and booted back to a black or grey screen. Just reboot from the dosdude1 flash drive, apply patches and you should be OK
I'm afraid you may also need to re-apply the dGPU disable process (nvram) as well if you need to disable the GPU. Anytime the PRAM get's reset, you will need to re-apply the nvram dGPU disable process.
I never tried to get acceleration for my AMD dGPU, because it was a bad/faulty dGPU....that is why I shipped my MBP off to dosdude1 to HW disable it. I got tired of having to re-apply the nvram dGPU disable process all the time. Now my MBP doesn't even know it exists...it only thinks it has the internal Intel HD3000. GPU.
Also, I'm afraid I cannot help much on Catalina, Big Sur, or Monterey. While I did try those, it was only once, and I was never able to get my MBP to work right like it does in Mojave....so I settled on Mojave for it. There are some big issues AFAIK supporting even the Intel HD3000 GPU on the legacy machine, and performance on my MBP was abysmal.
One thing you may consider for updating your OS is "SilentKnight" app, which does a great job of letting you know which updates are avaialble for your machine. Just Google search for it + macOS, and you should find the website.
Hope this helps,
Finny
Hi @Finny
Thanks again. You are great!!!
I think that I put again the discrete GPU ... working with accelaration
and until now works fine
I only need the MBP for development and programming projects, not using much graphics. The issue is that some tools and frameworks need the latest macos like Docker or Android Studio to work
I hope I have no more doubts
And for dosdude1 .... ✌️👍🏆🏆🏆🏆 many thanks!!!!!!!
Thanks again. You are great!!!
I think that I put again the discrete GPU ... working with accelaration
and until now works fineI only need the MBP for development and programming projects, not using much graphics. The issue is that some tools and frameworks need the latest macos like Docker or Android Studio to work
I hope I have no more doubts
And for dosdude1 .... ✌️👍🏆🏆🏆🏆 many thanks!!!!!!!
Patched Imac only booting a Safe Mode
I am using Dosdude1 Mojave patcher on Imac 8,1. (Used many times successfully on this and other Imacs previously)
If I start with a clean disk all works fine.
I want though to be able to run my current setup of Mojave (18G9223) with all the Users and software that is running natively on a later Imac.
So using Carbon Copy Cloner I installed my existing Mojave onto partition on Mac 8,1. Formatted at present as Mac Extended Journaled but also tried with APFS.
Ran Dosdude1 patcher and post patch programme. After rebooting into the patched partition it refuses to boot. Sits a long time ¾ bar complete then starts up again in a loop.
If I start up this partition is Safe Boot it works just fine with all the users and programmes, of my current Mojave, working.
Also in Safe Mode ran patcher update programme, OK.
If I get it to install all the patches again it stalls at “Legacy Video Card Patch” giving an error and so doesn’t complete the full reinstallation. It says though all patches are fully up to date.
In Safe Boot ran Etrecheck nothing untoward.
Have run Single Mode and "/sbin/fsck -fy" but found nothing wrong. Afterwards tried to boot but again unsuccessfully in normal boot.
Have run disk utility ‘First Aid” with no errors picked up.
In desperation removed LaunchDaemons and LaunchAgents folders from Library to nil effect (so put them back).
Why is it booting in Safe Boot not normal boot?
How can I identify those files that Safe Boot doesn’t use?
Can I delete files that Safe Boot doesn’t use so I can boot normally?
ps this is my first post so apologise if it is in the wrong place
I am using Dosdude1 Mojave patcher on Imac 8,1. (Used many times successfully on this and other Imacs previously)
If I start with a clean disk all works fine.
I want though to be able to run my current setup of Mojave (18G9223) with all the Users and software that is running natively on a later Imac.
So using Carbon Copy Cloner I installed my existing Mojave onto partition on Mac 8,1. Formatted at present as Mac Extended Journaled but also tried with APFS.
Ran Dosdude1 patcher and post patch programme. After rebooting into the patched partition it refuses to boot. Sits a long time ¾ bar complete then starts up again in a loop.
If I start up this partition is Safe Boot it works just fine with all the users and programmes, of my current Mojave, working.
Also in Safe Mode ran patcher update programme, OK.
If I get it to install all the patches again it stalls at “Legacy Video Card Patch” giving an error and so doesn’t complete the full reinstallation. It says though all patches are fully up to date.
In Safe Boot ran Etrecheck nothing untoward.
Have run Single Mode and "/sbin/fsck -fy" but found nothing wrong. Afterwards tried to boot but again unsuccessfully in normal boot.
Have run disk utility ‘First Aid” with no errors picked up.
In desperation removed LaunchDaemons and LaunchAgents folders from Library to nil effect (so put them back).
Why is it booting in Safe Boot not normal boot?
How can I identify those files that Safe Boot doesn’t use?
Can I delete files that Safe Boot doesn’t use so I can boot normally?
ps this is my first post so apologise if it is in the wrong place
Hi GeorgePatched
To boot from normal try this in a terminal using a usb install macos:
nvram boot-args=""
reboot
As i understand, you are running a clone of a existing Mojave from an Imac 8,1 in a Mac 8,1 ???
This is not a good idea because the clone is configured in the Imac 8,1 and not in Mac 8,1
This will bring problems in recognize some drivers and others things like some of the Software installed will not work on Mac 8,1
Nowadays, in machines windows, it´s almost impossible to make this kind of change: using the same clone in different machines
To avoid your issues, the best way is to make a clean install in a Mac 8.1
To boot from normal try this in a terminal using a usb install macos:
nvram boot-args=""
reboot
As i understand, you are running a clone of a existing Mojave from an Imac 8,1 in a Mac 8,1 ???
This is not a good idea because the clone is configured in the Imac 8,1 and not in Mac 8,1
This will bring problems in recognize some drivers and others things like some of the Software installed will not work on Mac 8,1
Nowadays, in machines windows, it´s almost impossible to make this kind of change: using the same clone in different machines
To avoid your issues, the best way is to make a clean install in a Mac 8.1
Thank you Shotboy for your help & interest.
I have an Imac 14,1 running Mojave natively but no other computer I can use if it fails without patching.
So I am using patching on Imac 8,1.
I did try
nvram boot-args=""
reboot
and yes it ‘booted’ but the progress bar as before went ¾ way and stopped.
Even more ‘research’ and with the monkey principle I removed all the extensions in: HD/library/extensions then ran the post patch routine in Dosdude1 boot usb. This inserted 2 extensions.
I was able to boot natively into the patched Mojave with all the files and programmes, I checked, from the Imac 14,1 working.
I then ran the Patcher updater.
I had to set the passwords for Mail and also had to reinstall LittleSnitch. All fine.
Originally there were about 12 kexts in Extensions which I have no idea whether they were needed for something – time will tell.
I am hoping this will work when I really need it but with all the experiments this patching is very sensitive to change and the ‘solution’ is a matter of guess work.
Any further advice would be gratefully received.
I have an Imac 14,1 running Mojave natively but no other computer I can use if it fails without patching.
So I am using patching on Imac 8,1.
I did try
nvram boot-args=""
reboot
and yes it ‘booted’ but the progress bar as before went ¾ way and stopped.
Even more ‘research’ and with the monkey principle I removed all the extensions in: HD/library/extensions then ran the post patch routine in Dosdude1 boot usb. This inserted 2 extensions.
I was able to boot natively into the patched Mojave with all the files and programmes, I checked, from the Imac 14,1 working.
I then ran the Patcher updater.
I had to set the passwords for Mail and also had to reinstall LittleSnitch. All fine.
Originally there were about 12 kexts in Extensions which I have no idea whether they were needed for something – time will tell.
I am hoping this will work when I really need it but with all the experiments this patching is very sensitive to change and the ‘solution’ is a matter of guess work.
Any further advice would be gratefully received.
I have a problem with my mac mini late 2009 (3.1) google chrome does not show anything like visual studio code
Attachments
I had the same issue here with my 2008 MacBook. After long search, the easiest way to fix this is simply... to run again macOS Mojave Patcher and rebuild caches.
Hello,
I have updated a MacbookPro5,1 with HFS+ from 18G103 to 18G9323 by downloading SecUpd2021-005Mojave.dmg and the help from @alphascorp & @avz :
I re-installed the patches with force cache rebuild and did a PRAM reset, and now when using SilentKnight or the terminal command softwareupdate -l I get this message:
A similar message is displayed when using the command tmutil:
Is this normal or did something go wrong with the update?
Any help would be appreciated!
I have updated a MacbookPro5,1 with HFS+ from 18G103 to 18G9323 by downloading SecUpd2021-005Mojave.dmg and the help from @alphascorp & @avz :
I re-installed the patches with force cache rebuild and did a PRAM reset, and now when using SilentKnight or the terminal command softwareupdate -l I get this message:
A similar message is displayed when using the command tmutil:
Is this normal or did something go wrong with the update?
Any help would be appreciated!
Hi,
It is possible that you might have to install the updates that happened in between 10.14.3(18G103) and SecUpd2021-005Mojave.dmg.
I personally don't upgrade past 10.14.3(18D42) but sometimes I am wondering if I can still install and use the latest available standalone Safari while remaining on a 18D42.
When I experimented with the unsupported installations I do remember similar messages and they are definitely not normal.
Thanks @avz for your quick reply,
Which update(s) do you think will help?
macOS Mojave - Wikipedia
From my understanding they are all combo updates since 18G103 and should include all previous updates?
Which update(s) do you think will help?
macOS Mojave - Wikipedia
From my understanding they are all combo updates since 18G103 and should include all previous updates?
This is not as straightforward as it may seem.
While APFS system will show you exactly what updates you need to install, with HFS+ it is a guessing game unless you are willing to try them all one by one.