Anybody ever had issues and unable to use multiple icloud backups for a restore due to some corruption? Story as follows...
Model is ipad pro 11" fall 2018 (256gb with LTE). Did overnight automatic update from 13.4->13.4.1. Woke up to find device with black screen, apple logo with progress bar under and progress bar at 99%. Waited. And waited. And waited, after about 8-10 hours and now worrying about screen burn in, hard reset. White screen with "swipe to upgrade" appears, completely unresponsive to touch input, soft reboots itself after about 60 seconds and goes back to swipe to upgrade screen and is stuck in perpetual loop.
Ok. Clearly the ipadOS update corrupted and I need a restore. No problem, I have icloud backups. DFU Mode -> Restore, seems to be working, allows me to set up face ID etc. Then of course I choose to restore from backup. Which it looks like it works, and then it restarts to black screen-apple logo-progress bar... makes it to 99% and.. see above. Same process. Hard reset results in swipe to upgrade loop. Ok. Recovery mode and I restore again. Try to use my icloud backup from a week prior. Same problem. Ok, restore again and this time lets set it up as a new ipad. Works fine. But I need my data so it's time to get crafty. Figure maybe this is a 13.4.1 issue and put the 13.5 public beta on it and then, rather than DFU mode restore, go to "erase all contents" and then try to restore from backup. No dice. Still in the swipe to upgrade loop. Happens using both my 4/26/20 and my 4/20/20 icloud backups. Can't downgrade to 13.4 since apple stopped signing that one, so that's out of the question.
I was able to successfully restore using a backup from 11/2019 when I had to swap the device under warranty for a hardware issue... So that worked. That was a backup made from a different (although identical hardware configuration) ipad pro. But now I'm 5 months behind on my backups (which ultimately I think is probably just app configuration since everything else (photos/notes/etc) is on icloud).
Not sure how to troubleshoot this any further, apple support has been very interested in the story but ultimately completely unhelpful.
Model is ipad pro 11" fall 2018 (256gb with LTE). Did overnight automatic update from 13.4->13.4.1. Woke up to find device with black screen, apple logo with progress bar under and progress bar at 99%. Waited. And waited. And waited, after about 8-10 hours and now worrying about screen burn in, hard reset. White screen with "swipe to upgrade" appears, completely unresponsive to touch input, soft reboots itself after about 60 seconds and goes back to swipe to upgrade screen and is stuck in perpetual loop.
Ok. Clearly the ipadOS update corrupted and I need a restore. No problem, I have icloud backups. DFU Mode -> Restore, seems to be working, allows me to set up face ID etc. Then of course I choose to restore from backup. Which it looks like it works, and then it restarts to black screen-apple logo-progress bar... makes it to 99% and.. see above. Same process. Hard reset results in swipe to upgrade loop. Ok. Recovery mode and I restore again. Try to use my icloud backup from a week prior. Same problem. Ok, restore again and this time lets set it up as a new ipad. Works fine. But I need my data so it's time to get crafty. Figure maybe this is a 13.4.1 issue and put the 13.5 public beta on it and then, rather than DFU mode restore, go to "erase all contents" and then try to restore from backup. No dice. Still in the swipe to upgrade loop. Happens using both my 4/26/20 and my 4/20/20 icloud backups. Can't downgrade to 13.4 since apple stopped signing that one, so that's out of the question.
I was able to successfully restore using a backup from 11/2019 when I had to swap the device under warranty for a hardware issue... So that worked. That was a backup made from a different (although identical hardware configuration) ipad pro. But now I'm 5 months behind on my backups (which ultimately I think is probably just app configuration since everything else (photos/notes/etc) is on icloud).
Not sure how to troubleshoot this any further, apple support has been very interested in the story but ultimately completely unhelpful.