iPhone update error 100 06a6 0064

Hey everyone,

I really need help with this because my iPhone 13 Pro Max has basically locked me out and I’m trying to avoid losing all my data.

What happened:

My iPhone was running iOS 18 and was almost out of storage (2-3gb left).

I tried updating to iOS 26 through my Mac because the phone didn’t have enough space to update itself.

The update failed and now the device is stuck in Recovery Mode (the laptop + cable screen). I made my last backup 11 Months ago and the data in-between are incredibly important to me. I just wanted to give a quick update and never expected it to give me such a headache...

What I’ve tried:

  • Tried “Update” through Finder multiple times → always fails with Error 100
  • Tried different USB ports and different Macs → same error
  • Didn’t press “Restore” (I can’t lose the data)
  • Didn’t enter DFU (screen always shows standard Recovery logo)

Went to an Apple Store → they didn’t even connect the device, just said “restore it”

iPhone 13 Pro Max, iOS 18

Posted on Feb 24, 2026 8:25 AM

Reply

Similar questions

24 replies

Feb 25, 2026 2:03 AM in response to ishaq347

ishaq347 wrote:

Is there no fix in development or solution in the pipeline? I can wait, my data is really important.

We wouldn't know what Apple has in development, but I am certain that this is not something that requires any new work.

This is just one of the dangers in not using iCloud for backups and data management. The two or three dollars a month could have prevented this.


If you disconnected the phone and tried forced restart and it is still in Recovery Mode, and you have no archived backup on the Mac or iCloud then the data is gone.


https://support.apple.com/guide/iphone/force-restart-iphone-iph8903c3ee6/ios


Feb 25, 2026 3:28 AM in response to ishaq347

Re: “In that case, why are we allowed to perform an update if we don't have enough memory?”


Possibly there was a bug in the software to do the update. Bugs do happen, despite efforts to prevent and to get rid of them. But with so little free storage, you may have been tempting fate even before you tried to do the update.


Re: “in theory, why not overwrite the old firmware to install the new one and avoid the problem?”


Why not? If something happens while you are in the middle of the update, your device may turn into a useless brick - one that does not have the ability to even try to load a new system, because you just destroyed the only working copy of the code the device needs to load a new system.

Feb 25, 2026 3:57 AM in response to ishaq347

No one here can fix your bug, if it is one. If that’s your goal, contact Apple Support. If you’re in the US, please call  1-800-MY-APPLE, or outside the US, consult the support articles below. In Canada, call 1-800-263-3394.


Contact Apple for support and service - Apple Support


Genius Bar Reservation and Apple Support Options - Apple


Explore Service Locations


Official Apple Support



Feb 25, 2026 2:26 AM in response to LD150

So Apple creates a product that can malfunction and cause you to lose all your data as a result, but the problem is because I don't pay for an iCloud subscription? Your concept opens Pandora's box. Since we don't have iCloud, we have a product that doesn't work, and another day it will be AppleCare, and then AppleX and AppleY. I'm willing to admit my mistake in not having a backup, but not the fact that I have to pay for a product that malfunctions and then get blamed for it.

Feb 25, 2026 2:42 AM in response to ishaq347

You were running on a knife’s edge when it came to free storage. You were running on a knife’s edge, without any recent backup of the data that you claim is so valuable. Then you tried to force an iOS update anyway, despite the lack of free space!


As for an iCloud+ subscription, that would have let you use automatic iCloud backups and iCloud synchronization to protect your data. But if you were absolutely opposed to paying for iCloud, you could have manually backed up your iPhone to your Mac or Windows PC. It would have taken more discipline to do this on a regular basis, but you could have done it.


It is not Apple’s fault that you failed EITHER to do an iCloud backup OR to do a local one for eleven months.

Feb 25, 2026 2:51 AM in response to Servant of Cats

In that case, why are we allowed to perform an update if we don't have enough memory? In theory, either you don't allow the update to happen, or you don't get stuck on an error at the end of the process. I don't know how it works in detail, but in theory, why not overwrite the old firmware to install the new one and avoid the problem? But I see that the only answer you have for me is just ‘Why don't you pay?’ Are you serious?

Feb 25, 2026 3:06 AM in response to ishaq347

Re: “But I see that the only answer you have for me is just ‘Why don't you pay?’ Are you serious?”


You are misrepresenting what I said. I mentioned that you also had the option to back up your iPhone to a Mac or a Windows PC. That would not have required an iCloud+ subscription.


You claim that your data is valuable, but you took no steps to back it up for eleven months. Failed updates are not the only way that you can lose your data when you keep it all in one basket. If a thief stole your iPhone, there was a hardware malfunction, or you forgot your passcode, you would have been in the same boat.


I get it that you are upset over losing your data, but you should be upset at yourself for not protecting it.

Feb 25, 2026 3:17 AM in response to Servant of Cats

if a thief stole your iPhone, there was a hardware malfunction, or you forgot your passcode, you would have been in the same boat.


In this case, it's not a third-party problem but an Apple problem that I'm facing. If my phone or something else had been stolen, I would never have posted here and would just be crying in a corner. But right now, I just can't update my phone because of a **** error, and I'm stuck in recovery mode with no solution, even though it's a software problem and not a thief or anything else.

Feb 25, 2026 7:05 AM in response to LD150


Sorry, I'm not trying to annoy anyone. I just want to understand why this bug exists and why, from what I've seen, it's been around for two or three years and still hasn't been fixed. As a developer, I also don't understand the logic of referring the problem back to the customer when there's an issue with the product. The responses I've received so far are not solutions. Normally, if a customer raises an issue, we should try to understand why and work to find a solution. Our job is to create new features, and it's normal for bugs to occur along the way, but debugging is also part of our job, and every customer is important. I would therefore like this bug to be reported to a higher level so that a solution can be found.

LD150 wrote:

You are not talking to Apple here, and it is pointless baiting hard-working volunteers with your rhetoric..

If the following restore using recovery method does not work on a proper computer like a Mac then I am afraid your phone is busted.

https://support.apple.com/en-gb/108969


Feb 25, 2026 7:47 AM in response to LD150

Thank you, I understand perfectly, but I don't see how your analogy could help move things forward and improve the aircraft. Nevertheless, I understand your point of view, which could be useful in educating pilots.



LD150 wrote:

You obviously didn't read or didn't understand my aeroplane analogy. You chose not to buy a parachute here.
A mechanical failure of the plane would not come back at you, but the consequences of hitting the ground at 120mph would.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

iPhone update error 100 06a6 0064

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.