I have a 2018 MBP 2.2 512Go 555X.
I took him to the apple store, they change the battery and the Keyboard.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2018 MacBook Pros crashing with "Bridge OS" error
- Thread starter kryptticAZ
- Start date
- Sort by reaction score
I have a 2018 MBP 2.2 512Go 555X.
I took him to the apple store, they change the battery and the Keyboard.
The latest supplementary update has made my computer feel brand new. (technically it is brand new being a 2019 model but you get the idea). Hopefully, this isn't just placebo.
Testing now! Had to download manually from Apple's website.
What's strange is my build number was already that latest, though the MBP did not refuse the installation.
https://support.apple.com/kb/DL2015?locale=en_GB&viewlocale=en_US
Last edited by a moderator:
I just pulled a brand new 2019 MBP 15" out of the box. And guess what?
Installed all updates then installed chrome, ran hangouts and the laptop kernel panic'd within a minute or two.
APPLE PLEASE FIX WTF.
Called Mac store their option is to replace the logic board (HAHA)
Installed all updates then installed chrome, ran hangouts and the laptop kernel panic'd within a minute or two.
APPLE PLEASE FIX WTF.
Called Mac store their option is to replace the logic board (HAHA)
This is more than ridiculous tbh! How come they are having so much trouble fixing this issue? It's been over a year now :/
Man... I was hoping my own machine did not have the same issue, though.
My personal work 2018 15" mpb also just kernel panic'd after joining a hangouts on battery power.
Brand new unboxed 2019's having the same issue as I previously posted.
My personal work 2018 15" mpb also just kernel panic'd after joining a hangouts on battery power.
Brand new unboxed 2019's having the same issue as I previously posted.
Had my first crash yesterday with a MBP 2018, 15", right before the update to macOS Mojave 10.14.6.
Computer was working flawless for four months. After half an hour using FaceTime, it made a "whoosh" sound and crashed, turned black, and restarted immediately. Then 3-4 more crashes (always trying to use FaceTime). Stopped at some point, and did the software update. No crash so far, though also no FaceTime so far.
Computer was working flawless for four months. After half an hour using FaceTime, it made a "whoosh" sound and crashed, turned black, and restarted immediately. Then 3-4 more crashes (always trying to use FaceTime). Stopped at some point, and did the software update. No crash so far, though also no FaceTime so far.
MBP 15" 2018 with j680ap T2 chip. Tried a LOT to stop it from:
1. Freezes (10-40 s) in Chrome.
2. Reboots after 10-15 min of sleep.
3. External USB-C monitor (LG Ultrafine 21.5) not going to sleep.
Updated the laptop from 10.14.6 to 10.15 Beta 5. It was my huge mistake.
Update triggered the iBridge update to version 4.0 Beta (17P50521d).
Cannot recommend this to anyone:
+ no more freezes!
+ external monitor working good.
- it is not charging. Even showing that charger is connected.
- !!! Laptop not powering up from sleep mode !!! (5-10 lid open-close cycles and many power button pushes returned it to life)
- Final one = not powering up at all -> I started it in DFU mode. And it's the start of an interesting part:
Apple Configurator Beta is stupid. It tried to downgrade 4.0 Beta iBridge Firmware to 3.6 Release. But it is not allowed! So it bricked the T2 to Recovery mode. Every other attempt the Configurator tried to install 3.6:
US Desc: backwards update not allowed: 17P50521d -> 16PXXX
Domain : AMRestoreErrorDomain
Code : 0x4F (79)
It was a complete disaster.
MB and TouchBar boards were replaced in 3 days. And the new board having the same j680ap T2 chip! Bad luck for me.
A friend of mine got his 2018 15" MBP recently with upgraded j780ap T2 chip and having no problems so far.
Most recent (August, 22) build of T2 version 3.6 (16P6571) version's release noticing fixes to sleep mode issues.
No luck for me. All 3 initial problems are still here.
I could confirm the 2 versions of MBP 15" 2018:
| Processor code | iBridge model ID | Installed machine model ID |
|-------------------|-------------------|-------------------------------|
| J137AP | iBridge2,1 | iMacPro1,1 |
| J680AP | iBridge2,3 | MacBookPro15,1 |
| J132AP | iBridge2,4 | MacBookPro15,2 |
| J174AP | iBridge2,5 | MacMini8,1 |
| J780AP | iBridge2,7 | MacBookPro15,1
| J140KP | iBridge2,8 | MacBookAir8,1 |
It seems that Apple has manufactured two kinds of _MacBookPro15,1_. One of them has J680AP T2 processor, which is distributed to the market at least before April 2019.
The other one has J780AP T2 processor, which should be distributed after that.
It's not hard to find your T2 model:
Open file
/private/var/log/install.log
with Console App and search for
project = BridgeOSInstall
bridgeOS prepare summary: 16P6568 -> 16P6571, update = 16.16.6571.0.0, brain = 16.16.6571.0.0, variant = com.apple.bridgeOSCustomer, macOS = 18G87 (customer), project = BridgeOSInstall-56.4, userAuth = 0, prod fused = 1, model = j680ap, client = SoftwareUpdate, retries = 0
1. Freezes (10-40 s) in Chrome.
2. Reboots after 10-15 min of sleep.
3. External USB-C monitor (LG Ultrafine 21.5) not going to sleep.
Updated the laptop from 10.14.6 to 10.15 Beta 5. It was my huge mistake.
Update triggered the iBridge update to version 4.0 Beta (17P50521d).
Cannot recommend this to anyone:
+ no more freezes!
+ external monitor working good.
- it is not charging. Even showing that charger is connected.
- !!! Laptop not powering up from sleep mode !!! (5-10 lid open-close cycles and many power button pushes returned it to life)
- Final one = not powering up at all -> I started it in DFU mode. And it's the start of an interesting part:
Apple Configurator Beta is stupid. It tried to downgrade 4.0 Beta iBridge Firmware to 3.6 Release. But it is not allowed! So it bricked the T2 to Recovery mode. Every other attempt the Configurator tried to install 3.6:
US Desc: backwards update not allowed: 17P50521d -> 16PXXX
Domain : AMRestoreErrorDomain
Code : 0x4F (79)
It was a complete disaster.
MB and TouchBar boards were replaced in 3 days. And the new board having the same j680ap T2 chip! Bad luck for me.
A friend of mine got his 2018 15" MBP recently with upgraded j780ap T2 chip and having no problems so far.
Most recent (August, 22) build of T2 version 3.6 (16P6571) version's release noticing fixes to sleep mode issues.
No luck for me. All 3 initial problems are still here.
I could confirm the 2 versions of MBP 15" 2018:
| Processor code | iBridge model ID | Installed machine model ID |
|-------------------|-------------------|-------------------------------|
| J137AP | iBridge2,1 | iMacPro1,1 |
| J680AP | iBridge2,3 | MacBookPro15,1 |
| J132AP | iBridge2,4 | MacBookPro15,2 |
| J174AP | iBridge2,5 | MacMini8,1 |
| J780AP | iBridge2,7 | MacBookPro15,1
| J140KP | iBridge2,8 | MacBookAir8,1 |
It seems that Apple has manufactured two kinds of _MacBookPro15,1_. One of them has J680AP T2 processor, which is distributed to the market at least before April 2019.
The other one has J780AP T2 processor, which should be distributed after that.
It's not hard to find your T2 model:
Open file
/private/var/log/install.log
with Console App and search for
project = BridgeOSInstall
bridgeOS prepare summary: 16P6568 -> 16P6571, update = 16.16.6571.0.0, brain = 16.16.6571.0.0, variant = com.apple.bridgeOSCustomer, macOS = 18G87 (customer), project = BridgeOSInstall-56.4, userAuth = 0, prod fused = 1, model = j680ap, client = SoftwareUpdate, retries = 0
Last edited:
Interesting post.
My 2018 Vega 20, but otherwise std i7 500/16gb machine, has build date of Feb 4th 2019 and has J780AP.
I had like at lest 3 or 4 store bought machines between Christmas and mid-jan 2019 which were problem central.
I did have a couple of crashes on this one, but nothing too annoying until 1st week of April, since then it has been rock solid. I think I had a system uptime for like 45 days at one time... or something crazy. And it gets used hard for video, raw photo, animation, ect... with files on external SSD's and running on and off wall power. Basically the only time my machine has rebooted is for an OS update in 5 months. I don't have filevault on and maybe some t2 stuff turned off? from mucking around in the early days. I still get a weird single pop sound when starting/stopping starting audio playback in FCPX or youtube every now and then, it doesn't happen with headphones though.
I tried this on my 2019 13" MBP (i5 2.4 GHz model 15.2) without finding this information. I only found some entries that my minimum BridgeOS version is satisfied and no update was necessary. I'm still on Mojave because I wait for 2 apps to be updated to 64 bit
I tried this on my 2019 13" MBP (i5 2.4 GHz model 15.2) without finding this information. I only found some entries that my minimum BridgeOS version is satisfied and no update was necessary. I'm still on Mojave because I wait for 2 apps to be updated to 64 bit
Here is the method to find it:
1. Open Terminal
2. cd /usr/libexec
3.
For short info:
./remotectl list
<your UUID> localbridge iBridge2,3 J680AP 3.6 (16P6571/16.16.6571.0.0,0) -
For all the details:
./remotectl dumpstate
State: connected (connectable)
UUID:
Product Type: iBridge2,3
OS Build: 3.6 (16P6571)
Messaging Protocol Version: 1
Heartbeat:
Last successful heartbeat sent 13.125s ago, received 13.121s ago (took 0.004s)
2530 heartbeats sent, 0 received
Properties: {
AppleInternal => false
ChipID => 32786
EffectiveProductionStatusSEP => true
HWModel => J680AP
HasSEP => true
LocationID =>
RegionInfo => LL/A
EffectiveSecurityModeAp => true
FDRSealingStatus => true
SigningFuse => true
BuildVersion => 16P6571
OSVersion => 3.6
BridgeVersion => 16.16.6571.0.0,0
SensitivePropertiesVisible => true
ProductType => iBridge2,3
BoardRevision => 1
Image4CryptoHashMethod => sha2-384
SerialNumber =>
BootSessionUUID =>
BoardId => 11
EffectiveProductionStatusAp => true
EffectiveSecurityModeSEP => true
UniqueChipID =>
UniqueDeviceID =>
RemoteXPCVersionFlags =>
CertificateSecurityMode => true
CertificateProductionStatus => true
ModelNumber => NQ2Y2
RegionCode => LL
InterfaceIndex => 8
HardwarePlatform => t8012
Image4Supported => true
}
Services:
Just in case anyone came down here looking for a Mac mini Bridge OS crash, the controller model in mine is j174ap. Frequent crashes (at least once everyday)
My mini has the same T2 model. It never crashed since I own it (April). The only restarts were due to software updates. It works as the family server with a 16TB LaCIE raid drive connected. I also use the mini to do weeklong multi thread Matlab model calculations where daily crashed would be fatal.
Last week I upgraded from my 2015 MBP 15" to a 4TB3 MBP 13. It has the J132AP T2 model. No issues so far. I have a Windows 10 bootcamp partition installed that I use through a Parallels virtual machine. At work I connect to an old monitor through HDMI, at home I use an eGPU with a 4k 27" monitor.
Running a 2018 MBP w/ Vega 20 and j780ap. I get crashes when waking from sleep while plugged into an eGPU
I do have a similar issue: though, sometimes it is crashing after 1.5 hours using the camera, sometimes immediately. There seems to be no straight correlation with this, however only happens to me when using the camera as well.
I am having problems with my MacBook Pro 2018 as well. Originally thought it might be a Zoom problem as it happens most of the time while I am in a Zoom meeting, but the crash is exactly what discussed here. Maybe it's Camera usage related.
Here's some specs:
MacBook Pro (15-inch, 2018), Graphics: Radeon Pro 560X 4 GB Intel UHD Graphics 630 1536 MB
Apple T2 Security Chip Firmware Version: 16P6571
Here's some specs:
MacBook Pro (15-inch, 2018), Graphics: Radeon Pro 560X 4 GB Intel UHD Graphics 630 1536 MB
Apple T2 Security Chip Firmware Version: 16P6571
It was good for almost two weeks, had the first internal webcam related crash again just today. Called up Apple and told them it looked like it was working at first but now it crashes just like before, they told me they are still working on fixing this particular problem.
Interestingly enough macOS does not show a window telling you a kernel panic happened when this happens, it used to do that before.
Last edited:
The old 2018 13-inch MBP I had, and my new 2019 15-inch MBP both have crashed. The old one was a crash-heaven, the new one just did it once (fortunately).
But I found the reason in my case: when I have some particular USB devices (not all) connected and/or its own software running, and the computer goes to sleep. For example, when using the old 13-inch MBP, I had an RME Babyface Pro USB audio interface, and if the computer went to sleep, with its software ("TotalMix FX") running, it would crash at random. As soon as I began to quit the applications before sending my Mac to sleep, it would no longer crash (audio interface connected or not). Similarly, the crashes would also occur when I connected anything and If I had the RME device connected at the same time. Similar thing happened just once with my newer Mac, but only when connecting a Sandisk USB C drive for the first time. Never again.
So, I think this is a combination of: T2 equipped Mac + some very specific USB devices and/or its software + sleep mode (not sure about this though, because I think it did crash once with no sleep).
None of my Macs have crashed when alone (with nothing connected to its ports).
My Mac is rock solid now that I isolated the causes, in MY case.
Does anyone have experienced something similar?
But I found the reason in my case: when I have some particular USB devices (not all) connected and/or its own software running, and the computer goes to sleep. For example, when using the old 13-inch MBP, I had an RME Babyface Pro USB audio interface, and if the computer went to sleep, with its software ("TotalMix FX") running, it would crash at random. As soon as I began to quit the applications before sending my Mac to sleep, it would no longer crash (audio interface connected or not). Similarly, the crashes would also occur when I connected anything and If I had the RME device connected at the same time. Similar thing happened just once with my newer Mac, but only when connecting a Sandisk USB C drive for the first time. Never again.
So, I think this is a combination of: T2 equipped Mac + some very specific USB devices and/or its software + sleep mode (not sure about this though, because I think it did crash once with no sleep).
None of my Macs have crashed when alone (with nothing connected to its ports).
My Mac is rock solid now that I isolated the causes, in MY case.
Does anyone have experienced something similar?
Last edited:
Same here, I don't always get the kernel panic-would-you-like-to-report-or-ignore-window shown after reboot.