Jump to content
gygabyte666

HP Envy 17t-j000 Quad (Haswell) + 10.8.5/10.9.5/10.10.x/10.11.x/10.12.x/10.13.x/10.14.x

1,319 posts in this topic

Recommended Posts

I appreciate it mnfesq but if your kext is like the original by ivik then I doubt it'll change anything.

 

Obviously, i've already tried using it. Twice actually. The first time I figured i'd try my luck with it without making the required DSDT edits. The second time, I made the required edits but ran into trouble when I had to make changes to _BCM _BCQ & _BCL. They don't exist in my DSDT and so I tried to luck my way through it and added them in anyway. Doing this gave me compile errors, which I ignored and upon booting, I always ran into a KP.

 

You're using an HP laptop right? Any chance you could post your DSDT so I could examine it? Maybe I could fix my brightness by using yours for reference. Thanks :)

Share this post


Link to post
Share on other sites
Advertisement

I appreciate it mnfesq but if your kext is like the original by ivik then I doubt it'll change anything.

 

Obviously, i've already tried using it. Twice actually. The first time I figured i'd try my luck with it without making the required DSDT edits. The second time, I made the required edits but ran into trouble when I had to make changes to _BCM _BCQ & _BCL. They don't exist in my DSDT and so I tried to luck my way through it and added them in anyway. Doing this gave me compile errors, which I ignored and upon booting, I always ran into a KP.

 

You're using an HP laptop right? Any chance you could post your DSDT so I could examine it? Maybe I could fix my brightness by using yours for reference. Thanks :)

You can also google for "shades" with arg "mac" and install this prefpane. Is an other possibility to fix your brigthness issues.

 

Have fun.

Share this post


Link to post
Share on other sites

You can also google for "shades" with arg "mac" and install this prefpane. Is an other possibility to fix your brigthness issues.

 

Have fun.

Thanks but I've used shades before and it's really nothing more than a "dimmer" app. It's not a suitable replacement for hardware functioning backlight adjustment.

Share this post


Link to post
Share on other sites

Yeah, this is ivik's kext.  I've got to get better at giving proper credit for other people's work.  Here's my DSDT.  In device GFX0 there is a device called DD02.  That is my LCD display.  It has the _BCL, _BCM and _BQC methods.  I added "Name (_HID, EisaId ("LCD1234"))" to this device and that is what made brightness work with ivik's kext.

 

DSDT.aml.zip

Share this post


Link to post
Share on other sites

Damn! That's why my brightness has been such a pain...

 

I forgot the reason was because unlike many people, my GFX0 isn't listed under my DSDT. It's listed under one of my SSDTs and since I use Clover's DropOemSSDT feature, I would probably have to merge mine in order to get brightness working with ivik's kext. Unfortunately, my SSDTs are almost as long and complicated (if not more) than my DSDT and I wanted to avoid merging them if possible.

 

Anyways, thank you. Maybe I can get lucky and add a new GFX0 section with yours as reference and it will trick it enough to work. >_<

Share this post


Link to post
Share on other sites

Try copying the GFX0 from your SSDT to your DSDT.  The important thing isn't GFX0 so much as it is the devices listed under it.  You need to find your display.  If you have GFX0 in your SSDT, couldn't you add the line to your LCD display in GFX0 in your SSDT?  Either way, if you have compile errors, look for the methods or other objects in your SSDT to add to your DSDT to get it to compile.

Share this post


Link to post
Share on other sites

I have little choice but to try to figure out how to do that. Unfortunately, I've already tried doing that several times already without success. My GFX0 section has TONS of devices listed under it and it is very complex and confusing when attempting to make any changes to it. I haven't checked it in awhile so I don't know off the top of my head if there is an LCD section or not. I have LID0 listed under my dsdt but as mentioned, none of the required methods for ivik's left are listed under it. Copying everything over is easy, removing the mountain of compiling errors is the real chore. I'll give it another try and we'll see where I end up.

Share this post


Link to post
Share on other sites

EDIT:

 

So, I wasted my time trying to merge my DSDT and one of my SSDTs together to try to fix my brightness issue only to discover that Clover can load multiple SSDTs at boot. >_>

 

