Jump to content

119 posts in this topic

Recommended Posts

Advertisement

also, did you Remove AppleIntelLpssI2C.kext and AppleIntelLpssI2CController.kext

when you tried the dsdt that had patches for trackpad?

you said your device dissapeared. but i see it in ioreg working.

 

try this after you deleted the above kexts from system/library/extensions and rebuilt cache

 

patched.zip

Edited by onejay09

Share this post


Link to post
Share on other sites

Hello @onejay09 yes I did delete AppleIntelLpssI2C.kext and AppleIntelLpssI2CController.kext, but I didn't say that my device disappeared I said it was detected in the system pref pane, but I had no input anyway I'm currently outside and will try the sleep and touchpad fixes and report any progress, btw: do you have working gestures (two finger scrolling etc), if so is your touchpad ELAN1200?

Thanks!

Share this post


Link to post
Share on other sites

you should delete voodoohda.kext and applehdadisabler.kext as youve got applealc.kext which is the best option.

also the ioreg you sent was without voodoo patches.

personally i think you should do a fresh install and keep the clover setup.

as youve got a lot of stuff you shouldnt have.

Share this post


Link to post
Share on other sites

Hello @onejay09 I will now do a fresh vanilla install without any modifications and keep the current EFI, if you could guide me through the post install process I would be grateful, thanks!

Share this post


Link to post
Share on other sites

Hello @onejay09 I did a fresh install and now the audio is working with AppleALC (jack sense now works!) but internal mic doesn't, and the display was detected without the injector but the brightness was the same among all levels, so I patched it again but then I had no backlight control at all (display still detected)?! so I then copied the old buggy patched AppleBacklight and the injector from a time machine I did before the fresh install and now it is back to what it was (same issues) here is the ioreg with the buggy kext, thanks!

https://www62.zippyshare.com/v/jGw1lLOt/file.html

Edited by M3G4DR01D

Share this post


Link to post
Share on other sites

you only need the injector not the applebacklight.kext, i hope you backed up the vanilla kext. 

dont do anymore things to the setup, not without someones help, ie me. ask before you do it so im not cleaning up your mess again.

Edited by onejay09

Share this post


Link to post
Share on other sites
14 minutes ago, onejay09 said:

you only need the injector not the applebacklight.kext, i hope you backed up the vanilla kext

Oh, well that explains a lot :hysterical: , yes I did back it up so I should add the vanilla backlight kext and the injector to S/L/E right?

Share this post


Link to post
Share on other sites

yes just the injector, i connects to your displays product id and loads applebacklight and injects properties for your display.

im back in work tonight so i will be available to help more.

Edited by onejay09

Share this post


Link to post
Share on other sites
4 minutes ago, onejay09 said:

yes just the injector, i connects to your displays product id and loads applebacklight and injects properties for your display.

im back in work tonight so i will be available to help more.

Thanks I just ordered pizza for the occasion :D 

Share this post


Link to post
Share on other sites

you may look at config.plist and delete fake cpuid as you might not need it, it may affect sleep if its still not working right

currently you inject plugin type 1 with clover for cpu PM. thats ok.

 

btw MacBookPro14,3 is same proccessor

i7 7700hq

what smbios do you use?

Share this post


Link to post
Share on other sites
6 minutes ago, onejay09 said:

you may look at config.plist and delete fake cpuid as you might not need it, it may affect sleep if its still not working right

currently you inject plugin type 1 with clover for cpu PM. thats ok.

 

EDIT: nvm I found it under kernel and kexts to patch but its empty?

Btw does the backlight level under system parameters have anything to do with the 4 extra backlight levels I'm having (apparently my display has only 12 but I get 16)

Edited by M3G4DR01D

Share this post


Link to post
Share on other sites
16 minutes ago, onejay09 said:

yes just the injector, i connects to your displays product id and loads applebacklight and injects properties for your display.

im back in work tonight so i will be available to help more.

So I did as you asked vanilla + injector and now I have no brightness control (slider or in the pref pane) but the display is still detected?

Share this post


Link to post
Share on other sites
3 hours ago, M3G4DR01D said:

EDIT: nvm I found it under kernel and kexts to patch but its empty?

Btw does the backlight level under system parameters have anything to do with the 4 extra backlight levels I'm having (apparently my display has only 12 but I get 16)

no the backlight in config.plist is so you dont boot with a black screen, as brightness will set to 0 at boot without it.

the 4 extra levels can be fixed by changing the values used in the injector, lets get it working first.

hows the config.plist?

Share this post


Link to post
Share on other sites
4 minutes ago, onejay09 said:

no the backlight in config.plist is so you dont boot with a black screen, as brightness will set to 0 at boot without it.

the 4 extra levels can be fixed by changing the values used in the injector, lets get it working first.

hows the config.plist?

It's great the smbios is now mbp 14,3

Btw the injector from the time machine (pre fresh install) works but the newly patched one from fresh install doesn't

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.5_18F132
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.5.zip
       
       
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
×