All posts tagged osx

Install OS X El Capitan on Mac [Direct Download]

Although there is no official way to download OS X El Capitan from outside the Mac App Store [MAS], we have found a reliable workaround for those who are facing similar issues with the OS X upgrade.

Installing El Capitan

When you download OS X El Capitan using the Mac App Store, a raw package (.pkg) file is downloaded from the Apple server. This raw file is not installable on its own. While downloading the package, MAS processes and converts it into an executable (.app) file, which can then be installed on your Mac.

In this workaround, we’ll be downloading the raw package directly from the Apple server using a suitable download manager. This will accelerate the download speed, and reduce the risk of download error at the same time. We’ll then configure the system in such a way that the MAS downloads and installs the new version of OS X from the locally downloaded raw package, instead of the one available on the Apple server.

The end result is the same as you would get if you had downloaded OS X El Capitan directly from MAS. The only thing you have skipped here is the annoying download interruptions and slow download speeds.

Note: On Mac App Store, the estimated download time was around 15 hours on a 2 Mbps connection. Using a download manager like Folx, the setup package was downloaded within 5 hours on the same connection.

OS X El Capitan [Direct Download]

First, download the El Capitan package (.pkg) file from the Apple server using a suitable download manager.

El Capitan package URL: http://osxapps.itunes.apple.com/apple-assets-us-std-000001/Purple3/v4/74/d2/82/74d28291-9db9-7ae2-305d-9b8b3f5fd463/ftk3252456602304584541.pkg

#Update: Here, we have mentioned the URL of the package file for OS X 10.11. If the latest version of OS X El Capitan available on the Mac App Store is a different one, MAS will fetch it from a different location. Hence the workaround mentioned here will no longer work, unless you know the URL of the latest package file and create the directory structure on localhost based on the same.

Before downloading the package, ensure that it is the latest version of El Capitan released on the MAS. To find out the URL of the latest El Capitan package file, you can either check out the comments below or search on the Internet for it.

Once you have got the raw package (ftk3252456602304584541.pkg), you need to configure your Mac so that the MAS uses it as the source for downloading OS X El Capitan. For this, first you need to edit the hosts file and point the root domain of the download URL (osxapps.itunes.apple.com) to localhost (127.0.0.1). To modify the hosts file as required, follow the steps below:

#1 Open Terminal from the Launchpad or Applications list.

#2 Type “sudo nano /etc/hosts” and hit the return key. You’ll be asked for your password. Enter your admin password. The hosts file is now open in editable mode within the Terminal window.

#3 Add the following line to the end of the file: “127.0.0.1       osxapps.itunes.apple.com”.

Editing hosts file on Mac

#4 Press control + X (^X), then Y and hit return to save the file and return to Terminal prompt.

The root domain osxapps.itunes.apple.com has now been pointed to localhost IP of your computer.

Note: Sometimes, you might need to flush the DNS cache for the changes to take effect. To flush DNS cache, type “sudo killall -HUP mDNSResponder” in the command line and hit return.

Next, you need to replicate the path of the source package on your computer in the same way as it is represented in the original URL. Only then, will MAS be able to download the package from localhost server.

To replicate the original download URL on localhost, you need to create the same directory structure on your computer within a particular folder, and then assign that folder as the root of the localhost server.

Note: OS X comes preinstalled with Python, which natively includes a SimpleHTTPServer by default. This server can turn any directory on your Mac into a web server directory (on localhost).

In this example, we will create a folder named “osxapps_local” on Desktop, and replicate the directory structure of the package URL under it. Follow the steps below to create the directory structure and then host “osxapps_local” as the root directory on localhost.

#1 Open Terminal from the Launchpad or Applications list.

#2 Type “cd Desktop” on the command line and hit return to enter the Desktop folder.

#3 Type “mkdir osxapps_local” and hit return to create the root directory of the same name on Desktop.

#4 Go to the newly created folder by typing “cd osxapps_local” and hitting return.

#5 To create the relative path inside the root folder, enter the following command: “sudo mkdir -p ./apple-assets-us-std-000001/Purple3/v4/74/d2/82/74d28291-9db9-7ae2-305d-9b8b3f5fd463/”. Provide the admin password when prompted.

