Internet Recovery Mode Fails Every Time - unable to Install on New MBP

Discussion in 'MacBook Pro' started by pgharavi, Jul 28, 2017.

  1. pgharavi, Jul 28, 2017
    Last edited: Jul 28, 2017

    pgharavi macrumors regular


    Nov 25, 2004
    tl;dr Internet Recovery Mode fails to install MacOS Sierra on a formatted 2016 MBP. I have no workable boot drive. I attempted to go with a “clean/fresh” install.

    I did the simple reboot and cmd + R (and cmd option R), formatted the drive using disk utility, and then selected “re-install MacOS.”

    It does it’s thing for a good 10-15 minutes and then fails, seemingly, at the exact spot every time.

    Something about Bless.plist (I don’t have the log in front of me but I will in a couple hours). I get a error message and tells me to try again.

    This has happened 6-7 times now so clearly o have to change something if I want any success.
  2. Erdbeertorte Suspended

    May 20, 2015

    are you sure you really got into Internet Recovery? Did the spinning globe appear, downloading the whole OS for a longer while?

    If not, try it again with cmd+option+shift+R. In your case it shouldn't matter if you use shift in addition or not, because it just downloads the oldest instead of the newest macOS (each latest .x.x-version of it) your Mac is able to run what would be Sierra 10.12.6 in both cases if it's a Late 2016.

    But it's worth a try. Maybe something got messed up by High Sierra because Internet Recovery does not work for betas.

    Good luck!
  3. pgharavi, Jul 28, 2017
    Last edited: Jul 28, 2017

    pgharavi thread starter macrumors regular


    Nov 25, 2004
    Edit: fixed!

    I’m definitely entering Internet recovery mode these last couple attempts, regardless of which button prompts are used. It says as much and it does indeed take some time to download.

    IIRC, I did regular recovery mode the first time. Cmd + R. That’s when I went into disk utility, formatted the hard drive, and then had my first unsuccessful attempt reinstalling the OS. It has failed every time since then giving me the exact same message and at the exact same spot when I am looking at the log.

Share This Page