Contribute
Register

[Solved] Big Sur upgrade stuck on MacOS installer(OC-Kaby Lake)

Status
Not open for further replies.
Joined
Oct 7, 2017
Messages
30
Motherboard
Asus R541UJ
CPU
i5-7200U
Graphics
HD620
Mobile Phone
  1. Android
  2. iOS
After successfully running Catalina on my Vivobook (core i5-7200u) with opencore, I tried direct upgrade to Big Sur. Anyway, after a few time I start the installation, the system reboots and I get the MacOS Installer entry. System automatically boots into the MacOS Installer while it got stuck by Kernel Panic.
Following this guide:
https://www.tonymacx86.com/threads/update-directly-to-macos-big-sur.304629/

panic.jpeg
 

Attachments

  • EFI_KABY.zip
    3.7 MB · Views: 534
Last edited:
Try this: You delete all of the voodoo stuff and again download voodoops2, voodooi2c and voodooi2chid to /EFI/OC/Kexts and make a OC snapshot of your EFI using ProperTree(plist editor) and make sure to keep a backup of your current efi folder before doing so.Go to opencore.slowgeek.com to recheck your config. That's how I got mine working. I have a vivobook hack laptop and I got the same error

P.S: Remove SMCbatterymanager and install and then use it after install or use ACPIBatteryManager.kext if you want battery stats during install
 
I removed voodooI2c, voodoI2cHID, smcBattermanager, smcSuperIO, smcProcessor kexts and rechecked the config.plist. still stuck at the same place..
previously I was getting this error message AppleActuatorDeviceUserClient::stop entered. Now I am getting no error message and the installer simply keeps restating.
 
Finally I got BigSur installed successfully. I am not quite sure what fixed it, but created a whole new EFI folder from OC 0.6.3 release and updated them with latest kexts, then I downloaded the install app once again and the installation went on flawlessly.
BTW, @Binuk which model of vivobook you do have?
1. could you get the Fn keys for brightness working
2. What about the card reader?
3. For me battery status is working with SMCBatteryManager and I didn't patch DSDT. Is patching DSDT is required/some special SSDT for proper power management?
 
@kingaslan I have a asus vivobook F542UA-DH71. I actually did not try to fix brightness and card readers and stuff cuz this hack is like my "try-out" sort of machine to test new OSes, like macOS Big Sur so it is not my main workbench hack. And I use ACPIBatteryManager.kext for battery and it requires no DSDT/SSDT patching.
 
Finally I got BigSur installed successfully. I am not quite sure what fixed it, but created a whole new EFI folder from OC 0.6.3 release and updated them with latest kexts, then I downloaded the install app once again and the installation went on flawlessly.
BTW, @Binuk which model of vivobook you do have?
1. could you get the Fn keys for brightness working
2. What about the card reader?
3. For me battery status is working with SMCBatteryManager and I didn't patch DSDT. Is patching DSDT is required/some special SSDT for proper power management?
Wow, it looks like we have identical laptop specs, but do you know how to fix the touchpad? I can boot to latest catalina using oc and touchpad (i2c) is work, but it doesn't work when I boot to big sur :(
 
Wow, it looks like we have identical laptop specs, but do you know how to fix the touchpad? I can boot to latest catalina using oc and touchpad (i2c) is work, but it doesn't work when I boot to big sur :(
What exact touchpad do you have? What are the kexts you are using?
 
What exact touchpad do you have? What are the kexts you are using?
It is FTE 1200, I already try dortania guide (SSDT-GPI0/XOSI), add the latest VoodooI2C and VoodooI2CHID kext, add "Prevent Apple I2C kexts from attaching to I2C controllers" to OC kernel patch, try using another laptop i2c SSDT but still no luck. Currently I'm using this EFI https://github.com/tunglamvghy/AsusS530UN-hackintosh which is work (i2c) on latest catalina like I mentioned before, but doesn't work on big sur.
 
I removed voodooI2c, voodoI2cHID, smcBattermanager, smcSuperIO, smcProcessor kexts and rechecked the config.plist. still stuck at the same place..
previously I was getting this error message AppleActuatorDeviceUserClient::stop entered. Now I am getting no error message and the installer simply keeps restating.
Hi, I have exactly the same issue, I can’t past from there. How did you repair it ? Thx.
 
Status
Not open for further replies.
Back
Top