Sixty Four On Thirty Two | How to (En)

Sixty Four On Thirty Two (SFOTT v1.3.9.5)

sfott_featured-image2

for 10.9.2 see here to get instructions :

Mavericks On “some” Unsupported Mac Models

Mavericks and Mountain Lion On “some” Unsupported Mac Models

Couldn’t be done without Tiamo© boot.efi from Macrumors – http://forums.macrumors.com/showpost.php?p=18411621&postcount=26

Report bugs to moc.n1566162919edmeo1566162919@meo1566162919


Major Update with new Options see here for details, updated How-to coming soon.
New Options :
– Choose your installer anywhere even on remote shares.
– Choose Mavericks or Mountain Lion
– automatic (or manual) Check for Updates.


This Script will fully automate the process for making a USB key
for 32 bits Unsupported Macs so they can install and Run mavericks (64bit)

The script will also allow you patch your key again later on and “at will” to add other computers if needed.

All this Couldn’t be done without Tiamo© boot.efi from Macrumors at the first place


1. Prerequities:

  • 1.1 Of Course an OS X Mavericks Installer in your App folder !

    Currently testing with Mountain Lion

  • 1.2 USB Key / hard Disc

You Only need to have a 8 Gig USB key (or a Hard disc),

If you are running from the target computer,
You just have to choose the USB key/hard drive to use.

If you’re not running the script from the target computer,
you’ll have to add computer infos manually.

Easiest and safiest way is to run sfoot from the target computer.

1.3 What sfott is not:

It will not help you to get Mavericks or Mountain Lion.

You’ll have to get it from the Appstore or another of your computers.

It will not help you to get kext for wifi or graphic acceleration either.

It won’t deal with any Video Card problem you may have

(especially on the Macpro1,1 or wifi on MacMini2,1)

This is not the purpose of this script. it only make a key and allow you to patch it again easily.

1.4 What sfott is:

Even if it (for now) runs into the Terminal,

It will simply help you making a key with the tiamo’s boot.efi in just a few clicks, and save you time and headache by not entering any command line.

Sfott comes bundled in an Applescript Application – the Launcher.

It is installed in /Applications/Utilities/sfott/

The sfott script is bundled in the Package content of this app.

I currently have successfully created a key for a Mac mini2,1 and then patched it again for a Macpro1,1.

2. Install Sfott:

Fecth the SFOTT_install.dmg from Main Sfott web page here :

http://oemden.com/?page_id=531

Open the disc image and double click the installer.

It will Install soft in /Applications/Utilities/sfott/

3. Use Sfott:

3.1 The Sfott Launcher

Go to the Sfott Folder and launch the SFOTT.app.

This is the launcher. It will save you time by asking for your administrator password, then Open the Sfott shell script in a new Terminal window and pass your password thru so you can run it with admin privileges.

The launcher will quit just after launch – note that your password is not saved.

  • Launch it

Sfott_launcher_launch_03-EN

  • password prompt

Sfott_launcher_launch-EN

3.2 The sfott shell script

Once launched by the sfott launcher, you’ll be prompt for your language.
I’ve made hard work to make it localisable. for now English and French are available.

Sfott_01-language

If you’d like to make a translation, either email me, or just duplicate the files in /Applications/utilities/Sfott/SFOTT.app/Contents/Resources/Scripts/Localizable.strings/sfott-EN_en. make the translation, save it and send it to me. I’ll be glad to add it to the script.

Edit it then send it back to me.

I’ll ask here and there for the most translations I can.

So either select French or english and press [ENTER]. You’ll have to accept a first warning but you won’t be asked twice.

You’re now in the Main Menu.

Sfott_02_MainMenu-EN

You’ll notice that you allready have some infos displayed concerning the current computer (the one you’re running sfott from).

It will display:

  • the “board_id”,
  • the “Model”
  • even tells you if you have a 32bit or 64bit firmware.

Once set, it will also display

  • Computer Model to add: MacMini2,1 in the exemple
  • Computer board_id to add: Mac-F4208EAA in the exemple
  • Chosen USB/Media Key is: AHHHH in the exemple
  • Chosen System for Install is: OS X Mavericks
    • soon we’ll be able to choose Mountain Lion if tests are successfull.

3.2.1 Settings

The first you’d like to do at the first launch is go to the settings by selecting the Choice3)

  • 1) Go back to main menu
  • 2) Choose USB/media key
  • 3) Set the Computer to add
  • 4) Select OS X System Version – Coming soon
  • 5) Set alternate Working Directory – Coming soon
  • 6) Enter a newer Tiamo boot.efi url – Coming soon

Sfott_03_Settings-EN

Note:

All thoses settings can also be set via the defaults command.
Only the first 3 are active for now. see below for the defaults write commands.

3.2.1.1 Choose USB/media key

There you will set which USB Key or Hard disc you want to use to make the Key.

Note : Hard work has been done to avoid choosing:

  • the System,
  • Network shares
  • Read Only dmg.

You’ll be warned if you choose:

  • An internal Volume, but you will be able to do so
  • A read Write disc image, but you’lle be able to do so in case you’d like to clone later on a USB stick. – I’ve not tested this yet.
  • DVD is not supported at all.

Sfott_04_Settings-Media-EN

Once you’ve choose you Media, confirm to save the setting, and then go back to Settings Menu.

3.2.1.2 – Set the Computer to add

There you choose for which computer you want to make the key.
If like in the example it is for another computer choose

** Choice 2) Set Another Computer**

WARNING : there only a very basic verification here.
If you enter something either with a space or tabulation, you’ll be prompt and asked to type again. For now, there is NO other Checks so be sure to enter the Correct informations for the Model and the board_id.

Otherwise, you just won’t boot at all, or to be more precise you’ll be able to boot (once the key is created) but the INstaller with claim that you can’t install Mavericks.
Soon there will be a way to call sfott from the Terminal so we’ll be able to patch again with correct ibnfos this time as they will be automatically calculated because you’ll be on the Target Computer.

Sfott_05_Settings_Computer-EN

Sfott_05_Settings_Computerb-EN

1) Choose Current Computer

If you’re running Sfott on the Targeted Computer then just confirm at the Menu by hitting 1)

You are now set to Create the key.

Note:
All thoses settings are saved so you can call Sfoot later on and won’t have to enter everything again.

hit 1) Go back to main menu

and then select

3.2.1.3 – Create / Patch Key

Ok now you’re ready to Rock.

you’ll have several options here:

Sfott_06_Settings-Patch-EN

They are quite obvious.

  • 1) Create a New key Step by Step
  • 2) Create a New key in Autorun
  • 3) Patch existing Media with Current config
  • 4) Extras – display only infos displayed elsewhere for now.
  • 5) Go Back to Main Menu
  • 6) Quit

If you have correctly entered all required infos, then just go and choose option

2) Create a New key in Autorun

You’ll have an ultimate warning displaying infos of the target computer to add to the patch, the Volume choosed (JUST CHECK THIS REALLY, it will be totally erased)

Confirm and go take break. The longuest part is the Packages copy part.
everything else is quite fast depending on your computer, your hard disc and the key you’ve choose.

each time I did erase my 8Gb Key it took 20-25 mn to complete.

Note: if you’ve played around before launching Sfott, just be sure any InstallESD.dmg image is allready opened nor Os X Base System.

For now there are no checks with uuid so eject all dmg (Os X installers I mean) then run the script in autorun. That way you’ll be sure all will be fine.

Sfott_06_Settings-Patch_auto-EN

If you’d like to do stuff step by step (for the Key creation), then choose:

1) Create a New key Step by Step

It is basically the autorun but step by step (quite).

I won’t go into details. Screenshots speaks for itself.

Note : If you decide to go step by step, Be sure to do them in order.
Don’t run one step if you did not run the previous one. ( you could but if you renamed the key for example it will fail)

Sfott_06_Settings-Patch_steps-EN

If you’d like to “patch again” your key then just choose the option 3) Patch existing Media with Current config

In this menu you’ll be able, and surelly be prompt to choose your sfott Key.
if you used the Autorun or step by step then most likely you’ll have a .iamasfottkey file identifier to help the tool find the Key. If it finds one you’ll be prompt if you’de like to use this key for another patch, or if you want to patch another Key – This Key MUST be created with the clone Method of the BaseSystem. if not just don’t use it.

Sfott_06_Settings-Patch_again-EN

3.4 Extras commands

defaults write

Some settings are saved in a .plist in the User’s Preferences folder using Apple’s defaults tool.

For those commandline savy, You could then if you like prior to launch the SFOTT tool change them like this :

