iPad Pro 10.5" continually reboots after 13.4.1 update.

Looking back at other forums it would appear this problem as been going on since 2016 on earlier models of iPad.

Well said chum. Probably find they will remove your post.

Thank you, Steve, for this update. Let's hope they figure something out in the next update. Fingers crossed!

Agree completely. Glad that you can post such frustration on our behalf. I certainly can not.

Welcome to the world of madness. Hope you have deep pockets to buy a new iPad.

Software version: from 13.4.1 to 13.6

Software Build No: 18A5332f

Full Model Number: MPHGLL/A

Model Version : A1709

[Edited by Moderator]

Yeah, I have had the exact same issue. Like the rest of you it occurred after iOS 13.4.3 (or what ever the most recent) installed. I have gone through everything, including DFU. Nothing helped. I did go ahead and download iOS 13.5 beta (which apparently Apple is rushing to get to market). Unfortunately I am experiencing only a slight improvement, in that I can now occasionally get 10 min before the iPad resorts to restarting every 45-90 seconds.

I did this, but I still have the problem.

While It was a good suggestion, it is highly concerning that this is the “Apple Recommended” approach and it doesn’t work.

Has anyone who had this problem of restarts every 45-90 seconds found this suggestion worked for them?

i had Apple run diagnostics on the iPad remotely. They told me there was no hardware issue.

They then told me I could pay them $449 plus shipping to send it in and have them “fix it”.

I found that highly irritating that they want to charge me to fix a software problem that they caused.

Yes...

I request that all experiencing this issue provide/confirm the following information from Settings > About:

• Software Version (e.g., 13.4.1) and
• Software Build No. (e.g., 17D262) (to reveal the Build No - tap the Software Version field)

• Full Model Number (e.g. MPME2A/A) and
• Model Version (e.g., A1709) (to reveal the Version - tap the Model Number field)

This information is sought from owners so as to help identify any commonality between users iPads that are spontaneously rebooting.

In context of the Software Build No. it wouldn’t be the first time that Apple have updated a ‘build” release, but kept the same Software Version number. (NB: the examples in this request for information do not correspond with actual build versions).

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.