Jump to content
8755 posts in this topic

Recommended Posts

My experience was that it rebooted two or three times and took a long time after the first boot after updating. All is fine after that.

I tried 4-5 times and each time it would reboot. It never gets to XX time remaining.
I can’t attach my config on my phone but the latest config is in the clover general discussion thread.



Sent from my iPhone using Tapatalk

Hello everyone, I am facing a strange issue and your feedback is welcome.

@vit9696 I cannot seem to be able to remove the NVRAM parameter that contains the OpenCore version.

% nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version	UNK-000-0000-00-00

% sudo nvram -d 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
Password:

% nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version        
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version	UNK-000-0000-00-00

It seems the variable cannot be deleted with simple user or sudo, I still cannot remove it.

Rebooting with OpenCore bootloader and selecting to clean NVRAM does not seem to solve the issue.

Any idea if there is a way to be able to remove it, via some OpenCore parameter or even UEFI Shell perhaps?

Thank you in advance.

11 hours ago, SavageAUS said:

Is there any reason I might get constant reboots after the first update stage? My AMD machine boots and runs fine but updating to 12.1 just doesn’t want to happen.
After the first reboot I choose macintosh hd then not long after it reboots.


Sent from my iPhone using Tapatalk

I had the same issue in my FX-6300 hackintosh too. Unable to update to Monterey 12.1 from 12.0: It's Macintosh HD always got reboot loop. The only solution is got updated Macintosh HD from other hackintoshs, then it can reboot 3 times successfully to newer version. No such an issue in my Ryzen 1700X hackintosh with both OpenCore 0.7.6 and Clover 5141.

[Solved on 2021-11-22]
This  issue was solved by the following method:

(1) OpenCore 0.7.5

(2) SMBIOS=MacPro7,1
(3) SecureBootMode=j160 To get updated Macintosh HD at first
(4) SecureBootMode=Disabled To reboot for 3 times and complete update process without reboot loop now !

[Waiting for solution]
I don't know why using the similar method of HWTarget in Clover 5142 did not work for me.

Clover's config.plist attached here for reference.

config.plist

Edited by jsl2000
  • Like 1
I had the same issue in my FX-6300 hackintosh too. Unable to update to Monterey 12.1 from 12.0: It's Macintosh HD always got reboot loop. The only solution is got updated Macintosh HD from other hackintoshs, then it can reboot 3 times successfully to newer version. No such an issue in my Ryzen 1700X hackintosh with both OpenCore 0.7.6 and Clover 5141.
[solved on 2021-11-22]
This  issue was solved by the following method:
(1) OpenCore 0.7.5
(2) SMBIOS=MacPro7,1
(3) SecureBootMode=j160 To get updated Macintosh HD at first
(4) SecureBootMode=Disabled To reboot for 3 times and complete update process without reboot loop now !
[Waiting for solution]
I don't know why using the similar method of HWTarget in Clover 5142 did not work for me.
Clover's config.plist attached here for reference.
config.plist

I’ll take a look at your config later. My smbios is already MacPro7,1 but securebootmode is default or disabled. I’ll try j60 from USB for first reboot.
Checked and mines set to Disabled. Will changing it too Default help?


Sent from my iPhone using Tapatalk
58 minutes ago, 1Revenger1 said:

Its added by Opencore every boot, but only exists in memory. It is not written to flash…

@MacKonsti

Do you have native or emulated NVRAM?

Do you have LegacyEnable and LegacyOverwrite true?

 

Edited by miliuco

Thank you @1Revenger1 and @miliuco for your help and very useful feedback. It seems I found the culprit.

 

On my NUC8 I was using Clover and have been trying to migrate to OpenCore as an alternative solution but in parallel; so Hackintool all of a sudden reports OpenCore as detected, despite having booted with Clover at that session.

So I raised an issue on GitHub and was told that Hackintool detected this value UNK-000-0000-00-00 as there existed an entry in 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version which was mistaken for OpenCore being booted.

Reverting to a previous Clover release, this is not happening. So something must have slipped in latest (today) Clover release, which made me mistakingly consider this was NVRAM-stored by OpenCore.

But thanks to @1Revenger1 comment that this is injected in memory, it made me suspicious and I traced back the issue...

 

So @1Revenger1 mate, can I safely assume that any parameter saved in 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 means this is injected per OpenCore boot session and not stored in the actual NVRAM of the device?

 

Apologies for troubling you with my original question, but life is full of learning I guess. Thanks to all of you.

  • Like 2

I try to build VirtualSMC-master but Build is succeeded I can't find Debug folder please help.

Happy Christmas to All

