Skip to main content
Help

Current version by: Jerry Wheeler

Text:

What that code tells us is that the phone's processor cannot communicate with one or more of the sensors on the charging port assembly. Usually that's because the sensor has failed, and replacing that sensor generally fixes the problem.
Obviously that didn't work in your case, so the problem is somewhere else. There are two lines for each I2C bus that are used to talk to those sensors, and if either of those lines is damaged or disconnected then you'll get the kernel panic you're seeing.
Unfortunately the only way to know where those signals go is to have a schematic diagram and/or board (Gerber) files, neither of which seems to be available for the iPhone 15 models. Alisha (@flannelist), have you seen any yet?
We have seen other cases similar to yours where replacing the flex cable didn't help, and one of our more technologically advanced users was able to reflow the interposer, which fixed the problem. Apparently the motherboard had somehow been physically stressed and the interposer connections broke loose. Do you know if there's been any physical damage to the phone that could account for something like that?
+
+One other thought occurred to me; there's always a chance the FPC connector on the motherboard has taken some damage on one of those pins; that would also account for that error, so be sure to carefully examine the logic board connector with a magnifying glass. Clean it with some 90% or higher concentration isopropyl (rubbing) alcohol and see if that makes any difference.

Status:

open

Edit by: Jerry Wheeler

Text:

What that code tells us is that the phone's processor cannot communicate with one or more of the sensors on the charging port assembly. Usually that's because the sensor has failed, and replacing that sensor generally fixes the problem.
Obviously that didn't work in your case, so the problem is somewhere else. There are two lines for each I2C bus that are used to talk to those sensors, and if either of those lines is damaged or disconnected then you'll get the kernel panic you're seeing.
-Unfortunately the only way to know where those signals go is to have a schematic diagram and/or board (Gerber) files, neither of which seems to be available for the iPhone 15 models yet. Alisha (@flannelist), have you seen any yet?
+Unfortunately the only way to know where those signals go is to have a schematic diagram and/or board (Gerber) files, neither of which seems to be available for the iPhone 15 models. Alisha (@flannelist), have you seen any yet?
We have seen other cases similar to yours where replacing the flex cable didn't help, and one of our more technologically advanced users was able to reflow the interposer, which fixed the problem. Apparently the motherboard had somehow been physically stressed and the interposer connections broke loose. Do you know if there's been any physical damage to the phone that could account for something like that?

Status:

open

Original post by: Jerry Wheeler

Text:

What that code tells us is that the phone's processor cannot communicate with one or more of the sensors on the charging port assembly. Usually that's because the sensor has failed, and replacing that sensor generally fixes the problem.

Obviously that didn't work in your case, so the problem is somewhere else. There are two lines for each I2C bus that are used to talk to those sensors, and if either of those lines is damaged or disconnected then you'll get the kernel panic you're seeing.

Unfortunately the only way to know where those signals go is to have a schematic diagram and/or board (Gerber) files, neither of which seems to be available for the iPhone 15 models yet. Alisha (@flannelist), have you seen any yet?

We have seen other cases similar to yours where replacing the flex cable didn't help, and one of our more technologically advanced users was able to reflow the interposer, which fixed the problem. Apparently the motherboard had somehow been physically stressed and the interposer connections broke loose. Do you know if there's been any physical damage to the phone that could account for something like that?

Status:

open