Yes, any applicable firmware updates will be applied, even if installing to an external disk.Hello,
I’d like to install Sonoma beta on an external drive, but will that update bridgeOS?
I’m assuming that bridgeOS is stored in the T2 chip itself, and thus that it will indeed be updated. Is that/does that seem correct?
Quite true, and this can have unforeseen consequences. My 2019 T2-equipped MBA shipped with Mojave, which was still installed on the internal drive a few years ago when I decided to install Big Sur to an external drive for testing. I subsequently discovered that attempting to boot into recovery without that particular external drive connected would reliably fail. Even reinstalling Mojave on the internal drive did not fix the problem.Yes, any applicable firmware updates will be applied, even if installing to an external disk.
This is why I don't install betas on production hardware, and I REALLY wish Apple provided a mechanism to downgrade firmware. The error you are referring to (and I know I'm really late to the party) is because the firmware won't let you boot a version of macOS that doesn't respect Activation LockQuite true, and this can have unforeseen consequences. My 2019 T2-equipped MBA shipped with Mojave, which was still installed on the internal drive a few years ago when I decided to install Big Sur to an external drive for testing. I subsequently discovered that attempting to boot into recovery without that particular external drive connected would reliably fail. Even reinstalling Mojave on the internal drive did not fix the problem.
At least on Apple Silicon Macs, doing a DFU restore to an older OS will also downgrade the firmware.This is why I don't install betas on production hardware, and I REALLY wish Apple provided a mechanism to downgrade firmware.
All the firmware? Including binary blobs on coprocessors?At least on Apple Silicon Macs, doing a DFU restore to an older OS will also downgrade the firmware.
All the firmware? Including binary blobs on coprocessors?
That's incorrect. Apple allows installation of any compatible version of macOS. They have not disabled any from booting or installing in full security mode as of now.BTW m1 macs will only allow installing old versions of the software if you "reduce security settings" in recovery mode.
Quite true, and this can have unforeseen consequences. My 2019 T2-equipped MBA shipped with Mojave, which was still installed on the internal drive a few years ago when I decided to install Big Sur to an external drive for testing. I subsequently discovered that attempting to boot into recovery without that particular external drive connected would reliably fail. Even reinstalling Mojave on the internal drive did not fix the problem.
Still true, I'm afraid. With Big Sur or later installed, booting to recovery works as expected. But with Mojave installed, attempts to boot to the local recovery partition always fail, as do attempts to do an internet recovery. Booting from a Mojave installer USB does work, so I keep one of those around for recovery purposes. To the best of my knowledge, there's no going back once the T2 firmware has been upgraded.I realize your post is a bit old now but curious is this still true? If I have a T2-equipped Mac (e.g. Mini 2018) running Mojave and I upgrade it to Big Sur or later will I be unable to downgrade it back to Mojave? This is the first I've heard that might be difficult.
Are you sure? I thought it worked provided you didn’t use Activation Lock. You get error 5101 if the device is AL’d but recovery isn’t AL aware (before Catalina), but it’s been a long time since I’ve tested it!Still true, I'm afraid. With Big Sur or later installed, booting to recovery works as expected. But with Mojave installed, attempts to boot to the local recovery partition always fail, as do attempts to do an internet recovery. Booting from a Mojave installer USB does work, so I keep one of those around for recovery purposes. To the best of my knowledge, there's no going back once the T2 firmware has been upgraded.
EDIT: Just to clarify, yes you'll be able to go back to Mojave, but the Mojave recovery partition will never work again.
As @chrfr said in post#5, wouldn’t Apple Configurator 2 restore Mojave firmware? Thought that was a cast iron method of completely (incl all firmware) restoring a machine back to factory state. Bootable installers will not roll back firmware.Still true, I'm afraid. With Big Sur or later installed, booting to recovery works as expected. But with Mojave installed, attempts to boot to the local recovery partition always fail, as do attempts to do an internet recovery. Booting from a Mojave installer USB does work, so I keep one of those around for recovery purposes. To the best of my knowledge, there's no going back once the T2 firmware has been upgraded.
EDIT: Just to clarify, yes you'll be able to go back to Mojave, but the Mojave recovery partition will never work again.
Configuratior cannot downgrade firmware on anything but Apple Silicon devices, so no, it won’t restore the firmware to that which finds Mojave in internet recovery because Mojave only runs on Intel Macs.As @chrfr said in post#5, wouldn’t Apple Configurator 2 restore Mojave firmware? Thought that was a cast iron method of completely (incl all firmware) restoring a machine back to factory state. Bootable installers will not roll back firmware.
Yes, I'm sure. Even after turning off Find My, trying to boot to recovery results in the machine immediately invoking internet recovery, which always fails with error -1008F. All I got from Apple Support was "oops..." As far as I'm aware, this problem affects only T2-equipped machines.Are you sure? I thought it worked provided you didn’t use Activation Lock. You get error 5101 if the device is AL’d but recovery isn’t AL aware (before Catalina), but it’s been a long time since I’ve tested it!
@MrMacintoshBlog posted this back in 2021, but there seems to be no signed firmware available corresponding to macOS 10.14.Configuratior cannot downgrade firmware on anything but Apple Silicon devices, so no, it won’t restore the firmware to that which finds Mojave in internet recovery because Mojave only runs on Intel Macs.
It doesn't matter anyway, as once Intel Mac firmware is updated, you can't downgrade it. If you had an old T2 Mac that was still on High Sierra and you updated that to Mojave it'd end up with a Mojave version of firmware– signing isn't relevant here. Mojave never ran on Apple Silicon Macs so there'd be no firmware for those no matter what.@MrMacintoshBlog posted this back in 2021, but there seems to be no signed firmware available corresponding to macOS 10.14.
Not strictly correct in the case of T2 if you believe the article I linked to, but I agree that it's irrelevant for my situation.It doesn't matter anyway, as once Intel Mac firmware is updated, you can't downgrade it.