I tried that this morning and it wasn't able to install for me? Not sure if it is me or the copy on the server, I was hoping there would be another source for 11.2.
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Catalina Apps Working/Not working
- Thread starter Brammy
- WikiPost WikiPost
- Start date
-
- Tags
- catalina
- Sort by reaction score
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
- Status
- The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I tried that this morning and it wasn't able to install for me? Not sure if it is me or the copy on the server, I was hoping there would be another source for 11.2.
It is generally advisable to only install from installers sourced directly from apple servers. The problem afflicting installers from 10.7 onwards is expired certificates - even ones previously downloaded from apple servers.
There are 2 ways of dealing with this. One way is to go back to apple's support page https://support.apple.com/en-au/HT211683 every few years and redownload ALL of them. These will have updated certificates.
The second way is if you are using an installer with an expired certificate, either previously downloaded from apple, or one from another source is to boot up from the bootable usb and use terminal to change the date of the computer to around about the same date as the release date of the installer - before installing. This circumvents the expired certificate preventing it from installing.
In the case of 11.2.3 which was released on March 8, 2021 you can proceed as follows.
You can make a bootable usb for 11.2.3, boot up from that and change the date of the computer to midnight March 9, 2021 with terminal command sudo date 0309000021
The format of the date is [MM][DD][HH][MM][YY], that is month, day, hour, minute, year.
You can also check the date has been reset with terminal command date.
There is a possiblility that your efforts may be thwarted by automatic network time resetting. If this is the case you can turn it off with command sudo systemsetup -setusingnetworktime off
PS. Don't feel too bad if you are forced to source apple software outside apple. Even apple themselves did this a few years ago when they lost an old beta version of System 7 and bought it back from some dude on ebay.
There are 2 ways of dealing with this. One way is to go back to apple's support page https://support.apple.com/en-au/HT211683 every few years and redownload ALL of them. These will have updated certificates.
The second way is if you are using an installer with an expired certificate, either previously downloaded from apple, or one from another source is to boot up from the bootable usb and use terminal to change the date of the computer to around about the same date as the release date of the installer - before installing. This circumvents the expired certificate preventing it from installing.
In the case of 11.2.3 which was released on March 8, 2021 you can proceed as follows.
You can make a bootable usb for 11.2.3, boot up from that and change the date of the computer to midnight March 9, 2021 with terminal command sudo date 0309000021
The format of the date is [MM][DD][HH][MM][YY], that is month, day, hour, minute, year.
You can also check the date has been reset with terminal command date.
There is a possiblility that your efforts may be thwarted by automatic network time resetting. If this is the case you can turn it off with command sudo systemsetup -setusingnetworktime off
PS. Don't feel too bad if you are forced to source apple software outside apple. Even apple themselves did this a few years ago when they lost an old beta version of System 7 and bought it back from some dude on ebay.
Last edited:
ok, can you give me very very clear and basic instructions on how to do the bolded part? I need to do what is bolded AND make an OCLP installer for that huge 12 gb macOS install file. i hope it is not as complicated as i think it is in my head, or I guess this will be the end for the OCLP project if apple keeps expiring certificates.It is generally advisable to only install from installers sourced directly from apple servers. The problem afflicting installers from 10.7 onwards is expired certificates - even ones previously downloaded from apple servers.
There are 2 ways of dealing with this. One way is to go back to apple's support page https://support.apple.com/en-au/HT211683 every few years and redownload ALL of them. These will have updated certificates.
The second way is if you are using an installer with an expired certificate, either previously downloaded from apple, or one from another source is to boot up from the bootable usb and use terminal to change the date of the computer to around about the same date as the release date of the installer - before installing. This circumvents the expired certificate preventing it from installing.
In the case of 11.2.3 which was released on March 8, 2021 you can proceed as follows.
You can make a bootable usb for 11.2.3, boot up from that and change the date of the computer to midnight March 9, 2021 with terminal command sudo date 0309000021
The format of the date is [MM][DD][HH][MM][YY], that is month, day, hour, minute, year.
You can also check the date has been reset with terminal command date.
There is a possiblility that your efforts may be thwarted by automatic network time resetting. If this is the case you can turn it off with command sudo systemsetup -setusingnetworktime off
PS. Don't feel too bad if you are forced to source apple software outside apple. Even apple themselves did this a few years ago when they lost an old beta version of System 7 and bought it back from some dude on ebay.
Well assuming OCLP is going to work, you could just change the date of the computer using another bootable usb with a version compatible with that mac before proceeding with OCLP. So maybe use what is compatible with the 2009 imac you can use High Sierra. I would make a bootable USB with instructions from https://support.apple.com/en-au/HT201372 boot up with that and use terminal to change the date to March 9, 2021 with sudo date 0309000021. This will circumvent the expired certificate of Big Sur 11.2.3 preventing to install.
Then proceed with instructions from https://dortania.github.io/OpenCore-Legacy-Patcher/START.html for the Big Sur installation - but that's assuming that is going to work.
If it still doesn't work there is whole tread on it here which might help https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/
Then proceed with instructions from https://dortania.github.io/OpenCore-Legacy-Patcher/START.html for the Big Sur installation - but that's assuming that is going to work.
If it still doesn't work there is whole tread on it here which might help https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/
Last edited:
ok, you are jumping ahead again, i DO NOT know how to do the bold part that you keep casually mentioning. Are you able to give a very very very basic and step by step instruction guide on how to do that?Well assuming OCLP is going to work, you could just change the date of the computer using another bootable usb with a version compatible with that mac before proceeding with OCLP. So maybe use what is compatible with the 2009 imac you can use High Sierra. I would make a bootable USB with instructions from https://support.apple.com/en-au/HT201372 boot up with that and use terminal to change the date to March 9, 2021 with sudo date 0309000021. This will circumvent the expired certificate of Big Sur 11.2.3 preventing to install.
Then proceed with instructions from https://dortania.github.io/OpenCore-Legacy-Patcher/START.html for the Big Sur installation - but that's assuming that is going to work.
If it still doesn't work there is whole tread on it here which might help https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/
Also, this might be a bit unrelated, but I just reinstalled 10.13 (which is the latest possibly due to the imposed artificial software limit by apple) on the imac 2009 yesterday, and did the 10.15 update (which is not supported officially this morning) from the dosdude1 patcher here https://dosdude1.com/catalina/ it works fine.
So I don't want to adjust the date on a brand new copy of 10.13 on a usb drive and install that and then install 11.2 (Which i hope, will not have an expired certificate somehow, otherwise it would be a waste of time to not be able to install it, and i would have to install 10.15 again. so what i am getting at it, is there a was to modify the 11.2 install image to make the certificate work, then i can use that image to make a OCLP boot usb and then use that usb to install straight from the point in the 2nd paragraph?
There are step by step instructions for changing the date via terminal at https://macosx-faq.com/how-to-change-date-time-terminal/ . It's basically the same as what I said before but gives more details.
But there could be 2 reasons why 11.2 is not installing:
1. Possible expired certificate.
2. It's an unsupported mac.
Changing the date only solves the first problem, not the second.
But there could be 2 reasons why 11.2 is not installing:
1. Possible expired certificate.
2. It's an unsupported mac.
Changing the date only solves the first problem, not the second.
Last edited:
HelloI updated the 2009 iMac 21.5", from High Sierra (this is the max stock OS) to Catalina, via dosdude1's patcher: https://dosdude1.com/catalina/
On firefox extended release edition, google maps does NOT work, it shows a black screen. I did some googling, there was a fix saying i should turn on/off webgl in the about settings, that didn't work though.
I tried Firefox extended release + google maps on my 2014 macbook pro and it works fine.
So my question is, why doesn't firefox extended release + google maps work on Catalina on my 2009 iMac? (video card is ATI Radeon HD 4670 graphics processor with 256MB of GDDR3 memory, which is a non metal GPU, not sure if this is related to the problem though)
Does anyone else have this problem or can reproduce it?
Please let me know what you think and who I should file the big report to, thanks
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.