.62761006_ScreenShot2021-12-25at5_53_59AM.thumb.png.4311adbd2b93fe6ad051ce4577d7443c.png

3 hours ago, Stefanalmare said:

Or use this: VirtualSMC.sh

 

Excellent work, it's an automatised version of the steps required for build VirtualSMC. Thanks.

 

In another thread of the forum, @Shaneee and @chris1111 talked about doing it this way:

Your script do the work fast, at the end VirtualSMC release version and plugins are in the VirtualSMC/build/Release/package/Kexts folder.

 

Edited by miliuco
  • Like 2

Another cool trick for OpenCore theme;  see ➤  MinimalmacOS12 theme with new Selected.icns (Monterey Disk) B) 

This is what it like on my MacBookPro 2013 😀

OpenCore.gif.5851955ae66b8043fea499f8a68bea76.gif

Edited by chris1111
  • Like 4
3 hours ago, miliuco said:

 

Excellent work, it's an automatised version of the steps required for build VirtualSMC. Thanks.

 

In another thread of the forum, @Shaneee and @chris1111 talked about doing it this way:

Your script do the work fast, at the end VirtualSMC release version and plugins are in the VirtualSMC/build/Release/package/Kexts folder.

 

You can make your own script:

Lilu.sh BrcmPatchRAM.sh FeatureUnlock.sh WhateverGreen.sh VoodooPS2.sh

Edited by Stefanalmare
  • Like 2
  • Thanks 1
4 hours ago, miliuco said:

 

Excellent work, it's an automatised version of the steps required for build VirtualSMC. Thanks.

 

In another thread of the forum, @Shaneee and @chris1111 talked about doing it this way:

Your script do the work fast, at the end VirtualSMC release version and plugins are in the VirtualSMC/build/Release/package/Kexts folder.

 

I have separate folders for each project and use sym links for anything that needs to be placed relative to another location. This way you can put your repositories wherever you like.

 

For example, I have a gfxutil folder containing repositories for my fork and the upstream fork, named joevt-gfxutil and acidenthera-gfxutil. I can add other folders for other forks or different branches or different commits for easy comparing. The gfxutil folder can contain notes and BBEdit worksheets and to-do lists without affecting the repository folders. The gfxutil repository requires an edk2 folder in the parent folder but my edk2 repository is nowhere near the gfxutil repository. Instead, I just put a edk2 symlink in the gfxutil folder (parent of joevt-gfxutil and acidenthera-gfxutil).

ln -s /Volumes/Work/Programming/EFIProjects/edk2/tianocore-edk2 /Volumes/Work/Programming/EFIProjects/gfxutil/edk2

 

Another example, The RefindPlus build process requires that a RefindPlusPkg be in its edk2 folder but the name of the folder is joevt-RefindPlus and it is not in the edk2 folder. So I put symlink named RefindPlusPkg in the edk2 folder that points to my joevt-RefindPlus repository.

ln -s "${WORK_DIR}" "${EDK2_DIR}/RefindPlusPkg"

 

So for joevt-Lilu, I put a symlink named MacKernelSDK in the repository. The symlink points to the acidenthera-MacKernelSDK repository. Same for joevt-Whatevergeen. joevt-Whatevergreen also has a symlink named Lilu.kext that points to the debug build in the joevt-Lilu folder.

cd /Volumes/Work/Programming/KextProjects/Lilu/joevt-Lilu
ln -s /Volumes/Work/Programming/KextProjects/MacKernelSDK/acidanthera-MacKernelSDK MacKernelSDK
cd /Volumes/Work/Programming/KextProjects/WhateverGreen/joevt-WhateverGreen
ln -s /Volumes/Work/Programming/KextProjects/Lilu/joevt-Lilu/DerivedData/Lilu/Build/Products/Debug/Lilu.kext Lilu.kext
ln -s /Volumes/Work/Programming/KextProjects/MacKernelSDK/acidanthera-MacKernelSDK MacKernelSDK

 

edit: @Stefanalmare's setup & build scripts also uses symlinks.

 

Edited by joevt
  • Like 4

hi. i have a question.

my hp 4230s is boot on 10.6~10.13.6 with UEFI.
but not support Native NVRAM.
so i can't save brightness value after reboot.
i tried to install oc nvram script. but no luck.
how can i use emulate NVRAM+UEFI mode?

thanks in advance.

Sent from my SM-N960N using Tapatalk

thanks. i will try

Sent from my SM-N960N using Tapatalk

I can't get either of my hacks (in sig) to boot Big Sur in safe mode with latest official OC. I get a prohibited sign with a support.apple.com/mac/startup url on screen.

 

EnableSafeModeSlide is set to true. Is there anything else I could try?

×
×
  • Create New...