macOS 12 Monterey on Unsupported Macs Thread

[StarPlayrX]

Tried the BluetoolFixup.kext, It wouldn't boot anymore, just get stuck at the apple logo. Luckily I can boot into Windows and edit the config.plist and remove the entry and it boots just fine.

Nothings working yet, Bluetooth is dead for now.

what version of MacOS are you trying to boot? There are still uses with Beta 4 on Bluetooth. I can't get Beta 4 to trigger even on my new Lenovo Card yet. I was able to get BT to work with Beta 2 and Beta 3 (not with the BCM 20702B0 BT4LE card but with an Intel Wireless card).

If your system does not be boot try booting at -v to see where it is stopping at, you may need another kext for your bluetooth card, your card may just be incompatible with Monterey or it's how it's treating the USB for your bluetooth. This is why many are bypassing the USB on their BCM card and redirecting it to another USB card or Hub. I'm doing the same my Lenovo Card just without any soldering or nail polish.

I am assuming you will need some type of Firmware.kext for your BT card to work.

 

[rehkram]

Hey folks without a signature set up on your user profile that lists your Macs and their s/w versions I encourage you to set it up because ...

• It will save you a lot of typing in the body of your posts telling us what you've got
• It will save people who read it a lot of time scrolling back through your posts to understand the context and scope of your posts

Thank you kindly! 🙂

 

[beruanges]

hi

 

[StarPlayrX]

Since some of Monterey betas my USB ports are defined incorrectly and therefore USB devices (e.g. WiFi adapter) work with 2.0 specification instead of supported 3.0. Is there any simple and effective way to correct this? Thank you all.

Just Bluetooth uses USB on a combo WiFi adapter. This seems to be combination of things. USB on Monterey does seem to prefer USB 3.0 and later. However, you can look up a USB 2.0 Hub to a Mac's USB 2.0 external ports and USB works fine off of that.

Seems Apple is changing the Bluetooth drivers and possibly BlueTool on every Beta release. I have also seen bluetooth entitlements and it seems that the Bluetooth Firmware needs to be uploaded by the system in order to work. These are just my observations. My guess is Apple is trying to beef up security on bluetooth. In the past there were bluetooth hardware keys and no security expert felt they were secure enough. This could be an effort to beef up security and bring back hardware security keys over BT. And this is probably due to the fact the M1 MacBook Air just has two USBC ports. a BT wireless key should not require taking up a port on each insertion.

In beta 1, my WiFi 802.11/BT4 LE Broadcom BCM card works. It gets read as a BCM 20702B0 BT card in Beta 1. After beta 1, it reads as a NULL device as does not get read in.

Then some clever users discovered they can route 2 wires off their BCM card and send that to USB 3.0 (USB 2.0 Hub should work as well). And then they put nail polish on the gold pins that are no longer needed. The rerouting seems to come from the adapter or from a small connector if your card or adapter has it.

Since I saw this working, but at this time did not want to modify my BCM cards, for 13.00 got a Lenovo PCIe WiFi 802.11ac/BT4.2 card that uses Intel Wireless instead and has drivers that can mesh with Apple's. I am also routing the USB to either USB 2.0 Hub or a USB 3.0 card using an 7-pin male adapter.

My card is working fine on B2 and B3. B2 even have Handoff working which I did not thing would be possible. Still investigating B3. My Motherboard in my 3,1 got its Serial # wiped just from sitting for a long time and I put its old Serial # back in using an Apple tool. Since then Handoff usually does not work. I can spoof another machine using OpenCore and that will usually result in gaining back Handoff. I do not use handoff much anyways. It is just nice to see it work when it does.

This bluetooth issue will remain a Cat and Mouse game until a public beta or RC1; whenever Apple decides it's done making changes.

I am hoping to analyze the drivers in beta 3 and compare to beta 4 and see what is different and if we can resurrect older drivers in future builds. My Beta 1 install has weird Kext's that don't have info.plists or signatures and was wanting to start with that, but will mostly likely start with Beta 3 and see unless beta 5 fixes it.

 

[Kirkafur]

I've never used one of these patchers to install MacOS on an unsupported machine, but would like to. I have a 2014 13" MBP (MacBookPro11,1), which supports Metal and which the OP suggests should have minimal issues.

If I were to install Monterey now, would I receive updates via the regular software update ever after? Or go through the rigamaroll each time I want to install a 12.X incremental update?

 

[Ausdauersportler]

I've never used one of these patchers to install MacOS on an unsupported machine, but would like to. I have a 2014 13" MBP (MacBookPro11,1), which supports Metal and which the OP suggests should have minimal issues.

If I were to install Monterey now, would I receive updates via the regular software update ever after? Or go through the rigamaroll each time I want to install a 12.X incremental update?