#6 Copy the source package (ftk3252456602304584541.pkg) file you have downloaded earlier and paste it in the last folder of the directory tree created within the root folder. Click on Authenticate when prompted, and provide the system admin password.

#7 The Terminal prompt should be pointed to the root directory inside Desktop. Now, you need to host this folder on localhost. In order to do that, execute the following command in the Terminal prompt: “sudo python -m SimpleHTTPServer 80”. Provide the admin password and click on Allow in the subsequent message prompt. This will start the localhost server in the Terminal window. Do not close the terminal window till the process is over.

Start SimpleHTTPServer on Mac

To check the status of the local server setup, enter the URL of the original package in your browser and check the download speed. It should be very high as it is downloading from the localhost server.

El Capitan Direct Download at High Speed

Now, launch the Mac App Store and install OS X El Capitan in the usual way. MAS will now download it from the local server at a high speed. Once downloaded, you may proceed with the installation by clicking on Continue when the setup launches.

Note: During the installation process, your Mac may request resources from the “osxapps.itunes.apple.com” domain. Thus, it is recommended to remove the entry from the hosts file before proceeding with the installation.

Is this method Genuine?

You might be wondering if this workaround to install OS X El Capitan is genuine enough. And to answer the question, it’s as genuine as the official method. Here, you’re downloading the same raw package that Mac App Store requests when it downloads OS X El Capitan. And you’re using MAS to convert the raw package into the executable app file. The only thing that changes here is the location of the raw file that Mac App Store downloads from (localhost instead of Apple server).

As for the build number, it is the latest version of El Capitan that was publicly released on September 30. Mac App Store downloads the update from a specific URL, and there is only one directory structure (with only one file in it) that you have replicated on the localhost server. If Mac App Store’s target URL did not match the relative path on localhost, it would not be able to download the package from localhost. After El Capitan has been installed, you may verify its build number (15A284) by clicking on “About This Mac” from the Apple Menu.

Additionally, we are also providing the MD5 and SHA1 hash values for the original disk image file (InstallESD.dmg) found within the processed OS X El Capitan app package. If you wish to download the raw package (ftk3252456602304584541.pkg) from alternate sources, such as torrents, you can verify the authenticity of the file using its MD5 or SHA1 (also provided below).

El Capitan (15A284) hash/md5

InstallESD.dmg

SHA1: 5e21097f2e98417ecc12574a7bb46a402594ea4a
MD5: d54b388282228df41f40e95649e8bc32

ftk3252456602304584541.pkg

SHA1: 8ff3e26ec16aece573b3cea680b0df67f85ccd8a
MD5: f46f412a5a74b0122ac1a317d604758a

El Capitan – Single Download Multiple Installations

If you or any of your trusted peers have already downloaded the raw package on any other device, you can simply copy the file to your own Mac and upgrade to El Capitan using the above method. Moreover, if you have multiple Macs registered with the same Apple ID, you can directly use the processed app package created by Mac App Store on a single device, to install El Capitan on other devices.

Once MAS has finished downloading the setup, just go to the Applications folder and keep a backup of the “Install OS X El Capitan.app” file. To install El Capitan on other Macs registered with the same Apple ID, copy the file to the Applications folder of that computer and double click it to run the setup. You may also create a bootable USB installer for OS X El Capitan from the installer app package.

Direct link for 10.11.5

for MacOS 10.11.5, there is a secondary file (.pfpkg) needed.

http://osxapps.itunes.apple.co…

http://osxapps.itunes.apple.co…

There are now 2 files for the OS, you will need to create 2 separate folder for both the files.

 

So, now that you know how to get the direct link, from now on, you can  generate the direct links for all the future releases.

 

Do you find this workaround useful? Let us know of your opinion in the comments below.

 

 

