Problems upgrading to macOS Mojave on MacBook Pro 2018

Finally I installed Mojave with 14.1

First I installed the security update of high Sierra with any problems, and after that I installed Mojave successfully on my MacBook Pro 15 2018.

Apple finally solved the bug

So, feedback as promised.

Install stopped at around 80 percent again. Booted into Safe mode, install completed.

Switched off FileVault, boots normally 🙂 - much celebration.....until

Switched FileVault on again, reboot.....gets stuck 3/4 way into the boot sequence

Repeated the above a couple of times to verify

I suspect that I may have enable FileVault while connected to the corporate network in order for it to work properly.

Going to try that next

try this

• removing all DNS search domains
• untick the automatic proxy configuration if ticked

SMC reset fixed it for me! Running on Mojave, Messages delays fixed, and Apple Pay issues/error logs gone!

Uninstall Bitdefender and CleanMy Mac3. They are both worthless pieces of just which only cause problems and offer no good.

The T2 chip will not let users of MBP 2018 install Mojave or for that matter a clean install of High Sierra. There is a work around but it is very complicated and time consuming and will be a bit much for the average user. Note: I have not tried it and I should not have to. Apple need to address this issue and quickly so I would wait until they have done so. Do not try to do a clean install without a back up. I have made Apple aware of this and will keep pressing them for a solution. Good luck

Maybe its something in the boot sector.

What I would suggest is to do a fresh install after having erased and reformatted the HD in correct type.

Then do an install using the option command R method this will do an internet install to latest OS.

If this does not work then make a genius appointment.

It's possible you had broken stuff in the backup that was ok in High Sierra, but showed up in Mojave. Especially since the clean install worked, and then it broke after restoring TM. For many years, I didn't even bother with TM, and just backed up manually what I needed to keep, when doing a clean install. Always has been a reliable solution for me.

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.

If Mojave was successfully installed and working when you got back from the Apple store, then the backup is the problem. Even though it should not be the case, there must be something in the backup that interferes with Mojave.

The only solution is to install Mojave without a backup and manually transfer your files and stuff over. To do this I would get an external drive and move everything like photos, music, documents, etc into separate folders. I would then install every app that you use and then move all of your stuff back to the internal drive.

You can also wait for 10.14.1 but there’s a big chance that Mojave will not work when restoring from the same time machine backup or whatever backup you were using.

dmauch, after checking with a friend, it seems like the most probable cause for you, and Ann's files is from legacy software that was passed down through your Time machine backups, especially hers since she said she's had the same backup going for years. If you have as well, it's very possible the same. What I would recommend at this point, to avoid further issues, is to make sure your system is stable and the way you want it, and start a fresh clean time machine backup from this point in time. That way you can get rid of all the legacy stuff that may cause future issues .

As long as everything you need is on your current install / setup, there is no harm in starting over with time machine from this point.

We just upgraded our 4th Mac to Mojave last night without incident. My initial "upgrade" attempt was complete disaster trying to put Mojave on my 2015 MBP, and I wasted nearly a weekend trying to troubleshoot the completely crippled installation, and only got my computer back by restoring back to High Sierra with Time Machine backup (hooray, Time Machine!!). Eventually, a remedy using Terminal to rename an old file was posted ( Mojave install a disaster ) and I tried it and yes, I had that old file on every machine. So, I got up my nerve to try this after about a week or so, ran the terminal script to rename the offending file, and installed Mojave with complete success. I have repeated this on all the Macs, including a 2012 MBP and a new 2018 MBP with the T2 chip (which is not the problem), and so far they are all running smoothly.

What bothers me is, why has Apple not addressed this and posted at least an informational statement, or better yet a patch? That is so weird, as this has been going on for over month now. I feel like a stepped into a trap with the initial installation. They seem to be in official denial over this problem.

Just to add one more data point. I have a MacBook Pro 15" i9 with touchbar.

When I first got it it had crypto_val errors which was only able to be cured with booting into recovery erasing the HD and reinstalling the OS (High Sierra at the time).

I had held off upgrading till 10.14.2 was released. I reset the SMC as some advised.

Installation of Mojave went very smoothly and no discernible issues (except for a minor one with the text box in notes).

It could be that one needs to fix the crypto_val errors before upgrading, it could be resetting the SMC or that 10.14.2 fixed the upgrade issues.

Hopefully this information is helpful to someone.

This is really strange. Have you checked the disk for errors? What about holding “D” when booting up. See if any errors pop up.

Hey!

Just out of curiosity -- what OS are you on right now?

1. are you on any OS lower than macOS High Sierra? If so, upgrade to High Sierra First.

2. Are you on any Beta macOS?

3. How much hard disk space is left?