mick3lson Posted July 18, 2020 Share Posted July 18, 2020 (edited) I'm trying to create macOS pendrive from an installed opencore Big Sur beta2, with this command: sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction but I have an error with this message: dyld: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD Referenced from: /Applications/Install macOS Big Sur Beta.app/Contents/Resources/createinstallmedia Reason: image not found but the image is already present dowloaded from another pc and copied in applications folder. Edited July 18, 2020 by mick3lson Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730866 Share on other sites More sharing options...
lottenow Posted July 18, 2020 Share Posted July 18, 2020 1 hour ago, mnfesq said: I'm still having the same problem as well. It's not just you. Would you be able to sum up what options you tried? So I can try and go by exclusion on my machine with your tests and see if I can get a positive result. Thanks! Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730878 Share on other sites More sharing options...
Matgen84 Posted July 18, 2020 Share Posted July 18, 2020 48 minutes ago, mick3lson said: I'm trying to create macOS pendrive from an installed opencore Big Sur beta2, with this command: sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction but I have an error with this message: dyld: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD Referenced from: /Applications/Install macOS Big Sur Beta.app/Contents/Resources/createinstallmedia Reason: image not found but the image is already present dowloaded from another pc and copied in applications folder. Sound like a corrupt installer or a copy problem from your other PC. Try to create USB Installer from the first PC to see the result Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730879 Share on other sites More sharing options...
mick3lson Posted July 18, 2020 Share Posted July 18, 2020 (edited) 1 hour ago, eSaF said: Rename your USB Drive Untitled and copy this script in Terminal exactly as this - sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled. Good luck. Unfortunately don't work even renaming the pendrive, I can't be able with macOS Developer Access Utility to download the install app to try with new one downloaded. 42 minutes ago, Matgen84 said: Sound like a corrupt installer or a copy problem from your other PC. Try to create USB Installer from the first PC to see the result Yep corrupted file, solved. Edited July 18, 2020 by mick3lson 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730880 Share on other sites More sharing options...
Riley Freeman Posted July 18, 2020 Share Posted July 18, 2020 3 hours ago, eSaF said: Have you tried cleaning the NVRAM then reboot to the named drive Opencore? Had that with Catalina and that method cured that pesky error. Good luck. Pretty sure I'd tried that before but I did again. With the first boot there was no error message, but it returned after a reboot. There's no panic in any of the CrashReporter locations or logs but there are shutdownstalls. However, I doubt they would trigger the message? Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730889 Share on other sites More sharing options...
Takiller Posted July 18, 2020 Share Posted July 18, 2020 You see these Apple people are taking their time with the release of the Big Sur public beta, just to try and make it more difficult for us hackintoshers Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730893 Share on other sites More sharing options...
Takiller Posted July 18, 2020 Share Posted July 18, 2020 9 minutes ago, eSaF said: And where did you get that bit of information from please tell. It is just my gut feeling and I so hope it is wrong Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730896 Share on other sites More sharing options...
Takiller Posted July 18, 2020 Share Posted July 18, 2020 16 minutes ago, eSaF said: Gut feeling! Ok - Well Big Sur came out not long ago so with the way Apple released this OS is inline with previous releases so you can be rest assured it's has nothing to do with thwarting hackintoshers. You do realise we are also among the biggest testers for their OSs whether they admit it or not so ignore your gut feeling and wait for the Public Beta. I hope it will come with the bluetooth fix for audio and also a fix for audio device selection within the music app. Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730902 Share on other sites More sharing options...
mnfesq Posted July 18, 2020 Share Posted July 18, 2020 (edited) 6 hours ago, lottenow said: Would you be able to sum up what options you tried? So I can try and go by exclusion on my machine with your tests and see if I can get a positive result. Thanks! I have tried just about every possible configuration of OC and Clover. With both bootloaders, I can boot to the USB installer or to a USB hard drive with an installation of Big Sur on it (made on a real Mac). No matter what configuration I use, or what drivers I use or what kexts I use, or what DSDT/SSDT I use, I cannot get any of the plugins for IOAHCIFamily.kext to work. (I have a DVD drive on my laptop so both SATA and ATAPI devices cannot be read). At this point, I am thinking that the issue may likely be the BIOS on my HP laptop. It cannot be configured and all advanced options are locked. However, SATA is set to AHCI so it should work. I am at a loss to understand what to do next. P.S. I took out my SATA hard drive and slipped it into a USB adapter and was able to install Big Sur on it. I then put it back into the SATA slot in the laptop and it could no longer be located when booting up. Edited July 18, 2020 by mnfesq 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730918 Share on other sites More sharing options...
arsradu Posted July 18, 2020 Share Posted July 18, 2020 (edited) Hi guys, I'm trying to make a fresh installation of Big Sur and...apparently I can't. It always reboots (looks like it's around the ramrod section). For what I could see online, you're supposed to either use VirtualSMC with boot-arg vsmcgen=1, oor use FakeSMC instead. Well, I tried both, including building Lilu + VirtualSMC from source. Nothing seems to work. I didn't follow this thread from the beginning, so if this has been discussed before, and if that fix still works with Beta 2, could you, please, help me with a link? Apparently starting the installation from Big Sur itself doesn't work (error: "Current device configuration and target is invalid for install in the current state. Please try again.") and installation from a USB drive doesn't work either (reboot). The only method that worked for me so far is installing it over Catalina. But that's not a clean install. So...any idea? Am I missing something? I'm using OC 0.6.0 (built from sources). Edited July 18, 2020 by arsradu 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730919 Share on other sites More sharing options...
MorenoAv Posted July 19, 2020 Share Posted July 19, 2020 1 hour ago, arsradu said: Hi guys, I'm trying to make a fresh installation of Big Sur and...apparently I can't. It always reboots (looks like it's around the ramrod section). For what I could see online, you're supposed to either use VirtualSMC with boot-arg vsmcgen=1, oor use FakeSMC instead. Well, I tried both, including building Lilu + VirtualSMC from source. Nothing seems to work. I didn't follow this thread from the beginning, so if this has been discussed before, and if that fix still works with Beta 2, could you, please, help me with a link? Apparently starting the installation from Big Sur itself doesn't work (error: "Current device configuration and target is invalid for install in the current state. Please try again.") and installation from a USB drive doesn't work either (reboot). The only method that worked for me so far is installing it over Catalina. But that's not a clean install. So...any idea? Am I missing something? I'm using OC 0.6.0 (built from sources). Hi @arsradu, how are you my friend? From my limited knowledge the boot.arg vsmcgen=1 isn't necessary anymore with last commits from OpenCore and new kexts, today I installed macOS Big Sur in another ssd that I own and all went well I upload my config.plist for you to see if it helps. Good luck config.plist 2 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730923 Share on other sites More sharing options...
STLVNUB Posted July 19, 2020 Share Posted July 19, 2020 (edited) Why is Big Sur the default boot in both OC and Clover, clearing NVRAM does not fix the problem ? Or am I the only one with this problem ? Edit: Fixed the problem by hiding it in Clover Edited July 20, 2020 by STLVNUB 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730924 Share on other sites More sharing options...
MorenoAv Posted July 19, 2020 Share Posted July 19, 2020 4 minutes ago, STLVNUB said: Why is Big Sur the default boot loader in both OC and Clover, clearing NVRAM does not fix the problem ? Or am I the only one with this problem ? Today I connected my windows ssd and I had to go to system preferences and change the default from windows 10 to macOS Big Sur... 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730925 Share on other sites More sharing options...
Sherlocks Posted July 19, 2020 Share Posted July 19, 2020 Why is Big Sur the default boot loader in both OC and Clover, clearing NVRAM does not fix the problem ? Or am I the only one with this problem ? press ctrl+macos entry number key나의 SM-N960N 의 Tapatalk에서 보냄 2 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730928 Share on other sites More sharing options...
STLVNUB Posted July 19, 2020 Share Posted July 19, 2020 1 hour ago, Sherlocks said: press ctrl+macos entry number key 나의 SM-N960N 의 Tapatalk에서 보냄 Clover still persists in booting Big Sur Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730934 Share on other sites More sharing options...
Max.1974 Posted July 19, 2020 Share Posted July 19, 2020 If I'm understood, are you try choose a startup disk? Try on boot make a choice your disk that you want, and type ctrl+i and ctrl + enter, so to the next boot you get the disk default bootloader. But all the time that you reset Nvram you need type again. Don't forget put a number in boot timeout...non zero... Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730936 Share on other sites More sharing options...
nmano Posted July 19, 2020 Share Posted July 19, 2020 Hi All I can't Install. If I choose Install Hard Drive->back to this screen same time. How to fix this error? Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730959 Share on other sites More sharing options...
arsradu Posted July 19, 2020 Share Posted July 19, 2020 9 hours ago, MorenoAv said: Hi @arsradu, how are you my friend? From my limited knowledge the boot.arg vsmcgen=1 isn't necessary anymore with last commits from OpenCore and new kexts, today I installed macOS Big Sur in another ssd that I own and all went well I upload my config.plist for you to see if it helps. Good luck config.plist Hello! I'm ok, just a bit frustrated with this issue. Can't seem to get it to boot into the 2nd/3rd step of the installer... All good until then. But then, it shows this screen, then a few more lines underneath and sudden reboot. With or without vsmcgen=1 (which I now removed since I already have the newest Lilu + VirtualSMC), same thing... I'll try to start it all over, in case that makes any difference... Spoiler 2 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730960 Share on other sites More sharing options...
MorenoAv Posted July 19, 2020 Share Posted July 19, 2020 (edited) @arsradu, That screen is the screen of death, it was what happened to me in the first try at install Big Sur beta 1 ... after that with the new commits of OpenCore and new kexts never happened again... but you can do it I know it's a question of time... Edited July 19, 2020 by MorenoAv 2 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730962 Share on other sites More sharing options...
Diepnguyen90hn Posted July 19, 2020 Share Posted July 19, 2020 I have same issue as @arsradu the installer is rebooting loop. I tried both fakesmc or virtualsmc. All kext are latest. Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730968 Share on other sites More sharing options...
MorenoAv Posted July 19, 2020 Share Posted July 19, 2020 I leave here my EFI Folder it may help you guys... EFI.zip Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730973 Share on other sites More sharing options...
d5aqoep Posted July 19, 2020 Share Posted July 19, 2020 Any USB Port Limit removal patch for Beta 2? Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730980 Share on other sites More sharing options...
arsradu Posted July 19, 2020 Share Posted July 19, 2020 (edited) 2 hours ago, MorenoAv said: @arsradu, That screen is the screen of death, it was what happened to me in the first try at install Big Sur beta 1 ... after that with the new commits of OpenCore and new kexts never happened again... but you can do it I know it's a question of time... Freaking finally! Done. Installed. God dang it! Looks like you were right. It was only a matter of time...and perseverance. :)) Now, the question is: what was different? Well, quite a few things actually. 1. switched back to VirtualSMC from FakeSMC. Same exact version as before. So still up to date. But no other difference there. 2. erased the volume I wanted to install Big Sur on, just to make sure there's no dirt from previous attempts (I believe this might have made the entire difference here). 3. cleared NVRAM right before booting into the installer 4. added corresponding NVRAM info (boot-args, UIScale, all that) to NVRAM -> Delete, as shown in the sample.plist. Previously I didn't have it. Didn't cause any issues with Catalina, but I guess it could be different with Big Sur. I'm still not sure how exactly is this actually working, but I'll try to read a bit more about it. Cause, as a normal user, I find it a bit confusing. 5. added run-efi-updater to NVRAM (7C436110-AB2A-4BBB-A880-FE41995C9F82) and set it to "No" (string). 6. added rtc-blacklist to NVRAM (4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102) but left it empty for now. 7. set csr-active-config in NVRAM to FF0F0000 One thing to note is that, in my attempts to make it boot, I also added booter-fileset-basesystem and booter-fileset-kernel to NVRAM. But that actually made things worse. It wouldn't even reach the first installer screen anymore. So, at least in my particular case, removing that also made a difference. And there were quite a lot of restarts during this installation (about 5 if I'm not mistaken). Anyway, it's all good now. Thank you very much for your support. Edited July 19, 2020 by arsradu 2 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730982 Share on other sites More sharing options...
Alex HQuest Posted July 19, 2020 Share Posted July 19, 2020 2 hours ago, nmano said: Hi All I can't Install. If I choose Install Hard Drive->back to this screen same time. How to fix this error? You likely has something identified to macOS as a battery source (Corsair’s CommanderPro USB module is the most common), which reports 0% charge. This causes the installer to fail, since any battery below a certain threshold will cause the installer to fail, even on real Apple hardware. 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730983 Share on other sites More sharing options...
Cyberdevs Posted July 19, 2020 Share Posted July 19, 2020 @arsradu Hi there, In my experience only resetting the NVRAM and erasing the hard disk were necessary, the booter-fileset-basesystem and booter-fileset-kernel are not needed anymore with the latest releases of OC they were only needed when you wanted to boot from a preinstalled version of Big Sur. But the reboot issue is now happens with Clover's latest releases (5120) and I think (fingers crossed) it will be resolved soon. 2 1 Link to comment https://www.insanelymac.com/forum/topic/344428-pre-release-macos-big-sur/page/39/#findComment-2730984 Share on other sites More sharing options...
Recommended Posts