error 29 iphone locked in recovery mode

Hi,

this is Krishna from the Iphone Technical support at 3Three-Vodafone...the solution to the above problem is a DFU mode restore or trying various t/s steps on the PC like restarting, reinstalling iTunes, checking drivers and updating them, disabling AV and firewall and trying again!!!

Isolate the issue on a different PC and identify where the fault lies@!!!

Specific error codes and resolutions
Error 6: All of the steps in this article apply to resolve this issue. Following iTunes for Windows: Troubleshooting security software frequently resolves this error. There may be third-party software installed that modifies your default packet size in Windows by inserting a TcpWindowSize entry into your Registry. If your default packet size is set incorrectly it can cause this error. Contact the manufacturer of the software that installed the packet size modification for assistance.

Error 9: This error occurs when the device unexpectedly drops off of the USB bus and communication stops. This can occur if the device is manually disconnected during the restore process. This issue can be resolved by performing USB isolation troubleshooting, using a different USB dock connector cable, trying another USB port, restoring on another computer, or by eliminating conflicts from third-party security software.

Error 13 and 14: These errors are typically resolved by performing one of more of the steps listed below:

Perform USB isolation troubleshooting, including a different USB port directly on the computer.
Put a USB 2.0 hub between the device and the computer.
Try a different USB 30-pin dock connector cable.
Eliminate third-party security software conflicts by following iTunes for Windows: Troubleshooting security software.
There may be third-party software installed that modifies your default packet size in Windows by inserting a TcpWindowSize entry into your Registry. If your default packet size is set incorrectly it can cause this error. Contact the manufacturer of the software that installed the packet size modification for assistance.
Connect your computer directly to your Internet source, bypassing any routers, hubs, or switches. You may need to restart your computer and modem to get online.
Try to restore from another known-good computer and network.
If you find an ASR error 1000 in the iPhone or iPod updater log file, that is an error decompressing and transferring the IPSW file that is downloaded during the restore. This error is frequently caused by third-party security software interference, a poor quality Internet connection resulting in a bad IPSW download, or a conflict on the USB bus.

Error 23, 28, 29, 1011, 1012, 1611: These errors may indicate a hardware issue with your device. Follow the steps in this article and also attempt to restore while connected to a known-good computer and network to isolate this issue to the device. If the IMEI or MAC address is missing or is a default value, this can also confirm a hardware issue.

Error 48: To resolve this error, follow the steps in this article. Also see the steps in "Restore using a new user account" above for .ipsw file locations.

Error 1015: This error is caused by attempts to downgrade the iPhone or iPod touch's software. This can occur when you attempt to restore using an older .ipsw file. Downgrading to a previous version is not supported. To resolve this issue, attempt to restore with the latest iPhone or iPod touch software available from Apple.

