• Your favorite

    Apple

    ,

    iPhone

    ,

    iPad

    ,

    iOS

    ,
    Jailbreak
    , and
    Cydia
    site.
  • First Generation iPad Users Reporting Bricked iPads After iOS 5

    ***WARNING***
    Be careful updating to iOS 5 on your 3G first generation iPads.

    iOS 5 seems to be full of bugs. First we had the Newsstand app which can be dragged into a folder and rendered unusable until dragged out, additionally we had the iPad 2 being able to be unlocked with a Smart Cover bug, and now we have first generation iPad (3G models) being bricked when trying to install the iOS 5 update.

    If you have an iPad 2, you shouldn't need to worry about this issue, however anyone using an iPad first generation (specifically the 3G model) will want to take into consideration that there is a massive bug with the iOS 5 software update. There is a bug causing the iPad first generation to become bricked or unusable after the update to iOS 5. As of late, the exact cause for the problem is unknown.

    The iPad fails to restore after trying to update from iTunes giving the user an error code (1) after restoring. The iPad then refuses to turn on correctly. After consulting with Apple, it seems that the problem is a hardware failure not accepting the new firmware onto the device. The only solution at this point is to consider buying a new iPad, or to just wait it out and see if there comes a fix anytime in the near future by Apple. Both situations are very inconvenient but if you have an Apple retail store near you, I would suggest trying to bring it in and see if they can't replace it or fix it there. If you're covered by your AppleCare warranty still, then you shouldn't have too much trouble just bringing it in and getting a replacement.

    The fix for all problems is usually to put your device into DFU mode and try restoring again, doing this is usually fail-proof on iOS devices because DFU mode is basically a switch telling the device to set everything back to default settings as if the device were shipped from the factory all over again. The DFU mode restore will not work under this circumstance and it's leaving iPad first generation users flustered with anger about the whole ideal.

    Apple's customer service has usually been very good in the past but it seems that it's weakening. Numerous iPad first generation owners are phoning into Apple to get answers about this problem and they are getting nowhere, but with a response that seems to mirror the rest of the people that are complaining. Apple just says that it appears to be a hardware failure. They don't offer very much insight on the problem, or offer any way to fix it. They best you can do is wait for a fix. My recommendation to you is that if you have this problem and Apple isn't being very delightful with helping you resolve it, keep calling in about the problem. Just keep on it. After enough volume of calls, Apple will work on the issue and attempt to roll out a fix for the problem.

    Are you having this issue or do you know anyone having this issue? Share a comment below! If you've found a fix for the problem, comments of that nature are welcome as well!

    EDIT: MuscleNerd reports on Twitter that using Redsn0w's recovery fix option will fix this issue. If you are plagued with this problem, try that.

    Sources: Cult of Mac
    This article was originally published in forum thread: First Generation iPad Users Reporting Bricked iPads After iOS 5 started by Anthony Bouchard View original post
    Comments 40 Comments
    1. iphoneadam's Avatar
      iphoneadam -
      Quote Originally Posted by Colby21 View Post
      Just go to the Apple Store and ***** about it.


      are you serious? ***** is a bad word?? they say it on tv!!
      Hahaha they get pretty prude on this forum.
    1. shopboy2's Avatar
      shopboy2 -
      I had the same problem with my devices and i found a work around for this specific issue. IOS 5 is really unstable. ok here are the procedures. (note) if you update to the IOS 5 with Ipad or any other Idevice and you are getting error (1) here are the steps to fix it.step 1 - after getting error (1) or (-1) disconnect ipad or iphone whatever is giving you the error from computer and turn it off by holding power button. ( failure to do this will out you in a recovery loop)step 2- download redsnow 9.9.b7 and jailbreak it. now your device should turn on normally. if it doesnt after you are done jailbreaking just put it in dfu mode and open redsnow and hit just boot tether. step 3 - i know some people dont like tether jailbreak so after you turn on your device normally and it boots up correctly just go to itunes and hit restore to factory setting to delete jailbreak.. voula after hitting restore on itunes your device wont give you any errors . comment here if it works or if you have any problems .
    1. cmwade77's Avatar
      cmwade77 -
      I may try sometime today to update, if this does happen, I will take it to an Apple store (although I am going to check my warranty before starting, I think mine is still covered).
    1. mastaryan's Avatar
      mastaryan -
      I updated on day 1 and my only issue was the server being overwhelmed. I have a 1st gen ipad 32gb 3g. It's been working fine except I find a lot of apps crash but it seems to be those few that haven't updated to iOS 5 yet. I can't complain of anything except not being able to put the newstand app somewhere. I jailbroke it and hid the icon and no troubles from the jailbreak. Mine is stable so far on iOS 5.
    1. defdad's Avatar
      defdad -
      I have a first generation wifi-only iPad that updated to iOS 5 without any problem, but when updating my wife's 3Gs iPhone, this exact same thing happened. It would not turn on, reset, connect to iTunes, or go into DFU mode.I took it to the local Apple store and they could not get it to do anything either. The phone was out of warranty so they said I could get an exchange for $149.00. After talking to the manager for quite some time, he offered me 25% off. I was still quite upset when I left, but my wife needed her phone and she is a few months away from an upgrade, so I bought the exchange before leaving. After I got home I did some searching on the Internet, but all that was coming up was all the server problems on iOS 5 launch day. I did the upgrade the day after launch day and had no problem with my iPad or my iPhone 4. I did find a few posts in the Apple developer forums a few days later so I decided to email Apple about it. I have not gotten a response and not really expecting one either. I was told by the Apple store manager that it must be a hardware failure and that there is no way that the software update could have caused it. I don't buy that one bit. I love my Apple products but this has really left me feeling cheated.
    1. JesseDegenerate's Avatar
      JesseDegenerate -
      Quote Originally Posted by shopboy2 View Post
      I had the same problem with my devices and i found a work around for this specific issue. IOS 5 is really unstable. ok here are the procedures. (note) if you update to the IOS 5 with Ipad or any other Idevice and you are getting error (1) here are the steps to fix it.step 1 - after getting error (1) or (-1) disconnect ipad or iphone whatever is giving you the error from computer and turn it off by holding power button. ( failure to do this will out you in a recovery loop)step 2- download redsnow 9.9.b7 and jailbreak it. now your device should turn on normally. if it doesnt after you are done jailbreaking just put it in dfu mode and open redsnow and hit just boot tether. step 3 - i know some people dont like tether jailbreak so after you turn on your device normally and it boots up correctly just go to itunes and hit restore to factory setting to delete jailbreak.. voula after hitting restore on itunes your device wont give you any errors . comment here if it works or if you have any problems .
      it's anything but unstable. I had it on my ip4 since b1 jailbroken, never had to restart.
    1. mmaboi21's Avatar
      mmaboi21 -
      I think it might be iTunes causing the problem. I have had no problems with my girls iPad 1gen 3G updating to the very first beta, the GM, and the official release(which was the same as the GM btw). I barely updated my iTunes a week ago and I updated the firmware way before so possibly a bug in iTunes 10.5.
    1. shopboy2's Avatar
      shopboy2 -
      Quote Originally Posted by JesseDegenerate View Post
      it's anything but unstable. I had it on my ip4 since b1 jailbroken, never had to restart.
      well that's my personal opinion you know. there are many factors that cause problems on your iphone. I've had IOS5 since beta 1 and I've experienced random crashes ( I'm aware is a beta). but on public release I've had like 4 crashes so far and it restarts by itself ( not jailbroken device) . im new to this forum thing btw . I've worked on IOS since the first g iphone. but i've never release anything. I'm working on new unlock for all devices to unlock any baseband. and this is not based on geohots exploit.i hope to get it to work as soon as possible . im still testing it on iphone 4.
    1. Donald Trumps Hair's Avatar
      Donald Trumps Hair -
      I updated to iOS 5 on day one and it worked fine on my 1st gen iPad 3G (16GB). Is this something I still need to be concerned about or does the issue only happen during the actual update process?
    1. tosbsas's Avatar
      tosbsas -
      you guys seen this? MuscleNerd MuscleNerd - tweetGenius Bar should just run redsn0w's "Recovery Fix" to fix iPad 3G "Error 1" http://t.co/7wM4x1o7 First Gen iPad Owners Complain About Bricked Devices After iOS 5 Updates | Cult of Mac (seriously)
    1. FinalBillybong's Avatar
      FinalBillybong -
      MuscleNerd say's Redsn0w recovery fix will sort the issue: https://twitter.com/musclenerd/statu...54723233153026
    1. PathKiller29's Avatar
      PathKiller29 -
      Quote Originally Posted by JesseDegenerate View Post
      it's anything but unstable. I had it on my ip4 since b1 jailbroken, never had to restart.
      Haven't seen u here in a while...

      I had a fun time yesterday trying to update from b7 to GA while not being to use the phone
    1. mutethoughts's Avatar
      mutethoughts -
      Quote Originally Posted by FinalBillybong View Post
      MuscleNerd say's Redsn0w recovery fix will sort the issue: https://twitter.com/musclenerd/statu...54723233153026
      pretty cool that a jailbreak tool can be used to fix a stock iOS issue
    1. Winterboarder's Avatar
      Winterboarder -
      Well this tends to magically happen some time before Apple releases new products. iOS 4 killed the 3g and 3gs phone batteries, now it's time for a new iPad. Never ever upgrade to a new firmware before making sure it can run with no problems. That iPad 3 gotta come out before the holidays so apple is making sure some people will have no choice but to buy new.
    1. JedixJarf's Avatar
      JedixJarf -
      Mod edit

      lol.
    1. KraXik's Avatar
      KraXik -
      Your telling me that no one noticed this in beta?!
    1. Truckerbear's Avatar
      Truckerbear -
      SAME ISSUE I HAVE TO SIGN OUT TO READ ALL COMMENTS. OTHERWISE ONLY ONE (FIRST) COMMENT SHOWS. So lets get this right. Hardware works fine then on all other iOS updates... APPLE releases iOS 5 and then hardware fails. So we blame the hardware and not the software? If this is a trend with a certain device then I call BS. Because if the item worked fine before update then the software which can modify the hardware is causing the failure. For APPLE to claim otherwise is turning their head and that is not going to bode well with the masses.
    1. jrentzke's Avatar
      jrentzke -
      And once again it's the jailbreaking community coming to the rescue of everyone else (including Apple), thanks MuscleNerd!
    1. luvmytj's Avatar
      luvmytj -
      Mod edit

      Is Colby talking about his female dog again? LOL
    1. BenderRodriguez's Avatar
      BenderRodriguez -
      Quote Originally Posted by Anthony Bouchard View Post
      we had the Newsstand app which can be dragged into a folder and rendered unusable until dragged out
      That ain't a bug that's a feature apple forgot to give us cause no one reads the freakin paper anymore but there to stupid to realize this, all we read in it is the funny pages