iPad Pro Gen 2 10.5 constantly rebooting after updating from 13.3.1 to 13.4.1.

This is what happened to me and they requoted me saying that there was a bend in the ipad and that was responsible. So be prepared for that. Also if you haven't yet sent it off, take photos. If they end up requoting you and you choose for them to send it back instead, definitely video yourself unboxing it. I did this and thank god because they hadn't packaged it up properly, which could've caused further unseen damage, and because I had proof they issued an automatic replacement.

Few hours later, it's still working. I'm typing this from the iPad. Download the beta profile to get the third beta. That's what I did. Fingers crossed. 😁

Having this same issue with iPad Pro 10.5 and 13.4.1. Contacted support after going as far as a DFU restore and they said 'it must be hardware' and wanted to charge $449 to do a mail in repair. I balked because of all the google hits with folks having this same issue, and asked them to log that this only started happening for me after 13.4.1.

One of the google hits talked about making sure Analytics is turned on (Settings >> Privacy >> Analytics and Improvements >> Share iPad Analytics). I am getting panic-fulls when it reboots, and when the iPad comes back up I can drill down into the Analytics Data logs and the first lines of the panicString say "no successful checkins from com.apple.thermalmonitord in 180 seconds". Is that what others are seeing? Is that the right line to be looking at?

Also, it seems to me that the reboots only happen if the device is being used (so frustrating!). By that I mean if it reboots and I walk away frustrated, it wont reboot on its own unless I return and enter the passcode to wake it. Not sure if that's consistent with others' experience.

Net is that I'm not convinced this is a hardware problem, especially since I don't have a spare $449 to get it repaired...

Same problem, same results! iPad Pro 10.5 rebooting every 3 minutes immediately after installing 13.4.1, problem disappeared after re-installing 13.3.1, then reappeared after auto update to 13.5. Restores in DFU mode no help and either is installing 13.5.1. Same analytics results: no successful checkins from com.apple.thermalmointord in 180 seconds. This is clearly a result of the interaction of the 13.4.1 update on this model of iPad. Apple Support tried to help over several phone calls but ultimately offered a replacement for around AUS$700!

Did you actually call Apple and have this iPad boot loop issue escalated up to higher tier Apple support employees?

You can go above the initial contact, first tier support.

You can calmly ask to have this issue escalated up the product support chain all the way to engineering level support employees, if need be.

You need to keep doing this and you need to keep posting feedback until Apple finally gets the message that there is something wrong with their upgrades/updates that are bricking/severely disabling certain iPad Pro models.

Everyone affected needs to stay on top of this and keep hounding Apple with feedback posts and constant phone calls.

DO NOT USE THE CHAT SUPPORT!

CALL instead!.

If none of you do not keep trying to help yourself, by hounding Apple and staying on top of this issue, Apple may not do anything about this issue.

Everyone here is already a couple more updates in with no fix for this.

All of you need to stay vigilant and active with Apple on this issue or it will go ignored.

Best of Luck to ALL of you!

I politely but firmly kept stating that this fault occurred at the time of the update. I also referenced this thread, I referenced the Forbes and Apple Insider articles on the same issue. I also made sure that they knew the reboot loop didn't happen when the screen was locked. My ipad will quite happily stay on for hours if I don't unlock the screen. That confuses even the engineers! When on the phone and in store I explicitly stated that I was invoking my consumer rights as per the Consumer Rights Act 2015 (this must be done at the store you purchased from), that electrical goods must be fit for purpose for up to 6 years and that from the research I had done, tech experts conclude that any product purchased from Apple after 2013 should have a working life of at least 3yrs 4months. Keep putting the onus back on them to prove it isn't a fault caused by the update. They should waive the service fee. They did nothing in store for me but I do believe invoking my rights in store and having that logged on the system (book a genius bar appt online) helped me when I spoke to them over the phone again. You'll need to have the call escalated in order to do that but if you remain polite but firm it will help you eventually. Keep calling until you end up speaking with somebody more sympathetic. I had to sprak with some proper arsehole supervisors and then the last guy I was put through to was such a gent and authorised the free service immediately. Good luck!!

