Receiving an error code (1109) in the middle of the restore on iPhone 11

I have resolved the issue. It appears to be a problem with ISPs or routers preventing connections to Apple servers. While restoring from the Apple Devices app, you need to be connected to a mobile hotspot. It worked for me, and I hope it helps you as well.

I should also add, while I have had issues with restore of iOS 18.0.1 and 18.1, I have no issues restoring the same devices to iOS 17.7, which fortunately is still being signed by Apple for the moment. So there definitely seems to be a problem with iOS 18 ipsw files.

Later I did also do a ipconfig /release and ipconfig /renew plus a ipconfig /flushdns. Probably a two or three Windows restarts too during the whole session.

I kept getting the message "the network connection was reset", I kept insisting, closing iTunes, disconnecting the iPhone cable, turning it off, connecting it again, turning it off while connected, then setting it again in recovery mode. I wanted to try and put in it DFU mode but it seems I did not succeed even once as I never saw in iTune "phone in DFU mode" nor a permanent black screen on the device Complete Guide: How to Activate DFU Mode on iPhone for Efficient iOS Recovery.

Other variables I played with were using different USB-A and C ports, non-Apple lightning cable and original Apple lightning cable.

My internet connection was good all the time, wifi.

Eventually, after many, many attempts, one download completed correctly again and it did restore the iPhone without failing at about 50-55% bar progress like the previous times. It was finally back 'alive' again at the Hello OOBE stage and out of the recovery mode.

Loads of perserverance. I began investigating whether using ipsw files (I did not know that existed) could be applicable as fix in production but in the end it was not necessary.

Also, I found a workaround for this yesterday. I reinstalled iTunes instead of using the Apple Devices app. iTunes was not detecting iPhone 15 devices when the Apple-issued USB-C to USB-C cable was in use, which is why I originally switched to the Apple Devices app, as this was detecting iPhone 15 devices when the Apple-issued USB-C to USB-C cable was in use. However I purchased both a generic USB-C to USB-A data cable AND a USB-C Socket to USB-A Plug Adaptor (thankfully my non-Apple PC still has USB-A ports), and when using either, iTunes was now able to detect the iPhone 15 and update/restore/DFU to iOS 18.1 via ipsw file works without issue. So the issue is definitely with the Apple Devices app with respect to the device update/restore/DFU error 1109 and also, iTunes cannot detect devices connected via the Apple-issued USB-C to USB-C cable (or perhaps USB-C to USB-C cables generally, although it can detect earlier devices connected via Lighting to USB-C cable), at least with my PC under both Windows 11 and Windows 10 before that. Hope this helps somebody :)

Another workaround I've found that worked was using a VPN to update the iPhone using Apple Devices.

In my case, I used PIA (Private Internet Access) on my Windows 11 PC and reattempted to update my iPhone 15 Pro to 18.1, after that never once saw any error code appear, especially the 1109 error while the update was installing.

I figured this would be useful for folks that don't have a Wi-Fi Hot-Spot available to them to connect to to work around this silly issue.

My ISP is Xfinity and I'm wondering if other folks are using Xfinity as well while encountering this error.

I hope this helps

After trying 3 different computers with the newest Windows 11 Pro 24H2 and NO result in restoring my iPhone 13 Pro, I tried on an old Asus PC with the latest Windows 10 Pro 22H2.

None of the 3 PC´s with 24H2 were able to do the job, they all ended with error 1109!

The old stationary Asus with an Intel E8400 processor from year 2008 and Windows 10 Pro 22H2 did the job flawlessly.

I had this issue with an iPhone 15 whilst doing a restore using Apple Devices on a PC after I forgot the passcode to the phone. After going through this thread and macobserver, I finally successfully restored the phone by doing the following:

