Contribute
Register

Install Bootloader and Extra to EFI Partition

Status
Not open for further replies.
Hello. When building for my new hackentosh setup, at the reboot step on my macbook it somehow goes to install OSX on my Mac of origin, and it won't boot without the install USB . Does anyone know what to tell terminal to reverse this? I am able to use the clover boot USB to get back into my MacBook pro but it's extremely slow.
Edit: used clover USB to access my original hd, pulled off all my info then reset and put in original install cd, erased hard drive and reinstalled original os. Better off that way
 
Article: Install Bootloader and Extra to EFI Partition

Worked great for my Asus Z87A.

Thanks.
 
After this actions in article sometimes we have a look or hear a paranormal activity ... EFI partition used by core services boot.efi software and update packages ... Better way to rename it but after renaming the partition scheme does not verify.

BIOS vendors don't want to do external editable partition on chip like a Flash part, but put it on drive. Dirty snitches use it silent.

Kill EFI ...
 
How to update chimera? (i want to upgrade to 10.10, but i got chimera on efi partition, so , just run in mavericks multibeast 7.0 and install bootloader (chimera 4.) on EFI (mounted) ?
 
i have to other partion will this remove my datas that are in these partions
 
Article: Install Bootloader and Extra to EFI Partition

i have to other partion will this remove my datas that are in these partions


Step 1 said:
To make sure your disk is identified as disk0:



  • Open /Utilities/Terminal
  • Type diskutil list


If your drive's root is disk0, you're ready to begin.


Ensure that you follow the guide correctly. As always, backup all valuable data in case of error. Running the above command in terminal will confirm the correct details for you to use in your build. Look for the description of the EFI partition as described. My EFI partition is 'disk0s1' in my current installation. write down your results on paper and use your results when completing the guide. :thumbup:
 
So if my EUFI isn't disk0 then what?
Mine is:dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *31.6 GB disk0
1: Apple_HFS Yosemite 31.6 GB disk0s1
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Yosemite 511.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
 
Article: Install Bootloader and Extra to EFI Partition

So if my EUFI isn't disk0 then what?
Mine is:dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *31.6 GB disk0
1: Apple_HFS Yosemite 31.6 GB disk0s1
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Yosemite 511.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3

The description below looks like this is your UniBeast Flash drive.
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *31.6 GB disk0
1: Apple_HFS Yosemite 31.6 GB disk0s1

This looks like it is the correct drive for your OS X Installation

#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Yosemite 511.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3

I have highlighted your EFI partition. When the guide uses either disk0 or disk0s1 you should replace these with disk1 or disk1s1 :thumbup:

I hope that clarifies the procedure that you need to use in your instance.
 
Article: Install Bootloader and Extra to EFI Partition

Oddly enough I swapped in disk12s2 and it worked, that was my true SSD location I guess.
Up and running great, thanks!
 
Article: Install Bootloader and Extra to EFI Partition

Hello everybody,
I tried to follow this guide to solve some troubles but I even complicated the situation! Just a brief summary:
I have a dual boot W7 and Mavericks on different SSDs. Chimera bootloader allowed to choose which to launch at startup. A third HDD with some NTFS partitions stores my data.
1) changed the SSD of W7 up to 256 Gb because of space requirements. To perform this I used Acronis software, but this required to set up BIOS IDE access to HDs. Changing this bypassed Chimera booting menù and I was able to copy W7 OS old to new SSD.
2) Disconnected the old W7 SSD drive and rebooted.
3) Chimera has no more loaded even restoring AHCI in BIOS setup.
4) Used Unibeast to launch Chimera and access Mavericks OS on its SSD. Upgraded CHimera to 4.0, but it doesn't start during normal booting without Unibeast.
5) Followed the procedure of this thread to create an EFI partition where to install Chimera. Something went wrong because if I keep connected the Maverick SSD the PC remains always stuck at the prompt: verifying DMI pool data..... even if I try to boot with Unibeast, W7 setup DVD and so on. The only way to access the PC (now only W7 obviously) is to disconnect the Maverick SSD.
How to solve the issue?
Many thanks in advance.
Bye
 
Status
Not open for further replies.
Back
Top