Hey! Thanks, that worked indeed! Had to try a couple of times, but eventually Bluetooth came back on. Thanks!
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
Sincerely it is a little mess and hard to handle
Firstly I don't know why my principal partition is not able to boot natively because I don't install OCLP on it
Anyway I've tried to create installer in my SD as usual, terminal command "createinstallmedia" but when I try to boot from this SD (Native) again I have the forbidden signal and a startup error
Summarize
- Principal partition, Big Sur micropached but not able to boot native
- Secondary partition, Catalina, supported macOS for maintain 32 bits apps, it could be booted native
- USB with Windows on the Go, it boot native
- SD for installing macOS now only works through EFI boot. I install OCLP on it, maybe do I need to force uninstall OCLP
- External SSD for macOS proofs
Addendum, I save OCLP in a old USB for get the mode to force EFI boots and load my principal partition just in case
To boot into the old micropatched Big Sur you need to install and boot the micropatcher EFI (step 7 of the instructions, using install_setvars.sh).
My advice:
Convert your Big Sur installation from micropatcher to OCLP by reinstalling it using the same or a more recent version of Big Sur. You should create a backup of your data, just in case....
Last edited:
As written in my signature below, it is a RX480, but displayed as Radeon Pro 570 from the vBIOS.
Have you done any additionsl step? Does not work for me…. EDIT: Worked after 20 tries.
Very appreciate, sorry for the inconvenience but I think I need improve my knowings
* I apply install_setvars.h over SD bootable but later on if I try to boot "native" with that SD installer I get forbidden signal.
* Not sure how could I convert Big Sur from micro patcher to OCLP, by now, even when I'm not conscious of have done the Big Sur partition con only be boot from EFI menu and OTA recognize that there is a update ready (this never happened before). May I patch system volume with OpenCore Patcher over the the micropatcher system directly?
* The last question, I'm trying MountEFI but when I select partition to mount in the script th Finder don't show anything nor Disk Utility
More troubles with Bluetooth under Beta 4.
iMac 13,2 late 2012.
OTA update from Beta 3 ran without problems. When first booted, OS and apps were very slow but after 30 minutes or so the activity light on the external HDD quietened down and performance improved.
According to System Preferences and the Menu Bar, Bluetooth is not running. However, BT keyboard and mouse both work, apart from scrolling with the Magic Mouse. Not possible to turn Bluetooth on or off in either System Preferences or the Menu Bar.
The suggested additional terminal command did not do anything, even after 20 attempts. No improvement after a couple of restarts.
With my 20702B0 card. If forget which BRCM 93xxxx card it is, but it is one of those knockoffs from China. Not a true broadcom card. It works fine under Beta 1, not in any of the other betas. I too am wondering if the newer and faster official broadcom cards work under the other betas. I may bite the bullet and get one. They not cheap and I question of the ones on eBay is official cards or not.
Proving things, I begin to understand some things (+) but not others (-)
+ supported system seems to work as usual (Mojave, and Catalina installer works from Mac Boot Picker)
+ unsupported system doesn't boot from Mac Boot Picker and need to use OpenCore Picker
- I can't understand why it's happening with Big Sur previous installation with micropatcher if I don't touch anything in this partition by now
- I can't understand why if I prepare USB installer Big Sur with micropatcher I can't load it from Mac Boot Picker as before and it shows the forbidden signal when I run it
+ Big Sur "micropatcher" needs boot from OpenCore Picker so I need a USB or something with OpenCore in the EFI so could be good idea install it in a internal SSD because if I loose or erase the actual USB I would be big problems
- for doing that I'm not sure I it's enough running OpenCore Patcher and select the internal Big Sur partition that already works or I need to reinstall it (I guess that I might install it directly)
- I was NOT able to install Big Sur or Monterrey with OpenCore patch in a external unit right now. I prepare USB installer as tutorial says. "createmedia", opencore over USB, boot, select OpenCore Picker, select Install, accept as always, begin the installation ... good ... first boot. Again press "alt" select opencore picker, select "install macOS" that is the name of external unit, again the typical screen with apple and the minutes to go ... but when it goes nothing happen, restart system, select the unit again through opencore picker, start the apple and a bar filling but again at the end nothing happens and restart system
This blow my mind, maybe should I erase NVRAM?
You mix and confuse a lot of things!
The Big Sur / Monterey installations take a long long time, sometimes more than an hour although it claims to take 29 minutes, only. So stopping it by forcing a restart does not make any sense. Just wait!
If you want to get back to your old working configuration you should try a PRAM reset and follow step 9 of the micropatcher online docs.
Mixing OCLP and micropatcher is not a good idea. Please check the micropatcher online docs, again. Since you got it installed you will get it repaired the same way.
Thanks a lot
Just to clarify I don’t stop installation to reboot anyway, just the process in self do it. The matter is that when install reboot the Mac choose principal partition to start and not continuing installation process. So I force the right one rebooting again cause I’m installing Monterey in a external partition but I don’t get do it with OCPL as I get with micropatcher. Even if I format the external partition previously
I think that I’m gonna stay with OCLP to progress in the future, so better apply in my principal Big Sur partition for be safe in the future for any accidentally lack of boot. Am I right?
1. Use the disk utility which comes with the installer to prepare your APFS partition on the new target disk. Never use older versions of it with later macOS versions.
2. Press CRTL while selecting the OC EFI on the first boot, that way you make it the default EFI to boot from.
3. If you have a working backup install OC on your main disk and reinstall Big Sur.
4. Monterey as currently some/a lot bugs (mostly BT related) - so do not expect a swift experience this early in the Beta test
Last edited:
The oldest officially supported MBAs have 4GB RAM on their base models so yes.
In addition, I ran it on a C2D MacBook Air with only 2GB RAM and SSD.
Not a joy (also for unpatched GPU reasons), but not worse than Mojave...Catalina on this machine in terms of memory shortage...
Finally I got it. The key is to reboot four times.
first when save files on to partition
Second when do the installation
Third one with correct name in partirion
Fourth and last to enter in system actually
maybe I stopped at third one before
Unless you have corrupted the install, The key is to re-boot as many times as it takes to get to a desktop.
Installed Monterey beta successfully on my retina mid 2012 MacBookPro10,1
I was determined to end up with a dual boot config (Big Sur & Monterey beta) on the internal 1 TB SSD but found it hard to find any info on how to do that. In case anyone would like to know I ended up doing the following:
I was determined to end up with a dual boot config (Big Sur & Monterey beta) on the internal 1 TB SSD but found it hard to find any info on how to do that. In case anyone would like to know I ended up doing the following:
- On Big Sur downloaded the Monterey beta installer
- Created a new APFS dynamic volume (i.e. not a hard partition, I wanted to use the macOS feature where it allocates storage on the fly) named 'Beta' on the internal SSD
- Created an installer+OCLP USB drive per procedures on the Dortania site and plugged it in
- Told the Mac via Preferences - Startup Disk to boot off the USB drive
- Rebooted, selecting 'install Monterey beta' from the picker
- At some point in the boot sequence it asks you where you want to install it, and glory Hallelujah, there was the new Beta volume available for selection so I selected it
- Monterey installed and booted to the Beta volume
- No sign of OCLP (I'm still not clear on what it does at installation time and where it does it, I have to assume it just does its model spoofing). Fortunately the MBP Monterey session was working well enough without any OCLP runtime intervention that I was able to download the OCLP TUI and build & install it on the volume. Rebooted and things noticeably improved
- Ran data migration from the Big Sur volume to the Beta volume, AOK
- Later, ran OCLP post install patching for enabling internal HD4000 graphics card
Last edited:
Successfully updated to Monterey on 10,1 its post-install patches applied (ie: Intel 4000 gfx), almost all good except VMWare Fusion 12.1.2. Any time I try to launch a virtual host, I receive the nefarious - "Transport (VMDB) error -14: Pipe connection has been broken." error. I have updated the permissions on /tmp (/private/tmp) to 777 but that did not fix the issue. Anyone have any luck getting Fusion to run on Monterey?
I think I found some bug in the OCLP most likely. I have to investigate further. Om my MBP11,3 Monterey beta 4 I can't play Amazon prime movies. Every movie I have tried comes with an error. After rebooting to Monterey without OC (
-no_compat_check only) all movies play fine.
Almost the same Bluetooth problems here on my MBP 10,1. The suggested 'killall' command seems to have no effect. BT showing as 'off' in Preferences, will not switch on. Bizarrely, the Apple Magic 2 Keyboard works despite that. Magic Mouse 2 does not work at all.
System report shows:
Code:
Bluetooth Controller:
Address: NULL
State: Off
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported services: 0x381139 < HFP AVRCP A2DP HID NtSv NtCl AACP GATT Serial >
Transport: USB
Vendor ID: 0x004C (Apple)(Edit: Now working, solution was this post from RogueB)
Last edited:
check USB and see if you see Composite devices. If a bluetooth device is not using the correct driver, it may be available as a Composite device and runs in a generic "windows" no driver like mode.
Last edited:
I get the same thing just usually get UART instead of USB. Tried USB dongles and they don't take. This NULL controller seems to take over in Beta 2 - 4 for me. Beta 1 is fine. I would try to use drivers from Beta 1 for USB HID, but my installation is missing files for the extensions. Either a bad install or B1 is just weird.
Hello to all,
Short report on installation of Monterey Beta4 on iMac 13,2 via OCLP 0.2.4 TUI.
Much as others have reported, installs fine, even through OTA, but Bluetooth is non-operational for any actions other then basic window focus, and application launch from the dock. It [Bluetooth] also can not be turned on via preferences.
An old, wired, USB mouse also fails to function properly.
I had to revert to Monterey Beta 3, via USB thumb drive which was build with "createinstallmedia" command and Monterey beta 3 full installer package. While that re-installation was successful (over Monterey beta 4), and without data loss, system appears to react slower to some commands, graphics in particular.
Hope this may be of help.
(Just a bit of trivia: Monetery 4 installs on C2D laptop, Macbook Pro 5,2, and works like a pre internet machine - no connections. There is also no graphic acceleration)
Short report on installation of Monterey Beta4 on iMac 13,2 via OCLP 0.2.4 TUI.
Much as others have reported, installs fine, even through OTA, but Bluetooth is non-operational for any actions other then basic window focus, and application launch from the dock. It [Bluetooth] also can not be turned on via preferences.
An old, wired, USB mouse also fails to function properly.
I had to revert to Monterey Beta 3, via USB thumb drive which was build with "createinstallmedia" command and Monterey beta 3 full installer package. While that re-installation was successful (over Monterey beta 4), and without data loss, system appears to react slower to some commands, graphics in particular.
Hope this may be of help.
(Just a bit of trivia: Monetery 4 installs on C2D laptop, Macbook Pro 5,2, and works like a pre internet machine - no connections. There is also no graphic acceleration)
From my experience (MBP 9,2)
1. I run sudo killall -9 BlueTool bluetoothd once in Terminal. Enter password.
2. Then once again. Without putting in the password.
3. Toggle bluetooth from menubar. Wait a few moments. max 10 secs
4. All devices come back on automatically.
It always works after two times and toggling the button in menubar. At the same time, when I have sys prefs open, all devices appear automatically.