AMRestoreErrorDomain error 1 - Failed to handle baseband update status message

Question

Level 1

5 points

AMRestoreErrorDomain error 1 - Failed to handle baseband update status message

Hi,

My iPhone5 started not working, that is couldn't use it as a phone. I attached it to iTunes on my pc to backup the photos etc before taking it to Apple Store in Beijing. As it's not bought in China they cannot help.

When I connected my phone to iTunes it suggested an update was required and downloaded the following iPhone5,2_7.1.2_11D257_Restore.ipsw

However, the phone failed to update properly through iTunes, with error 1. Below is the last section of the iPhone Updater Log. Another post (update failed with message AMRestoreErrorDomain error 1 - Failed to handle baseband update status messag) suggests the problem is because the phone was not 'factory' unlocked. I bought this phone legitimately in Dubai as a factory unlocked phone in about May or June 2013. So just over one year ago....

Please advise what is wrong with the baseband chipid? Do you need to see more of the error log?

Thanks,
Andy

<Restore Device 06A1CA50>: operation 16 progress -1

[02:56:59.0413] <Restore Device 06A1CA50>: operation 16 progress -1

[02:57:02.0456] requested restore behavior: Erase

[02:57:02.0470] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:02.0471] <Restore Device 06A1CA50>: operation 27 progress -1

[02:57:03.0415] <Restore Device 06A1CA50>: operation 27 progress -1

[02:57:03.0505] <Restore Device 06A1CA50>: operation 35 progress -1

[02:57:03.0505] requested restore behavior: Erase

[02:57:03.0507] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0510] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0513] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0516] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0519] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0523] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0526] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0529] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0532] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0535] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0538] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.

[02:57:03.0815] <Restore Device 06A1CA50>: operation 18 progress 0

[02:57:04.0068] <Restore Device 06A1CA50>: operation 18 progress 16

[02:57:04.0072] <Restore Device 06A1CA50>: operation 18 progress 25

[02:57:04.0088] <Restore Device 06A1CA50>: operation 18 progress 33

[02:57:04.0104] <Restore Device 06A1CA50>: operation 18 progress 41

[02:57:04.0121] <Restore Device 06A1CA50>: operation 18 progress 50

[02:57:04.0137] <Restore Device 06A1CA50>: operation 18 progress 58

[02:57:04.0154] <Restore Device 06A1CA50>: operation 18 progress 66

[02:57:04.0171] <Restore Device 06A1CA50>: operation 18 progress 75

[02:57:04.0187] <Restore Device 06A1CA50>: operation 18 progress 83

[02:57:04.0204] <Restore Device 06A1CA50>: operation 18 progress 91

[02:57:08.0394] <Restore Device 06A1CA50>: operation 18 progress 100

[02:57:08.0404] <Restore Device 06A1CA50>: operation 46 progress -1

[02:57:08.0421] <Restore Device 06A1CA50>: operation 46 progress -1

[02:57:08.0437] <Restore Device 06A1CA50>: operation 19 progress -1

[02:57:19.0840] amai: AMAuthInstallBasebandHandleUpdaterStatus: commandAccepted: NO

[02:57:19.0840] amai: AMAuthInstallBasebandHandleUpdaterStatus: outputDict is NULL

[02:57:19.0841] AMRAuthInstallDeletePersonalizedBundle

[02:57:19.0990] Restore completed, status:1

[02:57:19.0990] Failure Description:

[02:57:19.0990] Depth:0 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 1

[02:57:19.0990] Depth:1 Error:The operation couldn’t be completed. (AMRestoreErrorDomain error 1 - Failed to handle baseband update status message)

Windows XP Pro

Posted on Jul 21, 2014 8:27 PM

Reply

Answer 1

CarlAVII

Community Specialist

Jul 24, 2014 11:59 AM in response to yesmaybe

Hello yesmaybe,

The information below provides further information regarding this error and steps that can help resolve said error.

Check for hardware issues

Related errors: 1, 3, 10, 11, 12, 13, 14, 16, 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37, 40, 1000, 1002, 1004, 1011, 1012, 1014, 1667, or 1669.

These errors mean that your device or computer may have a hardware issue that's preventing the update or restore from completing.

Check that your security software and settings aren't preventing your device from communicating with the Apple update server.

Then try to restore your iOS device two more times while connected with a cable, computer, and network you know are good.

Confirm that your security software and settings are allowing communication between your device and update servers.

If you still see the error message when you update or restore, contact Apple support.

Resolve iOS update and restore errors

http://support.apple.com/kb/TS3694

Cheers,

Allen

Reply

Answer 2

Mar 3, 2015 1:04 PM in response to yesmaybe

I too suffered this fate on a customer's iPhone 5c that I repaired a screen on. I ended up just replacing their iPhone and later fixed this problem on the original. Of course, I also then realized I was not at fault for the issue and it was caused by the damage (drop and/or water) that I had repaired the screen for.

If you search around you'll find a myriad of things to try from Apple supported solutions to extreme reballing baseband chip. Apple suggests updating iTunes and OS, try a different (oem) USB cable, disconnect other peripherals.

I tried seemingly everything, at least everything that was easy. I tried DFU mode, along with using a pre-downloaded Apple firmware and "Option+Click" the "Update" button in iTunes. I tried on both a Mac and Windows computer. I tried disconnecting the battery and attempting restore from DFU multiple times.

At some point I felt it was time to take desperate action. I do not have the equipment to reball (comepletely re-solder) the baseband chip but I do have a good heat gun. So, I pulled the motherboard out and removed the EMI/heat shield from the lower portion of the motherboard (below the SIM reader). Protected the surrounding chips with aluminum tape and took a lot of heat to the baseband chip. The chip is the one with Qualcomm MDM9615 printed on it. I let everything cool down and then put it all back together. Hooked it up in regular Restore mode (not DFU mode), the mode where you get the connect to iTunes screen. The restore completed successfully, where previously it would error out at verifying firmware (with error 1 - Failed to handle baseband update status message).

Now it picks up AT&T signal, where it wouldn't before.

I strongly advise against attempting this, unless you have no other choice and are familiar with electronics and doing these sort of things. None of this is going to be advised or accepted by Apple. If you try this and further damage the device you can bet Apple will surely turn you away if they wouldn't have already.

If you do attempt to hot air reflow the baseband chip; please do yourself a favor and scour the web for all the information you can to be sure you get the right chip and avoid other mistakes.

Reply