1. connected my PC to a hotspot from another phone
2. restart Apple Devices
3. forced restart on my iphone and connected the phone to my PC using a usb-c to usb-a cable (the usb-c to usb-c that came with the phone does work for the restore as at this post)
4. Followed the restore prompt instructions on Apple Devices
5. With a lot of prayers after more than 7 attempts, the restore was successful and I can now use my iPhone

I wasn't able to use iTunes as suggested by others; it didn't give me the restore/update option.

Hope this helps someone that like me, switch off when instructions start to get a bit technical.

We encountered this exact issue yesterday. My partner locked herself out of her iPhone 13, and we encountered error 1109 about halfway through the restore.

Mobile signal coverage is terrible where we live (rural England) so we couldn't try the hotspot method.

We tried:

VPN - It didn't work.

via iTunes - It didn't recognise the device.

via Apple Devices - Recognised but errored at halfway.

Eventually, I changed the DNS to Google (8.8.8.8 / 8.8.4.4) and tried again... and it worked.

I have no idea whether or not changing the DNS solved it or it if was just plain dumb luck but this did it.

So final working method for us was:

Windows 11

USB A to Lightning (non-official cable)

Connected via WiFi

VPN Off

DNS to 8.8.8.8 / 8.8.4.4

So after 4 hours of messing around it was finally done.

Apple, you guys are awesome, but this whole process is terrible and seems to be affecting so many users, ya need to do better.

I was running into this issue as well, I tried with separate Windows 11 machines using the Apple Devices application and it gave me errors, (1109).06B4.0000 and (4017).0648.0000. Thinking it was a network or an Intune configuration I tried hotspot and a personal Windows 11 device and nothing. It only worked on a test Windows 10 machine so I think it might be some incompatibility with a Windows 11 update or something. Thank you, community, for the different ideas and possible solutions.

Error code (1109).06B4.0000 on restore & (75).067E.004B on update--issues with Iphone 12 to install 18.2.1 IOS update. I was using Apple devices on window 11 to install. The install would fail many times. I changed to my other PC with windows 10- issue fixed and IOS updated using windows 10 version and Apple Device app on PC! I did restore vs. update. Hope this works for others.

Hello world,

at me the same issue occured while restore my iPhone 15.

The update-log was showing that:

[21:39:27.0848] Completed checkpoint id: 0x66F (commit_sep_os)

[21:39:27.0848] Started checkpoint id: 0x6B4 (await_system_image_invert_retry)

[21:39:27.0848] <Restore Device 000001F863743500>: operation 13 progress 0

[21:40:08.0548] amai: _AMSupportHttpMessageSendSyncNoRetry: CFURLConnectionSendSynchronousRequest() error: The request timed out. (kCFErrorDomainCFNetwork -1001)

[21:40:08.0548] amai: _AMSupportHttpMessageSendSyncRetry: HTTP request failed (status=16)

[21:40:08.0548] amai: _AMSupportHttpMessageSendSyncRetry: HTTP request failed, httpResponseHeader is NULL

[21:40:08.0548] amai: _AMSupportHttpMessageSendSyncRetry: HTTP server returned unexpected HTTP response code -1

[21:40:08.0548] amai: _AMSupportHttpMessageSendSyncRetry: -------------------- Attempt 2 of 3 failed, sleeping for 2 seconds --------------------

[21:41:11.0221] amai: _AMSupportHttpMessageSendSyncNoRetry: CFURLConnectionSendSynchronousRequest() error: The request timed out. (kCFErrorDomainCFNetwork -1001)

[21:41:11.0221] amai: _AMSupportHttpMessageSendSyncRetry: HTTP request failed (status=16)

[21:41:11.0221] amai: _AMSupportHttpMessageSendSyncRetry: HTTP request failed, httpResponseHeader is NULL

[21:41:11.0221] amai: _AMSupportHttpMessageSendSyncRetry: HTTP server returned unexpected HTTP response code -1

[21:41:11.0221] amai: _AMSupportHttpMessageSendSyncRetry: !!!!!!!!!!!!!!!!!!!!!!!!!! Retries exhausted on attempt 3 !!!!!!!!!!!!!!!!!!!!!!!!!!

