Jump to content
leodaniel

Clover: iMessage/Facetime Fix for Yosemite

252 posts in this topic

Recommended Posts

image.png

 

IMPORTANT: CAUSED BY NEW APPLE VERIFICATION-STEPS, you need MLB (BoardSerialNumber) and ROM from a real Mac.

The use of real mac MLB/ROM is a temporary solution. I always prefer to use generated IDs, but actually there is no way around.

 

Note:
This guide is for Clover users only. Please do not ask questions related to Chameleon or other Bootloaders.

 

Please follow all steps, or at least read them all.
You will probably need to call the Apple support to activate iMessage, but don’t worry, I will explain you what you need to do.
Also try to change your IDs as less as possible, this is also why I advise you to disconnect temporary from internet after step 3. 

Never share your ID's and never believe or use ID's found on the internet!
 

 

Requirements:

 

1 Step
You need to mount you EFI partition, to do so, type following command in terminal (Applications>Utilities>Terminal)

diskutil list

The output should look like this:

post-1251536-0-99042100-1415126512_thumb.png

 

Look for your System HardDrive or SSD (in my case HackintoshSSD 10) and copy your EFI partition IDENTIFIER (in my case disk1s1)

 

Now type following command:

diskutil mount YOUR_IDENTIFIER

in my case this would be:

diskutil mount disk1s1

Now you should see EFI Drive in Finder.

 

 

2 Step

Open the Clover Configurator Application, you should see following screen:

post-1251536-0-97461200-1415126633_thumb.png

 

Select following config file: EFI > EFI > CLOVER > config.plist

(Highlighted in blue).

 

Now move to the SMBIOS Section (left menu). Click on the magic wand icon and select appropriate bios for your system.

If you are not sure which one, check your About this Mac>System Reports and check your Model Identifier (in this example iMac (13,2) ).

post-1251536-0-21971900-1415128338_thumb.png

Click several times on the little shake buttons to generate a Unique Serial for you Hackintosh. (Note: This is only an example, don’t use the serials shown in the image!)

Now you need to check, if your Serial is a generic one and not from a real mac.

To do this: go to https://selfsolve.apple.com and enter you generated serial. If you don’t get an error Message, just randomise the serial again with the 2 little shake buttons. Repeat this until you get an error message on the site.

Click on “OK” to save you SMBIOS.

 

3 Step

You should now have a screen similar to this one.

post-1251536-0-57853900-1415128496_thumb.png

Now you need to populate those 2 RED indicated fields.

Open again Terminal and enter:

uuidgen

This will output something like this:

C5FAA18D-AA58-44E4-ABBF-C31885429CD7

Repeat this 3-4 times to be sure to get an unique one. Copy it and paste it into SmUUID.

 

The second file that needs to be populated, is the board ID.

For this, just copy your Serial and Enter some random letters and numbers, that you get a length of 17 digits!

In my example this would be: C02LHIA7DNMP7E8G4

 

4 Step

Go to the RT Variables Section, enter the MLB (BoardSerialNumber) & ROM value from a real mac and click Calculate.

Do not use values found on the Internet! Only use values from your own mac and never ever share them! To learn more about MLB check out this Thread by holyfield.

To find those Values on a real mac, simply run iMessage Debug or for older macs (OS X Lion / Snow Leopard) check out here (by Fusion71au). The real mac does not need the be the same model as your SmBios, you can use the ROM/MLB form a MacBookPro with MacPro SmBios on you hack. You can also still use both Macs on the same times on iMessage.

post-1251536-0-99302600-1417963174_thumb.png

 

Go System Parameters Section on Clover Configurator and make sure, that those are empty! 

Now save the file (cmd + s).

Disconnect your computer form Internet and Reboot. Do this several times and always check with iMessageDebug (double click on the file), that all IDs are set and stay the same.

post-1251536-0-35347500-1415128611_thumb.png

 

If it is so, you can reconnect to your network. If not, retry steps 1-4.

You will now be prompted to re-login to iCloud and iMessage.

 

 

Normally you should not get any error or code from iMessage if you use a valid ROM/MLB combination.

If you get an Code and you are asked to call apple, you are using some invalid ID combination, usually related by ROM/MLB. I would not recommend you to call Apple, as you are not using a mac, even if some other tutorials tell you that.

 

Enjoy fully functional iMessage!

Hope it helped

Share this post


Link to post
Share on other sites
Advertisement

