Jump to content

Chameleon Wizard - Utility for Chameleon.


janek202
 Share

681 posts in this topic

Recommended Posts

Hi all. I made a new utility for Chameleon. It helps to install, update and download latest revs of this bootloader.

 

Wow! Great tool. I haven't used it yet, but if it works its a God send. I'm tired of Terminal snobs telling me to compile a binary if all I want is an updated boot file.

 

Beautiful... just beautiful.

Link to comment
Share on other sites

Wow! Great tool. I haven't used it yet, but if it works its a God send. I'm tired of Terminal snobs telling me to compile a binary if all I want is an updated boot file.

 

Beautiful... just beautiful.

 

I feel more comfortable with Terminal actually. But this is a time saver if I need to take care of something and I'm in a hurry to update. :)

Link to comment
Share on other sites

Thanks janek, I don't know what you did but it updated Chameleon successfully. :(

 

BTW, should I update boot1h too?

 

No idea about that - however, I just installed the latest version via the Wizard (since I was quite a few versions back - all the way to 874!). Update to r1005 was successful.

Link to comment
Share on other sites

Is there a need to update the boot0, boot1h, etc etc if I have done this already on Chameleon v2.0 RC5 earlier revisions?

 

Can I just copy over the boot to my EFI partition and skip all the procedures?

 

If not from which revisions on RC5 should this be done?

 

Thanks

Link to comment
Share on other sites

