Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
We have at least one report where an experienced user needed to go back to the latest OCLP release 0.3.1 to get macOS OTA updates displayed in software update. You might try that as well.
I saw that post and that does work going to 0.3.1 but then when I attempted to go back to 0.3.2 it wouldn't boot.
yes I did delete post patching before going back to 0.3.1 and back to 0.3.2
I was just seeing if there was another possible fix to this issue
 
  • Like
Reactions: K two
AHOY! ? Recent versions of OCLP_032N will not see the OTA installer for macOS 12.1 beta 4 on certain Macs. The Mini3,1 is one of them. Fortunately, gibMacOS-master came to the rescue. With createinstallmedia and the always reliable HP USB2 plug, the install atop Beta 3 proceeded as intended. Performing OCLP Step #3 from the last 032N OFFLINE VARIANT semi-completed the installation. So far, Beta 4 is pretty and responive. All browsers work as intended. Once, the most recent OCLP_032N was properly cold-boot re-installed.:rolleyes:

12.1B4 nice.jpg
 
Hey everyone,
I'm reporting back to say I've successfully upgraded my mini 6,1 to 12.0.1 OTA with absolutely no issues. Everything went smoothly; and wifi, bluetooth, airplay, handoff, etc. all function perfectly.

I got nervous for a moment when the second reboot seemed to stall at 50%, but it picked back up and loaded normally.

Siri's voice sounded strange at first (very robotic and unnatural), but I just needed to go into Siri settings and select the voice again.

Absolutely fantastic now, and thank you all for the work and guidance with this. You've saved my little mini from the junkyard and proved that even older machines are still perfectly viable today. This machine continues as my daily driver, and I have you all to thank!
 
  • Like
Reactions: jdmc and K two
Hey everyone,
I'm reporting back to say I've successfully upgraded my mini 6,1 to 12.0.1 OTA with absolutely no issues. Everything went smoothly; and wifi, bluetooth, airplay, handoff, etc. all function perfectly.

I got nervous for a moment when the second reboot seemed to stall at 50%, but it picked back up and loaded normally.

Siri's voice sounded strange at first (very robotic and unnatural), but I just needed to go into Siri settings and select the voice again.

Absolutely fantastic now, and thank you all for the work and guidance with this. You've saved my little mini from the junkyard and proved that even older machines are still perfectly viable today. This machine continues as my daily driver, and I have you all to thank!
I have the same system, can you check the sharing preferences in System Preferences and see if there is an option for airplay receiver?

like in this post: https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30666314
 
Monterey B4 21C5045a working great on all my machines.

Note:
Safari is working again on my MBpro 6,1 as well!!!!! WOW.
Didn't try Firefox.
Chrome always worked.
 
  • Like
Reactions: K two
Beta 4 working nicely so far after upgrading via OTA. USB 3.0 ports (via ExpressCard/34) also working on a MacBook Pro 4,1 as before with 12.0.1.
View attachment 1922744
Did a storage medium also work on the expresscard USB3 ports? In my case (using a nanoTech expresscard):
- mouse works well on USB3
- when connecting a memory stick or SSD to USB3, the trackpad pointer stops moving after some 10sec and need to force-poweroff
- when connecting such a device already before booting, the PCI expresscard and its USB3 ports are disabled when the system comes up.
Tried booting with OCLP 0.3.1 and with latest 0.3.2n. System os root-patched with latest 0.3.2n.

The expresscard works well in Big Sur, but in none of the Monterey versions so far.

