Problems upgrading to macOS Mojave on MacBook Pro 2018

Understood. But I do think Apple owes to itself as a company and its loyal customer base to look at Discussion Forums like this one and absorb the frustration, anger, at times vitriol, and overall dissatisfaction with their performance.

The saying too big to fail comes to mind.

I agree someone should monitor this site and get a pulse but too frequently when the company gets so big ......

I'm just disappointed really, after going from one OS to the other over the years without a problem and now trying to upgrade to Mojave the problem is a big one not just a minor flaw.

Oh well

What I’m curious about is whether the people who can’t install Mojave in their 2018 MacBook Pros are the same ones who have been facing the continuous kernel panics which cause the system to crash. Because a friend of mine with the same model as mine has neither faced kernel panic crashes nor experienced any trouble installing Mojave, while mine still crashes after Supplemental Update 2 and no Mojave upgrade.

Do you have any solid leads on what's causing the kernel panics?

Maybe if you solve that, it will help solve the upgrade problem. At least, maybe if Apple solves the first problem, then they can solve the second.

By your own statement, it doesn't sound like it's affecting every unit / model.

To solve the Kernel panics, they first have to admit that the crashes exist. Every time I called AppleCare, even on taking my device to Authorised Service, they couldn’t find anything and just reset the MacBook and say that it’s gonna be fine now. Yet facing crashes every couple of days without any apparent pattern. Such a waste of money.

OK, putting aside that Apple has to admit the problem exists, have you been able to diagnose anything on your own using console or any logs? such as system logs? Might be a good place to start (if you haven't already.)

I have diagnosed this: crappy company which doesn’t care about its customers as people will buy their products anyways. Apart from this, it’s the T2. T2 has some defect which seems to cause kernel panics in the bridge os. At least that’s what I’ve concluded from the error logs. I might be wrong, of course.

There has been mention on this thread regarding the Mojave upgrade failure, and people who have communicated with Apple have reported that Apple has identified the T2 having issues, or it being part of the issue at least. There hasn't been an official solution offered yet though.

But yeah, the kernel panic is caused in bridge os, not mac os, as described in the error logs. Bridge os is used to integrate the T2 to the main chip, right? That’s why I’ve concluded that it’s a hardware problem, not a software one, as not everyone is facing kernel panics. Quality control is not necessary, after all.

Since neither one of my Macs has a T1, or T2 chip, it's not something currently I have to be concerned about. I would like to see this resolved for those with the issue.

I happened to have very little trouble with my upgrade, and the glitches I had, I was able to repair myself.

There are some here where the upgrade could be failing when they restore their time machine backups. Then there are others that don't seem to have any kind of rational reason people have found currently.

Callback of the faulty machines and full refund of the payment will be the solution, I hope. Because the way they have handled it till now makes me suspicious that they are not near a proper solution. Or maybe they just don’t care anymore. Anyhow, unless they solve this, I cannot see how they can evade a lawsuit.

Well, if you've followed Apple for any length of time (meaning from their beginning)The first time they kicked Jobs out, and just about went bankrupt, and fell apart. This time, he's not coming back, and I feel like history might repeat itself.

I still genuinely like their products and use them. But Now, at least to me, hopefully to those who have followed them for a long time. Apple just feels like another name now, not the company they used to be.

The Mojave problem is not limited to 2018 MacBook Pros. I had no problem upgrading my 2.6 GZ model. I had no problem upgrading my 2016 MacBook. However, my 2.6 GZ mid-2012 MacBook Pro has failed to update five times. The most recent failed update attempt was guided a second level Apple tech. As I posted yesterday the first level tech I spoke to yesterday stated that they were having problems with their in-house non-pro iMacs. Apple is aware of the issue but as with recent issues they have failed to make a public statement.

armwood, I know the Mojave upgrade issue isn't limited to one model, or set of models. That's what makes it hard to give a straight answer for.

Hopefully as the week rolls on, we'll hear something from Apple. Usually, they are good at posting a fix, when they have one.

The closest thing I have to your 2012 MBP, is a late 2013 13" MBP. It didn't have trouble with the betas. I haven't tried to wipe it and do a clean install of the final version though.

It did upgrade to 10.14.1 without issues though.