3.0.0 have some problem

myselfghost commented 2 years ago

Update from 2.4 to 3.0.0，When the computer starts, the computer will crash when you go to the login interface

samwzlim commented 2 years ago

Update from 2.4 to 3.0.0，When the computer starts, the computer will crash when you go to the login interface

Can you provide a screenshot of the error you are facing? It's difficult to tell what you mean by 'crashing on login interface'.

samwzlim commented 2 years ago

Upon updating to the latest EFI release, I'm getting this error when trying to boot (during Huawei logo screen). Not sure what went wrong, all I did was replace my previous EFI with the latest one.

linshixiong commented 2 years ago

I have the same problem, computer freeze and restart after logging in

samwzlim commented 2 years ago

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick for me; the machine now boots without any errors. However, is it safe to leave SecureBootModel at Disabled? I had a look through the guide to enable BIOS Secure Boot with OpenCore, and it doesn't seem like a recommended thing to do. However, I solely run macOS on my machine (no dualboot), so I dont have to be worried about enabling secure boot right?

samwzlim commented 2 years ago

Alright, I'm experiencing freezing issues as well; happens a few minutes after logging in. The system will stop responding and I'm forced to restart it. Compared to the previous EFI, this release is much more unstable. I'm currently on macOS Monterey Beta 6

ldan93 commented 2 years ago

I also had to disable SecureBoot, but I haven't noticed any kind of instability at the moment with release 3.0.0 ... (Big Sur 11.6)

Edit : I have updated my MLB, SystemSerialNumber and SystemUUID values, I don't know if this is related...

BigEmperor26 commented 2 years ago

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick for me; the machine now boots without any errors. However, is it safe to leave SecureBootModel at Disabled? I had a look through the guide to enable BIOS Secure Boot with OpenCore, and it doesn't seem like a recommended thing to do. However, I solely run macOS on my machine (no dualboot), so I dont have to be worried about enabling secure boot right?

Also setting to j132 works. Check the guide to enable SecureBoot with OpenCore in this repo, just follow steps from 1 to 4

profzei commented 2 years ago

It's quite weird that

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick

Did someone have tried to reset NVRAM at first reboot? Honestly, I don't know if it could do the trick since with these settings I never had any issue for

Monterey Beta 5 + update OTA to Monterey Beta 6
a clean install of Big Sur 11.6 (which is now my running system)

Moreover, in "official" OpenCore Configuration.pdf, the setting Default points to x86legacy which is the minimum required for running Big Sur (and then Monterey)... the fact that setting j132 is working and Default not seems to point out that macOS didn't recognize your system as Big Sur but as older... For this reason, I suggested to try to reset your NVRAM. If, instead, you are running macOS Catalina, then it is obvious that the setting Default is wrong, but all my EFI are meant for Big Sur+ (then I'll add the changes needed for Catalina...)

Did everyone update MLB, SystemSerialNumber and SystemUUID values? Honestly I don't remember whether these values are checked (or not) during AppleSecureBoot... "the default ones" are clearly not acceptable anymore! Honestly, if those parameters could be relevant then the setting j132 should not be working...

this release is much more unstable

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

BigEmperor26 commented 2 years ago

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

Keep the hard work. Love what you are doing.

I didn't update MLB SystemSerialNumber SystemUUID, i kept the old ones with new SMBIOS so I didn't have to resign on iServices.

I don't have fully SecureBoot enabled, so I'm unable to confirm wether these values are checked during AppleSecureBoot

myselfghost commented 2 years ago

It's quite weird that

Changing Misc -> Security -> SecureBootModel from Default to Disabled in config.plist (similar to that of EFI V2.4.0) seems to do the trick

Did someone have tried to reset NVRAM at first reboot? Honestly, I don't know if it could do the trick since with these settings I never had any issue for

Monterey Beta 5 + update OTA to Monterey Beta 6

a clean install of Big Sur 11.6 (which is now my running system)

