barrykn / big-sur-micropatcher

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

MBP 10,1/2012 Retina. Filevault prevents upgrade from 11.0.1 to 11.1 #161

Closed dgaastra closed 3 years ago

dgaastra commented 3 years ago

Dear Developers,

Thanks for making such a great tool to support Big Sur on older Macs.

We managed to upgrade the - just unsupported - notebook to 11.0.1, but cannot upgrade to 11.1.

root@usermbp ~ # fdesetup status FileVault is On. FileVault master keychain appears to be installed. root@usermbp ~ # fdesetup disable Enter the user name:user Enter the password for user 'user': FileVault was not disabled (-69550). root@usermbp ~ #

Question: How can we upgrade?

Thanks Dennis

ghost commented 3 years ago

The README talks about this:

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.

dgaastra commented 3 years ago

Hi Ben,

that is unfortunate. So the problem is with Apple and not the patcher? Question: Could you encrypt the laptop again after a restoration procedure, or would you face the same issues for the next upgrade? Thanks Dennis

seyoon20087 commented 3 years ago
root@usermbp ~ # fdesetup status
FileVault is On. 
FileVault master keychain appears to be installed. 
root@usermbp ~ # fdesetup disable
Enter the user name:user
Enter the password for user 'user':
FileVault was not disabled (-69550).

fdesetup requires root privileges.

Try this command and do a upgrade:

sudo fdesetup disable
ghost commented 3 years ago

That does not matter. You cannot turn off FileVault without restoring to the best of my knowledge. Tip to barrykn: Add a fedsetup check inside the micropatcher.

dgaastra commented 3 years ago

fdesetup requires root privileges.

Try this command and do a upgrade:

sudo fdesetup disable

Hi Seyoon, this was already ran as root. You verify it by pound sign. I usually start by sudo zsh. Thanks anyhow Dennis

seyoon20087 commented 3 years ago

fdesetup requires root privileges.

Try this command and do a upgrade:

sudo fdesetup disable

Hi Seyoon, this was already ran as root. You verify it by pound sign. I usually start by sudo zsh. Thanks anyhow

Please try disabling FileVault on System Preferences.

ghost commented 3 years ago

That does not work either. It's the same exact program that handles it.

dgaastra commented 3 years ago

Good News!

I was able to get out of the problem by using Carbon Copy Cloner to a USB stick, and then, using Carbon Copy Cloner again back to the laptop's SSD, upgrading to 11.1, and finally, re-encrypting the SSD with FileVault. All is good now!

Dennis