ANY ONE KNOW WHAT IS ERROR 3 IN ITUNES WHEN I TRY TO RESTORE IPHONE 5 TO IOS 7 IT STUCKS IN THE END AND AFTER 30 MIN THIS COME OUT "UNKNOWN ERROR 3" CAN SOME ONE HELP ME PLZ

Hi Kennethyoung,

No, my problem was the iphone 4 stuck in apple logo loop. Reading posts in this forum I found I had to do the restore iphone from itunes, when I did the restoration via itunes and the phone did not work. I found this post and check the upgrade logs that are out here and most people have the same error as mine. Many have error -1

unable to convert ramrod error 1004

It says it is a hardware problem.

But it is not, succeed in making it run my iphone doing the steps mentioned above.

When to end the FW upgrade, when the status bar to end this, you have to insert and remove the sim card several times, 4 or 5 times and that makes the restoration completed successfully. I do the upgrade in itunes in dfu mode because the phone would not start and there are only detected an iphone that has to be restored.

This is the last message when the restoration didnt came succesfully.

[23:05:14.0078] amai: AMAuthInstallBasebandHandleUpdaterStatus: commandAccepted: NO

[23:05:14.0079] amai: AMAuthInstallBasebandHandleUpdaterStatus: outputDict: <CFBasicHash 0E2A2CF8 [72E5907C]>{type = mutable dict, count = 1,

[23:05:14.0079] entries =>

[23:05:14.0079] 12 : <CFString 05D081D0 [72E5907C]>{contents = "done"} = <CFBoolean 72E5ACA8 [72E5907C]>{value = false}

[23:05:14.0079] }

[23:05:14.0079]

[23:05:14.0091] device returned CFError with code -1

[23:05:14.0092] dumping CFError returned by restored:

[23:05:14.0092] CFError domain:AMRestoreErrorDomain code:-1 description:failed to update device firmware

[23:05:14.0093] CFError domain:AMRestoreErrorDomain code:-1 description:ramrod firmware update failed

[23:05:14.0095] CFError domain:RamrodErrorDomain code:1004 description:update_baseband: failed to perform next stage

[23:05:14.0096] CFError domain:BBUpdater code:16 description:(null)

[23:05:14.0098] Sending acknowledgement that final status was received

[23:05:14.0285] Restore completed, status:16

[23:05:14.0285] Failure Description:

[23:05:14.0285] Depth:0 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: -1

[23:05:14.0285] Depth:1 Error:The operation couldn\U2019t be completed. (AMRestoreErrorDomain error -1 - Failed to handle message type StatusMsg)

[23:05:14.0285] Depth:2 Error:The operation couldn\U2019t be completed. (AMRestoreErrorDomain error -1 - failed to update device firmware)

[23:05:14.0285] Depth:3 Error:The operation couldn\U2019t be completed. (AMRestoreErrorDomain error -1 - ramrod firmware update failed)

[23:05:14.0285] Depth:4 Error:The operation couldn\U2019t be completed. (RamrodErrorDomain error 1004 - update_baseband: failed to perform next stage)

[23:05:14.0285] Depth:5 Error:Exception at :0:

[23:05:14.0285] - kBBUReturnTimedOut(8)/16: Pinging timed out

[23:05:14.0285]

And this is the log when the restoration finish correctly.

[17:43:29.0256] amai: AMAuthInstallBasebandHandleUpdaterStatus: commandAccepted: YES

[17:43:29.0257] amai: AMAuthInstallBasebandHandleUpdaterStatus: outputDict: <CFBasicHash 06143FB0 [72BC907C]>{type = mutable dict, count = 1,

[17:43:29.0257] entries =>

[17:43:29.0257] 12 : <CFString 060595F0 [72BC907C]>{contents = "done"} = <CFBoolean 72BCACA0 [72BC907C]>{value = true}

[17:43:29.0257] }

[17:43:29.0257]

[17:43:29.0262] <Restore Device 06AB15E0>: operation 17 progress -1

[17:43:29.0332] <Restore Device 06AB15E0>: operation 49 progress -1

[17:43:55.0054] <Restore Device 06AB15E0>: operation 25 progress -1

[17:43:55.0190] <Restore Device 06AB15E0>: operation 51 progress -1

[17:44:17.0795] <Restore Device 06AB15E0>: operation 29 progress -1

[17:44:17.0845] <Restore Device 06AB15E0>: operation 29 progress -1

[17:44:17.0883] Restore completed, status:0

Hi, Kennethyoung,

