Skip navigation
This discussion is archived

Mysterious random total shut downs following 3.1 update

487643 Views 2,415 Replies Latest reply: May 10, 2010 1:32 AM by MrRapture RSS
  • andrewwynn Level 1 Level 1 (55 points)
    oh; haven't had a tiny bit of a hiccup since the recent re-install; i have MMS activated and i have 3.1 on my 3G that hasn't worked in 3 weeks.

    I'll let ya know if anything changes where i'd have to revert again. I have a fairly good feeling about this since the last time when i put 3.1 on, it didn't last ONE MINUTE before hanging.

    the steps I went through are not really reproducible by 'mere mortals'.. but just maybe it's not needed either.

    mine went from 3.0 to 3.01 to 3.1 to 3.0 with no cell, back to 3.1 legit to 3.1 kracked to 3.1 unlocked to 3.1 baseband rollback to 3.0 kracked to 3.01 legit (keeping rollback baseband).. and now to 3.1 legit with MMS.

    I had a weird hiccup at first where visual voicemail didn't work, but after 10 min. or so it gave me an alert that the v.vm password was wrong and a place to type it in; fortunately i guessed what the **** it was and not it is working.

    I did NOT restore any settings from backup at this point; actually.. i shouldn't have to either, so when /if it keeps working the next step will be re-build the app database and photo/tunes libraries.

    3.1 today has been working better than 3.01; no slow to answer slide like 3.01 has been.. and of course... not acting disfunctional like we all have been dealing with.

    I am hoping that if mine keeps working there may be a plan for 'the rest of everybody'.

    might look something like this:
    1) DFU the phone
    2) install 3.0 legit (wait for 1015 error)
    3) DFU the phone again
    4) re-install 3.0 legit
    5) make a new user
    6) DFU yet again
    7) let iTunes notice DFU and suggest the s/w is out of date... allow the update
    8) after rebooting phone, iTunes should notice MMS missing... allow that update also
    9) reboot iPhone manually (it won't restart auto after MMS upgrade).

    that is basically the steps i just took. I'm thinking of trying it out on my wife's 2G 3.01 iPhone, but not tonight ouch; another 2 hrs 'down the tube' just getting my phone functional again since iTunes monked it up by NOT giving me any 'are you sure' alerts but just upgrading to 3.1 with no suggestion that i may want to think twice, and certainly never any mention that i can never back-up to the previous system should the OS not function.

    if the 1-9 doesn't work above... i suspect that you'd actually have to do the baseband roll-back to exactly copy what i did; i certainly hope not since that is just a whole lot of work! (not to mention actually voids a warranty for anybody still under one).

    -awr
    iPhone, Mac OS X (10.5)
  • explorerlmh Calculating status...
    I have the same issues after updating to 3.1. My home button does not respond sometimes and the phone is locked totally and a hard re-boot is needed. I have tried to re-store from backup. Unfortunately, the backup is created when I have already upgraded to 3.1. Is there any chance we can downgrade to 3.0 by ourself and create several backups in our harddisk ?
    Other OS
  • jrbessette Level 1 Level 1 (0 points)
    does anybody else think this is going to ruin their battery? I have to charge my phone at least once a day and many times two. Lithium ion batterys only have so many charges in them. I am getting VERY tired of missing calls and having a "hot" iPhone in my pocket.
    mac book pro, Mac OS X (10.6.1), iPhone 16gb 3g
  • jTomasini Level 1 Level 1 (20 points)
    I am now on my 2nd replacement iPhone 3G - and in the first few hours after updating it to 3.1, it crashed, same as all the ones before it. The geniuses do not think it has anything to do with the OS. They are convinced it is a hardware issue. I'm wondering how many times they will replace it until they realize it is the software.
    iMac G5, MacBook, Mac OS X (10.4.7)
  • ecdc05 Level 1 Level 1 (0 points)
    While I understand everyone just wants to help, all the anecdotal stories about what "fixed" coma mode are not really fixing it. I've followed this thread pretty closely since it was first started.

    The following things do NOT fix coma mode:

    1) Turning off wi-fi.

    2) Turning off 3G

    3) Performing a full restore and then using the backup file

    4) Performing a full restore and setting up as a new phone

    5) Resetting the carrier settings

    6) Resetting any settings

    7) Turning off push notifications

    8) Turning Fetch settings to manual

    9) Deleting apps

    10) Turning off sleep mode

    11) Praying to the Deity of your choice

    Sorry, but I think people who find this thread for the first time could save themselves even more headaches by not latching onto one or all of these options and spending the hours trying to make it work.

    Based on the reports of people in this thread and in other forums, the ONLY proven thing to work is to downgrade to 3.01. If you need your phone and can't deal with coma-mode, then follow the instructions others have already posted. If you're not that fussed about it, then wait for 3.2. I'm as frustrated with Apple right now as the next guy, but if you need a working phone, these are your options.
    iMac, Macbook, iPhone, Mac OS X (10.6.1)
  • Intranut Calculating status...
    Had massive issues the 3.1 on 16GB 3G

    Initially, I turned off notifications and its helped a little. But phone would still randomly reboot 3 or 4 times a day

    Downgraded to 3.0.1, that didnt help at all. Phone wouldnt come back on and when it did, it wanted to be completely restored from scratch

    Finally last night, re-installed 3.1 using my Powerbook instead of the MacPro
    Ensured that I downloaded a fresh copy of the firmware.
    So far so good, but also noticed that "Notifications" is no longer available as a menu option
    General -> About ... shows Version 3.1 (7C144)
    No issues with the phone so far.

    Anyone else restore and see the menu option gone?
    Macpro Early 2008, Mac OS X (10.6.1)
  • digital_hooker1609 Calculating status...
    ok so obviously we are all having the same problem..so whats the best step? restarting or restoring? someone please tell me in simple english..what the best thing to do is? and if its restore..how do you get your media, contacts and messages back?
    compaq 500, iPhone OS 3.0.1, none
  • araut Level 1 Level 1 (0 points)
    For all the new ppl on this thread ... downgrading to 3.0.1 is the best solution .... i did it after weeks of issues with 3.1 ..... not issues for 2 weeks now .... I also got MMS working with 3.0.1 and got back tethering .... why on earth would anyone need 3.1 .....
    Windows XP Pro
  • ecdc05 Level 1 Level 1 (0 points)
    ok so obviously we are all having the same problem..so whats the best step? restarting or restoring? someone please tell me in simple english..what the best thing to do is? and if its restore..how do you get your media, contacts and messages back?<<</div>


    Don't restore. Won't do you a bit of good. Go to page 116 of this thread, follow the two links provided by "Lukeruls" and follow the instructions to downgrade your software to version 3.01. It is the ONLY option apart from waiting for Apple to issue a fix.

    If you look at those instructions and find you aren't comfortable doing them, then do nothing. No amount of restoring, tinkering, etc., will fix this problem. Simply wait for Apple to issue a fix and then update your phone when they do.
    iMac, Macbook, iPhone, Mac OS X (10.6.1)
  • andrewwynn Level 1 Level 1 (55 points)
    i initially upgraded ironically from 3.01 to hopefully fix the bug that was making it so slow to respond (slide to answer took 3-4 tries, etc)...

    so far since the final install of 3.1 about 6 hrs ago today, my phone hasn't worked better .. probably not since i got it. if it doesn't 'go coma' by tomorrow i will likely have to say i magically cured the bug. Consider this: if the firmware upgrade is only 1/4GB; there is no way that is the whole operating system, so there has to be some 'gremlins' that stay behind... it has to be in these gremlins where the problem lies.

    I should mention one more thing that happened during my last install.. it crashed during the first attempt to send that data to the phone.. hung on the progress bar (on iPhone)... i had to hard-reset the phone and start-over.. on the second attempt things went smoothly and quickly.. it is possible that because of a partially installed firmware, it may have 'went deeper' into replacing the parts, giving me the difference i'm seeing now.

    http://rouse.biz/family/Unresponsive-iPhone-31.m4v

    that's my phone a week ago; today it's instant response for any demand.

    coincidentally; to make sure iTunes didn't do anything 'behind my back' i named my iPhone differently.

    I'm going to try to run a couple days without adding apps if i can hold out... if it 'goes comatose' again i'll surely downgrade (again) to 3.01, but take notes this time.

    If i had to 'do another' fix like i just did on mine i would probably try this (don't try this at home)..

    1) start a restore to 3.1 in iTunes (in brand new user, fresh download)
    2) pull the usb plug 1/2 way through install
    3) DFU the iPhone and re-do the restore of 3.1

    if it works it would be surely the quickest solution i can imagine.

    from my experience it's darn darn difficult to 'brick' a phone; after using restore at least 20-25 times with all kinds of crazy ipsw files from all over the planet, and having it crash several different times mid-upgrade... as long as you can count to 10 you can usually get it back into DFU; you know it's in DFU when the screen goes black when you are in iTunes but it's still listed... when in recovery mode, the 'plug into itunes' icon or maybe 'syncing' will be on the display.

    Hope somebody can try it out and it works for them.

    -awr
    iPhone, Mac OS X (10.5)
  • manbeast7 Calculating status...
    I have this same exact problem too and I've waited silently for weeks in the hopes that this would be fixed or Apple would admit that something is wrong with some people's iPhones after upgrading to 3.1.

    Neither have happened.

    Please Digg this story via the link below in hopes that this will be brought to more people's attention and hopefully get resolved!

    http://digg.com/d316L6R
  • scottschmidt Calculating status...
    We have four iPhones in our household, three 3G and one 3GS. All of the 3GS have been experiencing the random shutdown since the 3.1 update. Apple, we know you are working on the problem - how about letting us know when we can expect a fix,
    and please try to expedite it, as iPhones are not only potential lifelines, they are also premiums products that comes with high pricetags, which should entitle the owners to a reasonable level of reliability.
    MacPro, iMac, and Mac Book Pro, Mac OS X (10.6.1)
  • casper25 Calculating status...
    OK this *****. Apple needs to fix this. I think I was able to use my phone 4 times today. I thought it was broken. I mean really we spend all this money for something that works! well fix it
    window xp, iPhone OS 3.0.1
  • MidwayFlux Calculating status...
    While this might correct some issues for the time being, the issues still continue. Just like a Hard Reset will pull the iPhone out of its "Coma State", that is not a real fix, only a Band Aid to get you to be able to use your phone again. It's really absurd that there are this many problems with an incremental update. Seriously. My phone seems to be crashing more and more, too. For example, when I try to create a Genius Playlist in the iPod app on a 3G iPhone, it crashes the iPod app. The iPod App is one of the MAIN FEATURES of the iPhone, and should be working WAY better than it does.

    Point being, I shouldn't have to restore my phone to a new phone and then install everything all over again, and then configure it to my liking, and then STILL have all of the same issues reported in these forums. There needs to be more testing and then more testing and then MORE testing to make sure that it works correctly, or they should allow us to revert back to 3.0 and still let us use MMS. As a legitimate non-jailbroken iPhone user, I pay enough money every month to AT&T to use their service, and I might be one of the only ones, but I can honestly say that I've never really had a real problem with their service (I've lived in the Chicago Suburbs and now am in Phoenix, AZ). But the iPhone experience should be more polished than it is at this point. When 3.0 came out and then 3.0.1, I was VERY Happy because it seemed as though it was finally starting to seem as though everything was running smoothly, at least for me. then another update comes out and it breaks all sorts of stuff. I know we are all here to help each other out, and I honestly do appreciate everyone here, but I shouldn't have to restore my iPhone or erase all of my settings just to get it to work for a short period of time, because no matter what I've tried here in these forums, I continue to have the same problems.

    I've tried restoring it on a Windows Machine and on a Mac. I've tried all sorts of things... Nothing seems to matter.
    G5 / HPd6150 / 16Gb 3G iPhone, Windows Vista
  • MidwayFlux Level 1 Level 1 (0 points)
    I think that Apple advises their employees to not say anything bad about their products. So, while it might not fix the issue, they appear to get "Brownie Points" by making people happy just replacing their phones, even though this still doesn't fix the issue...
    G5 / HPd6150 / 16Gb 3G iPhone, Windows Vista

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.