iPhone 12 Pro Max Ocean Water Damage: Data Recovery
- Aaron Harrington
- Mar 11
- 11 min read
Case category: Water Damage
Failure type: Severe ocean-water damage with multiple board-level faults
Actual billed price: Standard Recovery ($750)
Service page: Water-Damaged iPhone Data Recovery
Severe Saltwater Corrosion, Multiple Board Faults, and One Tiny Resistor That Kept the Phone Boot Looping
Watch the full repair:
Watch on YouTube: https://youtu.be/DerBkfrZ2cY (with comments and chapters)
The Problem [00:00]
This iPhone 12 Pro Max came in after ocean-water exposure with severe visible corrosion throughout the device.
Before I had done any real work, it was already obvious this was not going to be a simple cleaning job. Corrosion was visible under shields, around the connector areas, and in the part of the board where several critical display, touch, and power-related components live. Cases like this are exactly why water-damaged iPhones need a real board-level diagnostic process. The damage is often spread across multiple areas, and the first short you find is not always the last real problem.
Very early in the diagnosis, several serious faults started to show up at once:
severe corrosion around the display / touch area
a short on a 1v2 line near the NAND / EEPROM section
a short on VCC_MAIN
corrosion affecting both the image IC and touch IC area
later, an unexpected Apple logo boot loop caused by one damaged resistor on a CPU-related 0v7 line
One of the tricky things about water damage is that these faults do not have to appear together. Water damage does not have one clean symptom. Any one of these problems could have shown up on its own. A secondary rail short could leave the phone dead. A VDD_MAIN short could leave the phone dead. A different damaged line could let the phone get as far as the Apple logo and then boot loop. In this case, the faults were stacked. Fixing one exposed the next.
It had several overlapping faults, and the final one was the kind of subtle damage many shops would never think to check.
Step 1 – Initial Inspection and First Checks [00:20]
After opening the phone, I left assumptions out of it and started with the basics.
The first thing I checked was whether the power button and volume button lines were shorted to ground, because that can send the phone into misleading modes and waste a lot of time if you miss it. Those lines checked out fine.
But visually, the board already told the real story. There was obvious corrosion around the shielded section near the display and touch-related circuitry, and there was enough damage that I expected problems inside the board sandwich as well.
This is one of the biggest differences between a normal dead iPhone and a severe water-damage case. On a normal no-power phone, you may be able to narrow the issue down quickly. On a saltwater board, you have to assume there may be multiple faults hiding in different layers until the measurements prove otherwise.
Step 2 – Early Rail Checks Showed This Was More Than Cosmetic [04:00]
Before splitting the board, I checked the NAND-area power rails and quickly found something important.
The 2v625 NAND line looked normal. The 0.83 NAND line looked normal. But the 1v2 line did not.
That mattered because 1v2 in this area is not just a random rail. It can involve the EEPROM path, and when I see that line shorted on a data recovery board, I immediately start thinking about the possibility of deeper corruption or instability.
I then checked VCC_MAIN and found that main was shorted too.
So at this stage, I was already dealing with more than just visible corrosion:
one display-related IC area looked heavily damaged
the touch area looked suspicious as well
a 1v2 line was shorted
VCC_MAIN was shorted
That is a lot of damage to stack onto one board before even getting into the deeper repair work.
Step 3 – Splitting the Board and Isolating the Main Damage [12:06]
Once the board was separated and inspected more closely, the picture got better.
The iPhone 12 Pro Max is the only model in the 12 series that needs the bottom board connected to avoid the temperature-sensor issue that blocks access to the data, so I knew I would eventually need a known-good bottom board during extraction.
But first, I needed to clear the real faults.
Around the corroded image / touch section, I found damage serious enough that replacing both chips made sense. The board also showed an important clue on main: one part of the damaged area measured 0.53, while the actual VCC_MAIN via still measured short. That told me the pad itself was no longer directly tied into the rest of main the way it should have been.
That is the kind of detail that matters in water damage. A reading can look “less short” at one point while the real rail is still shorted somewhere else. You have to know whether you are measuring the actual line or a damaged branch that has partially separated from it.
Step 4 – Removing the Damaged Image and Touch ICs [15:07]
At this point, the image IC and touch IC both looked bad enough to come off.
The area was especially risky because the CPU sits directly on the other side, so heat control mattered. This is one of those areas where sloppy technique can turn an already difficult water-damage recovery into a true catastrophic board-loss case.
After removing the image chip, there were clearly issues underneath it. The touch chip came off next, and it showed damage as well.
That was important for two reasons:
First, it explained why the display / touch section looked so ugly on intake.
Second, it gave me a chance to see whether the board would at least begin a proper boot sequence without those failed chips loading things down.
Step 5 – First Boot Behavior After the Corroded Chips Were Removed [22:29]
With the failed image and touch ICs off the board, I checked the boot sequence on the DC power supply.
The board did appear to boot.
That was a major turning point, because it told me the phone was still alive at its core. At that moment, the board had no image and no touch, but it was no longer acting like a completely dead motherboard. That meant the recovery path was still open.
From there, the job shifted from “can the board live?” to “what exactly still needs to be restored so it can boot cleanly and give access to the data?”
Step 6 – The Missing Components That Look Small but Matter for Boot [24:00]
This was one of the most valuable parts of the case.
Around the damaged display / touch area, some capacitors were clearly not critical, while some resistors absolutely were.
That distinction matters. A lot of shops will remove obviously bad-looking parts and assume they can sort out the rest later. But on a board like this, one missing resistor can be the difference between a proper boot and a phone stuck at low amperage forever.
In this case, the important resistors were tied into i2c_display and CPU-related paths. Even though the naming can make them sound display-only, that does not always mean they are display-only in practice. If one side is tied to 1v8 and the other side goes into the CPU, that part may be required for the phone to boot at all.
That is why I said in the video that a board missing those resistors could easily end up stuck in “brain dead” mode around 0.06 to 0.07 amps. This is exactly the sort of failure most people do not think to check when they see a low-amperage dead phone.
Step 7 – Cleaning Up the 1v2_SoC Area [30:13]
There was also a group of damaged-looking capacitors on the 1v2_SoC line.
They did not measure fully short, and I pointed out why that made sense: if that line were hard shorted, I would not have already seen a decent boot sequence. But they still looked bad enough that I did not want to trust them.
After removing them, the reading changed significantly, which suggested they may have been partially loading the line even if they were not a full short.
That is another good example of how water damage can behave. The board may boot, but not boot cleanly. A rail may not be dead short, but still damaged enough to destabilize the phone. A lot of real data recovery work lives in those gray areas.
Step 8 – Reinstalling the Chips and Hitting an Unexpected Apple Logo Boot Loop [47:32]
After rebuilding the damaged display / touch section and reconnecting known-good parts, the board got far enough to show the Apple logo.
Then it boot looped.
That was not what I expected.
At that stage, an Apple logo boot loop told me the phone was already much further through the boot sequence than a truly brain-dead device. It also meant I had likely cleared the earlier major faults. But something was still wrong, and it was wrong late enough in the process to stop the phone just before a usable boot.
This is exactly why “my iPhone is boot looping” is not a diagnosis. An Apple logo loop can come from dozens of different faults. In this case, it turned out to be something extremely specific and unusual.
Step 9 – The Last Real Problem: One Damaged 0v7 CPU-Related Resistor [55:14]
The final fault was a small resistor in the same water-damaged area that had already caused so much trouble.
Visually, it was obvious that the resistor was no longer properly connected. Once I checked what it did, it made perfect sense why the phone was still failing.
The line was tied into PP0V7_VDD_LOW_S2, and on the other side it was connected into CPU-related communication paths including PP0V7_VDD_LOW_ULPPLL and PP0V7_VDD_LOW_FLPPLL.
I said it clearly in the video: I do not even need to know exactly what every one of those communication paths does in order to know this resistor is important. It runs between the PMIC side and the CPU side. That alone is enough to treat it seriously.
This is the kind of fault that proves why visual inspection still matters in advanced board work.
A normal diagnostic routine might never lead someone to check that resistor. If you only check the “common” failures, you can miss the one obscure damaged part actually stopping the phone from booting.
Once that resistor issue was addressed, the path to recovery was clear.
The Result – 100% Data Recovered [01:08:15]
Device: iPhone 12 Pro Max
Condition on arrival:
Severe ocean-water damage with visible corrosion across multiple areas of the phone and motherboard.
Main fault symptoms:
heavy localized corrosion around the display / touch section
short on a 1v2 line near the NAND / EEPROM area
VCC_MAIN short
failed image IC area
failed touch IC area
Apple logo boot loop after major faults were corrected
final boot issue caused by one damaged resistor on a 0v7 CPU-related line
Work performed:
full intake inspection and connector-line checks
board separation and corrosion mapping
rail testing around NAND, EEPROM, 1v2, and VCC_MAIN
removal of the damaged image IC and touch IC
analysis of missing / damaged surrounding resistors and capacitors
cleanup of partially damaged 1v2_SoC area
rebuild of the display / touch section with donor parts
identification and correction of the final damaged 0v7 CPU-related resistor
final stabilization for data access
Outcome:
✅ 100% successful recovery.The board was stabilized, the boot loop was resolved, and the customer’s data was recovered.
Conclusion
This was a very good example of why ocean-water data recovery is not about guessing and it is not about rushing to CPU work.
The first obvious problems were real. The 1v2 issue was real. The VCC_MAIN short was real. The image and touch chip damage were real. But even after all of that, the phone still had one final failure hiding in plain sight: a tiny resistor on a CPU-related 0v7 line.
That is what makes water-damaged boards dangerous in the wrong hands. A shop can fix several genuine faults and still miss the one subtle damaged part actually stopping the device from finishing boot.
This iPhone did not need a dramatic “hail Mary” repair. It needed careful diagnosis, correct sequencing, and enough board-level experience to know when a tiny resistor matters more than a much larger-looking problem.
Nerd Corner (For Technicians & Repair Shops)
A few technical notes from this job stood out:
The initial NAND-area checks were useful because 2v625 NAND and 0.83 NAND looked normal, while 1v2 did not. That helped narrow attention toward the EEPROM / surrounding shared-line area instead of blindly blaming NAND itself.
VCC_MAIN was not just “short everywhere.” One damaged section read around 0.53 while the actual via still showed the real short. That strongly suggested part of the damaged area had become electrically separated from the rest of main.
The image IC and touch IC area had severe enough corrosion that removing both chips was the right call. Once they were off, the board showed a valid-looking boot sequence, which confirmed the board was still fundamentally alive.
The i2c / display-related resistor section was more important than it looked. Some of those resistors were not just “for display.” Because they tied 1v8 into CPU-related paths, missing them could plausibly leave the board stuck in 0.06–0.07A brain-dead mode.
The damaged capacitors on 1v2_SoC did not read hard short, but the measurement changed after removal. That is a good example of partial loading or damage severe enough to affect stability without creating a textbook dead short.
The last real problem was the damaged resistor tied into PP0V7_VDD_LOW_S2 and CPU-related lines including PP0V7_VDD_LOW_ULPPLL / FLPPLL. That is the kind of obscure water-damage failure that proves why visual inspection of corroded resistors matters just as much as checking shorted capacitors.
This is also a good example of why an Apple logo boot loop is not a diagnosis. In this case, it was not NAND, not a generic restore issue, and not a random software fault. It was one damaged resistor in a highly specific corroded area.
Common Questions About Water-Damaged iPhone Data Recovery
Can you recover data from a water-damaged iPhone 12 Pro Max?
Yes. Water-damaged iPhone data recovery depends on getting the original logic board stable enough to boot again. In this case, the phone had multiple board-level problems from ocean-water corrosion, but the data was successfully recovered from the original board.
Why is my iPhone completely dead after water damage?
Water damage can kill an iPhone in several different ways. Corrosion can short major power lines, damage secondary rails, break communication lines, or destroy important components around the board. In this case, the phone had more than one serious fault, and any one of them could have caused a dead iPhone by itself.
Can water damage cause an iPhone to get stuck on the Apple logo?
Yes. Water damage does not always leave a phone fully dead. A damaged line or component can allow the phone to start booting, reach the Apple logo, and then restart over and over. In this case, the final boot-loop problem came from corrosion damaging a small but important component in a CPU-related circuit.
Why do water-damaged iPhones have different symptoms?
Water damage does not create one fixed symptom. One iPhone may be completely dead. Another may be stuck at low amperage and never properly boot. Another may show the Apple logo and repeat. In severe cases, several of those failures can exist on the same board at once, and fixing one problem may only reveal the next one underneath.
Is ocean water damage worse than normal water damage on an iPhone?
Yes. Ocean water is especially destructive because salt and minerals make corrosion more aggressive and more conductive. That increases the chances of shorts, damaged pads, broken lines, and hidden board-level failures under shields or around critical chips.
Does a boot looping iPhone after water damage still have recoverable data?
Yes. A boot loop does not automatically mean the data is gone. It means the phone is failing somewhere during startup. The real question is what motherboard fault is causing the loop, and whether the original board can be stabilized enough to finish booting and allow access to the encrypted data.
Should a shop jump straight to CPU work on a water-damaged iPhone?
No. Water-damaged iPhones should be diagnosed first. Most liquid-damaged boards fail from corrosion-related shorts, missing components, damaged pads, or broken communication lines on the original board. Jumping straight to CPU work adds risk and can damage the best chance of recovery.
If you have a water-damaged iPhone:
Comments