Needless to say, I was very happy when I figured this out and because of this I am now able to load the GenericBrightness kext. :)

 

That said, my brightness still can't be adjusted. I believe I know why now though. You see, ever since I got my 4600 working, i've been constantly trying to perfect it. I have had graphical glitches since the beginning and I still do, although now I have SIGNIFICANTLY less of them. So long story short, I am going to play around with values again until I find the right one that makes all the glitches disappear, or at least fixes the brightness adjustment. Whichever comes first.

 

So, stupid me for wasting my time thinking I had to merge my DSDT to get GenericBrightness working. Lesson learned. :D

 

UPDATE:

 

I was playing around with the values, trying to hit the sweet spot for my GFX when I came across a bad side-effect of keeping GenericBrightness in my kernel cache. Seems that kext keeps my display on pretty tight lockdown and if anything else tries to change it, the kext freaks out. Example, If the refresh rate on my display is switched, I get a KP. The mystery of brightness adjustment keeps getting more and more odd. >_>

 

Pardon my ignorance but isn't there a way to get native Apple-style brightness for laptop LCDs? I thought this was once a mystery that the good hacking people had figured out. I suppose Apple could have changed a bunch of things since then, this was afterall way back in the Leopard -> Snow Leopard days as I recall. I just never imagined my backlight brightness would be one of the most difficult puzzles to solve with OS X. *sigh*

Share this post


Link to post
Share on other sites

Yes I did add that in. I am pretty sure I did everything correctly. Do you have anything like this listed in your Console log?

Acpi brightness levels:11, lowest brightness:0, highest brightness:100

UPDATE:

 

Um...Ok? So I got it working...sort of. >_<

 

Turns out, I think my replacement ACPIPlatform and/or AppleSmartBattery kexts may have caused the problem. I figured this out by removing the power adapter for a few secs and was alarmed that my battery icon didn't auto switch to saying I was running off the battery, like it normally would. I let the system sit for a second or two until the display turned off, and when I woke it back up, the brightness had changed! After that shock, I tried using the slider again and to my amazement, it worked from then on. WTH?

 

Well, I'm not sure what to do now. On one hand I want the slider to work without having to go through all that each time I boot, but on the other hand I need my battery icon to be displayed and accurate. Not only that, i'm concerned about reverting to the stock ACPIPlatform kext because I am pretty sure it was causing me to get KPs when I first tried out the 10.8.5b. Any suggestions? What are you using for your battery icon mnfesq?

Share this post


Link to post
Share on other sites

Glad to see you are making progress!  You should check your power saving settings now that you can change your brightness.  BTW, yes, I do see the ACPI brightness levels in my boot log.  For my battery, I use iStat menu items but only for battery.  I still like menu meters and hwsensors for most other things.  Here are the kexts I use to get my battery to display correctly:

 

Archive.zip

 

Hope they help.

 

Share this post


Link to post
Share on other sites

Thanks mnfesq, yes WiFi/BT is still an issue. I've been waiting for something better to turn up. I was eyeballing that thread but glad u reminded me to check it again.

Share this post


Link to post
Share on other sites

Just a quick update as I have to get ready for work and don't have much time. I tried replacing my ACPIPlatform & SmartBattery kexts with the stock 10.8.5 versions only to discover something about the stock ACPIPlatform kext refuses to generate a kernelcache with my setup. That is very bad because I would have to boot every time without caches and I will not do that. I believe it's due to me using a different kernel. As you may know, I can't boot with the stock 10.8.5, it gives me a reboot loop but my current kernel works and it's a modified 10.8.4 kernel with Haswell support added. That said, I'll have to stick with my current working kexts until I can get the stock kernel working on this machine. For this reason, I have stopped using GenericBrightness for now because using it prevents me from changing display refresh rates and switching resolutions which is a HUGE no no for playing games and testing.

 

Another odd behavior is during the kext swapping test, I noticed that it tried to generate power management for my CPU based on my smbios. it failed and thanks to my required AsusPMPatch fix, it will KP when it does. So, I'm wondering what is so special about the 10.8.5ACPIPlatform kext that would make it try to fix my current CPUPM setup? I will have to try to investigate this.

 

