16 replies

Sign in or join Beachball Help to reply.

  1. 0

    Iceman12C

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I found the possible problem. When I upgraded my disk, the partition scheme of the new disk was set to MBR (the default of new HDs). However, it should have been a GUID Partition Table. This explains why the problem is occurring for people who upgraded their HDs.

    I have not verified this. I'll try it later tonight.

    But I believe the steps to fixing this are:

    1. BACK UP CURRENT HD TO ANOTHER DRIVE

    2. Boot from the backup.

    3. Use disk utility to access the INTERNAL drive.

    4. Under Partition >> Options..., change it from "Master Boot Record" to "GUID Partition Table" - THIS WILL WIPE YOUR INTERNAL HD

    5. Restore back up to internal HD

    Again, I haven't verified this. But it seems that the updater is looking for an EFI Partition on the drive, but it's not being found.

    If anyone has time, please try this and let us know if it works.

    Message was edited by: Iceman12C

  2. 0

    pbafhz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    same problem here with the standalone dmg & the autoupdater.

  3. 0

    cpozega

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I get the same message. EFI Firmware 1.1 update error 0. Don't know were to go for support.

  4. 0

    GFE

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No,

    you are not alone.

    Same Problem with my MacBook.

    Tried everything, get the same error all the time (0)

  5. 0

    Ray Allen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    it's worked OK, for me, not noticed any difference yet.

  6. 0

    GFE

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Do u use the orig harddrive, or did u grad up to a larger one ?

  7. 0

    pbafhz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    you are right, i've upgraded to a 250 gb samsung...

  8. 0

    Ray Allen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Can not see that would make any odds.

    Anyway mine is not the original drive but a 7200, 120gb, I also have 3gb RAM installed, and mine worked OK.

    GFE wrote:

    Do u use the orig harddrive, or did u grad up to a larger one ?

  9. 0

    GFE

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Me too, also 250 Samsung,

    maybe this is the problem ?

    Do anybody else experience this problem and also use an upgraded drive ? What type of drive ?

  10. 0

    Ray Allen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Seagate ST9120823AS, 7200, 120gb, no probs here

  11. 0

    GFE

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry, i do not get it.

    We are talking about a problem to get the EFI Firmware installer working on a MacBook.

    And you use 3 GB RAM in a MacBook ? Thought its limited to 2 GB ?

  12. 0

    Iceman12C

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem here.

  13. 0

    Ray Allen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Someone said, had the OP upgraded the hard drive.

    I replied saying I had upgraded my HD and RAM and had no problems installing the FW, just to point out that I can not see how upgrading HD or even RAM would stop a firmware update.

    C2D can use 3GB, this is not what Apple recommends, but I have been for months will no problems apart from a very fast MacBook with CS3 etc. But this is another topic and you will find it in other threads.

    GFE wrote:

    Sorry, i do not get it.

    We are talking about a problem to get the EFI Firmware installer working on a MacBook.

    And you use 3 GB RAM in a MacBook ? Thought its limited to 2 GB ?

  14. 0

    CyclingPlatypus

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've got an updated disk 160GB WD Scorpio but I can't see where this would factor in to the firmware update.

  15. 0

    GFE

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    uups, did not know that.

    So ... cool that the updater did not work, now i know i can go to 3GB ASAP 🙂

    thanks for the info

  16. 0

    Iceman12C

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    From console.log:

    2007-09-27 19:04:47.256 MacBook EFI Firmware Update[726] MacBook EFI Firmware Update version 1.1

    Run the executable in the Contents/MacOS folder with '-h' option to learn about running remotely.

    2007-09-27 19:04:47.257 MacBook EFI Firmware Update[726] OS version is 10.4.10 build 8R2218.

    2007-09-27 19:04:47.259 MacBook EFI Firmware Update[726] No AppleEFINVRAM

    2007-09-27 19:04:51.989 MacBook EFI Firmware Update[726] GetRootAccess success

    Sep 27 19:04:51 mustang authexec: executing /usr/sbin/bless

    EFI found at IODeviceTree:/efi

    Other partition scheme detected

    No auxiliary booter partition required

    Returning booter information dictionary:

    <CFDictionary 0x301750 [0xa080b1c0]>{type = mutable, count = 3, capacity = 4, pairs = (

    0 : <CFString 0x1862c [0xa080b1c0]>{contents = "Auxiliary Partitions"} = <CFArray 0x301f90 [0xa080b1c0]>{type = immutable, count = 0, values = (

    )}

    1 : <CFString 0x1863c [0xa080b1c0]>{contents = "System Partitions"} = <CFArray 0x301fa0 [0xa080b1c0]>{type = immutable, count = 0, values = (

    )}

    3 : <CFString 0x1861c [0xa080b1c0]>{contents = "Data Partitions"} = <CFArray 0x301f50 [0xa080b1c0]>{type = immutable, count = 1, values = (

    0 : <CFString 0x3017b0 [0xa080b1c0]>{contents = "disk0s1"}

    )}

    )}

    No appropriate ESP for /

    Failed to determine auxiliary partition mountpoint for /

    Error while writing firmware updater for EFI

    2007-09-27 19:04:52.023 MacBook EFI Firmware Update[726] pid 0x2d9, status 0x300

    2007-09-27 19:04:52.023 MacBook EFI Firmware Update[726] NORMAL EXIT 0x3

    2007-09-27 19:04:52.023 MacBook EFI Firmware Update[726] An error 0x3 was returned from /usr/sbin/bless.

    2007-09-27 19:04:52.023 MacBook EFI Firmware Update[726] bResult 0x0 Status 0x3 returned from CallAEWP bless

    2007-09-27 19:04:52.024 MacBook EFI Firmware Update[726] EFIUpdaterController::showError:3

    2007-09-27 19:04:52.024 MacBook EFI Firmware Update[726] CommonUpdaterController::showError:3