In Big Sur /S/L/E there is a driver called AppleUSBXHCIARM.kext, not present in Mojave. Put it there manually (jackluke's BigSurmountsrw.app), but has no effect.

Trying to debug...
 

Attachments

  • Bildschirmfoto 2021-12-04 um 11.17.02.png
    Bildschirmfoto 2021-12-04 um 11.17.02.png
    137.2 KB · Views: 68
  • Bildschirmfoto 2021-12-04 um 10.57.51.png
    Bildschirmfoto 2021-12-04 um 10.57.51.png
    166.6 KB · Views: 89
AHOY! macOS Finder version 12.1 has a built-in FTP D/L client which FTPs directly to the Downloads ƒ. (Other Finder versions may also have this capability?) Just now FTP'd a D/L of 4 GB very fast w/no interruptions. This very useful Finder capability may not be widely known? Selecting a FTP link in any browser will trigger the D/L complete with a Finder progress indicator and guesstimate. :cool:

?️ Why may this be important? Most browsers dropped direct FTP support, years ago when some FTP sites began to shift over to HTTP which meant an additional separate application was required to supplant the missing protocol.
For early legacy Mac users and collectors this Finder feature is really useful.
 
Last edited:
After rebooting several times, the only downside I've noticed is that boot times have more than doubled from Big Sur.

On Big Sur my boot time was around one minute.
On Monterey, I just clocked it at 3 minutes 40 seconds.

I tried to look at verbose mode, but I didn't notice any warnings or errors at the pinch points, though I may not know what to look for.

In any case, once the system does boot up, it's fast and responsive (even more so than Big Sur).
I'll just need to turn the system on in the morning before I make breakfast ?
 
Did a storage medium also work on the expresscard USB3 ports? In my case (using a nanoTech expresscard):
- mouse works well on USB3
- when connecting a memory stick or SSD to USB3, the trackpad pointer stops moving after some 10sec and need to force-poweroff
Connected to the expressCard (also nanoTech) I have an external 8TB HDD where I read from and write to with USB3 speeds, works without problems, the same for a SanDisk USB3 flash drive. The only thing – but that was always the case – sometimes, when a drive does not mount, I unplug the cable and stick it to the other port, that normally works, if even that doesen’t help, then a system reboot with the drive already plugged in does it.

It’s really interesting, that sometimes more or less the same machines show different anomalies. :rolleyes:

EDIT: releasing the card and pushing it back in, while booted up, may also be an option to try.
 
Last edited:
  • Like
Reactions: hvds
Did a storage medium also work on the expresscard USB3 ports? In my case (using a nanoTech expresscard)

Just one remark on the nanoTECH USB 3.0 ExpressCard|34: Contrary to my Sonnettech Tempo Duo USB3/SATA ExpressCard|34 (TSATA6USB3-E34) it doesn't have an auxiliary power input and I've noticed it doesn't deliver enough milliamps to 2,5" USB 3.0 HDs or SSDs, at least not in my MBP5,2. I've therefore ended up buying an additional USB 3.0 Micro-B Y-cable (Delock 82909) that is now sourcing further power from one of my MBP5,2's USB 2.0 ports. That has solved the problems with 2,5" USB 3.0 HDs or SSDs I had before.

It doesn't explain why your nanoTECH-connected storage media is working fine under Big Sur, but not under Monterey, of course. In theory, a changed energy management might lower the power delivery to usb 3.0 storage devices further, but I don't think that's a very probable scenario here. Nonetheless, if you happen to have such a cable, it might be worth trying what happens when you use it when connecting the problematic USB3 storage media.
 
Last edited:
MBP 8,1 working well on 12.1 Beta 4 using latest OCLP 3.2 GitHub code
had to install beta using gibMacOS-master as updater was not seeing the beta on 3.2 but does on 3.1
 
Just one remark on the nanoTECH USB 3.0 ExpressCard|34: Contrary to my Sonnettech Tempo Duo USB3/SATA ExpressCard|34 (TSATA6USB3-E34) it doesn't have an auxiliary power input and I've noticed it doesn't deliver enough milliamps to 2,5" USB 3.0 HDs or SSDs, at least not in my MBP5,2. I've therefore ended up buying an additional USB 3.0 Micro-B Y-cable (Delock 82909) that is now sourcing further power from one of my MBP5,2's USB 2.0 ports. That has solved the problems with 2,5" USB 3.0 HDs or SSDs I had before.

It doesn't explain why your nanoTECH-connected storage media is working fine under Big Sur, but not under Monterey, of course. In theory, a changed energy management might lower the power delivery to usb 3.0 storage devices further, but I don't think that's a very probable scenario here. Nonetheless, if you happen to have such a cable, it might be worth trying what happens when you use it when connecting the problematic USB3 storage media.
Yes, it sounds like a power problem.
And I had one with a certain HDD already under Catalina; but therefore I do a similar trick as you do, with an extra cable taking extra power from a USB2 connector (not with a Y, but I've verified that the power lines of the two USB3 ports are directly wired on the card, so I connect one of the USB3s to a USB2 powerwise).
Still it is not excluded that a changed power management makes it fail under Monterey. Thanks for the hint.
@macinfo , thanks. I released and pushed back in the expresscard, which is also reflected in the card symbol in the menu bar. Still, connecting any storage device to USB3 after that, stops cursor response before long, and before the device is visible in the Finder.
 
  • Like
Reactions: makra
Sorry if I missed this information, but I was searching and trying to find an answer in this thread.

MacBookPro mid 2012 (9,2), upgraded RAM & HD (Samsung 850 Pro SSD). I was able to update Catalina to Big Sur using OCLP 0.3.1 TUI. When trying to update to Monterey using the same process I'm getting stuck at the 'Firmware Update' error when the install assistant starts. I've tried with SMBIOS at moderate & advanced with no difference. I've done both with SIP disabled when built with no difference.

Updating using a USB 2.0 32gb drive. Any help appreciated. Not hating Big Sur, but would like to be able to use Monterey.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.