Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
:) One step closer to Beta.

Concept%2520MacPostFactor.png


- 32-bit method will be retained, similar to how MLPFv0.3 works. (For GMA 950 and 7300gt)
- 64-bit method will be included (For X1600, upgraded graphics on Mac Pro, this is based on Clover or Chameleon)
- All in one application process is similar to MLPFv0.3.
 
:) One step closer to Beta.

Image

- 32-bit method will be retained, similar to how MLPFv0.3 works. (For GMA 950 and 7300gt)
- 64-bit method will be included (For X1600, upgraded graphics on Mac Pro, this is based on Clover or Chameleon)
- All in one application process is similar to MLPFv0.3.

Will the 64bit method support updating as the Chameleon method does?
 
:) One step closer to Beta.

Image

- 32-bit method will be retained, similar to how MLPFv0.3 works. (For GMA 950 and 7300gt)
- 64-bit method will be included (For X1600, upgraded graphics on Mac Pro, this is based on Clover or Chameleon)
- All in one application process is similar to MLPFv0.3.

will be x3100, also?
thx
 
FANTASTIC! I can't wait since I wasn't able so far to install MV on my late '06 iMac... thx!!

- 32-bit method will be retained, similar to how MLPFv0.3 works. (For GMA 950 and 7300gt)
- 64-bit method will be included (For X1600, upgraded graphics on Mac Pro, this is based on Clover or Chameleon)
- All in one application process is similar to MLPFv0.3.[/QUOTE]
 
To those having an issue with iMessage, the issue is your Mac's serial that us checked by iMessage during registration, which is located in your nvram. The fix is actually pretty simple.

1. Open Terminal
2. Copy and paste this command

Code:
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=(6 randomdigits)

3. After the "=" in the command copy and paste your Mac's serial from System Profiler and add 6 random digits to the end of it then run the command.

@HackerWayne and @MLForAll it would be nice if you guys added that little command to MavericksPostFactor pretty please:)
 
So I have run into a problem helping a friends and have tried everything but always get a:

boot0: test
boot0: test
boot0: test
boot0: GPT
boot0: test
boot0: test
boot0: test
boot0: error

If the drive is formatted as a MBR then the first 4 lines don't show up, just:

boot0: test
boot0: test
boot0: test
boot0: error

He has a Mac Pro 1,1 with a 1TB Seagate HDD and a GTX260. The GTX260 works fine under Lion 10.7.5.

So far we have tried installing Chameleon using the package from Batman's guide, installing it using the Chameleon Wizard. We have tried with and without the mach_kernel and boot file from Batman's guide. We have tried using the method I used and have used many times and still the same thing. Tried Jabbawok's guide, same error. We can't get Chameleon to boot at all. Any suggestions on how to deal with the boot0 error?
 
To those having an issue with iMessage, the issue is your Mac's serial that us checked by iMessage during registration, which is located in your nvram. The fix is actually pretty simple.

1. Open Terminal
2. Copy and paste this command

Code:
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=(6 randomdigits)

3. After the "=" in the command copy and paste your Mac's serial from System Profiler and add 6 random digits to the end of it then run the command.

@HackerWayne and @MLForAll it would be nice if you guys added that little command to MavericksPostFactor pretty please:)

Does this method eschew the need for the FileNVRAM.dylib in the modules folder?

----------

So I have run into a problem helping a friends and have tried everything but always get a:

boot0: test
boot0: test
boot0: test
boot0: GPT
boot0: test
boot0: test
boot0: test
boot0: error

If the drive is formatted as a MBR then the first 4 lines don't show up, just:

boot0: test
boot0: test
boot0: test
boot0: error

He has a Mac Pro 1,1 with a 1TB Seagate HDD and a GTX260. The GTX260 works fine under Lion 10.7.5.

So far we have tried installing Chameleon using the package from Batman's guide, installing it using the Chameleon Wizard. We have tried with and without the mach_kernel and boot file from Batman's guide. We have tried using the method I used and have used many times and still the same thing. Tried Jabbawok's guide, same error. We can't get Chameleon to boot at all. Any suggestions on how to deal with the boot0 error?

What does bdmesg have to say? If unfamiliar with it you can use Chameleon Wizard to load up the most recent Chameleon boot log or run it in Terminal. It can be found in /usr/local/bin on your Chameleon install.
 
Does this method eschew the need for the FileNVRAM.dylib in the modules folder?

Yes, they do pretty much the same exact thing. I use this method because I, for one, have never been able to get Chameleon or Clover to work on my Macbook. This is the fix I am currently using on my Macbook right now (running Mountain Lion) and haven't had an issue since I ran it months ago when I first installed 10.8.3 using MLPostFactor
 
"No bootable device" insinuates that chameleon is not finding your mac kernel. You will need to find out the boot order of how chameleon is reading the drive the mac kernel/OS X system is located on (i.e. 0,1 0,2 1,2 etc) and adjust your org.chameleon.Boot.plist accordingly.

The much larger issue you will face is whether or not chameleon will load your unsupported graphic kexts. I have tried countless times (in vain) to get both Clover and Chameleon to load the ATI X1600 unsupported kexts and never once has either of these boot loaders accomplished this.

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.
 
NVIDIA GeForce 8800 GT

Does anyone know if the NVIDIA GeForce 8800 GT will work with Mavericks?

Thanks!
 
Does this method eschew the need for the FileNVRAM.dylib in the modules folder?

----------



What does bdmesg have to say? If unfamiliar with it you can use Chameleon Wizard to load up the most recent Chameleon boot log or run it in Terminal. It can be found in /usr/local/bin on your Chameleon install.

