Jump to content


  • Content Count

  • Joined

  • Last visited

About Zhen-zen

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

662 profile views
  1. You are literally using the existing apfs firmlink in filesystem from Catalina. However that's not possible on a clear installation to a blank partition/volume. And I also suppose that you can't open Safari by just clicking the icon since that's not migrated automatically. If you run diskutil apfs list, there's also no "sealed: yes" for system volume, which should exist with VM/real Mac installation. Meanwhile, don't over exaggerate and a lot of people have already succedded in this kind of "update" way, which may break in further updates. The real native solution hasn't arrived yet.
  2. https://github.com/RehabMan/OS-X-ACPI-Battery-Driver
  3. Which step are you at? Have you got the system fully extracted to disk? And can I have context of that log? There might be other useful information several lines above. Loop of lines seems related to apfs_get_firmlink errors near it. Do you install over a existing (fresh installed) Catalina? The stage 2 ramdisk cannot be booted which makes firmlink, so we need existing links made in Catalina. So far, I think you won't have more issues. After this one is solved, you will get the welcome screen at this stage.
  4. The tutorial was first posted at I think more people can see this after posting here and make some improvements. 1. Have a (fresh installed) Catalina container While it also works in the same container with currently installed system, there might be issues when removing the volume. My friends with real Mac says you can only use Big Sur Recovery to remove the volume. For a cleaner(?) install, you can stop after the boot entry changed from "macOS installer" to volume name and leave the initial configuration to Big Sur first boot. 2. Make sure you are ready to boot even without kexts Necessary but it may depends on your configuration. For example: Switching to a 1080p monitor instead of 4K ones. Btw enable-hdmi20 is unusable since user space patching is disabled. Also there's no binary at /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay Get a USB keyboard and a mouse just in case. Check your config.plist for arguments like -disablegfxfirmware and setup NVRAM variable booter-fileset-kernel and booter-fileset-basesystem under 7C436110-AB2A-4BBB-A880-FE41995C9F82 with data type value 00. (From https://github.com/acidanthera/OpenCorePkg/commit/dea60c2a1e2ff83e3b871425d6f3b4adbcc4ef9b) Set a MaxKernel such as 19.6.0 for SMCBattery.kext and get https://github.com/RehabMan/OS-X-ACPI-Keyboard with MinKernel 20.0.0 Temporary set MaxKernel 19.6.0 for VoodooI2CHID.kext (Don't know why it may cause kp at stage 3 when creating kernel cache, but works well afterwards) I'm not sure about the USB port limit patch, because I use a pure SSDT approach that disable unnecessary ports using _UPC. 3. Install Big Sur from Installer I ran it from another Catalina and the minimum disk space required is ~51G (Big Sur) + ~15G (installed Catalina) I left 66G for the new container, but the space's still not enough. Then I found VM volume takes 2G and then mount it to delete the 2G sleepimage inside. 4. Stage 1 (first reboot) with file extracted The installer will prompt things like 29 mins remaining and stop at 17 or so. Sometimes the installer will abort just at the beginning, please reboot into the installer again. After reboot to another Catalina system, you may find that the log in a new volume called Update. Please ensure that you have that volume and/or "macOS Install Data" (hidden folder) is gone in the data volume. By the way, ramrod (or patchd) also left a log there after stage 2 if you use VM or real Mac. 5. Mount the preboot volume Open folder named by Big Sur UUID (check timestamp) sudo cp ./com.apple.installer/boot.efi ./System/Library/CoreServices/ sudo cp -r ./System/Library/PrelinkedKernels.Staged ./System/Library/PrelinkedKernels (com.apple.installer is hidden) Now you can also move /System/Library/Templates/Data/Applications/Safari.app from the system volume to /Application/ at the data volume to manually update Safari. It's not possible to do that in Big Sur. 6. Reboot and choose the entry with new volume name. (Almost finished!) 7. Go to disk utility and get a first aid. (?) 8. Personal tips The macOS installer entry is still there, however you can override it like OC's AllowSetDefault. Maybe deleting the com.apple.installer folder and edit nvram can remove it. Since the recovery entry is not usable(or just me?), I repurposed this entry by editing com.apple.installer/com.apple.Boot.plist Copy the BaseSystem.dmg with chunklist from Recovery to some place in the data volume. Change the path in boot arg from ramdisk to that dmg. It seems that those volumes (preboot, VM) can not be mounted in Big Sur, you may need to edit them in Catalina or earlier. However Recovery volume can still be mounted. Hypothesis: In stage 2 you will boot into a ramdisk that do stuffs like converting the apfs volume into new format and seal it. But real hardware will failed for issues with SMC watchdog (ramrod quit after disable_watchdog failed). And if you try to boot from that partition directly without Catalina installed first, you will get apfs errors since firmlink to data partition are not established. So when upgrading from Catalina, these errors can be avoided. But there may be some risks using old apfs format. For example, new system partition has a "Sealed: yes" attribute and snapshot feature. First aid may do some work but still unclear.
  5. @tunglamvghy1210 @Anonym323 my bad, I wiped the partition and installed it again. Now I know what's going on. Use the terminal to ls what's in the data partition. If the folder called "macOS install data" still exist, then the system files are still not extracted. Also, after the stage 1, there should be a new volume called "Update", which can also be an indicator. So the first reboot may end earlier than expected. It just shows "About 29 minutes remaining…" and then rebooted. It seems some data are written to the nvram and cause a RTC loss on my desktop. But it didn't prompt the detail after I rebooted into Catalina. That also happened last time, but I thought it's something like DW1820a PCIe bug so I just rebooted and didn't write about it. And I suppose you're also stucked at this stage. So reboot into the installer one more time and wait for the system file to be extracted completely. This time it should reboot after like 19 minutes remaining (but not 29 minutes!). Sorry for the confusion. Also please check step 5 for a fix on Safari. It's not updated automatically.
  6. How's it going? Do you have more detailx about the kp? If all the files present, at least the prelinked kernel will boot. Weird. ./System/Library/PrelinkedKernels/immutablekernel ./System/Library/PrelinkedKernels/prelinkedkernel ./System/Library/CoreServices/boot.efi Or you can also edit the com.apple.installer/com.apple.Boot.plist like I mentioned in 8 Tips. Remove or comment out the boot argument and the one with kernelcollection.
  7. Do you also have PrelinkedKernels.staged? All those files are available in the corresponding (target) location in Big Sur system volume. But I don't know why they are missing, and if that may have some problems. If you don't mind uploading the installer log in "Update" Volume, I want do do a quick diff. Also @tunglamvghy1210, do you have com.apple.installer/boot.efi ?
  8. It's a hidden folder. Use terminal.
  9. kp seems not related to those steps. If the volumes are not linked successfully, there will be loops of apfs firmlink things. What's in the kp information? Also check debug OC log with AppleDebug on and find if is kernelcache instead of kernelcollection is loaded as well as if kext injections succeed.
  10. open /Volumes @tunglamvghy1210 let me know if that works, and I will update the previous post.
  11. Just diskutil apfs list to locate the disk number and then diskutil mount diskXsY. Btw it seems that they won't be mounted on Big Sur.
  12. Weird... Maybe you can try copying those files from Big Sir System volume. Have you added the nvram variable described in https://github.com/acidanthera/OpenCorePkg/commit/dea60c2a1e2ff83e3b871425d6f3b4adbcc4ef9b ?
  13. So what's the file structure inside "System"?
  14. Mine looks like ./System ./System/Library ./System/Library/PrelinkedKernels ./System/Library/PrelinkedKernels/immutablekernel ./System/Library/PrelinkedKernels/prelinkedkernel ./System/Library/CoreServices ./System/Library/CoreServices/boot.efi ... I suppose these files are created automatically after stage 1. However they are also available in the System partition. At this stage it should have not been updated to new version and can be accessed from Catalina.
  15. What do you have in the Preboot volume? Maybe run a tree to show your folder structure? Make sure you entered the folder with Big Sur's UUID.