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

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Ok. I messed up trying to pikify another macpro1.1

Inventory:
-2 macpro 1.1 one working good with Elcapitan pikified 1 year ago...the other with a new ssd that needs to get an Elcapitan pikified.
-1 Imac 27 late 2013 to work
-1 icy dock external usb case
-1 pen 16gb sandisk


This is what I've done:

1. Copy the Elcapitan Install app to a an 16Gb usb
2. Booting the working macpro 1.1 with pike's boot version
3. Attach the ssd dirve that I want to pickify with and external usb case
4. Open the elcapitan Install APP for trying to install the OS in the external ssd...and worked till I need to reboot.
5. Now I can't boot in the working macpro.

I need to restore the working macpro and pikify the other...what I must do now?

Any help would be apreciated.

Ouch.

========== edit ==========
It might be quicker to try a parameter RAM reset
Reboot MacPro 1
When you hear the chime, hold down the key combination :apple: ALT P R
Keep the keys held down until you hear a second chime, then release them...
That should clear any residue from the failed install, and hopefully reselect your primary internal drive/partition to boot from
=======================

Best case:
Restart the previously working MacPro.
Hold down the ALT key immediately you hear the chime
(I’m assuming your graphics card can show the boot screens)
Chose your usual startup disk.
Reboot
If you get into your usual MacOS, then open System Preferences, Startup Disk, and choose your usual partition.

If that doesn’t work:
Boot into the Recovery HD.
Hold down the ALT key immediately you hear the chime
Choose the Recovery HD
(Or hold the key combination CMD-R)
In recovery mode, you can access the Startup Disk panel (from the :apple: menu iirc)
Choose your usual startup disk
Restart


If that doesn’t work:
Boot into the Recovery HD.
Hold down the ALT key immediately you hear the chime
Choose the Recovery HD
(Or hold the key combination CMD-R)
You should then get access to the Terminal from the menus
Read back a few posts, I wrote about how to check and recover your main partition

Hopefully that gets you back to a working MacPro (number 1).

With the original MacPro working, and with the new SSD attached in the USB caddy...
(I’m going to reference your SSD as /Volumes/SSD if you have named it something else, amend that in the commands below)
Open a Terminal on the original Mac.
Let’s check to see if you put the installer files on the SSD
Code:
cd /Volumes/SSD
ls -al
Can you see a directory (aka folder) named OS X Install Data?
If you can great.
If not then you need to start over.

Here’s where I think your problem probably lies....
Original MacPros sometimes struggle to boot from USB devices, such as your external drive case. Macs of the era much preferred external disks to be connected by FireWire. USB connected drives where sort of assumed to be non-writable media such as CD/DVD, or memory sticks configured to behave like CD/DVD install media. The new Pikify v14 script, and the Pikify app, build the install media onto the disk drive but not in the CD/DVD emulation style any more....

I think you probably got to the reboot phase of the install, with the SSD selected as the boot device, but it’s connected over USB.

You could try refitting the SSD to MacPro number 2, so that it is now internal.
Reboot.
Hold the ALT key when you hear the chime.
I’m hoping at this point that you can select the SSD to start up from.
It should boot into the Installer.
Proceed from there.

If you need to start over....
Do you have a FireWire cable that you can string between the two MacPros?
If you do, put the SSD back into MacPro number 2, so that it is now internal.
Connect the FireWire cable between the two MacsPros
Have MacPro 1 booted and logged in
Reboot MacPro 2 into Target Disk Mode, after a few seconds the internal disks of MacPro 2 should mount onto the desktop of MacPro 1.
Run the pikify v14 script, or the new Pikify App....

If you don’t have a FireWire cable, fit the SSD to an internal drive bay of MacPro 1, proceed from there...
 
Last edited:

gavonder

macrumors newbie
May 2, 2004
14
0
Ct.
I'm kind of late to the party here, but I've been trying to install 10.11.6 on my mac pro 1.1. It's upgraded to 3 ghz quad core & 1.2 update. I've been running 10.10.2 for awhile.

I don't have access to another mac to do it that way.

I've been trying to follow the directions on page 56, post #1390. I've tried a few times now & when it gets to the installing part, it says this version cannot be installed on this machine.

Is there supposed to be an operating system on the destination drive or or should it be blank? Mine is blank. I'm not sure what else I could be doing wrong.
Any help is appreciated.

GAV
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
I'm kind of late to the party here, but I've been trying to install 10.11.6 on my mac pro 1.1. It's upgraded to 3 ghz quad core & 1.2 update. I've been running 10.10.2 for awhile.

I don't have access to another mac to do it that way.

I've been trying to follow the directions on page 56, post #1390. I've tried a few times now & when it gets to the installing part, it says this version cannot be installed on this machine.

Is there supposed to be an operating system on the destination drive or or should it be blank? Mine is blank. I'm not sure what else I could be doing wrong.
Any help is appreciated.

GAV
Yes, you can install onto an empty drive. If you’re having trouble, make sure the disk/partition is correctly formatted, it should be formatted as HFS+ and the GPT partition scheme.

The pikify script v14 (and the App), build modified copies of the Apple installer files onto the destination. It should then reboot into that location (using the modified files). It’s obvious when it reboots into the installer, you may see a language chooser (or not so if it’s already set), followed by the installer. You do not need to manually start the installer, it should start automatically.

From your brief description it sounds like you didn’t get to the reboot.
 
Last edited:

gavonder

macrumors newbie
May 2, 2004
14
0
Ct.
Yes, you can install onto an empty drive. If you’re having trouble, make sure the disk/partition is correctly formatted, it should be formatted as HFS+ and the GPT partition scheme.

