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

I have the same issue with an iPad Pro after upgrading to 13.4.1. Have an open ticket with Apple Support. Support was unable to fix so referred to engineering. Got a call back from support saying that my IPAD has a "hardware" failure. They were unable to tell me what hardware failed or what test was run to determine the failure. Apple has no way for me to downgrade to previous software release.

Quit interesting that support claims that my IPAD hardware failed at the exact instant that I upgrade to 13.4.1.

It seems to me that Apple knows what the problem is but won't admit it. My best guess is a firmware issue in some of the IPAD, IPHONE products that was exacerbated with the software release.

Have been suffering with this problem for a week. May need to buy a replacement if not resolved.

I doubt I'm the only one with this problem.

I had a similar discussion with Apple. They said that since a restore didn't fix the issue it has to be hardware and to take it to an authorized service center. I pointed out that several people in this discussion thread have the same issue and it seems like an amazing coincidence that the restarts began immediately after 13.4 finished installing. Their comment was "interesting".

I keep hoping that 13.4.2 (or 13.5?) will come out and fix it.

future software fix may not be in the cards. If 13.4.1 hosed firmware there may be no way to recover. If this is the case Apple should rebate customers and offer a favorable trade-in program for affected “bricked” products.

This is a problem created by Apple software upgrade process due to lack of testing prior to general release.

Hi PaulDorn. I encountered this problem again and I leave my opinion about this.

Recently, I initialized my iPad to sell it because I thought that this problem was solved perfectly. But I was wrong.

• Initializing iPad occurs this problem again.
• Updating iPad occurs this problem again. (Actually, I tried to update my iPad to 13.5 today, and the problem is happened again.)

From my recent experience,