Error 1604: This error is often related to USB timing. Try changing USB ports, uninstalling and reinstalling USB ports, and other available USB troubleshooting steps (troubleshooting USB connections, device not recognized properly, computer won't recognize a FireWire or USB device). If you are using a dock, bypass it and connect directly to the USB 30-pin dock-connector cable. If the issue persists on a known-good computer, the device may need service.

If the issue is not resolved by USB isolation troubleshooting, and another computer is not available, try these steps to resolve the issue:

Connect iPhone to iTunes, confirm that the device is in Recovery Mode. If it's not in Recovery Mode, put it into Recovery Mode.
Restore and wait for error 1604.
When prompted click OK.
Close and re-open iTunes while iPhone remains connected.
iPhone should now be recognized in Recovery Mode again.
Try to restore again.
If the steps above do not resolve the issue, try restoring using a known-good USB cable, computer, and network connection.

Error 2000-2009: If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, reset the SMC, and then try to restore. Learn how to reset the SMC. If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore. If that does not resolve, try the USB issue-resolution steps and articles listed for Error 1604 above. If the issue continues, it may be related to conflicting security software.

Error 3000-3999: Error codes in the 3000 range generally mean that iTunes cannot contact the gs.apple.com server on ports 80 or 443. This may be because out-of-date or incorrectly configured security or firewall software is interfering, or due to your Internet proxy settings. If you are using a proxy, try without using one or with a known-good network. If that does not resolve the issue, follow iTunes for Windows: Troubleshooting security software issues.

Error 3004: If the steps listed in Error 3000-3999 do not resolve, you may be able to resolve an error 3004 by quitting iTunes and using the following command at the command line: dscacheutil -flushcache

Error 9807: If you see "Error 9807", open access to the following VeriSign servers:

evintl-ocsp.verisign.com
evsecure-ocsp.verisign.com
Error 9808: Follow the steps in iTunes Store: Unknown alert error message when connecting to resolve the issue. If those steps do not resolve the issue, or if the settings revert to their original values after the restart, then follow iTunes for Windows: Troubleshooting security software issues.

I too ,had this problem only mine was complicated by the fact that several months ago that my iphone took a dunk,which appparently no one at apple bothers to make note of .I was told to go see a "genius" and he did really not care to try anything more than i had already done because he & his trusty little flash light found the water damage evidence.That being said my phone had been perfect up until the time of syncing and updating and the world crashed down .
The sad part is i knew without a doubt that the water issue was NOT related at all ,and I have proven that fact I used the Quikpwn which like the rest of those that tried it found success!!!!!!!

I need to vent a bit that dear ol apple treated me as though i was trying to pull a fast one and get that new phone they had promised me,becuase my error 29 wasn't happening for the same reason the rest were,and the little genius dude even snickered about my story .All i really wanted was a fixed xphone we had paid $200 for ,oh yeh and we have 2 of them .So now I have fixed the phone myself with onformation from all of you and I say thank you!
I really could imagine people making these things up but when itunes keeps throwing error codes and well 100's or 1000's of people are facing the same issue becuase of a software glitch shame on you apple for taking the easy way instead of finding a fix for your glitch.
So we are debating at this point as to whether we are keeping these phones or are going to find phones that will actually be covered by our cell phone carrier and not just manufacturer. Husband gets his way there won't be another apple anything even close to home.

Thanks heaps - your a legend. Had a brand new 3GS to replace my old faithful 3G I had for 2 years. The new 3GS fell over as soon as I upgraded iTunes to 3.1.3.

Tried all sorts of websites for advice and yours was the only one that worked.

Ever thought about a job at Apple?

Haha. Thanks Caro, glad you were able to get your phone back up in action!

Hi all

I just wanted throw my own experience of error code 29 into the ring - I have had my 3gs open a few times (Im a bit of a stickler for punishing myself!) and this weekend I bought an entirely new backplate complete with all parts so I could just pop my mobo and screen in and have a shiny new backplate - first issue was that my songs all vanished instantly and my 3rd party apps didnt work. I went home, put the phone into restore but I got stuck in the error 29 loop! After trying and failing irecovery on my windows 7 PC, I tried **** raisers quickpwn solution - and it worked! Thank you so much!

However, I'm slightly concerned that when a new OS comes out, say 3.2 or 4.0, I'll have the same issue upgrading!

Any thoughts?

Well I've been struck down by this same issue.

Last night I went to sync my iphone to grab some pictures & iTunes says there is a update. So I click yes.. BIG MISTAKE as it turns out. The update gets 3/4 of the way through an whamm. 'A unknown error has occurred, you will need to restore your iPhone before you can use it.' So yae I just lost all my pics & audio recordings which I need.

So I goto do the restore & yep 3/4 way through 'Error 29'. So I tried all the crap that the apple support page tells you to do. Tried another PC with a fresh install of iTunes & updates downloaded again. Even formatted a PC with a brand spanking new copy of XP Pro.. No luck.

I'm reluctant to try the iRestore just at this point. I’m going to the retailer today to see what they know. I plan on showing them this thread as proof of this issue.

I’m warning all my work mates to not do the current iTunes update.

I must add that this phone is under 30days old & is not a 'jailbreak' phone.

Message was edited by: mrchrise

screw you apple and your 3gs tell all of us how to fix our error 29 so we can uses our phones. i guess i still have my 3g due to your wonderful 3gs that works os well lol

Just spoke with apple & I've got a appointment to see the service center in Robina (QLD Australia)on Saturday. They are simply replacing the phone. I guess Im happy to get a new phone but that still doesnt answer the question of why it happen in the first place.

I could try the iRestore & alike but I guss I'll be patient & get a new iPhone on Saturday.

Still ****** about loosing all my Pics etc.

Well people check you iTunes updates as they have a new 9.1 out. Not only that if you run a Diag check & then look at the log (No Phone Connected) you'll see that they have gone back to iPhone firmware 3.1.2

I just did the restore to see if anything had changed & Woo Hoo it fixed my iPhone. Its not in the recovery Error 29 loop any more. Looks like I dont need to got the Apple shop on Saturday!

i just came out from the same problem!, all i did to fix it was this, take the sim card out, put it on dfu mode, and restore it on itunes, then when de iphone shows the message about the sim card, just put it in, and it will b working again... (let itunes finnish,)WARNING , I LOST ALL THE PICS AND MUSIC!!APPS TOO, BUTI HAVE A WORKING IPHON AGAIN....

Hey guys I think I found out what's going on with the 3.1.3 update. It
is not wanting to update the baseband. For some reason I believe that the code for the 3.1.3 baseband update corrupt something for the update of the baseband

my reasoning for this is because I updated to 4.0 update and I got the same error and my baseband is still from 3.1.2

@TLeaf07... maybe you are on to something here. For the rest of us who may not know, can you tell us what the baseband is? Thx!

🙂
well the baseband is what controls the phone part of the phone, calling, data and etc. And i got stuck in the same stuff you guys were talking about.
I updated to 3.1.3 and boom! error 29, i knew irecovery can fix it. but now that i am on 4.0 my phone shuts off randomly! i know you are thinking because its beta it will do that. but i looked at my baseband from my about part from settings. And my baseband is still from 3.1.2!!!

So I think apple has something wrong with the 3g[s] firmware update for 3.1.3 because know my baseband is frozen and my warranty is gone :/
they need a fix asap

Interesting - my baseband is also a lower one, 5.12... I can also confirm the issue follows into OS 4.0 Beta 1 and using the Quickpwn method works to get out of the loop. So are you saying that removing the SIM card the error 29 does not appear??