Check the online docs of the patchers - especially OCLP. It will answer all your questions. Check the first post of this thread in case you cannot find the link where OCLP has been hidden in the depth of the web.

 

[Kirkafur]

Will do. Some of the info I come across warns of a variety of things so I was hoping for reassurance that with that model there’d truly be minimal issues.

 

[macpro_mid2014]

I've never used one of these patchers to install MacOS on an unsupported machine, but would like to. I have a 2014 13" MBP (MacBookPro11,1), which supports Metal and which the OP suggests should have minimal issues.

If I were to install Monterey now, would I receive updates via the regular software update ever after? Or go through the rigamaroll each time I want to install a 12.X incremental update?

I would definitely wait for the first Monterey release in the Fall before installing it. Right now, I've been testing Monterey public beta in an external SSD. So far so good in a MacbookPro11,2. The only thing I still cannot do is OTA updates with the delta from Software Update. I need to download the 12GB installer and use it instead.

 

[Kirkafur]

Thank you for that! I’ll wait, since doing everything once and being able to rely on regular system updates afterward will be wonderful.

 

[Prohere7321]

I would definitely wait for the first Monterey release in the Fall before installing it. Right now, I've been testing Monterey public beta in an external SSD. So far so good in a MacbookPro11,2. The only thing I still cannot do is OTA updates with the delta from Software Update. I need to download the 12GB installer and use it instead.

There is a way to get delta updates. Before doing OTA update, unpatch system volume in OCLP first [Unpatch System Volume (Experimental)]. Once updated to a new beta, redo the Post-Install Volume Patch. This works to get delta updates because unpatching system volume reverts the system volume to original stock state, allowing delta updates to work just like unmodified system volume.

 

[Ausdauersportler]

There is a way to get delta updates. Before doing OTA update, unpatch system volume in OCLP first [Unpatch System Volume (Experimental)]. Once updated to a new beta, redo the Post-Install Volume Patch. This works to get delta updates because unpatching system volume reverts the system volume to original stock state, allowing delta updates to work just like unmodified system volume.

Did you try this yourself and was it successful?

 

[shafez]

Has anyone seen this, I got the following on boot then the os starts to boot as in the second image after a clean install.
how do I get back the normal black boot screen?,

 

[Ausdauersportler]

Has anyone seen this, I got the following on boot then the os starts to boot as in the second image after a clean install.
how do I get back the normal black boot screen?,

It cannot be a clean install since there is already a user configured.

This happens after mistyping a password three times in a row.

Follow the on screen instructions to reset your password.

1. boot into opencore
2. hit spacebar to see the recovery partitions
3. boot into the Big Sur recovery
4. open terminal app
5. enter resetpassoword command

and follow the instructions to reset your password

or just disable shift 🙂

 

[Prohere7321]

Did you try this yourself and was it successful?

Tested on MacBookPro9,2 from Beta 3 to 4, around 2GB+

 

[shafez]

It cannot be a clean install since there is already a user configured.

This happens after mistyping a password three times in a row.

Follow the on screen instructions to reset your password.

1. boot into opencore
2. hit spacebar to see the recovery partitions
3. boot into the Big Sur recovery
4. open terminal app
5. enter resetpassoword command

and follow the instructions to reset your password

or just disable shift 🙂

This is not the case, The first image is a boot login screen and after entering the correct password the the os starts to boot as in the second image.

 

[shafez]

I found the problem, it's a filevault login, I disabled it and everything is back to normal

 

[StarPlayrX]

I found the problem, it's a filevault login, I disabled it and everything is back to normal

I was just about to say that’s file vault.

 

[macpro_mid2014]

Tested on MacBookPro9,2 from Beta 3 to 4, around 2GB+

I never went through 3. Post-Install Volume Patch - 1. Patch System Volume because I don't think I need it for the MacBookPro11,2. BUT, I will try to Unpatch the system volume next time.

Thanks

 

[StarPlayrX]

I have not seen this before:

During one my startup locks I found:

"not adding subscription due to missing boot-arg wlan.iorsubscriptions"

and a few lines after

"setting fWlanRanging80MHzBootArg to 0"

 

[beruanges]

Has anyone seen this, I got the following on boot then the os starts to boot as in the second image after a clean install.
how do I get back the normal black boot screen?,

file vault

 

[Ausdauersportler]

I never went through 3. Post-Install Volume Patch - 1. Patch System Volume because I don't think I need it for the MacBookPro11,2. BUT, I will try to Unpatch the system volume next time.

Thanks

If you did not patch the system there is no need to unpatch it. There will be no difference at all. In general patching the root system volume breaks the ability to receive and apply the smaller delta upgrades.

Another reason might by:
If you are not enrolled to the Apple developer beta program you may not see those updates unless the public beta program will get an updated version of Monterey.

 

[macpro_mid2014]

