iPhone 16 Pro Max Stopped Charging: Data Recovery
- Aaron Harrington
- Apr 8
- 11 min read
Updated: 5 days ago
Diagnosing a 3-Stage Board Failure
Case category: Dead / No Power
Failure type: Multi-stage charging circuit failure
Actual billed price: Standard Recovery ($750)
Service page: Dead iPhone Data Recovery
Watch the full repair:
Watch on YouTube: https://youtu.be/qkFctJpCMkY (with comments and chapters)
The Problem [00:00]
This iPhone 16 Pro Max died immediately after a charging event. According to the customer, the phone got hot after being plugged into a charger and then would no longer turn on.
At the bench, the first surprise was that this was not a simple “dead short equals dead phone” case. Through the battery connector on a DC power supply, the board would still respond to a prompt-to-boot. But through the charge port, it took essentially no amperage at all.
That told me something important right away: the phone was not truly dead in the usual sense. It could still boot. The real problem was that the charging circuitry had suffered severe damage, and that damage was preventing the device from charging normally, staying stable on external power, or connecting properly for extraction.
What followed turned into one of the strangest charging failures I have seen on a modern iPhone: multiple separate faults inside the charging path, all apparently caused by one bad charging event.
Step 1 – Initial Bench Diagnosis [00:46]
After removing the motherboard from the housing, I started with the basic checks I always use on “dead” iPhones.
The phone showed no charging behavior through the USB ammeter. But when I powered it directly through the battery connector and manually prompted boot, it did come to life. That immediately changed the direction of the case. I was no longer looking at a classic no-power board. I was looking at a true no-charging failure severe enough to leave the customer with a dead phone.
From there, I moved into the charging sequence and started tracing the main charging-related ICs and their rails to figure out where the failure was beginning.
Step 2 – Finding the First Fault at U4000 [13:42]
With the shield removed and the charging rails exposed, I started comparing how the board reacted when voltage was injected into different points in the circuit.
That mattered here because the behavior was not the same on every line. Injecting into VDD main produced only a small draw, but injecting into the charging-side rail produced the larger leak I had been seeing. On thermal camera, that difference pointed directly at U4000.
Once I measured the surrounding components closely, I found a tiny capacitor tied to a U4000 internal fly-capacitor line that was showing a measurable short on a side that should not have had a path to ground at all. That was the first real smoking gun in the case.
At that point, the plan was clear: remove U4000, confirm the short clears, then replace the chip.
Step 3 – Replacing U4000 Clears the First Problem [23:19]
I harvested a donor U4000, reballed it, and installed it onto the customer board.
That repair did exactly what it was supposed to do: it cleared the original measurable fault. The phone powered on, read battery data again, and looked healthier than before.
But the case was not over.
Even after the first charging IC was fixed, the phone still would not charge normally. The charging icon flashed on and off, the ammeter still showed essentially no real charging current, and the phone would not stay stable enough for a normal wired extraction.
That is what made this case so unusual. The first problem was real. Fixing it did matter. It just was not the only problem.
Step 4 – The Residual Leak and the Real Second Failure [29:01]
After the U4000 repair, I still had a small pre-boot amperage leak showing on both main and battery. That told me there had to be another problem further along in the system.
There was a stretch here where I had to slow down and think through the sequence carefully. One suspect reading in the charging path looked abnormal enough that I chased it, but donor-board comparison later showed that reading was actually normal. That mattered, because it kept the repair honest. Not every weird measurement is the final answer.
The real second fault turned out to be elsewhere: a smaller charging/accessory-related IC with an enable line that was hard shorted. With one-volt injection, that line pulled heavy current immediately, which confirmed it was not just a misleading diode reading or schematic confusion.
I first removed the nearby capacitor to rule out a simple cap short. The short remained. I then removed the IC itself, and the short cleared.
That instantly resolved the residual leak on both main and battery.
So now the picture was becoming clearer:
The bad charging event had not damaged just one chip. It had damaged multiple parts of the charging system in separate ways.
Step 5 – Still No Charging: One More Failure in the Path [57:24]
At that point, I expected the phone to finally behave normally.
It did not.
Even after clearing the original U4000 problem and the smaller accessory/enable-line short, the phone still would not charge correctly. The screen would flash the charging symbol on and off, and the ammeter would occasionally blink a reading but not settle into normal charging behavior.
That is when this crossed over from a strange case into what I would call truly catastrophic charging circuit damage.
By then, process of elimination narrowed the remaining failure down to the final charging logic stage. I briefly tested the reverse-voltage-protection path by replacing the MOSFET feeding the protected VBUS line, but that did not solve it.
That left the real remaining suspect: U9500 and its paired ROM.
Step 6 – Replacing U9500 and the Paired ROM [01:02:30]
Because U9500 is paired to its ROM, this was not a simple chip swap.
I removed the damaged charging logic IC, harvested a donor replacement, reballed it, and then replaced the paired ROM from the same donor set so the charging logic stage would remain properly matched.
This was the last major repair in the chain.
Once those parts were installed, I cleaned the work, returned the board to the testing setup, and checked charging behavior again.
Step 7 – Final Test and Complete Extraction [01:05:23]
This time, the board immediately behaved the way it should have from the beginning.
The phone prompted to boot through the charge port. The USB ammeter showed normal charging current. The charging icon behaved normally. Replugging the cable produced the same correct result again.
In other words, the charging system was finally back.
This device also turned out not to have Stolen Device Protection enabled, which meant I could complete a normal full extraction once the board was stable.
The Result – 100% Data Recovered [01:06:30]
Device: iPhone 16 Pro Max
Condition on arrival:
Completely dead after a charging event. Customer reported the device got hot on the charger and then would not turn back on.
Main fault symptoms:
No meaningful amperage draw through the charge port
Phone could still boot when prompted through the battery connector
Flashing/intermittent charging icon
Failure to maintain a stable wired data connection
Multiple separate charging-circuit faults caused by one event
Work performed:
Initial bench triage using USB ammeter and DC power supply
Charging-path diagnosis using schematics, diode mode, voltage injection, and thermal camera
U4000 replacement after confirming a measurable internal-line short
Isolation and removal of a second shorted charging/accessory-related IC tied to the residual pre-boot leak
Reverse-voltage-protection stage tested as part of process-of-elimination work
U9500 charging logic IC and paired ROM replaced
Final board testing and full extraction
Outcome:
✅ 100% successful recovery. The phone was stabilized, normal charging behavior was restored, and the customer’s data was fully extracted.
Conclusion
This repair is a good example of why understanding sequence matters, even when your first theory is not perfect.
The first bad chip was real. The second leak was real. The final charging logic failure was real. If I had assumed they were all the same issue, or if I had stopped after the first repair just because the phone booted, I still would not have had a usable recovery path.
That is what made this case valuable: each measurable change told me whether I had actually fixed the problem in front of me, or only one layer of a much larger failure.
This was not a single charging fault. It was cascading charging-circuit damage from one bad event.
Nerd Corner (For Technicians & Repair Shops)
This case was worth documenting because the charging failure was not just “bad charging chip = replace charging chip.” The board behavior split into multiple distinct problems, and the rail behavior mattered.
PP_VBUS1_E85 was the starting point from the charge port. From there, charger voltage fed U4000 directly and also passed through the MOSFET path that created the protected VBUS_RVP line going into U9500.
U4000 was taking that charger input and producing VDD_SNS_BPIC. From there, U4200 used that rail to create VDD_MAIN. That distinction mattered, because the failure pattern did not behave the same on the BPIC side as it did on main.
Early in diagnosis, injection behavior split cleanly:
VDD_MAIN showed about 0.02A
BAT_VCC showed about 0.06A
injecting on VDD_MAIN showed very little on thermal cam
moving injection to BAT_VCC clearly heated U4000
That difference was important because it showed the heavier leak was still upstream on the BAT_VCC side, not fully present on VDD_MAIN yet.
On the bad U4000 section, the measurable fault was on a capacitor tied to the chip’s internal fly-capacitor circuitry. In the video, that was compared to the CFLY behavior:
previous known-bad example: CFLY-N
this case: the opposite side, CFLY-P, was the side showing short to ground even though it should have had no pathway to ground
That is the kind of measurement I like because it is not just “this area gets hot.” It is a real schematic-backed fault: a line that should not read to ground was reading to ground.
Before the first repair, the major leak pattern was:
roughly 0.06A on BATT_VCC_BPIC side
only about 0.02A on VDD_MAIN
After replacing U4000, that original measurable short cleared. The capacitor that had been showing short was no longer short. That proved the first fault was real and the chip replacement mattered.
But the case did not end there. After the U4000 repair, there was still a residual leak:
about 0.015 to 0.016A on main
and about 0.015 to 0.016A on VBAT
That second pattern was different from the original 0.06A VBAT leak, and that difference helped separate “first bad chip” from “second remaining fault.”
The next real failure was on the USB accessory side, specifically the enable line on U9800.
that enable line measured fully short to ground
there was a 39K resistor in the path
the rail on the other side was referenced as 3V3
when 1V was injected onto that enable line, it pulled about 0.8A
That was a strong clue because it ruled out a vague or misleading reading. A one-volt probe pulling roughly 0.8A on an enable line is not normal interpretation noise. Something there was genuinely dragged down hard.
The nearby capacitor was removed first to rule out a simple cap short. The short remained. Once the IC was removed, the line cleared.
Clearing that U9800 enable-line short also cleared the 0.016A leak that had been showing on both VDD_MAIN and VBAT.
At that point the board still was not charging correctly. The phone showed a flashing charging icon and still would not take normal current through the charge port.
From there, the remaining charging-path suspect narrowed to U9500 and its protected charger input path:
raw charger line: VBUS
protected version feeding U9500: VBUS_RVP
The MOSFET in that RVP stage was tested/replaced as part of process-of-elimination work, but it did not solve the flashing-charge behavior.
Final fix was U9500 plus its paired ROM. Once that matched pair was replaced, the board finally:
prompted to boot through the charge port
showed normal amperage through the ammeter
displayed a normal charging icon instead of cycling on and off
The big lesson here is that the numbers mattered. This was not random parts swapping. The difference between 0.06 on the VBAT side, 0.02 on main, and the later 0.016 leak on both main and VBAT is what separated one charging failure from another and kept the repair grounded in sequence.
iPhone 16 Pro Max Charging Failure Data Recovery – Common Questions
My iPhone 16 Pro Max got hot while charging and now it will not turn on. Can the data still be recovered?
Yes, most of the time. In this case, the phone was effectively dead to the customer because it would not charge, but the original board could still be made to boot once the charging-circuit damage was repaired. When the original encrypted logic board is preserved, full data recovery is still possible.
iPhone 16 Pro Max shows no charging amperage through the port, but it still boots on DC power supply. What does that mean?
That usually points to a true no-charging failure rather than a classic full no-power main short. In this case, the phone would boot when powered directly at the battery connector, but it would not take normal current through the charge port because multiple charging-related chips had been damaged.
Why is my iPhone 16 Pro Max flashing the charging icon on and off but not actually charging?
A flashing charging icon can mean the phone is seeing charger presence intermittently, but the charging path is failing deeper in the circuit. In this case, the cycling charge icon remained even after the first charging repair and was only fully resolved after the final charging logic stage was repaired.
Can one bad charger damage multiple charging chips on an iPhone 16 Pro Max?
Yes. That is what made this case unusual. This was not one simple failed IC. The charging event appears to have damaged U4000, a separate USB accessory / enable-line circuit, and finally U9500 / ROM, all in the same chain.
iPhone 16 Pro Max stuck at 1% and not reading battery correctly after charger damage — is that a charging IC problem?
It can be. In this case, the phone came up showing behavior consistent with a charging-circuit fault and an inability to read battery data normally. That does not automatically mean the battery itself is bad. Board-level charging faults can create the same symptom.
Does a flashing charging symbol mean the motherboard is destroyed?
Not necessarily. It does mean the phone needs proper board-level diagnosis. A cycling charge icon can come from a damaged charging path, a protected VBUS problem, charging logic failure, or other rail-level issues. It is not something a battery swap or charging-port guess should be expected to solve.
My iPhone 16 Pro Max died after plugging in a charger. Do I need a CPU swap for data recovery?
Usually, no. This case did not need CPU work. The recovery was completed on the original board by repairing the damaged charging circuitry. CPU-level work is a last resort, not the default answer for a phone that died during charging.
Can an iPhone have more than one charging-circuit failure at the same time?
Absolutely. This case is a good example. The first measurable fault was real, but fixing it did not solve the entire problem. There was still a second short and then a final charging-logic failure after that. That is why sequence-based diagnosis matters.
What is the difference between a dead iPhone and a no-charging iPhone in data recovery?
A truly dead iPhone may have a main power issue that prevents all boot activity. A no-charging iPhone may still be capable of booting if powered another way, but cannot charge normally, stay stable, or connect for extraction. From the customer’s point of view both phones look “dead,” but the board-level diagnosis is very different.
If my iPhone 16 Pro Max got hot on the charger and died, should a shop replace the charging chip immediately?
Not blindly. In this case, replacing the first bad charging chip was necessary, but it was not the whole answer. The right approach is to diagnose the exact rails, compare measurements, follow the sequence, and confirm which part of the charging path is actually failing before moving on.
If you have an iPhone 16 Pro Max that is not charging and need to recover the data:
Comments