Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Then you are old enough to remember the days BEFORE Kernel Exploits and Government Rootkits. Ya know, the things that started making always-on Encryption of local storage and Trusted Boot procedures an actual necessity.

Very few things become simpler over time. OS design in particular.
[doublepost=1532709854][/doublepost]
To sow FUD.

See, e.g., recent Samsung ads.
[doublepost=1532710023][/doublepost]
In ALL of the iMac Pro KPs, Apple has noted that the issue was permanently resolved by reinstalling macOS.

Just sayin'...
[doublepost=1532710215][/doublepost]
If you owned a PowerMac 6500, then you KNOW about Crashes...
Cite your source where “Apple has noted that this issue has been permanently resolved in ALL iMPs”.
 
Apparently you still missed the part I wrote that states Apple did something to these new machines that you cannot do a clean OS install after wiping your HD. It ends up in a loop. I’d call that a showstopper.
Have you even considered the possibility that you might simply have a defective unit? It DOES happen, ya know...
 
What issue or error are you seeing when you try and restore? There was an issue the first weekend when Apple "forgot" to add the correct build to their servers so Internet Recovery and Restore was not available. But, that was resolved by Sunday night.

I successfully restored my 2018 a couple of times, so it is possible. Have you possibly tried creating a bootable USB stick? You need to download the right build, but it can be done.
 
What issue or error are you seeing when you try and restore? There was an issue the first weekend when Apple "forgot" to add the correct build to their servers so Internet Recovery and Restore was not available. But, that was resolved by Sunday night.

I successfully restored my 2018 a couple of times, so it is possible. Have you possibly tried creating a bootable USB stick? You need to download the right build, but it can be done.
I tried both from internet recovery and using a USB stick. Neither would install the OS. It kept looping back to "you need to reinstall the OS" after going through the spinning globe phase of recovery. I have a brand new machine sitting right here in an unopened box that I want to do a clean install of the OS, but to say I am nervous is to put it lightly. I am going to try though because this has to work.
 
"Apple Looking Into Limited Reports..."

What's up with always using qualifiers like "limited" when reporting about the issues with Apple products? It's not like there is such thing as "unlimited reports".
It's their attempt at using language to try to minimize an actual issue, and trying to cover it up when they have no idea how many machines will be exhibiting that behavior.
 
So in the midst of trying to do a clean install of macOS after a senior advisor suggested it might help with kernel panics related to the T2 chip, I discovered yet ANOTHER oversight on Apple's part. It has to do with startup security settings. I have documented it here in a video. All I can do at this point is SMH.

 
It's not moaning, it's not whining, I know I'm not the only one who has had multiple kernel panics due to the T2. I have High Sierra on some of my machines and aside from some bugs that exist on all the machines I've tried with High Sierra, my iMac Pro by far is the worst. I have nonstop bugs everywhere. I'm not whining and moaning, and there is definitely no hidden agenda anywhere here. I have real issues that many other people on these forums have too.
 
So in the midst of trying to do a clean install of macOS after a senior advisor suggested it might help with kernel panics related to the T2 chip, I discovered yet ANOTHER oversight on Apple's part. It has to do with startup security settings. I have documented it here in a video. All I can do at this point is SMH.

Ok, so let's marked this as SOLVED. In order to re-enable startup security settings you have to boot into recovery using opt-cmd-R as opposed to just cmd-r in order for the proper download to take place from Apple's server. I figured this out by trying the many different key commands to boot into recovery. Thanks to everyone for all the ideas!

https://support.apple.com/en-us/HT204904
 
Last edited:
Ok, so let's marked this as SOLVED. In order to re-enable startup security settings you have to boot into recovery using opt-cmd-R as opposed to just cmd-r in order for the proper download to take place from Apple's server. I figured this out by trying the many different key commands to boot into recovery. Thanks to everyone for all the ideas!

https://support.apple.com/en-us/HT204904

Does that mean that you were able to end the dreaded loop and install OS 10.13.6 again? Or just re-enable startup security?

Cheers.
 
Does that mean that you were able to end the dreaded loop and install OS 10.13.6 again? Or just re-enable startup security?

Cheers.
I do not know if this fixes the loop of trying to install macOS clean, as I have a brand new machine that was swapped out because the other was 'bricked'. For now this just solved the re-enabling startup security loop. So I recommend that anyone doing anything in recovery boot using opt-cmd-r because apparently that pulls does the 'latest and greatest' from Apple's servers... :confused:
 
Last edited:
  • Like
Reactions: DeepIn2U
I do not know if this fixes the loop of trying to install macOS clean, as I have a brand new machine that was swapped out because the other was 'bricked'. For now this just solved the re-enabling startup security loop. So I recommend that anyone doing anything in recover boot using opt-cmd-r because apparently that pulls does the 'latest and greatest' from Apple's servers... :confused:


Ah yes, you had to replace it. Oh well, best of luck with the new one!

Do keep us posted!
 
  • Like
Reactions: dspdoc
I'm following this thread as I'm having the same kernel panics referencing Bridge OS & bug type 210. Mine also often happens when I pickup or move the computer around. I got the computer (15" 2018 MBP) yesterday and had maybe 6 or so yesterday and about 4 so far today. Something is very wrong & I hope for a fix soon!
 
I'm following this thread as I'm having the same kernel panics referencing Bridge OS & bug type 210. Mine also often happens when I pickup or move the computer around. I got the computer (15" 2018 MBP) yesterday and had maybe 6 or so yesterday and about 4 so far today. Something is very wrong & I hope for a fix soon!
Please be sure to log this with Apple by calling tech support and speaking to a senior advisor so that they can escalate yet another person having the issue to engineering.
 
The main problem is whether apple is able to fix this issue using a patch like before or this requires hardware replacements. If it is the latter, then they are in big trouble.
 
The main problem is whether apple is able to fix this issue using a patch like before or this requires hardware replacements. If it is the latter, then they are in big trouble.
If it is hardware related we are talking about a very ugly massive recall.
 
I have some really bad news for everyone. Apple has done something that has screwed these new MBPs up so bad that you cannot do a clean install of the OS. It gets stuck in a perpetual loop. I dare anyone to try. My machine is being returned tomorrow for a refund. I am beside myself with disgust over this latest fiasco of a release. A train wreck from day one.
[doublepost=1532820081][/doublepost]I did this when I took back my 13" and picked up the 15" and I had not a single problem. I erased the hard drive and reinstalled the OS. Sounds like a problem with your machine.. Hope it works out for you!
 
[doublepost=1532820081][/doublepost]I did this when I took back my 13" and picked up the 15" and I had not a single problem. I erased the hard drive and reinstalled the OS. Sounds like a problem with your machine.. Hope it works out for you!
This issue was figured out. If you read the entire thread in context you’ll see that. Thanks for the well wishes though! Hope all goes well with you too.
 
These Apple standards that Macrumors said Samsung's new tough screens must adhere to should maybe be applied to Apple's inhouse components first.

And people seriously want to trust Apple with the actual CPU to replace Intel?!

Actually, if you look at all the iOS devices that run on Apple chips, how many of them Kernel panic?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.