There are simply too few iPad Pro users affected by this boot loop issue for Apple to care and to take any time or research to look into and this issue and to come up with a software fix.

And, as I continually state, this maybe a combination hardware/software issue with no fix or resolution.

Could just be a small batch of defective iPad Pro models that always go through the supply chain.

This post has only 9 pages of users who reported this boot loop issue with repeat users posting here!

There is one more smaller, active post here the same, as well.

So, we're talking about, to date, what, maybe, MAYBE 100 users here who reported this issue to date?

Too few users affected by this for Apple to care and look into this issue and issue a fix for this in a software update.

Especially if it is both a hardware/software issue.

This is my guess as to why Apple is failing to do anything about this issue on a wider investigative level.

A very, VERY low percentage of users being affected.

Cheaper, I think to opt just to take the out of warranty, new or refurbished replacement, 10.5 inch iPad Pro and still use your existing accessories.

OR

Consider a refurbished 2018 model iPad Pro which would be 20%-30% cheaper OR even another option, the 10.5 inch iPad Air 3.

Same screen, same laminated and coated display/glass with the higher color gamut and tru-tone display and has an updated CPU. You still end up using all your existing accessories.

You just miss out on all the other “Pro” features, like the 120 Hz screen refresh rate, 1-3 GBs more of internal RAM, 4-speaker audio and the Apple Pencil 2.

Purely your decisions on what you want to do.

I don't have another $1500 to spend, so a $500-600 replacement iPad seems like a better deal to me and you go on using all your existing iPad accessories that you do not have to purchase all over again, too, if all of your existing accessories are all still in working order.

*Update:

Oh doom, the issue has returned. I was feeling triumphant and decided to stress test the device after my initial success.

I had been very gentle with the device since my relief of solving the reboot of doom in caution of agitating it and bricking the device again, but I needed to test it under normal use conditions and have it stuck in reboot again. What I did was to take the iPad out of its protective case and that triggered a reboot -- it was working fine immediately after fixing the issue while it was laying flat on a desk, standing stationary, or with minor movement up until this comparatively stronger jolt and force.

I was momentarily able to return it to a functional lock screen page by pressing on the iPad slightly but again I became overconfident and was less cautious with how I was holding the iPad. I held it by it lower right corner with no support at any other area, and that seemed to have retriggered the rebooting. Pushing the screen with my entire palm in its lower left or right quadrant sometime seems to allow it to load past the Apple boot logo, but only for two seconds or so before it bricks again.

-- this leads me to the inkling that this issue is somehow related to the thinness of the device and how holding it in a certain way without support to the rest of the device is dislodging/ bending the iPad internals and triggering some software check/ threshold that fails.

I will have to see if putting the device back into the freezer when I am near one will fix the problem by either bypassing a temperature check issue or compacting the internals due to cooling/ making the device more rigid.

IOS 14 Beta did the trick for me. I installed yesterday. Had to endure a couple of reboots but when it started to install, I closed the cover and in successfully installed. Mine says 14.0. I have been on my iPad for an hour so far this morning.

*Moderators: if you see reason for removing my post for containing confidential information or any other, please tell me what specifically in my post has violated community rules and why.

For those of you who have had your issues temporarily resolved with unofficial software, congratulations to you. I am glad to see that Apple is willing to listen to community feedback and are open to testing out solutions.

However, there are still those of us leftover who have yet had our issues resolved -- a small number of us, a large number of us? Who is vocal? How much of our presence is recognized and how much can our experiences be corroborated due to the militant post removal happening now. From my email logs, at least two additional people have posted about their unsuccessful attempts beside those whose have trace posts left stating their lack of success.

I am continuing to pursue our unresolved issue here because I believe the bootloops surfacing at the upgrade to iOS 13.4.1 is a wider issue beyond the specific error that has been fixed by the current unofficial software. Namely, Apple's increasing concern for 'consumer security,' and their measures to ascertain that: Software locking.

