The core problem is that the BridgeOS firmware on the T1 chip is now mismatched and inactive. The only way to fix this is to use another Mac to force the correct firmware and a supported OS onto your machine using Apple Configurator 2.
Prerequisites:
Another Mac (This is mandatory. You will need it to create a revive/restore image).
A USB-C to USB-C cable (Thunderbolt 3 cable is highly recommended for reliability).
A second USB-C cable for power (or use the power adapter on the target MacBook).
Apple Configurator 2 (Free on the App Store, install it on the other Mac).
Step-by-Step Guide: DFU Mode Revive/Restore
This process will either Revive (attempts to restore firmware and OS without erasing user data) or Restore (completely wipes the machine and installs the latest supported OS). Try Revive first.
Step 1: Prepare the Helper Mac
On your other Mac, ensure Apple Configurator 2 is installed.
Open Apple Configurator 2.
Connect this Mac to the internet.
Step 2: Prepare Your Bricked MacBook Pro
Shut down your problematic MacBook Pro completely.
Connect its power adapter.
Step 3: Enter DFU Mode
This is the most crucial step. The timing can be tricky.
Press and hold the following three keys simultaneously on your MacBook Pro for 3 seconds:
Right Shift Key
Left Option (Alt) Key
Left Control Key
After 3 seconds, keep holding those three keys and now also press and hold the Power Button (Touch ID) for another 6 seconds.
After the 6 seconds, release only the Power Button. Continue holding the Shift, Option, and Control keys for another 5-10 seconds.
If done correctly, the screen will remain completely black. The MacBook Pro will not show any signs of life. This is normal. It is now in DFU (Device Firmware Update) mode.
Step 4: Connect and Recognize
Take your USB-C to USB-C (Thunderbolt 3) cable and connect it from a USB-C port on the helper Mac to the top-left USB-C port on your bricked MacBook Pro.
In Apple Configurator 2 on the helper Mac, you should see your MacBook Pro appear as a connected device. It will likely show up with a generic icon and name or in Recovery mode.
Step 5: Revive or Restore
Recommended First Step: REVIVE
In Apple Configurator 2, hold the Option key and click the Revive Device button.
This will download the latest compatible
BridgeOSfirmware and a signed IPSW restore file for your Mac model from Apple's servers. It will attempt to flash the T1 chip and restore the OS without erasing your data. This process takes 15-30 minutes. The Mac will reboot several times.
If Revive Fails or You Want a Clean Slate: RESTORE
WARNING: This will erase ALL data on the machine.
In Apple Configurator 2, simply click the Restore Device button.
This will perform a clean installation of the latest macOS version that is officially supported by your MacBook Pro (likely macOS Monterey 12.x or Ventura 13.x). This is the guaranteed fix.
Step 6: Complete Setup
Once the process is complete, your MacBook Pro will reboot. If you performed a Restore, it will boot into the Setup Assistant as if it were a new machine. If you performed a Revive, it should hopefully boot back into your existing installation, but now with a functional Touch Bar, Touch ID, and keyboard.
What If You Don't Have a Second Mac?
Your options are limited and less ideal:
Visit an Apple Store or AASP: Explain that your Mac is "bricked and needs a DFU restore." They have the tools to do this for you. Be aware there might be a service fee if the machine is out of warranty.
Use a Friend's Mac: This is the most common solution. The process with Apple Configurator 2 is relatively quick once you have the hardware.
Paired Mac Rentals: Some independent repair shops offer a "DFU restore" as a service for a fee.
Important Lesson Learned
Never install an OS version on a T1/T2 Mac that is not listed in its official support list on Apple's website. The secure enclave (BridgeOS) is tightly coupled to the main OS, and breaking that link causes the exact problem you experienced.
Your path forward is clear: use the DFU restore process with a second Mac to return to an official, supported version of macOS. This is the only way to get your Touch Bar MacBook Pro back to 100% functionality.
Apple made some changes when they released the first beta of macOS Sequoia 15.7.
ISSUE #1: Due to changes in the way that Sequoia 15.7 is listed in the SUS Catalog, OCLP 2.4.0 thinks that macOS Sequoia 15.7 is the latest public release. The problem with that is, 15.7 (24G207) is a BETA Version.
ISSUE #2: Apple has not released the required Kernel Debug Kit for macOS Sequoia 15.6, 15.7 Beta and macOS Tahoe Beta 2,3,4,5 or 6.
PROBLEM #1: Any new users creating a Sequoia OCLP installer will be prompted to download 15.7 as the latest OS version. Once installed, the 2nd problem occurs.
PROBLEM #2: When the 15.7 system comes back up, OCLP 2.4.0 will not allow the root patches to be installed on KDK required Macs. This is due to the built in protection of OCLP that will not allow a KDK that is older than 1 previous versions i.e N-1. This built in protection prevents the possibility of 15.5 KDK drivers not being compatible with 15.7 causing system issues. The error that you will get is "Error: No KDKs found for 24G207 (15.7) Sequoia"
SOLUTION: As of now, the solution is to backup all your data and create and perform an erase and install of 15.6 (Direct downgrades with a previous OS version are now allowed by Apple). It is unknown if or at all Apple will release the 15.6 or 15.7 Beta KDK. So if you install 15.6, the 15.5 KDK will be pulled and will work fine.
SOLUTION #2: It is possible that Apple will release a KDK for 15.6 and 15.7. If they do that would fix things. If not it is also possible that the OCLP devs release a hot fix for OCLP to prevent 15.7 from being shown at the create installer screen.
Other Apple changes after 15.7 Beta was released:
macOS Ventura is no longer supported (no new security updates will be released for this OS)
macOS Sequoia is now the number 2 supported OS under Tahoe even though Tahoe is has not been released (Sonoma is 3)
Safari Beta was released for ONLY for Sequoia and Sonoma further confirming that Ventura is dead.
The Sequoia 15.7 Beta has been classified as an RC or Release Candidate. Normally a Release Candidate is the final beta and has a proper non beta build version and is ready for release.
Let me know if you have any questions.
[link] [comments]
Problem is, if you have a MacBook with the Touch Bar (T1 chip), then deleting the OS will also delete the security driver that is no longer included with the OS since these Macs are out of support. Unfortunately, I grabbed the 15.7 since it was listed without checking if it was an official release first. Now I'm in a half supported state and cannot go back and staying here is painful.
ReplyDeleteOf course. This is a classic and very serious issue with older T1/T2-chip Macs and unsupported macOS versions. You've essentially stranded the Touch Bar and its associated security/input functions by installing an OS that doesn't include the necessary drivers and firmware.
ReplyDelete