Vinicius P. Miranda Posted March 22, 2016 Share Posted March 22, 2016 Hi Guys. I downloaded and installed the update for OS X 10.11.4 on an test HD. The update was installed, but when restarted the computer after Clover screen, appeared the following error, and always back to Clover. Does anyone know how to solve this problem for me to get into in OS X normally? Thanks for help. My PC: Intel i7 3930k Stok. Asus Rampage IV Extreme - Bios 4901 Asus Radeon 7970 DirecCU II Top 16 GB Ram (4x4GB) Ripjaws 4866 MHZ. Fusion Drive SSD 120GB Corsair + HD 3TB. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/ Share on other sites More sharing options...
gengik84 Posted March 22, 2016 Share Posted March 22, 2016 Try OsxAptioFIx2Drv Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225635 Share on other sites More sharing options...
Slice Posted March 22, 2016 Share Posted March 22, 2016 Or just reboot again. It often works after reboot. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225643 Share on other sites More sharing options...
KWS Posted March 22, 2016 Share Posted March 22, 2016 Here 10.11.4 works only with OsxAptioFix2Drv-64.efi.zip 1 Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225654 Share on other sites More sharing options...
Vinicius P. Miranda Posted March 22, 2016 Author Share Posted March 22, 2016 Nice, work fine. Thanks guys. I uninstall OsxAptioFIx and installed OsxAptioFIx2. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225655 Share on other sites More sharing options...
Flyinace2000 Posted March 22, 2016 Share Posted March 22, 2016 Nice, work fine. Thanks guys. I uninstall OsxAptioFIx and installed OsxAptioFIx2. I was having the same problem. I mounted the drive in Win10, removed OsxAptioFix and replaced it with OsxAptioFix2, but now i just get **************************************************** Safe mode and Verbose give the same results. Mobo: Z87-UD5H 4770k Nvidia 780 Here is my Driver64UEFI Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225739 Share on other sites More sharing options...
Riley Freeman Posted March 22, 2016 Share Posted March 22, 2016 Or just reboot again. It often works after reboot. Not in this case. Happened to me a few betas back when Apple made this change in .4. It's somehow related to nvram as enabling unrestricted nvram in SIP (CsrActiveConfig=0x40) fixed it for me with AptioFix. AptioFix2 works with SIP fully enabled. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225756 Share on other sites More sharing options...
Flyinace2000 Posted March 22, 2016 Share Posted March 22, 2016 Not in this case. Happened to me a few betas back when Apple made this change in .4. It's somehow related to nvram as enabling unrestricted nvram in SIP (CsrActiveConfig=0x40) fixed it for me with AptioFix. AptioFix2 works with SIP fully enabled. Mine was set to 0x3, changed it to 0x40, but same results. Just a bunch of ****************************** BootArgs: darkwake=no npci=0x2000 kext-dev-mode=1 rootless=0 Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225763 Share on other sites More sharing options...
AppleIIGuy Posted March 22, 2016 Share Posted March 22, 2016 Flyinace2000 why do you have npci=0x2000 on a haswell system? Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225787 Share on other sites More sharing options...
Riley Freeman Posted March 22, 2016 Share Posted March 22, 2016 Mine was set to 0x3, changed it to 0x40, but same results. Just a bunch of ****************************** That's a different problem if you're not even getting the AptioFix error. But if you're already using 0x3 and need it (for unsigned kexts etc) delete AptioFix2, put back AptioFix and set CsrActiveConfig to 0x43. Also rootless=0 doesn't work anymore. It's taken care of via CsrActiveConfig. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225790 Share on other sites More sharing options...
tarasis Posted March 22, 2016 Share Posted March 22, 2016 Just had this exact error happen to me. Will try to linked driver, thanks KWS --- edit Deleting the OsxAptioFixDrv driver and replacing it with the version 2 worked. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225803 Share on other sites More sharing options...
Flyinace2000 Posted March 22, 2016 Share Posted March 22, 2016 Flyinace2000 why do you have npci=0x2000 on a haswell system? Honestly, not sure. It fixed something at some point. But based on the below posts it seems that i have some outdated flags. That's a different problem if you're not even getting the AptioFix error. But if you're already using 0x3 and need it (for unsigned kexts etc) delete AptioFix2, put back AptioFix and set CsrActiveConfig to 0x43. Also rootless=0 doesn't work anymore. It's taken care of via CsrActiveConfig. This worked. I set CsrActiveConfig to 0x40 and the AptioFix driver. Just need to fix audio now.... Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225866 Share on other sites More sharing options...
Slice Posted March 22, 2016 Share Posted March 22, 2016 I have CsrConfig 0x67 and AptioFix first version. In my configuration this works. If someone want a proof I can make any dump you like. Forget about npci=0x2000. It came from Dinosaur epoch and not needed with Clover and moreover in ElCapitan. Detailed analysis can be made by looking into IOPCIFamily source if any doubt. Stop after AptioFix is usually related to dirty RAM. Reboot is often a medicine to cure the issue. Stop after +++++ can be with bad DSDT patch, kext patch or kernel patch. Especially if the object changed. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225881 Share on other sites More sharing options...
cecekpawon Posted March 22, 2016 Share Posted March 22, 2016 AptioFix first version combined with CsrConfig 0x67 will work Slice. Ver 2 doesnt need CSR_ALLOW_UNRESTRICTED_NVRAM Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225889 Share on other sites More sharing options...
Slice Posted March 22, 2016 Share Posted March 22, 2016 AptioFix first version combined with CsrConfig 0x67 will work Slice. Ver 2 doesnt need CSR_ALLOW_UNRESTRICTED_NVRAM Good. Then explain me what is the reason for CSR_ALLOW_... restrictions? Someone afraid viruses? Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225901 Share on other sites More sharing options...
AsusFreak Posted March 22, 2016 Share Posted March 22, 2016 I have CsrConfig 0x67 and AptioFix first version. In my configuration this works. If someone want a proof I can make any dump you like. Forget about npci=0x2000. It came from Dinosaur epoch and not needed with Clover and moreover in ElCapitan. Detailed analysis can be made by looking into IOPCIFamily source if any doubt. Stop after AptioFix is usually related to dirty RAM. Reboot is often a medicine to cure the issue. Stop after +++++ can be with bad DSDT patch, kext patch or kernel patch. Especially if the object changed. X99 boxes won't boot without npci=0x2000. They hang on PCI configuration (using Nvidia 900 series cards) Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225908 Share on other sites More sharing options...
Flyinace2000 Posted March 22, 2016 Share Posted March 22, 2016 X99 boxes won't boot without npci=0x2000. They hang on PCI configuration (using Nvidia 900 series cards) Fair enough. I removed a bunch from my boot args, nothing broke. So now i just have the following. <string>darkwake=no kext-dev-mode=1</string> Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225909 Share on other sites More sharing options...
cecekpawon Posted March 22, 2016 Share Posted March 22, 2016 Calm down slice, it just report compatibility comparing 2 of your drivers with last osx releases. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225917 Share on other sites More sharing options...
Awesome Donkey Posted March 22, 2016 Share Posted March 22, 2016 Had this issue too, replaced with AptioFix2 and all is well again. Link to comment https://www.insanelymac.com/forum/topic/311499-fail-update-10113-to-10114/#findComment-2225927 Share on other sites More sharing options...
Recommended Posts