• This problem cannot be solved completely by squeezing iPad.
• When iPad is initialized or updated, iPad performs some check routines (e.g., devices's healthy). If the routine is failed, iPad does reboot and tries it again.
• I think that the check routine occurring reboot is performed only one time. The squeezing iPad is a way to bypass the routine.
• So... I think that my iPad has a hardware problem where is in the logic board.

[My opinion]

If you do not want to see the problem again, you do not update, or initialize iPad. Honestly, I will update my pad again as I can avoid the check routine by the squeezing. HaHa..

Bye!

A moderator deleted my first post because they said it was a rant. Yet I was merely pointing out that I was also a victim of updating to 13.5.1 and getting stuck in the reboot loop caused by a panic from watchdog not being able to read thermalmonitord. Was working perfectly prior to the update. Restores were no help. And Apple support said it would take $500 to replace my iPad.

IPad pro 10.5

Mphv2ll/a

13.5.1

It's interesting that your iPads were briefly working again after the 13.6 install. Hopefully that could be helpful information in getting them to pursue an escalation with the engineering team. That was what my advisor was going to do for me but then my iPad was damaged on return from the repair centre so a replacement was issued automatically. The new one is running 13.3.1 and I daren't update it!! If you have the energy, keep pursuing that engineering escalation.

Yeah,

That is what I did, as well.

I needed a larger storage, 256 GBs, iPad Pro to replace my 2015, 128 GBs model.

I didn't trust getting any 2017 or 2018 iPad Pro models as all of these have, to date, at least three different major issues going on, like touch screen issues, boot loop issues and/or fast battery draining issues.

So, I opted for purchasing a slightly newer 2016, 256 GBs iPad Pro with WiFi and cellular data that only had iPadOS 13.2.3 installed.

I purchased this back in March 2020.

I paid less than $500 U.S.D. and got a third party, three year warranty for this iPad Pro and it is running perfectly fine with NO issues, to date, running iPadOS 13.3.2.

I have decide NOT to upgrade this iPad to any other versions of iPadOS 13.

I am going to hold out hope that iPadOS 14 will be a better OS release when it arrives.

All the iOS/iPadOS release since the switch to 64-bit code have all been, overall, complete garbage with more bugs and issues that I cannot even remember!

Hoping iPadOS 14 will see a marked change in more trouble-free operations, functionalities and features.

But Apple lied to us, once again, and issued a new iPadOS 14 with more features, again, instead of focusing on fixing all of the issues still present in iPadOS 13, which I do not see too many more issued updates for.

Originally, iPadOS 14 was going to be a simple maintenance and bug fix release with focus on performance, optimisations and bug squashing and less on introducing new features.

So, once again, I am left pondering which way iPadOS 14 will go and whether, once again, I will have to pass on another potentially bad iPadOS version, in the near future.

My first 2015 iPad Pro is still running iOS 10.3.3, but is still receiving some app updates to date.

None of the previous iOS version, IMSO, were worthy of upgrading to, so I have passed on the last 3 years of iOS/iPadOS versions for that iPad Pro.

Once again, hoping for a miracle with iPadOS 14.

I have the iPad Pro 12.9" here in Australia and this exact same issue started happening on an accidental iOS update 3 days ago. I've tried all the suggested fixes and also updated to 13.6 but the issue still remains basically making it unusable. I have sent feedback to the Apple link supplied on this board and will start making phone calls tomorrow. Thanks to all of you for your input.

I updated to the recent public beta 3, restart loop is GONE. I'm not getting my hopes up, though. It's been an hour now. Is this the light at the end of the tunnel? Maybe. I will post an update later today to let you know.

Oh my... APPLE NINJAS!

Thank you so much @mehdichopin for your post!

I had upgrade to iPadOs 14 Public Beta 2 two days ago and that did nothing to resolve the issue and downgraded back to 13.6 after chatting with Apple Support. I was feeling so hopeless after even bringing the device into Genius Bar and having them wave me off with 'hardware issue, replacement, replacement.'

I just reinstalled Public Beta 2 (Beta 3 isn't available to me) after your post and... NO MORE BOOTLOOPS! I've since taken my iPad out of the fridge and have shakening it this way and that and still no bootloops or panic logs! Magic! Seems like some sort of rogue update has stabilized the issue currently, but I will likewise report back if this is only a short-lived celebration.

-------------

If anyone is stuck with reboots so prevalent that you can't even update, see if cooling your device in the fridge momentarily stops the bootloops long enough for you to update. If that is not enough, compress your potential problem areas lightly (I suspect my issue is a loose contact problem, my panic logs pointed to an 'ACMM error' and a 'Fatal Coherency Point Error,' so pushing around the top of the iPad allowed me to pass the kernal checks to stop the boot looping).

*I initially squeezed the circled area with both palms, but found that clipping the top while in the fridge worked well enough.

*And thank you with a magnitude of a thousand suns if there are any Apple Ninjas reading this that implemented the change!

I'm on Public Beta 2 through https://beta.apple.com/sp/betaprogram/

and that's worked for me - it wasn't working two days ago, but seems something has changed even with Beta 2 at the release of Beta 3.

Make sure to turn on 'Share iPad Analytics' in Settings -> Privacy if you're comfortable sharing your data to help the engineers diagnose what's wrong.

Click into 'Analytics Data' and see if you have 'panic-full' logs. Click into them and check after the "panicString," what kind of error follows?

Thanks so much for the response: Yes..many Panic full reports: here's the last one:

"build" : "iPhone OS 13.6 (17G68)",

 "product" : "iPad6,7",

 "kernel" : "Darwin Kernel Version 19.6.0: Sat Jun 27 04:35:07 PDT 2020; root:xnu-6153.142.1~4\/RELEASE_ARM64_S8000",

 "incident" : "3F4E3429-978A-451E-A79F-1B86AAF9DE84",

 "crashReporterKey" : "09fca0a5da3a51c3999e6d16985b0e2f024cf6e2",

 "date" : "2020-07-23 13:48:34.28 +1000",

 "panicString" : "panic(cpu 0 caller 0xfffffff014652470): userspace watchdog timeout: no successful checkins from com.apple.thermalmonitord since load\nservice returned not alive with context : is_alive_func returned unhealthy : current 19fffffffe, mask 1ffffffff, expected 1ffffffff. Missing sensor(s): TG0B \nservice: com.apple.backboardd, total successful checkins since load (180 seconds ago): 19, last successful checkin: 0 seconds ago\nservice: 

Im confused why 13.6 is still showing and also my iPad is a Pro 12.9" not an iPad 6,7"??

Mine has been up and running almost 24 hours with Public Beta 3.

The only issue I had was the boot loop, and that started immediately after updating to 13.4 in late March. I installed every incremental update since (and betas) hoping for a solution, including DFU restores setting up as a new iPad so that no third party apps were installed. I even tried some of the other suggestions like pressing to the left of the home button and putting it in the freezer. I also communicated with Apple multiple times and every communication ended with "if you've done a restore and are still having an issue then it's hardware" and it needs repair ($$$).

I concur with Zajog that at a minimum Apple needs to acknowledge the fix in the release notes. I feel like I dodged a bullet as I refused to pay for repair and the new iPad Pro 11 has been mostly unavailable through Apple and other approved outlets.

Same story here, SSFC. Mine has been working flawlessly since yesterday. I even binge-watched a show on it. So far so good.

Most of us did not rush into paying exorbitant prices for a "repair", because we persisted in using our common sense. That a collective hardware problem is a nonsensical notion that must be abolished at all costs. It's a stupid myth. We voiced our frustration and disappointment, and it took time to be heard. Everyone needs to learn that one simply doesn't go and buy a new iPad because it was bricked by a software bug. The facts were clear as day; all of our woes started at the same time, and we were being told that all of us were wrong.

I hope Apple does the right thing and admits this issue in its release notes. I also hope Apple refunds those who paid for repair. It's unfair for their loyalty to the brand.

Our posts are continually being removed for 'speaking on the solution' that has helped others here. My previous post removed of any confidental information:

"Seems like several of my posts and others' as well have been removed on account of [containing confidential information] -- even though some were unrelated.

To summarize, for those who [the above solution] didn't solve the issue, our panic logs were showing a different error. I suggested that it would be a good idea to pool our data to see if there is any correlation. The production date of my device is 29-08-2017 in Foxconn (China) according to an online serial number checker. While nobody here has yet posted panic logs that share my errors, somebody with a blog post in Taiwan has, errors related to the iPad's light sensor and (assumed) CPU power supply.

Software locking is an old Apple implement, and I believe is related to the the original bootloops posted here as well as the continued bootloops that have yet been resolved:

'The mysterious error message that may destroy your iPhone' https://www.news.com.au/technology/gadgets/mobile-phones/the-mysterious-error-message-that-may-destroy-your-iphone/news-story/b5354fbfcbafe9f5d04e3ad7f5fb6b6e

I now worry for those who have resolved their issue by [the above solution] as their input and experience can be policed. Save your SHSH blobs everyone so you can downgrade if issues arise in the future! If our messages here continued to be censored, we may have to make the move to another platform to discuss freely.

This whole ordeal has been extremely disappointing; I have only just recently begun to consider introducing Apple into my computing needs and the iPad Pro is such an attractive option. However with this ordeal of a troubleshooting experience, I can't say I'm not a little more than apprehensive to continue down the Apple ecosystem.

My panic logs saved while on 13.6:

AMCC Error:

{"bug_type":"210","timestamp":"2020-07-20 06:02:37.00 -0700","os_version":"iPhone OS 13.6 (17G68)","incident_id":"3BC428FB-3A9D-4D67-9D29-BFCC7CC18F24"}{"build" : "iPhone OS 13.6 (17G68)", "product" : "iPad7,4", "kernel" : "Darwin Kernel Version 19.6.0: Sat Jun 27 04:36:05 PDT 2020; root:xnu-6153.142.1~4\/RELEASE_ARM64_T8011", "incident" : "3BC428FB-3A9D-4D67-9D29-BFCC7CC18F24", "crashReporterKey" : "5f9fffa2032645ae219b1d236756e0b28989c1e6", "date" : "2020-07-20 06:02:33.54 -0700", "panicString" : "panic(cpu 0 caller 0xfffffff0297c6540): \"AMCC Error! AMCC_IRERRDBG_INTSTS=0x1000000, MCCTAGPARLOG1\/2=0\/0, MCCDATERRLOG=0, MCCAFERRLOG[0..2]=0xfffff080\/0x1f140f\/0xa044, RNKCFG[0..3]=0x6011\/0x6011\/0x6011\/0x6011\"@\/Library\/Caches\/com.apple.xbs\/Sources\/AppleT8010\/AppleT8010-63.0.1\/AppleT8010PlatformErrorHandler.cpp:269\nDebugger message: panic\nMemory ID: 0x6\nOS version: Not set yet\nKernel version: Darwin Kernel Version 19.6.0: Sat Jun 27 04:36:05 PDT 2020; root:xnu-6153.142.1~4\/RELEASE_ARM64_T8011\nKernelCache UUID: C5AF7A5E78CF1631FEB7A5BEB39C5FC3\nKernel UUID: 8112CE26-A0EC-39C5-8E50-B83C0E62CEBE\niBoot version: iBoot-5540.140.12\nsecure boot?: YES\nPaniclog version: 13\nKernel slide: 0x0000000022a74000\nKernel text base: 0xfffffff029a78000\nmach_absolute_time:

Fatal Coherency Point Error:

{"bug_type":"210","timestamp":"2020-07-21 11:41:49.00 +1000","os_version":"iPhone OS 13.6 (17G68)","incident_id":"AA4F6AFD-69E3-4520-AB6B-206CC9D56CE0"} { "build" : "iPhone OS 13.6 (17G68)", "product" : "iPad7,4", "kernel" : "Darwin Kernel Version 19.6.0: Sat Jun 27 04:36:05 PDT 2020; root:xnu-6153.142.1~4\/RELEASE_ARM64_T8011", "incident" : "AA4F6AFD-69E3-4520-AB6B-206CC9D56CE0", "crashReporterKey" : "5f9fffa2032645ae219b1d236756e0b28989c1e6", "date" : "2020-07-21 11:41:43.17 +1000", "panicString" : "panic(cpu 0 caller 0xfffffff02a6db0c8): \"Fatal Coherency Point Error! CP_COM_NORM_REQUEST=0x2 Captured state=0xffffffe0006e7600 CP CCU0 PIO Response Error: ADDR=0x80 INFO=0x10a0442c: STATUS\/TID\/ID\/CMD=0x1\/0xa0\/0x44\/0x2c(NCRdIncrRsp-RO)\n\"@\/Library\/Caches\/com.apple.xbs\/Sources\/AppleT8010\/AppleT8010-63.0.1\/AppleT8010PlatformErrorHandler.cpp:576\nDebugger message: panic\nMemory ID: 0x6\nOS version: Not set yet\nKernel version: Darwin Kernel Version 19.6.0: Sat Jun 27 04:36:05 PDT 2020; root:xnu-6153.142.1~4\/RELEASE_ARM64_T8011\nKernelCache UUID: C5AF7A5E78CF1631FEB7A5BEB39C5FC3\nKernel UUID: 8112CE26-A0EC-39C5-8E50-B83C0E62CEBE\niBoot version: iBoot-5540.140.12\nsecure boot?: YES\nPaniclog version: 13\nKernel slide: "