crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934243:0crwdne2934243:0 Jerry Wheeler

crwdns2934249:0crwdne2934249:0:

Hi deniz,
The Prs0 sensor is indeed found on the charging port flex cable, so your instinct to replace the charging port flex was the right call. Were you getting the same error before you replaced the flex, or did the error change afterward? In any case, it doesn't appear the phone is able to read the sensor on the replacement part. There are two logical possibilities as to why; either the new flex cable doesn't have or incorrectly implemented that sensor, or the problem isn't on the flex cable, but rather on the motherboard. If it's a motherboard issue it could either be the connector or the chip that handles the I2C communication to the sensor.
-@flannelist has written an excellent guide to iOS kernel panics that'w worth your time to take a look at.
+@flannelist has written an excellent guide to iOS kernel panics that's worth your time to take a look at.
[[iPhone Kernel Panics|iPhone Kernel Panics - iFixit|new_window=true]]
I'd suggest you use the guide to locate the panic log(s) on the phone and either screenshot or cut and paste the first page or so of any and all the logs that are present so we can take a look at them; there may be more to them than what your analyzer is showing; i.e., there might be more at issue than just the one sensor.
Add that information to your question and we'll take a look and figure out what to do next.
[guide|21499|Adding images to an existing question - iFixit Repair Guide|new_window=true]
I've personally changed out a few charging port assemblies and never had an issue with aftermarket parts, but you never know. In the absence of any more information I'd probably just bite the bullet and replace the port again, perhaps find one that has good ratings by users.
Let us know what you find with regard to the panic logs.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934245:0crwdne2934245:0 Jerry Wheeler

crwdns2934249:0crwdne2934249:0:

Hi deniz,
-The Prs0 sensor is indeed found on the charging port flex cable, so your instinct to replace the charging port flex was the right call. Were you getting the same error before you replaced the flex, or did the error change afterward? In any case, it doesn't appear the phone is able to read the sensor on the replacement part There are two logical possibilities as to why; either the new flex cable doesn't have or incorrectly implemented that sensor, or the problem isn't on the flex cable, but rather on the motherboard. If it's a motherboard issue it could either be the connector or the chip that handles the I2C communication to the sensor.
+The Prs0 sensor is indeed found on the charging port flex cable, so your instinct to replace the charging port flex was the right call. Were you getting the same error before you replaced the flex, or did the error change afterward? In any case, it doesn't appear the phone is able to read the sensor on the replacement part. There are two logical possibilities as to why; either the new flex cable doesn't have or incorrectly implemented that sensor, or the problem isn't on the flex cable, but rather on the motherboard. If it's a motherboard issue it could either be the connector or the chip that handles the I2C communication to the sensor.
@flannelist has written an excellent guide to iOS kernel panics that'w worth your time to take a look at.
[[iPhone Kernel Panics|iPhone Kernel Panics - iFixit|new_window=true]]
I'd suggest you use the guide to locate the panic log(s) on the phone and either screenshot or cut and paste the first page or so of any and all the logs that are present so we can take a look at them; there may be more to them than what your analyzer is showing; i.e., there might be more at issue than just the one sensor.
Add that information to your question and we'll take a look and figure out what to do next.
[guide|21499|Adding images to an existing question - iFixit Repair Guide|new_window=true]
I've personally changed out a few charging port assemblies and never had an issue with aftermarket parts, but you never know. In the absence of any more information I'd probably just bite the bullet and replace the port again, perhaps find one that has good ratings by users.
Let us know what you find with regard to the panic logs.

crwdns2915684:0crwdne2915684:0:

open

crwdns2934241:0crwdne2934241:0 Jerry Wheeler

crwdns2934249:0crwdne2934249:0:

Hi deniz,

The Prs0 sensor is indeed found on the charging port flex cable, so your instinct to replace the charging port flex was the right call.  Were you getting the same error before you replaced the flex, or did the error change afterward? In any case, it doesn't appear the phone is able to read the sensor on the replacement part There are two logical possibilities as to why; either the new flex cable doesn't have or incorrectly implemented that sensor, or the problem isn't on the flex cable, but rather on the motherboard. If it's a motherboard issue it could either be the connector or the chip that handles the I2C communication to the sensor.

@flannelist has written an excellent guide to iOS kernel panics that'w worth your time to take a look at.

[[iPhone Kernel Panics|iPhone Kernel Panics - iFixit|new_window=true]]

I'd suggest you use the guide to locate the panic log(s) on the phone and either screenshot or cut and paste the first page or so of any and all the logs that are present so we can take a look at them; there may be more to them than what your analyzer is showing; i.e., there might be more at issue than just the one sensor.

Add that information to your question and we'll take a look and figure out what to do next.

[guide|21499|Adding images to an existing question - iFixit Repair Guide|new_window=true]

I've personally changed out a few charging port assemblies and never had an issue with aftermarket parts, but you never know. In the absence of any more information I'd probably just bite the bullet and replace the port again, perhaps find one that has good ratings by users.

Let us know what you find with regard to the panic logs.

crwdns2915684:0crwdne2915684:0:

open