Asus-Zenbook-Hackintosh
Asus-Zenbook-Hackintosh copied to clipboard
hieplpvip
BIOS no more accessible
What is your laptop? 2 models UX430UA and UAR, BIOS 305
Which version of macOS are you using? 10.14.6 with last sécurity update.
Describe the problems The 2 laptops work great, however I cannot anymore access BIOS. It is as OS X flash « something » on them. When I want to enter BIOS, I’ve got only a black screen. I tried also ALT F2 to enter directly EZ Flash, same issue. I tried to use Asus Winflash, this one say that this BIOS is not supported. I have a look with AMI flash tool however this one didn’t rencognize any memory chip (previously it found some windbond something).
Did anyone else enconter the same thing (as it appears on my 2 laptops).
Sorry, it is not a bug but as we have all here the same laptop, I request here.
Attach output from gen_debug
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
Hi.
I remove this morning battery, press power button for 30 seconds to check if it clears something, same issue at the end, no access to the bios is possible.
I'm quite convince that OSX updates flash something. No idea when, but as my 2 laptops have got the same behaviors, I think we can say it is a fact...
Hi. I have ASUS UX430UAR laptop too. For me macOS (10.14.6 and 10.15.3) works fine only with BIOS 304. When AsusUpdate updates BIOS to version 305 and above, macOS doesn’t work well. I uninstalled AsusUpdate on Windows and installed BIOS 304 using WinFlash. I never have had problem with entering to BIOS. There is one idea – desolder flash memory chip, reprogram it and solder back.
Hi.
Thanks for your response. I will not try the "desolder" solution, It's not for me :P. I'm surprised that I'm the only one with this issue. Perhaps because I case in release 305 on both laptops.
I thought about using FPT from Intel to flash BIOS but I need to boot in DOS mode for that, and so to have CSM activated. And I cannot do that as I haven't access anymore to BIOS.
Perhaps I can use RU.efi to access BIOS parameters from EFI shell. I need to investigate that.
This problem occured also after upgrading to 10.15.4
UPD: Actually, just solved that via installing fresh copy of Windows 10 in dual boot mode and then using WinFlash utility from it. It successfully launched BIOS update after reboot, so now I’m sitting with freshest BIOS on Catalina again, able to access it whenever I want. Before trying this trivial solution I assumed that it won’t work, so searched for lots of information about that problem, including «creation of dos live-cd with AFUDOS utility» and some linux solutions on archwiki but gladly, the stupidest thing worked for me.
Hope you will find/have found solution to your case!
You are right !!!
My issue is that I'd got a too old Win10 on my USB drive (I use WintoUSB to create an external bootable USB drive).
So I bought the tool (that is not free anymore), create a new USB W10 drive and was able to use Asus WintoFlash. So I upgrade to 3.07 (was obliged to as WintoFlash want to have a newer bios version date) and just after downgrade to 3.05 with EZFlash in BIOS.
Fine !!!
I will kept this procedure as now, we are sure that OSX flash a part of our BIOS during some firmware upgrade.
Note that I had to remove all firmware update under Apple folder on EFI drive because without that, the firmware is flashed again by Apple process with the result of no more access to bios again.
So I'm afraid that we will have to check Apple folder after all OSX update to ensure to avoid this anymore.
You are right !!!
My issue is that I'd got a too old Win10 on my USB drive (I use WintoUSB to create an external bootable USB drive).
So I bought the tool (that is not free anymore), create a new USB W10 drive and was able to use Asus WintoFlash. So I upgrade to 3.07 (was obliged to as WintoFlash want to have a newer bios version date) and just after downgrade to 3.05 with EZFlash in BIOS.
Fine !!!
I will kept this procedure as now, we are sure that OSX flash a part of our BIOS during some firmware upgrade.
As far as I can tell, a working solution requires installation of Windows 10 1903 at least and flash any suitable bios version using WinFlash. Then you can just delete windows partition(s) if you don’t need it(them) and load to mac os normally. The only difference is that I flashed bios version 308 and it worked for me, I have now a bit increased battery life and performance, so advise you to update too.
Should mark this issue as solved.
I wait before upgrading to 308 because we need to add VoodooTSCSync with this version (in fact becoming version 307).
Some people said that they have instability after wakeup. Is it something you encounter ?
I wait before upgrading to 308 because we need to add VoodooTSCSync with this version (in fact becoming version 307).
Some people said that they have instability after wakeup. Is it something you encounter ?
It’s true that I occasionally met some CPU errors after hibernation – the solution is to turn off PowerNap (it doesn’t work anyway, from what I can tell). Everything else seems OK.
Sometime soon I will be migrating to OC bootloader as it seems to be more future-proof thing than clover.
My BIOS was flashed again by I don't know what... I checked my EFI partition and there is no specific firmware (one for MacbookPro 14,1 for example) under Apple folder outside of firmware.scap that came back (I'm sure I deleted it previously).... No idea what really flashed my BIOS.
As I have the procedure to revert, it's not an issue anymore. But I must say that I'm curious to know what flashed my bios in OSX...
What is your laptop? 2 models UX430UA and UAR, BIOS 305
Which version of macOS are you using? 10.14.6 with last sécurity update.
Describe the problems The 2 laptops work great, however I cannot anymore access BIOS. It is as OS X flash « something » on them. When I want to enter BIOS, I’ve got only a black screen. I tried also ALT F2 to enter directly EZ Flash, same issue. I tried to use Asus Winflash, this one say that this BIOS is not supported. I have a look with AMI flash tool however this one didn’t rencognize any memory chip (previously it found some windbond something).
Did anyone else enconter the same thing (as it appears on my 2 laptops).
Sorry, it is not a bug but as we have all here the same laptop, I request here.
Attach output from gen_debug
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
should to clear navrm and then to enter bios