Moreover, in "official" OpenCore Configuration.pdf, the setting Default points to x86legacy which is the minimum required for running Big Sur (and then Monterey)... the fact that setting j132 is working and Default not seems to point out that macOS didn't recognize your system as Big Sur but as older... For this reason, I suggested to try to reset your NVRAM. If, instead, you are running macOS Catalina, then it is obvious that the setting Default is wrong, but all my EFI are meant for Big Sur+ (then I'll add the changes needed for Catalina...)

Did everyone update MLB, SystemSerialNumber and SystemUUID values? Honestly I don't remember whether these values are checked (or not) during AppleSecureBoot... "the default ones" are clearly not acceptable anymore! Honestly, if those parameters could be relevant then the setting j132 should not be working...

this release is much more unstable

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

I update MLB, SystemSerialNumber and SystemUUID values and restart. There is no option for reset NVRAM in opencore with 3.0.0. the computer will crash when go to the login interface

I updated the EFI in the bootable USB flash drive to version 3.0.0 and booted from the USB flash drive, the installation process would also crash.

myselfghost commented 2 years ago

have reset NVRAM ,also crash.

linshixiong commented 2 years ago

Still crash after resetting nvram

profzei commented 2 years ago

the computer will crash when go to the login interface

For Login interface do you mean the screen where you insert your password after all the boot process with loading bar under apple sign? ...or are you improperly referring to OpenCanopy boot picker where you choose to boot or not OpenCore?

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash? Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100? Could you report them, please?

myselfghost commented 2 years ago

the computer will crash when go to the login interface

For Login interface do you mean the screen where you insert your password after all the boot process with loading bar under apple sign? ...or are you improperly referring to OpenCanopy boot picker where you choose to boot or not OpenCore?

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash? Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100? Could you report them, please?

the screen where you insert your password.

debug log : 1: https://imgtu.com/i/4BbKfJ

2: https://imgtu.com/i/4BbRhQ

profzei commented 2 years ago

@myselfghost Thank you for your report!

the screen where you insert your password.

To my knowledge, it should not be related to enabling SecureBootModel key to Default value

In fact your two images taken from debug log point out to a fatal error (Kernel Panic) due to your nvme... It is a well known issue in hackintosh world. References are:

in my homepage: search for Notes: NVMe SSD support
official thread
Official fix is reported in my Notes: NVMe SSD support or in WhateverGreen Official Known Issues

Try if the official fix is working for you otherwise, please, report your issue in official thread asking if there could be a correlation between SecureBootModel flag and such an issue to acidanthera team . Let me know whether it works! Btw, what are your nvme specifics? ...and did you make an internal install?

Edit #1: Maybe there could be a relation between Apple snapshots (made on filesystem i.e. on your nvme) and your trim specifics: try also to disable trim as suggested in the same thread...

Edit #2: Could anyone who had trouble enabling SecureBootModel key as Default share its NVMe specifics (manufacturer + model), please?

samwzlim commented 2 years ago

I'm sorry... I tested/tuned it for about two months without any relevant issue, otherwise I didn't share it here...

No, don't apologize! I really appreciate your hard work even though this issue just a side project. Without your repo I would hardly manage to hackintosh my machine.

@profzei Regarding the NVMe specifics, my SSD is the WD Black SN750. I changed the stock SSD to this as my previous one was dead and this particular model was highly recommended by the hackintosh community. FYI, I am currently on macOS Monterey Beta 6.

In fact, I am now greeted with a new error while booting with SecureBootModel set to Default: According to Apple's Support page, this happens when the macOS version/build is not something the machine can use? The solution provided was to use Disk Utility in Recovery to repair the startup disk and if that didn't work, reinstall macOS, but I didn't go through the hassle of doing either.

Setting SecureBootModel to Disabled bypasses this for me. However, similarly to the others, my machine freezes, although it happens after I'm logged in.

If you need any further report/help let me know!

profzei commented 2 years ago

If you need any further report/help let me know!

In my opinion, it should be useful if all people, who had issues with Release v. 3.0.0, could share their report about the following:

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash? Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?

samwzlim commented 2 years ago

If you need any further report/help let me know!

In my opinion, it should be useful if all people, who had issues with Release v. 3.0.0, could share their report about the following:

Have you tried to add to your boot-args -v keepsyms=1 debug=0x100 and see where it is the crash?

Have you tried to replace RELEASE OpenCore files with their DEGUB version and see where it is the crash using -v keepsyms=1 debug=0x100?

Upon booting, it's stuck here for a while:

Then after that, it shows this screen which I mentioned earlier:

Kokkolabs commented 2 years ago

Just updating to 3.0.0 and all go well, zero issues. Boot is really faster, thank you :)

samwzlim commented 2 years ago

Just updating to 3.0.0 and all go well, zero issues. Boot is really faster, thank you :)

What macOS version are you on? Did you directly upgrade from previous EFI without making any changes? If not, what changes did you make?

Kokkolabs commented 2 years ago

Monterey beta 5 and i change only serialnumber. Edit1: i have beta 5 Edit2: updated today latest beta, all ok. Edit3: Still beta 5. I start update and go out, it wont update some reason.

profzei commented 2 years ago

Boot is really faster, thank you :)

@Kokkolabs Thank you!

@samwzlim

Your first image is "readable": system is loading/injecting Bluetooth driver... it "hangs" since, as you know, support for Monterey Beta6+ is "not optimal"...
Your second image is "not readable": it seems there could be something related to WiFi but I'm not sure... Please, try a second shot...

Monterey beta 5

"All the patches" I wrote were tested on Monterey Beta 4 - 5 - 6 without any particular issues... now I replaced Monterey with Big Sur 11.6 and, by my side, all is working fine!

samwzlim commented 2 years ago

@profzei I totally forgot to disable IntelBluetoothInjector.kext in config.plist as I'm still on Monterey! I gave it another shot but the machine still does not boot with SecureBootModel set to default. It now shows a different error log:

Regarding the 2nd image, there is nothing I can do about the clarity of the image, as it is blurry irl as well. However, it seems to me that logs on the 2nd image are the same as that of the 1st image.

profzei commented 2 years ago

@samwzlim

I gave it another shot but the machine still does not boot with SecureBootModel set to default. It now shows a different error log:

Honestly, I do not see any relevant issue reported in your system boot log: as you could see also my system boot log (Big Sur 11.6) reports some "fails" for nvme but they are not relevant since boot phase is fine...

