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

By the way, has anyone with a properly working 10.5. skipped both the 13.4x and 13.5x updates and gone straight to 13.6?

Would be VERY interesting to know if the reboot/bootloop problem appears then as well. Getting a true fix to repair the damage already done by 13.4/13.5 is one thing (and sadly, I'm not holding my breath), but there might be situations where you're buying a 2nd hand 10.5 that's running 13.3... do you update now or not?

Recently I had this exact problem and ended up not buying the device. Too much risk.

My 2017 iPad Pro started exhibiting the boot-loop problem when I updated to 13.4.1 back in April. Following this thread and the discovery that iOS14 Beta 3 solved the problem, I updated to that version. Problem solved. Decided to gamble and update to iOS 14 Beta 8 - and lost - boot-loop has returned. Either the source code change that solved the problem got dropped, or during a code review some manager asked "What's that code doing in here?" and it was deleted . . . regardless, iPad Pro is now a useless brick (for now) . . .

My story is much like the others, except I didn't waste time with DFU restores etc. after reading they didn't help. My 10.5 went from bootlooping to a total brick pretty quickly - in the end I couldn't even get it to turn itself on. Went to an authorized Apple service place here in my country and told them to try their hardest to get some life into the device. They managed to get the boot-up to the Apple logo stage ONCE... nothing else. They handed me back the iPad and told me to call Apple support. I did, and spent like an hour on the phone - making sure that they understood that this was a case where a perfectly functioning tablet went straight to **** after the 13.5 update.

In the end they told me to take the iPad to a service desk AGAIN, let them verify the situation, after which I could fill a kind of consumer complaint report that's part of the legislation in this country. I went there, had another hour long discussion with the guy at the counter as he filled up a ridiculously detailed repot of the situation. He also checked the device for any signs of physical damage, including barely visible scratches on the glass (there weren't any). I was told it would take a while to get to the next stage and there were no guarantees. So I went home.

To my surprise, the next day I got a message from the service desk, saying that my case had been solved. I went there and was promptly handed an identical refurb device, free of charge. It's been working absolutely perfectly (running 13.6) and I'm happy with it.

Feel really bad for anyone who had to pay out of pocket for a refurb or bought a new device after running out of options.

I'm very disappointed that Apple fixed it and ruined it in a matter of weeks. I feel they knew about it and decided not to fix it. It sucks. I'm disgusted by Apple's disregard for its loyal customers. Mine is still working because I turned off the update but this doesn't mean I'm going to stick with Apple. The beta will deactivate at some point. Before that happens, I'm planning ahead my transition to Samsung in the near future since I'm not that tied to the Apple ecosystem. Good luck for all of you having issue. My heart goes to you.

There is a new beta, please try and get back to us. My piece of advice: let the update download while the device is locked. The working beta on my device is really bad; battery life is utterly HORRIBLE.

Ssfc did you update to 14.0.1 and then update to beta 3? Apple engineering already within 6 hrs of having the data said it’s a hardware issue but if you updated to 14.0.1 and observed the issue and then updated to beta 3 and the issue was resolved then it’s hard to believe at that point that the issue is HW related. My service advisor is passing this thread along to engineering, let’s see if they review and actually figure it out.

Cool. It’s at least promising that it’s really not a hardware issue. Btw did the latest beta release translate into the official release of 14.0? Was wondering if there’s a chance of betas 3-5 being released as 14.3 to 14.5 down the line?

Hello. I'm "I have This Question Too" # 180. (Apple, if youre reading this, please take note of the Number of people with the same issues)

My Device: Ipad Pro 12.9 1st gen

Same story as others...updated to 13.4, reboots after 3 mins.

Researched and Googled for MONTHS (intermittently, as Ive Raged Quit several times...good thing I still have a backup iPad i can use as this iPad Pro is effectively a brick now)

Spent HOURS trying to fix it, like most people here did:

• Reset
• Restore (diff ways.. from Backup, Factory reset, DFU, from device OTA, from iTunes)
• Tried 14 beta (forgot which build no)
• updated to official 13.7, 14.0, 14.01, and now latest 14.1 ...still Reboots every 3 mins

I Searched and posted on diff forums, saw many other folks with the same issue (mostly on iPad Pros).

Finally found a tip to check Analytics... saw a bunch of "ThermalTempd" errors...

I Googled "ThermalTemoD" and found my way to a similar discussions.apple.com thread, posted there, and read about this thread, and now Im here :)

