⟐ Edited by author April 26, 2026 at 9:52 MST

• Chassis (housing)
• Display
• All 4 speakers
• USB-C charging port

After reassembly, I’m now facing multiple issues:

• Charging is detected but extremely slow (battery percentage barely increases)
• All speakers are heavily distorted (on all corners)
• USB-C audio only works on one side (only one earbud)

The USB-C port is brand new and properly installed.

I double-checked all connections and flex cables, nothing seems out of place.

Has anyone already encountered this kind of issue after a repair like this?

What could be causing it?

I was thinking about something related to power management (PMIC / charging IC or maybe a damaged power line), but I’d like to hear if others have seen similar symptoms.

Alternatively, if it's just... left this way, will it get worse over time?

The screen works perfectly fine. But if you touch the bezel just about 1" to the right of the home button it glitches like crazy. As soon as you stop touching the bezel it goes back to normal.

I have taken a quick video, but can't upload video here. Some screenshots attached.

It does not do this with any part of the screen nor any other part of the bezel. Only specifically when touching the bezel in this exact space.

To be clear, a small bit of pressure is required. Just physical contact on that spot doesn't do anything, but a small amount of pressure (around the same amount to click the home button) produces these weird results.

First photo is screen working fine. Next photos are just some examples of the crazy chaotic glitching that can happen.

⟐ Answered March 14, 2026 at 20:46 MST

Now I want to open it up and look inside but can't find anything about these specific sensors. Any ideas?

{"bug_type":"210","timestamp":"2025-11-30 08:37:47.00 -0500","os_version":"iPhone OS 16.7.12 (20H364)","roots_installed":0,"incident_id":"35ED8459-61C0-40DE-9B3E-88411B9B7F97"}

