Search results

Sound is working. Webcam I don't care. HDMI reboots no matter what configuration I make, maybe I need to patch Whatevergreen.kext... I didn't understand framebuffer patching very well.

Hello again guys... unfortunately HDMI is still not working (rebooting after plugging in my UX333FN). I tried the frame buffer patching method suggested by Hackintool after changing the DP connector to HDMI but nothing changed (framebuffer-con1-type & framebuffer-con2-type). Maybe I missed...

Thanks, now almost everything is working on my UX333FN. - HDMI still doesn't work, always reboot when I plug my monitor. I tried to do the framebuffer whatevergreen patch but I found the guides very difficult and I failed. - The wi-fi kext you linked causes reboot too :(

Let me know the procedure you did and how you installed a generic audio driver in Windows please, I couldn't do it

My audio is now working with Layout 12 (?). I have the same problem @nnst broken audio if I restart from Windows. Tried uninstalling Realtek drivers and installing Microsoft stock drivers with no success...

My audio is still not working, put CodecCommander.kext in L/E and SSDT-ALC294.aml in the Patched folder, then rebuilded cache. Not sure what is the problem with my PC. What version of Catalina are you guys running?

I tried so many patches for the audio and no one worked. At this point I think we need a custom patch...

Audio is not working either, I tried Voodoo HDA that always worked in my experience but I got no sound... just the microphone input showing signal

I have a UX333FN (Nvidia MX150) and it's working. No keyboard backlight and no sound too, but I saw we have ALC 294 via codec dump.

Me too. I got "Invalid property list" error. Not working

The WiFi/Bluetooth module is soldered, we can't upgrade it. P.s. I bought the edimax wifi adapter because it was listed as one of the few compatible with Sierra and it works so bad that I throw away after 10 minutes (I get about an unstable 1mbps that goes to 20kbps at about 10 cm from the...

The internal Intel card is known to have problems loading the bluetooth firmware. When I did the guide I was thinking that it would have been working ok forever but I was wrong. After a few reboots it stopped working completely resetting the ID exactly like in your case. Sometimes when I boot...

So have you tried injecting VoodooI2C with DSDT and the terminal without putting it in S/L/E? cd ~/Desktop sudo chown -R root:wheel VoodooI2C.kext sudo kextload VoodooI2C.kext

If every time you have to open a VM it's not convenient. About the NVME drive: don't know if someone got it working or not. Have you found anything about that? I see informations only about the 13.

About VoodooI2C: I remember before installing it in S/L/E I put the kext on the desktop and ran the command at the end of the guide. Don't know if it's important or not.

I've got another problem today.. Bluetooth stopped working randomly. It worked well in the last days but after a few reboots system report shows ID: 00 00 00 00 00 under Bluetooth. Have you got that problem too?

It's clear you're right. I was trying to figure out some differences between my original DSDT and their one, because with mine the trackpad didn't work. Apparently there's no difference in the I2C code and they did not apply any of the patches on the VoodooI2C Maciasl's repo so I'm a bit lost.

Xiaomi only produced the Xiaomi Mi Notebook in series. There's only one 12.5 model and BIOS never got an update. Infact the DSDT I linked in the guide is not mine but it's working for my laptop.

It's strange. For me it's working perfectly and I've only followed the steps I said in post #11. Maybe you'll have to redo the installation from the beginning.

Are you sure you have the DSDT linked in the guide in EFI/Clover/ACPI/patched ? Have you deleted AppleIntelLpssI2C.kext and AppleIntelLpssI2CController.kext in System/Library/Extensions as required? If you have no success you can download my EFI HDD FIXED atteched above and intall the VoodooI2C...