Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

[Guide] Installing 10.9 Mavericks on older Macs. -HackerWayne

Hennesie2000 said:
What exactly do you mean by step 4?
Click to expand...

The command assumes that the file it's being told to copy is in the directory it is being invoked from. In the Terminal you need to change directory to the folder the boot1h file resides in. The easiest method is to type 'cd' with a space afterwards and drag the folder that the boot file is in to the Terminal window. Hit enter and you're good to go. Use an ls command to verify that the boot1h file is present.
 
Treksdot said:
The command assumes that the file it's being told to copy is in the directory it is being invoked from. In the Terminal you need to change directory to the folder the boot1h file resides in. The easiest method is to type 'cd' with a space afterwards and drag the folder that the boot file is in to the Terminal window. Hit enter and you're good to go. Use an ls command to verify that the boot1h file is present.
Click to expand...

So.....people are hacking their Macs in Terminal (performing shell commands) and they don't know what "cwd" is?

EDIT: Also the command does not assume anything. The command requires a full path name to the input file. My example assumes that the file is in the current working directory. (For those not in the know -- Google).
 
Last edited:
Treksdot said:
If it was easy they wouldn't need guides or prefer GUI over CLI. Also yes.
Click to expand...

I hear you. No one said it was easy. There are some basics for screwing around in the shell (Terminal) if you want to forge ahead. Otherwise.....wait for the GUI.
 
wwanthony said:
I hear you. No one said it was easy. There are some basics for screwing around in the shell (Terminal) if you want to forge ahead. Otherwise.....wait for the GUI.
Click to expand...

But that's the rub isn't it? They're in the Terminal because the GUI method isn't working and, by the looks of it, won't be working for a good while. I will add that it makes me giggle how Apple hides a users library folder from them but still leaves the Terminal readily accessible.
 
Treksdot said:
But that's the rub isn't it? They're in the Terminal because the GUI method isn't working and, by the looks of it, won't be working for a good while. I will add that it makes me giggle how Apple hides a users library folder from them but still leaves the Terminal readily accessible.
Click to expand...

I will make one more comment.

It is not an Apple thing. There is a lower level interface to every modern OS that has a GUI. It is there for those that seek it out.
 
RV-ABZ said:
Don't want blow your candle guys, but don't confused: the way I read this, GMA950 is just for 32bit ML; it looks like this new app is a combination of both MLPF (i.e. same as before) + the elusive MVPF (i.e. mostly for X1600-based Macs) -> "all in one application process similar to MLPF v0.3"

I still can't imagine any change for Mavericks as far as Intel GMA or older nVidia chips are concerned: no support for GMA950/nVidia 7300 (Wayne saying 32bit retained for those means "MLPF" to me) and buggy X3100 if beta 64bit X3100 kexts are included (i.e. you'll quickly abandon Mavericks on that graphics chip). These chips can't be supported without a 32bit kernel and that does not exist for Mavericks.

If Chameleon method has been integrated for full 64bit & Vanilla installation, that's great, although nothing new as such. At least the app should greatly simplify the process.
Click to expand...

You're confused. What we're attempting to do is 32-bit kernel of Mavericks.
 
128keaton said:
It has ML on it, using ML post factor. The OS X drive, according to OS X, was 0,2. I put in hd(0,2) in the <string> and it never liked it.
Click to expand...

I am afraid I misunderstood your original post. MLPF utilizes the modified boot.efi files and therefore an alternative boot loader cannot and should not be used. You should back up your files, erase/zero out your internal hard drive and reinstall ML using MLPF from scratch.
 
yes - thanks to hennesie2000, wwanthony, and treksdot for the assistance. 10.9 is now up and running! i have a bit of configuring to do, but most seems well.
 
gpatpandp said:
Firstly, I must preface this warning with the old adage "Your Mileage May Vary". I felt it important however to relate some very disconcerting results when testing the stability of a successfully installed system that includes both Mavericks and Chameleon, both installed on HFS+/GUID partitions on the same hard drive.

iMessage becomes troublesome when doing so. When switching back to my two (2) hard drive system set-up (i.e. Mavericks and Boot/Installer each on there own separate hard drives), iMessages works perfectly like it always did.

The most significant aspect that I found however is that a deep system cache clean using Mavericks Cache Cleaner completely BRICKS the entire drive/system. Ironically, the Mavericks OS X system will still boot with the old "Windows" BOOT drive created/used in the original set-up. The unusable/unstable part is the BOOT partition created on a HFS+/GUID partition. Once the caches are cleaned, it immediately destroys the partition and it will not/never boot again. So unless your really cramped for space where it becomes absolutely necessary to do so, I would advise against using this method as it is NO WHERE NEAR AS STABLE as the traditional method with installing your BOOT drive separately from your OS X System.

Jabbawoks method maybe old, but the most brilliant aspect of it is that it is damn near infallible and solid as a rock. Besides, I always live by the motto that "If it ain't broke...don't fix it".
Click to expand...

Other findings/limitations when utilizing a Mavericks and Chameleon, both installed on HFS+/GUID partitions on the same hard drive set-up. Any deviation to the original partition map (adding or subtracting a partition via terminal) breaks the system completely. Also, one better hope that nothing ever goes wrong with the original Chameleon BOOT partition specifically. It is impossible to recover it or reinstall Chameleon and re-bless/re-enable it to boot a pre existing Mavericks OS X system that has already been installed on the same hard drive. In other words, if within this set-up your BOOT partition ever fails, the ONLY way to fix it is to scrap the entire hard drive including your Mavericks OS X System and your Installer and re partition it/start all over again.
 
