Is there any change in T2 Firmware for the 10.14.2 beta from 10.14.1? Suppose if there is, it's a sign they're still actively working on things.
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
Hilarious and sad at the same time. Looking at this senior advisor who told me that taking months to fix this issue is doomsday speak, it really is doomsday. Extremely happy I got a full refund for my MBP.
Baffling one of the most valuable companies in the world can be so incompetent.
Knock on wood ... a few posts back, someone mentioned doing the SMC reset twice in a row. I'd done it once before to try and fix this, but no luck. Per the suggestion of the post, I did it twice in a row a couple days ago and haven't had a KP since.
My KPs only occur immediately after entering password on boot from a shutdown state. Haven't had them in any other case. Will continue following and report back either way in a week or so (or if I get another KP).
My KPs only occur immediately after entering password on boot from a shutdown state. Haven't had them in any other case. Will continue following and report back either way in a week or so (or if I get another KP).
please let us know where you saw this...with no source, this is useless.
Just made an account so that I can post in this thread. Just experienced my first KP on a brand new MBP w/ touchbar purchased last Friday. Part of the log below:
{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1
Seems like the 3.1 version didn't fix the issue so I am wondering if it is indeed a hardware issue. In this case, I might just return it or have it replaced, but if the issue persists on other devices, then why bother replacing?
All in all, it happened while sleeping with the lid open and the power chord plugged in the top left usb-c port. I have seen someone mentioning this already so we start to see a pattern. However, this is so specific and why in the world such an expensive machine would restart because of this...
{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1
Seems like the 3.1 version didn't fix the issue so I am wondering if it is indeed a hardware issue. In this case, I might just return it or have it replaced, but if the issue persists on other devices, then why bother replacing?
All in all, it happened while sleeping with the lid open and the power chord plugged in the top left usb-c port. I have seen someone mentioning this already so we start to see a pattern. However, this is so specific and why in the world such an expensive machine would restart because of this...
Maybe the SMC reset needs to be performed after being updated to a very recent version of BridgeOS? To anyone that may have tried an SMC reset in the past with no improvement, try it again after updating to the latest version of Mojave.
https://forums.macrumors.com/threads/any-t2-related-crashes-with-2018-mini.2153202/
Granted, some others are suggesting his mini is a lemon with more than T2 chip issue since it is refusing to boot now.
I was strongly convinced it was a software/firmware bug, for the reasons I wrote in the thread, but as time goes by, it’s starting to look more and more like a hardware defect affecting some units only. BTW, wasn’t the T2 the chip that Apple was so proud of because of its smallest nanometer technology behind? (I’m talking from my memory and I could be wrong, but if the smallest nanometer one was this T2 chip maybe they are having some yield issues in some T2 chips).
@SDColorado
I followed your saga for awhile, but lost track of things back in early-to-mid-October.
I think you threw in the towel after the 3rd problematic 2018 MBP, and swore you'd given up for good... but then picked up another (4th) at a local Apple store.
What ever happened with that 4th machine?
Sorry, you have so many posts, it's hard to find a post that describes the outcome of the experience with that 4th machine.
Last edited:
A user at the Apple discussion board suggested to do the SMC reset twice in a row.
Im free of kernel panics for more than 48hours!
I can only encourage you to try it out, but be aware of the new procedure for Macs with T2 chip!
Den System Management Controller (SMC) auf dem Mac zurücksetzen - Apple Support
(Hope you will be redirected to your country page
)
I will keep you updated!
Im free of kernel panics for more than 48hours!
I can only encourage you to try it out, but be aware of the new procedure for Macs with T2 chip!
Den System Management Controller (SMC) auf dem Mac zurücksetzen - Apple Support
(Hope you will be redirected to your country page
)I will keep you updated!
Got my MBP 13 2018 3 days ago and had the first crash on first boot seeing the language selector.
Bridge OS 3.2 (16P52534b) on that machine.
I'm getting the unit replaced this week. Support asked me to do SMC reset but I did't do it. I asked them to send me a replacement or give my money back.
I'll keep you posted.
Bridge OS 3.2 (16P52534b) on that machine.
I'm getting the unit replaced this week. Support asked me to do SMC reset but I did't do it. I asked them to send me a replacement or give my money back.
I'll keep you posted.
There's 84 instances of the word SMC in this thread, and perusing the usage, it seems many people have tried resetting the SMC, with little to no success. I don't think such a simple action as that will fix it for everyone since we have evidence it's not working for others.
To be honest, i also didn't believe that it will solve the issue. But there was also nothing to lose to give it a try.
And for me it seems to work(, too). I had crashes regularly after waking up my MBP from sleep( > 3 crashes a day). Also did only a single SMC reset, which did not solve the issue.
So i suggest to try it out: twice SMC resets in a row with respect to the correct procedure for T2 Macs.
Some positive/negative feedback would be nice!
No harm in trying, but my point is that they were trying that with little to no luck
Sorry, I have no interest in trying the SMC reset, if the pristine OS on a new mac crashed on first boot on my my side.
This was a refurbished Mac, and I suspect that the pervious owner had the same problems and Apple just re-sold the Mac without fixing anything.
BTW: I just tried macOS beta for 10.14.2 and there is no change: still Bridge OS 3.2 (16P52534b) installed and still crashing.
That was about the gist of it. I decided to try one more. But with the continued issues with keyboards, kernel panics, long repair times and time without their computer for repair being reported by some, I decided that I didn't feel the 2018 MacBook Pro was going t be a good, dependable machine for the long haul. Despite not having issues with the 4th, 3 out of 4 with problems is not a good track record.
I decided to return the 4th while it was still inside the 14-days. I am going to sit this round out until there is a revision. I will have another look then.
I don't blame you and if I were in your shoes, I too would get a refund. I actually would avoid the MBP, not just get it replaced. Had I known about this problem before plunking down almost 3k, I would probably avoid it myself. I'm one of the lucky ones that has a stable machine. Overall its a great laptop but, this whole T2 issue is concerning.
I tried to do the SMC reset twice in a row way back with unit #1. It made no difference. As you say, it is nothing that you can remedy that easily. If it could be, Apple would probably have put out some sort of bulletin about that, similar to the one they tried with the keyboard cleaning method.
I was aware of the issue, but after extending and extending the lifetime of my MacBook Air because Apple didn't release a worthy successor to it, I was in a situation where I couldn't work anymore with my (late 2010) MBA, and I really needed to buy a new MacBook. I waited as much as I could, even up to the day of the iPhone event, hoping seeing a new 14inch or 15inch MBA successor. But nothing was released, and I couldn't wait anymore, so even being aware of the issue I bought a 15inch MBP, as it was almost 100% clear that Apple wasn't going to release any MB bigger than 13inch apart from the MBP. Just like you, I've been one of the lucky ones... no KPs (at least not yet).
This has been an interesting set of events to watch unfold. This may someday become another case-study in how screwing over long-time-loyal customers eventually causes significant erosion of the bottom line. I hope Apple pulls their heads out of their *** soon. Their arrogance (or maybe it's just plain ignorance) has got to be showing up in attainment of overall revenue targets eventually.
Speaking for myself, I will NEVER confidently buy another Apple product on launch day EVER again. They have demonstrated to me (and my friends and family) that neither their product reliability, nor customer service, can be trusted. A purchase decision will only be considered after a product has been in the market for a while, and there's no systemic customer-sat issues.
I agree. As a die hard Apple fan, who has bled Apple Juice for the last 12+ years to give up on this model is a bit heart breaking to say the least. I am really hoping that they get their **** together for a serious revision in the near future. It isn’t just the casual buyer and occasional punter they are losing these days, it’s their loyal repeat customers.
I have a brand new MacBook Pro 2018 since 10 days: it has been a nightmare. In my kernel report I also get mentions op 'MacBookPro15' ... Why is that? Apple support has been not a great help, the Apple shop where I bought it from refuses to take it back or replace it unless it's a proven hardware problem. They did a clean install of the OS and considered the issue as fixed??? I still have 6 crash reports in a timespan of not even 3 hours. Have been using Mac's since 1994 and feel like I'm totally been taken for a ride.
[doublepost=1542055805][/doublepost]
I have the same issues. I have a brand new MacBook Pro 2018 since 10 days: it has been a nightmare. Apple support has not been a great help, the Apple shop where I bought it from refuses to take it back or replace it unless it's a proven hardware problem. They did a clean install of the OS and considered the issue as fixed??? I still have 6 crash reports in a timespan of not even 3 hours. Have been using Mac's since 1994 and feel like I'm totally been taken for a ride.