I have not mentioned the fact that I had done all the manipulations without a SIM-card present. I've installed it just after the 2nd trick with the freezer and successfull activation then. It showed me that cellular module works OK while iPad stays cool. Then I've turned the airplane mode on and removed the SIM-card. Thus, the SIM-card doesn't affect the problem.

Today I've tried to turn the airplane mode off with warm device. It started all over again: 3-4 minutes of work and reboot. The interesting fact is that when I turned the airplane mode back on after reboot, it didn't stop to reboot. So I've put the device into the freezer again 😁 and now it woks properly while the airplane mode is on. Btw, bluetooth works as well.

I also enclose some screenshots of error reports sent by the device. You may find them interesting (do not pay attention to russian language).

Just got off the phone with a senior supervisor at apple that forwarded my logs to apple engineers. She basically said its a hardware fault and said I had to pay £166 for a replacement device.

No at all happy.

Hi V74,

Sounds like you may have a real hardware issue with the cellular modem chip if you can physically feel the iDevice getting warm after 3-4 minutes then starting the reboot loop. There is a temperature sensor in the iPhone that will shut the iDevice down when it gets too warm, but usually it will display a custom screenshot that verbalizes that fact before the iDevice shuts down. You don't mention seeing that screen, so I'm not sure that the device is getting too warm, but rather something in the celluar modem chip is causing the reboot. I don't know anything more you can try at this point since you don't mention being a developer, in which case I could recommend you try the lastest developer 7.1.x beta and see if that brings your iDevice cellular service back to life. You should search this forum and see if there is another thread addressing the issue that you are now seeing, since you have solved the Error (3) issue, at least for now. Keep us appraised of your status.

Hey kennethyoung, just got an iPhone 5 with the same error #3... just wanna to upload my log so you may search for anything unusual... thanks for all the effort on this matter!

Here's the log:

https://dl.dropboxusercontent.com/u/16324761/iPhoneUpdater%207.log

Regards,

Bruno.

I am having the same issue with my 4S. Phone was continually searching for the network. Apple suggested restoring the phone. Uninstalled, reinstalled itunes to do a restore (with anti virus off, updates loaded on computer, all other USB unplugged) and could not restore phone. Repeated error 3 messages. I think I've tried at least 10 times now. Error 3 always comes up at the very end stage of the firmware phase- with a few millimeters left on the status bar. So frustrating- this phone was a warranty replacement for yet another hardware problem/failed iPhone 4S and so this phone was only covered for 90 days - it's only 6 months old and appears to be dead. Not happy 😠 We are a big Apple family- and an unhappy Apple family now with two failed 4S devices within a year's time. Thank you for all the information and for those of you who are pursuing this further (and know how to do so!). I did try the freezer method but it didn't work at first pass- will try freezing for more time (impatiently tried after 5 minutes)!

Hi KennethYoung,

Ok i'll keep an eye on the forum but theres literally nothing else I can do to help this issue now. Iv'e been to the depths of the earth and back and got no where. From trying all your fixes and speaking to a high representive in apple which has forwarded logs to engineers which said I have a hardware fault.

I appreciate your continuous input into this ever so tiresome error.

Thanks

Pelling

I tried the freezer trick a while ago and it didn't work for me. The restore did not work when leaving it in the freezer either.

Yesterday I got an Eureka-moment that maybe my freezer wasn't cold enough. And i bumped the fridge up from coldness "3" to "6", meaning it got colder.

Now if I take the iPad out of the freezer and try to restore I still get error 3.

But if I leave it in the fridge I get random errors that look like 400x (4005, 4013 etc) and error 200x.

I've searched the webb for information about these errors and they seem to be related to the usb connection, tried different cables but still same errors.

Anyone has any ideas if this can be fixed?

Has anyone else tried to make the freezer colder and restoring the iPad/iPhone?

kennethyoung... i went through the entire post.. here are the links of the restore log files generated. The following file was geneated when i tried to restore my ipad 3 A1430 using latest .ipsw file (iPad3,3_7.0.4_11B554a_Restore.ipsw) downloaded by iTunes. it gave me unknown error 3

https://www.dropbox.com/s/mlnzjnjsijcx7ii/iPadUpdater%2028.log

I also tried to use iPad3,3_6.1.3_10B329_Restore.ipsw for restore. The logs generated during this restore are in the following link. This time it gave me error 3194. I am not sure what is happening and why?

https://www.dropbox.com/s/43vquv4kje2r3c9/iPadUpdater%2029.log

