fusion71au Posted August 24, 2020 Share Posted August 24, 2020 (edited) 4 hours ago, fuzzylogic said: still get the same results even with a new install (trying to delete snapshots) Spoiler You need to perform the commands in my guide from terminal, booted into Big_Sur Recovery or Installer USB. From your screenshots, it is obvious that you are booted into the completed Big_Sur volume, not the Recovery/Installer terminal which has a bash prompt (also in Recovery, you are automatically the admin so no need for sudo)... -bash-3.2# PS Extra Info As reported by @AppleBreak and confirmed by @ameenjuz, the "UpdateOptions.plist method" to prevent sealing of the Big_Sur volume has the unfortunate side-effect of later preventing the deletion of APFS snapshots from Recovery/Installer USB, throwing out "Operation not permitted" and "Insufficient privileges" errors. Therefore if you want to prevent volume sealing and allowing access to Big_Sur volume from older macOS, I recommend using @ASentientBot's hax2 patched installer or interrupting phase3 installation method. Edited August 24, 2020 by fusion71au Extra info 5 Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted August 24, 2020 Share Posted August 24, 2020 3 hours ago, Gumuskalp said: very simple diskutil apfs listSnapshots /Volumes/BigSur diskutil apfs deleteSnapshot disk3s5 -uuid ????????-????-????-????-???????????? This worked perfectly for me. Thank you Gumuskalp. Link to comment Share on other sites More sharing options...
fuzzylogic Posted August 24, 2020 Share Posted August 24, 2020 35 minutes ago, fusion71au said: You need to perform the commands in my guide from terminal, booted into Big_Sur Recovery or Installer USB. From your screenshots, it is obvious that you are booted into the completed Big_Sur volume, not the Recovery/Installer terminal which has a bash prompt (also in Recovery, you are automatically the admin so no need for sudo)... -bash-3.2# I actually booted from my usb flash drive into big sur, even when done in recovery I still get the same result, I will post to show you in recovery exactly the same outcome, thank you for responding Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted August 24, 2020 Share Posted August 24, 2020 4 minutes ago, fuzzylogic said: I actually booted from my usb flash drive into big sur, even when done in recovery I still get the same result, I will post to show you in recovery exactly the same outcome, thank you for responding I booted into installer to run terminal from recovery. I had no issues. For me the surprise was I didn't even need to disable CSR Link to comment Share on other sites More sharing options...
fuzzylogic Posted August 25, 2020 Share Posted August 25, 2020 1 hour ago, sonicthehedgehog2 said: I booted into installer to run terminal from recovery. I had no issues. For me the surprise was I didn't even need to disable CSR hurray the nutter did it, I deleted the xxxsnapshot!! pulls shirt over my head and crashes into the goal post!! rofl Link to comment Share on other sites More sharing options...
mick3lson Posted August 25, 2020 Share Posted August 25, 2020 6 hours ago, Stefanalmare said: This is third time you ask me this! On SAME disk. Not very polite to don't believe me and ask for print screen but here you have. Give me also your open core EFI to see how you managed to have mic after wake. Arhivă.zip Sorry I didn't read when you wrote that you have installed on single disk, with your efi I had panic when I boot Big Sur, maybe for different cpu and display, I've i5 3230m and display 1080p, I've to fix this issue. Regarding Multiboot on my laptop with your efi booting only with OpenCore bootloader, Ubuntu boot correctly but Windows 10 crash, I've try to format my disk and start from scratch, can you explain if you have installed before Big Sur or Windows 10. I attach my efi folder. HP4540s 1080p i53230m.zip Link to comment Share on other sites More sharing options...
ameenjuz Posted August 25, 2020 Share Posted August 25, 2020 7 hours ago, fusion71au said: You need to perform the commands in my guide from terminal, booted into Big_Sur Recovery or Installer USB. From your screenshots, it is obvious that you are booted into the completed Big_Sur volume, not the Recovery/Installer terminal which has a bash prompt (also in Recovery, you are automatically the admin so no need for sudo)... is there a way to avoid sealing partition? old way do not work using interupting thirth phase of installation Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted August 25, 2020 Share Posted August 25, 2020 7 hours ago, fuzzylogic said: hurray the nutter did it, I deleted the xxxsnapshot!! pulls shirt over my head and crashes into the goal post!! rofl Yay, nice to have a fan Link to comment Share on other sites More sharing options...
fusion71au Posted August 25, 2020 Share Posted August 25, 2020 3 hours ago, ameenjuz said: is there a way to avoid sealing partition? old way do not work using interupting thirth phase of installation 10 hours ago, fusion71au said: PS Extra Info Therefore if you want to prevent volume sealing and allowing access to Big_Sur volume from older macOS, I recommend using @ASentientBot's hax2 patched installer... 1. Create Big_Sur Installer USB with createinstallmedia method 2. Boot to Installer USB, open Terminal to disable SIP & then set NVRAM boot-args csrutil disable csrutil authenticated-root disable nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" reboot 3. Download and extract Hax2.app + Source into your home folder 4. With your Big_Sur Installer USB plugged in or alternatively, with "Install macOS Big Sur Beta.app" in /Applications, run Hax2.app by double clicking on it. If you did everything correctly, you should not see any errors and the Installer app should automatically open ---> choose target partition to install...installation proceeds after reboot... Spoiler 5. After installation, you should be able to access the Big_Sur volume from older macOS eg Mojave... Spoiler 6 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 25, 2020 Share Posted August 25, 2020 Hi all, Today I'm at work and her I have an Mac mini 2018, and after the Beta 4, it says that have an update and when I try to install it again... it don't install. How do I solve this? Thanks in Advance ... Link to comment Share on other sites More sharing options...
AlfredoM Posted August 25, 2020 Share Posted August 25, 2020 (edited) 12 hours ago, fusion71au said: 1. Create Big_Sur Installer USB with createinstallmedia method 2. Boot to Installer USB, open Terminal to disable SIP & then set NVRAM boot-args csrutil disable csrutil authenticated-root disable nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" reboot 3. Download and extract Hax2.app + Source into your home folder 4. With your Big_Sur Installer USB plugged in or alternatively, with "Install macOS Big Sur Beta.app" in /Applications, run Hax2.app by double clicking on it. If you did everything correctly, you should not see any errors and the Installer app should automatically open ---> choose target partition to install...installation proceeds after reboot... Reveal hidden contents 5. After installation, you should be able to access the Big_Sur volume from older macOS eg Mojave... Reveal hidden contents @fusion71au Can you send me please a download Link for Hax2.app Edited August 25, 2020 by AlfredoM Link to comment Share on other sites More sharing options...
Max.1974 Posted August 25, 2020 Share Posted August 25, 2020 (edited) 1 hour ago, AlfredoM said: @fusion71au Can you send me please a download Link for Hax2.app macrumors Hax2....app Edited August 25, 2020 by Max.1974 1 Link to comment Share on other sites More sharing options...
iCanaro Posted August 25, 2020 Share Posted August 25, 2020 13 hours ago, fusion71au said: PS Extra Info Therefore if you want to prevent volume sealing and allowing access to Big_Sur volume from older macOS, I recommend using @ASentientBot's hax2 patched installer... 19 minutes ago, Max.1974 said: macrumors Hax.2app hax2 1 Link to comment Share on other sites More sharing options...
AlfredoM Posted August 26, 2020 Share Posted August 26, 2020 (edited) 1 hour ago, iCanaro said: hax2 @iCanaro and @Max.1974 Thank you my Friend.. ist this from 25.07.2020 not to old ? i hav read exist a Hax3.app ? I successfully removed the snapshot from my clean reinstallation of Big Sur Beta5 following the instructions from @fusion71au and now I have full write access to this partition. Is it now possible to replicate the Big Sur Beta5 with the Disk Utility and then restore the image to another partition? and does the removed snapshot stay away? or is the OS sealed again? Edited August 26, 2020 by AlfredoM 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted August 26, 2020 Share Posted August 26, 2020 Hi @AlfredoM you can try version 3 that app. Thanks and good luck!!! 1 Link to comment Share on other sites More sharing options...
fusion71au Posted August 26, 2020 Share Posted August 26, 2020 (edited) On 8/26/2020 at 10:18 AM, AlfredoM said: this from 25.07.2020 not to old ? i hav read exist a Hax3.app ? Is it now possible to replicate the Big Sur Beta5 with the Disk Utility and then restore the image to another partition? Hax2 from the provided MacRumors link still works for latest Big Sur Beta 5 to prevent APFS volume sealing (see screenshot from earlier post ). Hax3 was designed for a different purpose - to bypass firmware checks so that old macs ("pre High Sierra compatible") with old firmware could still install Big Sur. Haven't tested it myself to see if it also prevents APFS sealing. Edit - Hax3 also results in unsealed Big Sur volume. AFAIK, you can't clone Big Sur with Disk Utility (I tried a while back but boot failed. In contrast, you can clone Catalina successfully with DU from Installer USB). Have to do sector by sector disk clone eg with dd. Edited August 29, 2020 by fusion71au Confirm both Hax2 & Hax3 prevent volume sealing. 7 Link to comment Share on other sites More sharing options...
AlfredoM Posted August 26, 2020 Share Posted August 26, 2020 (edited) Thank you friend @fusion71au for your information. I wanted to ask again how I can clone an unsealed partition in order to restore it to another partition? Is there any information? thank you Edited August 26, 2020 by AlfredoM Link to comment Share on other sites More sharing options...
iCanaro Posted August 26, 2020 Share Posted August 26, 2020 as far as I know, R-Drive Image clones raw bits per bit 1 Link to comment Share on other sites More sharing options...
AlfredoM Posted August 26, 2020 Share Posted August 26, 2020 R-Disk is only for Windoof Link to comment Share on other sites More sharing options...
iCanaro Posted August 26, 2020 Share Posted August 26, 2020 24 minutes ago, AlfredoM said: R-Disk is only for Windoof Negative! you're not up to date, R-Drive Image clones bits for macOS bits, so well, that if you start OC or Clover with both partitions connected, it doesn't know which one to start by being identical and it only shows you one personally tested, and not only me 3 Link to comment Share on other sites More sharing options...
AlfredoM Posted August 26, 2020 Share Posted August 26, 2020 (edited) iCanaro yes ok I understand, so I have to run the R-Drive under Windows 10 and then I can clone a macOS partition byte for byte or sector by sector is that correct? Edited August 26, 2020 by AlfredoM Link to comment Share on other sites More sharing options...
iCanaro Posted August 26, 2020 Share Posted August 26, 2020 you can do it even like this... I use a LivePE important is to use latest release of R-Drive Image 1 Link to comment Share on other sites More sharing options...
AlfredoM Posted August 26, 2020 Share Posted August 26, 2020 2 minutes ago, iCanaro said: you can do it even like this... I use a LivePE important is to use latest release of R-Drive Image Yes, I have just loaded the latest version of R-Drive Image for Windows, I have installed Windows 10 on a different SSD so no problem. I also installed the Paragon APFS in Windows10. I will then test it out and report tonight. Link to comment Share on other sites More sharing options...
fusion71au Posted August 26, 2020 Share Posted August 26, 2020 (edited) On 8/26/2020 at 11:09 AM, fusion71au said: AFAIK, you can't clone Big Sur with Disk Utility (I tried a while back but boot failed... Actually it seems you can clone an unsealed Installed Big_Sur with beta5 DU (tested in a Virtual Machine) . Prerequisites 1. Unsealed Big_Sur beta5 installation (Hax2 method) with APFS snapshots removed after the installation Edit - Cloning proceeds OK, even with snapshots still present in original source 2. Big_Sur Beta5 Installer USB made with createinstallmedia 3. Target HD/SSD the same size or larger than HD with Source Big_Sur Beta5 installation Procedure 1. Boot to Big_Sur Beta5 Installer USB and open Disk Utility Spoiler 2. Erase target HD, formatted as GUID, APFS filesystem. In this example, I named it "macOS", while the source installation was "Big_Sur" Spoiler 3. On the LHS list pane, click on the macOS clone volume. Click on Restore button on DU menu bar, choose source Big_Sur in "Restore from", then click Restore Spoiler 4. After this first phase, the Big_Sur system volume will have been restored but not yet Big_Sur - Data. On the LHS list pane, click on the Big_Sur -Data volume of the clone (will be empty), then click the Restore button on DU menu bar. This time, choose source Big_Sur - Data in "Restore from", then click Restore Spoiler 5. After restoring both the System and Data volumes to the clone, shut down the system. Remove the original Big_Sur system HD (and also the Installer USB), then reboot the system to the Clone HD. Note: during the clone process, the "Update" volume was not recreated on the Clone but a "live" snapshot was. The cloned APFS filesystem was still unsealed and accessible from Mojave... Spoiler 5 hours ago, d5aqoep said: @fusion71au Does Big Sur Beta update correctly with built in updater to next beta after you remove snapshots and have unsealed volume? Sealing and snapshots are related (they both occur during the third installation phase) but are separate processes. The default vanilla installation results in a sealed volume and creates a single APFS snapshot ---> OTA automatic updates complete normally. However, it is also possible to manually remove the snapshot post install ---> sealed volume with no snapshots. IIRC, if you manually remove all your APFS snapshots, the builtin OTA software update is still offered but the upgrade process fails later on with some error. An unsealed APFS volume allows older macOS to access it but can still have APFS snapshots associated with it eg after install with Hax2 method, an APFS snapshot still remains (which can similarly be removed later on, manually). I'm not sure whether sealing by itself affects OTA automatic updates of Big Sur since I usually perform my upgrades with the full installer app ---> bypasses the problem. Edited August 27, 2020 by fusion71au Answer @d5aqoep's query 6 2 Link to comment Share on other sites More sharing options...
ANTIKO Posted August 27, 2020 Share Posted August 27, 2020 The fight with Big Sur continues)). Now the bootloader startup stops at these lines. What else could be the problem? 1 Link to comment Share on other sites More sharing options...
Recommended Posts