My guess is that they should have updated BridgeOS before MacOS. Whatever certificate they used to sign the new MacOS wasn't accepted by the old BridgeOS, so the T2 refused to boot because security.
That's just from looking at mrmacintosh's post above.
If that's the case, they need to look at their production packaging process. Back in the old days before the T2 the installer would update your firmware first then reboot and install the update. That must have either gotten lost or changed in this update, which is unfortunate.
That's just from looking at mrmacintosh's post above.
If that's the case, they need to look at their production packaging process. Back in the old days before the T2 the installer would update your firmware first then reboot and install the update. That must have either gotten lost or changed in this update, which is unfortunate.