Lastly, I wanted to thank mnfesq again for the kext upload. I haven't had a chance to check it out yet but I will and I'll update you after I do. Just wanted to acknowledge that you did upload it and express my gratitude for you doing so.

 

That's all for now. Alright, gotta run and get ready for work. >_>

Share this post


Link to post
Share on other sites

To start, once again thank you mnfesq for the kext upload. I finally got around to messing around with those. Here are both my concerns and my findings:

 

1) Not to sound ungrateful but why did you include AICPUPM? You do realize that has nothing to do with the battery icon right? If anything, I would have expected to see ACPIPlatform in it's place because 10.6 Snow Leopard's version that works with VoodooBattery to identify AC adapters and batteries for many machines. Seems the more modern versions of ACPIPlatform are considerably more picky about what they allow to pass through.

 

2) Are you actively using these kexts now? If so, you may want to consider deleting one of them because you are using two battery injectors and you likely only need one. ACPIBattery (aka SmartBattery) will probably do you just fine alone. The only thing VoodooBattery does that the other injector does not is detect AC adapters but that is provided you have detection of that working with a corrected DSDT. Another note is AFAIK, VoodooBattery hasn't been actively updated in a LONG time.

 

3) I'm using the most recent version of ACPIBattery I could find. Until I perform some more DSDT edits, it won't even detect my battery. However, It does display the menubar icon and everything appears correct in the power settings pref pane. So, i'll be looking into fixing that later. As long as it can detect when I plug in AC power and when it's disconnected, I see no reason why I shouldn't rely on it for future use. So, thank you again for your upload and subsequently for suggesting it. Because of this I can update my ACPIPlatform kext to the newer 10.8.4 version and get even better and more authentic PM. :)

Share this post


Link to post
Share on other sites

Oops, you are correct about AICPUPM, it was next to ACPIPlatform and I added the wrong kext to the archive.  Here's the ACPIPlatform that works with SmartBattery.  As for Voodoo, all I know is that I have all battery/AC functions working and have used both for quite some time (Lion days.)  Whether I actually need Voodoo, I can't really say.  Try it and see if it makes any difference.  If not, toss it.  I have noticed that if I unplug the AC and replug it back in a moment later, it will switch to battery power and will not detect the AC.  If, however, the battery level drops below 100%, when I replug in the AC adapter, it will detect it right away and begin charging.

 

AppleACPIPlatform.kext.zip

Share this post


Link to post
Share on other sites

No worries, just wanted to make you aware that's all. :)

 

Yup, as expected! The ACPIPlatform you uploaded is the Snow Leopard version. I was using that too for the same reason. It picks up non-Apple batteries better than the modern ones do.

 

You should kick VoodooBattery out of your S/L/E or where ever you have it installed at. It's more than likely not doing you any good since you have the other injector. It might even fix the issues you're facing now with battery/AC detection. Having two injectors for the same purpose has always been seen as doing more harm than good in the osx86 community. Like I mentioned, the only good it serves is it has AC detection in ioreg where the other injector did not. Otherwise, it's just another injector that is horribly outdated. Give it a try sometime and see what happens. Besides, worse case is i'm wrong and you just reinstall it. :)

 

Anyways, if you're interested, the attachment is the method I was using to get my battery displayed. I say was because I really should try to keep using the ACPIPlatform from 10.8.4 so I can keep using all the PM features it offers. Obviously though if I can't get my battery back without it, then i'll have to pick and choose. The ACPIPlatform included is the same as the one you uploaded, so you probably won't need to use it but I provided it anyway, just in case.

 

However, I uploaded it for you to try. After seeing that you have been having delay issues with your current method, mine quite possibly might fix that if the other method above doesn't work. The kexts in mine almost always picked up everything I did with my battery just about instantly. I never had any issues with it detecting me unplugging or plugging in. It was almost always dead on the money. Give it a shot, you might like it more. Otherwise I worry something in your DSDT is off. Delay problems like that usually are a sign of an DSDT edit or a setup problem. No matter what, it's not good to have PM problems like that on a laptop. Sometimes, they can't be helped much either though. >_<

