Halfway through a restore your iPhone stops dead and hands you Unknown error (1109), sometimes with a second code like 06B4.0000 underneath. I know that is a horrible place to be, because the phone is usually sitting there unusable while you read this.
One thing is worth knowing before you buy a cable or book a repair. Apple files 1109 under network connectivity, not hardware.
Seven fixes, and the first four are all about the path between your computer and Apple.
1. Read what Apple actually says this error is
Thirty seconds, and it redirects everything you do next.
Apple, in If you see Error 3194, Error 1109, or other network connectivity errors: "If your computer can't communicate with Apple software update servers, you might see one of these messages." Error 1109 is on that list, alongside Error 3194, Error 17 and Error 1639.
So this is a conversation between your computer and Apple, and something is interrupting it. Not a dead battery. Not a bad screen. Not a failing logic board.
That single line explains why the fixes that work are DNS settings and firewalls rather than parts.
2. Turn off your security software, which Apple names first
Apple's own opening move, and it fixed this for at least two owners.
Apple: "If you have a firewall or security software installed on your computer, they might block access to some Apple software update servers." Then: "Make sure that your security software or firewall allows access to Apple software update servers." And plainly: "Configure or temporarily uninstall your security software."
Jim9781234 found it exactly there. Disabling the Norton 360 Smart Firewall cleared their 1109 error, which was showing with the code 130A.0000.
MrPancakes721 was told by Apple Support to disable all firewalls temporarily. The restore then completed. They turned the protection back on afterwards, which is the right way round.
⚠️ Turn your security software back on the moment the restore finishes. This is a temporary measure for one job.
3. Change your DNS, which is the fix owners found and Apple does not print
This is the one to try if rung 2 changed nothing, and it is the most reported success on the biggest thread about this error.
Fyrstar posted it after four hours of failed attempts with a VPN and with iTunes: changing DNS to Google's servers, 8.8.8.8 and 8.8.4.4, cleared the error.
ivica162 confirmed the same change worked, and noted they had been on Cisco OpenDNS before it.
Why it fits: Apple's own page says proxies, firewalls and other network security measures cause these errors. A filtering DNS service is exactly that. Plenty of home routers and security suites now run one, and you may never have chosen it.
Change DNS on the computer doing the restore, not on your iPhone. On a Mac it is in Network settings, under the active connection. On Windows it is in the adapter's IPv4 properties.
4. Take the router out of the path
Apple's next step, and it is more specific than it first looks.
Apple: "Bypass your Internet router. Some routers might block iTunes from accessing the update server." The instruction that follows is exact: "Disconnect from your wired or wireless router and use an Ethernet cable to connect your computer directly to your modem." Then: "Restart your computer and modem."
Apple adds the wider version too: "Proxies, firewalls, and other network security measures can cause these errors. If necessary, find a different network connection to restore the device. For example, if you're restoring at work, try to restore at home or on a friend's computer and network."
vash83 did the network version of that and it worked. A VPN to the United States cleared it. They traced the problem to their internet provider, a Japanese mobile network.
A phone hotspot is the quickest test of this whole theory. Different network, two minutes, no settings changed on the computer.
5. Check the hosts file, because an old edit blocks the server permanently
Narrower, and it is the cause that never fixes itself.
Apple: "After you update your Mac or update iTunes or Apple Devices to the latest version, check the hosts file to make sure your computer can contact the update server."
What you are looking for is specific. Apple: "Use the arrow keys to find an entry containing 'gs.apple.com'. If you don't see any entry containing gs.apple.com, then the hosts file isn't related to the issue."
That entry usually arrives from an old jailbreak tool, an ad blocker, or a guide somebody followed years ago. It quietly points Apple's activation server at nothing. Every restore then fails the same way until you remove it.
Follow Apple's steps on that page rather than editing the file from memory, because a hosts file with a mistake in it breaks more than restores.
6. Change the computer, not the phone
Now the rung that feels like giving up and is actually diagnostic.
Three owners on the same thread got there. Scottlk traced the fault to Windows and finished the update on a Mac laptop. Christopher_5309 had a personal PC fail repeatedly, and an Apple Store's Mac completed the restore. LexK25 narrowed it to a Windows build. Windows 11 24H2 was the problem, and an older version worked.
chetanovsky stayed on Windows 11 and simply switched software, moving from the Apple Devices app to iTunes after several failed restores. That one is worth trying before you go looking for another computer.
If a second machine works, you have proved the phone is fine, which is the most valuable thing on this page. And if the phone will not appear on the second computer at all, that is a different problem and iPhone not showing up in Finder covers it.
7. What to do about the third-party flashing tools
The last rung, and it exists because the biggest thread is full of them.
Two owners, Shznzu and Michael Hall5, reported clearing this with a Windows tool called 3uTools using a quick flash, in one case with a battery health option ticked.
I am reporting that rather than recommending it, and I want to be clear about why. Those tools write firmware outside Apple's process. Some of their options alter reported battery data. And a failed flash on a phone that is already stuck leaves you far worse off than you are now.
Every fix above is reversible. That one is not. Try the network, the firewall, the DNS and a second computer first. Still stuck after all that? An Apple Store appointment costs nothing to book.
If your phone is stuck on the update screen rather than failing with a code, iPhone stuck on Verifying Update is the page you want.
What does not help
- Buying a new cable first. The error is about server communication, and no owner on the thread traced it to a cable.
- Repeating the restore unchanged. The thread has 110 replies and nobody got through by trying again.
- Blaming the phone's battery or storage. Apple's classification does not mention either.
- Waiting for an iOS release. The failure is on the computer's side of the connection.
Status: iOS 26.6.1, checked 19 August 2026. Apple classifies 1109 as a network connectivity error. The DNS and firewall fixes are owner-confirmed across a thread carrying 1,406 Me Too votes.
What does error 1109 mean on iPhone?
Apple lists it as one of the messages you see when your computer cannot communicate with Apple software update servers. It is a network error rather than a fault with the phone, the cable or the battery.
How do I fix error 1109 when restoring my iPhone?
Work outwards from the computer. Disable security software temporarily, change DNS to 8.8.8.8 and 8.8.4.4, connect straight to the modem or use a different network, then check the hosts file for a gs.apple.com entry.
Why does 1109 come with 06B4.0000?
The second code is an additional identifier shown alongside the error. Owners report several variants including 130A.0000, and the troubleshooting is the same because Apple classifies all of them as connectivity errors.
Does error 1109 mean my iPhone is broken?
Not on Apple's own classification. Several owners completed the same restore on a different computer or a different network with no change to the phone at all.
The Short Version
- Apple files 1109 under your computer failing to reach its update servers.
- Security software and firewalls are Apple's first suspect, and two owners confirmed it.
- Changing DNS to 8.8.8.8 and 8.8.4.4 is the most reported owner fix.
- Apple tells you to bypass the router and connect straight to the modem.
- A gs.apple.com line in the hosts file blocks every restore until removed.
- Several owners finished the same restore on a different computer.
- Third-party flashing tools are reported but not recommended here.
Where to Next
The most expensive mistake with this error is treating it as hardware. People buy cables, book repairs and start talking about logic boards over a message that Apple itself files under network connectivity.
Work outwards instead. Security software. Then DNS. Then the network, then the computer. A phone hotspot tests half of that in two minutes.
If DNS was the one for you, I would like to know what you were using before you changed it. Two owners named a filtering service they had forgotten was there, and if that is the common thread it would be worth saying much louder than anyone currently does.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.