appreciate your help to save my ipad from dying... .

Well I found the solution to my error 3 and error 1. I simply place the iPad on an online auction site and sold it. Which is where I first purchased it when it was working perfectly. Even made a little profit. Full details were disclosed when sold. I figured that by the time Apple acknowledged the problem the iPad 8 would be out and this one would no longer be supported thus still making it an expensive paper weight.

Good luck to the rest of you!!!! Hope y'all find a solution!!

Hi All,

I just met with my contact at Apple regarding the Error (3) issue. I as stated earlier, I can only share bits and pieces about what is being done on this issue. Here is my interpretation of what I can share openly.

"Apple team(s) are aware of the issue. It has been duplicated inside Apple, the cause has been studied and is understood. Software solutions are being considered but the decision to roll out a fix or not, has yet been made."

NOTE: The words above are 'solely mine' and in no way reflect any position Apple or anyone at Apple is taking on this issue. My sole goal in sharing this information with the people in this thread is to let you know that, in my opinion, Apple takes all product issues a customer has with their devices seriously and would like to fix every problem anyone has with an Apple device, but sadly, it is not always possible or practical to do so.

From my 30 years experience in high volume manufacturing, with any high volume product, an "issue" has to rise to a minimum "defect level" before resources are (1) put into analyzing the issue, then (2) coming up with a solution(s) to the issue, then (3) determining whether or not the risk/benefit ratio is "across the line" to roll out a "solution" to the issue.

This thread has done an excellent job of getting Apple to get through steps (1) and (2). Right now, its not clear if the volume of device failures is sufficient "at this time" to come out on the "solution roll out" side of step (3).

Nobody wants to have their $700-$1000 device become a "brick" due to an Apple iOS update. Apple I'm sure doesnt' want that either. However, with any "solution" to a problem, there are "risks" that the "solution" could cause a failure rate equal to or higher than that currently in existence. We have some 40K hits on this thread, and there are likely multiples of people who have this issue that don't know about this thread but have bricked Error (3) devices, but that's a math guessing game.

My contact at Apple is doing what they can to convince the "powers that be" that this issue is likely to only get worse with time, due the the basic "physics" of Flash chip technology, and that Apple should "roll out" a "solution". We need this threads help to make this happen.

How? Call AppleCare and have a bug report filed on this problem on your device. Do so before next Tuesday. AppleCare is the "key" to pushing through (3) above. Fundamentally, we need more people making "NOISE". The squeaky wheel gets the grease and we need to be "more squeaky". I've done all I can at this point and pushing it across the goal line, is now in the hands of those in this thread willing to pick up the phone and call AppleCare and register a complaint, and DO IT BEFORE NEXT TUESDAY! (don't ask me why).

Just called them and tried to explain the error 3. Of course they tell me to go through a series of pointless tasks that I've obviously already tried to fix the problem...useless. One time, the guy actually told me to call Microsoft and inquire about error 3! Lol, these people are clueless. They all seem to be under the impression that this issue is a problem with iTunes or the computer, rather than the iphone it self. Anyways, I cant seem to get them to do anything due to the fact that i dont have access to serial number or imei. The phone doesnt boot, so i can get it from the settings app, and i no longer have the packaging so thats also a no go.

Also, some info: Ive got an iPhone 4s, tried restoring/updating via iTunes, got error 3, and phone will only boot into recovery mode now. Heres the log if anyones interested: http://pastebin.com/d0fH0Nnn

Ive tried freezing the phone for 40 minutes and restoring, but it didnt do the trick. Ive also tried freezing the phone for about a week, and that has not worked either.

Hey kennethyoung, I've read and aknolowdged your last post, even posted a small thing on facebook to try to get more attention to our cause till next tuesday... anyways, I was getting a little nervous about this timeframe and tryed to redo to restore process, this time after a 45min into the freezer, and I almost thought it would go through ** it didn't... 😟

I'm attaching the log file so you may have a look and maybe see anything different...

https://www.dropbox.com/s/50hazc9gt9cf831/iPhoneUpdater%209.log

Thanks for all the help on that matter!

Regards,

Bruno

I just wanted to thank you very much, I to had this error and tried everything out there to fix it, saw your post and figured i would try it. It worked! i put in freezer for 40 mins, with rice, paper towel and rice. took it out started the restore immediately. i also placed the ipad on a table, i figured if i held it, it might heat back up to fast. at the point of firm ware was slowest, actually it went through twice itself, at one point i thought it wasnt going to go any further but it did! thank you so much for this post! 😀