10.8_Battery_Support.zip

Share this post


Link to post
Share on other sites

So I deleted Voodoo Battery kext.  Yes, it was extraneous.  I tried your battery support files - no change.  They seem to be the same as mine and, at a minimum, work the same.  I still have the delay in recognizing power state changes and, particularly, can't get the AC recognized unless the power level drops below 100%.  Not really a big deal but I like testing out stuff in the event that I may get my installation that much closer to perfect.

 

BTW, I spent some time trying to see if I could get my card reader to work.  It is a Realtek PCIe card reader (10EC:5229) and it appears there is simply no support for the card reader I have.  It has never been an issue for me since I don't use SD cards but, again, i was looking to enhance the functionality of my installation.

Share this post


Link to post
Share on other sites

Oh well, it was worth trying out. At least you freed your system by 1 extra kext though so that's good. That's all I'm looking to do now too. Just trying to fix the bugs really. My only real issues now are trying get my brightness to work properly without having the inconviences that GenericBrightness was causing. Updating my ACPIPlatform has caused me to lose my battery support, so I have to fix that but in doing so, I gained SpeedStep, or at least my CPU has dynamic frenquenies working now. So, that's good and if I have to downgrade ACPIPlatform again to get my battery support back, I'm probably going to lose that. I'm also planning on looking into getting my PCIe graphics working since Apple added support into their iMacs.

 

My SD card reader doesn't work either. I also have a Realtek PCIe but I don't know the dev ids off the top of my head. I'll add them up when I'm on my computer again to check. It's probably similar too yours though. Closest I got to getting it working was through VoodooSDHC kext. It could detect it but it couldn't make it work. Oh well...

Share this post


Link to post
Share on other sites

I tried upgrading from ACPIPlatform version 1.3.5 to 1.3.6.  All I got was a KP.  Just like every other version of ACPIPlatform since 1.3.5.  I cannot seem to boot up unless I am using version 1.3.5.

Share this post


Link to post
Share on other sites

Getting panics from ACPIPlatform can have several causes. You should check the panic screen to see where it's having trouble. It should say something right before the panic ex:) CPU0, etc...

 

If you are using a SleepEnabler kext, they can cause panics. VoodooHDA is also a known cause of KPs with ACPIPlatform. You should investigate what kexts you are using and do your best to minimize what you need vs what you can live without. I get absolutely no panics with ACPIPlaform. The only versions of ACPIPlaform I currently can't use are the stock versions bundled with 10.8.5 & 10.9 but that's because of how they were made. Something about them is different from previous versions. That's why I get panics. Yours is probably related to other kexts though from the sound of things.

 

On a side note, does your AC adapter have AppleACPIACAdapter loaded for it in ioreg? If not, I may have a solution for your battery plugin/unplug delay. Let me know.

Share this post


Link to post
Share on other sites

I am using VoodooHDA.kext but that's because I was able to add a device for my subwoofer.  Do you have all of your speakers working with AppleHDA?  If so, are they a single device or multiple devices?  I know you use AppleHDA and I would like to try that out but not at the loss of my subwoofer.  My audio is so tinny without that subwoofer.  However, if I switched to AppleHDA, I could try using a newer version of AppleACPIPlatform.  Who knows, I may still get a KP.

Share this post


Link to post
Share on other sites

Thanks, Charlie! I will investigate and possibly test this provided I get some free time. Good find. :D

 

I am using VoodooHDA.kext but that's because I was able to add a device for my subwoofer.  Do you have all of your speakers working with AppleHDA?  If so, are they a single device or multiple devices?  I know you use AppleHDA and I would like to try that out but not at the loss of my subwoofer.  My audio is so tinny without that subwoofer.  However, if I switched to AppleHDA, I could try using a newer version of AppleACPIPlatform.  Who knows, I may still get a KP.

