Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 12 Monterey on Unsupported Macs Thread

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.
mwidjaya said:
Bootcamp works in a narrow corridor as Apple sees it.

For eg, I did some absurd experimentation to finally run unsupported Bootcamp version to run unsupported Win11 on a partition on 2010 MacBook Pro running supported High Sierra.

All working well now, so it stays like that, not fiddling with it some more, lol.
Click to expand...
I was about to try that, was going to downgrade to an earlier MacOS version from 2017 or something, install bootcamp from there and then upgrade again to Monterey, when Monterey randomly finally decided to make bootcamp work. So I didn't have to go that far.
 
I have monterey with clover it works perfect injecting edid and injecting intel with opencore I always get black screen I have injected framebuffer, nvram, busid, ports, flag, deviceid, edid, connectors, platformid and always black screen only works well with hdmi port but with internal display black screen here I leave ioreg and config I'm crazy I don't know what to do anymore I have also followed dortania guide but nothing works the ioreg is with the display with clover

my specs are

toshiba r930
intel hd 4000
intel 3320m processor
memory 8gb
 

Attachments

  • ioreg.zip
    737.5 KB · Views: 94
  • config.plist.zip
    6.1 KB · Views: 74
Well, I just tried and it's not that simple. I am afraid we were too optimistic with the idea of running the patcher from Recovery (hence "theoretically" in my post).
Unfortunately, the Recovery environment does not contain all the libraries needed for the Patcher to run:

IMG_8414.jpg


As for now, it seems not possible.

(BTW @******* - the exact command was cd /Volumes/usbname/OpenCore-Patcher.app/Contents/MacOS/ and then ./OpenCore-Patcher ;) )
 
Last edited:
  • Like
Reactions: hvds, macpro_mid2014, 0134168 and 1 other person
XLN82 said:
Hi everyone, is there a way to install opencore patcher from Terminal in recovery mode?
Click to expand...
I hadn't got round to testing, and didn't think it was worth speculating - correctly as it turns out - that it probably wouldn't run in Recovery. The (positive!) reason for this additional comment is that you asked if it was possible to install OCLP-configured OpenCore in Recovery mode. Yes - if you have another Mac (and you know all the settings for your Mac) or if your Mac can still boot in normal mode. You can run OCLP not in Recovery mode, ask it to write to a non-standard output directory, e.g. a USB, then install by copying those files into the right place (e.g. onto your ESP) in Recovery mode.
 
  • Like
Reactions: hvds, macpro_mid2014 and hwojtek
Bmju said:
You can run OCLP not in Recovery mode, ask it to write to a non-standard output directory, e.g. a USB, then install by copying those files into the right place (e.g. onto your ESP) in Recovery mode.
Click to expand...

Yupp, exactly. I may only add that booting from said USB by pressing "C" on startup and choosing "Recovery HD" from OpenCore picker would help. Obviously the config.plist must contain:
Code: 
<key>HideAuxiliary</key>
            <false/>
 
Sorry if I'm stupid, but what does this mean "Native BRCM20702 and BRCM20703 are still fully support by OpenCore Legacy Patcher"? I have a BRCM20702 in my Mac Pro 5,1, and in Monterey Bluetooth works, but without handoff support. System Report recognizes it as "THIRD_PARTY_DONGLE". Is this something that can be remedied with post-install-patches? Or are there newer modules that the Mac Pro can be upgraded with in a similar way?
 
Last edited:
Taipan said:
Sorry if I'm stupid, but what does this mean "Native BRCM20702 and BRCM20703 are still fully support by OpenCore Legacy Patcher"? I have a BRCM20702 in my Mac Pro 5,1, and in Monterey Bluetooth works, but without handoff support. System Report recognizes it as "THIRD_PARTY_DONGLE". Is this something that can be remedied with post-install-patches? Or are there newer modules that the Mac Pro can be upgraded with in a similar way?
Click to expand...
When I first installed bluetooth hardware in my Mac Pro 3,1 it was reported the same way. After an OS update I no longer see the third-party-dongle reference. I doubt this fixes the Handoff situation which I think is a more complex problem.
 
hwojtek said:
Yupp, exactly. I may only add that booting from said USB by pressing "C" on startup and choosing "Recovery HD" from OpenCore picker would help. Obviously the config.plist must contain:
Code: 
<key>HideAuxiliary</key>
            <false/>