1. When you to open “android-ndk-r10c-darwin-x86_64.bin” with “Archive Utility.app” or other app.
2. Then you’ve got “android-ndk-r10c-darwin-x86_64.bin.cpgz”, OH! Crap it’s not extract but archive .bin to .cpgz extension.
Warning!! extracted file take more disk space up to 3.55 GB on disk
[Solution 1] recommended!!
1. open Terminal then type “chmod +x [path]/android-ndk-r10c-darwin-x86_64.bin” and press “Enter”, after that type only “[path]/android-ndk-r10c-darwin-x86_64.bin” and press “Enter” as below image.

After that Terminal was extract with 7-Zip SFX, as below detail.
7-Zip SFX 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
p7zip Version 9.20 (locale=utf8,Utf16=on,HugeFiles=on,4 CPUs)
Processing archive: /Users/dtkad/Downloads/android-ndk-r10c-darwin-x86_64.bin
2. just wait process until Terminal show “Everything is Ok”

[Solution 2]

1. It’s too easy just rename by remove “.bin” if your non-extension file can be execute.
“android-ndk-r10c-darwin-x86_64.bin”
to
“android-ndk-r10c-darwin-x86_64”
you should see it’s as execute file, check it by right-click and choose “Get Info”, you will see detail like below image.
2. double click on “android-ndk-r10c-darwin-x86_64” execute file or open with “Archive Utility.app”,  so if you not see “Archive Utility.app” in both Launchpad and Application folder, it should be here “/System/Library/CoreServices” like below image.
then the Terminal was run and execute file will do extract process, leave it run until it’s show message as below.

 

Everything is Ok
logout
[Process completed]
 
3. Let’s see your extracted folder “android-ndk-r10c”, it’s contain in “Users” by default, for example my users is “poraweeraksasin” from step 2. name on bar, see below image.

This Guide is full walkthrough to how you can Dual Boot your Mac OSX El Capitan and Windows 10 on Hackintosh is very Simpler and Easier .

Using Single HDD / Hard-Drive  it is not difficult and it requires no experience and all basic installation steps are mentioned in this Guide

I assumes you have installed Mac OSX El Capitan on your Hard-Drive but if you haven’t installed it then Please follow below Guide and do installation First ::

1.At least 8 GB USB Drive

2. Windows 10 ISO Image

3. Latest revision of Rufus Download Here 

3. Latest revision of EasyUEFI Download Here

Making or Preparing for Windows10 USB installer 

Step 1: Now Run RuFus app and make sure your USB is Selected or Select it and Select Windows10 ISO Image as in ScreenShots Below ::

Rufus Installation

Step 2 : When Process Complete , Reboot your PC and Boot With USB Drive we prepared .

 Install MicroSoft Windows 10

Step 1 : Now Click on Install Now

Dual Boot Windows1 and OSX El Capitan

Step 2 :Choose your Language /Time/KeyBoard Setting and Click Next

Dual Boot Windows1 and OSX El Capitan 1

Step 3 : Select Custom Install and Look for Unallocated Partition , Choose and Click next , windows will prompt you “this will Create System Partitions ” .

Dual Boot Windows1 and OSX El Capitan 2

Step 4 : Now there will be Partions are as follow :

1.EFI Partition ( 200 MB)

2.OSX Partition (100 GB or more than what space you provided it )

3.MicroSoft Reserved Partition (620 MB)

4. Now Left Partition (320 GB ) Select it and Click Next and wait Untill Installation Complete

Dual Boot Windows1 and OSX El Capitan 3

 

Dual Boot Setting for OSX El Capitan and Windows10 

Now you have Windows But you are not able to Boot to OSX El Capitan due to Missing Boot Entry , now we gonna Fix This ::

Step 1: Run EasyUEFI   and See which Boot Entries are available , now we gonna add Missing Entry for OSX Bootloader ( Clover Bootloader ).

Disk0 is usually the internal Hard Drive / SSD. In the Boot order section, we can see that only Windows Boot Manager is detected. There is no mention of Clover UEFI anywhere.

EasyUEFI Setting

Step 2: To solve this problem, click on the Add button (the second button you see on the right).

EasyUEFI Settings 2

