hieplpvip / Asus-Zenbook-Hackintosh

Run macOS on Asus Zenbook with OpenCore
199 stars 44 forks source link

Blank screen BIOS #95

Open akaditya13 opened 3 years ago

akaditya13 commented 3 years ago

What is your laptop? UX430UNR

Which version of macOS are you using? MacOS 11.0.1

Describe the problems After installed big sur, it seems that I cannot enter BIOS. I've tried to reset NVRAM using the picker on Open Core but the problem persisted. Does anyone have similar problem?

finax1 commented 3 years ago

Same Laptop (UX430UNR)... I've had the same issue (in clover-times) multiple times, but I have absolutely no clue what it could be. When wiping or tiding out the EFI-Partition then I was able to enter the UEFI-Setup.

I think it has something to do with the registrated boot options from the bios, when those .efi files are not there any more.

Ubsefor commented 3 years ago

This seems to be a common issue, I suggest reflashing BIOS from windows using Asus winflash utility, this will certainly fix that. Also, you can utilize Asus’s BIOS FlashBack (? – I don’t quite remember how its called) to reflash BIOS. Also, don’t forget to include tsc (CPUTSCSync kext for example, can be found in this repo as download dependency) fixes if you are going to flash versions greater than 307 or 307 itself.

alexVinarskis commented 3 years ago

Had similar issue. Have no idea where it is coming from and what is the 'correct' solution. After hours of struggling, found a walk around:

Summary: wipe your EFI folder/ pull out SSD, enjoy. Now update BIOS (yes, even latest works!) though EZ flash (from BIOS itself) and reinstall EFI

Full version: Experimentally found out that when there is no bootloader on the system, it would enter BIOS with no issues. When there is Windows/OC/Clover, sometimes it would just 'break'. As far as i understood, issue is somewhere in NVRAM configs (resetting if from OC didn't help me though). Wiping EFI - rebuilding in a specific order to exact state as before would fix issue for me.

I am suspecting this laptop has physical memory issue, perhaps dying ROM, or TPM, as this BIOS problem would appear randomly in my case. Moreover, sometimes when trying to update BIOS boot option from inside of BIOS my PC would just hang, and only hard reset would fix it (anyone else having this crap?).

Once I fixed BIOS, i had new issue: OC/Clover wont boot as long as there is Windows bootloader in the system (even from USB..). Quite sure it is same BIOS issue, as all i did to fix it was to wipe EFI, in a specific order rebuild it to exaclty what it was when it broken, and it would magically work again.

If this helps, I also had Bitlocker issue, so after decrypting drive I didnt just turn off secure boot, but also pressed 'reset key to defaults' to wipe all TPM data.

I've got two almost the same laptops, both are currently successfully running Windows+BigSur on latest BIOSes (311 and 307 for UX430UNR and UX430UA). Both at some point of their lifetime would fail to open BIOS at least once.

P.S. Just saw comment about, CPUTSCSync.kext, don't have it my system, all seems to work fine. P.S.S. easiest way of wiping/moving/rebuilding EFI partition is to get a 8+gb USB, install Ubuntu installer and boot up from it. (Try out mode). Works like a charm, quite fast, and Linux is amazing for these things.

Ubsefor commented 3 years ago

Had similar issue. Have no idea where it is coming from and what is the 'correct' solution. After hours of struggling, found a walk around…

CPUTSCSync or alternatives like Voodoo TSC (dozens of them!) are required for sleep to work properly, it fixes kernel panics for tsc timers not initialized properly by hardware after sleep.

I do believe that your issue is hardware-based, though I suggest you to try and reflash bios to the latest version (for UX430UAR it is, apparently, under number 308 for some reason).

There are also tools in OpenCore such as «Reset System», which actually wipes all the nvram and other cleanable boot params. Also, there is a different nvram cleaner, which doesn’t preserve OpenCore’s nvram values as «Reset NVRAM» does, suggest looking into that.

You can also boot directly into UEFI shell using bios – find an UDK II UEFI Shell and place the .efi file in the root of your EFI partition, rename the file as shellx64.efi and after that you can boot directly into it using the bios option to load EFI Shell (if there is a such thing in your bios). It quite helps with debugging boot options in general and other boot-related problems. And btw, setting boot options using shell is by far the most comfortable way due to asus making shitty and crashing boot options manager 😊