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

10:56:04.610: Checkpoint started id: 0x6B4 (await_system_image_invert_retry)

STACKED on 50%with this info

How to update my phone

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 this same error when trying to restore an iPad 7 via Apple Devices app on Windows. I resolved it by restarted my PC and trying again. I remember a pop-up saying that I needed to restart my computer while it was in the middle of restoring the iPad which I thought didn’t make sense so I ignored it. But it turns out this is why I kept getting the error.

^thiss!!

Saved me also. I tried to VPN suggested & connected to United States (East Coast) VPN and it worked wonders!