I thought you were using VoodooHDA. As I recall, you sent me your kext for testing. Yeah, i'm using AppleHDA for my audio. Considering the amount of time I spent getting it to work with it, of course i'm using it, lol. I only have my headphones/webcam mic and basic speakers working using it. Both my sub and my HDMI audio don't work with it. that's probably what's causing the KP with ACPIPlatform for you though. AFAIK, Apple's HDA kext doesn't support multiple devices such as subwoofers because no authentic Macs (to my knowledge) have anything like that built-into them so they just don't support it. Even HDMI isn't natively supported though AppleHDA. It must be patched in through both the HDA binary and through the native framebuffer binary before it will work. Again, this is all based on my current understanding of how it works. Some of that info may be incorrect. So that is probably the cause. If you can't live without your sub, then stick with what you've got. I mainly use my headphones so missing the sub isn't much of an issue for me and with all the BS that is required to get HDMI audio working, it's just another thing I can live without. Now if a patch ever comes along that makes it an easier process, maybe i'll look into getting those devices working but until that happens, I am quite pleased with what I have. :D

Share this post


Link to post
Share on other sites

The sound quality is really good when it is fully functional.  I use OS X primarily for entertainment, not work.  My wife and I watch downloaded TV shows and movies together on it and it is our only "sound system" for music.  It really provides a good entertainment experience.  My headphones output is also quite good but I seldom use them because I tend to watch videos with my laptop on a coffee table at least 3 feet away from me.  BTW, I have been using an app called Flutter and it allows me to control iTunes and VLC media player using hand gestures so I don't have to lean over to start or stop videos or to fast forward or rewind.  It uses the webcam to do this.  I see this as the way of the future since touch screens have always seemed like a flawed concept to me.

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 yehia2amer
      Dell Precision T7610 Workstation
      Hackintosh GUIDE (Work in Progress)
       
                        
      Introduction: 
      Hi Everyone,
      This Workstation used to be a Beast with Dual CPUs and tons of RAM, I Know it is now normal to get that much cores in a Desktop but it is still a very decent machine for me (As a Programmer), and I thought it would be a good idea to Install MacOS as the Daily Driver Rather than Linux and It turns out to be a very Great Experience (with Some Challenges ).
       
      Specs:
      CPU: 2x Xeon E5-2680 v2 2.8GHz Ten Core Processors RAM: 128 GB 1333 MHz DDR3 ECC Memory GPU: SAPPHIRE PULSE Radeon RX 580 8GD5 Chipset: Intel C602 Audio: Realtek ALC3220 (ALC280) High Definition Audio SAS Drive Controllers (RAID): LSI 2308 SATA/SAS 6Gb/s controller with host based RAID 0, 1, 10 (4  Network Controller 1: Intel 82579 Gigabit Ethernet controller with Remote Wake UP, PXE and Jumbo frames support
      Network Controller 2: Intel Ethernet Controller I210
      NEC USB3.0 xHCI Controller: Renesas Electronics uPD720201 & uPD720202
       
      Working:
      Both "Xeon E5-2680 v2" and all cores with Power Management and P-States (using VoodooTSCSync & ssdtPRGen.sh) ATI Radeon HD 4870 (Vanilla) Realtek ALC3220 (ALC280)  (using VoodooHDA till Now - it is partially working with AppleALC using layout-id 13) LSI 2308 SAS (using AstekFusion2) Intel 82579 Network Controller (Vanilla) Intel I210 Network Controller (IntelMausiEthernet) USB 2.0  
      Not Working:
      NEC USB3.0 xHCI Controller (Renesas Electronics uPD720201 & uPD720202) Sleep  
      https://github.com/yehia2amer/Dell-Precision-T7610-Workstation-Hackintosh-Guide
    • By ludufre
      Installing macOS Mojave on Lenovo ThinkPad L440

       
      There are two version of this laptop:
      - 20AS = Chipset QM87, without Express Card (mine).
      - 20AT = Chipset HM86, with Express Card.
      I strong believe is the same thing...
       

      Changelog:
       
      02/05/2019 18:47h GMT-0
      - Updated info about CPU replacement and 4G LTE modem.
       
      02/04/2019 15:24h GMT-0
      - Sometimes the VoodooHDA.kext doesn't work.
      - Added AppleHDADisabler.kext to fix that (attached bellow).
       
      01/24/2019 14:42h GMT-0
      - Added more adjustments to use of VoodooHDA.
      - Updated VoodooHDA links to 2.9.1 official (without installer).
      - Changed PCM volume from 90 to 180 in Info.plist (attached modified VoodooHDA.kext bellow)
      - Updated SSDT-L440.aml (Removed HDEF and HDAU, not needed).
      - Updated config.plist (Changed to user Audio layout to 1).
       
      01/22/2019 20:47h GMT-0
      - I gave up on the AppleALC.
      - Headset does not work.
      - Now with VoodooHDA is perfect and the sound even louder.
       
      01/22/2019 14:37h GMT-0
      - Add info about update 10.14.3. 
       
      01/22/2019 13:46h GMT-0
      - Add link to BIOS reassing guide.
       
      01/20/2019 11:49h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i5-4300M ->  Work. All SpeedStep stages.
      - Video Card: Intel HD4600 ->  Work. QE/CI and Metal.
      - Chipset: Intel QM87 ->  Work.
      - Mini DisplayPort ->  Work. But no audio, yet.
      - VGA ->  Not work. Normal.
      - Audio: ALC292 ->  Work.
      - WiFi/Bluetooth: Intel AC 7260 ->  Not work. Replaced with DW1560 (need whitelist removal).
      - Ethernet: Intel I217-LM ->  Work.
      - Card Reader: Realtek RTS5227 ->  Not work.
      - Keyboard and Touchpad ->  Work.
      - Webcam ->  Work.
      - Fingerprint Reader ->  Not work. Normal.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Extras
       
      - FullHD 1920x1080 display upgrade: 
      Replaced with AU Optronics B140HAN01.1 30pin eDP (B140HAN01.2 and B140HAN01.3 also compatible)
      Apparently same screen as Dell Latitude E6440, E7440, Lenovo Ideapad U430 and E129.
       

      Todo
       
      - Make DP audio work.
      - Make Card Reader work.
      - Upgrade CPU to i7-4712MQ (Ordered. It's on the way) Done, but received i7-4700MQ (47w TDP and I have overheating issues)
      - Replace touchpad with T460 model (Ordered. It's on the way)
      - Sierra Gobi5000 4G LTE modem EM7355 (Ordered. It's on the way. I hope works. ) Done, but not work. Do not even recognize in LSPCI...
      - Upgrade to 16GB RAM Done
       
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ .app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes.
       


      Install bootloader

      Download the RehabMan's CloverEFI fork (used 4701) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix64


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop.
      - Replace the /Volumes/EFI/CLOVER/config.plist with mine attached below
                    If you have modded BIOS with Advanced Menu and enabled 128MB DRAM-prealloc use 128MB_DRAM-prealloc_config.plist.zip
                    If no, then use 32MB_DRAM-prealloc_config.plist.zip
      - Put SSDT-L440.aml attached below in /Volumes/EFI/CLOVER/ACPI/patched/
       
      Generate your Serial, MLB and SmUUID
       
      - Open the replaced config.plist with Clover Configurator (used 5.3.2.0)
      - Go to SMBIOS, click few times in "Generate New" in Serial Number and SmUUID.
       
      Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the FakeSMC.kext from here. I used the version 2018-0915.
      - Download the VoodooPS2Controller.kext from here. I used version 2018-1008.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-1031.
      - Download the Lilu.kext from here. I used the version 1.3.1.
      - Download the AppleALC.kext from here. I used the version 1.3.4.
      - Download the VoodooHDA from here. I used the version 2.9.1.
      - Download the WhateverGreen.kext from here. I used the version 1.2.6.
      - Download the AppleBacklightFixup.kext from here. I used the version 2018-1013.
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
      - Download the ACPIBatteryManager.kext from here. I used the version 2018-1005.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Unfortunately, some notebook manufacturers are currently blocking the replacement of wireless cards. They want you to only use the models sold by them. And of course, none of them from Lenovo for this notebook model is compatible with MacOS.
       
      If you try to start with an unauthorized wifi card for them, you will receive a screen error:
      1802: Unauthorized network card is plugged in - Power off and remove the network card. Since this check is done directly in the BIOS, the only solution is to modify it.
      But since nothing is easy in this life, there is one small big problem:
      - The BIOS update procedure does not allow you to use modded files as it used to be.
      - You will need to physically reach your BIOS on the motherboard and make use of a USB BIOS reader/writer.
       
      So what you need to do:
      1. Disassembly your laptop;
      2. Dump your BIOS with an USB BIOS reader with SOIC8 clip (to not desolder from the motherboard);
      3. Patch it (In addition to removing the whitelist, add the advanced menu);
      4. Fix RSA signature;
      5. Reflash BIOS;
      6. Replace wireless card;
      7. Remount your laptop;
      8. Done.
       
      Soon, I'll provide step by step in this process. Probably until end of this week.
      In the meantime, if you need to, send me your dump that I do steps 3 and 4 for you.
      I also add the Advanced Menu so you can increase to 128MB the DRAM-prealloc.
       
      To fix a Modded BIOS to remove the 5 beeps on boot, you need this guide: https://www.insanelymac.com/forum/topic/337333-guide-fix-insyde-h2o-bios-signature-5-beeps-on-lenovo (traduzido: pt-BR)
       
       
      After replaced the wireless card. Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the AirportBrcmFixup.kext from here. I used the version 1.1.9.
      - Download the BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext from here. I used the version 2018-0505.
      - Download the BT4LEContinuityFixup.kext from here. I used the version 1.1.2.
       
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      My BIOS is the latest: 1.93 (J4ET93WW) 

      - Shutdown and insert the flash drive.
      - Power on with F1 pressed to enter BIOS setup.
      - Change value: Config - Intel(R) AMT - Intel(R) AMT Control to DISABLED
      - Change value: Security - Security Chip to DISABLED
      - Change value: Security - Anti-Theft - Intel(R) AT Module Activation to DISABLED
      - Change value: Security - Anti-Theft - Computrace to DISABLED
      - Change value: Security - Secure Boot to DISABLED
      - Change value: Startup - UEFI/Legacy Boot to BOTH, Legacy First and CSM Support = Yes
      - Save & Exit Setup (F10)
       
      - Now, hold the F12
      - In the list, select your flash drive.
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "Macintosh".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot. Maybe you have to press F12 again and select the flash drive.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the config.plist inside your destination disk EFI parittion with config.plist inside flash card EFI partition.

      The flash drive EFI partition is unmounted. Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 1.
       
      Last step
       
      Copy all Kexts from flash drive to /Library/Extensions, with those commands in Terminal:
      sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/Other/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.3
       
      - Updated with success;
      - Everything works perfectly after reboot;
       

       
       

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas, @Shiki and all others members involved directly or indirectly.
       
       
       
       
       
       
      32MB_DRAM-prealloc_config.plist.zip
      128MB_DRAM-prealloc_config.plist.zip
      SSDT-L440.aml
      VoodooHDA.kext.zip
      AppleHDADisabler.kext.zip
    • By ucif19
      Hi, First of all, sorry for my English.
      I want to buy a WiFi/bt card for my hackintosh. I want a card that have a native support for MacOS because I need to use Handoff and AirDrop. I saw the card in the link below: anyone could tell me if the card have the requirements I mentioned before?
       
      wifi/bt card  Broadcom 94352Z DW1560: https://rover.ebay.com/rover/0/0/0?mpre=https%3A%2F%2Fwww.ebay.it%2Fulk%2Fitm%2F272204993348
       
      my build
      macos Mojave 10.14.3
      mobo: H170N-WiFi 
      cpu: i5-6500
      gpu: gtx 1060 6gb (not work on Mojave)
      Ram: 16Gb ddr4 2133 MHz
    • By ucif19
      Hi,  I replaced the H170N-WIFI onboard bt card with the ASUS USB BT400 dongle. It works but Handoff and AirDrop won’t work. I install all kexts for fixing Broadcom card, but in System Information, in Bluetooth section I see “Handoff: no”. Anyone can help me? Sorry for my English!
       
      my build
      mobo: H170N-WiFi 
      cpu: i5-6500
      gpu: gtx 1060 6gb (not work on Mojave)
      Ram: 16Gb ddr4 2133 MHz
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×