sudo defaults write $HOME/Library/Preferences/com.oemden.sfott Media USBVolumeName
sudo defaults write $HOME/Library/Preferences/com.oemden.sfott SupportedBoardIds Mac-F4208EAA
sudo defaults write $HOME/Library/Preferences/com.oemden.sfott SupportedModelProperties MacMini2,1
  • where USBVolumeName is the Volume Name of the target USBkey,
  • where Mac-F4208EAA will be the Board_id of the target Computer,
  • where MacMini2,1 will the Model of the target Computer.

More settings will be available, later on.

you must sudo – for now because the script in runned with sudo and plist is set under sudo. Note to myself just chmod the file.

if you do not run sudo

  • write will fail (if already runned at least once)
  • read will output nothing
IMPORTANT notes :
  • 1) those are NOT the correct defaults write for the plist command during patching.
    They are only for the sfott tool. so don’t try those on the USB plist or you will mess things up.

  • 2) Be sure to enter the correct info of course.
    if you’re running the tool from the target computer only the USB default write will be relevant.
    two others are always calculated at launch.

I’m currently preparing tests for Mountain Lion,
there are tiny differences on Volume labels of the dmgs so I have to adapt.
Then I’ll test it. If it is a success there will be a choice or prompt to choose target OS Version 10.8 vs 10.9.

I’ll make Mavericks the default settings anyway, but ML could be selected.

ToDos

– Improve basic user input check for the new computer confirmation. – Done to improve again
— Change working directory inside the bundle – not in tmp anymore.
or at least include boot.efi and icon in the bundle.
so no need for a working dir should then be needed at all
— A better help. this may be online and a pdf too – English Done. todo french.
— explain that now anyone could make a translation
— change the “first prompt” to list available languages rather than hardcode them
tricky would need to source a first file for trads just for this menu – doable.
— Choose Mavericks or ML – done
— Menu Set computer: Add a choice to keep saved computer in pref
not clear enough right now
— ability to choose or not to display some more vars – Done invoke script with -v
could be in a special page called from extras menus
— Option Make a standard Key – not a patched key a real key based on asr method
— Option Make a standard Key with Apple tool – not a patched key,
a real key based on createmediainstaller method – official official method
— Move all this to Xcode
— Add a Patching menu for the Real “unsupported” Computer (in case a new boot efi comes by)
would need Target disk mode
— Look and see if there is a way to add it to the recovery partition – if exists
— add a small script in usr/bin to call it from? – done

Versions History


Sfott.sh – The script

Log History


Back online…. some news

oem.avatar-300x300

Hello guys, I’ve been really busy in my new job and personnal life since last year. I’ll try to answer hundreds of pending comments concerning Sfott. Please Note that I do not have any hardware to test SFOTT since a

Posted in Admin, Mac, sfott

SFOTT download issues

SFOTT_icon_75x75

Hi all, Downloads have reached a huge rate from 25k to 100K+ in less than a month… Holly S…. Website then had serious issues with downloading for about a month, Ticket has been made and I’ve asked my provider to investigate

Posted in sfott

Je suis Charlie

je-suis-charlie
Posted in Admin, Defaults, Deploy, Design, Development, Linux, Mac, sfott, tips tricks scripts, Windows

SFOTT | YOSEMITE beta release

EDIT 20141118 : Update runs fine from AppStore with 10.10.1 seeded today. I am very very very late at coding Sfott, I have focused on Yosemite Server for my job lately. I’ll do my best to go further and at

Posted in sfott Tagged with: , , , , , , , , , , , , , , ,

SFOTT | YOSEMITE : success

sfott_icon

Thanks to macrumors great people, I too, succeeded to install YOSEMITE (on my MacMini2,1) I do not have anymore MacPro1,1 at hand to test on it. But if a MacMini2,1 takes it, no worries Macpro1,1 & 2,1 will do has

Posted in sfott Tagged with: , , , , , , , , , , , , , ,

10.9.5 Update and SFOTT | All smooth but BEWARE (again)

sfott_icon

10.9.5 Update runs smooth. No need to repatch the System once done, like for the previous 10.9.3 / 10.9.4 I’ve just downloaded and installed the 10.9.5 Update on my Guinea MacMini2,1 with no hassle. Note I do not have access

Posted in sfott Tagged with: , , , , , , , , , , , , , , ,

SFOTT | Successful reported installs with Tiamo’s boot.efi and SFOTT script.

sfott_icon

Successful reported installs with Tiamo’s boot.efi (and SFOTT script). PLEASE NOTE : Getting it to be installed is ONE thing. Having a usable system is another thing. For some machines it may be not worth it, to loose wifi, audio

Posted in sfott Tagged with: , , , , , , , , , , , , , ,

SFOTT | Comments replies

sfott_icon

Dear All, Just a word to tell you, I’m very late in answering comments and emails lately. I’ll answer them all. Major Changes in my professional life are occurring. Please accept my apologies, and note that I’m still working on

Posted in sfott Tagged with: , , , , , , , , , , , ,

10.9.4 Update and SFOTT | All smooth but BEWARE (again)

sfott_icon

10.9.4 Update runs smooth. No need to repatch the System once done, like for the previous 10.9.3 I’ve just downloaded and installed the 10.9.4 Update on my Guinea MacMini2,1 with no hassle. This Update still installs in two steps :

Posted in sfott Tagged with: , , , , , , , , , , , , , ,

SFOTT | 10K downloads

sfott_icon

Thank you all ! Today, 10K downloads have been reached for SFOTT. I hope all of you enjoy as I do. Thank you Tiamo for your great job. N.B. : Currently editing code to test with YOSEMITE… stay tuned. Merci