[21:41:11.0221] amai: AMSupportHttpSendSync: _AMSupportHttpMessageSendSyncRetry returned 16

[21:41:11.0221] sock 5556: closed

[21:41:11.0273] AsyncDataRequestMsg: StreamedImageDecryptionKey: Switching to background queue to prevent restore queue deadlock

[21:41:11.0275] sock 6492: connected to [usbmux_3]:49168

[21:41:11.0275] WKMS: No authorization token available for wkms.sd.apple.com; failing

[21:41:11.0276] sock 6492: closed

[21:41:11.0277] device returned CFError with code 1109

[21:41:11.0277] dumping CFError returned by restored:

[21:41:11.0277] CFError domain:AMRestoreErrorDomain code:1109 description:Error retrieving WKMS decryption key

[21:41:11.0277] Restore completed, status: 1109

[21:41:11.0277] Elapsed time (in seconds): 274

[21:41:11.0277] Restore Checkpoint Fingerprint: 06B4.0000

[21:41:11.0277] Failure Description:

[21:41:11.0277] Depth:0 Code:-1 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 1109

[21:41:11.0277] Depth:1 Code:1109 Error:Failed to handle message type StatusMsg (Unrecognized error (1109))

[21:41:11.0277] Depth:2 Code:1109 Error:Error retrieving WKMS decryption key

[21:41:11.0277] Sending acknowledgement that final status was received

[21:41:11.0277] device restore output unavailable

[21:41:11.0277] AMRAuthInstallDeletePersonalizedBundle

[21:41:11.0277] preserved personalized bundle: (null)

[21:41:11.0277] <Restore Device 000001F863743500>: Restore failed (result = 1109)

[21:41:11.0277] Can't send dump_console command since device is not in recovery mode

[21:41:11.0277] Finished RestoreOS Restore Phase: Failed

[21:41:11.0277] State Machine Dump, status:ERROR - [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:0 (current state)]

[21:41:11.0278] Changing state from 'Restoring' to 'Error'

[21:41:11.0278] State is now set to error: AMRestorePerformRestoreModeRestoreWithError failed with error: 1109

[21:41:11.0278] ASR progress: Could not read all of client request

[21:41:11.0278] ASR progress: Finished

[21:41:11.0278] sock 3904: received error waiting for EOF: 10054

[21:41:11.0278] sock 3904: closed

the process stopped at 59%

Due to the case of missing a different hotspot, I used the Fixppo app and did finally a iOS downgrade to version 18.2 successfully.

Thereafter I did a restore from my latest backup from the iCloud.

done and dusted

regards ;)

Hi all,

I rarely contribute to these forums but I feel compelled to today after losing 4-5 hours of my day off trying to solve this infuriating problem.

My issue arose after downloading Apple Music and Apple Devices on my PC running Windows 11. I wanted to sync my iPhone 14 Music with my PC's new Apple Music - it had been ages since I did this but clearly iTunes for Windows cannot do anything music-wise any more. Anyway...while on Apple Devices for the syncing I saw an option to update my iPhone's iOS software. I clicked it without thinking and what an error that was! Once it got underway, it started rebooting my phone and on the status bar it got pas the stages such as firmware but when it got to software it paused, thought about it then rejected the process with this famous error message and number.

Unsure what else to do, I performed a hard reset, tried it again same issue.

"The iphone could not be restored. Unknown error occurred (1109). 06B4.0000"

I am currently in Qatar and usually do everything via NordVPN so I turned that off on my PC, no joy. I tried the Apple Support page suggestions for this error - turned off my AVG antivirus software. No joy again. Tried deleting cookies, browsing history etc, restarted the PC, hard reset the phone again...still no joy!

I came on here and tried the method suggested of changing the DNS. Still no joy.

