Saltar al contenido principal

Información de reparación y desmontaje para el iPhone SE de segunda generación, anunciado y lanzado en abril de 2020.

Preguntas 239 Ver todo

3 minute reboot, missing sensor mic1, thermalmonitor unhealthy,

iphone se 2020, reboot every 3 minutes, panic logs showed missing sensor mic1 and thermalmonitorhd unhealthy, after doing much research I came to the conclusion that a new charge port flex was the solution. Ordered an OEM SE2020 charge port flex from a reputable retailer, because from my research the aftermarket or iphone 8 charge flexs don't have the thermal sensor that was necessary. Replaced the part, thought all was well, my phone lasted ~20 hours without rebooting until the problem returned. missing sensor mic1 again. thermalmonitorhd unhealthy. I had also replaced the battery at the same time, not sure if that matters. Any ideas? i'm about ready to give up and just order a used phone on swappa.

Contestado! Ver respuesta Yo también tengo este problema

Es esta una buena pregunta?

Puntuación 4
1 comentario

Do you have the original battery still? Even though I don’t think a battery could cause these issues it can’t hurt.

- de

Agregar un comentario

2 Respuestas

Solución Elegida

It’s still possible that you have a bad dock flex, but I would wager this is actually an issue with your logic board.

The 2020 SE has a fault that is fairly well known now within repair circles that the line which transmits the necessary signal to the CPU develops a break, somewhere under the SIM tray. So the signal never makes it to its destination. It is also fairly common for this fault to occur with a specific touch related line traveling similar paths under the SIM tray area to the CPU. You can verify you have this issue if you have a multimeter and good eyes. I will have to update later with places to test, but you can check for continuity between two points in the circuit, or use diode mode to see if the circuit is open.

Unfortunately, in order to repair this you will need microsoldering skills (or you’re gonna need a new board). Typically the fix involves running a long jumper wire to circumvent the broken circuit and restore the connection. There’s an excellent video on this repair on Jesse Cruz’s YouTube channel. If you’re not adept at this sort of repair, I would ask your local repair shop if they can do this, or can recommend someone who might if they can’t. But it’s a well documented issue, and any shop who works on boards regularly should be familiar.

Fue útil esta respuesta?

Puntuación 6

2 comentarios:

Thank you for this. I was able to use Jesse Cruz's video to diagnose this as a motherboard problem by finding the same OL in the same spot. I unfortunately do not have the skills to do this repair, but it is helpful to have an exact diagnostic.

- de

@erelectronics Fabulous. It’s a bit of a tricky repair regardless. But I’m always glad to put Jesse on people’s radar.

Also, unsolved issues really nag at me, so I understand the satisfaction in closure.

- de

Agregar un comentario

@flannelist has an excellent Wiki article on kernel panics, the technical term for the boot loop you are seeing. In it, they confirm that mic1 is located on the charge port flex, so your inclination to replace the charge port was spot on.

iPhone Kernel Panics - iFixit

What you're seeing is that the kernel scans its sensors every 3 minutes. If a particular sensor cannot be read, the operating system reboots the phone in an attempt to recover. The actual mechanism is called the I2C bus, which is a two wire connection between the SOC, or main processor, and the peripherals scattered throughout the phone.

In this case, the signal runs through the logic board to the FPC connector for the charge port connector. From there it travels down the flex cable to the microphone at the bottom of the phone. So if the signal is interrupted anywhere along the way, you'll get a kernel panic.

Typically, replacing the lightning port assembly cures the problem. However, if the issue lies on the motherboard itself, then of course changing the port won't help. Given that the behavior changed for most of a day, there's something odd going on, but it's hard to say exactly what that might be.

About all I can suggest at the moment is to check the big connector on the motherboard for any signs of bent or broken pins, along with any signs of small components next to the connector having been knocked off in the process of replacing the port. Although it's not a high probability, it is always possible you got a defective assembly that conked out on you early.

Fue útil esta respuesta?

Puntuación 3
Agregar un comentario

Añadir tu respuesta

A f estará eternamente agradecido.
Ver Estadísticas:

Ultimas 24 horas: 29

Ultimos 7 días: 184

Ultimos 30 días: 811

Todo El Tiempo: 8,897