Posted in sfott Tagged with: , , , , , , , , , , ,
131 comments on “Sixty Four On Thirty Two | How to (En)
  1. Avatar Charlie Pope says:

    I’m looking into buying a Mac Pro but with only about £300 to spare I can only really get a 1.1 but I want to be able to run MV or at least ML and after scanning the web I have to say this has to be the best and easiest way of installing MV on an original Mac Pro! The others aren’t that hard either but this has to be the easiest because it’s a script with a good UI. One concern I have before I go and splash out £300 is whether MV will run well on a 1.1?! Has anyone done this who can tell me what it’s like because if it’s really laggy and uses up all your processing and graphical power then I don’t think it’s worth it! Cheers in advance!

    • oem oem says:

      Hello Charlie,

      Sorry for the late reply,
      I would say that i should go well with no much trouble, but you should follow threads on Mac rumors. The only big concern would be the Graphic card but now there are cheap one from the PC world that goes well.
      Personnaly I’ve tested on a Macpro1,1 with a default 7300 and Screen is ok, but not accelerated; I have to admit that my main concern is the coding challenge for itself.
      This macPro is quite not used here at work and I don’t go much on it. SO get a cheap PC card and you should not have trouble as many have done it.
      I currently don’t have Macrumors or xlr8yourmac urls at hand but google will definitly give you hints.

      Another thing is for sure, if the MacPro1,1 I’m using for test was mine and @ home, I definitly would install Mavericks on it (well it has Mavericks yet as it is the guinea pig) and search for a PC card.

      my best and Happy New Year.

  2. Avatar faf says:

    Hi i have Macpro 1,1 !! would you tell me please how can i install OSX Mavericks ??
    and with this app i can,t find the Password , where is the Password for Administator ?
    is any Youtube link ?? that i can see how is working ??

    Thanx

    • oem oem says:

      Hi !
      the asked password is simply your (admin) password – aka the password of your user account

  3. Avatar Luke Spadavecchia says:

    Thanks so much for this great tool. I successfully updated my Macpro 2,1 (with upgraded graphics card) using SFOTT to a clean SSD. It’s running great – very quick and responsive.

    I was wondering if anyone else out there is struggling to get location services working under Mavericks on 2006 Macpros? I have wifi enabled (using an original factory installed card) and my router is an apple time machine so assume the hardware should be supported. Any similar experiences? Also I don’t seem to gave a recovery partition – any tips on setting one up?

    Many thanks and best wishes,
    Luke

    • oem oem says:

      Hi Luke,

      Great it worked.
      I’m late on this but i’m working on the Recovery Partition stuff.
      This will get you Location Services to work then. Stay tuned.

  4. Avatar Freddy P says:

    Awesome Work! Just wanted to let you know…

    • oem oem says:

      Hi Freddy,
      Thanks for the feedback…

      — I have to say Tiamo did the “first” Magic part

  5. Avatar Swoosh Woosh says:

    Hi, I have tried to install both Mavericks and Mountain Lion on my iMac 5,1 with Lion, but I could not get past this message “To download and restore OS X, your computer’s eligibility will be verified with Apple.” I pressed enter and am stuck with “Could not find installation information for this machine.” Judging from the comments above, it seems to work mostly for Mac Pros.

    Will you be able to verify this so that I can give up trying? Thanks!

    • oem oem says:

      Hey,

      I can’t verify with iMacs as I don’t have one at hand at all.
      I also can’t tell for sure if it could work or not, I really don’t know.
      I’ve got a client that has some iMacs so I’ll check and see if the are supoorted or not and if not I’ll give a try with the key and install, but I’m not schedule to go there until next month, and they are production computers so I won’t play much with them, but I’ll give a try for sure. Sooner if I can pass by the office before next schedule.

      Sorry I can’t help more, MacRumors should be the best place to search for infos on that.

      • Avatar Swoosh Woosh says:

        Thanks for your help. That’s handy to know. I’m just glad that other users of Macpros are able to keep working on their old machines with the new os. Just trying to hold on dearly to mine ;) Cheers.

  6. Avatar &e says:

    I successfully created a SFOTT patch key (as shown in Terminal);

    Your new Softt Key is ready
    You can now install OS X Mavericks
    on your : MacPro1,1

    However, when I launch Install OS X Mavericks.app I still get “OS X Mavericks cannot be installed on this computer”.

    Couple questions; Should the installer still be in the Applications folder? (The modified date shows the downloaded date – ie. wasn’t updated after running the Sfott script) Also, the USB thumbdrive was renamed SFOTT but doesn’t appear to have anything but an Applications folder with Safari.app and a few Utilities and Sfott folder within it.

    Maybe the setup wasn’t really properly installed?

    • oem oem says:

      Hello,

      It seems you’re launching the installer directly from the key on your current System.
      — You have to boot from the key to get things work – aka booting with tiamo’s boot.efi (on the key) then using the (pacthed) installer should go fine.
      MacPro is definitely one of the easiest to go with this “trick” of Tiamo’s boot.efi.

      Please note that :
      1) Yes you only see the installer and Applications Folder on the so-called SFOTT key :)
      this is to make it “look good”, so don’t worry all the stuff is in there (System, etc…)

      2) to boot from the Key just hold on the “option-alt” key at boot, then the key will show up, and you’ll be able to choose it.
      you could also go to the System Preferences -> Startup Disc and choose the SFOTT key too. but really just reboot holding the option key…

      3) Concerning the Date, no worries as it is “inside” the installer itself that “magic-patch” happens

      4) before trying to Upgrade to Mavericks on a System please be absolutely sure to have Backups, Clone or both as “usual” when updating/upgrading a system.
      you are playing with your datas remember it.

      Best practice is to do a fresh install, at least the first time on another drive or partition. If all is ok, then you can attempt an upgrade on your current system.

      If you install on another drive/partition, you can also use the Migration assistant that will show up.

      5) did I say to backup prior to install ;)

      if you read comments in here you’ll see that I really insist on this, either with supported or unsupported Macs – in our case.
      Better safe than sorry.

      Now that I’ve warned – a bit :) – on basic stuff concerning your datas and systems, Some did indeed install on an existing System without fresh installs with no glitches at all.

      Finally Note also that depending on your video card you may have to do as others and get a (cheap or not so cheap) Video card to get full Video acceleration. (look at comments to get some of the settings) I did not change the video card as it is a guinea pig MacPro from my Company and I can not “play” with it as much as I want. It a production computer and it is running Lion – I don’t have the responsability of this Mac and the person in charge will never try to install unsupported System (in fact he just don’t care – and I suspect he just don’t know he now can with Tiamo’s boot.efi- but that’s another story)

      So considering you’ve backuped everything you can boot from the key and install Mavericks on your Macpro1,1 and enjoy it.

      6) One more thing :
      if you want to upgrade your system then – I guess – you’ll have a recovery partition (the one from Lion) but I’m not sure of that.
      if you do a fresh install you won’t have the recovery partition. you’ll have to use others utility to do so.
      I’m working on this but I’m over late on this. Last month was really busy and I did not code much…
      It will be on the Sfott utility that’s for sure, I still didn’t choose if I’ll make a second utility or include it with scott script.

      Anyway you should be good to go. I hope I was clear enough and I did not wrote too much.

      My best,

      • Avatar &e says:

        Thanks for the detailed reply!

        After cloning my startup disk, I restarted and selected the thumb drive with the key but all I get is the apple logo startup and the spinner…going on 15+ minutes now.

        I’ll note that I had Mountain Lion running on my Mac Pro 1,1 using the Chameleon method – perhaps this is muddying the processes?

        • oem oem says:

          Hello,

          Maybe Chameleon mess things up, I really could not tell. I did not gave a shot to Chameleon I have to admit.

          I would try to reset the PRAM (command option P R ) then boot directly from the stick and see if it goes well. That’s what I did the first time when testing on the the MacPro1,1.
          and before that I would take out the Chameleon drive (and any drive that matters to avoid trouble with datas – you know how I am with backups) anyway I would only have the target disc for the System.

          if you have a Lion System at hand I would also boot on it first to eventually be sure Chameleon isn’t playing with the install – after take out the Chameleon drive).
          then I would reboot, reset the PRAM and then choose the Key and give a shot.

          of course if it goes well put the discs back in place to get your datas….

          • Avatar &e says:

            Thanks so much for pulling this together and especially for your active support.

            I have successfully installed Mavericks on my MacPro1,1 going with an internal hard drive (same as the Chameleon approach with Mountain Lion).

            What I love about this solution, I don’t have to hold down option when I reboot and as a nice surprise, iCloud and Messages works again! I figure I now have at least another year or two of production out of my aging but very capable MacPro. Many thanks, to you and Tiamo!

          • oem oem says:

            Good news !

            Yes Tiamo did a wonderfull job with his boot.efi. Even if I didn’t try the Chameleon method – I did though about it – Tiamo’s one is way more convenient as far as I can tell and as you report :)
            Glad the “Sfott” script helped you to get this working. Enjoy your MacPro’s new life…

            Note for any other readers: you seem to benefit an “older-existing” recovery Partition from previous Lion or Mountain Lion install explaining you have the iCloud and Messages working ( well I guess that)
            I over late on working on this Recovery stuff I’m working on (I take time for Apple Certifications and to learn Cocoa to go a step further but all this takes me lots of time ….)

  7. Avatar Jeff says:

    After rebooting from the created usb key… any estimate as to how long a typical install would take? I’ve been looking at a gray screen with the spinning gear in the middle of the screen for over an hour… starting to wonder if I did something wrong but don’t want to kill it if nothing is wrong and it just takes a long time… I’m updating a Mac 1,1 to Mavericks… thanks so much for all the work… even if this doesn’t work!!

    • oem oem says:

      Hello Jeff

      you should not have to wait that much that’s for sure.
      Some have had trouble with USB keys. Can you try with an internal disc or partition or a FW disk.
      Also the installer should be obtained directly from the Appstore rather than hmmm someplace somewhere..

      Also the video card could be troublesome but most have succeeded.

      • Avatar Jeff says:

        sorry for delayed response… but I went w/ the internal disc approach and it worked beautifully… i carved out a small 8gb space for the key, on the same volume… and it still worked great! very thankful for the hard work provided to us novices…

        • oem oem says:

          Heyyy

          This is great Jeff !
          Good you ‘ve got it and it tends to confirm that internal idsc/partition can save the install when USB keys are “failing”..
          I’ll so give atry with Mountain Lion and the install on a partition to see if I’ve got a success. I’ll try next week

          Enjoy your New MacPro”Vericks”

  8. Avatar Alokin says:

    I have tried everything noting worked. it just show the apple logo and boot into mountain lion. Also i have to say that the script is not working for me i have to manually copy packages, boot.efi and manually edited the plist files to add my board id and supported mac and manually edited the osinstall.mpkg file.

    This are my macs specs i have followed the steps but is not booting at all. i am using external HDD partition for this, it is bootable.

    Board id Mac-F22788C8
    MacBook 3,1
    OS Mountain Lion

    • oem oem says:

      Hello Alokin,

      I’m sorry that it does not work for you.
      I’m not sure it can work on macbook at all.

      Concerning the script and failures please email me some log of the terminal window or screenshots so I can dig on what ‘s wrong.

      Most problems usually appears after using the script when trying to install, I’ve had not been reported with suchs problems on such steps of the script.

      Maybe a localisation stuff, what is your main System language ?

  9. Avatar Fabio says:

    Hello i need your help ;( I have a macbook early 2008 so not capable to run mavericks because of old graphic card. I cannot download Mavericks from App store, as you can i magine. I obtained a DVD .dmg Mavericks DVD but with this .dmg i don’t know how to put Mavericks.app in Application folder. If you have a regular email i can send you some screenshot showing my problem. Since i cannot start from “Maverick installation app in Application folder” nothing works ;( I used another method to create the USB key. It appears all goes well but when i boot from the usb key with alt, i get a prohibited sign. Can you help me ? Thank you very much.

    • oem oem says:

      Hello Fabio,

      I can’t tell for sure but I do think macbook won’t run Maverick because of older graphic card.
      If you wan’t to try anyway just double clic on the dmg you speak of. then choose the installer from there in the settings menus to choose installer.
      you should choose either search or enter manually the path of the installer. (you normally can drag and drop the installer on the window when prompted to enter manually the path).
      you’d better go and check on Macrumors about macbook as you may waste time trying to get things working for a computer that will (maybe) never be able to run it.

      For this the only way would be modified kext and so, and as for now I’ve not worked on those particular pbs.
      sorry I can’t help you more. I have not tested macbooks myself at all

  10. Avatar Jack says:

    The program did a flawless job of creating the boot USB. Very simple to follow instructions and menus. I appreciate how the program read my board ID and automatically edited the necessary files, inserting the new EFI etc.on my Mac Pro 1,1. Thank you OEM! I did pull my ATI 5770 video card out and put my original video card in so that I could see the boot screen during this process. I should add that I did a clean install on a new SSD drive mounted on a PCI card adapter. After successfully installing Mavericks I removed my Lion OS ATA hard drives and reinstalled the ATA 5770 video card. Unfortunately now I see nothing when I try to boot from the new SSD alone. My next step will be to put the original video card back in and see if there is any message showing up during the boot process. Any suggestions on how to resolve would be much appreciated.

    • oem oem says:

      Hello Jack,

      I’m not sure I got the exact trouble you have.
      You have successfully installed Mavericks with the original video card.
      you have another one (ATA 5770 video card) and then you don’t have video right ? or you jut don’t boot at all ?

      I’m not the kext trouble expert I’ve got to say.
      first as you suggested I would boot with the video card you got success with.
      I’ve read on macrumors for those kind of trouble than some just keep both Cards so in case of trouble they plug the old one.

      and so I would try to boot with both video cards, plug the screen on the one that works, see what happens, if the other ATA 5770 appears in system profiler. if not then I’m affraid it won’t fit unless you play with kexts.

      I don’t want to say stupid things and I’ll take a lot at the comments on my site to see if others had succes swith this video card.

      can you tell what are the both videocard you have and what is the ‘original’ one;

      cheers

  11. Avatar Jack says:

    OEM, I did try booting with the original video card, which allows me to see the boot process. I learned that the SSD drive shows up when I hold down the alt key and I can boot up successfully if I go though that process and select the drive manually. I think this is because apparently the Mac Pro recognizes the PCI mounted SSD as an “external” drive. I tested this by using the installation USB to install Mavericks on a spare clean partition on an existing hard drive in my normal ATA bay. It installed and worked flawlessly. So now I will have to purchase an Icy Dock adapter and install the SSD in the normal ATA drive bay to make it be recognized as an “internal” hard drive. Then it should boot up automatically when designated as the startup disk. I will lose the extra speed of connecting directly to the bus via PCI, but I do not know of any way to make the Mac Pro 1,1 recognize the PCI mounted SSD as an internal HD. Thanks for your excellent work in making the creation of a Mavericks installation tool for the Mac Pro 1,1 so simple and effecive!

    • Avatar Jack says:

      To clarify the video card issue, when upgrading a Mac Pro 1,1 to Mavericks, it is necessary to upgrade the video card in order for the graphics to work well. Unfortunately the new card, typically an ATA Radeon 5770 does not allow for viewing the boot information, so one cannot manually boot with the new card. So I put the old card back in only for the time necessary to troubleshoot this issue, then I put my new card back in so that Mavericks works well. Thanks again for your help.

      • oem oem says:

        ok,

        I really really have to begin to think of compilation of the success and failures reported here !
        thanks for the feedback.

    • oem oem says:

      Thanks Jack,

      Really cool you figured it out.
      I can’t help with PCI SSDs as the MacPro1,1 is at work and I can’t play much with it. I also work everyday on Macpro3,1 so no Tiamo’s boot.efi needed with it.

      And I really appreciate your congrats.

      Cheers

  12. Avatar Andi says:

    Hi,

    thanks for the work.
    But I have still problems to run the Key. The Scipt tells me at the End, that everything is fine an i can use the SFOTT Key.

    But the Key only has a size about 23 MB. When i go to the Key and open the installation package there is no Shared support Folder an no Install.dmg and no OSInstal.mpkg in it.

    So have you any Idea how I can solve this Problem.

    During the the compiling of the key the Script runs all Processes fine. Also it takes a while to copy the packages to the SFOTT Key.

    But after all its done and the Script says I fine to use the Key, there are only 23 MB of data on the Key…

    I tried it on may Mac Pro 1,1 (the Machine the Key are for) and I tried it on my rMPB 2013 with entering the datas of my Mac Pro 1,1

    Greatings

    Andi

    • oem oem says:

      Hello Andi,

      Not sure I understand the 23mb you’re talking about. I’d say that’s the left space but I may be mistaken.
      Your Key must be an 8 Gig USB key. Damned did I specified this? – I’ve got to check for that.

      Anyway, unless you have changed Finder’s settings to show invisible files, it’s perfectly normal you don’t “see” things – that’s the part “making the key look good” ;)
      you should only see Applications and the installer.

      I also didn’t get if you DID boot on the key or not ?

      you can also in the Terminal – considering your key’s name is let’s say “SFOTT” ;) – run this command and send me the result :
      ls -la /Volumes/SFOTT

      cheers

      • Avatar Andi says:

        Hi,

        thank’s for the quick replay :-)

        I mean, that the SFOTT datas on the Drive only about 23 MB. I use a 500 GB USB HD. When I do a right klick on the Installation folder in it, an chose Information, it say that the data in it only 23 MB. But it should be about 5GB, shouldn’t it?

        When I try to boot from the SFOTT key, I can choose it anyway. But after choosing the system load for a while an starts then from the normal system HD with Snow Leopard on it, although I have choosed the SFOTT Key for booting.

        Here we go with the Terminal data:

        total 640
        drwxrwxr-t@ 24 Andreas staff 884 6 Mär 00:23 .
        drwxrwxrwt@ 7 root admin 238 6 Mär 00:59 ..
        -rw-r–r– 1 Andreas staff 6148 6 Mär 00:30 .DS_Store
        drwx—— 5 Andreas staff 170 6 Mär 00:18 .Spotlight-V100
        d-wx-wx-wt 2 Andreas staff 68 6 Mär 00:18 .Trashes
        -rw-r–r–@ 1 Andreas staff 304335 6 Mär 00:23 .VolumeIcon.icns
        ———- 1 Andreas staff 0 25 Aug 2013 .file
        drwx—— 5 Andreas staff 170 6 Mär 00:30 .fseventsd
        -rw-r–r– 1 Andreas staff 0 6 Mär 00:23 .iamasfottkey
        -rw-r–r– 1 Andreas staff 0 6 Mär 00:23 .metadata_never_index
        drwxr-xr-x 2 Andreas staff 68 25 Aug 2013 .vol
        drwxrwxr-x+ 5 Andreas staff 170 17 Feb 23:42 Applications
        drwxr-xr-x 3 Andreas staff 102 13 Feb 05:57 Install OS X Mavericks.app
        drwxr-xr-x@ 15 Andreas staff 510 17 Feb 23:37 Library
        drwxr-xr-x@ 4 Andreas staff 136 17 Feb 23:28 System
        drwxrwxrwt@ 2 Andreas staff 68 25 Aug 2013 Volumes
        drwxr-xr-x@ 35 Andreas staff 1190 17 Feb 23:45 bin
        drwxr-xr-x@ 2 Andreas staff 68 25 Aug 2013 dev
        lrwxr-xr-x@ 1 Andreas staff 11 17 Feb 23:42 etc -> private/etc
        drwxr-xr-x@ 5 Andreas staff 170 17 Feb 23:38 private
        drwxr-xr-x@ 60 Andreas staff 2040 17 Feb 23:45 sbin
        lrwxr-xr-x@ 1 Andreas staff 11 17 Feb 23:42 tmp -> private/tmp
        drwxr-xr-x@ 8 Andreas staff 272 17 Feb 23:30 usr
        lrwxr-xr-x@ 1 Andreas staff 11 17 Feb 23:42 var -> private/var

        Thank’s for your Help!

        Andi

        • Avatar Andi says:

          Sorry. I’ve been blind. The datas were invisible. I thought the data are in the Installation folder, but the data are directly in the SFOTT folder. So I thought the Installation folder should have over 5 GB…. my fault.

          But the boot process doesn’t work at all…

          Cheers

          Andi

          • oem oem says:

            ok :)

            did the key (500 usb drive) boots a bit then fails
            or does it just don’t boot (like you choose it with option-alt key, and then it just boot on your regular Os ?)

            I also see this little tiny detail : Mär
            which means that you may be dutch or german language, well not english nor french ;)
            This could be an issue… I don’t know what but anyway I’d like to know.
            So, if you could try this :

            – Either wipe the key “again” or go to disk utility and add a 8 gig partition to the disc.
            – Renamme existing SFOTT name ! to BadSFOTT or example

            — then
            – go to Sys Preferences / language and text => choose english (put it on top of the list)
            – logout / log in

            – launch the script again
            – in Extras Menu => choose dummy mode
            – then choose the new 8gig partition, and
            – run the script in autorun

            This will :
            1) Avoid the copy of the Packagaes but only the OsInstall.mpkg than needs to be patched.
            you’ll have a dummy key and it will only take few minutes to make.

            2) It is to see if the language may be a cause of the “non-booting key” issue…
            In the early days of the script, I had a comment about a guy that seemed to have troubles too and whoose language made the Utilities folder named … not Utilities.
            If it boots and you see the installer (DON4T try to install it would fails – simply reboot on your regular System, and go back in Sfott script – don’t turn the dummy option – it is not by default anyway) and select convert dummy key to real key.
            If it don’t boot… hmmm we’ll have to dig deeper.

            Normally, Language should not be an issue as I do copy a file for localisation but we never know I did not test it in other language than english (well yes I didi test a bit in French but not much)

  13. Avatar Nikki says:

    Anyone try this on a MacBook Air? I click on the Installer from the USB after it reboots and it starts processing but then I get: “To download and restore OS X, your computer’s eligibility will be verified with Apple.” And then “Could not find installation information for this machine.” What am I missing?

    Do I need to wipe the Lion install and let it load fresh? It’s a new install anyway since I just replaced crashed HD with SSD.

    • oem oem says:

      Hello Nikki,

      FIRST don’t WIPE OUT your working system never ever do that. UNTIL you know it works !
      I’m not sure if mba will work, but if you did get the installer you should be close.
      I’m quite sute first mba model won’t work, for others, hmmm I just don’t know, I’m not very active on Macrumors lately and di not really follow what Machines did work.

      I mostly do the script to ease the process of making the patched key (and as a personnal challenge)

      in anycase:
      you should try an external USB drive first before trying on the internal drive.
      And I’d try a bit more as you’ve reached the instaler screen. So be sure you do have entered correct models and board-id…
      I would have said that if it did’nt work at all, you wouldn’t have reached the install screen, but I may be wrong.

      please pardon me as I can’t give you an accurate answer and would most likely tell you stupid things.. I just dont know for mba.

      • Avatar Nikki says:

        First, I forgot to thank you for the SFOTT script in my first comment. It rocks and made prepping the bootable USB with Tiamo’s boot.efi effortless. I’ll keep troubleshooting “could not find installation information for this machine” issue. If I succeed getting Mavericks on early 2008 MBA, I’ll post what I did here.

        I won’t try a fresh install unless I’ve exhausted other options. But don’t worry if I do wipe the system. There is no data for me to lose yet. I have a new SSD in it with a new Lion install. We’re just trying to recycle what was a broken MBA. So far so good. I’m typing on it now.

        • oem oem says:

          Hi Nikki,

          thanks for thanks :)
          well you do know what you’re doing.. that’s great.

          I’ll dig a bit to see if I found any infos on MBAs.
          don’t hesitate to report back if you have success (or failure…)

          my very best.

  14. Avatar Noah says:

    This is a very helpful script which replaces a lot of drudgery. As most good scripts do. However, I made a key using a 10.9.2 installer and the latest script. I carefully added my MacBookPro2,2 board ID Mac-42187CB to the key and followed the steps. Boot works great (looks just like booting a hackintosh) but when I try to run the installer I get a modal dialog saying I can’t install mavericks on the machine in question. I am perplexed an di can’t find much on the web to help me.

    • oem oem says:

      Hello Noah,

      Sorry to hear that, seems I’ll have to do a key with this new Installer to see if I’ve got it working or not.
      I’ll try to do that this week and I’ll report back here.

      Please note that your Board-ID “Mac-42187CB” is not listed in the Lion installer (in which it should be present ! – and in which I did found the Mac-F4208DC8 of my Macpro1,1)
      Are you sure you’ve got the right Board-ID ? I did find a close one : Mac-F42187C8 in the Lion plist. maybe you did a typo…??
      don’t really see other reason but I may be wrong.

  15. Avatar David says:

    Hi, I have a MacPro 1,1 with an ATI 5770. It is working extremely well but I need to move it onto Mavericks for compatibility with some applications I use. I have read and re-read the information here, and in Mac Rumours, and think I know what should be done but I just wanted to check first, and ask a few questions.

    I am using all four drive bays on my system. Bay 4 is the boot disk and is an SSD with just the OS and Applications installed.

    1. Am I correct in thinking that I create the USB key whilst booted from this drive?
    2. To test that everything is working as planned, after I have created the key I intend to replace the boot SSD with a formatted regular drive to do a clean install.

    Is that the correct procedure?

    3. Assuming that works, can I replace the SSD again, re-run the installer from the USB key and upgrade the existing 10.7.5?
    4. Will it matter that my home directory is not on the same drive as the OS?
    5. After all my reading I am still not clear if an ATI5770 will work. Can anyone tell me (I am currently driving two monitors with it).
    6. Did I read correctly that the system’s wi-fi will not work after upgrade? What about Bluetooth?
    7. I already have the installer for the original Mavericks Installer in my Apps folder, but presumably I need to download from the App Store agin to get 10.9.2. Is that correct?
    8. Am I also correct that after installation ‘normal’ software update for Mavericks doesn’t work and we have to go through this process again?

    Sorry for so many questions, just want to get this right. And YES, I will make sure I have a clone before I start :)

    Thanks,

    David

    • oem oem says:

      Hello David,

      Sorry for the late reply,

      1) Yep… you can run the script from any (Intel) Version System (for now).
      I’ve runned it from 10.6.8 – 10.7.5 – 10.8.2 on MacPro3,1 – 1,1 – MacMini2,1 – mbpro (very recent one :) )

      2) That’s what I’d do. Never ever test on “real system” such tricks.
      If you can afford a guinea disk just do it. in each case Backup, back, backup :)

      You could also use an external enclosure. I’ve tested on internal PATA drive below the Optic bay, then moved it out in an enclosure (so I can also test on the Mini).

      Note that I’ve plugged out ALL internal HDD bays from the Macpro1,1 in my first Tests as I couldn’t afford to ruin the existing 10.7.5 System. !
      this is not mandatory but we’re always better safe than sorry.

      3) Yes … and No…

      Yes, it should work. I’ve read some have done that way.
      No, I think I’ve also read it was better to do a Clean install, then use the Assistant @ first launch to get datas moved.

      I’m not sure I’ve not tested.

      What I’d do :
      well a mix of 1) and 2).
      Do as said on 1) then a first boot use the Assistant to get datas and so.

      You could also make four (4) partitions (A, B, C, D) on the GUINEA disc so :
      0) Clone your current SSD on partitions C & D)
      1) run the script and install on partition A.
      if you have another bootable System at hand or cloned your existing System on your guinea disc partition D) :
      before booting in Freshly installed 10.9.x on Partition A) => clone it on partition B.

      Now,
      test 1:
      – boot from Partition A), don’t transfer datas and do basic tests.
      test 2:
      – boot from partition B), and this time, DO transfer datas and again do basic tests and see if all goes nice.
      test 3:
      – reboot on the key to re-run the script to instal on the partition C (one of the clone of your SSD)

      Now, you’d be able to decide if you prefer to to do a Fresh Install and transfer datas, or upgrade your SSD directly.

      4) Not at all

      Even better in my point of view.

      But to ease things, you’d better always have an account (either invisible or visible) on the System drive. trust me it is helpful mostly when upgrading and debugging.
      you can then use that account for basic tests then relog into your regular account.

      Note : That I think I remember I had to delcare “again” the Correct path of the User once. and I was glad to get the admin account on the system ;) to do so.

      5) Damn I so bad on graphic cards !
      Yes some have reported it worked, but you won’t have boot info, only when the system will be fully loaded you’ll have info.
      So, this could be a bit tricky if you don’t have another graphic card at hand for debugging.
      in so you’ll have to be patient, and you should have the partition “D” to trouble shoot durint testing. I’d always have a “qualified” System – 10.7.5 at hand…

      6) In my macMini2,1 there’s no wifi.
      for the Macpro1,1 well I can’t tell there no wifi on mine. and have not searched for the info. while Im’ writing I don’t know if the Wifi is a card or if it is built-in the motherboard, if it’s a card you could upgrade it, if it’s built-in you may have to get a PCi wifi (in case it does not work of course)

      7) No if you have already an installer you can go on with it.. the you’ll be able to update from the App Store.
      note that you’ll have to ree-patch the system to get it working but no worries it is OK. see here : http://oemden.com/?p=791 for details.
      Note taht if you have a qualified mac then just download direclty the 10.9.2 installer to make the key avoiding the hassle of the 10.9.2 update procedure.

      8) No, Normal system update runs fine once Mavericks is installed.
      just go to the Updates tab and install. I’ve had no trouble doing so on the Macpro1,1, that’s also how you’ll do it in step 7.

      Woooo, thats was some text ;)

      hope I’m clear and you can play with Mavericks…

      don’t hesitate to report back (success – failures, wifi/bluetooth)

      Cheers,
      Oliver

      • Avatar David says:

        Oliver,

        Thanks for the extremely comprehensive set of answers. Rather than try and rush this job today, I think I will make it my project for next weekend. I will let you know how it goes. Again, sincere thanks.

        David

      • Avatar David says:

        Hey Oliver,

        Just a quick note. After extensive testing using the method you suggested, I eventually went for an upgrade of my existing 10.7.5. I am pleased to report it went like a dream. All software is working, the wi-fi is fine, my graphics card (ATI 5770) is perfect and reporting its full VRAM and there appears to be nothing untoward. There were a couple of minor permissions issues initially, I think because my home directory is not on the boot disk, but I manually resolved these.

        Thank you SO SO MUCH for your work. I now have a really fast system WITH the latest OS, rather than a really fast system two versions out of date. I remain puzzled why Apple has locked some of up out of the upgrade process when the hardware is still absolutely capable of taking the OS, but thanks to people like yourself who spend time making these things possible.

        I note that there is no recovery disk, but presume I can boot off the USB stick if ever I need to get at the utilities?

        Kind regards,

        David

        • oem oem says:

          Hello David

          So glad it worked fine. thanks for reporting back here, and thanks for your congrats, always nice.

          Concerning the Recovery you’re right on both statements
          1) there is no recovery – and I am damn very late on my Recovery utility coding. Note there are utilities around that will help you create one.
          2) you are perfectly right, you can indeed use the Key as a recovery Partition alternative – in fact there are slight changes but on most part the Recovery is based on the BaseSystem.dmg from what I’ve seen during my numerous tests.

          Cheers and enjoy your Mavericks MacPro :)

  16. Avatar Dodino says:

    Hi, thanks for your great work!
    I have an early 2008 MacBook 4,1 (the black one).
    I tried many ways to install Mavericks without any success.

    Problem is that the installer won’t boot.
    I tried with tiamo’s boot.efi, i tried SFOTT, i tried also a hackintosh installation with Unibeast.
    I tried to boot the installer with Clover, i tried Chimera.
    I tried with different USB drives and finally tried to copy the installer directly in a partition of a secondary SATA SSD.
    There was simply no way to get the Mavericks installer to boot.

    All the devices regularly booted in a Macbook 5,5 unibody (early 2009) that natively supports Mavericks.

    I’m starting to think i’m missing some kernel flag. Have you any idea that could help me?

    Thank you!

    • oem oem says:

      Hey Dodino,

      Sorry for this late reply, have been busy lately.

      I can’t tell if others may have succeeded with this model.
      I’m afraid it is not doable but can’t affirm you for sure, best would be to dig the original Timao’s thread…

      • Avatar BonzoG says:

        Sadly I am having the same problem with a black 2008 Macbook 4,1. I cannot boot the installer, I always end up back at the installed OS login screen.

        I have tried both USB and second partition on main HDD to boot the Mavericks installer from. Both with SFOTT and manually patching everything myself using Flat Package Editor.

        I have set boot-args=”-v” and this shows the SFOTT boot always failing at:
        “Loading System\Library\Caches\com.apple.kext.caches\Startup\Extensions.mkext……………”

        Immediately the system reverts to booting from the installed 10.6 OS X.

        Thanks for this script anyway, it is very easy to use even if something isn’t working quite right. :)

    • Avatar BonzoG says:

      Hi Dodino, I might have finally found a solution.

      Patch your key using SFOTT, but DON’T USE TIAMO EFI. The Macbook4,1 already has 64-bit EFI so doesn’t need the hacked EFI.

      Also you must delete “/System/Libray/CoreServices/PlatformSupport.plist” from your key – patching this file doesn’t seem to get around the hardware check, but deleting it does.

      My Black MB4,1 is installing Mavericks 10.9.4 right now. Hopefully it will be successful.

      • oem oem says:

        Hello BonzoG,

        This is good info… thanks to
        hopefully I now know I’ll keep the step by step menu to “simply” patch files…

        I may consider to create alternate patch menu or option to patch a key without Tiamo’s boot.efi …

        • Avatar Adam says:

          Hi

          I’ve tried to remove the support plist and I didn’t patch with the custom EFI.

          When I boot, It tells me Mavericks can’t be installed on the computer and asks if I would like to use Time Machine to restore my files.

          2008 Macbook 4,1

          • oem oem says:

            Hello Adam,

            I can’t be much help for those kind of install (yet) I have no such hardware.
            please try to read the successfull reports page, as If I’m correct one User gave a method that worked for him.
            I know I have to create an alternative menu/method for such installs, but did not yet as I have no hardware to test it.
            And I now, will focus on YOSEMITE – tempus fugit

      • Avatar Lynus76 says:

        Finally I installed mavericks 10.9.5 successfully with SFOTT 1.4.4

        Here is what I did.

        Patching key with SFOTT. My mavericks version was 10.9.1 at this time.

        Absolutely I did not use TIAMO EFI, I kept original EFI.

        The main point is PlatformSupport.plist file. I did not erase PlatformSupport.plist file. I just modified order of SupportedBoardIds and SupportedModelProperties.

        Normally, after patching key, my boardID and Model are added at the end of list of SupportedBoardIds and SupportedModelProperties in PlatformSupport.plist file. However, I putted my boardID(F22788
        A9) above F223BEC8, and Model name(MacBook4,1) just above MacBook5,1.

        Moreover I did the same thing at InstallableMachines.plist file.

        After this work, I could boot with USB Install Key and install.

        After installation, however, booting failed, so I rebooted with my USB install key again and executed terminal and I double checked the PlatformSupport.plist file on my installed hard drive. The file was restored, there was no my macbook4,1 information.

        I modified PlatformSupport.plist file of hard drive again like I did before installation, and reboot.

        Finally, my macbook 4,1 booted successfully.

        Update was success as well. Now it is 10.9.5.

        Xcode 6 also works well.

        My macbook has new life. ;-)

  17. Avatar Levi says:

    So due to some video card incompatibility issues with my Mac Pro 2,1 I have to build the USB key on an iMac 12,1.

    I have a detailed explanation of my problem at this post: http://forums.macrumors.com/showpost.php?p=18905957&postcount=1006

    However, to summarize it. The USB key is being created and when I try to run the installer on the MP it just sits at the Apple loading window and nothing appears to be happening. I have let it sit there spinning for about 10 minutes.

    Any help would be great. Thanks!

    • oem oem says:

      Hey Levi

      Sorry for the late reply, I had internet trouble.

      OK, so I’m not sure I get the issue.
      When you say ” I try to run the installer on the MP” you mean the Mavericks Installer app ? Do you actually boot from the key ?
      if so, then does “Apple Loading window” means the Grey Apple window from the boot sequence ?

      I don’t know why many have problems with USB sticks, you may be one of them.
      Best would be to use an internal drive/partition on the MacPro:
      – 1st) get a spare disc for this if you can it is always better to test all of this on a dedicated disc, or at least a partition on one internal drive.

      – plug your MP in target mode on your iMac, if you have a spare disc for the Os Install, then create a partition on it – 8gig will do, at the end of it.
      So will use the main bigger partition for the Mavericks System, and the last 8 gig for the “Key”.
      So your MP plugged in on your iMac, you’ll then choose the 8 gig partition in the prefs, go on for the key creation.

      – Once done, eject your MacPro. shut it down.
      then start it with alt key pressed, choose the “installer key” and you should be good to go.

      Be sure to enter the correct informations concerning your MacPro2,1 Model and board-id…. !

  18. Avatar Victoria says:

    Hi,

    thanks for proving us with this great opportunity. I have some issues, though: (I hope I followed all steps correctly.) I’m not sure what to do after rebooting and selecting the usb drive. If I click on the Install OS X Mavericks, I get an error message: “This is not the supported methods of installing the operating system. Please run Install OS X Mavericks.app that you downloaded from the App Store”.

    Any idea why this could be?

    • oem oem says:

      Hello Victoria,

      Obviously something is wrong…
      meaning when you boot from the key in case of Success you should land on the Installer window but without Finder and Os X “standard” environment.
      So, if when you “boot” from the Key and you have a Finder then it is not good at all. This is what seems to happen as you state that you do click on the installer, which means you did NOT boot from the Key. In such case, this means that even if you choosed the key at boot it failed and selected first/any System available.

      As I’m not sure you did choose the Key at boot, here is the procedure – pardon me if this is what you did, better safe than sorry –
      when you boot or restart you have to press the option/alt key until you see a grey screen. all available Systems will show up including the USB stick – it should be labeled SFOTT and at least it should have the Sfott icon.

      Please note that not all unsupported Macs can do the trick, and you did not tell what Mac you’re attempting to use.
      Please also note, I always insist that you really really really should use a spare / guinea partition/hard drive first to test the installation, and if successful then go on further. In any case you must (should, really really should) have a Backup of your system.
      You should not attempt this on your “unique” System if that’s the case.

      That being said (backup, backup, use of spare drive) if you did run the script from the targeted Mac you should be able to boot it from the patched Key.

      In some cases – and I don’t know what are the cause(s) – Some had to use an internal drive and/or partition to make the key as booting from USB stick did not work. – maybe something with the Key itself, conflict betwwen the USB and some component – I don’t know. Use of internal disc partition was a sucessful alternative for many who had USB boot failures…

      don’t hesitate to comment back if yo uhave still troubles or if you succeeded and givingyour hardware configuration.

      My best,

      Oliver

      • Avatar Victoria says:

        thanks for your help, although i don’t seem to be able to run it. I’m definitely booting from the SFOTT key. I’ve also tried to use a partition of my HD as key, but I keep ending up with the finder after booting form the key. It’s a macbook4.1 i’m using.

        • oem oem says:

          Hello Victoria,

          Hard for me to get what the problem is, but you have a boot “failure” – aka you try to boot from the key but as it fails you end up in the Finder (your actual System).
          I’ve read somewhere in MacRumors -I think- that not all macbooks will be able to do the trick even with the installer patched. you should dig a bit on the site. I believe it is a graphic card “issue”.

          what’s for sure is that somehow patch is quite working as it begins to boot from the “key” but if you end up on Finder, it fails – as you of course have figure out, I know.
          The only other things besides the graphic video issue, would be a wrong Model board-id info.

          Did you get the correct Model board-id when entering the settings ?

          Please note that some have had trouble with getting correct Model board-id on some MacPro1,1 as they get infos that they have a MacPro3,1.
          one may have found a clue, he has used Mavericks Download Enabler. did you eventually use Mavericks Download Enabler ?

          trying to narrow things here

  19. Avatar Rachel says:

    I thought I followed your steps perfectly. I pressed restart, and held down the option key. I chose your “OS X Base System” and pressed the arrow underneath it. My computer restarted, the Apple logo came up (which is a great sign since lately all I’ve been getting is that anti symbol) and a few seconds after the Apple logo came up, the computer shut down on itself. I tried again, some issue. Could it be because I’m running 10.5.8 on my computer? (no, not 10.8.5). Also may I mention that I have two hard drives? One is called “Mac HD” and it’s an SSD. The second hard drive is “Old Mac HD” and it’s NOT an SSD. Any help would be greatly appreciated!

    • oem oem says:

      Hi Rachel,

      What Mac are you running ?
      I’ve not tried at all to create a key from 10.5.x, the lowest I tried and code was on 10.6.8…
      give me more details.

      Have you runned the Steps by Steps or autorun to create the key ?

      • Avatar Rachel says:

        After posting my comment yesterday, I thought 10.5 might be too early of an OS to work. So I installed 10.6.8 just now onto the MacPro1,1 (Mac-F4208DC8). I ran your Script. I chose Autorun, and once the program was complete, it turned the USB drive name from “OS X Base System” into “SFOTT”. So I changed it back to “OS X Base System”. I clicked restart. When I heard the ‘chime’ I held down the option key, and it showed me the options for which drives I could boot up to. The USB drive “OS X Base System” didn’t show up there as an option. It showed up yesterday as an option to boot up to, but not today :( Now I’m trying this other USB drive that I did manually myself without your software and it has mountain lion on it. And I was able to boot up to it. It said installing. Once the installation was complete, the computer restarted, and showed me a big “anti” symbol which went away quickly and then the apple symbol showed up and the computer booted up to 10.6.8, not mountain lion. Then I think I plugged the Mountain Lion usb back in and tried booting from that, and it sat on an “install” inscreen forever, so I forced the computer off since it was clearly stuck thinking and wasnt moving for a really long time. Now my mac monitor wont turn on for some reason!!!! The only way to see the computer now is to thether it (connect it) to an older imac at my office via Target mode. So I’m viewing this computer through an iMac and I ran the Mavericks installer from the desktop, not your boot drive. and it said it installed. When I go to System Prefs->Startup Disk, it says the SSD drive is 10.9.2 and the older hard drive is 10.6.8. So I click the 10.9.2 hard drive as the startup disk. The computer restarts and boots up to 10.6.8 despite my request to boot up the 10.9.2 hard drive. I’ve just restarted, held down the option key, chose the USB Mavericks install drive as the boot up drive, and it just boots up to the old hard drive which is 10.6.8. I accidentally click someone or typed something while your script was booting up and now your script wont open any more. I deleted and reinstalled it. and when I open the script and type my password, nothing happens in terminal now. I’ve spent a week now trying to troubleshoot this computer to get it to mavericks. I came close to some successful results, only to warrant new problems and issues. my boss says spending all this time on it isn’t worth it to get keynote (mavericks version). Has anyone else on this forum been successful at this with a MacPro 1,1 with an SSD as one hard drive and a normal drive as the second hard drive? Will this not work because Mavericks is 64 bit and my computer is 32? (which I thought what your software was for), but now I’m just having way too many issues. bad day?

        • oem oem says:

          Hi Rachel,

          was going to sleep…
          wahooo I have to read all that in depth tomorrow, but you did so much I have to decipher all what you’ve stated/tried.

          I can assure you that yep many have succeeded in getting Mavericks on a MacPro1,1 – myself for example and with having a key created from a 10.6.8 System.

          Just a point and I’m not sure it is a big Matter but you’d better not rename the key labeled SFOTT, this is not mandatory but this definitly not what’s causing you troubles.
          I label the Key Sfott to be sure not to conflict with the original dmg name “OS X Base System” when repatching or updating the key have to occur (like new version of the script or any other reason)
          having the key labeled “OS X Base System” could really mess things up in some way as it would be much tricky and harder to get the dmg
          vs the USB stick…

          My SFOTT script is aimed to ease the patched installer Key creation (either on USB Stick, external or internal hard drive/partition).
          What’s making the Mavericks installation possible on some of 32 bit Boards like our MacPro1,1 and 2,1 is the Tiamo’s boot.efi. this is what does the magic.

          I’ve understood you have “obviously” troubles, indeed. Don’t give up, but please let me read and understand all what you have done.
          I’ll take a deeper look at this during the week-end. but most likely it will be on sunday…

        • oem oem says:

          After posting my comment yesterday, I thought 10.5 might be too early of an OS to work. So I installed 10.6.8 just now onto the MacPro1,1 (Mac-F4208DC8). I ran your Script. I chose Autorun, and once the program was complete, it turned the USB drive name from “OS X Base System” into “SFOTT”. So I changed it back to “OS X Base System”.
          ——————————————————————–
          AS I said in my previous comment, don’t rename the Key. I here understand you’re trying to get Mountain Lion. I’d go to Mavericks straight as I’ve had difficulties with Mountain Lion (succeeded on my Mac mini2,1
          ——————————————————————–

          I clicked restart. When I heard the ‘chime’ I held down the option key, and it showed me the options for which drives I could boot up to. The USB drive “OS X Base System” didn’t show up there as an option.

          It showed up yesterday as an option to boot up to, but not today :( Now I’m trying this other USB drive that I did manually myself without your software and it has mountain lion on it.
          ——————————————————————–
          Some have had trouble and had to try 3 times or more to get it boot. I suspect the USB Key power here. I also have had a “bad” USB key that just did not work, althought I was able to create the patched key on it, I could not boot. I choose a brand new Key to create the Sfott again and it worked straight.
          Note that I also had to plug the Key on the Back once or two as it did not want to show up from the front panel.
          ——————————————————————–

          And I was able to boot up to it. It said installing. Once the installation was complete, the computer restarted, and showed me a big “anti” symbol which went away quickly and then the apple symbol showed up and the computer booted up to 10.6.8, not mountain lion.
          ——————————————————————–
          Ok I’m almost lost here, this is what I understand : you’ve installed Mountain Lion on another USB external enclosure. But is it a Patched Os ? how did you patched it ?

          If not patched with correct Model and board-id you will never boot from your Macpro1,1 with Mountain Lion.
          ——————————————————————–

          Then I think I plugged the Mountain Lion usb back in and tried booting from that, and it sat on an “install” inscreen forever, so I forced the computer off since it was clearly stuck thinking and wasnt moving for a really long time. Now my mac monitor wont turn on for some reason!!!!
          ——————————————————————–
          Main reason would be graphic card drivers. or altered files on the filesystem when you shut it down.
          ——————————————————————–

          The only way to see the computer now is to thether it (connect it) to an older imac at my office via Target mode. So I’m viewing this computer through an iMac and I ran the Mavericks installer from the desktop, not your boot drive. and it said it installed. When I go to System Prefs->Startup Disk, it says the SSD drive is 10.9.2 and the older hard drive is 10.6.8. So I click the 10.9.2 hard drive as the startup disk. The computer restarts and boots up to 10.6.8 despite my request to boot up the 10.9.2 hard drive.
          ——————————————————————–
          Here I’m begining to be afraid that you are trying all of that on your production System.
          If so and it would be too late, note that you have to Back up your system and that best is to use a spare drive first. Abit late bust I always insist on this in my pages and in comments too.

          Now if you did install Mavericks from an iMac on your target disc MacPro (thethered MacPro) without using the Key it just won’t work for sure.

          The meaning of the Key (SFOTT Key) is to get a PATCHED installer so
          you can boot From it and then install Mavericks FROM it.

          Launching the installer on the Key from the Cyurrent System (10.6.x for exemple) won’t work at all.

          Again you must boot from the installer in any case.
          ——————————————————————–

          I’ve just restarted, held down the option key, chose the USB Mavericks install drive as the boot up drive, and it just boots up to the old hard drive which is 10.6.8.
          ——————————————————————–
          This is because, your install is just not correct (not patched) so your Mac will just automatically search for a Correct System to boot from.
          ——————————————————————–

          I accidentally click someone or typed something while your script was booting up and now your script wont open any more. I deleted and reinstalled it. and when I open the script and type my password, nothing happens in terminal now. I’ve spent a week now trying to troubleshoot this computer to get it to mavericks. I came close to some successful results, only to warrant new problems and issues.
          ——————————————————————–
          Ok, so this is a first….

          I don’t see what could have caused this behavior.
          try this :
          – Go in your User’s Library => Preferences and find the com.oemden.sfott.plist file.
          delete it.
          – GO in /Applications/Utilities => find the Sfott directory and trash it too. nothing else !

          Empty the trash.
          reinstall the Sfott Script/launcher from the dmg.
          ——————————————————————–

          my boss says spending all this time on it isn’t worth it to get keynote (mavericks version). Has anyone else on this forum been successful at this with a MacPro 1,1 with an SSD as one hard drive and a normal drive as the second hard drive? Will this not work because Mavericks is 64 bit and my computer is 32? (which I thought what your software was for), but now I’m just having way too many issues. bad day?

          ——————————————————————–
          Yeah I’d say bad day ;)
          I understand your boss too. for sure.

          I’m still a bit confused on all of what you did. from what I’ve understood.
          this is what I’d do :

          1- Remove production System’s disc – in case it’s not too late now.
          and Any other drives…
          2- use a spare drive and make 3 partitions. (internal is better – external should work)

          2a– a small one (8 gig) – name it “Installer” for example – it will be used to install the Patched Key instead of using a USB key.
          – and two Other partitions name them for example
          2b– “MPSL” (you’ll install Snowleopard on it)
          2c– “MPMAV” (you’ll use it to install Mavericks)

          3- Install SnowLeopard on MPSL partition. Run all Updates available and be sure to be in 10.6.8 so you have AppStore.
          3a — Now boot on MPSL, 10.6.8 launch the AppStore and download Mavericks.
          3b — Eventually you can COPY FROM your iMac TO your MPSL disc the Mavericks Installer you have (if I’m correct of the Mavericks Installer App)
          3c — Install SFOTT from the dmg on your MPSL System. Run it.
          —- Choose the 8Gig partition “Installer” as a Target for the Key.
          —- Choose Mavericks, then choose the Installer’s Location.

          4- You Now should have a SFOTT drive on your Desktop.
          (you can’t choose it from the Startup pref Pane (yet – but it’s the upcoming new feature soon to be released ;) )

          5- Reboot hold the option-alt Key and you should have the SFOTT Key appear.

          6- If yes boot from it and you should be good to go.
          — if no, well I just can’t get why so…

          IMPORTANT NOTE :
          to go faster and avoid lost of time, in the extra menu of the script, choose enable DUMMY KEY.
          That way you’ll have a Sfott Key but without any Packages.
          Meaning you’ll reach the Install screen but DON’t TRY to INstall !!
          It is only to verify all is fine. If you do reach the install screen and have no “messages stating you can’t install on this computer” then we can assume the key works fine.

          From the Apple up left Menu, choose reboot. and reboot on 10.6.8 MPSL partition.
          Relaunch the script and in the Patch Menu choose convert dummy key to real key.

          You then will have a correct Sfott Key and be able to install Mavericks.
          reboot hold down the option/alt key, choose the Sfott adn there you go.

          I hope it is more “clear”.

          Again, Many many have succeeded either with my script or by patching on their own an installer or Existing System. MacPro1,1 and 2,1 are the easiest to install Mavericks on.

          One last important note, If you succeed in getting Mavericks installed,
          you may have to consider getting a Video Graphic Card compatible. as you may experience laggy video if you stick to the original shipped one. but that’s a good investment that worth it, when Mavericks is up and running.

          Another way, I think of to get Mavericks could also to :

          Thether it on your iMac. install Mavericks as you already did.
          then DON’t eject the drive and DON’t Boot it yet.

          Launch the Sfott script, and this time choose Patch Existing System.
          this will patch the system and place the boot.efi on it.
          this is the method used to get 10.9.2 back up and running when updated from 10.9 – 10.9.1.

          That was a hell of a comment…. and really hope you’ll be able to go with all this.
          But there is no reason that you can’t get Mavericks as all others did.

          my best,
          ——————————————————————–

  20. Avatar Bilal says:

    Hello..
    Im from Germany..
    My question is what i must do after a reboot i must hold the alt button than i choose my Usb (name is sfott) than i click on the installer and it comes a error that he could not install it on my mac. What i must do.. Please in slow and understanding steps… :( i doesnt know what the boot.efi is.

    • oem oem says:

      Hello Bilal,

      if you have an error then Patch is not correct for the target computer.

      on What computer do you try to install that ?

      • Avatar Bilal says:

        not an error it comes that mavericks isnt compatible on my mac i have an macbook 3.1; 2.5 RAM and 3100X Intel Graphix

        • oem oem says:

          Hey Bilal,

          I know it is not supported ;) that’s why you’re here and try to use the SFOTT script/key to get Tiamo’s boot.efi on your Computer.

          I’ve compared the MacMini2,1 and your macbook3,1. you have a chance to go on but you’ll have to dig a bit. the main issue would be graphic card.
          As I’ve succeeded on the Mini you could have a chance. but from what I’ve read on Macrumors most old macbook won’t go.
          Again if the Mac mini did it you could try.

          How (on what computer) did you runned the script to make the Key ?

2 Pings/Trackbacks for "Sixty Four On Thirty Two | How to (En)"
  1. […] I was able to install Mavericks 10.9 on a MacPro 1,1 (2×3.0GHz dual core, wifi, bluetooth, 13GB RAM, 2TB 7200RPM disk, NVidia 8800GT 512MB) using SFOTT: http://forums.macrumors.com/showpost.php?p=18411621&postcount=26 http://oemden.com/?page_id=585 […]

  2. […] | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | see comment here | […]

Leave a Reply to Victoria Cancel reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>