iPad Pro 10.5" continually reboots after 13.4.1 update.

Ok, I tried this. I Shutdown all apps (per instructions). Then I forced rebooted (per instructions). Then it restarted and I didn’t open any apps. I waited and it restarted on its own.

So check that off the list, this problem exists even when no apps are running.

I have no apps on my iPad and it still reboots every 3-5 minutes. I even started eliminating Apple apps that get loaded with the IOS. I have only 5 Apple apps still installed at the moment with no improvement. Had nothing to lose...

Thank you for taking this positive step.

May I respectfully request that you post this request to the following additional threads that address the very same issue. (There may be more):

“iPad crashing down after every 3-5 mins”

“iPad 13.4.1 update problem”

Thanks!

After talking to support person, who tried to get me to do i.e. reboot/reload. Twice they could not come up with a answer. They sent me a link to book my iPad in with an engineer but was then expecting me to foot the bill!!!!! Informed them i will not be paying to have my iPad repaired simple because the fault is with the Apple update. At this point i left the chat room because i had to go to work. Utterly disgusted with Apple. I have had iPhone since iPhone 1 and now on iPhone 11. Considering moving to another phone/tablet manufacturer. THANKS APPLE.

Every one here need to call Apple and make some serious noise about this issue!

iOS 13.5 did not fix this issue for all of you affected by this iPad boot loop issue!

LotusPilot is just another volunteer user here.

None of us here work for nor represent Apple, in any way!

He can’t fix this issue for anyone, if this is any type of hardware or software issue that Apple needs to address!

You all need to just CALL contact Apple and push this issue up to the highest support level employees possible!

EVERYONE WITH THIS ISSUE NEEDS TO MAKE SOME NOISE TO APPLE!

This is now time to start taking some serious action toward Apple on this issue.

I saw something similar happen with an issue with older iPads that ended with iOS 12.4.6 that still ended up with unresolved issues.

My mum's 2013, 1st gen iPad Air has some permanent issues that I found workaround fixes for these that Apple is never going to go back and fix.

So, everyone with this issue can still send constant feedback to Apple, but you all REALLY need to keep on top of Apple by actually calling Apple customer support, regardless of what you were told previously in a support call.

Best of Luck to Everyone affected by this!

[Edited by Moderator]

Thanks. The more data we can gather, the better.

Whilst this problem is affecting a significant number of users/devices, it is not affecting all devices within a model range. As such, data is the key to running this to ground. Whilst this data collection exercise will not directly resolve the problem, it may help to isolate possible cause.

Good engineering practice, in tracing faults in complex systems, is based upon empirical data - not unqualified speculation.

I don’t necessarily take that as bad news. 13.5 was rushed out to correct problems that affected many more users than apparently have our problem. Problems that were known much earlier than ours. I get the impression that 13.5 didn’t even make an attempt to address our problem, but that doesn’t mean a later version (13.5.1 ?) won’t.

Still, I am not holding my breath.

Other than being a customer of Apple, just like you, I don’t have a relationship with Apple. All contributors here are end-users of Apple devices. This platform is where users with technical problems can seek help from other experienced users.

As for the data that users with this reboot issue have been invited to provide, I am attempting to identify any pattern or correlation between devices that experience this problem. I am lucky in that I have access to multiple devices that are not affected by this issue - so more data to add to the mix.

Devices of similar model or specification are not necessarily manufactured in the same assembly plant. Internal components and sub assemblies come from a variety of source-manufacturers - and may have some influence on occurrence or susceptibility to this problem. Whilst end-users cannot readily identify these differences, a pattern may emerge that can be fed-back to Apple Support.

Software Version - 13.5

Software Build - 17F75

Model # MPF02LL/A

Model Version A1701

I had the same problem as everyone else with failure after updating to 13.4.1. I have been in touch with Apple on numerous occasions and have done a complete wipe and install of 13.4.1 numerous times, and recently to 13.5 with the same problems. It seems there are enough people here with the same issue, Apple should be helping out in some way.

I posted here a couple of days ago. Chatted (texted) again with Apple Support without success. I have a call scheduled for Saturday and Genius Bar on Wednesday.

Today the representative said that it could be a battery related problem, which i don't think is possible since all we have done is update to 13.4.1 or 13.5.

KEEP POSTING AND CALLING APPLE.

Tried the new update to no avail. My wife says it seems to be more prevalent when she turns a page when using kindle app. Hoping the Genius Bar is able to help you and then we can all visit when they fully open.

It’s sad that Apple is still trying to pin this on a hardware problem. They changed a parameter in 13.4.1 that caused our affected iPads to fault out repeatedly.

If you haven’t done so yet, PLEASE call Apple Support and request to speak to Advanced Support about your issue. The more people who complain, the better the chance that they’ll address this in the next update.

Hi, Everybody.

Has anyone tried just letting the battery in your iPad Pros fully drain until the iPad goes dead, then fully charge the iPad and then try using the iPad and see if the boot loop goes away, or not?

I tried to escalate the issue. Got to a second level specialist. She was not able to escalate the issue. Only goes to the 599$ replacement/repair. She's offering me a battery replacement to start with which is cheaper. I do feel it's working around the issue instead of dealing with it.

I’m working on that right now. The battery is down as far as I can get it, but there’s still a residual charge that powers the flashing red battery indicator/lightning cable icon when you hold the power button for a few seconds. I’d like to get it to zero, but there’s no easy way to do that. (Wish I had a reset button that would really disconnect the battery momentarily.) I’ll just keep trying to power on repeatedly until the icons stop coming up. Of course, there is a chance that the battery won’t charge back up after I get it to zero, but I don’t really have another choice right now.

So, my plan is to get the battery to zero, carefully clean the lightning connector with an artists brush and a little contact cleaner, charge it back up, then do another factory restore in DFU mode with an OEM Apple charging cable. (I’ve been using certified aftermarket cables to date. Maybe there’s a remote chance of incompatibility. I’ll rule that out too.)

I like the battery discharge idea. I read somewhere online where someone had some success in resolving a clock issue that way. Some of my analytics data indicates that there may be a difference between “user time” and “system time”, so maybe a complete battery drain down will fix the problem. I’ll report here with the results.

My plan is to get it t