Found a way to get rid of the BootStart! BootError!:

In DOS, I removed every Partition and Updated MBR from the USB-stick with Paragon Disk Manager (hirens Boot CD).

Then I plugged in the USB stick under Windows and denied the question if I wanted to format the new device.

After that, I used dd for windows, but changed synthax to

dd if=c:\complect\imageefi.img of=\\?\Device\Harddisk6\Partition0 bs=1M --size --progress

dd if=c:\complect\usbmbr_novesa of=\\?\Device\Harddisk6\Partition0 --size --progress


where Harddisk6 is my USB-drive (found via diskpart in cmd).

Now it boots without errors.



Unfortunatly, the system reboots without any errors, while loading the kernel after like 6 lines of ".............." - could be a VESA issue, because this is on Core2Duo T7300 with NoNX enabled in BIOS, HPET enabled in BIOS, SSE3 of course and i965+ICH8M chipset.

It could also be a kernel issue - T7300 is SantaRosa - first seen with 8.9.4 kernel and the provided kernel is 8.9.1 I think - netkas, any idea?

Originally Posted by themaxx32000

EDIT: Also, how does Apple manage the decryption on current Mac's, since some don't have a TPM-module anymore? Is this managed by an EFI-module? If so, can't we use it for this implementation to boot of original restore-discs?

AFAIK Decryption is handled by the kernel module which pulls it's key from the SMC hardware...?

Originally Posted by themaxx32000

Found a way to get rid of the BootStart! BootError!:

In DOS, I removed every Partition and Updated MBR from the USB-stick with Paragon Disk Manager (hirens Boot CD).

Then I plugged in the USB stick under Windows and denied the question if I wanted to format the new device.

After that, I used dd for windows, but changed synthax to

dd if=c:\complect\imageefi.img of=\\?\Device\Harddisk6\Partition0 bs=1M --size --progress

dd if=c:\complect\usbmbr_novesa of=\\?\Device\Harddisk6\Partition0 --size --progress


where Harddisk6 is my USB-drive (found via diskpart in cmd).

Now it boots without errors.



Unfortunatly, the system reboots without any errors, while loading the kernel after like 6 lines of ".............." - could be a VESA issue, because this is on Core2Duo T7300 with NoNX enabled in BIOS, HPET enabled in BIOS, SSE3 of course and i965+ICH8M chipset.

It could also be a kernel issue - T7300 is SantaRosa - first seen with 8.9.4 kernel and the provided kernel is 8.9.1 I think - netkas, any idea?

Hi guys,

themaxx, any way this is make in OSX? i have tryed but all time have this err, and dont have more a winPC for try this metod.

any idea for help me?

thanks

No idea, but found out, that it does not work with my other 2gb usb stick....

EDIT: Please, somebody who got this working... My stick boots strait to the menu instead of the shell... I can hit continue twice to load the shell or select "Boot Maintance Manager" -> "Boot from file" and then select the shell from \efi\boot\bootia32.efi

but this does not work, so i need to load it automatically....

EDIT1:

Hmm, just me working with this?

I compiled latest DUET, cause netkas version was pretty old... Currently my goal is to get ICH8-M AHCI EFI module to access my HDD in AHCI mode. Also, I am looking for an UGA VESA generic driver, which could easily fix the VESA issue - just a guess...

Also, I found out, that I get BootStart error like 8 of 10 times I copy the image to the stick, or use the nmake usb command. You have to try a couple of times and clean your USB-Sticks MBR before that.

Last one is, that I did not manage to get DUET working on my 2GB stick. From 512--128, every stick was ok but this one always gives me BootStart error!


EDIT2:

two questions:

1.) Does anyone else get a gray screen (apple-grey) when loading fm1.fv with "loadfv fs0:\apple\fm1.fv"?

2.) Netkas, could you provide a kernel which shows us where it hangs (actual kext file and not "............" while "loading drivers..."?

good topic! bump...

Check this!!!

http://netkas.freeflux.net/blog/arch...1/05/w00t.html

hi all and netkas.

have a question:

u use all original kexts or need some modification in kexts?

thx

this looks really good !! I'm looking forward to dd the new bootloader to my Leo partition

woow!... exellent job!

if you're running Apple stock kernel with pc_EFI bootloader, then you might need to edit the FSB setting in boot file (default is 200Mhz)

here is how you can do it yourself :

1/ open the boot file in an hexadecimal editor (hexedit or any other you like)

2/ search for ASCII string FSB (only one occurence at the end of the file),
FSB setting is right before it (starting at offset 0xD798) :

Code:

90 FA EF 7E 01 00 00 10 00 C2 EB 0B 00 00 00 00

00 C2 EB 0B is endian flipped 0b eb c2 00 -> 200 000 000 for 200Mhz

3/ convert your actual FSB to hex :
let's say you're running your FSB at 350Mhz, this will be 350 000 000
- open OS X calculator in programmer mode, click the decimal button and enter 350 000 000
- click Hex button, this gives you 0x14DC9380
- click the "reverse bin. octet" button to get the value flipped (my OS X is french localized, so not sure of the name in english localized OS X),
this gives you 0x8093DC14, 80 93 DC 14 is the value you want to use
- replace the original value with your own value

4/ overwrite the boot file to the boot sector of your OS X partition, same as you've done first :
- boot in single user mode (do not /sbin/mount -uw / )
- CD to the directory where you have startupfiletool and boot files
- enter the command :

Code:

./startupfiletool /dev/rdisk0s1 boot

rdisk0s1 is first partition of first harddrive, if you booted from another OS X boot disk, or if your boot partition is not first partition, you will need to enter your own value...

reboot and you're done !