The pikify script v14 (and the App), build modified copies of the Apple installer files onto the destination. It should then reboot into that location (using the modified files). It’s obvious when it reboots into the installer, you may see a language chooser (or not so if it’s already set), followed by the installer. You do not need to manually start the installer, it should start automatically.

From your brief description it sounds like you didn’t get to the reboot.


Thanks for the reply. Sorry I was not more clear. I did get to the language chooser & then the installer. That's where I get the error message.

GAV
 

mani girafe

macrumors member
Aug 12, 2016
50
11
FRANCE
Yes it's my MAC PRO 1.1 ( 2.1 )
NEXT STEP : only 2 * X3650 SLAED GO Xeon Cpu to install :)
and Nvidia GTX 980 Video card

Rock and roll baby :)
 

Attachments

  • photo-87 (002).jpg
    photo-87 (002).jpg
    96.7 KB · Views: 385

mani girafe

macrumors member
Aug 12, 2016
50
11
FRANCE
Anybody installed the Security Update 2018-001 for 10.11.6 on a 1,1 or 2,1 MP yet? Just checking if I'll need to replace my boot.efi after doing the update or not. Looks like it makes some changes to the Kernel and other areas:

https://support.apple.com/en-us/HT208465
and no problem
--< No Updated* for security fix 2018.001
But make an clone with carbon copy cloner if you want before apply the update :)

* Not updated ... but SSD clone done for TEST security fix 2018.001
 
Last edited:

SuperMatt

Suspended
Mar 28, 2002
1,569
8,281
Updated and no problem
But make an clone with carbon copy cloner if you want before apply the update :)
I'm also in a boot-loop after the Security Update 2018-001. I took out that hard drive and am running off a clone I made a few weeks ago. I'm wondering what files from this working clone I need to move over to the current one to get it working. I can find scripts, etc. on this forum but not exactly the files to move if I want to manually move them over myself. Perhaps I'm not searching very well.
 

owbp

macrumors 6502a
Jan 28, 2016
719
245
Belgrade, Serbia
Boot loop after update usually points to OS unsuccessfully trying to load Apple nVidia drivers with unsupported cards (Maxwell and Pascal). But i guess all you guys are using AMDs with 1,1/2,1 on El Cap?

Anyone checked the size of boot.efi files from other/older OS?
 

SuperMatt

Suspended
Mar 28, 2002
1,569
8,281
Boot loop after update usually points to OS unsuccessfully trying to load Apple nVidia drivers with unsupported cards (Maxwell and Pascal). But i guess all you guys are using AMDs with 1,1/2,1 on El Cap?

Anyone checked the size of boot.efi files from other/older OS?

I copied the 2 boot.efi files (the /usr and the /System ones) from my working clone to the new drive - still stuck in a boot loop on that drive after doing so. I have an AMD Radeon card.
 

owbp

macrumors 6502a
Jan 28, 2016
719
245
Belgrade, Serbia
I copied the 2 boot.efi files (the /usr and the /System ones) from my working clone to the new drive - still stuck in a boot loop on that drive after doing so. I have an AMD Radeon card.
If AMD is flashed, could you boot in verbose mode and try to see where it reboots (what is the last thing you see on the screen before reboot)? I don't know if it will be of any help but it's worth a try...
 

SuperMatt

Suspended
Mar 28, 2002
1,569
8,281
If AMD is flashed, could you boot in verbose mode and try to see where it reboots (what is the last thing you see on the screen before reboot)? I don't know if it will be of any help but it's worth a try...
My card isn't flashed - hopefully somebody else can help that has a flashed card? I know the Boot64 script at post #1391 in this thread is supposed to prevent things from being overwritten. Is there a script that takes the good files from a working installation and moves them to a drive that either never had the updated boot.efi files or else got them hosed by an update? I'm guessing since this security update was for the "meltdown" bug, that it made some serious kernel changes that are hosing our hacked installations.
[doublepost=1516743122][/doublepost]
Was it just the security update you did or a combo update from an OS earlier than 10.11.6?
Security update 2018-001 for 10.11.6 only. I was already on 10.11.6 without issues.
 

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
boot.efi has not been changed with this security update, the files on the disk after the update are still Piker's Alpha modified boot.efi. The change must be somewhere else.

Running reflashed R290x on a 1,1 reflashed to 2,1 with x5355's.
 

SuperMatt

Suspended
Mar 28, 2002
1,569
8,281
OK so looking through my updated El Cap drive, the following folders were updated:

Within /System/Library/

CoreServices, Receipts, PrelinkedKernels, Extensions, Frameworks, Kernels, LaunchAgents, BridgeSupport

Within /usr/

bin, lib, libexec, sbin
 
  • Like
Reactions: hwojtek

Adesz88

macrumors newbie
Aug 22, 2017
10
3
Hungary
I know this is not much, but i can't focus it, because it's really fast (about 1 second)
 

Attachments

  • Képernyőfelvétel (80).png
    Képernyőfelvétel (80).png
    2.3 MB · Views: 390
  • Like
Reactions: owbp

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
OK, great minds think... etc. ;)
OK so looking through my updated El Cap drive, the following folders were updated:

FOLDERS!!!
****, this looks like a heavy hacking game. Is this security update available as a standalone download already, so we could look into the package?
 
Last edited:

owbp

macrumors 6502a
Jan 28, 2016
719
245
Belgrade, Serbia
At least we can assume that it is happening at early stage of the boot?
@Adesz88 , can you boot into the Single user mode or even better Safe mode? (Assuming that boot into Recovery HD is left untouched and is still working ok, but not so important for this)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.