What`s the advantage of update - boot1h ?

Unless the code from which it's compiled was changed, none!

Even then, the changes done may not affect the functionality... it depends...

 

Is there a need to update the boot0, boot1h, etc etc if I have done this already on Chameleon v2.0 RC5 earlier revisions?

Can I just copy over the boot to my EFI partition and skip all the procedures?

Azi: answer above.

 

If not from which revisions on RC5 should this be done?

r881 for boot0, chain0 and boot1h.

r902 for boot1he.

r186 for cdboot.

 

Check the repo here, here and here; look at the rev column, for the last rev were changes were made.

Edited by Azimutz
Link to comment
Share on other sites

@Azimutz

 

This is the procedure I follow from scratch but it seems to be missing how to install boot1he? Is that also boot01he?

 

http://forum.voodooprojects.org/index.php?topic=649.0

 

about halfway down the thread starting with:

 

10.6x:

 

 

@janek202,

 

I have tried and tried and tried again but the wizard keeps crashing on me when I try to install boot0 or install boot and check box next to it. This is for EFI partition formated as HFS+.

 

I am able to install boot though.

 

Maybe the crashing is related to the mounting and unmounting?

Link to comment
Share on other sites

@Azimutz

This is the procedure I follow from scratch but it seems to be missing how to install boot1he?

oSxFr33k, don't worry about boot1he! i only mentioned it to stress the point of looking at latest file revision,

to determine if it should be updated or not and because it was updated recently (nothing important if you were using it).

I'm not even sure of it's use :) just keep on using boot1h for hfs installs.

Read the comments at the start of the boot1*.s files (after "@APPLE_LICENSE_HEADER_END@") for info on them.

 

 

p.s.: by the way, i see your an ESP (EFI system partition) "user"; did you ever tried using boot1f32 instead of boot1h,

so you don't have to screw with it by formatting to hfs?! Well, thinking again, installing boot1f32 to it is also another way of screwing with it!?

Anyway, using the ESP to install the booter is a big "non sense" to me!!... just an opinion i like to mention from time to time :P

Edited by Azimutz
Link to comment
Share on other sites

@Azimutz,

 

I always format as the link I provided shows been doing this since day one that Chameleon started to allow the install.

 

I see many more advantages to it rather than putting the boot on the root of the drive. Just my opinion.

 

I have to look up boot1f32 to see what it offers over boot1h.

 

I can format my drive and still have chameleon boot. Where as if the boot is on the root of the drive good luck.

 

Why are you against having the boot on the EFI? I know this is actually not the way as in a real mac right?

 

Anyhow its just the way I have been doing it for years now and I just don't want to change my routine. There are other covert reasons as to why I do it this way.

Link to comment
Share on other sites

I can format my drive and still have chameleon boot. Where as if the boot is on the root of the drive good luck.

If you have the need to completely wipe the HD, you will lose boot anyway.

 

Why are you against having the boot on the EFI? I know this is actually not the way as in a real mac right?

No i'm not against it, i just think it's a big waste of time;

from the pain in the rear, that's having to mount it (when it's not supposed to be mounted after boot process) just to update stuff,

to formatting it as hfs, which completely invalidates the UEFI specification, thus invalidating the GPT, which can cause recognition

problems for other systems (like Windows starting showing it on the Explorer) and even OS X,

going through the fact that people insist in spreading that it's a FAT32 partition when it's not (read),

and that to keep 3 patched system kexts there (or in Extra, for that matter) i have to add 6 other as dependencies**

(not counting with AppleHDA.kext plugins, 3 of them if i do remember), etc, etc...

 

And then there's the "keeping the system vanilla" justification; even Mac users hack the system to change/add functionality,

therefor killing vanilla so, were do we stand here??... there's no vanilla! (imho)

Etc, etc, etc...

Yeah, i have many reasons to call it "non sense", but i'm not against it... i just don't support it! ;)

You are free to do as you please, as much as i'm entitled to have an opinion.. that's all.

 

Now, let's quit the talk and go do something really useful, like lunch and try to code a bit :fiery:

 

Stay safe...

 

 

 

**(ATIFramebuffer.kext, ATISupport.kext, IOAudioFamily.kext, IOGraphicsFamily.kext, IONDRVSupport.kext and OSvKernDSPLib.kext

for AppleHDA.kext, ATIRadeonX1000.kext and ATI1300Controller.kext)

Link to comment
Share on other sites

@Azimutz,

 

I decided to try it with chameleon on the root. How can I format the EFI back to what it should be, UFI correct? I want to use Chameleon Wizard to create the boot0 boot1h on the active partition rather than the EFI partition. Either way I have a USB Flash Empire EFI boot so if I screw up which I do 98% of the time, I can get me back!!

Link to comment
Share on other sites

@Azimutz,

 

I decided to try it with chameleon on the root. How can I format the EFI back to what it should be, UFI correct? I want to use Chameleon Wizard to create the boot0 boot1h on the active partition rather than the EFI partition. Either way I have a USB Flash Empire EFI boot so if I screw up which I do 98% of the time, I can get me back!!

That's a good question... i don't know how to format it back :P what i did last time i tried to play with it, was follow Apples advice in

"... including a (compressed) disk image of the ESP within your disk utility". Well, sort of; i read the the advice to late so, what i did was

created a GPT disk image (with Disk Utility) big enough so the ESP partition is created, extracted the ESP from the image and restored it

to it's place. I can't remember exactly the steps... let me take a look around... i remember posting a message about it on VoodooForums.

Meanwhile we should continue this talk some were else.. i completely forgot were i am... sorry Janek :P

 

Just a final comment on behalf of ESP use to install the booter; what i really consider incorrect, is formatting it to hfs, specially on a multiboot

environment with more than one HD and several filesystem types. Besides that, if one doesn't mind the hassle or has the process of updating

the partition simplified with script/s (that's what i'd do if i'd use it) there's no big problem. You shouldn't change your mind just because of what i said!

Learning is the best excuse to mess with stuff, imho :)

Pm me if i don't pm you...

 

See ya later...

 

p.s.: ... that's obvious; gpt tool seems to do it (check "man gpt" on Terminal or web); efi partition type can be specified.

And don't forget that all this stuff can be tested on a disk image ;)

Edited by Azimutz
Link to comment
Share on other sites

I've been having trouble booting my Dell D430 with Snow Leopard 10.6.6. I've installed Snow Leopard on 2 other D430s and a D420 without any problems, but this one is a real headache.

 

I installed 10.6 and installed Chameleon RC5 r665, and the EDP 1.8 extras from the osxlatitude site. This is the way I've always done it. I used the USB pen method to boot and install.

 

But on this D430, which has a new 120GB HDD (hope that's not the problem), I cannot boot from the HDD. I can only boot from the USB, then select the HDD in the Chameleon page, and then the D430 boots fine and works well once booted.

 

But if I try to boot from the HDD, I get the boot erros:

 

boot0: GPT

boot0: test

boot0: test

boot0: error

 

I tried to make sure the HFS Snow Leopard partition was active, so I used Chameleon Wizard in order, trying each of the 3 options, one at a time. But no go. I still get the boot0 error when I try to boot from HDD.

 

I'm really at a loss here. I've never had any problem with the install before.

 

If anyone has a suggestion it would be greatly appreciated. Thanks.

Link to comment
Share on other sites

Ok, since i posted this stuff here, i'm closing it here to; some day i'll write about this some were else, if worth it.

Anyway, we're on a topic that deals with Chameleon installation so, it's not as out of place as it may seem.

 

Conclusion: if i didn't liked it before, i like it even less now!!! And to spare me some time, i'll just post the

conclusion i sent to oSxFr33k in private:

Well, i'm sorry but i didn't found any way of restoring the partition to the original specification.

I think what i used the other time to clone the partition was "cat", but that left it with an unknown file system. Using iBored:

/dev/disk0		466 GB (976773168 * 512)	unknown, HFSj+, HFSj+, HFSj+, HFSj+, HFSj+, HFSj+
	 /dev/disk1		298 GB (625142448 * 512)	NTFS, Ext, HFSj+, HFSj+
	 /dev/disk2		3 GB (6000040 * 512)		FAT, HFSj+
	 /dev/disk3		3 GB (6000040 * 512)		HFS+, HFSj+

disk0 = my HD, GPT (notice the unknown file system on the ESP)

disk1 = machine original 320GB HD, MBR

disk2 = mounted GPT disk image created with Disk Util, UNTOUCHED

disk3 = same as above, but ESP was removed with

sudo gpt remove -b 40 disk3

and added back with

sudo gpt add -b 40 -i 1 -s 409600 -t efi disk3

it does the job, but did you noticed the file system... hfs+ ??? wtf tongue.gif

 

drutil dump:

512 bytes read - No such file or directory
	 00000000  00 00 00 00 00 00 00 00  00 00 00 00 02 01 20 00  |.............. .|
	 00000010  02 00 00 00 00 F0 00 00  20 00 10 00 00 00 00 00  |........ .......|
	 00000020  00 40 06 00 4F 0C 00 00  00 00 00 00 02 00 00 00  |.@..O...........|
	 00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
	 00000040  00 00 29 01 17 D6 70 00  00 00 00 00 00 00 00 00  |..)...p.........|
	 00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
	 *		  (1968 bytes of 0)
	 Unable to guess the block type!

 

drutil dump of the original ESP:

512 bytes read - No such file or directory
	 00000000  EB 58 90 42 53 44 20 20  34 2E 34 00 02 01 20 00  |.X.BSD  4.4... .|
	 00000010  02 00 00 00 00 F0 00 00  20 00 10 00 00 00 00 00  |........ .......|
	 00000020  00 40 06 00 4F 0C 00 00  00 00 00 00 02 00 00 00  |.@..O...........|
	 00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
	 00000040  00 00 29 01 17 D6 70 45  46 49 20 20 20 20 20 20  |..)...pEFI	  |
	 00000050  20 20 46 41 54 33 32 20  20 20 FA 31 C0 8E D0 BC  |  FAT32   .1....|
	 00000060  00 7C FB 8E D8 E8 00 00  5E 83 C6 19 BB 07 00 FC  |.|......^.......|
	 00000070  AC 84 C0 74 06 B4 0E CD  10 EB F5 30 E4 CD 16 CD  |...t.......0....|
	 00000080  19 0D 0A 4E 6F 6E 2D 73  79 73 74 65 6D 20 64 69  |...Non-system di|
	 00000090  73 6B 0D 0A 50 72 65 73  73 20 61 6E 79 20 6B 65  |sk..Press any ke|
	 000000A0  79 20 74 6F 20 72 65 62  6F 6F 74 0D 0A 00 00 00  |y to reboot.....|
	 000000B0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
	 *		   (320 bytes of 0)
	 000001F0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 AA  |..............U.|
	 00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
	 *		  (1536 bytes of 0)
	 Unable to guess the block type!

 

"gpt show" output for both:

gpt show disk2
		 start	 size  index  contents
			 0		1		 PMBR
			 1		1		 Pri GPT header
			 2	   32		 Pri GPT table
			34		6		 
			40   409600	  1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
		409640  5328216	  2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
	   5737856   262151		 
	   6000007	   32		 Sec GPT table
	   6000039		1		 Sec GPT header

C12A7328-F81F-11D2-BA4B-00A0C93EC93B = uuid for ESP.

The only difference seems to be the file system.

 

Didn't managed to do the job with iBored.

Tried the fdisk procedure i pointed you on the web and it didn't worked on a disk image;

needs a reboot and i'm not in the mood to try it on the HD as i don't like to manipulate GPT

disks with fdisk; i assume the result will be the same as with gpt ??

 

The conclusion, a pain in the rear!

The best solution so far, restore the system to a fresh formatted HD, as you mentioned...

another pain in the rear!!! biggrin.gif

One thing is true; as long as the uuid identifies a ESP, the file system doesn't seem to matter,

unless we really had to use the ESP on a true EFI boot !?

 

This is as far as i go; got more important things to do smile.gif

If you get to any conclusion on your own, please return the info.

 

Stay safe, oSxFr33k.

 

Azi

iBored site... nice tool; it even identifies Chameleon if it's installed to the HD, amongst other goodies.

The fdisk procedure i mention can be found all over the net, even used by Mac owners to restore accidentally

deleted deleted or messed up ESP's... i ended up trying it on my HD... it doesn't work!!! I deleted the ESP

with gpt from a 10.6.3 retail installer restored to the MBR HD, but no getting it back with that procedure.

 

There's probably a way to do it... i'll look into it when i'm old and wise... and retired.

For now, all i can say is :) it!

Again no support from me to this "non sense".

 

Stay safe, you all...

Link to comment
Share on other sites

 Share

×
×
  • Create New...