If you've replaced the Apple SSD in your Mac with a third-party model and attempt to install Monterey, you may receive an error like:
To resolve, reinstall an Apple SSD, install Monterey, reinstall your third-party SSD, and install Monterey:
Results of some cursory testing with a MacBook Air (13-inch, Early 2015) which was still running macOS 10.12 Sierra with Boot ROM version MBA71.0166.B02:
Maleficent_Stranger's reddit comment, the bulk of which is reproduced here verbatim, offers more detail:
If you already changed your ssd back in early mojave or high sierra time, you firmware was not updated since that time, because, only after 195.xxx BootRom version (which came together with Catalina 10.15.7) Apple enable firmware upgrade through third party ssd. Prior to that, you can't update firmware using third party, only through original apple ssd. So, something like 122.xxx , 162.xxx, or something older like MBA.xxx & MBP.xxxx , you won't be able to update to Monterey right away, because the firmware wont't allow new version installation on 3rd party ssd. Installing Catalina or BigSur first won't help, since it won't update your firmware either.
You should have no problem installing Monterey if your BootRom version is already on 4xx.xxx digit. Regardless what SSD is installed in your Macbook.
I do several Monterey upgrade on my customer's macbook which already have my custom branded 3rd party ssd inside, and all installed just fine. Key is, all those units already on BigSur firmware version (4xx.xxx)
If you already in 195.xxx BootRom , you can manually upgrade your firmware through terminal as well. As long as you have the firmware file (can be extracted from BigSur/Monterey installer itself)
For those without access to an Apple SSD, a possible workaround is described separately by u/lbableck and 传说中的慕容, though it requires firmware version ≥195.0.0.0.0 already be installed (check "System Firmware Version" (≥macOS 11) or "Boot ROM Version" (≤macOS 10.15) in the Hardware section of "/Applications/Utilities/System Information.app"):
Disable SIP (csrutil disable in macOS Recovery)
Mount "Install macOS Monterey.app/Contents/SharedSupport/SharedSupport.dmg" (if you receive a "Resource busy" error, it may already be mounted)
Extract the .fd or .scap file which corresponds to your Mac's model identifier (as reported in "System Information.app") from "/Volumes/Shared Support/com_apple_MobileAsset_MacSoftwareUpdate/40charstring.zip/AssetData/boot/EFI/EFIPayloads/"
sudo bless -mount / -firmware /path/to/your/extracted/fd/or/scap --verbose -recovery
Following successful execution, shut down Mac then turn it back on to begin fimware update process (the Mac may reboot several times)
Upon successful completion, reenable SIP (csrutil enable in macOS Recovery)
Install Monterey
Xaphier and others have reported frequent crashes after installing Monterey on a third-party SSD:
My Mid 2015 15" MBP with 1TB Sabrent SSD (Sintech adapter) started to crash a lot after upgrading to Monterey. I had almost 0 crashes during Big Sur, but now I get 3 to 4 crashes a day, very frustrating. I updated to Monterey by swapping the drive to original Apple SSD and update to Monterey, swap to Sabrent SSD with adapter and update to Monterey again.
OWC support suggests same workaround (reinstall Apple SSD, install Monterey, reinstall OWC SSD, install Monterey)
This tweet claims that the original SSD (not just any Apple SSD) must be used because, "Apple BridgeOS right now verifying original SSD." However, Alexandre Torres points out that:
The tweet about iMac 2017 and BridgeOS is wrong in so many levels, from the start, the 1st iMac to have T2 is 2020 iMac 27". Without T2, no BridgeOS at all. Even if he is talking about iMac Pro, the SSD from MBP won't even fit (iMac Pro uses NAND modules, same as 2019 Mac Pro).
Reminiscent of:
/mac | Oct 27, 2021