/Install OS X Mavericks.app/Contents/PlugIns/IA.bundle/Contents/MacOS/IA on the flash drive with the file Jazzzny attached in his most recent post. Then, boot from the USB drive, try to install Mavericks and let us know what happens.
You can use the Carbon Copy Cloner application. Ignore the warnings about not being able to create bootable copies of macOS Catalina and older, creating the basic install media still works fine.
Yes, as a Mavericks user I use this all the time. This isn't that—among other things, I'm not recieving a two factor code. App passwords are only for (and only work with) third party apps, never Apple software.
It's turned off.
Are you sure about this? My understanding is that only the individuals who have the app in the "purchased items" can download Mavericks. I am pretty sure the machines shipped with Mavericks and have internet recovery can't download Mavericks, but Yosemite form the servers.
Well, there is your link:
Someone can see if this works.sudo nano /etc/hosts
- Launch Terminal on your Mac from Launchpad or Applications list.
- Type in the following command:
- Provide the System Password (if required). The hosts file is now open in editable mode within the Terminal window. Append the following line to the end of the file: “127.0.0.1 osxapps.itunes.apple.com”. Press control + X (^X), then Y and hit return to save the file and return to Terminal prompt. Now, whenever any request is generated from your computer to the root domain (osxapps.itunes.apple.com), it will point to your localhost.
Note:
Sometimes, you might need to flush the DNS cache for the changes to take effect. To flush DNS cache, type the following in the command line and hit return:
sudo killall -HUP mDNSResponder
cd Desktop
- Place the downloaded packages (.pkg and .pfpkg files) in a certain relative path (directory structure) on your Mac, as indicated by the structure of their respective download URLs. In this example, we will create a folder named “macos_local” on Desktop, and replicate the directory structure of the two package URLs under the same. Once the relative path has been created, we’ll configure the localhost server to point to the macos_local directory on Desktop and run it. Follow the steps below to achieve the same:
mkdir macos_local
cd macos_local
sudo mkdir -p ./apple-assets-us-std-000001/Purple69/v4/a6/b2/66/a6b26643-7d56-d42f-1b0f-e605e094c8fa/
Password:
sudo mkdir -p ./apple-assets-us-std-000001/Purple49/v4/a5/ef/b4/a5efb468-7f48-1395-d8e4-2194ba4d688a/
sudo python -m http.server 80
Password:
Serving HTTP on :: port 80 (http://[::]:80/) ...
~/Desktop/macos_local/apple-assets-us-std-000001/Purple69/v4/a6/b2/66/a6b26643-7d56-d42f-1b0f-e605e094c8fa
- Copy the raw files from the MAS with Jdownloader or another download manager:
- pfpkg in the folder:
curl -L -o "~/Desktop/macos_local/apple-assets-us-std-000001/Purple69/v4/a6/b2/66/a6b26643-7d56-d42f-1b0f-e605e094c8fa/encrypted1094904501970168333.pfpkg" "http://osxapps.itunes.apple.com/app...05e094c8fa/encrypted1094904501970168333.pfpkg"
- Or with Curl:
~/Desktop/macos_local/apple-assets-us-std-000001/Purple49/v4/a5/ef/b4/a5efb468-7f48-1395-d8e4-2194ba4d688a
- And the pkg file in the folder:
Or with Curl:
curl -L -o "~/Desktop/macos_local/apple-assets-us-std-000001/Purple49/v4/a5/ef/b4/a5efb468-7f48-1395-d8e4-2194ba4d688a/encrypted5063122388219779779.pkg" "http://osxapps.itunes.apple.com/app...2194ba4d688a/encrypted5063122388219779779.pkg"
- Open the macOS Mavericks MAS link:
On a macmini3,1 I was able to download and install, by logging to that screen. From my research there are 2 requirements from recovery: supported machine and Mavericks in the "purchased apps". To download from MAS you only need the "purchased apps" condition.
Yes, I am sure. I came to this conclusion by putting the binary responsible for the installer into a disassembler and proxying/inspecting all internet traffic that came out of the Internet Recovery environment.
That may be true, but without logging in you can’t proceed forward. After logging in there is a hardware check performed by the installer. So with the patched binary any machine can download the full installer from recovery?
github.com
/usr/bin/shasum -a 256 InstallMacOSX.dmg along with the patch level (i.e. 10.9.5) for it? There are lots of places from which to download installers but verifying the validity is really the ultimate goal.
There are at least 2 versions of the installer. Back in 2013 the installer shipped with the DMG packed correctly and you could use creatinstallmedia to create a USB installer. At some point Apple started packing all legacy installer DMG's downloaded directly from the MAS inside packages. These
InstallMacOSX.dmg's can't be used directly without some manipulation. See here for more details:
forums.macrumors.com
If we get far enough, we can eventually feed the server whatever hardware identifiers we want, we just need someone with the right hardware to share the correct strings. Ideally this should be someone with a semi-broken computer they aren't going to use, because there is some chance that Apple will ban the identifier—but I honestly don't think they're going to bother, all the evidence suggests they simply don't care about this at all.
Wait. What?!