Thank you for the tutorial. I was finally able to get the Customer Code screen, which seems to be the gateway to get it fixed. Now I was wondering, my current build is obviously modern, able to run Yosemite and all. I do have an official serial number, however, it is from an old G4 Mac Mini. Will they recognize this? Or is that completely subjective to the rep?

 

I know that you may not even need the serial, but just in case, I wanted to know if they could see that, hey this machine can't even run an OS that uses iMessage.

Share this post


Link to post
Share on other sites

 

All you need, is a valid apple Serial from a real mac. In some cases, they don't even want to know the serial. And if you don't have any, just tell them your actually not home and you just have copied the Support Code. Anyway, the Serial is only needed to associate your case with a device. Explain, that you get an error while trying to log in to iMessage. They will ask your for the Code (Something like 9378-3847-3904). After that all should work!

 

 

 

If possitioned correctly, you do not need a SN at all, read my post here about this.

Share this post


Link to post
Share on other sites

Thank you for the tutorial. I was finally able to get the Customer Code screen, which seems to be the gateway to get it fixed. Now I was wondering, my current build is obviously modern, able to run Yosemite and all. I do have an official serial number, however, it is from an old G4 Mac Mini. Will they recognize this? Or is that completely subjective to the rep?

 

I know that you may not even need the serial, but just in case, I wanted to know if they could see that, hey this machine can't even run an OS that uses iMessage.

I can't give you an complete answer. What I know, is that the serial is send to apple. If and what they check about it, I'm not sure.

But I would never use a Hackintosh with a real Mac Serial. I think it's always better to use a generated one if you can.

 

What I know, is that the System Infos need to match the Serial. So you can't use a MacBookPro serial with the SMBIOS of a mac pro.

And I will update the guide with the infos from YoYelloW, so that a serial isn't needed.

Share this post


Link to post
Share on other sites

Finally worked up the courage to call Apple Support. I took YoYelloW's advice and kept mentioning "My AppleID" and "iMessage", hardly ever brining up my Mac. I actually got an initial person that couldn't help me, then I was sent to another person that never experienced this problem before, and she was a director. So, I guess it is common, but not that common. Anywho, she was able to fix it before I got off the phone! The Customer Code really is the key to get this fix, otherwise they can't really find how to correct it. Thanks again to people in this thread, and in other threads to fix it!

Share this post


Link to post
Share on other sites

It's way to much info around regarding iMessage and facetime. All you need is to make sure that you have unique SN generated in clover configurator and can't leave board ID field empty as clover generated Numbers are blacklisted. Calling Apple just say you upgraded to Yosemite and Messeges gives you code. They will never ask for SN.

Share this post


Link to post
Share on other sites

This hack works fine! You need SMBIOS settings on your Clover configuration. Make sure, that those are correct and valid for your model Clover suggest by-self the best model for your comp. So, generate based on suggested model the actual SMBIOS setting. Also these unique ID's as described by leodaniel.

 

Please note you also need an IPhone, iPad etc. They send the verification code on your iPhone screen at support call time.

Share this post


Link to post
Share on other sites

This hack works fine! You need SMBIOS settings on your Clover configuration. Make sure, that those are correct and valid for your model Clover suggest by-self the best model for your comp. So, generate based on suggested model the actual SMBIOS setting. Also these unique ID's as described by leodaniel.

 

Please note you also need an IPhone, iPad etc. They send the verification code on your iPhone screen at support call time.

 

I don't really think iphone or iPad is really needed at all just generating the serial numbers and making sure you get the customer code at the login screen of iMessage worked just fine. You only need a serial number of a real mac m give them that serial number of that real Mac and they will unlock for u as easy as that.

Share this post


Link to post
Share on other sites

I don't really think iphone or iPad is really needed at all just generating the serial numbers and making sure you get the customer code at the login screen of iMessage worked just fine. You only need a serial number of a real mac m give them that serial number of that real Mac and they will unlock for u as easy as that.

 

There is nothing to do with thinking/guessing. I activated iMessage by myself.

 

Here is the full list of information required by Apple support:

  • First and Last Name
  • Apple ID
  • Computer Serial from About This Mac
  • iMessage Activation ID (from iMassage alert box)
  • Then, they send a verification code to iPhone, which you have to tell to support 

teddybearapple, you can think/believe whatever you want, I told what actually happened.

 

