Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iPhone XS dead (?) after update to 18.7.3 - help appreciated!

ShiftHappens

ShiftHappens

macrumors member
Original poster
Dec 6, 2022
84
130
My son has been using my old XS for a while and yesterday I tried to install the 18.7.3 update (not sure from what exact version, but I'd guess 18.7.2 or 18.7.1).
Seems the update failed and the phone got stuck in a boot loop:
apple logo for 2s -> black screen for 5 seconds -> apple logo for 2s -> black screen for 5s -> ...

Forced restart (vol up -> vol down -> side button) did not help, so tried connecting it to one of my Macs (running 15.7.3) and went into recovery mode (vol up -> vol down -> side button until "cable and computer icons").
Tried both update and restore, but getting the "The iPhone “iPhone” could not be updated. Declined to authorize this image on this device for this user." error message (or "...could not be restored...").

EDIT: First I tried using my own (macOS) account, but since the error message was talking about user, I created an account for my son, using his iCloud account, but the same error...

My next idea was to go into DFU mode, but I can't get there... Phone goes black as per boot loop above, so screen going black is not helping. Also tried to enter DFU mode using timing, like: vol up -> vol down -> side button for 10s -> side button and volume down for 5s -> vol down for 10s, but I only get into recovery mode, which again doesn't help...

Any ideas?
 
  • Like
Reactions: Hans300
You need a new signed ipsw restore file. For 18.7.3 for the XS you can find a download directly from Apple here: https://updates.cdn-apple.com/2025F...one11,4,iPhone11,6_18.7.3_22H217_Restore.ipsw

Note the URL starting with https://updates.cdn-apple.com. You can verify independently (via WHOIS search for example) that updates.cdn-apple.com belongs to Apple and hence that this URL is genuine. These ipsw files are the official iOS firmware restore files and only genuine ones from Apple will install in the first place.

The problem you likely have is that whatever ipsw restore file you have either downloaded manually or your Mac has cached automatically is too old and no longer recognized as a genuine one from Apple and so authorizing the restore/install fails. Apple does this regularly, on purpose, to restrict users to restoring only the newest versions of iOS.

You should try the update option with the new file first as a successful installation will save all your data on the iPhone. The restore function might reset the device to factory defaults but it might be necessary to make the iPhone work again.
 
  • Like
  • Love
Reactions: arc of the universe, winxmac and ShiftHappens
Thanks!
I'll try that, but it would be weird if that's the case... I've never had any iPhone connected to this particular Mac before, so there shouldn't be any cached iOS updates and the image was downloaded to the Mac when I entered recovery mode...
Not sure how to select a manually downloaded image in the recovery mode screen, but we'll se if I can figure it out.
 
Definitely unusual, i'd try the new file above and see if that works. Rarely though, sometimes a software update will make an unknown hardware failure evident when it tries to install....based on your description, I don't think that's what's happening here, but still a slight possibility.
 
  • Like
Reactions: ShiftHappens
OK - tried with little success... At least I got another error message (translated, so may differ from what you'd get in English): "The iPhone “iPhone” could not be updated. An unknown error occurred (4013)."

ChatGPT is telling me this is likely due to HW issues (battery, storage, PMIC or lightning port).
So maybe it's time to say goodbye to my trusty old XS... 😢
 
One thought... When I just let the Mac try to update (or restore), it suggests 18.7.2 (not 18.7.3)... Maybe I should try to get the ipsw for that instead..? @okkibs - Do you have a link for that version as well (I haven't been able to find it myself...)?
 
bogdanw said:
Try with ‎Apple Configurator https://apps.apple.com/app/apple-configurator/id1037126344
Click to expand...
Thanks - hadn't thought of that, but didn't work unfortunately...
Screenshot 2025-12-22 at 10.42.54.png
 
You get that message when using the 18.7.3_22H217_Restore.ipsw or with the version downloaded by Apple Configurator?

You can download the 18.7.2 ipsw , but according to https://ipsw.dev/product/version/iPhone11,2
and https://appledb.dev/device/iPhone-XS.html it’s no longer signed by Apple.

Just to exclude it as a potential cause, install MobileDeviceOnDemand.pkg & CoreTypes.pkg and reboot your Mac.

 
  • Like
Reactions: ShiftHappens
That is what I see too, only the 18.7.3 ipsw that I have linked above is signed by Apple. Any authorization error messages are caused by using the wrong ipsw file. The one I linked is correct for that iPhone model and if it does not install then we have to look at that error. That would be error 4013. I think the Apple restore process where it downloads a file in the background isn’t up to date and is downloading 18.7.2 which cannot be used anymore.

Anyway, I do not know what causes the 4013 error, but a workaround for restore issues can be to use a Windows machine. Copy the ipsw to a Windows machine and select it manually for a restore. You’ll need the iTunes software or perhaps the Apple devices software that’s newer, I am unsure as I don’t use Windows at all.

People report that restores failing on macOS can be successful on Windows.

There is a good chance though that a hardware defect caused the update to fail in the first place leading to the boot loop. I suspect that you will not be able to recover the iPhone. If this is about data recovery then there are businesses that can disassemble the device and attempt to replace defective components in order to get the device to boot one last time so you can copy off any data.

For now I’d try suggestions for error 4013 if you can find any and attempt to use a Windows machine for the restore. You’ll need the ipsw file I linked. There is no other ipsw file I can find for your device.

Also you should really try to get the iPhone into DFU mode. And you might want to use a brand new original lightning cable in case yours is of questionable quality and age and might no longer work correctly.
 
  • Like
  • Love
Reactions: arc of the universe and ShiftHappens
  • Like
Reactions: ShiftHappens
klasma said:
18.7.2 (and down to 18.7.0) can still be signed using delayed OTA (https://dhinakg.github.io/delayed-otas.html) for iPhone XS/XR, but it would require MDM enrollment of the iPhone first, which I guess is not possible if the device isn’t working normally.
Click to expand...
I don’t think Delayed OTA allows installation of OTA updates that are no longer signed by Apple.
The profile just sets forceDelayedSoftwareUpdates to true and enforcedSoftwareUpdateDelay to 49 days. After installing the profile, the user will not see updates that are newer than 49 days, but not if Apple has already removed them.

enforcedSoftwareUpdateDelay https://developer.apple.com/documentation/devicemanagement/restrictions
 
  • Like
Reactions: ShiftHappens
bogdanw said:
I don’t think Delayed OTA allows installation of OTA updates that are no longer signed by Apple.
Click to expand...
Not of OTA updates, but of IPSWs. I’ve used this in the past to install otherwise expired versions.

bogdanw said:
The profile just sets forceDelayedSoftwareUpdates to true and enforcedSoftwareUpdateDelay to 49 days. After installing the profile, the user will not see updates that are newer than 49 days, but not if Apple has already removed them.
Click to expand...
You can configure up to 90 days. Apple then still signs those IPSW installations when the profile is present.
 
  • Like
Reactions: ShiftHappens
bogdanw said:
You get that message when using the 18.7.3_22H217_Restore.ipsw or with the version downloaded by Apple Configurator?

You can download the 18.7.2 ipsw , but according to https://ipsw.dev/product/version/iPhone11,2
and https://appledb.dev/device/iPhone-XS.html it’s no longer signed by Apple.

Just to exclude it as a potential cause, install MobileDeviceOnDemand.pkg & CoreTypes.pkg and reboot your Mac.

Click to expand...
That came when I just let Configurator do it’s thing - I didn’t tell it to use the 18.7.3 ipsw, so not sure what it tried to use… I’ll try what you suggested when I get some time after Christmas… Thanks for your input 🙏
 
okkibs said:
People report that restores failing on macOS can be successful on Windows.
Click to expand...
Unfortunately, the only WinDos machine I’ve got access to is seriously locked down (BeyondTrust etc.) so can’t use that…
okkibs said:
Also you should really try to get the iPhone into DFU mode. And you might want to use a brand new original lightning cable in case yours is of questionable quality and age and might no longer work correctly.
Click to expand...
Have tried a couple of lightning cables, but neither one would be called new…
May have some newer ones at home I can try after the holidays…
 
The weirdest thing just happened...
Back home after the holidays and started off moving my son back to the XR he had before he moved to my old XS.
Next, I was going to try installing the 18.7.3 ipsw I previously downloaded on the XS using Apple Configurator from my Tahoe AS MBP (the one I tried from before was a Sequoia i5 Mini). After finally finding a USB-C to Lightning cable in mint condition, I started Configurator and connected the XS to the MBP, but before I even went into recovery mode or saw any iPhone in Configurator, the XS started up! The only thing I've done that would be considered a change since my last, failed, tries was to remove the SIM card (moving it to the XR)...
It's still on 18.7.2, but I've reinitiated the upgrade to 18.7.3 (on the XS itself - not from Configurator)... Will let you know how it goes!
Fingers crossed...
 
The upgrade worked fine and the SIM card is back in the XS!
No idea what magic solved the issue, but thank you all for sharing your wisdom in this thread 🙏
 
  • Like
Reactions: iEB
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back