Maybe you could try to boot into recovery with a different key combination?: https://support.apple.com/en-us/HT204904
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
Maybe you could try to boot into recovery with a different key combination?: https://support.apple.com/en-us/HT204904
Tried all that. Even tried installing from a 10.13.6 bootable USB that works perfect on my iMP. Apple has altered something about these 2018 MBPs and screwed things up. I would love for someone else to try and do a clean install and see what happens.
I know you can't boot from external devices (including USB) because of the new encryption thing. I have no idea why recovery isn't allowing you to install though. Maybe the Apple servers are down? Sorry you're going through this, man...
Your frustration is justified and your experience is clearly unacceptable; but it is just a machine that needs returning and replacing. It does not mean that all new MBPs are bad, so it is not exactly bad news for everyone.
Good luck.
Thanks for this, I did a disk check (luckily after doing a time machine backup) from the recovery partition and it had the crypto thingy errors, when I rebooted it had knackered my OS and asked for a reinstall. I did a time machine restore same as you but I was scared to do another disk check (as it took 1 1/2 hours to reinstall and I assumed the errors would be just put back onto the drive). After reading your post I gave it a go and sure enough the disk check has come back ok this time.
Just wanted to say thanks
Seriously? So, there is no way to boot a live linux system with USB? If so, that's pretty bad.
Actually yes it is because more and more users are starting to confirm that you cannot do a clean install of macOS on these new machines. Apple has screwed something up and they get caught in a loop and will not install the OS. I venture to say that once even more people start to realize this that it is going to be as bad as the throttling issue was. If you have a 2018 I dare you to try and do a clean macOS install. Let me know how that works out for you. You end up with a machine you cannot use at all!
[doublepost=1532698399][/doublepost]
I did that. You still cannot do a clean install of macOS the machine gets stuck in the loop!
Last edited:
How can Apple get away with this? Releasing a whole line up MBP computers that you CANNOT reinstall the OS cleanly?!?!
Got mine 8 days ago and broke it 12 hrs later, I just assumed the installer would be fixed by now ( I think some users have reported to be able to network boot from apple servers) but I don't want to run the risk of having to reinstall again. I plan to do a fresh install when 1013.7 is available or Mojave, whichever comes first. If you still cant install from a USB I wont be very happy.
So you have reported this same issue to Apple then, that you cannot do a clean macOS install?
Nope, unless I need to do a fresh install and can't again then I will, mines running fine now and checkdisk reports no errors so I'm happy. They really should have had a working OS you could reinstall from scratch but as apple employees don't even know when a product is going to be launched I'm guessing the tech staff arent told either that they have to have the files ready for customers. Thats the trouble with apple - so secretive.
The Restart issues has been ongoing now since last year with iMac Pros, and continues to the best of my knowledge unresolved. The Apple Discussion Forum at https://discussions.apple.com/message/33585049?start=195&tstart=0 speaks of the "engineers at Apple" working diligently on this, yet there seems to be a lack of transparency.
Sure hope that Apple issues an "official status report" soon as there are many businesses depending on getting this issue resolved ASAP.
Sure hope that Apple issues an "official status report" soon as there are many businesses depending on getting this issue resolved ASAP.
I have the 13" 2018 and do not get the KPs, but I was seeing the crypto val errors is Disk Utility First Aid like you two gents.
I found some posts in the Apple Support forums from iMac Pro (uses the T2) users who had this issue and it was resolved by a wipe and reinstall. So I did a command-option-r boot to Internet recovery, erased the drive to APFS, then reinstalled and all is well and the error is gone.
@StudioSanctum have you tried command-option-r Internet recovery and not just regular command-r recovery.
If you are trying TM restores or installs from USB keys made in other Macs, that won't work, since these machines are using a custom/special build of 10.13.6.
Only other thing I can think of I may have done differently than you is when I first booted the new MacBook, I did a command-r boot to recovery and used that firmware security utility to password protect the boot process (similar to the old firmware password). So when I ultimately booted to Internet recovery, it prompted me for that firmware password to allow a boot to another source, and everything worked fine after that.
Hope this helps you.
So far my 2018 MacBook Pro i9 is good! No Problems
When I got my iMac Pro in January it restarted once every day the first month or so when using Blender. However after the first patches of Mac OS X it did never happen again.
When I got my iMac Pro in January it restarted once every day the first month or so when using Blender. However after the first patches of Mac OS X it did never happen again.
That's interesting, Mine is set up the same way, but was still having occasional kernel panics when I wasn't using the computer. I haven't had one since the last update. Before this, I usually just shut it off and never left it running overnight, and doing that I went several weeks without a kernel panic. But then my pattern of use changed and I was leaving it on all the time, and sometimes I'd come back and find there'd been a kernel panic.
I tried command-option-r still loops. And I turned off boot security completely first.
Actually, now that you mention it, I do occasionally (like maybe once every week or two) in the morning find that something peculiar has happened... the several external drives that I typically keep attached but unmounted are showing up on the desktop, as if the machine had restarted at some point overnight. I don't recall ever seeing any kind of message that indicated a KP had occurred though. I'll pay more attention to it next time it happens.
Try turning the boot security on with a password like I did, then when you command-option-r boot it will ask for the firmware password. That worked for me.
I have been experiencing this issue as well since day one. This only happens while the MBP goes to sleep, usually after a couple of hours into it, when I try to wake the MBP up it doesn't responds. Sometimes I get a crash report, some times like today I do not. This is the latest in the logs that I could dig from this morning:
Notice the jump in time from 06:29:36 to 11:20:24 EST when my MBP did not wake pop and just booted from scratch. All of these after I reinstalled/re-patched the OS to get rid of the crypto errors that I noticed I also had yesterday.
I have two LG Ultra HD Displays connected each directly using a USB-C -> DisplayPort. Its the only things plugged to this MAC, I will try unplugging them and putting the computer to sleep to see if it happens again.
I have enable/disabled all settings possible related to activities that may interfere with the sleep process, none of that has helped.
Code:
Jul 27 06:28:43 xxx-MBP syslogd[39]: ASL Sender Statistics
Jul 27 06:28:54 xxx-MBP systemstats[50]: assertion failed: 17G2208: systemstats + 914800 [D1E75C38-62CE-3D77-9ED3-5F6D38EF0676]: 0x40
Jul 27 06:29:24 --- last message repeated 1 time ---
Jul 27 06:29:36 xxx-MBP kcm[775]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?
Jul 27 11:20:24 localhost bootlog[0]: BOOT_TIME 1532704824 778411
Jul 27 11:20:26 localhost syslogd[39]: Configuration Notice:Notice the jump in time from 06:29:36 to 11:20:24 EST when my MBP did not wake pop and just booted from scratch. All of these after I reinstalled/re-patched the OS to get rid of the crypto errors that I noticed I also had yesterday.
I have two LG Ultra HD Displays connected each directly using a USB-C -> DisplayPort. Its the only things plugged to this MAC, I will try unplugging them and putting the computer to sleep to see if it happens again.
I have enable/disabled all settings possible related to activities that may interfere with the sleep process, none of that has helped.
command-r boot to recovery then in the Utilities menu launch the Startup Security Utility and turn on a firmware password. Then restart into Internet recovery. You should get a prompt to enter firmware password you set, then it proceeds with the usual grey spinning globe as the recovery utility downloads.
Once that comes up, start Disk Util and erase Macintosh HD to APFS. Then quit DU and click reinstall OS.
This worked for me and setting that FW password is the only thing I can see here I did differently.
Last edited:
I’ll try that after they replace my MBP because as of now it’s a brick. Thank you.