Results 1 to 2 of 2
Discuss [8GB 2G on 2.2.1] [Solved] Crashed and won't restore at the iOS 3.x (iPhone OS 3.x) - Hackint0sh.org; I'm not quite sure what's wrong with my iPhone. I was on Facebook yesterday and ...
  1. #1
    Rookie Array

    Join Date
    Apr 2008
    Posts
    28
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default [8GB 2G on 2.2.1] [Solved] Crashed and won't restore

    I'm not quite sure what's wrong with my iPhone. I was on Facebook yesterday and it locked up, so I force quit it and went back in and it locked up again and wouldn't force quit. So I rebooted the phone and it came back up with the "connect to iTunes" screen and wouldn't ever boot normally again.

    I tried kicking it out of recovery mode using various tools... iRecovery, quickpwn, ziphone, but no luck. iRecovery talks to it, but booting in normal mode would just crash and reboot back to recovery mode. I figured I could just restore it to the new firmware (3.0.1), but I wanted to get a backup of my shit because I hadn't done it since February. But it wouldn't restore either.

    3.0.1 failed with "unknown error 1604" in iTunes. it gets to "preparing phone for restore" and the phone screen goes black and nothing ever happens. I tried DFU mode, but same thing. 3.0 also fails the same way. I tried all this on two different computers (one running Win7 32bit and one running XP pro SP3). All in the latest iTunes (8.2?). Tried front and rear USB ports and two different sync cables. Nothing.

    So I tried restoring to 2.2.1 which I was using previously. It seemed to restore fine and even got to the activation screen and started receiving text messages I missed all day, but I couldn't get it activated with quickpwn or redsn0w. That's where it's stuck right now. I can make emergency calls, but nothing else. Quickpwn gets to "preparing to enter recovery mode" and doesn't progress. I can get the phone in DFU mode, but quickpwn never recognizes it. Redsn0w doesn't recognize the 2.2.1 firmware IPSW file.

    Next thing I'm gonna try is making a custom pre-activated and unlocked firmware based on 2.2.1 and restore to that. I think that will work, but who knows if the original problem is fixed.
    Last edited by nullitum; 08-12-2009 at 05:04 PM.
    8GB iPhone 2.2.1 Pwned on T-Mobile



  2. #2
    Rookie Array

    Join Date
    Apr 2008
    Posts
    28
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Up and running again... I restored to 2.2.1, ran quickpwn as administrator, disconnected the USB while it was waiting to reboot in recovery mode and then it recognized the phone and started the DFU procedure. Normal jailbreak from there.

    I'm still wondering if I'll be able to restore to 3.0.1 (or rather 3.1 as I was originally waiting for).

    If I don't have a hardware problem (so far seems like not), it kinda makes me mad that an App Store app like facebook can crash and send the OS into kernel panic. What if I needed to use my phone that day?
    Last edited by nullitum; 08-12-2009 at 09:04 PM.
    8GB iPhone 2.2.1 Pwned on T-Mobile

 

 

Similar Threads

  1. Replies: 1
    Last Post: 08-27-2010, 07:38 PM
  2. [FW2.2] [Solved] categories crashed icon disappear and won't come back anymore
    By D_Street in forum Free Toolchain Software (Cydia App's)
    Replies: 1
    Last Post: 12-29-2008, 04:52 AM
  3. Replies: 4
    Last Post: 11-21-2008, 09:25 PM
  4. [2.0] [Problem] Can't restore [Solved]
    By zenkx in forum Winpwn
    Replies: 3
    Last Post: 08-03-2008, 11:23 PM
  5. Crashed 1.1.1, trying to restore
    By oxeneers in forum General
    Replies: 5
    Last Post: 11-20-2007, 02:50 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 01:04 PM.
twitter, follow us!