Jump to content

Jake Lo

Moderators
  • Posts

    14357
  • Joined

  • Last visited

  • Days Won

    867

Everything posted by Jake Lo

  1. Try disabling Inject Intel under Graphics of Config.plist If still fails, try enabling nvda_drv=1
  2. Replace Wern's DSDT with this one. Changed EHCI to EHC1 and HDef layout-id from 0->12
  3. Make sure to have SATA Operations set to AHCI in the BIOS
  4. Your don't have graphics injection in your Config.plist so I assume you have in your DSDT, but you don't have that either. Try this Config file. Boot to Clover, hit F4 to extract the raw file. Upload the folder here /EFI/Clover/ACPI/Origin. I'll try to patch them for you. config.plist.zip
  5. See if you could go to Network Preferences and add a Wifi.
  6. Here are the text/hex representation of MBA5,2 Mac-2E6FAB96566FE58C 4D 61 63 2D 32 45 36 46 41 42 39 36 35 36 36 46 45 35 38 43 MBP9,2 Mac-6F01561E16C75D06 4D 61 63 2D 36 46 30 31 35 36 31 45 31 36 43 37 35 44 30 36 To add on the fly patch to Clover, add this to KextToPatch of your Config.plist Comment DW1520 Whitelist Patch (MBP9,2) Find TWFjLTJFNkZBQjk2NTY2RkU1OEM= Name AirPortBrcm4360 Replace TWFjLTZGMDE1NjFFMTZDNzVEMDY=
  7. I don't see BrcmPatchRam2, try downloading from Rehabman's Git rebuilding //System/Library/PrelinkedKernels/prelinkedkernel kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_BCM94352Z_as_BCM94360CS2.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext EAPDFix_beta5.kext kext file:///Library/Extensions/DisableTurboBoostBattery.kext/ is in hash exception list, allowing to load kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDA_ALC293C.kext /System/Library/PrelinkedKernels/prelinkedkernel not cached. Successfully updated disk0s3. kextcache updated critical boot files, requesting launchd reboot Finished
  8. Does anything show under USB? From our IOReg, I don't see BrcmPatchRAM2 loaded. Can you output the screen here after you run the permission?
  9. Try adding BrcmFirmwareData.kext or BrcmFirmwareRepo.kext from here
  10. Did you run the permission fix? sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U /
  11. What's your system specs? What loader are you using? Clover or Chameleon? Try the bootpack here.
  12. Sorry, forgot to add the link to the Clover guide. Updated link in post #15 In your BIOS, you should uncheck Optimus and Enable AHCI
  13. Try the version in this post. Kext by Son Vu
  14. Try this guide, use the E6420 bootpack, but replace DSDT with this one.
  15. @Allen_N Is your SD Carder working with your current config?
  16. Try A11, not sure about A12, I see some video enhancement on that update.
  17. Open Config.plist from /EFI/Clover with Clover Configurator 4.24/5. Next to Kernel and Kext Patches, enable Asus AICPUPM. Save the file and try again.
  18. What loader are you using? Clover or Chameleon Chameleon = You need the Extra folder copy to the USB installer, that's your bootpack Clover = You need to Clover folder from the EFI partition, this is your bootpack Run this from terminal to determine which kexts you have installed to /System/Library/Extensions. You can then copy those kexts to a folder in the USB to be installer later. You can install kexts with Kextwizard or other kext utility. sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U /
  19. @ssprod The DSDT I uploaded is for singleLink 1366x768, can you confirm you have that resolution? Also you need to use the Config from E6230, confirm that also. Lastly, downgrade your BIOS to A03, and then install A12.
  20. Downgrade BIOS to A03 and then upgrade to A12. Yes, first remove the SSDT/DSDT from Patch folder, reboot, then hit F4 to extract raw files. Compress and upload it here.
  21. Googling the system specs and determine that the s model can either have an IvyBridge with HD4000 or SandyBridge with HD3000. List your system's spec to determine which bootpack is best fitted for your system. If it's an IvyBridge, you could try the E6230 bootpack with lower resolution.
  22. No need, I think I have it patched in the Config file. Check your system report under SATA/SATA Express to verify.
×
×
  • Create New...