[Guide][New VoodooI2C] Asus Vivobook S15 X510UAR 10.13+

[crash036]

Your ACPI/patched content is a complete mess.

Well, Thanks but how do I fix it?
I tried updating to 10.13.6 but the computer reboots shortly after the installer initialisation (I can get to installer but it reboots during the installation without updating)

Just tried the stock EFI folder by Saintno1997 (with the added sata kext you told me about before) and it gives me a kernel panic now (caused by VoodooI2C), removing the kext results in “Still Waiting For Root Device” or a boot with a 7 Mb Intel Graphics HD620 so No Qe/Ci (it did this in a few occasions but the “still waiting” freeze is more frequent)
What can I do?

 

[RehabMan]

Well, Thanks but how do I fix it?
I tried updating to 10.13.6 but the computer reboots shortly after the installer initialisation (I can get to installer but it reboots during the installation without updating)

Just tried the stock EFI folder by Saintno1997 (with the added sata kext you told me about before) and it gives me a kernel panic now (caused by VoodooI2C), removing the kext results in “Still Waiting For Root Device” or a boot with a 7 Mb Intel Graphics HD620 so No Qe/Ci (it did this in a few occasions but the “still waiting” freeze is more frequent)
What can I do?

ACPI patching guide:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

 

[crash036]

Okay so, I got it working
I reinstalled MacOs High Sierra 10.13.3 and used RehabMan's Config plist for Intel HD620
I used my SSDTDiscreteSpoof made with RehabMan's guide and re-activated "Rename oem _DSM to ZDSM" patch (that being disabled was causing the loop ioconsoleusers gioscreenlockstate 3 hs 0)

Finally Got Audio, Bluetooth, Qe/Ci, Brightness and FnHotkeys working

Now I really need to get the Trackpad working, I installed the VoodooI2C and VoodooI2CHID kexts and followed the guide to GPIO Pinning and installation of VoodooI2c but nothing..
I also need the battery working but that's a minor problem due to DSDT patches I've got to do (it keeps spamming me errors in the _BIX method)
Currently working on KeyboardBacklight..

EDIT: I Tried patching I2C with SaintNo's writeup at the start (without replacing all three methods) but still no trackpad, I've done GPIO Pinning again and applied Windows 10 patch and GPIO Patch, still nothing..

EDIT #2: Installed the new M2 SSD and did a fresh HFS+J Install
Patched everything and got everything working excerpt the damn TrackPad, currently working on it, nearly there!

 

[saintno1997]

NEW UPDATE: READY FOR 10.14
INFO:

• Update date: 24/07/2018
  • Delete all SSDT not necessary
  • Use config from @RehabMan
  • Renew all kext -> Ready for 10.14
  • Better thermal -> 37C on idle
• Update date: 25/07/2018
  • Update DSDT patch detail -> remove some un-need patchs
  • Support BIOS FW 303 -> Better stable

 

[bugsb]

NEW UPDATE: READY FOR 10.14
INFO:

• Update date: 24/07/2018
  • Delete all SSDT not necessary
  • Use config from @RehabMan
  • Renew all kext -> Ready for 10.14
  • Better thermal -> 37C on idle
• Update date: 25/07/2018
  • Update DSDT patch detail -> remove some un-need patchs
  • Support BIOS FW 303 -> Better stable

Thanks, saintno1997 - just updated to 303 and will try your pack asap. It's obviously necessary because right now High Sierra only boots via -x (safe mode), LOL.

One question in advance: I see you use BrcmFirmwareData.kext (in Clover/kexts/Other) and not BrcmFirmwareRepo.kext in /L/E + custom SSDT. Not sure if you've been following this thread at all lately, so.. are you aware that accdg. to RehabMan using BrcmFirmwareData.kext is just a temporary work-around with probable side effects? Have you tried at all to create the custom SSDT, following RehabMan's manual?

 

[saintno1997]

Thanks, saintno1997 - just updated to 303 and will try your pack asap. It's obviously necessary because right now High Sierra only boots via -x (safe mode), LOL.

One question in advance: I see you use BrcmFirmwareData.kext (in Clover/kexts/Other) and not BrcmFirmwareRepo.kext in /L/E + custom SSDT. Not sure if you've been following this thread at all lately, so.. are you aware that accdg. to RehabMan using BrcmFirmwareData.kext is just a temporary work-around with probable side effects? Have you tried at all to create the custom SSDT, following RehabMan's manual?

Oh sorry, i forgot to remove that kext from clover, i have update my wifi card to DW1560 so i have that kext!
My asus dont have any kext in S/L/E or L/E an still stable so i dont push to that yet!
I will try to gen an SSDT for all DSDT if I have time :3, sorry for bad english, my free time is coding so sorry if i cant support this thread frequently

 

[bugsb]

Oh sorry, i forgot to remove that kext from clover, i have update my wifi card to DW1560 so i have that kext!
My asus dont have any kext in S/L/E or L/E an still stable so i dont push to that yet!
I will try to gen an SSDT for all DSDT if I have time :3, sorry for bad english, my free time is coding so sorry if i cant support this thread frequently