So, keep your iOS device next to you when placing an support call to activate iMessage on Hackintosh.

 

Done!

Share this post


Link to post
Share on other sites

Thanks so much for this guide! The hardest part was the near hour long wait on hold with Apple support. Also, I did not need an iPad or iPhone to complete the procedure -- Robert, the support tech, took care of it there over the phone.

Share this post


Link to post
Share on other sites

There is nothing to do with thinking/guessing. I activated iMessage by myself.

 

Here is the full list of information required by Apple support:

  • First and Last Name
  • Apple ID
  • Computer Serial from About This Mac
  • iMessage Activation ID (from iMassage alert box)
  • Then, they send a verification code to iPhone, which you have to tell to support 

teddybearapple, you can think/believe whatever you want, I told what actually happened.

 

So, keep your iOS device next to you when placing an support call to activate iMessage on Hackintosh.

 

Done!

I have called them several times myself, I only needed a serial once and all the other times they required a support token. 

Maybe it is related to your Apple ID which wasn't verified before (no Credit Card)? Anyway, it worked, that matters :D.

Share this post


Link to post
Share on other sites

If you say that you updated to Yosemite and message does give you code to contact them, they will never ask for s/n only for that code. I did hovewer had many real Apple products registered on my id before.

If you start your conversation mentioning your machine model than that triggers model specific problem and they might ask s/n. Talk only yosemite and message.

Share this post


Link to post
Share on other sites

If you say that you updated to Yosemite and message does give you code to contact them, they will never ask for s/n only for that code. I did hovewer had many real Apple products registered on my id before.

If you start your conversation mentioning your machine model than that triggers model specific problem and they might ask s/n. Talk only yosemite and message.

 

Thank you luki1979!!

 

I don't understand why to state something, thats not true for sure :D. Probably on some cases it's true. Whatever Apple needs to take or ask to make sure you are not some cracker, etc, they will ask and do.

I just wrote, that they ask for serial number etc, also there are several post on various Hackintosh forums, which reveal the same, that Apple Support asks for serial number etc.  

 

My intention was to inform, that this method is working and what Apple support asked, so others can be well prepared for support call

 

I have called them several times myself, I only needed a serial once and all the other times they required a support token. 

Maybe it is related to your Apple ID which wasn't verified before (no Credit Card)? Anyway, it worked, that matters :D.

 

My Apple ID is fine. I have used AppStore to buy software/apps. 

 

Probably Apple is trying to protect users from being cracked/spied  trough iCloud or iMessage. I think, they shall implement for iMessage similar activation like they have for Keychain.

Share this post


Link to post
Share on other sites

I have called them several times myself, I only needed a serial once and all the other times they required a support token. 

Maybe it is related to your Apple ID which wasn't verified before (no Credit Card)? Anyway, it worked, that matters :D.

They never asked for a serial or customer code. I think my experience is in the vast minority. I had to push them to check the customer code. Then after some prompts, the rep was able to figure it out. As aforementioned, she has never heard of this problem, so your milage may vary. Just keep pushing that there is a problem with iMessage and the Messages app.

Share this post


Link to post
Share on other sites

They never asked for a serial or customer code. I think my experience is in the vast minority. I had to push them to check the customer code. Then after some prompts, the rep was able to figure it out. As aforementioned, she has never heard of this problem, so your milage may vary. Just keep pushing that there is a problem with iMessage and the Messages app.

 

I activated iMessage for another comp today.

 

Today they requested

 

First and Last Name

Apple ID
Computer Serial from About This Mac
iMessage Activation ID (from iMassage alert box)
 
They didn't sent verification code to iPhone this time, but support personnel mentioned, you had a issue couple of days ago. I explained, it's my second comp, which I upgraded too into Yosemite.
 
Just for case, I recommend to backup your Clover config file, if you replace HD etc, you can restore previous settings for iMessage, so there is no activation needed I guess.
 
Continuity calling is really call feature if enabled from FaceTime prefs. Really easy to place call directly from desktop trough you iPhone cellular network with comp headset!

Share this post


Link to post
Share on other sites

leodaniel, thank you so so so much. I followed all the steps, call apple and now I have iMessage working like in my macbook pro!. Really thank you. 

Share this post


Link to post
Share on other sites

I just did all this, called Apple, told them I wasn't physically near my computer and that my (now angry) wife can't login to Messages for Mac or FaceTime. No serialnumber needed. After I told them what to do and look for (rather unknown problem apparently), I gave them my customer / validation code annd they said my account would be "unlocked" again. So I tried and it threw the exact same code at me again. Calling them back now, trying to get it unlocked again... the advisor, who I had to tell what to do again, they unlocked it again but it still throws the same code. I'm currently on hold for a Senior Advisor...  Also, the FaceTime is doing the same now, throws that code too, unlike before where it'd just not work. To be continued.

 

Anyone else had this issue?

 

Edit: Waited in line for well over an hour... was told to boot into safemode and try again. So eh yeah. I told them I'd try later tonight but did it rightaway. Booted with an added -x boot argument, tried, still the same error. Now going to contact them... again...

 

Edit 2: Got back in contact with the guy. Apparently there's another case just like this where they had to boot the system in safemode, then "unlock" the account, reboot into normal mode and then try to login again. Still no luck on my end though. Highly doubt this is a Hackintosh problem though, this is Apple's BS imho. He's going to email me some sort of script or program that gathers logs from the computer to figure out what's going on. Which will be interesting to say the least xD

Share this post


Link to post
Share on other sites

I just did all this, called Apple, told them I wasn't physically near my computer and that my (now angry) wife can't login to Messages for Mac or FaceTime. No serialnumber needed. After I told them what to do and look for (rather unknown problem apparently), I gave them my customer / validation code annd they said my account would be "unlocked" again. So I tried and it threw the exact same code at me again. Calling them back now, trying to get it unlocked again... the advisor, who I had to tell what to do again, they unlocked it again but it still throws the same code. I'm currently on hold for a Senior Advisor...  Also, the FaceTime is doing the same now, throws that code too, unlike before where it'd just not work. To be continued.

 

Anyone else had this issue?

 

Edit: Waited in line for well over an hour... was told to boot into safemode and try again. So eh yeah. I told them I'd try later tonight but did it rightaway. Booted with an added -x boot argument, tried, still the same error. Now going to contact them... again...

 

Edit 2: Got back in contact with the guy. Apparently there's another case just like this where they had to boot the system in safemode, then "unlock" the account, reboot into normal mode and then try to login again. Still no luck on my end though. Highly doubt this is a Hackintosh problem though, this is Apple's BS imho. He's going to email me some sort of script or program that gathers logs from the computer to figure out what's going on. Which will be interesting to say the least xD

 

Hi C.44,

 

please make sure, that you have prepared you comp 100% properly! Use iMessageDebug tool to make sure that it's done properly.

 

Please note, Apple is trying to protect their customers from being hacked. New features of iMessage/FaceTime provide various functionality how to link your Mac with your iPhone or other iOS devices. You can now make cellular calls, send SMS etc directly from your Mac computer etc. There is a big risk, that someone can hijack your comp settings to spy after you (For example room mate on campus, angry spouse, colleagues at work etc. So, I believe that Apple is trying to protect everyones privacy.

Share this post


Link to post
Share on other sites

Hi Holyfield,

 

i followed the guide to the letter. Checked 3 times between power downs to make sure all hashes were identical between sessions (I used iMessageDebug), which they were. It was only then that I even tried to log in. Ever since I'm getting the Customer Code. Friend of mine has the exact same problem.

Share this post


Link to post
Share on other sites

Hi Holyfield,

 

i followed the guide to the letter. Checked 3 times between power downs to make sure all hashes were identical between sessions (I used iMessageDebug), which they were. It was only then that I even tried to log in. Ever since I'm getting the Customer Code. Friend of mine has the exact same problem.

 

Did you cleaned up all iMessage and FaceTime caches and junk? 

Share this post


Link to post
Share on other sites

Did you cleaned up all iMessage and FaceTime caches and junk? 

 

That I didn't do. Got some more information on which specific files and folders to trash?

Share this post


Link to post
Share on other sites

That I didn't do. Got some more information on which specific files and folders to trash?

 

 

Reset network configuration

 
Go to
  • /Library/Preferences/SystemConfiguration/
Trash these file
  • NetworkInterfaces.plist
  • preferences.plist 
Empty trashcan and reboot you comp
 
Clean iMessage cache etc
 
Switch on on Finder Show All Files (Terminal)
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
 
Open folder:
  • /StartupDrive/Users/username/Library/Caches
Trash all files which begin with the prefix:
  • Caches/com.apple.Messages
  • Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent
Open
  • /StartupDrive/Users/Username/Library/Preferences
Trash all files which begin with the prefix:
  • com.apple.iChat.
  • com.apple.imagent.
  • com.apple.imessage.
  • com.apple.imservice.
Also trash the folder
  • /StartupDrive/Users/Username/Library/Messages

Reboot, try to log into iMessage, you should have a new case ID.

 

Reset Finder

defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

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
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
    • By Masha24
      Hi guys, I've been lurking in the shadows for months trying to learn how to hackintosh this laptop.  Perhaps if anyone has the time, I could use some help getting it to install 
       
      Trying to install High Sierra on this Laptop:
       
      Lenovo Ideapad 110-171KB-80VK (2017)
      Intel Core i5 7200U
      Intel HD 620 Graphics
      Resolution: 1600x900
       
      Elan PS2 Track Pad - [ACPI\VEN_ETD&DEV_0675 - system device -PCI\VEN_8086&DEV_9D23&SUBSYS_383117AA&REV_21]
      Realtek Network    - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
      Realtech audio
       
      SATA Controller    - [PCI\VEN_8086&DEV_9D03&SUBSYS_382F17AA&REV_21]
      USB 3.0 XHC        - [PCI\VEN_808
       
      --- Using Clover *
      --- I'll attach it below.
       
      I can't quite get it to install, and i've been going in circles for months now ...
      I'll attach everything I have so far including, verbose pics, clover preboot, Clover folder, etc.
       
      Here are some photos of the verbose text leading up to the installer, if maybe there is something useful in here?
       

       
       
       
      And now photos of the installer
       
       
       

       
       

       
       
      Above is an image of the Installer log, (the main pop up window loads from about 10 mins and stops arbitrarily at 2 minutes left, every time) of the nearly hundred attempts i have made, this is the final screen i get, pretty much no matter what i do.
      Sometimes the the order of what it says is different , but the main things of interest are:
       
      "Target is not convertible to APFS: This volume is not formatted as Mac OS Extended journaled."
      "Warning: Couldn't find Board ID, Chip ID, & ECID in new namespace, falling back"
      "Unable to get fs for null"
      " NO native mechanism to verify Applediagnostics.chunklist"
      " NO native mechanism to verify Installfa.plist"
      " NO native mechanism to verify Basesystem.dmg"
      " NO native mechanism to verify AppleDiagnostics.dmg"
      " NO native mechanism to verify InstallESD.dmg"
      " NO native mechanism to verify Basesystem.chumklist"
       
      I have tried many many ... many .. different combinations of kexts, drivers, copies of clover, forks of clover - different copies of drivers and kexts from different sources.. including from all the official repositories.
       
      * I am not trying to install with APFS - the drive i am using is a spinning HDD - so i don't understand the first line quote above.
      * I am using a usb2 slot - there is only two on this machine - 1- usb2 and 1- usb3
      * As you'll see in the Clover folder i'm using APFSdriverloader. - so the installer should detect the installer-APFS-thing - and see it should be HFS+ ?? no?
       
      I'll detail the procedures:
       
      I wiped the Target HDD drive with a live linux USB.
      i prepair the USB with Createinstallmedia method, install clover to the EFI on usb, load kexts and drivers (I've been recently attempting with the Plist from a 'certain other site' Ton*****86) As it has the dvmt preallocation patch and other bits - i'm of course open to ANY other files/pLists .. this is just the one i've been experimenting with lately.)
      Add ' -v ' in clover options to see the verbose output
      in the installer (acts sketchy sorta, delayed and sluggish) i use DiskUtility to erase the drive 'Macos extended journaled'
      Make initial selections, agree to license and begin install.
      it proceeds to 2 minutes left every time, and hangs. many times i've left it for hours, and even overnight.
      I'm honestly not kidding, it's nearly 100 times ive' tried this, i've downloaded high sierra from the app store 5 times to rule out that, i've used countless combinations of everything .. i'm almost completely burned out.
       
       
      If anyone can shed some light i'll be VERY thankful!... I'm ready to go in a completely new direction...please please please help
       
      I'll put the Clover in the next post because i ran out of space in this one......
       
       
       
       
       
       
       
      Here is the latest clover i've been using, with the preboot, and DSDT/SSDT (F2 & F4) in it.
       
      CLOVER-Oct15.zip
       
      Thank you very much for ANY help you can provide
    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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 
       
       
       
      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






×