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 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
i have to use patch-kext.sh again, but its not starting to patch because its iMacPro1,1 after booting with OC from internal EFI.
is there a procedure documented what to do after OTA?
after OTA I had to reinsert the SD Card with patched BS installation and rerun "./patch-kexts.sh --2011" but this time with --2011 added to force the patching.
Last edited:
You have to patch again after each OTA update - it is the same as with @dosdude1 before. Apple installs on an OTA full upgrade a completely new macOS system volume with not patches applied at all.
The error message you are getting is caused by the @jackluke OpenCore spoofing which changes the model from iMac12,2 to iMacPro1,1
Nevertheless you can force patching with:
patch-kext.sh --model=iMac12 (or patch-kext.sh --model=iMac11 for users of iMac11,x systems).
Last edited:
Micropatcher Automator got my MBA 5,2 2012 running 11.2.2 swimmingly well.
We need to fix it and hide it from all users. For now I will add a line to the README.md on the GitHub page.we need this on #1
EDIT: Added a short section about OTA upgrades and how to handle this in general.
Last edited:
I installed OCP on an SD card in my Mac Mini 2012, core i7. I am still trying to figure things out, but when I booted from the SD Big Sur Installer I made, it would not allow me to install on the USB 3.0 external drive I have been using. Then, when I booted back into my SSD main drive, it started up in verbose mode. I was very careful, so OCP would not have been installed on the SSD main drive. The computer still boots fine, although now it is showing me the Big Sur upgrade in System Updates. Makes me think my SSD EFI partition somehow now has OCP on it? It still boots and runs Catalina and the Wifi seems to be working, which OCP does not allow from what I understand. Not sure what happened. For sure I did not install OCP on my main SSD boot drive (Catalina).
Last edited:
Since I have an iMac12,2 with a K4100M and an updated BCM943602CDP WiFi/BT card, I guess I don't understand what the benefit would be for me to go through the process of moving to OC. Sounds like I would still have to download updates (via Apple Updates in the OS) and I'd still have to patch the system.
Right now I just download the updates myself, apply the patches to the USB installer, install over the top of it, and patch.
Am I missing something? It seems like I wouldn't really be gaining a lot by moving to OC other than installing OTA updates as I'd still have to reboot and patch. I'm wanting to do it but I'm not seeing the benefits outweigh all the work and time it would take to get there. Am I missing something?
Right now I just download the updates myself, apply the patches to the USB installer, install over the top of it, and patch.
Am I missing something? It seems like I wouldn't really be gaining a lot by moving to OC other than installing OTA updates as I'd still have to reboot and patch. I'm wanting to do it but I'm not seeing the benefits outweigh all the work and time it would take to get there. Am I missing something?
Will do. The Big Sur update offer went away. I think somehow my SSD was just starting in verbose mode, so I used Terminal to turn that off. Seems back to normal now. I will go through the docs very carefully again.
I had wanted to do the EFI backup, but there is an alert about knowing which chip one has. I did not want to take my Mac Mini apart to determine that, so forged ahead. Now I think that was risky?
Currently the way to use it is creating an USB (SD) installer and then it is your decision to put the EFI created by OCLP onto the USB (or SD) or onto your internal disk.
Reboot and hold alt/option an select the device where you put the EFI onto. It will show up as EFI boot in different colours and with different icons depending on the device type (USB, internal disk, SD).
Boot into the OC aka Boot EFi brings up another graphical boot selector which allows you to select the USB/SD installer and run the Apple installation program. Doing this you select the target drive for your installation.
What was your question?
Hi! I trusted you, followed the procedure, used OpenCore Lecacy Patcher to reinstall Big Sur 11.2.2 which I had installed with micropatcher and everything go very fine, System starts up quickly, even with the USB key extracted from the Mac except that ... when my iMac starts-up or shuts-down always does in Verbose mode.
How can I deactivate the verbose mode?
I specify that first of installation I mounted the internal EFI partition with the Terminal and the command <sudo mount /dev/discxsx> and I copied the EFI of the USB key to the EFI Partition of the main System disk (Macintosh HD and not Macintosh HD-Data). So! To run installation I booted OpenCore from EFI of internal SSD and then I selected "Install macOS Big Sur" USB disk. [Note: I maintained also the EFI folder in the USB Key EFI Partition. I wrong? Maybe I should have left only one EFI? and which one is better to leave?]
After Installation I see now, in the EFI Partition internal to the Mac, that the EFI-Partition/EFI folder there is only a file "BOOTx64.efi", while the USB Key EFI/EFI contains nine files, among which one called "setvars-verboseboot-x86_64.efi" The size and date of "BOOTx64.efi" file in the Macintosh HD EFI and that of the EFI of USB Key are also different.
Maybe now, after installation, I have to reinsert the entire EFI folder into the EFI partition of internal SSD, copying it from the EFI partition of the USB key? Perhaps did I do it wrong to make it before and the installation overwrote the EFI folder?
Did I do something wrong?
Thank you for your help
1. delete the -v from the boot-args to get rid of the verbose mode. since it does only hurt during boot I wonder what you guys do the whole day? constantly rebooting the Mac?
2. how to install the (complete OpenCore) EFI folder on the target device of your choice is part of the standard OpenCore docs and even part of the OCLP docs. I will not start the read, copy and paste marathon
--
formam brevitati would be nice - your messages are far too long to read and the constant bold printing does not help. Normally I am a fast reader and I am able to read across longer pages, which is not possible any longer if one decides to use bold printing on a stochastic base. I wrote before that I have to read your messages several times. I will no do this again!
I understand... and you're right... By highlighting the salient points in bold I thought I was making it easier to read and that mine was a gesture of love... But from what you say I realize that it is not. Thank you
Switching of the verbose mode is on the list of upcoming changes. So if you do not want to mess with the config.plist you can leave it and wait. Otherwise it is a good idea to get a basic idea of the structure of the file. Who knows when you are going to need it? This thread follows a completely different approach. One can get all pieces needed to create a working config.plist, but you have to construct it by reading and following the docs on the first post. This way everybody learns the (f**...) details.I understand... and you're right... By highlighting the salient points in bold I thought I was making it easier to read and that mine was a gesture of love... But from what you say I realize that it is not. Thank you
Last edited:
Yes, these are common problems for someone new to OCLP.
I am in the same boat. Will wait for the enhancement in the next version(s). For now, just left the verbose mode alone and left the EFI on SD card. I don't reboot often; only when needed.
Add EFI disk mounting and editing post-install · Issue #74 · dortania/OpenCore-Legacy-Patcher
Would allow for easy transfer of drive between USB and internal drive once setup, also allows users to easily disable -v in their config.plist
github.com
Thank you! Unfortunately for me, I am someone who likes to have full control of the computer, even at "low level".
Your encouragement to use OpenCore has overcome my anxiety about being able to lock the Mac; now that I have started I am not afraid to study OpenCore and I think I have already figured out how to disable Verbose mode (from pure picky ;-))
A curiosity: did you by chance attend the Liceo Classico? Or why your cultured and perfect ancient Latin? ... Don't tell me you are a Trappist or Carthusian monk writing from a monastery...
Be that as it may, you prove to be a great person, like dosdude1 and others.Thanks again and goodnight.
Wish you all the best.
OpenCore is not for the faint-hearted. That rabbit hole is deep.
Faint of heart? ... I don't know OpenCore yet and I'm not a developer, but I get along very well with the Terminal at the system level and beyond.
That said, you know many who dare to take apart a PoweMac G4 MDD to modify the AGPI Bus to use the Graphics Cards of the new (at the time) PowerMac G5s, as I was annoyed that I could not see the waves that made the Widget at startup? ..
Do you want me to list other crazy things to improve other Apple hardware and want to see the photos if you don't believe me?
As for the software, however, do you know many who, despite being elderly and non-IT, manage to enter the NIB armored files, improve the Mail Preferences Panels and try to demand from Apple today what Steve expected when he was alive?
Check out this post of mine and see the attached clips too:
https://forums.macrumors.com/thread...prove-function-beauty-and-ergonomics.2246268/
Best regards and goodnight 😊
The recent posts about OTA updates haven't commented on what happens to the 'sealed' system status. I found that full installs (or overwrites) with a full installer, once patched, produces 'Sealed: No' [Big Sur System] partition info in Recovery, but an OTA update always produces a 'Sealed: Broken' status. I suspect many/most people haven't (re)checked this. Does a 'broken' sealed system matter in any way? Personally, it's warned me off OTA updates and to only wait until a full version installer is available to Hax micropatch each time, to guarantee the system remains unsealed.
Imac 13,1 late 2012 was updated today to Big Sur 11.2.2 and beta 11.3 (20E5196f) in dual boot mode.
Everything went smoothly, although the installation on the SSD attached via USD was very slow.
The iMac can also be booted into Catalina. Here are some Geekbench results
Release single thread multi thread
Catalina 721 2191
11.2.2 745 2247
11.3 732 2304
The absolute test results may not be in line with other users' experience. However, the performance difference between the various releases is immaterial. There is no indication that Big Sur performs badly on a fusion drive.
I'm going to try to move 11.2.2 to Open Core.
I will surely install it, but for now I'm reading and thinking about a dual boot to test it and get trained with OCLP.
My mac at home is used by my daughter too, so I don't want to install something too coomplex to handle for her.
Anyway thanks a lot for your suggestion!
Bye
OCLP 0.0.14 is out offering to disable verbose and some other add ons. Did no test it myself.
Whoever is using OCLP can try it out without touching the Big Sur installation. Of course please keep your running former EFI to put it back in case something does not work as planned.
Whoever is using OCLP can try it out without touching the Big Sur installation. Of course please keep your running former EFI to put it back in case something does not work as planned.
Last edited: