crwdns2894164:0crwdne2894164:0

Released September 20, Apple's largest and most expensive 2019 smartphone features a 6.5" OLED display, a triple-lens camera system, and greatly improved battery life. Successor to the iPhone XS Max.

crwdns2886949:096crwdne2886949:0 crwdns2858137:0crwdne2858137:0

iPhone 11 Pro Max not charging.

Hi all,

So I have this 11PM that has a dead battery (Which is Apple original), no problem I'll replace the battery. After replacing the battery I found that the device turned on but was stuck at 0% and not charging, it would also not show any battery information on 3uTools with the battery value and the ex-factory value both being at N/A, an indication that it is not reading information from the bottom connector.

After checking all the connections I tried a different battery from a different reputable supplier but have exactly the same issue. Both of these batteries give me all of their information on my jc v1s just not in the iPhone and thus although it does turn on it will not charge but it does still detect USB.

I should also note that the iPhone does not draw any current from a wall socket.

Any advice on next steps?

Thank you,

Tom

crwdns2893858:0crwdne2893858:0 crwdns2893862:0crwdne2893862:0

crwdns2894050:0crwdne2894050:0

crwdns2889612:0crwdne2889612:0 1
crwdns2892346:0crwdne2892346:0

crwdns2886778:01crwdne2886778:0

crwdns2893814:0crwdne2893814:0

Sounds like a problem with the charge port (the original battery may not even need replacing) The phone only turns on because replacement batteries are usually (should be) shipped with some charge.

I can't explain the zero percent indication though, other than that there maybe issues with your replacement batteries.

Do you get the same result charging it via a wireless charger?

crwdns2894046:0crwdne2894046:0

crwdns2889612:0crwdne2889612:0 1

crwdns2893872:0crwdne2893872:0:

I would absolutely agree with this assessment. As for why it would be showing zero percent, bear in mind that the 11 Pro/Pro Max batteries actually have 2 connectors.

One goes directly into the logic board. The second, "south" battery connector, is part of a small daughterboard, which is essentially a part of the dock assembly. This daughterboard contains the charging chip itself. And battery sensor data needs to travel to that chip. So if there is damage to the flex cable that data can be garbled or can't get where it needs to. So the battery may misreport how much charge is left because it cannot communicate that information effectively.

crwdns2893770:0crwdnd2893770:0crwdne2893770:0

Yes wireless charging creates the same issue, I don't think it is the charging port because the phone does detect a charge because it says charged 0% but never goes up. It also connects to a pc just fine and allowed me to restore just fine as well. Like Alisha said i believe it is the south connection i'm having issues with as when the first connector is plugged directly into the logic board without the osuth connector connected the phone boots with the 0% issue. But when I connect the south connector, the phone will no longer even give me an Apple logo until I disconnect the south connector and then it will turn on with the issues mentioned above.

crwdns2893770:0crwdnd2893770:0crwdne2893770:0

Also, after you mentioned with the original battery I tried the original battery without the south connector attached and it booted up but with the same 0% and no battery information issue as with the other batteries and connecting the south port (With the device off and battery disconnected of course) the phone failed to boot once again, so thats 3 batteries 1 Apple original and 2 from different suppliers so I think I can rule out battery issues.

crwdns2893770:0crwdnd2893770:0crwdne2893770:0

My apologies! I've only just realised the daughterboard is attached to the charging port so yes I do agree that it is the charging port that's the issue. I'll order a genuine pull and keep you updated. Thank you for your advice!

crwdns2893770:0crwdnd2893770:0crwdne2893770:0

Well a new charging port didn't fix the issue unfortunately, still the same problems :( looks like mainboard issues I guess

crwdns2893770:0crwdnd2893770:0crwdne2893770:0

crwdns2892346:0crwdne2892346:0

crwdns2893896:0crwdne2893896:0

Thomas Watson crwdns2893898:0crwdne2893898:0
crwdns2894754:0crwdne2894754:0:

crwdns2894766:024crwdne2894766:0 0

crwdns2894768:07crwdne2894768:0 3

crwdns2894768:030crwdne2894768:0 26

crwdns2894770:0crwdne2894770:0 62