EivoTech Laptop & Mobile Repair Master Course
Mobile Repair Course — Part 18
Smartphone Liquid / Water Damage Complete Master Workflow
Chapter 18: Water-Damaged Android aur iPhone ko Safe aur Professional Tareeqe se Diagnose Karna
Liquid-damaged phone repair mein sabse badi mistake ye hoti hai ke technician phone ko baar baar:
Power ON karta hai
Charger lagata hai
Battery reconnect karta hai
sirf check karne ke liye ke phone chalta hai ya nahi.
Liquid damage mein first rule:
POWER ISOLATE FIRST
Master workflow:
POWER ISOLATE → INSPECT → CLEAN → MEASURE → TRACE → REPAIR → FULL TEST
1. Liquid Damage Kya Karta Hai?
Liquid motherboard par multiple types ke faults create kar sakta hai:
Short circuit
Leakage
Corrosion
Open circuit
Connector damage
Component deterioration
Bus communication fault
Isliye liquid damage ko sirf:
“Board short ho gaya”
mat samjho.
2. Water Khud Hamesha Main Problem Nahi
Pure water relatively poor conductor ho sakta hai.
Lekin real-life liquid mein:
Minerals
Salts
Dirt
Sugar
Chemicals
hote hain.
Ye conductivity aur corrosion increase karte hain.
3. Salt Water Sabse Dangerous Kyun?
Salt water conductive aur corrosive hota hai.
Sea water exposure:
Board damage bohat fast kar sakta hai.
4. Sugary Drinks
Examples:
Soft drinks
Juice
Tea/coffee with sugar
Dry hone ke baad sticky residue chhor sakte hain.
Ye:
Leakage
Corrosion
Connector contamination
cause karte hain.
5. Clean Water Exposure bhi Ignore Nahi
Tap water/mineral water mein dissolved minerals hote hain.
Phone chal raha ho tab bhi later corrosion develop ho sakti hai.
6. Liquid + Electricity
Sabse serious damage tab hota hai jab liquid ke waqt board energized ho.
Current + moisture:
Electrochemical corrosion ko accelerate karte hain.
7. Electrolysis Concept
Voltage present ho aur conductive liquid ho:
Metal migration/corrosion rapidly occur kar sakti hai.
Result:
Tracks/pads/components damage.
8. First Action
If wet phone arrives:
Battery / Power Isolate
Charging cable remove.
Phone ko repeatedly ON mat karo.
9. Damaged Battery
Agar battery:
Swollen
Punctured
Unusually warm
Mechanically damaged
ho:
Use/testing stop karo.
Battery ko open ya repair mat karo.
10. Customer se History
Ask:
Kis liquid mein gira?
Kitni der submerged raha?
Phone ON tha?
Uske baad charger lagaya?
Phone kab dead hua?
Koi previous repair hui?
11. Immediate Dead vs Later Dead
Immediately Dead
Possible:
Hard short.
Power-rail fault.
Connector short.
Hours/Days Later Dead
Possible:
Progressive corrosion.
Leakage.
Open trace.
12. Phone Abhi Chal Raha Hai
Still internal inspection useful ho sakti hai if meaningful liquid exposure confirmed.
Because corrosion later fault create kar sakti hai.
13. External Inspection
Check:
Charging port
SIM tray
Speaker holes
Mic holes
Camera area
Display edges
Liquid entry clues.
14. Board Inspection
Microscope under good lighting.
Look for:
Green corrosion
White residue
Blackened pads
Rust-like deposits
Missing components
Solder discoloration
15. Green Corrosion
Copper oxidation/corrosion ka clue ho sakta hai.
16. White Residue
Mineral/salt residue.
Needs proper cleaning.
17. Blackened Component
Could indicate:
Corrosion.
Burn.
Severe oxidation.
Need electrical confirmation.
18. Liquid Indicators
Some phones liquid-contact indicators use karte hain.
Useful clue only.
They don't tell exact damage area.
19. Shields
Corrosion may hide:
Under shields.
Around shield edges.
Under connectors.
20. Don't Remove Every Shield Immediately
First inspect accessible areas.
If evidence points under shield:
Then controlled service/inspection may be justified.
21. Connector Areas High Risk
Especially:
Display connector
Battery connector
Charging flex
Camera connectors
Front sensor connectors
22. Why Connectors Corrode Fast?
Exposed metal contacts.
Small pitch.
Liquid traps.
23. Connector Corrosion Symptoms
Can cause:
No display
No touch
No camera
No charging
No mic
No sensor
Intermittent faults
24. Corrosion Can Create Short
Two adjacent pins/networks can become electrically connected.
25. Corrosion Can Create Open
Metal can be eaten away.
Result:
Broken trace/pad.
26. Corrosion Can Create Leakage
Not full short.
But small unwanted current path.
Can cause:
Battery drain
Random restart
Ghost touch
I2C errors
27. Hard Short vs Leakage
Hard Short
Very low resistance.
Leakage
Abnormally lower resistance but not near-zero.
Both matter.
28. First Electrical Test
With power removed:
Check main rail resistance.
Then suspicious secondary rails.
29. No Blind Powering
If main rail has abnormal hard short:
Don't connect battery repeatedly.
30. Main Rail Normal
Does not mean board healthy.
Secondary rail could be shorted/leaking.
31. Liquid Damage Often Local
Example:
Phone boots.
But camera dead.
Likely camera local corrosion.
Not whole board.
32. Liquid Cleaning Goal
Remove:
Moisture
Ionic residue
Corrosion contamination
without damaging board.
33. Cleaning Is Not Repair by Itself
Important:
CLEANING ≠ COMPLETE REPAIR
After cleaning:
Electrical diagnosis required.
34. Corroded Component
If component/pad already damaged:
Cleaning alone won't restore missing electrical connection.
35. Microscope After Cleaning
Reinspect.
Sometimes corrosion hides:
Missing pad
Broken resistor
Cracked filter
Eaten trace
36. Connector Pin Cleaning
Power removed.
Clean contamination carefully.
Check pin integrity.
37. Broken Connector Pin
If pin physically gone:
Cleaning won't fix.
Connector repair/replacement needed.
38. Under-Connector Corrosion
Can break solder joints.
Symptoms intermittent.
39. Display After Liquid
Possible:
Display module liquid damage
Connector corrosion
Display bias rail fault
Touch bus leakage
40. Black Screen After Water
First prove phone boots.
Then known-good screen.
Don't assume board dead.
41. Touch Ghosting After Water
Could be:
Wet/damaged digitizer
Connector corrosion
Touch bus leakage
Ground contamination
42. Camera After Liquid
Possible:
Module damage
Connector corrosion
Camera rail leakage
I2C bus stuck
43. All Cameras Dead
Check shared:
Camera power.
I2C.
Connector corrosion.
44. One Camera Dead
Specific module/path.
45. Charging After Liquid
Charging port is high-risk entry point.
Possible:
Port corrosion
USB-C CC fault
Lightning interface fault
VBUS protection
Charging IC
46. Phone Charges Slowly After Water
Check:
Port contamination.
Cable contact.
CC/data detection.
Battery condition.
47. No Charging but Wireless Works
Strong clue:
Wired charging path.
48. Mic Problems After Liquid
Mic openings exposed.
Possible:
Mic damaged
Mesh blocked
Sub-board corrosion
Digital mic bus fault
49. Speaker Problems
Liquid can cause:
Muffled sound
Low volume
Speaker module damage
Not motherboard first.
50. Cellular Network After Liquid
Check:
Antenna contacts
Coax
RF filters
Baseband power/control
51. Wi-Fi Weak After Liquid
Likely:
Antenna/contact/front-end corrosion.
52. Sensor Faults
Front sensor area especially vulnerable.
Possible:
Proximity.
ALS.
Face/biometric hardware.
53. Shared I2C Leakage
Corroded sensor can pull SDA/SCL low.
Then multiple sensors disappear.
54. I2C Diagnostic
If SDA/SCL abnormally low:
Isolate removable sensor/module branches where possible.
55. Bus Returns Normal After Disconnect
Strong clue:
Removed component/flex was loading bus.
56. No-Power After Liquid Workflow
Battery disconnected.
↓
Inspect.
↓
Main rail resistance.
↓
PMIC input.
↓
Always-on rail resistance.
↓
Clean/repair corrosion.
↓
Re-measure.
↓
Controlled startup diagnosis.
57. Main Rail Hard Short After Liquid
Map consumers.
Don't randomly remove PMIC.
58. Common Shorted Parts
Could include:
MLCC
Protection IC
Charger IC
Audio amp
Corroded connector
Exact case-specific.
59. Secondary Rail Short
May only prevent boot.
Example:
1.8V sensor/storage rail short.
60. Short Removed but Phone Still Dead
Because liquid may have created multiple faults.
Continue power sequence.
61. Multiple Faults Common
Liquid damage often not one-component repair.
Example:
Main short + connector corrosion + mic fault.
62. Boot Loop After Liquid
Could be:
Battery
Storage
Sensor
Camera
Shared bus
Power rail leakage
63. First Falling Rail
Still use Part 16 logic.
Which rail/signal disappears first?
64. Fixed-Interval Restart
Could indicate expected sensor missing.
Especially after corrosion damaged flex/sensor path.
65. Random Restart
Could be:
Leakage.
Battery.
Thermal sensor.
Power rail.
66. Battery Drain After Liquid
Even if phone works:
Leakage can increase standby current.
67. Phone Gets Warm Idle
Check abnormal leakage.
Identify area.
68. No Blind Voltage Injection
Liquid-damaged board may have unknown damaged sensitive rails.
Never inject arbitrary voltage into unknown net.
69. No High-Current Injection
Could burn corroded traces or damage SoC/storage.
70. Do Not Bypass Protection
Liquid may have triggered fuse/OVP for a reason.
Root cause first.
71. Data-Important Phone
If customer data is important:
Priority:
Preserve Original Board and Boot Path
72. Avoid Unnecessary Restore
Software erase does nothing for corrosion and may lose data.
73. Original SoC/Storage Preservation
Especially modern encrypted phones:
Original security-related hardware matters for user data.
74. Data Recovery Mindset
Goal:
Make original board stable enough to boot and access authorized data.
75. Don't Start with Major BGA Work
First:
Connectors.
Power.
Corrosion.
Peripherals.
Shared buses.
76. Corrosion Near SoC
Serious.
But don't random reflow.
Need evidence of broken rail/signal.
77. Corrosion Under BGA
Possible but harder to confirm.
Use surrounding measurements/logical symptoms.
78. Pad Damage
Corrosion can remove pad.
Repair requires correct net restoration.
79. Trace Damage
Use schematic/BoardView to determine:
Where trace comes from.
Where it goes.
80. Random Jumper Wrong
Especially on:
MIPI.
USB high-speed.
RF.
Memory.
These are impedance-sensitive/high-speed lines.
81. Low-Speed Signal Repair
Some low-speed control lines may be repairable if exact net/path known.
Still follow schematic.
82. Display MIPI Corrosion
Can cause:
Lines.
No image.
Flicker.
Don't use long random jumper.
83. USB High-Speed Corrosion
Can cause:
Charging works.
Data doesn't.
Needs proper high-speed path repair.
84. RF Corrosion
Tiny missing RF passives can cause:
Weak/no network.
Exact part required.
85. Corroded RF Filter
Same-size random component not acceptable.
RF frequency-specific.
86. Audio Corrosion
Codec/amp area can cause:
No sound.
Distortion.
Mic failure.
87. PMIC Corrosion
Could affect multiple rails.
But confirm inputs/outputs/loads.
88. Charging IC Corrosion
May cause:
No charge.
Heating.
VBUS leakage.
89. UFS/NAND Area Corrosion
Potentially data-critical.
Avoid unnecessary heat/rework.
90. Inspect Both Board Sides
Liquid can travel under shields/connectors to opposite side.
91. Flex Cables
Don't ignore:
Corroded flex can load motherboard signal.
92. Known-Good Flex Test
Useful for:
Charging assembly
Display
Camera
Sensors
93. Liquid-Damaged Display Assembly
If screen has moisture internally:
Board repair won't fix panel.
94. Water Resistance After Repair
Original water resistance may not remain after opening.
Important customer expectation.
95. Corrosion Continues?
If ionic residue remains and moisture returns:
Corrosion can continue.
Proper cleaning important.
96. Post-Repair Inspection
Before final assembly:
Recheck previously corroded areas under microscope.
97. Post-Repair Resistance
Check repaired rail resistance against expected/known-good.
98. Post-Repair Power Sequence
Verify:
Main rail.
Standby.
Startup.
Boot.
99. Full Functional Test
Test:
Charging
Display
Touch
Cameras
Speaker
Mics
Wi-Fi
Bluetooth
Cellular
GPS
Sensors
Buttons
100. Why Full Test?
Liquid may damage multiple unrelated subsystems.
Phone boot hona repair completion nahi.
101. Sleep/Battery Drain Test
After repair:
Observe standby behavior.
Liquid leakage may remain.
102. Charging Temperature
Check phone/battery not abnormally warm.
103. Camera Test
All lenses.
Front/rear.
Autofocus.
Flash.
104. Audio Test
Speaker.
Receiver.
Mic.
Recording.
Call audio.
105. Wireless Test
Wi-Fi range.
Bluetooth.
Cellular.
GPS.
106. Sensor Test
Proximity.
Auto brightness.
Rotation.
Fingerprint where applicable.
107. Case Study 1 — Dead after Water
Phone fell in water while ON.
Main rail low resistance.
One corroded main-rail capacitor confirmed faulty.
After repair:
Main rail normal.
But phone still doesn't boot.
Standby rail then found open due corroded bead.
Lesson:
Liquid can create multiple faults.
108. Case Study 2 — Phone Boots, Touch Ghosts
Display appears normal.
Touch ghosting.
Known-good screen works perfectly.
Diagnosis:
Liquid-damaged display/digitizer.
109. Case Study 3 — All Cameras Dead
Phone boots.
Camera power good.
Shared I2C stuck low.
Front camera disconnected:
Bus returns normal.
Root:
Liquid-damaged front camera module.
110. Case Study 4 — No Charging
Wireless charging works.
Wired charging dead.
Charging port heavily corroded.
Direction:
Port/input path.
111. Case Study 5 — Battery Drain
Phone functions normally.
Battery drains overnight.
No hard short.
Sensor rail resistance significantly lower than known-good.
Corrosion leakage found.
Root:
Leakage.
112. Case Study 6 — No Network
SIM detected.
Baseband normal.
Cellular signal weak after water.
RF antenna contact corroded.
Root:
RF antenna path.
113. Case Study 7 — Boot Loop
Phone loops after liquid.
Main rails stable.
Disconnect corroded sensor flex:
Phone boots.
Root:
Peripheral/shared communication fault.
114. Case Study 8 — Mic Dead
Calls recipient cannot hear user.
Voice recording dead.
Bottom sub-board corroded.
Known-good sub-board fixes.
Root:
Mic/sub-board.
115. Case Study 9 — Display Black
Phone detected by PC and rings.
Known-good display still black.
Display bias rail absent due corroded regulator connection.
Direction:
Display power path.
116. Case Study 10 — Charging Icon but No Percentage Increase
Port clean.
Battery health known-good.
Charging power path has corrosion-related high resistance.
Direction:
Charging circuit/path.
117. Case Study 11 — Random Restart
Phone works several minutes.
Repeated diagnostic evidence points temperature sensor invalid.
Corroded sensor line found.
Root:
Sensor path.
118. Case Study 12 — Phone Works Initially after Drying
Three days later Wi-Fi/camera issues appear.
Board inspection reveals developing corrosion.
Lesson:
“Dry phone” does not mean “clean board.”
119. Liquid Damage Worksheet
Phone Model: __________
Liquid Type: __________
Exposure Duration: __________
Phone Was ON: Yes / No
Charged After Exposure: Yes / No
Current Symptoms: __________
Battery Condition: __________
Main Rail Resistance: __________
Visible Corrosion Areas: __________
Connectors Affected: __________
Hard Short: __________
Leakage Suspected: __________
Standby Rails: __________
Startup Rails: __________
Boot Stage: __________
Shared Bus Condition: __________
External Modules Tested: __________
Customer Data Important: __________
Final Fault Areas: __________
120. Post-Cleaning Worksheet
Board Visually Clean: __________
Corroded Components Replaced/Repaired: __________
Open Traces: __________
Shorted Rails: __________
Rail Resistance After Repair: __________
Phone Boots: __________
Charging: __________
Display/Touch: __________
Camera: __________
Audio: __________
Wi-Fi/BT: __________
Cellular: __________
Sensors: __________
Battery Drain: __________
121. No-Power Liquid Decision Tree
Power isolated?
↓
Inspect corrosion.
↓
Main rail abnormal?
YES → Short diagnosis.
NO ↓
Standby rail good?
NO → Standby path.
YES ↓
Power key/startup rails?
↓
First missing stage.
122. Boot-Loop Liquid Decision Tree
Power rails stable?
NO → Power/leakage.
YES ↓
Peripheral/shared bus fault?
↓
Recovery/boot mode stable?
↓
Storage/firmware only after hardware evidence.
123. Function-Specific Liquid Decision
Phone boots?
YES.
Only camera dead?
Focus camera.
Only charging dead?
Focus input/charging.
Only network weak?
Focus antenna/RF.
Don't repair unrelated sections.
124. Common Beginner Mistake 1
Wet phone ko ON karke repeatedly check karna.
125. Common Beginner Mistake 2
Charger laga kar dekhna ke chalega ya nahi.
126. Common Beginner Mistake 3
Cleaning ke baad repair complete samajhna.
127. Common Beginner Mistake 4
Har liquid fault ko short samajhna.
128. Common Beginner Mistake 5
Leakage ignore karna.
129. Common Beginner Mistake 6
External flex/module corrosion ignore karna.
130. Common Beginner Mistake 7
Random PMIC/CPU heat.
131. Common Beginner Mistake 8
High-speed corroded line ko random jumper dena.
132. Common Beginner Mistake 9
Data-important phone ko unnecessarily restore/erase karna.
133. Common Beginner Mistake 10
Phone boot hota hai to full repair complete samajhna.
134. Liquid Damage Golden Rules
1. Liquid phone ka first step power isolation hai.
2. Repeated ON/charging attempts damage increase kar sakte hain.
3. Liquid short, leakage aur open teenon create kar sakta hai.
4. Cleaning sirf first stage hai; electrical diagnosis zaroori hai.
5. Connectors aur exposed flexes high-risk areas hain.
6. One corroded shared-bus device multiple functions fail kar sakta hai.
7. Liquid damage mein multiple faults common hain.
8. Data-important phone mein destructive restore avoid karo.
9. High-speed/RF lines ko random jumpers se repair mat karo.
10. Final repair ke baad full phone QC karo.
135. Part 18 Quick Revision
Corrosion
Metal deterioration due chemical/electrical reaction.
Electrolysis
Voltage + conductive liquid se accelerated chemical damage.
Hard Short
Very-low-resistance unintended path.
Leakage
Partial unwanted current path.
Open Circuit
Broken electrical connection.
Shared Bus Fault
One bad device multiple devices ko affect karta hai.
Data-First Repair
Original board ko stable boot tak restore karna without unnecessary erase.
136. Part 18 ka Sabse Important Lesson
Liquid-damaged phone mein technician ka first question ye nahi:
“PHONE ON HO RAHA HAI?”
Pehla question:
“POWER ABHI ISOLATED HAI?”
Uske baad:
INSPECT → CLEAN → MEASURE → TRACE
Agar short hai:
Rail identify karo.
Agar leakage hai:
Affected branch identify karo.
Agar open hai:
Broken path locate karo.
Agar phone boot ho jata hai:
Tab bhi complete functional test karo.
Because liquid damage:
EK FAULT NAHI — MULTIPLE HIDDEN FAULTS KA SOURCE HO SAKTA HAI.
Professional workflow:
POWER ISOLATE → INSPECT → CLEAN → MEASURE → TRACE → REPAIR → FULL TEST
Mobile Repair Course — Part 18 Complete
Next — Mobile Part 19: Smartphone Schematic + BoardView + Signal Tracing Complete Mastery
Part 19 mein hum cover karenge:
Mobile schematic reading
BoardView navigation
Net names
Power-source to load tracing
Connector pin mapping
Test-point selection
Enable/reset/PGOOD logic
I2C/SPI/UART tracing
Display/touch paths
Camera MIPI/control paths
UFS/eMMC rails
USB-C/Lightning paths
Audio paths
RF power/control paths
Known-good board comparison
Last Good → First Missing method
Master formula:
0 Comments