Did iOS 12.1 brick anyone else's iPhone?

Discussion in 'iOS 12' started by blahbrah, Oct 30, 2018.

  1. blahbrah macrumors 6502

    Joined:
    Nov 9, 2006
    #1
    So my iPhone has been stuck on the Waiting for iPhone part of the update and after a restart I'm stuck with the dreaded 4005 error. After a computer restart and a cable swap out it looks like the problem is here to stay. I've got an iPhone 8 and a 2016 MBP TB.
     
  2. alex.wein macrumors member

    alex.wein

    Joined:
    Jun 8, 2015
    #2
    I restored my iPhone X yesterday and had also some troubles with "Waitin for iPhone". Later my phone also stuck in recovery mode and i became i little nervous :). So whatever...

    My solution was in another computer where I restored my phone in 1. try.

    I also tried with another cable to restore but just on first computer. So i can not say if trouble was in cable like i said before on another compouter there was not any issues :).

    P.s.: I updated iTunes before on both computers and my error number was 4013.

    Hope it helps :)
     
  3. makShot macrumors newbie

    Joined:
    Sep 20, 2014
    #3
    I have exactly the same "Waiting for iPhone" issue. Today I updated my MacBook to macOS 10.14.1, and tried to update my iPhone X to iOS 12.1 via iTunes. The update failed due to the 4005 error. My phone is dead now :(
     
  4. dbrewood macrumors regular

    dbrewood

    Joined:
    Jun 8, 2018
    Location:
    Manchester, UK
  5. M33-1 macrumors regular

    M33-1

    Joined:
    Jun 15, 2010
    #5
    I’ve had nothing but problems from updating using a cable and computer. I don’t have a solution, but would recommend only updating using Over The Air (OTA) from now on. I know this does not help now, but just trying to keep this from happening again. OTA updates don’t have these issues. That are just more reliable. Sorry for your troubles.
     
  6. NoBoMac macrumors 68020

    Joined:
    Jul 1, 2014
    #6
    Ummm.... no.

    For example, one of the biggest cases of failed ota updates.

    https://www.macrumors.com/2016/09/13/ios-10-update-bricking-iphones-and-ipads/

    Conversely, NEVER had an issue with iTunes updates over last decade.

    As alex.wein pointed out, seen cables to be a big issue, and generally the ones that came with the device. Have not used an Apple cable in years myself, no issues (use Anker and Amazon MFi certified cables). Ex: sister was having update issues on a device, their family has a corner in the house where they keep four chargers for their two iPads and two iPhones, every Apple cable from there was causing issues. Tried a different Apple cable that is not/rarely used, fine, as well as husband's 3rd party cable.
     
  7. decafjava macrumors 68030

    decafjava

    Joined:
    Feb 7, 2011
    Location:
    Geneva
    #7
    Worked for me.

    I always do major iOS updates through iTunes using the cable that came with my iMac and is always plugged in and never been used and abused as the cables I carry with me for my iPhone. I agree it likely is a cable issue.
     
  8. makShot, Oct 31, 2018
    Last edited: Oct 31, 2018

    makShot macrumors newbie

    Joined:
    Sep 20, 2014
    #8
    Could be. I tried 2 different lightning cables which came with Magic Mouses. Both didn't work. When I get home I'll try again with a cable that came with my iPhone.

    The last option before going to the service center is to restore my iPhone on another mac as Apple adviced me today. Hope this works.

    Update:
    ok, so with the cable that came with my iPhone the issue was fixed.
     

Share This Page

7 October 30, 2018