Some examples of Apple's previous 'security' implements that have wreaked havoc on their users' device and share very similar experience and progression to our current issue at hand:

Error 53: 'What is iPhone Error 53 and how do I avoid it?'

https://www.macworld.co.uk/feature/iphone/what-is-iphone-error-53-3634865/

iOS 12/ 13 Battery locking: 'Apple Is Locking iPhone Batteries to Discourage Repair'

https://www.ifixit.com/News/32343/apple-is-locking-batteries-to-iphones-now

I would like to posit that the errors (whether now solved or not) surfacing at the upgrading to official firmware 13.4.1 (13.4?) and above are due to a new round of Apple implementing 'security measures,' aka software locking. Whether this is intentional or 'accidental,' to reference Error 53, I won't comment.

How this may be a wider issue than the specific error that has been resolved, if my position is on the right track, is that kernal checking on iOs 13.4.1-13.6 on boot-up or while in use can throw the device into bootlooping, so long as the check fails in some way. Be it a failure to recognize the 'thermalmonitor' hardware component, or any other component coded to require a kernal check pass. -- meaning any failed checks can brick your device, whether the check fails due to a coding mistake, fails because it detects a 3rd-party repair component, or fails because a component (vital or accessory) may be dislodged due to use/ damage/ or failure by design susceptability. Why a select group of iPad Pro 10.5" user seem to be susceptible to a failed 'thermalmonitor' check while on iOs 13.4.1-13.6 I won't comment, though I wouldn't say it's far-fetched to induct that there are other susceptible components out there as well.

So please let us, those who have our issues yet resolved, share our input, experience and data. We just have to take care that we are commenting about the original errors encountered on official software iOS 13.4.1-13.6.

On the latest public release version 14.0.1 and am in contact with Apple about the issue, I was previously on13.7.1 and provided a screenshot of the panic-full...ips log that shows the thermalmonitord issue that causes our iPads to reboot after 3 minutes. After updating, the problem expectedly persists and they ran system diagnostics per engineering and I sent the logs for their review. Next follow up call is in a week or whenever engineering finishes their review. Will provide an update after the next call.

Yes, the stable version of 14.2 downloaded from ipsw.me, did a clean restored using finder, just restored back up data, download some apps, playing youtube video for 10 mins, no panic-fulls and com.apple.thermalmonitord

I just updated to 14.4. It's been up and running for almost 2 hours with no issues.

Just to add my voice and show solidarity (as I have in another thread https://discussions.apple.com/thread/251269923?answerId=252658194022), here is what I just sent via the feedback page linked by MichelPM (by the way, thanks MichelPM):

iPad Pro 10.5" (2017) working perfectly until iOS -> 13.4.1 update ~10 May.

On first use right after the update, the device restarted (I now know from Analytics Data) after exactly 180s up-time.

Second time I realised it was a problem caused by the update and started troubleshooting.

Day 1: I tried options, up to a full factory restore - no joy.

Looked at Settings > Privacy > Analytics & Improvements > Analytics Data (based on others' experiences): my Analytics Data contains panic-full... .ips and stacks+thermalmonitord... .ips error reports matching the restart times.

Day 2: I chatted online with Apple support - no joy, ultimately defaulting to: "This is a hardware issue..."

There may be a hardware fault, but affected devices worked until the 13.4.1 update!

Earlier there was a tip posted that recommended to put the iPad on a hard surface, then press down hard to the left of the home button. I did this with mine, and it did stop rebooting every 3 minutes. But, it was only a temporary fix as it began doing the reboot loop again a couple days later. So, for now, if I want to do anything on the iPad more than 3 minutes, I do the press down trick and it quits rebooting. That seems to indicate that there is a hardware issue, but it wasn't until 13.4.1 that the software was able to detect it. The sheer number of iPad 10.5's having the same issue would also indicate that this iPad model was defective at the factory. Is there a "lemon law" for electronics? The right thing for Apple to do would be to recall these iPads or replace them.