Want to add my voice to the many (like I noted, im # 180 in the growing list of people) who have this issue.

Also would like to share my own experience to add to the mix.. and maybe ask you guys if you have similar results.

My Experience and "3D Hack":

• When iPad reboots , I run the clock Timer and it will almost always reboot BEFORE it reaches 3 minutes (2 min+, like 2:40-2:50+ . It passed the 3 min mark only a couple of times before rebooting.

Anyone also do this "Timer Test"? Also, just curious..are your "3 minutes" experience an EXACT rule of 180 seconds? (it would make sense if its triggered by a timer) or just a rough estimate? Maybe i have a few seconds delay in setting up and activating the timer. IDK....

• I set the screen timer off to 15 min so screen wont black out, and just let it sit idly...still reboots within 3 minutes while doing absolutely nothing.

-So even doing absolutely NOTHING, or just a simple Timer, it will reboot.

• "my 3D hack" - in one of my many "experiments", I downloaded 3DMark Benchmark (SlingShot) on the iPad and ran it. It runs 3D modeling benchmarks for 4 mins. IPad didnt reboot! When Test was done, I ran it again. I kept doing this several times for a total running time of over 30 mins and not once did the iPad reboot.. So apparently when its doing "heavy lifting" of 3D graphics processing, it wont crash...but sitting idly by it will. (One would think the opposite would happen)

3D Graphics rendering makes the iPad hotter...so my observation is that when its running hot, its stable? And the error code for the crashes is called "THERMALMONITOd"? Somehow I think its related?

Would be helpful if some of you guys can try this out to see if you get similar results...

Because of the "Reboots every 3 min" issue, I couldn't download large files from the App Store, let alone the OTA update, because the downloads needs longer than 3 minutes. (my Internet isn't that fast) I was able to get around it by running the 3DMark app over and over again while things download in the background. Might help some of the folks here where Ive read they had problems downloading because of the Reboots. Please Try it and see if this "hack" will work on you too.

Conclusion: There are SO many of us here that experienced the ff:

• reboots every 3 minutes after updating to 13.4 and above
• have the "thermaltempd" error log

for it to be a coincidence that all of us have this same "hardware" issues. WHY ISNT APPLE LISTENING??? And What can we do about it?

KyleRyner wrote:

3D Graphics rendering makes the iPad hotter...so my observation is that when its running hot, its stable? And the error code for the crashes is called "THERMALMONITOd"? • Somehow I think its related?

Just like to add, this seems to go against the "put iPad in Freezer so its cold and wont reboot" fix/theory. (and Yes, I read ALL 20 PAGES of this thread)

I also tried downloading a 3D Racing game (download took a while, but I was able to do it it the background while I ran the 3DMark app).

I played the 3D Racing game and iPad is stable while im Racing (doing 3D rendering) for 15+ minutes. But when after a race, and its in the Menu Screen (Score, Options for Next Game) where its not doing any heavy 3D rendering and I just leave it there, it will reboot within minutes. It will only be stable when I do actual 3D racing (where the GPU is taxed) I would have test it longer, but im not a big fan of Racing and I suck at it...lol.

Can anyone suggest other intensive 3D rendering games/apps for me/us to try out?

Anyway, running these 3D apps makes the back of the iPad hot...and as I said, it seems to prevent it from rebooting. (Again, the error log being "THERMALTEMPd" related seems to be a big clue.

Also, how can it be a "hardware" issue if it can be stable doing lots of complex calculations (millions of instructions per second, probably) when it runs a large, complex 3D game, but stumbles with a simple timer that a 1970s era Apple II computer with 16kb memory can do with no problems?

Would love to show and ask this to the Apple Engineers and see what they make of it..

Anyone with the 12.9” iPad Pro 1st or 2nd gen fix the boot loop with 14.2? My brother updated mine from 13.6 to 14.2 through dfu & many other ways & it’s still restarting. He’s an IT guy & has had Apple products for years.

How do you scribble an iPad? I’ve tried everything including letting the battery run down completely and leaving it for a few weeks. Worked fine in ‘hello’ mode but always wants to update to ios14 and reboots while doing that, even in locked screen or sleep mode.

glad you’ve had success though

If you're within 2-years, that works. Unfortunately though, if you're past the 2-years, its $599 to Apple to fix. It would be called ransomware if 13.4 came from anyone else.

HaHa.. my article was helpful to you. congratulations!

Whereabouts did you squeeze it?

In my case, it was yes.

PaulDorn might be the same.