No worries - and your English is totally fine, I understand everything you write, and am sure everybody else does.

You have not updated to 10.13.6 yet, have you (from this thread's and your github's page)? Because also from all the comments I have read, BrcmFirmwareData.kext stopped working for anybody with 10.13.6. So you would need to create your custom SSDT anyway, then install the repo kext to /L/E because it can't seem to be injected properly by Clover from kexts/Other.

Here's the link to RehabMan's guide for that; some people have created their custom ssdt with ammulder's guide (another moderator here), scrolling down to 7.2.1. Identifying Ports and follow from there.

Good luck !!!

BTW, if you have a chance, could you explain briefly reasons (pros, cons?) for your new additions:
ACPIPoller.kext
SSDT-FAN.aml
SSDT-PNLF.aml
SSDT-RMNE.aml
?

Great work saintno1997 - greetings to Viet Nam.

(I'm using your 303 BIOS EFI folder now minus any DSDT because my 301 BIOS DSDT stopped working after the 303 update and yours did not work for my model. Will create my own new 303 DSDT accdg. to your neat instructions asap).

 

[saintno1997]

No worries - and your English is totally fine, I understand everything you write, and am sure everybody else does.

You have not updated to 10.13.6 yet, have you (from this thread's and your github's page)? Because also from all the comments I have read, BrcmFirmwareData.kext stopped working for anybody with 10.13.6. So you would need to create your custom SSDT anyway, then install the repo kext to /L/E because it can't seem to be injected properly by Clover from kexts/Other.

Here's the link to RehabMan's guide for that; some people have created their custom ssdt with ammulder's guide (another moderator here), scrolling down to 7.2.1. Identifying Ports and follow from there.

Good luck !!!

BTW, if you have a chance, could you explain briefly reasons (pros, cons?) for your new additions:
ACPIPoller.kext
SSDT-FAN.aml
SSDT-PNLF.aml
SSDT-RMNE.aml
?

Great work saintno1997 - greetings to Viet Nam.

(I'm using your 303 BIOS EFI folder now minus any DSDT because my 301 BIOS DSDT stopped working after the 303 update and yours did not work for my model. Will create my own new 303 DSDT accdg. to your neat instructions asap).

I'm in 10.13.6 and you can see in picture that my bluetooth still work fine by using that kext!
SSDT-PNLF.aml is for brightness
SSDT-RMNE.aml for emulator ethernet port
ACPIPoller.kext and SSDT-FAN.aml for better FAN thermal by @black.dragon74

 

[bugsb]

I'm in 10.13.6 and you can see in picture that my bluetooth still work fine by using that kext!
SSDT-PNLF.aml is for brightness
SSDT-RMNE.aml for emulator ethernet port
ACPIPoller.kext and SSDT-FAN.aml for better FAN thermal by @black.dragon74
View attachment 343757

OK (nice screenshot), I do see your 10.13.6 + BT (so you could even change the topic title to 10.3.6 )

I had first ordered the DELL DW1560, but it arrived dead, not even working in Windows, and the supplier only wanted to issue me a refund, not send a new one. The only other supplier in my country only had the Lenovo FRU 04X6020, which worked fine until 10.3.5 with the same kexts you use + port limit removal patch (which I did not even see in your config.plist, so I guess you don't even have to use any such patch??).
For me, BT discovery already stopped after the 10.3.6 update, but now after the 303 BIOS update, High Sierra does not even find BT at all anymore, neither with my EFI folder + my patched DSDT, nor with your EFI folder + my patched DSDT. Bummer. I guess I'll have to order the DW1560, because it is obviously more compatible over time...

saintno1997, have you tried removing the BrcmNonPatchRAM2.kext? It should not be necessary for any BCM94352Z NGFF M.2 (Dell DW1560, Lenovo FRU 04X6020 etc.).

Thanks for explaining your add-ons.

 

[saintno1997]

OK (nice screenshot), I do see your 10.13.6 + BT (so you could even change the topic title to 10.3.6 )

I had first ordered the DELL DW1560, but it arrived dead, not even working in Windows, and the supplier only wanted to issue me a refund, not send a new one. The only other supplier in my country only had the Lenovo FRU 04X6020, which worked fine until 10.3.5 with the same kexts you use + port limit removal patch (which I did not even see in your config.plist, so I guess you don't even have to use any such patch??).
For me, BT discovery already stopped after the 10.3.6 update, but now after the 303 BIOS update, High Sierra does not even find BT at all anymore, neither with my EFI folder + my patched DSDT, nor with your EFI folder + my patched DSDT. Bummer. I guess I'll have to order the DW1560, because it is obviously more compatible over time...

saintno1997, have you tried removing the BrcmNonPatchRAM2.kext? It should not be necessary for any BCM94352Z NGFF M.2 (Dell DW1560, Lenovo FRU 04X6020 etc.).

Thanks for explaining your add-ons.

Yeah, i dont use any such patch )
Try to patch a new dsdt maybe solve your problem
Like you said, BrcmNonPatchRAM2 is not necessary! thanks for that <3