2021-09-26 16:38:13.524930+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: ( fClients->getCount ( ) == 0 )
2021-09-26 16:38:13.524934+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> ErrorExit
2021-09-26 16:38:13.524938+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeBlockStorageDevice.cpp
2021-09-26 16:38:13.524943+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 2406
2021-09-26 16:38:13.524944+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> 
2021-09-26 16:38:13.526059+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: result
2021-09-26 16:38:13.526061+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> ErrorExit
2021-09-26 16:38:13.526064+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/AppleNVMeSMARTUserClient.cpp
2021-09-26 16:38:13.526067+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 79
2021-09-26 16:38:13.526068+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> 
2021-09-26 16:38:13.527210+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> AppleNVMe Assert failed: result
2021-09-26 16:38:13.527213+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> DetachUserClient
2021-09-26 16:38:13.527218+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> file: /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeBlockStorageDevice.cpp
2021-09-26 16:38:13.527223+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert> line: 2352
2021-09-26 16:38:13.527224+0200  localhost kernel[0]: (IONVMeFamily) <IONVMeFamily`IONVMeDebugAssert>

Regarding the 2nd image, there is nothing I can do about the clarity of the image, as it is blurry irl as well. However, it seems to me that logs on the 2nd image are the same as that of the 1st image.

I agree with you! ...but this also means I do not have any clues for your issue...

samwzlim commented 2 years ago

@profzei Would it be possible for you to share the exact EFI you used when you were still on Monterey beta 6? Hopefully I might be able to find some differences between mine and yours and fix the issue.

profzei commented 2 years ago

my SSD is the WD Black SN750

Maybe it could be useful monitor also this issue

Would it be possible for you to share the exact EFI you used when you were still on Monterey beta 6?

I need to check its presence in my backup (i.e all the EFI): it should be the same config.plist I included into my release 3.0.0 (there is no reason for including any changes to it since the same file is working fine , for me, both for Monterey beta 6 and Big Sur 11.6 which I installed later...), but I surely checked it asap

sev7en2507 commented 2 years ago

Good morning, thanks for the thread, I tried multiple times the procedure (very well done... thanks!) but I am stuck on that:

I am using OpenCore 0.7.3 and I don't how to go ahead...

Thanks for your support.

profzei commented 2 years ago

@sev7en2507

I guess you installed successfully macOS since there is no macOS Installer icon in your OpenCanopy boot picker...
I really don't know why two windows partition are visible (Windows + EFI? or Windows + Data?)... but nevermind
Enter your Windows partition and add OpenCore entry to UEFI boot following this guide

stevezhengshiqi commented 2 years ago

SecureBootModel should be kept as Disabled for general use. Default does not apply to all users, and it will cause KPs on certain machines. Unless user test by themselves that Default is safe, I agree that Disabled should be used for general public. Disabled is safe for all macOS versions.

profzei commented 2 years ago

@stevezhengshiqi Thank you very much for your advice since I consider very valuable your opinion! I'll update failsafe condition setting SecureBootModel key as Disabled in my next update...

I'd like your opinion, if possible, about our situation i.e. all Huawei Matebook X Pro 2018 users:

the settings I shared in my last release are those recommended in OpenCore Configuration.pdf for enabling Apple SecureBootModel
if those settings are working fine for my Matebook X Pro, why other users (using the same identical machine) could report issues?
In your experience, which could be the possible KP causes that may arise from identical machines?

Edit:

When I say identical machines I mean that all our Matebook X Pro 2018 are the same except NVMe SSD... Is NVMe SSD a possible KP source just enabling Apple SecureBootModel in your opinion? If yes, there are bug reports I may consult? The last factor of diversity (among our Matebook X Pro) could be BIOS version... Could it be a possible source for a KP just enabling Apple SecureBootModel?

All other hardware is soldered...

There is no mention in OpenCore Configuration.pdf about these two possible sources of KP related to Apple SecureBootModel... just to be honest, there is no mention in such document about possible issues enabling Apple SecureBootModel...

sev7enITA commented 2 years ago

@sev7en2507

I guess you installed successfully macOS since there is no macOS Installer icon in your OpenCanopy boot picker...

I really don't know why two windows partition are visible (Windows + EFI? or Windows + Data?)... but nevermind

Enter your Windows partition and add OpenCore entry to UEFI boot following this guide

Dear profzei, As first... My thanks for your help and quick reply 🥰

I have not installed MacOSX: that screenshot is the first boot when rebooted the Matebook with the USB pendrive for the installation. Basically I don't know the reason but the recovery partition in the USB isn't discovered.
You are in the right, there is a partition of OS and partition for data on my SSD
Thank you, it will be done as soon... Installed.

I did the procedure different times, following your guide. It is very strange.

profzei commented 2 years ago

I have not installed MacOSX: that screenshot is the first boot when rebooted the Matebook with the USB pendrive for the installation. Basically I don't know the reason but the recovery partition in the USB isn't discovered.

Just to understand and to be sure... have you followed Dortania's Guide? I guess you followed instruction for Windows since you refer to recovery partition... honestly I never used a such approach... Have you tried, for example, balenaEtcher? maybe downloading full Big Sur 11.6 from All Mac World...?

I suggest you opening a new issue only to keep this one as clean as possible!

sev7en2507 commented 2 years ago

You are unique ❤️ Thank you so much.

I will follow your instructions and if I haven't sorted it out, a dedicated thread will be created.

Have a lovable day

On Thu, 30 Sep 2021, 04:10 profzei, @.***> wrote:

I have not installed MacOSX: that screenshot is the first boot when rebooted the Matebook with the USB pendrive for the installation. Basically I don't know the reason but the recovery partition in the USB isn't discovered.

Just to understand and to be sure... have you followed Dortania's Guide https://dortania.github.io/OpenCore-Install-Guide/installer-guide/mac-install.html#setting-up-opencore-s-efi-environment ? I guess you followed instruction for Windows since you refer to recovery partition... honestly I never used a such approach... Have you tried, for example, balenaEtcher https://www.balena.io/etcher/? maybe downloading full Big Sur 11.6 from All Mac World...?

I suggest you opening a new issue only to keep this one as clean as possible!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/profzei/Matebook-X-Pro-2018/issues/186#issuecomment-930421930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOM4HTWC2NETM4LCSZZMX3LUENJAHANCNFSM5ESWDI6Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

elliotnash commented 2 years ago

I'm not sure if this is the same issue, but my matebook is also failing to boot on 3.0.0 with Mac OS 11.6. Booting from an usb installer works fine, but the installer doesn't recognize my internal SSD, and booting to my internal SSD hangs on this screen PXL_20210929_214549944 I'm running the i5 matebook, but my main difference is I've replaced the SSD with a 1tb Sabrent Rocket Q, which has worked on every past efi version, but doesnt seem to be detected on this. Im wondering what nvme related kexts / patches were updated so I could try reverting them, as I assume that's where at least my issue lies. Thank you so much for all your hard work by the way :)

profzei commented 2 years ago

@elliotnash

I assume you read this thread and you have already set Misc -> Security -> SecureBootModel key as Disabled.

All NVMe related kexts/patches/settings are the following:

SSDT-NVME.aml
NVMeFix.kext
HibernationFixup.kext
PciRoot(0x0)/Pci(0x1c,0x4) device properties

My suggestion is (at the same time)

disabling SSDT-NVME.aml binary patch AND
disabling loading NVMeFix.kext AND
disabling loading HibernationFixup.kext AND
commenting/deleting pci-aspm-default key and its value AgAAAA== from PciRoot(0x0)/Pci(0x1c,0x4) device properties

If USB key is now starting properly then you could try restoring only one item at a time following this order:

SSDT-NVME.aml
NVMeFix.kext
HibernationFixup.kext
PciRoot(0x0)/Pci(0x1c,0x4) device properties

If you find out that one or two items determine your issue, try however loading remaining items in order to isolate as much as possible the cause. Please, share your findings!

elliotnash commented 2 years ago

It seems even with those disabled, my boot still fails at a very similar spot (same place as last time, except now it fails one line sooner and doesn't show the apfs_module_start line). I do have SecureBootModel set to disabled, and I've filled in my Generic section with serials from my last efi

Edit: it sometimes still shows the apfs_module_start line

profzei commented 2 years ago

@elliotnash Try to set in config.plist:

<key>ProtectSecureBoot</key>
<false/>

<key>DisableWatchDog</key>
<true/>

elliotnash commented 2 years ago

It's still stuck at the same place after that

Kokkolabs commented 2 years ago

My hack working fine with beta 5. But i cant update newer beta some reason. It start install and reboot, then bootloop. I test couple times and some settings on config.plist with no luck. Then i deleting update app in applications folder to starting update again but now it wont show update anymore. It show i on latest software, i have(21A5304g).

profzei commented 2 years ago

But i cant update newer beta some reason.

@Kokkolabs OpenCore v. 0.7.4 is needed! See Acidanthera October Release Update

Kokkolabs commented 2 years ago

But i cant update newer beta some reason.

@Kokkolabs OpenCore v. 0.7.4 is needed! See Acidanthera October Release Update

I just notising that other forum, but thanks i try again.

Edit: Updated latest beta after OpenCore update.

samwzlim commented 2 years ago

But i cant update newer beta some reason.

@Kokkolabs OpenCore v. 0.7.4 is needed! See Acidanthera October Release Update

I just notising that other forum, but thanks i try again.

Edit: Updated latest beta after OpenCore update.

Glad to hear that you were able to update to the latest beta of Monterey. I am currently on Beta 6 and am unable to update as well, as my OpenCore version is not v0.7.4.

Did you have to make any modifications to the contents of the OC folder for our MBXP, or simply moving it into the EFI will do? Please advise as I am looking to update as well.

rohirrim27 commented 2 years ago

Thank you profzei for all the hard work!

@myselfghost & @linshixiong were you able to resolve your problems in upgrading to 3.0.0? If yes, could you lay them out please for those of us considering upgrading?

Thanks!

profzei commented 2 years ago

I close this issue since I just released v. 3.1.0

PLTorrent commented 2 years ago

I'm not sure if this is the same issue, but my matebook is also failing to boot on 3.0.0 with Mac OS 11.6. Booting from an usb installer works fine, but the installer doesn't recognize my internal SSD, and booting to my internal SSD hangs on this screen I'm running the i5 matebook, but my main difference is I've replaced the SSD with a 1tb Sabrent Rocket Q, which has worked on every past efi version, but doesnt seem to be detected on this. Im wondering what nvme related kexts / patches were updated so I could try reverting them, as I assume that's where at least my issue lies. Thank you so much for all your hard work by the way :)

I have MBXP i5 version with the original 256GB LiteON NVMe and I have exactly the same issue. Used it previously with 2.4.0 and Big Sur and worked flawlessly, then cleaned it to test drive Windows 11 and now I cleaned the drive and wated to go back to macOS but it was hell. First of all no matter what I did I was not able to force the installer to see my internal drive on either 2.4.0 or 3.1.0. FInally I have found in wiki the https://github.com/profzei/Matebook-X-Pro-2018/blob/master/Wiki/BigSur_OC_EFI_INSTALL.zip and with this one the installer finally recognized my drive and I was able to install Big Sur 11.6.

Now there is no way I can use neither 3.0.0 nor 3.1.0 regardless of the Secure Boot setting. I am able to boot from 2.4.0. On both 3.0.0 and 3.1.0 I get the denial circle and booting stops.

Therefore I think @profzei that maybe it is worth mentioning somewhere in visible place that for install the BigSur_OC_EFI_INSTALL.zip should be used?

Also is it possible that 3.0.0 and 3.1.0 are not compatible with Big Sur, just with Monterey?

Didn't want to open new thread with the same issue...

profzei commented 2 years ago

@PLTorrent I'm writing a guide for install... see my comment @ #193

EFI releases are only for updating system and not for a clean install: during install many fixes present in config.plist could not be applied... this could be considered the price for a very fine tuned configuration... ahahah!

PLTorrent commented 2 years ago

@profzei hahaha now it is clear for me as well. ;] Good that I have finally found the BigSur_OC_EFI_INSTALL.zip ;]

However another issue is that still it is not possible to use BigSur 11.6 with 3.0.0 and 3.1.0. I have tried disabling

disabling SSDT-NVME.aml binary patch AND
disabling loading NVMeFix.kext AND
disabling loading HibernationFixup.kext AND
commenting/deleting pci-aspm-default key and its value AgAAAA== from PciRoot(0x0)/Pci(0x1c,0x4) device properties

But I still get the prohibitory circle. Any other suggestions what I could try to disable in order to pinpoint the exact cause for the issue?

profzei commented 2 years ago

@PLTorrent I'm using Big Sur 11.6 with 3.1.0 without any issues (same thing with EFI 3.0.0): this means that I'm not able to reproduce your/other issues...

Any other suggestions what I could try to disable in order to pinpoint the exact cause for the issue?

Probably the only thing is waiting for updated installation guide and use the updated minimal config.plist as a starting point to which add all the patches which are present in complete config.plist... I don't know if I was clear...

PLTorrent commented 2 years ago

@profzei

You are completely clear. Would you happen to have a minimal config.plist for 3.1.0 and could you share it e.g. in the wiki? I could try to investigate in the meantime and try to nail down the issue as it seems that quite a few people are affected.

profzei commented 2 years ago

@PLTorrent I renewed/added some instruction on Readme file on homepage and I updated/wrote guide in Wiki section for installing macOS using EFI releases' content

Please, check if now you are able to fix your installation issue.

Please, be sure that Misc -> Security -> SecureBootModel key is set as Disabled I didn't need it but you could also try to set Misc -> Security -> DmgLoading as Any

profzei / Matebook-X-Pro-2018

3.0.0 have some problem #186