If you did not patch the system there is no need to unpatch it. There will be no difference at all. In general patching the root system volume breaks the ability to receive and apply the smaller delta upgrades.

Another reason might by:
If you are not enrolled to the Apple developer beta program you may not see those updates unless the public beta program will get an updated version of Monterey.

The public beta gives me the same macOS build # which is now 21A5294g.

From Beta 2 (first Public Beta) to Beta 3 and from Beta 3 to Beta 4, the delta update was downloaded but the install process never happened:

1- Downloaded the delta update via Software Update;
2- Waited for the 30 minutes "preparing";
3- Black screen with an Apple logo and a progress bar, which lasted for few minutes without any time indication;
4- Automatic reboot;
5- Chose EFI from the list. macOS Installer did not appear in the second (EFI) menu (but only in the first menu together with the EFI option);
6- (When I choose macOS Installer in the first menu, I get an error (circle crossed on a black screen)😉
7- Then I chose the disk where I wanted the update to be installed;
8- The Apple logo with a 5 minutes progress bar appeared but after the reboot, macOS Installer was still in the first menu together with EFI;
9- After I chose EFI and then the disk where the update should have been installed, the system booted to Monterey Beta 3, NOT Beta 4;

When I use a USB stick or the complete install app (12GB), macOS Installer showed AFTER I chose EFI in the first boot menu.

Any idea what I am doing wrong?

 

[Ausdauersportler]

The public beta gives me the same macOS build # which is now 21A5294g.

From Beta 2 (first Public Beta) to Beta 3 and from Beta 3 to Beta 4, the delta update was downloaded but the install process never happened:

1- Downloaded the delta update via Software Update;
2- Waited for the 30 minutes "preparing";
3- Black screen with an Apple logo and a progress bar, which lasted for few minutes without any time indication;
4- Automatic reboot;
5- Chose EFI from the list. macOS Installer did not appear in the second (EFI) menu (but only in the first menu together with the EFI option);
6- (When I choose macOS Installer in the first menu, I get an error (circle crossed on a black screen)😉
7- Then I chose the disk where I wanted the update to be installed;
8- The Apple logo with a 5 minutes progress bar appeared but after the reboot, macOS Installer was still in the first menu together with EFI;
9- After I chose EFI and then the disk where the update should have been installed, the system booted to Monterey Beta 3, NOT Beta 4;

When I use a USB stick or the complete install app (12GB), macOS Installer showed AFTER I chose EFI in the first boot menu.

Any idea what I am doing wrong?

Hi!

I assume you applied the post install patches for the HD4000 after you installed Beta3. IMHO it is simply a glitch within the Apple software update if you were offered the delta updates. After all what I have learned here you cannot apply delta updates to a modified root system volume.

There are efforts to make this un-patching work to restore the original state Apple creates when doing a virgin clean installation, but my current level of understanding was that this is still not possible with Big Sur (works for Catalina and Mojave, because in these cases the root system volume has not been sealed using cryptographic hashes (like ZFS Sun Solaris filesystem) does.

My conclusion: This is an Apple bug which will be surely fixed soon. Then you will be offered the new full installers, only (when available).

P.S.:
I spent half a year on understanding/learning the patching of Big Sur with systems having a modified root system volume after the patching process using the micropatcher. During this time I was offered by Apple the full installers all the time and was wondering what could be broken with my system, unless some other users helped me here discussing this topic in detail, i.e. patching your volume <=> no delta upgrades

 

[macpro_mid2014]

Hi!

I assume you applied the post install patches for the HD4000 after you installed Beta3. IMHO it is simply a glitch within the Apple software update if you were offered the delta updates. After all what I have learned here you cannot apply delta updates to a modified root system volume.

There are efforts to make this un-patching work to restore the original state Apple creates when doing a virgin clean installation, but my current level of understanding was that this is still not possible with Big Sur (works for Catalina and Mojave, because in these cases the root system volume has not been sealed using cryptographic hashes (like ZFS Sun Solaris filesystem) does.

My conclusion: This is an Apple bug which will be surely fixed soon. Then you will be offered the new full installers, only (when available).

P.S.:
I spent half a year on understanding/learning the patching of Big Sur with systems having a modified root system volume after the patching process using the micropatcher. During this time I was offered by Apple the full installers all the time and was wondering what could be broken with my system, unless some other users helped me here discussing this topic in detail, i.e. patching you volume <=> no delta upgrades

As I said in Post #1,218, I never patched the system!
Anyways, I still have a couple of new ideas and will try them when I have Beta 5 available.

Thank you,

 

[rehkram]

Vielen Dank Ausdauersportler, alles klar.

That issue was confusing me and your explanation makes perfect sense. I'll be staying on the version I first installed (luckily it was the current one, beta 4). It's working very well for me, apart from having to reapply the workaround command via terminal to enable bluetooth after rebooting, which is not a big deal.