EivoTech Laptop & Mobile Repair Master Course
Mobile Repair Course — Part 19
Smartphone Schematic + BoardView + Signal Tracing Complete Mastery
Chapter 19: Mobile Motherboard ko Diagram ki Madad se Logical Tareeqe se Diagnose Karna
Mobile repair mein microscope, multimeter aur soldering skills bohat important hain.
Lekin advanced technician ki sabse powerful skill hoti hai:
SCHEMATIC KO SAMJHNA AUR BOARDVIEW SE EXACT CIRCUIT TRACE KARNA
Agar technician schematic nahi samajhta to wo aksar:
Random components check karta hai
Random IC replace karta hai
Beep sun kar short bol deta hai
Voltage missing dekh kar regulator replace kar deta hai
Professional diagnosis ka master formula:
SYMPTOM → BLOCK → SCHEMATIC → NET → TEST POINT → LAST GOOD → FIRST MISSING → ROOT CAUSE
1. Schematic Kya Hai?
Schematic motherboard ka electrical map hota hai.
Ye batata hai:
Components electrically kaise connected hain
Kaunsi rail kahan se aa rahi hai
Kaunsa signal kis IC ko ja raha hai
Enable/reset/clock/data paths kya hain
2. BoardView Kya Hai?
BoardView motherboard ka physical layout map hota hai.
Ye batata hai:
Component board par kahan laga hai
Component reference kya hai
Kis pad par kaunsi net hai
Same net par aur kaun components hain
3. Schematic vs BoardView
Schematic
Electrical relationship.
BoardView
Physical location.
Best diagnosis:
SCHEMATIC + BOARDVIEW TOGETHER
4. Example
Schematic tells:
PMIC output
↓
L1200
↓
PP_1V8
↓
UFS + Camera + Sensors
BoardView tells:
L1200 board par exactly kahan hai.
5. Component Reference Designators
Common references:
R
Resistor
C
Capacitor
L
Inductor / Coil / Ferrite
U
IC
Q
Transistor / MOSFET
D
Diode
F
Fuse
J
Connector
Exact manufacturer naming vary kar sakti hai.
6. Net Name Kya Hai?
Net electrically connected points ka naam hai.
Example:
PP_BATT_VCC
ya:
VPH_PWR
ya:
1V8_IO
Same net ke multiple capacitors/components electrically connected ho sakte hain.
7. Same Net = Same Electrical Rail/Signal
Agar BoardView mein 20 capacitors same net show karte hain:
All electrically same power rail par hain.
Isliye ek capacitor beep kare to sab beep kar sakte hain.
8. Power Net vs Signal Net
Power Net
Voltage supply.
Example:
1.8V rail.
Signal Net
Control/data communication.
Example:
RESET_N.
SCL.
SDA.
9. Ground Net
Ground common reference.
Often names:
GND
VSS
AGND
DGND
depending circuit.
10. Schematic Reading Start Kahan Se Karni Hai?
Fault symptom se.
Example:
Camera dead.
Do not open PMIC page randomly.
Start:
Camera block.
11. Symptom → Block
Examples:
No Charge
USB/charging block.
No Display
Display block.
No Touch
Touch block.
No Wi-Fi
Wireless block.
No Service
SIM/baseband/RF block.
No Power
Main power/PMIC block.
12. Block Diagram Thinking
Before individual components:
Understand overall chain.
Example charging:
PORT → PROTECTION → CHARGER IC → BATTERY
Display:
SoC → MIPI → CONNECTOR → PANEL
13. Signal Tracing ka Basic Rule
Always ask:
Signal kahan se aa raha hai aur kahan ja raha hai?
Source.
Path.
Destination.
14. Source
Signal/rail generate karta hai.
Examples:
PMIC.
SoC.
Clock IC.
Regulator.
15. Destination / Load
Signal use karta hai.
Examples:
UFS.
Camera.
Display.
Sensor.
16. Intermediate Components
Source aur destination ke beech ho sakte hain:
Resistor
Filter
Ferrite bead
ESD protection
Connector
Switch
17. Power Rail Trace Formula
SOURCE → COIL/LDO → FILTER/BEAD → LOAD
18. Control Signal Trace Formula
CONTROLLER → SERIES/PULL COMPONENT → DESTINATION
19. Communication Bus Formula
MASTER → BUS → DEVICE
Example:
SoC
↓
I2C SDA/SCL
↓
Camera sensor.
20. Last Good → First Missing
Ye entire repair course ka strongest method hai.
Measure sequence points.
Example:
PMIC VIN ✅
PMIC EN ✅
PMIC OUT ❌
Then fault area:
Regulator/output/load.
21. Example 2
Battery rail ✅
PMIC standby ✅
Power key ✅
CPU auxiliary rail ✅
RAM rail ❌
Then first missing:
RAM rail.
22. Why Last Good Important?
Last good point prove karta hai:
Upstream circuit wahan tak working hai.
23. Why First Missing Important?
First missing point root cause area ko narrow karta hai.
Later missing signals may simply be consequences.
24. Test Point Selection
Best test point wo hai jo:
Easily accessible ho
Same net par ho
Probe slip risk low ho
Component damage risk low ho
25. Good Power Test Points
Usually:
Coil output
Large capacitor
Test pad
Ferrite bead side
26. Bad Test Point
Dense BGA pin directly probe karna.
Risk:
Short between pins.
Probe slip.
Board damage.
27. Connector Pin Testing
Connector par testing useful hai.
But:
Use exact pinout.
Power isolate when resistance/diode testing.
Avoid bridging neighboring pins.
28. Coil as Test Point
Buck regulator output coil commonly excellent voltage test point.
29. Capacitor as Test Point
A capacitor connected to rail gives convenient:
Voltage.
Resistance-to-ground.
Diode comparison.
30. Ferrite Bead as Diagnostic Point
Bead ke dono sides compare karo.
If upstream voltage present but downstream absent:
Possible open bead/path or downstream issue.
31. Fuse as Diagnostic Point
Input side voltage ✅
Output side voltage ❌
Fuse open possible.
But:
Never bridge before root cause.
32. Resistor in Signal Path
Series resistor can be useful.
Check:
Source side.
Destination side.
If source changes but destination not:
Resistor/trace/path issue.
33. Pull-Up Resistor
Digital buses such as I2C often use pull-ups.
SDA/SCL idle high reh sakti hain.
34. Pull-Up Missing
Bus may not communicate.
35. Pull-Down
Some control signals use pull-down to define default state.
36. Enable Signal
Possible names:
EN
ENABLE
REG_ON
PWR_EN
37. Enable Diagnosis
Regulator output missing.
Check:
VIN
EN
OUT
Master formula:
VIN → EN → OUT
38. VIN Missing
Upstream source fault.
39. EN Missing
Control/upstream logic.
Do not replace regulator immediately.
40. VIN + EN Good, OUT Missing
Possible:
Output short
Regulator fault
Incorrect mode/control
41. PGOOD
Power Good signal.
Regulator tells controller:
“My output is stable.”
42. PGOOD Missing
Could stop next boot stage.
43. Reset Signal
Reset keeps IC held inactive until system ready.
Possible names:
RST
RESET_N
RST_N
44. _N / #
Usually active-low notation.
Meaning signal is asserted when low.
Always verify schematic.
45. Reset Diagnosis
Power good but device inactive.
Check:
Reset released?
46. Clock Signal
Digital IC commonly needs clock.
Examples:
UFS.
Camera.
Wi-Fi.
SoC subsystems.
47. Clock Missing
Power may be perfect but IC still dead.
48. Clock Testing
Clock diagnosis often needs oscilloscope or indirect evidence.
Do not randomly short/probe dense clock pins.
49. I2C
Common low-speed control bus.
Lines:
SDA
SCL
50. I2C Master
Usually SoC/controller.
51. I2C Slave
Examples:
Camera sensor.
Touch controller.
Sensor.
Power IC.
52. I2C Stuck Low
If SDA or SCL stuck low:
One device can block whole bus.
53. Shared Bus Fault
Multiple devices dead together?
Look for shared I2C.
54. I2C Isolation
If removable module is on bus:
Power off.
Disconnect module.
Recheck bus.
55. Bus Returns Normal
Strong clue removed module was loading bus.
56. SPI
Higher-speed serial control/data bus.
Signals may include:
Clock.
Data in/out.
Chip select.
57. UART
Serial communication.
Often used for:
Diagnostics.
Boot communication.
Internal interfaces.
58. USB Data Path
Simplified:
Connector
↓
ESD
↓
Mux/PHY
↓
SoC.
59. USB Charging vs Data
Same connector but different paths.
Phone charges but PC doesn't detect:
Data path.
60. USB-C CC Path
CC1/CC2:
Orientation/detection/power negotiation.
If one orientation works:
CC branch clue.
61. Lightning Path
Lightning has proprietary reversible interface.
Diagnosis high-level:
Port/flex
↓
Detection/interface
↓
USB/data/charging control.
62. Display Schematic Tracing
Master path:
DISPLAY POWER + RESET + MIPI DATA → PANEL
63. Display Power Page
Find:
Display regulator/bias IC.
Output coils/caps.
Enable.
Connector.
64. Display No Image
Trace:
Boot confirmed?
↓
Panel power?
↓
Reset?
↓
MIPI path?
65. LCD Backlight
Separate path:
Power
↓
Boost driver
↓
BL_EN/PWM
↓
LED string.
66. OLED
No traditional backlight.
Focus:
Panel power.
Reset.
MIPI.
67. Touch Circuit
Master flow:
TOUCH POWER → RESET → I2C/SPI → INTERRUPT
68. Touch Power Good, Bus Dead
Focus:
Connector.
Bus component.
Touch controller/module.
69. Camera Schematic
Main formula:
POWER → RESET → I2C → MCLK → MIPI CSI
70. Camera Power Rails
Multiple supplies can be present.
Always map exact rail to exact camera.
71. One Camera Dead
Specific rail/control/data path.
72. All Cameras Dead
Search shared:
Power.
I2C.
Clock/control.
73. Camera MIPI
High-speed differential data.
Do not treat as normal low-speed jumper.
74. UFS Schematic
Main areas:
Core power
I/O power
Reset
Reference clock
High-speed data lanes
75. Storage Power First
Before UFS replacement:
Verify required rails.
76. UFS Reset
Power good but reset held?
No communication.
77. UFS Clock
Clock missing can stop storage access.
78. UFS High-Speed Data
Direct SoC link.
Very sensitive.
Avoid random jumper/rework.
79. eMMC Schematic
Typical concepts:
VCC
VCCQ
CLK
CMD
DATA
80. Storage Formula
POWER → RESET → CLOCK → DATA → RESPONSE
81. Audio Schematic
Speaker path:
SoC/audio bus
↓
Amp
↓
Speaker.
82. Speaker Amp Diagnosis
VIN → EN → AUDIO BUS → OUTPUT
83. Speaker Output Warning
Class-D/BTL output may not be ground referenced.
Do not connect grounded scope probe blindly to speaker output.
84. Mic Schematic
Digital mic:
Power
↓
Clock
↓
Data
↓
SoC/codec.
85. Charging Schematic
Master formula:
VBUS → PROTECTION → CHARGER IC → BATTERY
86. Charger IC Inputs
May include:
VBUS/input.
Battery.
System rail.
Control bus.
Temp/battery data.
87. Charging Fault
Check source-to-load sequence.
88. RF Schematic
Cellular RF has digital + RF sides.
89. RF Power Tracing
Power rail to:
PA.
LNA.
Transceiver.
Switch/tuner.
90. RF Signal Path
Receive:
Antenna → filter/LNA → transceiver.
Transmit:
Transceiver → PA → filter/switch → antenna.
91. RF Schematics Difficult Kyun?
Because:
Many bands.
Many filters.
Complex switches.
Frequency-specific paths.
92. RF Multimeter Limits
Multimeter RF carrier signal measure nahi karta.
Use it for:
Power.
Resistance.
DC control.
93. Wi-Fi Schematic
POWER → ENABLE/RESET → DIGITAL BUS → RF → ANTENNA
94. Wi-Fi Greyed
Focus power/digital side.
95. Wi-Fi Weak
Focus RF/antenna.
96. Baseband Schematic
Master:
POWER → CLOCK → RESET → MODEM → RF
97. SIM Schematic
SIM POWER → CLOCK → RESET → DATA
98. No SIM
Trace SIM connector to modem interface.
99. BoardView Net Search
Search exact net.
Then identify:
Source
Every capacitor
Every load
Every branch
100. Component Search
Search component reference.
Example:
C1234
BoardView shows location.
Schematic shows function.
101. Cross-Probing
Good schematic/BoardView software may allow:
Click schematic component
→ board location.
Or reverse.
102. Net Highlight
Highlight same net.
Very useful short tracing technique.
103. Net Color Coding
If software allows:
Color different rails:
Main rail.
1.8V.
3.0V.
Ground.
Useful learning method.
104. Draw Your Own Block Diagram
Before repair:
Make small flow.
Example:
Battery → PMIC → 1V8 → UFS
Then measurements fill karo.
105. Voltage Table
Create:
| Point | Expected State | Measured |
|---|---|---|
| PMIC VIN | Battery connected | ___ |
| EN | Power key/start | ___ |
| OUT | Startup | ___ |
This prevents confusion.
106. State Matters
Same test point phone OFF par 0V ho sakta hai.
Function ON par voltage appear.
107. Always Write Test State
Examples:
Battery connected
Phone OFF
Power key pressed
Booting
Camera open
Charging connected
108. Example Wrong Diagnosis
Camera rail 0V with camera app closed.
Technician replaces regulator.
Wrong.
109. Correct Diagnosis
Open camera / trigger camera initialization.
Then check rail.
110. Dynamic Signal
Some rails only milliseconds appear.
Scope may be needed.
111. Multimeter May Miss Pulses
Brief startup rail might average to near-zero.
Oscilloscope can show pulse.
112. Scope Use
Useful for:
Enable pulse
Reset transitions
Clock presence
Rail collapse timing
113. Scope Ground Safety
Use proper board ground.
Never attach ground where output is floating/differential, especially audio BTL.
114. Resistance Map
Known-good board ke common rails ki resistance record karo.
Over time own database ban jata hai.
115. Diode Map
Important connectors:
Display.
USB.
Camera.
Battery.
Touch.
Record known-good diode values.
116. Known-Good Comparison Rules
Same:
Model
Board revision where possible
Meter
Probe polarity
Power state
Use karo.
117. Different Model Comparison Risk
Same component purpose but different circuit values.
Do not use blindly.
118. Open Circuit Diagnosis
Signal source side good.
Destination side missing.
Possible:
Open resistor
Open bead
Broken trace
Connector issue
119. Short Circuit Diagnosis
Rail abnormally low.
Use net map.
Branch isolate.
120. Leakage Diagnosis
Resistance lower than known-good but not hard short.
Can affect:
Battery drain.
Bus voltage.
Power stability.
121. Intermittent Fault
May require:
Microscope.
Gentle connector pressure test.
Thermal/environmental observation.
Do not flex board aggressively.
122. Connector Before BGA
If signal leaves connector and destination missing:
Inspect connector/path first.
Don't jump directly to SoC.
123. Filter Components
Signal lines often pass through filters/ESD arrays.
One damaged filter:
Signal open.
124. ESD Short
Can pull signal to ground.
Common near:
USB.
SIM.
Display/touch.
External connectors.
125. ESD Open
Can break signal continuity.
126. Pull-Up Rail Missing
I2C bus may appear stuck/inactive even though devices good.
127. Shared Rail Diagnosis
Multiple functions dead together:
Find common supply.
Example:
Touch + sensors + camera control all affected.
Possible shared 1.8V rail.
128. Shared Reset/Clock
Multiple subsystems may share clock/control resource.
129. Common Cause Thinking
If three unrelated-looking faults start together:
Look for common:
Rail
Bus
Connector
PMIC output
130. Example Case 1 — No Touch
Known-good screen same.
Touch power present.
SDA stuck low.
Display disconnected:
SDA returns normal.
Diagnosis:
Touch/display module loading bus.
131. Case 2 — No Camera
Rear camera rail input good.
Enable present.
Regulator output absent.
Output resistance normal.
Direction:
Camera regulator.
132. Case 3 — No Display
Phone boots.
Display logic rail good.
Bias positive rail good.
Negative bias missing.
Direction:
Display bias circuit.
133. Case 4 — No Charge
VBUS at connector good.
After protection IC output = 0V.
Input normal.
Direction:
Protection/control/output path.
134. Case 5 — No SIM
SIM VCC present.
Clock present.
Reset present.
Data line diode reading abnormal vs known-good.
ESD array found shorted.
Root:
SIM protection component.
135. Case 6 — No Wi-Fi
Wi-Fi power present.
Reset remains low.
Direction:
Reset/control path.
136. Case 7 — Weak Wi-Fi
Digital side perfect.
Antenna contact missing.
Root:
RF physical path.
137. Case 8 — Storage No Boot
UFS core rail good.
I/O rail missing.
Direction:
UFS I/O power source.
Not UFS IC first.
138. Case 9 — Multiple Sensors Dead
Shared 1.8V rail absent.
Root direction:
Common sensor supply.
139. Case 10 — Phone Restart
PMIC rail output falls.
Enable stays asserted for short period.
Rail resistance abnormal.
Direction:
Downstream load/rail.
140. Schematic Diagnostic Worksheet
Phone Model: __________
Fault Symptom: __________
Affected Block: __________
Schematic Page/Block: __________
Source: __________
Net Name: __________
Destination: __________
Intermediate Components: __________
Expected State: __________
Last Good Point: __________
First Missing Point: __________
Root Cause Area: __________
141. Power Rail Worksheet
Rail Name: __________
Source IC: __________
VIN: __________
EN: __________
Output: __________
PGOOD: __________
Resistance to Ground: __________
Known-Good: __________
Loads: __________
142. Signal Worksheet
Signal Name: __________
Type: Reset / Enable / Clock / Data
Source: __________
Destination: __________
Series Components: __________
Idle State: __________
Active State: __________
Measured: __________
143. Bus Worksheet
Bus: I2C / SPI / UART / Other
Master: __________
Devices: __________
Power: __________
SDA/Data: __________
SCL/Clock: __________
Pull-Ups: __________
Stuck Low: __________
Isolation Result: __________
144. Connector Worksheet
Connector: __________
Pin Number: __________
Net: __________
Voltage: __________
Diode Reading: __________
Known-Good: __________
Physical Condition: __________
145. Diagnostic Decision Tree
Symptom identified?
YES ↓
Correct block identified?
YES ↓
Schematic page found?
YES ↓
Source present?
NO → upstream.
YES ↓
Signal/rail reaches destination?
NO → path/component.
YES ↓
Destination responds?
NO → load/control.
146. Power Regulator Decision Tree
VIN?
↓
EN?
↓
OUT?
↓
PGOOD?
This 4-step check solves many power faults.
147. Digital IC Decision Tree
POWER → CLOCK → RESET → BUS → RESPONSE
148. Display Decision Tree
BOOT → POWER → RESET → MIPI → PANEL
149. Touch Decision Tree
POWER → RESET → BUS → INTERRUPT
150. Camera Decision Tree
POWER → RESET → I2C → MCLK → MIPI
151. Storage Decision Tree
POWER → RESET → CLOCK → DATA → RESPONSE
152. Wi-Fi Decision Tree
POWER → RESET → BUS → RF → ANTENNA
153. Cellular Decision Tree
SIM → MODEM → TRANSCEIVER → FRONT-END → ANTENNA
154. Charging Decision Tree
PORT → VBUS/CC → PROTECTION → CHARGER IC → BATTERY
155. Common Beginner Mistake 1
BoardView ko sirf component location ke liye use karna.
156. Common Beginner Mistake 2
Net name ignore karna.
157. Common Beginner Mistake 3
Voltage missing dekh kar IC replace karna without EN/VIN.
158. Common Beginner Mistake 4
Reset/clock ignore karna.
159. Common Beginner Mistake 5
All zero-volt rails ko fault samajhna without power state.
160. Common Beginner Mistake 6
High-speed MIPI/UFS/RF lines ko normal jumper samajhna.
161. Common Beginner Mistake 7
Connector fault se direct SoC fault par jana.
162. Common Beginner Mistake 8
Known-good comparison na karna.
163. Common Beginner Mistake 9
Last Good → First Missing note na karna.
164. Common Beginner Mistake 10
Schematic ke bina random measurement.
165. Schematic Golden Rules
1. Schematic electrical map hai; BoardView physical map hai.
2. Symptom se correct circuit block identify karo.
3. Har measurement se pehle net name pata karo.
4. Power regulator ko VIN → EN → OUT → PGOOD se diagnose karo.
5. Digital IC ko Power → Clock → Reset → Bus se diagnose karo.
6. Last Good → First Missing root-cause narrowing ka best method hai.
7. Measurement ke saath phone state zaroor note karo.
8. High-speed lines par random jumper mat do.
9. Known-good board comparison extremely valuable hai.
10. Major IC ko tab tak suspect mat karo jab tak uske inputs/outputs/control prove na ho jayein.
166. Part 19 Quick Revision
Schematic
Electrical connections ka diagram.
BoardView
Physical motherboard layout.
Net
Electrically connected points ka common name.
VIN
Regulator input supply.
EN
Enable control.
OUT
Regulator output.
PGOOD
Power-good status.
Reset
IC initialization control.
Clock
Timing/reference signal.
Last Good
Last confirmed working point.
First Missing
Sequence ka first failed point.
167. Part 19 ka Sabse Important Lesson
Advanced mobile repair ka matlab ye nahi ke technician 500 IC names yaad kare.
Professional skill ye hai ke kisi bhi unknown motherboard par:
SYMPTOM SE BLOCK IDENTIFY KAR SAKE
phir:
BLOCK SE SCHEMATIC PAGE
phir:
SCHEMATIC SE NET
phir:
NET SE BOARDVIEW LOCATION
phir:
LAST GOOD → FIRST MISSING
find kar sake.
Agar charging fault hai:
Port se battery tak trace karo.
Agar camera fault hai:
Power se MIPI tak trace karo.
Agar storage fault hai:
Power → Reset → Clock → Data.
Agar no-power hai:
Battery → PMIC → Standby → Startup.
Aur sabse powerful rule:
FAULTY COMPONENT KO GUESS MAT KARO — BROKEN SEQUENCE KO DHOONDO.
Yahi schematic-based professional board repair ka foundation hai.
Mobile Repair Course — Part 19 Complete
Next — Mobile Part 20: Smartphone Advanced Multimeter Testing + Diode Mode + Voltage + Resistance Mastery
Part 20 mein hum detail mein cover karenge:
Continuity mode ka correct use
Resistance-to-ground
Diode mode
Known-good diode maps
Voltage testing
Ground selection
Probe polarity
Rail low-resistance interpretation
Connector diode testing
Open vs short
Leakage
MOSFET basic checks
Fuse/bead/coil testing
Power-state measurements
False readings se bachna
Practical diagnostic tables
Master formula:
0 Comments