Click to expand...
... or you can just press space ... !
 
  • Like
Reactions: hwojtek
Bmju said:
I hadn't got round to testing, and didn't think it was worth speculating - correctly as it turns out - that it probably wouldn't run in Recovery. The (positive!) reason for this additional comment is that you asked if it was possible to install OCLP-configured OpenCore in Recovery mode. Yes - if you have another Mac (and you know all the settings for your Mac) or if your Mac can still boot in normal mode. You can run OCLP not in Recovery mode, ask it to write to a non-standard output directory, e.g. a USB, then install by copying those files into the right place (e.g. onto your ESP) in Recovery mode.
Click to expand...
is it possible by default patch an usb drive?
I have a time machine image, very time I try to recover it, Mac OS for whatever reason is not starting and reinstalling the Os from any kind of source, is deleting the backup restored with migration assistant.
My plan was to remove the HD and connect it to an external usb, and try patch it and see if is turning back to like.
I say so because every time I boot it is loading but than is crashing, and safe mode is crashing too...
 
Regarding the people who are mentioning the use of Windows 11 (Bootcamp) and not messing with the main macOS partition, in fact I don't mess with the W11 partition, the macOS partition I delete and reinstall whatever system I want, both macOS Mojave , macOS Catalina, macOS Big Sur, and macOS Monterey. I can go back and forth between these systems at any time by performing a fresh install, but I don't move the Windows partition, and it continues to work perfectly regardless of the macOS.

I just had to use Bootcamp Assistant to create the Windows 11 bootable pendrive and partition it once using macOS Catalina, from then on this partition became independent, as if it were a separate disk, in OpenCore there is no entry for it , my EFI doesn't have that /EFI/BOOT/BOOTx64.efi just what is needed to work on MacBook Air 2012
 
alexcorpse said:
I have monterey with clover it works perfect injecting edid and injecting intel with opencore I always get black screen I have injected framebuffer, nvram, busid, ports, flag, deviceid, edid, connectors, platformid and always black screen only works well with hdmi port but with internal display black screen here I leave ioreg and config I'm crazy I don't know what to do anymore I have also followed dortania guide but nothing works the ioreg is with the display with clover

my specs are

toshiba r930
intel hd 4000
intel 3320m processor
memory 8gb
Click to expand...


Hello

I put the patch for your graphics card as well as the EDID of your laptop that is detected in ioreg

- I don't know why you don't use the same bootloader you were using before and it works, either one works and that's the interesting thing
 

Attachments

  • config 2.plist.zip
    6.9 KB · Views: 50
khronokernel said:
Additionally regarding Bluetooth support on older machines, it seems I glossed over a few missing firmwares. Apparently Monterey dropped all 2011 and older Bluetooth modules, not just BRCM2046. 2012+ machines should be fine (MacPro5,1 not included, needs upgraded bluetooth as well)

Following Firmware Files are missing, should be easy for users to match device IDs off file name:
Code: 
* 2046_820F.dfu
* 2046_8210.dfu
* 2046_8213.dfu
* 2046_8215.dfu
* 2046_8216.dfu
* 2046_8217.dfu
* 2070_821A.dfu
* 2070_821B.dfu
* 2070_8218.dfu
* 20702_821D.dfu
* 20702_821F.dfu
* 20702_828A.dfu
* 20702_828B.dfu
* 20702_828C.dfu
* 20702_8281.dfu
* 20702_8286.dfu
Apple really trying to clean up legacy hardware support with macOS Monterey, understandable as they haven't supported these machines since High Sierra (or Mojave for the MacPro5,1) however quite unfortunate as this adds more work onto our plate as community developers. Will continue researching this issue

Also note that all Apple branded BRCM20702 are still supported. Firmware dropped seemed to be modules Apple didn't use at first glance (do correct me if I'm wrong)

Edit: 2012 MacBook Pros in fact do use the 20702_821D.dfu firmware, Apple already killing the 2012 series it seems
Click to expand...
The BRCM20702 module in my Mac Pro 5,1 works, but without handoff support. Do you know whether there are 20703 modules that I can use with the same adapter card and whether those would still support handoff?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back