I'm the friend hennesie2000 was referring to. Tried opening bdmesg file with Wizard but keeps saying "boot-log property not found".

when opened in terminal i get "/Volumes/Startup\ Disk/usr/local/bin/bdmesg ; exit;
"boot-log" property not found.
logout
[Process completed]"
 
I'm the friend hennesie2000 was referring to. Tried opening bdmesg file with Wizard but keeps saying "boot-log property not found".

when opened in terminal i get "/Volumes/Startup\ Disk/usr/local/bin/bdmesg ; exit;
"boot-log" property not found.
logout
[Process completed]"

And this is from a fresh Chameleon install or one you actually tried to boot from? Anyway, sounds like you're running into the 4k sector problem. Google is your friend accomplice.
 
And this is from a fresh Chameleon install or one you actually tried to boot from? Anyway, sounds like you're running into the 4k sector problem. Google is your friend accomplice.

I've read a bit about the 4k sector problem. I'll read a bit more in depth.
 
And this is from a fresh Chameleon install or one you actually tried to boot from? Anyway, sounds like you're running into the 4k sector problem. Google is your friend accomplice.

Fresh install. Just tried sudo blessing Boot Drive and had default partition in the org.chameleon.boot.plist file set to my lion drive. still did not boot to chameleon
 
Fresh install. Just tried sudo blessing Boot Drive and had default partition in the org.chameleon.boot.plist file set to my lion drive. still did not boot to chameleon

If Chameleon won't load then the log won't be populated. What you'll have to end up doing is installing Chameleon manually using the Terminal and tweaking the sector size. Before you begin look up the model number for your Seagate drive to confirm that it is in fact set to 4k sector size.
 
If Chameleon won't load then the log won't be populated. What you'll have to end up doing is installing Chameleon manually using the Terminal and tweaking the sector size. Before you begin look up the model number for your Seagate drive to confirm that it is in fact set to 4k sector size.

Yes it is a 4k sector drive. http://www.newegg.com/Product/Product.aspx?Item=N82E16822148840 (I have the 1TB). Hennesie2000 also has a 4k drive. http://www.seagate.com/www-content/...s/desktop-sshd-data-sheet-ds1788-2-1308us.pdf he has the 1TB as well.

----------

http://www.tonymacx86.com/25-boot0-error-official-guide.html
what do you think of this? how would this work using chameleon installer

FYI.. lion hdd in bay1… boot/install/mavericks hdd in bay 2
 
Yes it is a 4k sector drive. http://www.newegg.com/Product/Product.aspx?Item=N82E16822148840 (I have the 1TB). Hennesie2000 also has a 4k drive. http://www.seagate.com/www-content/...s/desktop-sshd-data-sheet-ds1788-2-1308us.pdf he has the 1TB as well.

----------

http://www.tonymacx86.com/25-boot0-error-official-guide.html
what do you think of this? how would this work using chameleon installer

FYI.. lion hdd in bay1… boot/install/mavericks hdd in bay 2

Mine is a 4k drive but it is a SSHD so I wonder if the 8GB NAND is loading Chameleon and that is what is allowing it to work.
 
Yes it is a 4k sector drive. http://www.newegg.com/Product/Product.aspx?Item=N82E16822148840 (I have the 1TB). Hennesie2000 also has a 4k drive. http://www.seagate.com/www-content/...s/desktop-sshd-data-sheet-ds1788-2-1308us.pdf he has the 1TB as well.

----------

http://www.tonymacx86.com/25-boot0-error-official-guide.html
what do you think of this? how would this work using chameleon installer

FYI.. lion hdd in bay1… boot/install/mavericks hdd in bay 2

Ignore that guide and use this one instead. Modify step 9 with the code below and make sure you're pointing it at the correct disk. Be aware that some users have reported a bug in OS X's dd implementation and that they recommend using it while the drive is unmounted. Hennesie should be able to walk you through it.

Code:
sudo dd if=boot1h of=/dev/rdisk0s2 bs=4096
 
And this is from a fresh Chameleon install or one you actually tried to boot from? Anyway, sounds like you're running into the 4k sector problem. Google is your friend accomplice.

Yes it does. I was having the problem on my 2TB WD. In a nutshell:

1. You need to get a copy of the boo1h file from a MacOS installation. I am not sure if it has to be a MV install, but that is where I got it from. It is a tiny file, so I could zip it and mail it. PM me.

2. After you format your Cham partition (before you install Cham) make note of the device the partition is mounted on. For example /dev/disk0s2.

3. Unmount the device (Cham partition) with diskutil or Disk Utility. If you do not unmount the device, you will get an error.

4. Copy the boot1h:

sudo dd if=boot1h of=/dev/disk0s2

This command assumes the boot1h file is in the current working directory.

5. Remount the device.

6. Install Cham, do the mods, and bless.

EDIT: I did these steps from within Lion 10.7.5.
 
Last edited:
Yes it does. I was having the problem on my 2TB WD. In a nutshell:

1. You need to get a copy of the boo1h file from a MacOS installation. I am not sure if it has to be a MV install, but that is where I got it from. It is a tiny file, so I could zip it and mail it. PM me.

2. After you format your Cham partition (before you install Cham) make note of the device the partition is mounted on. For example /dev/disk0s2.

3. Unmount the device (Cham partition) with diskutil or Disk Utility. If you do not unmount the device, you will get an error.

4. Copy the boot1h:

sudo dd if=boot1h of=/dev/disk0s2

This command assumes the boot1h file is in the current working directory.

5. Install Cham, do the mods, and bless.

EDIT: I did these steps from within Lion 10.7.5.

What exactly do you mean by step 4?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.