Results 1 to 7 of 7
Discuss Error 9 and boot loop at the iOS 4.x (iPhone OS 4.x) - Hackint0sh.org; Greetings everyone, I have a very bad situation in here. My phone was working ok ...
  1. #1
    Newbie Array

    Join Date
    Dec 2011
    Posts
    3
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default Error 9 and boot loop

    Greetings everyone,

    I have a very bad situation in here. My phone was working ok for last half-year or so since I bought it in Glendale, CA but two days ago it just bricked.
    Right now I'm not in US and won't be in the country for uncertain time period thus I can't exchange it under warranty conditions.

    Basically, when I want to update (5.0.1) or restore (4.3.3 w/ blobs saved) it just gives me error # 9 all the way, all the time.
    When I come out of recovery mode it just boot-looping back and forth. I see an Apple logo then it fades away after 7-8 seconds, then it turns back on and goto 10.

    I managed to try a different battery but it did not helped. Tried to google almost the end of the internet and tried all the methods - still no luck.

    So, guys, tell me - is this the end?



  2. #2
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    Won't know until you publish a restore log for us. Can you read the 'Restore Problems' link in my sig and follow the directions there to post a restore log for us to review? The error number can be an indicator but most of the time really isn't enough to troubleshoot.
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

    Did we solve your problem? Got a dollar or two spare? Please Donate!


  3. #3
    Newbie Array

    Join Date
    Dec 2011
    Posts
    3
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by n1ckn4m3 View Post
    Won't know until you publish a restore log for us. Can you read the 'Restore Problems' link in my sig and follow the directions there to post a restore log for us to review? The error number can be an indicator but most of the time really isn't enough to troubleshoot.
    Thanks for reply man, here is the log:

    Error # 9 - Pastebin.com

    I heard that draining out the battery helped someone, so I did that too - but still it gives me error # 9.

    Before I'll consider to recycle the phone, your response worth a ton n1ckn4m3, thank you in advance!

    P.S. By the way, error pops out when phone turns off upon making any progress (0%) with progress bar displayed and "Apple" logo shown above it.
    The logo and progress bar fade away and as soon as they are gone (1-2 sec.) - iTunes shows error message.
    Last edited by pe4ceman; 12-22-2011 at 06:49 AM.

  4. #4
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    Hate to say that the log indicates similar to the error message -- error 9 is indicative of either a faulty cable, bad usb port, running through a hub, etc. It's usually caused when the USB session is terminated unexpectedly -- your log file indicates that is the case here as well.
    Code:
    2011-12-22 11:36:40.264 [5928:2b0]: recv(3200, 4) failed: connection closed
    You've got a few options here, some of which are easier than others:

    1) If you're using a non-OEM dock cable, you'll probably want to find an original or go buy one. Meritline cheap cables have caused problems with people upgrading to new iOS revisions because they don't shield the cable as well as they should and you can get failed flashes.
    2) If you're running through a USB hub, plug in directly and try.
    3) If you haven't already, try all of the other USB ports on the computer.
    4) If none of that works, try on another computer if possible.

    Other than that, there are some older security programs that can impact your ability to successfully restore, specifically overzealous internet security packages like ZoneWall or Norton Internet Security. If you have either of these (or McAffee, etc., or anything like them) go ahead and disable them for the restore as they can be interfering with the restore process.

    If all of that fails, your only real option would be to take the phone in to an Apple store to have them review -- if it's not under warranty it could cost $100-$150 for a replacement device. Last but not least, if you're not near an Apple store or can't get in to a Genius, see if you can get it looked at by a local repair shop. It could be a simple logic board replacement and you could probably do that cheaper than getting a replacement from Apple.
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

    Did we solve your problem? Got a dollar or two spare? Please Donate!


  5. #5
    Newbie Array

    Join Date
    Dec 2011
    Posts
    3
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by n1ckn4m3 View Post
    Hate to say that the log indicates similar to the error message -- error 9 is indicative of either a faulty cable, bad usb port, running through a hub, etc. It's usually caused when the USB session is terminated unexpectedly -- your log file indicates that is the case here as well.
    Code:
    2011-12-22 11:36:40.264 [5928:2b0]: recv(3200, 4) failed: connection closed
    You've got a few options here, some of which are easier than others:

    1) If you're using a non-OEM dock cable, you'll probably want to find an original or go buy one. Meritline cheap cables have caused problems with people upgrading to new iOS revisions because they don't shield the cable as well as they should and you can get failed flashes.
    2) If you're running through a USB hub, plug in directly and try.
    3) If you haven't already, try all of the other USB ports on the computer.
    4) If none of that works, try on another computer if possible.

    Other than that, there are some older security programs that can impact your ability to successfully restore, specifically overzealous internet security packages like ZoneWall or Norton Internet Security. If you have either of these (or McAffee, etc., or anything like them) go ahead and disable them for the restore as they can be interfering with the restore process.

    If all of that fails, your only real option would be to take the phone in to an Apple store to have them review -- if it's not under warranty it could cost $100-$150 for a replacement device. Last but not least, if you're not near an Apple store or can't get in to a Genius, see if you can get it looked at by a local repair shop. It could be a simple logic board replacement and you could probably do that cheaper than getting a replacement from Apple.
    Well, I've tried everything. Changed 3 cables, a dozen of usb ports and 3 PCs. Turned off firewall and applications alike. Nothing helps.
    One repair guy told me that he encountered such problem with another iphone (error # 9) and it was faulty flash inside the board. Is that possible?
    Since the procedure just shuts off when I want to restore exactly when the bar is displayed, not earlier. And phone can stay on for hours with "connect to iTunes" message, but turns off as soon as I want to boot it on my 4.3.3. I tried the 4.3.X boot loop fix too (tinyumbrella), no luck.


  6. #6
    Super Moderator Array n1ckn4m3's Avatar

    Join Date
    Mar 2009
    Location
    USA
    Posts
    2,717
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    145

    Default

    I suppose it's possible, but you'd likely be getting different errors that either reported bad CRC for the attempted write to flash, or errors that indicate that the flash is not responding to the write request, verification failed, etc. You wouldn't normally get an error that the connection was closed, but it is definitely possible.
    The preceding forum post has been brought to you by the letter "N" and the number 42.

    iPhone 4, 32GB (iOS 6.1.2 | evasi0n | SHSH: 4.0 - 6.1.2)
    iPad 2 3G, 64GB (iOS 6.1.2 | evasi0n
    |
    SHSH: 4.3 & 4.3.3 - 6.1)

    Restore problems? Read this: http://www.hackint0sh.org/f137/130802.htm

    Did we solve your problem? Got a dollar or two spare? Please Donate!


  7. #7
    Newbie Array

    Join Date
    Jan 2012
    Posts
    1
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    I'm having the same problem. Can I ask how you solved it, if you were able to? Oh and I've tried the things that were recommended, but they didn't work for me.

 

 

Similar Threads

  1. boot loop recovery loop on FW 3.1.2 BL: 05.11.07 after blackra1n
    By Dirkdiggler in forum Blacksn0w (3G(S) unlock)
    Replies: 8
    Last Post: 03-09-2010, 11:51 PM
  2. How do you boot up when you're stuck in a boot loop?
    By lantern in forum Installation
    Replies: 1
    Last Post: 10-14-2009, 11:21 PM
  3. Replies: 3
    Last Post: 10-01-2009, 10:28 PM
  4. Boot loop w/ 10.5.6
    By jkrusic19 in forum Installation
    Replies: 0
    Last Post: 07-19-2009, 09:58 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:33 AM.
twitter, follow us!