{

"build" : "iPhone OS 16.7.12 (20H364)",

"product" : "iPad6,7",

"socId" : "8001",

"socRevision" : "10",

"incident" : "35ED8459-61C0-40DE-9B3E-88411B9B7F97",

"crashReporterKey" : "03eb87a8f9a7ffaf3704d9bfa30c3436ca6ed91e",

"kernel" : "Darwin Kernel Version 22.6.0: Tue Jul 2 20:45:41 PDT 2024; root:xnu-8796.142.1.703.8~1\/RELEASE_ARM64_S8000",

"date" : "2025-11-30 08:37:47.55 -0500",

"panicString" : "panic(cpu 0 caller 0xfffffff00e6a04fc): userspace watchdog timeout: no successful checkins from thermalmonitord\nservice returned not alive with context : is_alive_func returned unhealthy : current 1d7ffffff, mask 1ffffffff, expected 1ffffffff. SD: 0 BC: 0 RC: -1 BS: 0, Missing sensor(s): Tc1i Tc1x \nservice: backboardd, total successful checkins in 197 seconds: 19, last successful checkin: 0 seconds ago\nservice: SpringBoard, total successful checkins in 169 seconds: 17, last successful checkin: 0 seconds ago\nservice: mediaserverd, total successful checkins in 197 seconds: 18, last successful checkin: 0 seconds ago\nservice: logd, total successful checkins in 197 seconds: 19, last successful checkin: 0 seconds ago\nservice: thermalmonitord, no successful checkins in 197 seconds\nservice: runningboardd, total successful checkins in 197 seconds: 19, last successful checkin: 0 seconds ago\nservice: wifid, total successful checkins in 197 seconds: 17, last successful checkin: 0 seconds ago\nservice: configd, total successful checkins in 197 seconds: 16, last successful checkin: 0 seco\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 20H364\nKernel version: Darwin Kernel Version 22.6.0: Tue Jul 2 20:45:41 PDT 2024; root:xnu-8796.142.1.703.8~1\/RELEASE_ARM64_S8000\nKernelCache UUID: D64A923972F3E10F3B7B352B55EDC9EB\nKernel UUID: 65EDDC9F-FB45-3BCF-B2F0-FEB79BC3CFB7\nBoot session UUID: 35ED8459-61C0-40DE-9B3E-88411B9B7F97\niBoot version: iBoot-8422.142.2.700.1\nsecure boot?: YES\nroots installed: 0\nPaniclog version: 14\nKernel slide: 0x0000000007ab8000\nKernel text base: 0xfffffff00eabc000\nmach_absolute_time: 0x11a50e88a\nEpoch Time: sec usec\n Boot : 0x692c47da 0x000d2f2c\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x692c4898 0x000b62b7\n\nZone info:\n Zone map: 0xfffffff142000000 - 0xfffffff742000000\n . VM : 0xfffffff142000000 - 0xfffffff228664000\n . RO : 0xfffffff228664000 - 0xfffffff275330000\n . GEN0 : 0xfffffff275330000 - 0xfffffff35b994000\n . GEN1 : 0xfffffff35b994000 - 0xfffffff441ff8000\n . GEN2 : 0xfffffff441ff8000 - 0xfffffff528660000\n . GEN3 : 0xfffffff528660000 - 0xfffffff60ecc8000\n . DATA : 0xfffffff60ecc8000 - 0xfffffff742000000\n Metadata: 0xfffffff0021a4000 - 0xfffffff0039a4000\n Bitmaps : 0xfffffff0039a4000 - 0xfffffff004508000\n Extra : 0 - 0\n\nTPIDRx_ELy = {1: 0xfffffff35b216b78 0: 0x0000000000000000 0ro: 0x000000016d7270e0 }\nCORE 0 is the one that panicked. Check the full backtrace for details.\nCORE 1: PC=0x00000001e0d77054, LR=0x00000001a4141408, FP=0x000000016d44a7c0\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nTotal cpu_usage: 46145980\nThread task pri cpu_usage\n0xfffffff35b216b78 watchdogd 97 0\n0xfffffff35ad2d6f0 backboardd 63 8474\n0xfffffff35ae27928 thermalmonitord 37 0\n0xfffffff35b5cb928 launchd 37 1\n0xfffffff35a99ab78 watchdogd 31 0\n\nPanicked task 0xfffffff35b371d70: 194 pages, 4 threads: pid 57: watchdogd\nPanicked thread: 0xfffffff35b216b78, backtrace: 0xfffffffb7d3e7150, tid: 1253\n\t\t lr: 0xfffffff00ec745cc fp: 0xfffffffb7d3e71c0\n\t\t lr: 0xfffffff00ed9860c fp: 0xfffffffb7d3e7230\n\t\t lr: 0xfffffff00ed976a8 fp: 0xfffffffb7d3e7300\n\t\t lr: 0xfffffff00ec3d594 fp: 0xfffffffb7d3e7310\n\t\t lr: 0xfffffff00ec74008 fp: 0xfffffffb7d3e76c0\n\t\t lr: 0xfffffff00f2da244 fp: 0xfffffffb7d3e76e0\n\t\t lr: 0xfffffff00e6a04fc fp: 0xfffffffb7d3e7700\n\t\t lr: 0xfffffff00e69fe88 fp: 0xfffffffb7d3e7720\n\t\t lr: 0xfffffff00e69f054 fp: 0xfffffffb7d3e7840\n\t\t lr: 0xfffffff00f268504 fp: 0xfffffffb7d3e79e0\n\t\t lr: 0xfffffff00ed69144 fp: 0xfffffffb7d3e7b00\n\t\t lr: 0xfffffff00ec79b48 fp: 0xfffffffb7d3e7b80\n\t\t lr: 0xfffffff00ec53004 fp: 0xfffffffb7d3e7be0\n\t\t lr: 0xfffffff00ec67398 fp: 0xfffffffb7d3e7c90\n\t\t lr: 0xfffffff00ec6779c fp: 0xfffffffb7d3e7d90\n\t\t lr: 0xfffffff00ed8f604 fp: 0xfffffffb7d3e7e40\n\t\t lr: 0xfffffff00ed97a18 fp: 0xfffffffb7d3e7f10\n\t\t lr: 0xfffffff00ec3d594 fp: 0xfffffffb7d3e7f20\n\n",

"panicFlags" : "0x802",

"bug_type" : "210",

"otherString" : "\n** Stackshot Succeeded Bytes Traced 200644 (Uncompressed 510976) \n",

"repairStatus" : "1",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"memoryPressureDetails":{"pagesWanted":0,"pagesReclaimed":0},"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":112304,"throttled":0,"fileBacked":141149,"wired":19961,"purgeable":4202,"inactive":71274,"free":11890,"speculative":40076}},

"processByPid" : {

Since a few months back my iPad pro 1st generation has been randomly rebooting every few minutes.

I checked the panic.full reports in the analytics data and I can see two types of errors:

* "panicString" : "panic(cpu 0 caller 0xfffffff01b1414fc): userspace watchdog timeout: no successful checkins from thermalmonitord\nservice returned not alive with context : is_alive_func returned unhealthy : current ffffffff, mask 1ffffffff, expected 1ffffffff. SD: 0 BC: 0 RC: -1 BS: 0, Missing sensor(s): Tc2x \n

• "panicString" : "panic(cpu 0 caller 0xfffffff011e31ae8): \"AppleTriStar2: could not find system ID: bad IPC message ID bc 1 98 f0 2c 0\" @IOAccessoryManagerAID.cpp:44\nDebugger message: panic\nMemory ID: 0x6\nOS release type: Not set yet\nOS version: Not set yet\nKernel version: Darwin Kernel Version 22.6.0: Tue Jul 2 20:45:41 PDT 2024; root:xnu-8796.142.1.703.8~1\/RELEASE_ARM64_S8000\nKernelCache

I have seen many similar messages related to the "Thermalmonitord" panic logs, but they refer to other sensors.

Does anyone know what sensor is "TC2X"? Or generally, how to fix the issue?

Thank you in advance.

⟐ Edited by author October 27, 2025 at 2:34 MST

It randomly reboots especially when charging and this seems to happen consistently every 3 minutes or so when the problem flares up.

I can still use the iPad for daily tasks but the restarts are obviously a major annoyance.

I checked the analytics logs, and the 'panic-full' files clearly show: Missing sensor(s): TG0B.

Some background:

- I had the battery replaced by a third-party shop about a year ago. - The issue started appearing roughly a year after that, possibly right after I dropped the device (I'm not 100% sure).

- When it's working fine, the battery percentage looks stable. The reboots sometimes happen when I'm just watching YouTube, not so frequently though.

If the reboot happens when not charging, it's usually happens only once.

Since this is an older iPad, I'm hesitant to pay a repair shop for expensive diagnostics or microsoldering—it's just not worth the cost. I'm hoping it's a simple fix.

Is this 'TG0B missing sensor' error commonly fixable by just reseating the battery connector?(Although I'm not sure that reseating the connector is actually a simple job as a student) Or is micro-solering the only option?

I'd appreciate any advice, especially from those who have fixed a TG0B error on this older model!

⟐ Edited by author October 24, 2025 at 7:11 MST

⟐ Commented October 20, 2025 at 17:46 MST

I tired again using my Mac and Finder to transfer and restore a backup of my FIL’s iPad onto it… failed a few times with errors without any specific code.

Then I tried to use Apple Configurator, this time failed with two error codeS

Now it’s stuck in recovery/restore mode without my or any Mac being able to detected it (tried different cables, USB-C and USB with an adapter). Couldn’t not get it into DFU mode either.

Apple Genius tells me the port on iPad is broken, but the iPad detects the cable and connection and turns on each time it connects to a computer. I refuse to believe a software transfer attempt broke something hardware (especially when there was no problem in the wireless transfer mode too)

What should I do / try next, my ingenious community?

⟐ Edited by author October 12, 2025 at 23:19 MST

⟐ Edited by author October 06, 2025 at 8:47 MST

I need some guidance regarding my iPad Pro 11" (2018, model A1980) which suffered a water incident about 1-2 years ago. I just tried to power it on after a long time, and here’s the situation:

Symptoms / Observations:

• The iPad initially did not respond at all.
• I used an FNB58 USB tester to monitor charging.
• After cleaning some corrosion at the USB-C port with 99% isopropyl alcohol:
  • Initially drew ~0.08 A at 5 V (minimal current).
  • After a hard reset and leaving it connected, it briefly reached 15 V / 1 A → iPad made the charging chime, but it did not start and is not detected by a Mac.
  • Currently, I cannot get it back to 15 V / 1 A. It stays at 5 V / 0.08 A, and when performing a hard reset combination, it briefly goes to 5 V / 0.5 A for a few seconds, then drops back.
• USB-C port had minor green/blue corrosion, cleaned.
• iPad reacts to PD negotiation sometimes, but cannot maintain the higher voltage/current.

Other notes:

• Hard resets can temporarily change the current, but it never boots.
• I suspect the battery may be too deeply discharged or damaged.

Questions:

1. Given the PD behavior and charging currents, does this point to just a failing battery, or could the logic board be damaged?
2. Is it worth attempting a USB-C port replacement, or would that not change the current behavior?
3. Are there any safe ways to get it to stabilize at 15 V so I can see if it will boot?
4. Any other tests you would recommend before considering a battery or board replacement?

Thanks in advance for any guidance – I can provide photos of the port and FNB58 readings if needed.

・usb-c to 3.5mm earphone jack adapter doesn’t work. Some adapter works, but it also losts connection when reversed .

・PD charging doesn’t work though it charges with normal speed.

This is part I ordered.

https://ja.aliexpress.com/item/100500869...

The question is that the cause of these is whether the part I replaced or my replacing process?

If first one, I repurchase and repair again.

I think it is difficult to make it sure, but I want to hear opinions of yours.