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 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Make certain the disk you want boot from is selected in the Startup Disk CP and OCLP_033 is fully installed?
After OTA update from 12.2b1 to 12.2b2 I am experiencing massive WiFi-problems, either the available networks are not showing at all, or my machine does n o t logon to the preferred WLANs.
System info>WLAN is showing all available networks correctly, but I cannot logon.
I did NVRAM reset, SMC reset to no avail.
I tried both OCLP 0.3.3 and 0.3.4n, same result.
And my initial OTA update to 12.2.b2 was doomed after I ticked FileVault in the setup assistant.
I had to re-install from scratch via external FireWire 800 drive (OCLP 0.3.4n FireWire option "True").
Migration assistant did n o t run from the Macintosh HD (Samsung SSD), o n l y within the setup assistant after a clean installation of 12.2b2. It took me 4! full days and nights to get back my configuration, but now WiFi is a complete pain in the ass.
Can anyone help with a solution to get a stable Wifi back?
System info>WLAN is showing all available networks correctly, but I cannot logon.
I did NVRAM reset, SMC reset to no avail.
I tried both OCLP 0.3.3 and 0.3.4n, same result.
And my initial OTA update to 12.2.b2 was doomed after I ticked FileVault in the setup assistant.
I had to re-install from scratch via external FireWire 800 drive (OCLP 0.3.4n FireWire option "True").
Migration assistant did n o t run from the Macintosh HD (Samsung SSD), o n l y within the setup assistant after a clean installation of 12.2b2. It took me 4! full days and nights to get back my configuration, but now WiFi is a complete pain in the ass.
Can anyone help with a solution to get a stable Wifi back?
OK.... this is interesting. I downloaded OCLP and rebooted by holding option, selected the efi thing, it appeared to install something, and then had Macintosh data icon and then Macintosh HD icon. The data icon is before the Macintosh HD icon, and if I let it boot into that it boots into Monterey 12.1..... if I select Macintosh HD, it boots into Big Sur. How or what it did, I have no clue, but now it appears that I have both working operating systems, Monterey and Big Sur... how I have no clue.....
I was in the same situation (BS -> OTA Monterey), but Intel Power Gadget doesn't work with my *DP* MP5,1 ?
Searching for Preboot re-construction, I found an article from 2019 discussing APFS problems.
Boot Failures After Converting MacOS SSD To APFS - TeckLyfe
After converting your MacOS hard disk to APFS, you could run into a situation where your Mac is no longer bootable and you get errors like "Building boot
www.tecklyfe.com
The author suggested entering Recovery, then (in terminal) use:
Code:
# diskutil apfs updatePreboot /Volumes/Macintosh\ HD/The thought of waiting for the Recovery to boot gave me chills (and I don't have 'Macintosh\ HD/'), so, let me have some fun...
In a regular User Terminal session, I elevated my terminal to an admin account:
Code:
% su - admin
Password:
Code:
% diskutil apfs
Usage: diskutil [quiet] ap[fs] <verb> <options>
where <verb> is as follows:
[...]
updatePreboot (Update a macOS Volume's related APFS Preboot Volume)
[...]Further:
Code:
% diskutil apfs updatePreboot
Usage: diskutil apfs updatePreboot <apfsVolumeDisk> [-noGlobalEFIGraphics]
[-od <overrideODFullPath> | "/"]
where <apfsVolumeDisk> = APFS Volume DiskIdentifier
-noGlobalEFIGraphics overrides for-all-users localized rendering
<overrideODFullPath> = use this path instead of on-APFS-Volume
Examine the given APFS Volume for macOS and Open Directory (OD) database files,
correlate the Volume's APFS crypto users with OD users, and update the related
Preboot Role Volume's Subject Directory with data such as EFI login graphics.
Specifying "/" for <overrideODFullPath> will use /var/db/dslocal/nodes/Default.
No crypto passdata is needed, but ownership of the affected disks is required.
Example: diskutil apfs updatePreboot disk5s1This is IT! Hmmm . . . where is IT?
Code:
% diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 2.0 TB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk1
Physical Store disk0s2
1: APFS Volume Monterey - Data 370.5 GB disk1s1
2: APFS Volume Monterey 15.8 GB disk1s2
3: APFS Snapshot com.apple.os.update-... 15.8 GB disk1s2s1
4: APFS Volume Preboot 355.9 MB disk1s3
5: APFS Volume Recovery 1.1 GB disk1s4
6: APFS Volume VM 1.1 MB disk1s5APFS splits the default "Macintosh HD" into two, distinct Volumes:
A) The SSV (Sealed/Signed System Volume); a mounted snapshot of the unmounted read-only System volume named "Macintosh HD"
B) The writable Data volume named "Macintosh HD – Data"
Boot disk layout in macOS Monterey
In Monterey, these haven’t changed much since Big Sur. However, those small differences are significant, particularly on M1 Macs.
eclecticlight.co
My /dev/disk1 (synthesized) Container has a "Monterey - Data" Volume @ /dev/disk1s1, which was my intended target.
I then ran:
Code:
% diskutil apfs updatePreboot /dev/disk1s1
Started APFS operation
UpdatePreboot: Commencing operation to update the Preboot Volume for Target Volume disk1s1 (Monterey - Data)
UpdatePreboot: Commanded forwarding to System-role regardless of target input = InhibitAutoGroupTarget = 0; ForwardingEnabled
UpdatePreboot: Commanded moving Preboot/etc UUID dirs from old to modern = MigrateSubjectDir = 1; MigrationEnabled
UpdatePreboot: The Target Volume is part of APFS Container disk1
UpdatePreboot: The Data-sibling or self of the target is disk1s1 err=0
UpdatePreboot: The Target (normalized to Data-role) Volume's non-special-kind-probably-OD user count is 2 and the Recovery (any of 4 kinds) user count is 0
UpdatePreboot: There are OpenDirectory user(s) but no Recovery user(s)
UpdatePreboot: The above is an abort condition for some purposes but not UpdatePreboot; continuing
UpdatePreboot: The Target Volume is part of APFS Volume Group AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE
UpdatePreboot: Explicit macOS and OD source paths given to the UP core
UpdatePreboot: Sourcing VAR directory relative to source macOS
UpdatePreboot: Sourcing USR directory relative to source macOS
UpdatePreboot: Search Path For macOS Source Files = (nil=NotMounted) = /
UpdatePreboot: Directory That macOS "var" Is Searched To Be In = (nil=NoMacOS) = /
UpdatePreboot: Directory That macOS "usr" Is Searched To Be In = (nil=NoMacOS) = /
UpdatePreboot: Open Directory Database Search Path = (nil=MacOSSearchPathNotMounted) = /var/db/dslocal/nodes/Default
UpdatePreboot: Preserve EncryptedRootPList When No-OD = 0
UpdatePreboot: Successfully opened Open Directory database; setting AuthODNodeOrNil accordingly
UpdatePreboot: Mounting and ensuring as mounted the related Preboot Volume
UpdatePreboot: Preboot Volume = disk1s3 (Preboot)
UpdatePreboot: Preboot Volume Target Directory (currently in use; no migration, if any, yet) = /System/Volumes/Preboot/AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE
UpdatePreboot: Taking mount hold on Preboot Volume
UpdatePreboot: Migrating UUID Folder name as necessary
[...]
UpdatePreboot: Exiting Update Preboot operation with overall error=(ZeroMeansSuccess)=0
Finished APFS operationI did not have to re-bless, or select System Startup.
Now I can re-boot to "Monterey" in the OC booter
hth
you can boot with option pressed just to verify if it is booting from the oclp disk. If not, select it and press control(the arrow will turn circular) and enter to boot.
See this video from 1:36 for possible solutions for your problem:
Well it looks like it is a success. Not really sure how it managed to do the install, but it did, and still have Big Sur somehow. When the computer starts, it shows two icons, one say Macintosh data and the other one say Macintosh HD. If I boot into the one that says Macintosh data it loads Monterey, if I boot into the one that says Macintosh HD it boots into Big Sur. I guess somehow I got the best of both.... both work properly so no complaints, just a little confused how it happened. Using Monterey now and quite impressed with how much prettier the screen display looks, maybe its just because it is something new....
So I decided to go for Monterrey..... left the update running overnight, and it worked with no problem. All I had to do was run the post Volume patch to fix WiFi and Nvidia card.
It might be worth going for an AMD card and the upgrade for the WiFi/Bluetooth card.
It might be worth going for an AMD card and the upgrade for the WiFi/Bluetooth card.
So… i have 2 problems :
First : i loose my second screen (DVI)
second :
I thinks i cannot patch the system on my SSD, i have this message with OCLP 0.3.3
www.dropbox.com
What i can do ? Thanks
First : i loose my second screen (DVI)
second :
I thinks i cannot patch the system on my SSD, i have this message with OCLP 0.3.3
Dropbox - File Deleted - Simplify your life
What i can do ? Thanks
So did you try to disable SIP?So… i have 2 problems :
First : i loose my second screen (DVI)
second :
I thinks i cannot patch the system on my SSD, i have this message with OCLP 0.3.3
Dropbox - File Deleted - Simplify your life
What i can do ? Thanks
you lost the second screen since no driver for the Nvidia card is loaded, you need to run the post volume patch. also you need to disable SIP before.So… i have 2 problems :
First : i loose my second screen (DVI)
second :
I thinks i cannot patch the system on my SSD, i have this message with OCLP 0.3.3
Dropbox - File Deleted - Simplify your life
What i can do ? Thanks
You mean if I ran OCLP patch for something like a graphics fix, I have to run the patch again after I update to 12.2? Are you sure?
p.s. If I backup my OCLP Monterey using Time Machine then I restore using same TM backup to a new M1 MBP, everything is copasetic? No funny biz? No gotcha's?
That how it works. In fact, I think the OTA would be full download instead of delta OTA.
That is why it is so much better if your mac hardware doesn't require post-install patch.
Delta OTA just like a supported mac and that's it.
Restore is probably not the right word.
Setting up new Mac, pointing to a TM, is like moving your content to a new mac. Should be ok, I can't think of a reason why not.
Move your content to a new Mac – Apple Support (AU)
Migration Assistant is doing a fine job.
I did a clean install, which equals a new Mac right out of the box, the Setup assistant fired up Migration assistant, I chose Time Machine>latest backup, Migration assistant copied everything into place, no shenanigans, 100% working, everything in place, no lost files.
Weird, I'm preparing my MacBook Pro 11,3 for Monterey, and downloaded and built OCLP 0.3.3 release version. I didn't do step #2, which was to install to the current drive.
It's currently at Catalina, but just now it I got a system message telling me I could upgrade to Monterey?
It even let me go to the App Store link for Monterey, but of course as soon as I tried to download it, it said that there wasn't an installer for this machine.
Very strange, since I know that I did #1 but not #2, and I don't boot to OCLP currently.
It's currently at Catalina, but just now it I got a system message telling me I could upgrade to Monterey?
It even let me go to the App Store link for Monterey, but of course as soon as I tried to download it, it said that there wasn't an installer for this machine.
Very strange, since I know that I did #1 but not #2, and I don't boot to OCLP currently.
So far so good. Still haven't figured out how it installed Monterey just by booting into the OCLP efi boot and letting that install, or how it made its own partition for Monterey and left Big Sur as well, but it is working very nicely on Monterey now. It is a 2013 MacBook Air 13. Figured out why the replacement aftermarket battery didn't work as well, it wouldn't recognize 3 of them from amazon, today I took the third one out and looked at the plug. turned the plug over so it looked the same as the original battery plug and it works. be nice if they would either make it right or mention that in the instructions. All's well that ends well though, and nice to not be confined to the power adapter and carry an extension cord all the time.
MacBook 9,1 here - 15'' 2012 model.
I cannot install Windows 10 nor 11 via Bootcamp. Windows 10 did install however I received stopcodes upon boot. Windows 11 will not allow me to install. It gives me an error in the installer saying my system is unsupported.
Any obvious workarounds? I'm thinking as a next step to create a standalone USB installer and bypass bootcamp.
thanks all
I cannot install Windows 10 nor 11 via Bootcamp. Windows 10 did install however I received stopcodes upon boot. Windows 11 will not allow me to install. It gives me an error in the installer saying my system is unsupported.
Any obvious workarounds? I'm thinking as a next step to create a standalone USB installer and bypass bootcamp.
thanks all
I've had good luck with this set of instructions with the exact problems you are noting : Shows Wifi networks but will not connect to saved or newly discovered Wifi Networks.
Mac – Howchoo
howchoo.com
Thank you jowaju, that worked, my WiFi is back again. Great tip!I've had good luck with this set of instructions with the exact problems you are noting : Shows Wifi networks but will not connect to saved or newly discovered Wifi Networks.
Mac – Howchoo
I didn't use Bootcamp at all when I installed Windows 10 on my old MacBook Pro ( 5,4 - mid 2009).
As I never use the CD/DVD drive I removed that and bought a drive caddy to put an old SSD into to. I then installed Windows 10 on to the new drive. After installation I downloaded Brigadier 0.2.4 and 7Zip to install the drivers specific to my Mac. I wrote an explanation some time ago that may help if you did want to go the route of using another drive to install Windows on. Find it here - https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28476449
Last edited:
Did you follow this guide?
Why would anyone want to install Windows on their beautiful Mac, and ruin the "it just works" experience? I have found that all the Mac operating systems I have used from Tiger to now Monterey is far superior to anything Microsoft creates.