search

barrykn / big-sur-micropatcher

A primitive USB patcher for installing macOS Big Sur on unsupported Macs
1.25k stars 174 forks source link

macOS Big Sur 11.0.1 #94

Open ramonenghaw opened 4 years ago

ramonenghaw commented 4 years ago

Hello, can someone provide the download link for macOS Big Sur 11.0.1? Thanks!

ghost commented 4 years ago

Developer Installer | Public Installer

Btw, I'm keeping a catalog of these links for my patcher, but you can use them if you would like. I test the releases before updating them, so it's safe too!

Developer Catalog | Public Catalog

ramonenghaw commented 4 years ago

Thank You!!

ghost commented 4 years ago

macOS 11.0.1 RC is out and I'm testing it right now, the developer link is in the developer catalog, I'm waiting until I test it before I put a link the the public catalog (that will be the general pattern going forward).

Edit: I tested and they both worked! So there's one in the public beta catalog too.

logusgraphics commented 3 years ago

Confirmed v0.5.0 works with 11.0.1 Beta 2 RC (20B5012d)

barrykn commented 3 years ago

My initial tests with 11.0.1 RC2 (20B28) have succeeded, but I need to do a little more testing before I know for sure that's it's compatible. (It may be several hours before I get around to finishing my testing, which is why I'm posting this comment now.)

By the way, at some point in 11.0.1 development, Apple actually fixed the bug that used to cause Setup Assistant to crash on non-Metal GPUs.

philo-meerman commented 3 years ago

Just installed Big Sur 11.0.1 (20B29) on MBP10,1 successfully.

Feedback I had to deviate from the manual at step 15: Booting from USB required my password which was not recognized (don't know why), and therefore that route did not work. Instead of booting from the USB, I tried booting regularly and ran the patch in a terminal. It ran successfully and I rebooted and big yay!

barrykn commented 3 years ago

@philo-meerman It's disappointing to know that Apple hasn't fixed that bug yet. I guess this wasn't enough warning? (quoting from the README)

FileVault has been buggy throughout the entire Big Sur development cycle. For maximum stability, disable FileVault before upgrading to Big Sur. Once you upgrade to Big Sur, bugs may make it impossible to disable FileVault and may make it impossible to unlock your FileVault volumes when applying updates or booting from the installer USB. (Not to mention, FileVault bugs may also make it impossible to open Terminal on the installer USB.) The best way out of this conundrum is probably to back up the entire Big Sur installation using Time Machine (Time Machine encryption, unlike FileVault, appears to be stable), erase and reinstall Big Sur, and use the Setup Assistant to restore the Time Machine backup.

I'll see what I can do to modify the patcher to provide extra warnings for FileVault users.

philo-meerman commented 3 years ago

@barrykn I did read it, but didn't connect the dots, so that's on me. If desired, happy to help describing a workaround in the manual. Apart from that, this is great work and well done to the team!

barrykn commented 3 years ago

The best way out of this conundrum is probably to back up the entire Big Sur installation using Time Machine (Time Machine encryption, unlike FileVault, appears to be stable), erase and reinstall Big Sur, and use the Setup Assistant to restore the Time Machine backup.

That's the 2nd simplest workaround, unfortunately. (The simplest is to disable FileVault before installing Big Sur, but once Big Sur is installed, it's too late.) I'll add code to future patcher releases (hopefully v0.5.2) so that FileVault users can't simply sleepwalk into this trap. I'll also change the phrasing to be a bit simpler/easier to understand.

barrykn commented 3 years ago

Actually, if you have a Time Machine backup of Catalina, don't bother making a second one with Big Sur, just do a fresh install of Big Sur and restore from the Catalina Time Machine backup.

philo-meerman commented 3 years ago

Maybe I have missed a section in the README; what is the benefit of doing that, since Big Sur seems to be working as expected now?

barrykn commented 3 years ago

Big Sur is not really working as expected now, because you can't fully boot into a Big Sur recovery environment, hence your need to "deviate from the manual at step 15". There is one option that will still work in the recovery environment -- the option to wipe out your Mac's internal HD or SSD. In order to not lose data when doing that, you will need a Time Machine (or equivalent) backup to restore from afterward. And you will need to be able to boot into a recovery environment if anything goes wrong -- or if you ever want to update from Big Sur 11.0.1 to 11.0.2 or whatever Apple releases over the coming weeks and months (i.e. if you ever want to be able to apply security patches).

Regarding that last point, all the dots are there in the README, but in hindsight it's clear that I need to be more explicit about it, so that people don't have to connect the dots.

(Not to mention, there are some more situations that can require booting from the Big Sur USB stick even if nothing goes wrong, particularly in situations where you're dual booting Big Sur and an earlier macOS version and you want to choose the Big Sur volume in the Startup Disk preference pane.)

harrykl commented 3 years ago

Developer Installer | Public Installer

Btw, I'm keeping a catalog of these links for my patcher, but you can use them if you would like. I test the releases before updating them, so it's safe too!

Developer Catalog | Public Catalog

Is the public installer the Release Version of Big Sur?

barrykn commented 3 years ago

Is the public installer the Release Version of Big Sur?

I think the public installer link you quoted is outdated (so the answer is no). Here's the link to the 11.0.1 release: http://swcdn.apple.com/content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg

harrykl commented 3 years ago

Thank you