Last edited:
One more thing to share.

For those that want to run 10.9 and Chameleon on a Raid 0 setup I got it to work.

I formatted one of my 2TB drives with two partitions - 1G and 1.99 TB. I formatted the other drive with a single 2 TB partition. I used the two large partitions to create the Raid and installed Chameleon on the 1G partition (non-Raid 0). I then cloned my Mavericks install to the Raid partition using CCC. I have discovered that the Mavericks installer will not work on a Raid 0 (probably because it requires creation of a recovery partition --- just a guess).
 
So can I just confirm that if this works I will be able to use Mavericks on my MacBook Air 1.6GHz intel Core 2 Duo? (1st Gen Air)
 
gpatpandp said:
Other findings/limitations when utilizing a Mavericks and Chameleon, both installed on HFS+/GUID partitions on the same hard drive set-up. Any deviation to the original partition map (adding or subtracting a partition via terminal) breaks the system completely. Also, one better hope that nothing ever goes wrong with the original Chameleon BOOT partition specifically. It is impossible to recover it or reinstall Chameleon and re-bless/re-enable it to boot a pre existing Mavericks OS X system that has already been installed on the same hard drive. In other words, if within this set-up your BOOT partition ever fails, the ONLY way to fix it is to scrap the entire hard drive including your Mavericks OS X System and your Installer and re partition it/start all over again.
Click to expand...

If you choose to add a partition it will tell you no bootable device on restart. Simply boot into your old Lion install or boot to Mavericks using another chameleon install and reinstall Chameleon onto the boot partition. If you use your lion install you will have to re-bless the Chameleon partition and put it back into legacy mode. If you use another chameleon partition to boot you do not need bless it again. Just shutdown and remove the temp chameleon install. When you boot back up everything will be normal again and you will have your added partition all on one drive.

I just did this starting with a fresh Mavericks install. Had 3 partitions boot/installer/OS X. Split the OS X partition in two using disk utility. Then fixed it using my normal drive that has chameleon/OS X/windows. Could have used my Lion install too.

Please fully test your claims before posting. It took me less than 5 mins to fix it. No disrespect meant.
 
Last edited:
Hennesie2000 said:
If you choose to add a partition it will tell you no bootable device on restart. Simply boot into your old Lion install or boot to Mavericks using another chameleon install and reinstall Chameleon onto the boot partition. If you use your lion install you will have to re-bless the Chameleon partition and put it back into legacy mode. If you use another chameleon partition to boot you do not need bless it again. Just shutdown and remove the temp chameleon install. When you boot back up everything will be normal again and you will have your added partition all on one drive.

I just did this starting with a fresh Mavericks install. Had 3 partitions boot/installer/OS X. Split the OS X partition in two using disk utility. Then fixed it using my normal drive that has chameleon/OS X/windows. Could have used my Lion install too.

Please fully test your claims before posting. It took me less than 5 mins to fix it. No disrespect meant.
Click to expand...

I tested it extensively before reporting my findings. I believe it a certainty at this juncture that will you immediately rush to defend this shoddy sloppy concept and present something/anything to the contrary that exposes it for being what it is. Make no mistake that this "bright" idea of yours is nothing more then gimmick not to be trusted nor relied upon by anyone preferring/requiring a hassle free OS X Mavericks system on their unsupported Mac Pro. No disrespect intended.
 
gpatpandp said:
I tested it extensively before reported my findings. I believe it a certainty at this juncture that will you immediately rush to defend this shoddy sloppy concept and present something/anything to the contrary that exposes it for being what it is. Make no mistake that this "bright" idea of yours is nothing more then gimmick not to be trusted nor relied upon by anyone preferring/requiring a hassle free OS X Mavericks system on their unsupported Mac Pro. No disrespect intended.
Click to expand...

Do you want videos? I have provided screen shots and other proof. You have never provided anything but your word. Others have asked you questions about your previous finding... You never answered them.

All I did to your "irreparable" "bricked" setup was reinstall Chameleon.

You have done a good job finding issues and there will always be issues. However you can't be upset when a simple fix is found. I did not rush to dispute your claim. I took the time to replicate it and then fix it.
 
Last edited:
Hennesie2000 said:
Do you want videos? I have provided screen shots and other proof. You have never provided anything but your word.
Click to expand...

Nah...you can save the video for your Nobel Prize in Physics application for proving to the world that Chameleon can boot from a HFS+/GUID partition.
 
gpatpandp said:
Not quite the cure for cancer...ah but what the heck "All hail the King" !
Click to expand...

Is this how you react when a mechanic fixes something that you were unable to fix on your car?

All I did was provide a solution to a problem that you deemed catastrophic. There is nothing stopping your chameleon install on a second disk from becoming corrupt and having to do the exact same thing. Being able to run Chameleon from the same drive as the OS is something that others have wanted to do, not just me. Since the thread really is all about experimenting to get Mavericks on older Macs we tested it out and found out it is possible. Again, you have brought up some issues and while you say they are irreparable, a fix has been provided. You don't seem to like that, oh well.
 
gpatpandp said:
I am afraid I misunderstood your original post. MLPF utilizes the modified boot.efi files and therefore an alternative boot loader cannot and should not be used. You should back up your files, erase/zero out your internal hard drive and reinstall ML using MLPF from scratch.
Click to expand...

I thought MLPF used Chameleon, but I guess I am wrong. Anyway, I would wipe it, but I would like to boot Chameleon first into the Mavericks installer, then wipe it.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back