Step 3: Now Change Type fromWindows BootManager to Linux or Other OS , Type Name in Description Box (Whatever you want Clover Bootloader or Mac OSX Bootloader or Else depends upon you),  and Click Browse Button

EasyUEFI Settings 3

Step 4:  Now Expand EFI => BOOT or CLOVER Folder , Select any of Bootx64.efi or Cloverx64.efi  , Both are Clover Bootloader files Choose one or add Entry for Both but one is Enough to Boot Clover then why you waste your time but if you having Issue with and Then Use Another Option.

EasyUEFI Settings 4

Note : Remember these things :

1.Bootx64.efi is Bootloader file (this file is from Clover Bootloader )

2.Bootmgfw.efi is Windows Bootloader

3.Cloverx64.efi is Clover Bootloader

initially when we Click on drive to Boot it loads Bootx64.efi First then Required Files to Boot to OS (Operating System) . Every OS Contains it Bootx64.efi , Windows and Linux too . above Bootx64.efi is from CloverBootloader but anyhow your file is got Replaced with particular OS then Bootx64.efi will load that OS only .Clover is capable of running any OS.

But Don’t Worry use Above Bootloader Files to Boot to OS what you want .

Now Everything is done and you have Successfully added Boot Entry for OSX El Capitan in BIOS , Just Select This Entry and Boot to OS you want .

You will See Boot Menu Like This :-

Asus UEFI BootMenu

Also You can Set you OS’s Priority . you will see like This :-

Asus UEFI BIOS

Additional Workarounds :

These Following Steps i used to Format my Single HDD to Dual Boot in Mac OSX DiskUtility .

OSX El Capitan DiskUtility is not providing option to set you HDD as Free Space (as we were have in Yosemite or before OSX Version)

i have HDD (500 GB ) 250 GB for OSX El Capitan  and 250 GB for Windows 10 .

if you set you HDD first 250GB as Mac OSX and Second 250 GB as FAT32 or ExFat , This Way OSX WIll make Format your HDD as Hybrid GPT , there’s only way to Format you HDD as OSX Journaled to get Full GPT Drive .

Window 10 Can’t be Install on HyBrid GPT Drive you will Receive this Error Continously :-

Windows Error

Solution to This Error :-  

1 :  I Used Mac OSX Yosemite USB installer and Fomatted My HDD as

First 250GB for OSX  formatted as OSX Journaled and Left 250 GB as Free Space .

Free Space will be as Unallocated Space in Window10 Installation Disk Management

2 : You Can use GptFDisk to Convert your Hybrid GPT Drive into Pure or Full GPT then Windows Installation Can Proceed .

Pure/Full GPT Disk will look like :-

GPT FDISK

Above Screenshot is from Gdisk you can use Partition Manager Softwares on Windows as well as OSX to Determine Drive is Full GPT or Hybrid GPT .

Note : In My Case i was not able to Convert Hybrid GPT Disk using GDisk , receiving too many error then i used solution 1 , which is much Easier .

Things to be Remember Always Before Dual Boot:-

1. Always Install Install OSX First on HDD , Don’t try to Install Windows First .

2.EFI Partition is Required for UEFI Bios System , if EFI is not Present then it not Booting UEFI is using Legacy Boot.

3.Disable Secured or Set it to Other OS in Bios Menu , otherwise you won’t able to Boot from any OS then Windows .

Never try to Install Windows First Because Windows always make first partition as OEM (100MB), Second EFI (100 MB) and Third MSR (620 MB ).

OSX always Requires EFI to be First Partition and of (200 MB) at least of Size , otherwise you will Receive this Error Continuosly . Error will look like this :-

MEDiaKit reports partition (map) too small - Error

PS: This Guide is not only for Dual Booting With OSX El Capitan with Windows10 , you can Dual Boot any Version of OSX and Windows (UEFI Support ) on Single Hard Drive using This Method .

Well, keeping it short. Couldn’t find all clover’s boot args, so here goes the list:

At this section you can add “Boot Flags” and “Kernel Flags” to be used by the system…
Here we will list only Clover’s proprietary “Boot Flags”, different flags, like for example,npci=0x2000, npci=0x3000, darkwake=0, etc…, should work as expected…
Flag Action
WithKexts Boot OS X loading System Kexts and ignoring kernelcache.
-v Verbose Boot.
-s Boot OS X into Single User Mode.
-x Boot OS X into SafeBoot (Safe Mode).
MountEFI=yes/diskX Mount EFI partition at every boot or from disk X (X = disk number).
LogLineCount=0 Set maximum number of lines for log file, default 0 (no Limit).
LogLocation=PATH Set the path for the log files to be saved.
LogEveryBoot=Yes/No Save log files at every boot.

 

Here’s a completish guide though:

https://clover-wiki.zetam.org/Configuration#boot-args

Everything about clover can be found here:

https://github.com/JrCs/Clover-Wiki/wiki

Will be adding more with time.

Cheers!

Enable facetime or imessage in hackintosh is pretty straight forward. All you need is 5 minutes of your time! And yeah follow this guide. 🙂

Hello! Before I begin I just want to credit /u/johnnyfortune for their write-up here. Their instructions were mostly correct for me, but I had to add a few extra steps that I believe others will need to include as well. This may only apply to those that have never used iMessage on their machine in the past.

As for the instructions:

  1. Open CloverConfigurator and mount your EFI
  2. Open your config.plist
  3. In the Rt Variables section, make sure everything is clear.
  4. Go to the SMBIOS section and click on the magic wand. Match the specs options as best you can to your machine. On the two sections that say shake, click a few times to generate a random serial. Click ok.
  5. Go to https://selfsolve.apple.com/ and search for that serial number that was generated. If you get an error message, that is good. It means you aren’t using a serial number assigned to a real Mac. If you don’t get an error, repeat step 4 and search for the new serial instead.
  6. Open terminal and run “uuidgen”.
  7. Copy this UUID and paste it in the “SmUUID” field in the SMBIOS section.
  8. In the “Board Serial Number” field, paste in your system serial number (the one generated by the magic wand) and add 5 random letters and numbers to the end to reach a total of 17 characters.The reason for step 7 and 8 is to keep your ROM (last 12 digits of the UUID that was generated) and MLB (Board Serial Number) values constant and unique on each boot of the OS. If the values change from boot to boot, iMessage will notice and fail to activate and there is potential that Apple will notice and blacklist your UUID, serial, or Apple ID. All Clover-generated ROM and MLB values are automatically blacklisted, as well.
  9. Export config.plist
  10. In terminal, run the commands:
    1. defaults write com.apple.finder AppleShowAllFiles TRUE
    2. killall Finder
  11. Navigate to /Users/[Username]/Library/Chaches and delete all files or folders beginning with: (if there is nothing there with these file names, that is ok)
    1. com.apple.Messages
    2. com.apple.imfoundation.IMRemoteURLConnectionAgent
  12. Navigate to /Users/[Username]/Library/Preferences and delete all files or folders beginning with: (if there is nothing there with these file names, that is ok)
    1. com.apple.iChat.
    2. com.apple.imagent.
    3. com.apple.imessage.
    4. com.apple.imservice.
  13. Navigate to /Users/[Username]/Library and delete the folder “Messages”(if there is nothing there with that file name, that is ok).
  14. Empty the trash. If it says files are still in use, reboot and empty it immediately upon startup.
  15. Open up Disk Utility, select your OSX partition, and rebuild the permissions. Reboot when this is completed.
  16. The moment of truth: open up iMessage and attempt to sign in. It worked for me on the first try.
  17. If it worked, you can re-hide hidden files and folders with the terminal commands:
    1. defaults write com.apple.finder AppleShowAllFiles FALSE
    2. killall Finder

Feel free to ask me any questions! I hope this is helpful.

Edit: As some users have pointed out, your primary network must be set as en0. You can check this by opening up System Profiler, clicking on either Ethernet or Wifi and making sure that your internet network is listed as en0. If it is not, reset your network preferences by going to /Library/Preferences/SystemConfiguration and deleting “NetworkInterfaces.plist” and “preferences.plist”.

 

The more updated guide will be there at: