Here is what I have tried:

• I inspected the components on the board (they look fine)
• Took one by one each connector thinking that could be a camera issue etc.
• Resetting the all settings.
• Replacing the battery
• Turning on without the charging port connector plugged in

Now I am kind of out of options, any help would be great…

I found the issue and actually Chris you are right, it will still reboot even if the port is disconnected or connected.

The problem is the Charging port must be OEM or genuine.

I tested around 3 ports and same problem, the I moved the motherboard into genuine frame having the original port and is working like charm.

I hope this it will help others as I spent plenty of hours believing that is a board issue.

⟐ Commented April 28, 2022 at 17:57 MST

⟐ Commented November 14, 2020 at 8:48 MST

⟐ Answered August 25, 2023 at 17:09 MST

My phone frequently restarts, for instance, it suddenly restarts while I'm using it. After the restart, the battery level is at 10%. This 10% lasts a long time, even though it's based on the charge level after reboot. Sometimes, the restart results in a normal battery level, while other times it's at 10%, and this 10% remains constant. Below is my restart analysis report, hoping someone can provide an explanation.

Here's the restart analysis report for reference:

{"bug_type":"210","timestamp":"2023-08-12 23:17:59.00 +0800","os_version":"iPhone OS 16.6 (20G75)","roots_installed":0,"incident_id":"D3F44D40-AA84-4DC1-9E9A-1B1F78F31C2F"}
{
  "build" : "iPhone OS 16.6 (20G75)",
  "product" : "iPhone11,6",
  "socId" : "8020",
  "socRevision" : "11",
  "incident" : "D3F44D40-AA84-4DC1-9E9A-1B1F78F31C2F",
  "crashReporterKey" : "0fb9d45f15bc9d0139f8c3f0ef4762bce241074d",
  "kernel" : "Darwin Kernel Version 22.6.0: Wed Jun 28 20:51:42 PDT 2023; root:xnu-8796.142.1~1\/RELEASE_ARM64_T8020",
  "date" : "2023-08-12 23:17:59.77 +0800",
  "panicString" : "panic(cpu 0 caller 0xfffffff02c5e536c): SMC PANIC - ASSERT: smc\/bms\/battery.cpp\n - BMSTask(4)\nASSERT: smc\/bms\/battery.cpp\n\nRTKit: RTKit-2062.142.1.release - Client: AppleSMCFirmware-3424.140.21.0.4.iphone11-imola.REL\n!UUID: b7a3fa21-7489-3aeb-a83d-057e7f95e7ae\nTime: 0x00000005e120f4bb\n\nFaulting task   4 Call Stack: 0x000000000002bfd0 0x000000000002b9a0 0x000000000002b7b0 0x000000000002d860 0x00000000000173b8 0x000000000001ee28 000000000000000000\n\nChinook ASC Async error info: \nl2c_err_sts 0x10001bfc00000000, l2c_err_adr 000000000000000000, l2c_err_inf 000000000000000000\nlsu_err_sts 000000000000000000, fed_err_sts 000000000000000000, mmu_err_sts 000000000000000000\ndpc_err_sts 000000000000000000\n\nMailbox (0): (0)\n  Inbox  AKF_KIC_INBOX_CTRL = 0x00020001, AKF_KIC_MAILBOX_SET = 0x11111101\n  Outbox AKF_AP_OUTBOX_CTRL = 0x00020001, AKF_AP_MAILBOX_SET  = 0x00000000\n\n    dir   endpoint      timestamp           msg\n    ====  ============  ==================  ==================\n    [RX]        user01  0x00000005e0012a94  0x544730420000c013\n    [TX]        user01  0x00000005e001303c  0x000000000000c000\n    [RX]        user01  0x00000005e00154a0  0x544730420008d010\n    [TX]        user01  0x00000005e0017ff0  0x000000000008d000\n    [RX]        user01  0x00000005e00191fc  0x423053530000e013\n    [TX]        user01  0x00000005e001b160  0x000000000000e000\n    [RX]        user01  0x00000005e001bb1c  0x423053530008f010\n    [TX]        user01  0x00000005e001da7c  0x000000580002f000\n    [RX]        user01  0x00000005e001e478  0x4230525300000013\n    [TX]        user01  0x00000005e0020268  0x0000000000000000\n    [RX]        user01  0x00000005e00225a4  0x4230525300081010\n    [TX]        user01  0x00000005e00241e4  0x0000001500021000\n    [RX]        user01  0x00000005e00264c0  0x4230464700002013\n    [TX]        user01  0x00000005e0028110  0x0000000000002000\n    [RX]        user01  0x00000005e002a3f0  0x4230464700083010\n    [TX]        user01  0x00000005e002c0b8  0x0000000000083000\n    [RX]        user01  0x00000005e002d054  0x4230414300004013\n    [TX]        user01  0x00000005e002d500  0x0000000000004000\n    [RX]        user01  0x00000005e002e254  0x4230414300085010\n    [TX]        user01  0x00000005e002e828  0x0000fe6500025000\n    [RX]        user01  0x00000005e002fc84  0x4230495600006013\n    [TX]        user01  0x00000005e003194c  0x0000000000006000\n    [RX]        user01  0x00000005e00322c4  0x4230495600087010\n    [TX]        user01  0x00000005e0034224  0x0000fe6500027000\n    [RX]        user01  0x00000005e0034e54  0x4230434800008013\n    [TX]        user01  0x00000005e0036ac0  0x0000000000008000\n    [RX]        user01  0x00000005e00374a8  0x4230434800089010\n    [TX]        user01  0x00000005e0039358  0x000000ee00029000\n    [RX]        user01  0x00000005e003b670  0x544730560000a013\n    [TX]        user01  0x00000005e003cec8  0x000000000000a000\n    [RX]        user01  0x00000005e003dc20  0x544730560008b010\n    [TX]        user01  0x00000005e003e284  0x000000000008b000\nRTKit Task List:\n   name                    | pri     | stack use | status     | resource | warning\n 0 rtk_ep_work             | 057     |   640\/2048  | SEMWAIT    | 0x4ac20 | \n      0x000000000001e324 0x000000000001f2cc 0x000000000002c32c 0x000000000001ee28\n\n 1 power                   | 000     |   832\/2048  | RUNNABLE   | 0x40d80 | \n      0x000000000001e324 0x000000000002b134 0x000000000002ad6c 0x000000000001ee28\n\n 2 Misc                    | 019     |  1440\/4096  | SEMWAIT    | 0x37cb0 | \n      0x000000000001e324 0x000000000001f2cc 0x000000000000dee0 0x000000000000f6f4 0x000000000001b4fc\n\n 3 InductiveTask           | 019     |  1296\/2048  | RUNNABLE   | 0 | \n      0x000000000001b268 0x0000000000020b54 0x0000000000006c20 0x000000000000c160 0x0000000000008e00 0x000000000001ee28\n\n 4 BMSTask                 | 019     |  1424\/2048  | RUNNABLE   | 0 | [Faulting task]\n\n 5 PMUEventTask            | 019     |  1040\/2048  | SEMWAIT    | 0x462a0 | \n      0x000000000001e324 0x000000000001f2cc 0x0000000000003e20 0x000000000001ee28\n\n 6 APComms                 | 019     |  1296\/2048  | SEMWAIT    | 0x45690 | \n      0x000000000001e324 0x000000000001f2cc 0x000000000002c32c 0x000000000001ee28\n\n\n\nSleep Count: 127406\nWake Count:  105409\nDuty Cycle:  28\nSleep Count: 127406\nWake Count:  105409\nDuty Cycle:  28\n\nRTBuddy(AP): Debug info:\n_iopStatus = 0x8\n_powerStateChangeLocked = false\nMailbox Status:\nIDLE_STATUS: 0x00000028\nMAILBOX_SET: 0x00000000\nMAILBOX_CLR: 0x00000000\nINBOX_CTRL: 0x00020001\nOUTBOX_CTRL: 0x00021101\nAP->IOP Mailbox

Previous usage scenarios:

Even with the original battery, I experienced similar issues with high restart frequency. It would restart automatically after being fully charged, and the battery level would still be around 20%. This 20% would last quite a while. I suspected it was a battery problem, so I replaced both the battery and cells. However, after replacement, screen responsiveness issues emerged. The screen didn't respond to touch, and upon inspection, it was identified as a motherboard problem. The motherboard was repaired, and the screen works fine now. However, the frequent restarting problem persists. Initially, a repair technician thought it could be related to the battery cells, so a new battery was installed, but the issue remained. The technician further examined it but couldn't pinpoint the exact cause, as there's no consistent pattern to the restart intervals.

⟐ Commented August 15, 2023 at 11:26 MST

Best examples of what I’m working with currently. The old screen never did anything like this even up to when I changed it because of a crack. Normally would have more defined lines and darker blacks.

⟐ Answer accepted July 25, 2023 at 14:44 MST

I changed my battery and the battery was draining fast so I got a warranty replacement and put it in my phone... The issue was when I was taking the screen off the adhesive strip got stuck on the ribbon cables for the screen and ended up tearing the black metallic film on the back of the screen!!! I thought nothing of it assuming it is just a ground plain and swapped the battery and turned on the phone. When I did I noticed my touch was not working at all. When I opened up the phone and took off the connectors and checked them all I noticed a very thin and tiny round piece of plastic it was orange and looked like kapton tape in-between the touch connectors. I thought this was the only issue so I removed it and put eye back together and it still was not functioning!!! Please help I have included macro pictures of the connectors.

PS I followed the iFIXIT tutorial but yes I did. My issue was that the battery I bought from iFIXIT was not making a proper connection and the phone would reboot randomly. So I was changing the battery

⟐ Commented February 01, 2023 at 9:01 MST

I was in an event and i think my phone fell out my bag and mabe someone step on it i found it on the woredrob finally, try to use it the screen is totally fine and working but the touch is nor responsing. any help maybe appreciate it thanks

⟐ Answer edited November 20, 2022 at 4:07 MST

In the photo you can see I have a a new flex charging cable but it's did not come with a mute rocker button, it has the small black switch underneath but no red/black button piece, so question is how do I take the button off and tranfer it to the rocker/switch

⟐ Answer edited October 14, 2022 at 10:52 MST

⟐ Answered June 05, 2020 at 7:49 MST

⟐ Answer accepted March 02, 2019 at 7:35 MST

⟐ Commented August 22, 2022 at 3:35 MST

PS.: I guess this is the reward from apple when buying a flagship device tie Face ID with T2 so repair isn’t possible!

⟐ Answered September 24, 2020 at 0:11 MST

⟐ Answered January 21, 2026 at 12:00 MST

⟐ Answer edited November 14, 2024 at 12:43 MST

⟐ Answered September 20, 2021 at 12:14 MST

so far only the customer’s original screen is showing something randomly. Pictures below. Thanks in advance.

⟐ Answered September 10, 2021 at 4:14 MST

⟐ Answered November 10, 2019 at 4:25 MST

I replaced the logic board of my iPhone XS Max and now the front-facing camera is not working.

I understand that, after replacing the logic board, only FaceID will not work. However, I have never heard that the front-facing camera will not work as well.

In this case, do I have to replace the front-facing camera as well?

⟐ Commented July 05, 2024 at 2:25 MST

⟐ Answered April 17, 2024 at 13:47 MST

⟐ Answered July 20, 2023 at 10:37 MST