iPhone Keeps Restarting After Water Damage: iPhone 11 Data Recovery
- Aaron Harrington
- Mar 12
- 8 min read
Case category: Water Damage
Failure type: 3-minute reboot / PRSO panic log caused by water-damaged resistors
Actual billed price: Standard Recovery ($750)
Service page: Water-Damaged iPhone Data Recovery
Severe Water Damage, a PRSO Panic Log That Was Not the Charge Port, and Two Tiny Resistors
Watch the full repair:
Watch on YouTube: https://youtu.be/aHTBTihFI9U (with comments and chapters)
The Problem
This iPhone 11 came in with severe water damage. By the time this video starts, I had already done the earlier board-level work needed to get the phone to boot again, but it still was not stable enough for data recovery.
The phone would power on, run for about three minutes, and then restart.
That symptom matters because a 3-minute reboot usually points people toward a familiar group of causes. In many cases, technicians will look at the panic log, see PRSO or mic1, and go straight to the charge port, the surrounding charge-port resistors, or the audio IC area. Those are real checks, and they are often correct. But in this case, the usual fixes were not solving the problem.
That is what made this case worth documenting.
The panic log looked familiar. The actual failure did not.
Step 1 – Confirming the 3-Minute Reboot and Reading the Panic Log [00:00]
I started by showing the phone in a known-good setup with the original board mounted in a jig and a three-minute timer running beside it.
Before the timer finished, the phone restarted.
That confirmed the symptom was real and repeatable. From there, I connected the phone to the computer and opened 3uTools to read the panic logs. The crash history showed repeated restarts, and the panic log pointed to PRSO.
At that point, the case looked like a normal “3-minute reboot / PRSO” problem.
But only on the surface.
Step 2 – Why the Usual PRSO Fixes Did Not Fit This Board [01:53]
A lot of technicians use the Repair Wiki for panic logs, and for good reason. It is a very useful resource. But it is not a full diagnosis by itself.
In this case, the common PRSO path did not line up with what I was seeing on the actual board.
The charge port was already known-good. I use that same charge port setup regularly, so I was not guessing there. I also cleared the underfill and checked the surrounding components in the charge-port area. Nothing there looked like the real fault.
That matters because panic logs can narrow a search, but they do not tell the whole story. PRSO can point you in the right direction, but it does not guarantee the failure is physically sitting at the charge port.
This board was water damaged, and water damage does not always fail in the “normal” location.
Step 3 – The Earlier Water-Damage Fault Had Already Been Cleared [04:00]
Before this stage of the case, I had already done the work needed to bring the phone back from a more serious no-power condition.
When I first opened the board, I injected at the battery FPC and saw a very fast amperage spike that pointed to a power-rail short. That led me to a NAND-area power rail short at a capacitor near the NAND. The short was severe enough that it even produced visible heat damage in that area.
Once that shorted capacitor was removed, the board was basically ready to turn on. There was still some corrosion on main in other spots, but it was not dragging the line down hard enough to stop boot. I cleaned those areas and removed a few more damaged capacitors.
That got the phone back to life.
But “alive” is not the same thing as “stable enough for data.”
Once it was able to boot, the real remaining symptom appeared: the 3-minute reboot.
Step 4 – Localized Water Damage Near the Camera FPC Pointed to the Real Problem [06:48]
One useful part of this case was how localized the remaining corrosion was.
The inside of the board looked relatively clean overall. The bottom board was also largely usable, which meant I did not have to fight a second cluster of unrelated faults at the same time. That narrowed attention to the areas where corrosion was actually present.
The heaviest remaining corrosion was near the camera connector area.
Normally, corrosion around camera FPCs is not the first thing people worry about in a 3-minute reboot case. Cameras often corrode because several power rails run through that area, but many camera-related parts are not required to make the phone boot or stay on long enough for data extraction.
This case was different.
In that corroded area near the camera FPC, a few capacitors on VDD_MAIN had already been removed, and two resistors stood out as suspicious. They were still connected on one side, but no longer properly connected on the other.
That was the moment the case started to make sense.
Step 5 – Why Two Small Resistors Were Able to Cause a 3-Minute Reboot [08:03]
Once I checked the boardview, those two resistors stopped looking “camera-related” and started looking critical.
One side of the resistors was tied to PP1V8_S2. That is not some throwaway line. It is an active rail feeding important circuitry. On the other side, the resistors fed paths tied into the audio amp, the charge-port related path, potassium lines, and an i2c / AOP communication line including I2C1_AOP_SCL.
That changes everything.
This is exactly the kind of detail that gets missed when someone diagnoses only by symptom category. A panic log may say PRSO, and the usual teaching may say “check the charge port,” but that does not mean the failed component has to be physically located right there.
If a resistor has 1v8 on one side and a CPU- or AOP-related communication path on the other, I treat it as important until proven otherwise.
That is also why I always say corroded resistors need to be checked for function, not just appearance. Some missing resistors are harmless. Some will leave a phone low-amp brain dead. Some will cause a repeating Apple logo. In this case, these two caused the 3-minute reboot.
Step 6 – Pulling Donor Parts and Rebuilding the Missing Resistors [10:24]
Once the likely cause was clear, the fix itself was straightforward in concept but still had to be done carefully.
I needed donor resistors.
I checked an iPhone 11 Pro donor board for matching parts by following the same line names in boardview. One donor gave me one resistor, but not the second one I needed. I had to move to another donor board to pull the other matching part.
That is a normal part of advanced board work. The diagnosis can be correct, but the repair still depends on finding the right donor parts and placing them cleanly.
After reinstalling both resistors, I reassembled the phone enough to test stability again.
Step 7 – The 3-Minute Reboot Was Gone [20:35]
With both replacement resistors back in place, I ran the same three-minute timer test again.
This time, the phone stayed on past the restart point.
That confirmed the real problem was not the charge port, not the common charge-port resistor cluster, and not simply the audio codec. The stabilizing fix was the two water-damaged resistors near the camera FPC.
This was exactly the kind of case that can fool people because the panic log still points toward a familiar category, but the board-level failure lives somewhere less obvious.
The Result – Data Recovery Path Restored [21:05]
Device: iPhone 11
Condition on arrival:
Severe water damage with an earlier no-power fault already corrected, followed by a remaining 3-minute reboot that prevented normal data extraction.
Main fault symptoms:
initial power-rail short near the NAND area
phone later able to boot, but not stay on
repeated 3-minute restart
PRSO panic log
localized corrosion near the camera FPC
two critical resistors no longer properly connected
Work performed:
confirmed repeated 3-minute reboot behavior
reviewed panic logs in 3uTools
ruled out the common charge-port explanation with a known-good charge port and inspection of the usual PRSO area
traced the earlier no-power issue to a shorted NAND-area capacitor
cleaned remaining corrosion and removed damaged capacitors
inspected the remaining corroded area near the camera connector
identified two missing / failed resistors tied to PP1V8_S2 and important communication paths including I2C1_AOP_SCL
sourced matching donor resistors from iPhone 11 Pro donor boards
rebuilt the damaged resistor section
retested the phone past the 3-minute restart point
Outcome:
✅ Successful stabilization for data recovery. The phone stayed on past the restart window, the 3-minute reboot was eliminated, and the board was stabilized on the original logic board for normal data access.
Conclusion
This was a good example of why panic logs help, but they do not replace diagnosis.
The PRSO code was real. The common repair advice was real. But the actual fault was not the textbook version of the problem. The board had already survived the earlier water-damage short and was booting again. What kept it from staying on was two tiny corroded resistors near the camera FPC that most people would not expect to be the final answer in a PRSO case.
That is the danger of treating water damage like a shortcut problem.
A shop can know the common panic log causes, check the common area, and still miss the real failure if they are not following the board itself. In this case, the phone did not need a dramatic CPU-tier repair. It needed careful board-level thinking and the discipline to verify what those corroded resistors actually did before ignoring them.
Nerd Corner (For Technicians & Repair Shops)
A few technical points from this job stood out:
The first major fault was a NAND-area power rail short that showed itself as a very fast amperage spike when injecting at the battery FPC. Clearing that short brought the board back to boot, but did not solve the case.
PRSO pointed in the right general direction, but not to the exact failed location. The charge port was already known-good, and the normal surrounding PRSO suspects did not fit the board.
The remaining corrosion was fairly localized, which made it possible to focus hard on one area instead of chasing imaginary failures across the whole board.
The two key resistors near the camera FPC were not “just camera parts.” One side tied into PP1V8_S2, and the other side fed important paths including the audio amp, charge-port related lines, potassium lines, and I2C1_AOP_SCL.
That is exactly why visual corrosion around resistors matters. A resistor that only feeds a nonessential peripheral can sometimes be left off during a data recovery boot. A resistor bridging a live rail into an important communication path often cannot.
This case is also a reminder that missing resistors do not always create the same symptom. Depending on what the line does, you may get low-amperage brain-dead behavior, a repeating Apple logo, or a timed reboot like this one.
Common Questions About Water-Damaged iPhone Data Recovery
Can you recover data from an iPhone that keeps restarting after water damage?
Yes. If the original logic board can be stabilized enough to stay on, the data can often still be recovered. A restarting phone does not mean the data is gone.
Why does my iPhone keep restarting after water damage?
Water damage can corrode components, short power rails, or damage important board connections. A phone may start to boot again but still restart because another hardware fault remains.
Can water damage cause an iPhone to reboot every few minutes?
Yes. Water damage can leave an iPhone stuck in a repeating restart cycle, especially when corrosion affects lines needed for normal startup and stable operation.
Can photos be recovered from a water-damaged iPhone that will not stay on?
Yes, in many cases. The key is getting the original board stable enough to boot and allow access to the encrypted data stored on the phone.
My iPhone turns on but keeps restarting. Is it still repairable for data recovery?
Often, yes. For data recovery, the goal is not always full long-term repair. The goal is to make the original board work well enough to access the data safely.
Can Apple recover data from a water-damaged iPhone?
Usually no. Apple generally replaces devices rather than performing board-level data recovery on the original logic board.
Should I keep charging or powering on a wet iPhone?
No. Repeated power attempts can make water damage worse. If the data matters, it is better to stop powering it and have the board properly evaluated.
Can data be recovered from a dead water-damaged iPhone?
Sometimes, yes. Recovery depends on whether the original logic board can be repaired enough to boot again, because modern iPhone data stays tied to that original board.
If you have an iPhone that is water-damaged and restarting and need to recover the data:
Comments