Thank you so much for the person who recommended the github website - looking through there, I saw the option of using 3uTools. I tried this method first (copied and pasted from https://github.com/nooneknowspeter/iOS-issues?tab=readme-ov-file):

3u Tools Method

• Install 3uTools
• Connect your phone and enter the Pro Scan section on 3uTools
• It will prompt you to go into DFU with valid instructions
• Add the ipsw file and install

I got very hopeful following these steps - but it got halfway through then I received a new error code: unable to restore idevice(-75)

So back to Google this new one, and I came across a thread from this support thread (copied and pasted from ERROR: Unable to restore iDevice(-75). - Apple Community)

(Quoting Community user bra-itchy)

Just like alway iPhone never provides enough to solve the problem they create.. so I had to Beat around till I found the solution... and fortunately I did ... that error is mostly vague and sometimes revolves around insufficient power.. buh what they don’t tell u is when making a restoration your battery health is also verified.. and if it’s subpar you could keep getting this obnoxious error code... buh thank God for 3utools

Assuming u know what u are doing and are already in recovery or dfu mode

1. connect to the computer where voltage is sufficient

2. ⁠open 3utools and select Smart Flash (It on the top bar at the time of when I was typing this)

3. ⁠select quick flash and check the “Fix battery health” box. Of course you’d have to either download or import your required firmware to proceed..

4. ⁠This it, click flash and sit back and watch yet another genius fix apples “cough cough” intentional problems “cough cough”

Your welcome

Aaaand it finally worked!!

As long as you have a recent back-up of your iPhone on your iCloud to use once you eventually get back onto your phone, this method may well work for you too.

I am never touching Apple Apps via the Microsoft store again!!!! Apple - you really need to resolve this, I have wasted hours of my precious free time on this today. And now I have to sign back into all my apps, reset my wallet up etc etc. :-(

I had the same problem (both on an iPhone (iPhone 12) and an iPad (iPad 8th generation)), I used different computers but I could not solve it.

When we talked to Apple Support, they asked me to do / did not check the following;

1. The PC you are using must be Windows 10 and above,

2. The latest version of iTunes or the Apple Devices application must be installed and you must do this installation from the official Microsoft Store application,

3. There should be no restrictions on the Internet connection you are using and there should be no additional protocols such as VPN,

4. The cable you are using must be an original Apple cable.

I tried everything written above completely and on three different PCs, but I kept getting the error.

The error occurs in two different ways,

1. If you do it in iTunes, the restore starts and after a while iTunes suddenly closes; the process stops.

2. If you do it in the Apple Devices application, the restore starts and after a while it gives this error; the process stops.

After experiencing this several times, I decided to do this process on a Mac as a last resort and completed the process on Mac without any problems.

I think this problem is currently caused by a bug in Windows computers accessing Apple servers or writing data to Apple devices, and this may also be related to the latest iOS / iPadOS.

If you continue to experience this problem, I recommend using a Mac computer for the fastest and most accurate solution.

I hope it was helpful.

Wasted most of my day trying to update to iOS 18.3 this morning and it bricked my phone. It took me over 4 hours to get it recovered.  It’s still doing a restore of my backup. Only 19.2 GB to go. Thanks Apple 😤

Yes.. this method worked for me for restoring ipad 10.. I had exact same errors 1109 & then later -75.. don't know why Apple has messed up 18.3 restore files.. Also Apple devices app from Microsoft store is not very helpful.. this 3U application is far better to restore Apple devices such as iPad.. I had exact same errors 1109 & then later -75..

After doing Quick Flash & selected restore Battery option, things worked like a charm..

Thanks a lot for posting this method..

Yes.. one of the reason why I had restore the iPad was because for some reason iPad did not recognize the 6 digit code which I had set up previously.. I was using my ipad after a break of 1 month.. did that somehow made iPad forget my code? I do not know.. I have set up same code again.. at least this time it is working... lets see..

Thanks a lot for posting above method