Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDE
V1.0
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
TABLE OF CONTENTS
1. Snapshots of Antennas ………………………..………………….……….……………... 3
2. Snapshots/plots of Main Board .….…………….………………….……….……………. 5
3. Touch Troubleshooting……………...…….……………………………………..……….. 9
4. Display Troubleshooting…………….…….………………………..…………....…….…. 17
5. Audio Troubleshooting……………………………………………..………..…………….. 24
6. No Power up Troubleshooting…………………………………..…………..……………. 40
7. Battery & Charger Troubleshooting………………………………………….…………... 57
8. Sensors and SIM…..………………………………………….…………….……………… 68
9. Processor and Memory……………………………………….…………….……………… 80
10. Camera Troubleshooting………………………………………………….……………….. 85
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
SNAPSHOTS OF
ANTENNAS
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Antenna Locations
This product has an external metal antenna band.
All antennas are made using the metal band.
There is an extra stamped metal piece on the rear
housing for extra diversity bandwidth and isolation
to GPS.
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
SNAPSHOTS OF MAIN
BOARD
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
PCB
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Main Board – Top Placement
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Main Board – Bottom Placement
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
TOUCH
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Display ZIF
Touch ZIF
Main Board – Location of LCD & Touch ZIF Connector
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Touch System – Block Diagram
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
3.2V
1.8V
Touch Connector
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Touch IC Schematic
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
1. No Touch response when display touched
• Swap display panels with known good panel. If touch works,
problem with display flex or IC (Go to 2). If still not working,
problem with main board (Go to 3).
2. Display module issue
• Check Touch flex for any damage
• Ensure DC power is at ZIF pin 9 for 3.2VDC and pins 11&12 for
1.8VDC
• Verify Reset signal is high on Touch ZIF pin 4, IRQ is high on ZIF
pin 7
• I2C Data and I2C Clock at 1.8VDC
• When touching panel and moving finger, INT should toggle low,
I2C data and clk will toggle.
Touch Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
3. Main Board Issue
• Check touch connector for proper insertion of flex
• Ensure DC power is at ZIF pin 9 for 3.2VDC and pins 11&12 for
1.8VDC
• Verify Reset signal is high on Touch ZIF pin 4, IRQ is high on ZIF
pin 7
• I2C Data and I2C Clock at 1.8VDC
• When touching panel and moving finger, INT should toggle low, I2C
data and clk will toggle
Touch Troubleshooting (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
4. TRX-GND test failures
Transmitter/Receiver to short to
ground check
• Verify kapton tape is correctly
placed
• Kapton is used to isolate EMI
coating (black layer) to any
metal including copper tape
and front housing
EMI
Coating
Kapton
tape
Touch Troubleshooting (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
DISPLAY
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Display size: 5.43inch
Display Type: TFT, pOLED, Plastic Lens, Diamond Pixel Arrangement
Pixel Number: 1440xRGBx2560
Pixel configuration: RGB 16.77 M Colors (24 bits per Pixel)
Pixel Pitch: 47um
PPI: 540
Active Area: 67.68mm(H) x 120.32mm(V)
Response Time: <1ms
Max Brightness: 350
Contrast Ratio: min. 10000:1
Uniformity: 400P typ 1.05 max 1.47
Display Driver IC: S6E3HF2 (Samsung DDI, (1/2 Frame RAM))
Display AVDD/AVEE Driver: STOD32BTPQR
Display
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Display ZIF
Pin 1
Touch ZIF
Main Board – Location of Display & Touch ZIF Connector
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
-2.5
V
4.6V
3.1V
7.3V
1.8V
Display Main Schematic
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Pin17 of J5300;
DISP_VIO_FL
Pin10 of J5300;
DISP_VCI_FL
Pin54 of J5300;
DISP_RST_N
Display Power-up Sequence
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
TPS65633_VIN
; C5354
ELON1 (AVDD cntrl)
Pin50 of J5300
ELON2 (cntrl for ELVDD,
ELVSS, AVDD at DC/DC
U5350)
Pin49 of J5300
DISP_AVDD; Pin11 of J5300
DISP_ELVDD; Pin6-9 of J5300
DISP_ELVSS; Pin3-5 of J5300
External DC/DC Converter Power Up Sequence
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Check 55pin display ZIF connector
1. Properly inserted
2. Any damage to ZIF receptacle on main PCB or plug on disp flex
tail
3. Swap in known good main PCB or good disp module to see if
issue follows main PCB or display flex
• If the issue follows main PCB,
a. Check DISP_VIO_F voltage 1.8V typ (1.65-1.95VDC) at Pin17 of J5300
b. Check DISP_VCI_F voltage 3.1V typ (2.9-3.3VDC) Pin10 of J5300
c. Check voltages from DCDC converter U5350 at J5300 conn
(DISP_ELVDD 4.563-4.637VDC / Pins6-9, DISP_ELVSS -2.45V to -2.55VDC / Pins3-5,
DISP_AVDD 7.2-7.37VDC / Pin11)
d. Check DISP_RST_N, should be High (1.8V) / Pin54 at J5300
conn
• If the issue follows Display Module, replace the module.
Display Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
AUDIO
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
3.5mm Headset Jack
Loudspeaker Port
Front View
Earpiece Port
Top View
Mic 1 (Primary) & Mic 4
(Quaternary) Port
Mic 2 (Secondary) Port
Mic 3 (Tertiary)
Microphone Port
Back View
Mic 5 (ANC) Port
Deco removed to
expose actual port
locations
Audio Devices
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Tertiary Mic
(Grommet not shown)
Loudspeaker Module
(Pre-Sealed) 8-Ohms
Earpiece speaker
(32 ohms)
Secondary Mic
(Audio Flex)
Rear Housing “Endo” Assembly
Earpiece contact
pads (Audio Flex)
Loudspeaker PCB
Spring Contacts
Headset Jack Pads
(Top Flex)
Loudspeaker Module
Contact Pads
Headset Jack
(Rear Housing)
Audio Devices (Rear/Endo Assy View)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Primary mic
(grommet not shown)
Display / “TOP” Side Rear Hsg / “BOTTOM” Side
Mic 4
(grommet not shown)
Mic 5
(grommet not shown)
Mic 3 (Tertiary)
(grommet not shown)
Audio Devices (PCB View)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Launching the CQA app will help resolve and root-cause the vast majority
of problems.
• Go to the phone/dialer and enter *#*#2486#*#*
• The CQA main menu will pop-up – select “Start CQA Test in Menu Mode”
• Select the appropriate debug area – for Audio, primarily you will use
AUDIO and HEADSET
• The AUDIO CQA area has test capability for microphones, earpiece, and
loudspeaker
• The HEADSET CQA area should be used to debug any detection, or lack
of audio on the headset jack path
*
CQA Application
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• The CQA apk can be used to verify a broken audio path. Under the “Audio” menu, select
“Mic Loopback”.
– The “PRIMARY MIC” setting allows a mic1 to earpiece loopback (recommended)
• Note* - The “DEFAULT MIC” setting also allows this, if a headset device is not plugged in.
– The “SECONDARY MIC” setting loops mic2 to the earpiece, and so on and so forth; *Note* there
are 5 microphones on this device.
– If a headset is inserted, the “DEFAULT MIC” setting will loopback the headset mic if one exists
rather than the handset primary mic.
– Selecting the other microphone paths while a headset is inserted will loopback the audio to the
headset speakers/output device.
• If no mic-to-earpiece loopback paths are not functional, the earpiece speaker path is likely
damaged. In the “AUDIO” menu of the CQA apk, select “Ear Speaker” and the “Buzz
Sweep” should begin playing. Toggle and select “Play Harvard speech pattern” to hear
human speech to be sure the transducer is operating correctly.
• The loudspeaker can be tested by selecting “Loudspeaker” via the CQA apk. A musical
composition should start playing and be easily heard.
• If audio is not present on the HEADSET path, select the “Headset” entry in the main menu
of the CQA app, then plug-in the headset device to view whether the lack of audio is a
detection-cycling issue or other anomaly.
“No Audio” Complaints
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Microphone schematics are presented based on proximity on the PCB and/or
location on a particular flex.
Microphones
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Microphone schematics are presented based on proximity on the PCB and/or
location on a particular flex.
Microphones (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Microphone schematics are presented based on proximity on the PCB and/or
location on a particular flex.
Microphones (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
MIC 2 CKT ABOVE IS LOCATED
ON THE AUDIO FLEX
(See Rear/Endo View)
Part of Mic 2 CKT located on Main
PCB (near J4600, Audio Flex B2B)
Microphone schematics are presented based on proximity on the PCB and/or
location on a particular flex.
Microphones (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
If a mic is not functioning…
• Check to make sure the microphone and mic ports are not blocked.
• Check to make sure the mic gasket and mic grommets are seated properly (Mic 1/3/4/5). Check to
make sure the J4600 B2B connector is seated properly (MIC 2 only).
• Check the microphone for diaphragm debris indicating a shattered diaphragm. Look under a
microscope to view inside the microphone port for damage or debris near port hole or surrounding the
microphone area where tiny, shiny particulate material may be visible when varying viewing angle.
• Check to make sure no capacitors on any of the applicable mic lines are shorted or damaged.
• Check the mic bias C4500 (Mic1), C4510 (Mic2), C4520 (Mic3), C4530 (Mic4), C4540 (Mic5). The mic
bias should be 1.8VDC when the microphone is enabled.
• If the failure is no microphone audio, check mic loopback through CQA at the board level with a
display connected. (Mic loopback may be easier to check with a headset plugged in, in which case
the rear hsg assy may be req’d.)
• If there is no audio during mic loopback, inject a 35mVrms, 1kHz sine wave onto the mic signal side of
C4501 (Mic1), C4511 (Mic2), C4521 (Mic3), C4531 (Mic4), C4541 (Mic5) and listen for the tone
during loopback. If you can hear the tone now, you know either the mic is bad, or there’s a process
defect with the mic-to-PCB connection.
• X-ray the mic to check for process defects.
• If swapping the microphone fixes the issue, the bad microphone should be sent to the supplier for FA.
Microphones Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Check that the impedance of the earpiece speaker is near 32 ohms, and that the spring contacts are
not bent.
• Check that the earpiece flex is seated properly in the rear housing with no debris on it. You should
also be able to see slight imprints in the gold pads where the speaker spring contacts were touching
the flex; these imprints should be centered - if they are on the edge of the pad, there may be an
alignment issue.
• Check that the J4600 B2B flex connector on the PCB is seated properly with no damage to any pins
on the PCB-side or Flex-side.
• Check C4691, C4692, VR4690 and VR4691 for any placement issues.
Located near J4600, Main PCB
On Audio Flex (PADS ONLY)
Earpiece Speaker (Handset Mode DOWNLINK)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Verify the impedance of the loudspeaker module is ~8 ohms.
• Lack of mechanical contact should also be checked between the PCB spring contacts and the
loudspeaker module (check for bent/broken/missing pins on PCB spring contacts).
• Make sure L4680 and L4681 are not skewed or damaged.
• Check C4680, C4681, C4682, C4683, C4684, VR4680, and VR4681 for any placement issues.
Loudspeaker
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
This section of headset circuit on MAIN PCB, at/near J800
3.5mm Headset Path
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
This section of headset circuit on TOP FLEX
3.5mm Headset Path (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Check the pins on the headset jack for any bent pins or missing pins (In
rear housing)
• On the TOP FLEX:
– ESD Diodes VR4900, VR4901, VR4902, VR4903, VR4904 must be
open circuit. Measure these with a DMM to ground. If any short circuit
is found, replace the ESD diode.
– Shunt caps C4900, C4901, C4902, C4903, and C4904 must not be
shorted across.
– Check that there are slight indentations on the headset pads,
preferably centered. If any indentations fall close to the gold pad edge,
there may be an alignment issue.
• On the MAIN PCB:
– U4800 must have voltage on the VDD line, and can be probed on
C4813 or C4819. This should measure 1.8V nominally.
– Check that the J800 B2B connector is seated properly and there is no
damage to either the connector (TOP FLEX-side) or receptacle (MAIN
PCB-side).
Debug Procedure: Headset
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
NO POWER UP
DEBUGGING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Purpose of this document is to cover the debugging steps used to
root cause PCB that do not power up properly so that they may
be used again to initiate corrective actions.
No Power Up Debugging
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
MSM AP/BP MSM8994 U1000
Power Management IC PMIC
PM8994
PMI8994
U2000
U2500
SMB Charging IC SMB1351 U540
Kung Kow Factory Kill IC User Reset IC U650
B_PLUS VSYS System Battery Voltage
VBUS USB Voltage Charger Voltage
Terms on the same row are synonyms and will be used interchangeably
in this section.
Glossary/Synonyms
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Generally the first step to troubleshooting a no turn on PCB is to look at its boot
current. A blank board (no software flashed yet) will normally draw about 80mA at
a constant level.
• Also it is helpful to find out what level of functionality is available. These distinct
modes were observed:
1. Blank Flash mode
• Normally will enter this mode for a newly built PCB.
• Can be forced by shorting debug connector as shown in later slides.
2. Fastboot mode
• Normally will enter this mode after flashing bootloader into newly built
PCB.
• Can be forced using volume down key during bootup
3. Full Power up
• Will enumerate to PC as Motorola Network device and ready for board
test.
• Failed boards will be able to achieve one of these modes but fail to get to the next.
This bit of information is useful for debugging.
• Start with the phone off, then plug in the USB cable. If the phone does not turn on
when the USB cable is inserted, there is most likely an issue with the connector.
• If the current is abnormally high for a blank board, the root cause is most likely a
short. Going through the power on sequence is helpful for finding shorts, it is
shown on the next page.
Debug Procedure
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Connect USB
Start
I < 100mA
I < 1mA
I > 1000mA
Check Input
Power Path
Check USB
Enumeration
and/or DDR
Failure
High Current
Failure
Check PMIC
Yes No
Yes
No
Yes
No
Check MSM
Measure Current
NTO Debug Flow Chart
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Check Input
Power Path
VBUS ≈ 5V
Yes No
Measure Input Voltages
B_PLUS ≈ 3.5V
Inspect/Replace
USB Connector
Inspect/Replace
PMI (U2500)
SMB (U540)
No
Check PMIC
(U2000)
Yes
Check Input Power Path
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
J510
Battery Connector
BATT_PLUS
J500
USB Connector
VBUS
U2500
PMI8994 Charger
B_PLUS
U2000
PMIC
PM8994
2.7V- 4.4V
2.7V- 4.4V
5V
To System
Simplified Input Power Tree
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Check PMIC
All
Regulators
Turn On?
Yes
Check Power
Up Sequence
Check USB
Enumeration
PS_HOLD =
1.8V
Yes
Replace MSM
(U1000)
No
No
Use XRay to find
Shorts near
PM8994 (U2000)
PMI8994 (U2500)
Use Ohmmeter to
look for short circuits
on all power rails
Use Power Sequence Slides as a reference
Replace MSM
(U1000)
Replace PMIC
Check PMIC
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Check Power
Up Sequence
Remote PMIC
Can
Check Primary
Power On
Sequence
Check
Secondary
Power On
Sequence
Check Power Up Sequence
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Power-On Sequence
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Check MSM
Check PoP
Alignment
X Ray and Look
for Solder
Shorts
Replace MSM
Replace RAM
Check MSM
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
High Current
Failure
Use Thermal
Camera or feel
with hand to find
Hot Shield
Use X Ray to
find Shorts on
B_PLUS, BBYP,
or BATT_CONN
Inspect
components
under hot shield
and replace
components
High Current Failure
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• First check for solder
ball shorts on major
ICs or discrete
resistors or capacitors
that are skewed and
shorting to each other
• Follow the list at right
• Replace parts in order
• Recheck test after
removing each shield
and after removing
each component
Circuit Typ [uA] Ref
PM8994
18
1
PMI8994
52
2
SMB
7
3
LPDDR Buck
12
4
5V Boost
5
5
Loud Speaker
1
6
OLED Driver
5
7
LED Cam Flash
1
8
Tuner
1
9
WiFi Buck-Boost
5
10
RF Boost-Bypass
26
11
Kung Kow
3
12
Audio Buck
1
13
TOTAL
137
High Kill or Off Current
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• First check for solder
ball shorts on major
ICs or discrete
resistors or capacitors
that are skewed and
shorting to each other
• Follow the list at right
• Replace parts in order
• Recheck test after
removing each shield
and after removing
each component
Circuit Typ [uA] Ref
PM8994
18
1
PMI8994
52
2
SMB
7
3
LPDDR Buck
12
4
5V Boost
5
5
Loud Speaker
1
6
OLED Driver
5
7
LED Cam Flash
1
8
Tuner
1
9
WiFi Buck-Boost
5
10
RF Boost-Bypass
26
11
Kung Kow
3
12
Audio Buck
1
13
TOTAL
137
High Kill or Off Current (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Check USB
Enumeration
Blankflash
Mode
Yes
Device Enumerates
in...
Pull Android
Logs
Reflash
Bootloader
Fastboot
Mode
Yes
No
Android
Device
Enumerates
?
No
Check PMIC
(U2000)
Check JTAG
Connector for Shorts
Reflash Android
Check/Replace
eMMC
Check/Replace
eMMC
Capture UART
Logs during
bootup
Check USB
Connector
(J500)
No
Yes
Yes
Yes
Yes
Check USB Enumeration
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Sometimes if a board has software already flashed, or there was some problem
with software, a board can be forced into this mode by shorting two highlighted
pins on the debug connector.
• Then when board is in this mode, blank flashing can be attempted to reflash the
device and/or find more information on the failure.
Force Blankflash Mode
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• If in blankflash Mode, the device will enumerate like this.
Blankflash Mode
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
BATTERY AND CHARGER
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
No turn on with battery only:
• If device does not power up with battery only, battery is most likely dead, or there could be an
issue with the battery safety control FETs in the PMIC or the safety IC. Also likely is an
intermittent or broken trace or via in the battery PCB or the flex, or with the board-to-board
connection of the battery to the board.
• If dead battery cannot be recovered with a charger, measure the battery voltage. If it is normal,
monitor on a scope for voltage dipping below 3V while attempting to power it up with battery. This
can happen due to high impedance FET or IC in the battery or excess current drain.
• If device powers up with factory cable, replace the battery, and if the issue is resolved, send the
battery to development team.
Thermistor reading out of spec:
• Thermistor usually reads between 20 to 30C, depending on ambient temperature and if device
has been in use or charging. This can be read with adb commands or under “Battery Info” in
CQA mode.
• Notify the mechanical engineer in charge of the battery and thermistor to inspect the rear housing
of device for any signs of thermistor damage.
• X-ray the NFC connector to ensure that it is seated properly and shorts/debris are/is not present
• Carefully measure the thermistor resistance with a meter. Take care not to apply unnecessary
pressure on the device so that condition can be preserved for analysis. If the measurement is not
between 8-12Kohms, hand the device as is to the mechanical engineer for further analysis and
corrective action.
Battery and Thermistor
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
BATT+ BATT-
BATTERY
CONNECTOR
Battery Connector – Location and Test Points
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
BATTERY
THERMISTOR
DISPLAY CONNECTOR
Thermistor – Location and Test Point
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
GND
ID
D+
D-
VBUS
USB Connector - Pinout
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Ensure the device is not in factory mode. Ensure battery temperature reading is as expected
(between 20-30C). If the battery temperature reads cold (-20C), the NFC flex is disconnected
and the thermistor is not present. If the battery temperature reads hot (>60C), the thermistor
lines are shorted.
Inspect the battery for any damage or abuse. Ensure by measurement or from CQA battery info
menu that the battery pack voltage and cell plus sense voltage levels are according to the
expected charge current level.
There could be an issue with the USB connector or its connections to the board and the charge
IC. Measure VBUS (5V, or 9V for turbocharger), D+, D-, and ID (2V). Measure this at the
charger cable if possible or preferred at first, then on the PCB and, as needed, next to the
charge IC. See table below for expected turbocharger D+/D- levels.
If the ID voltage is low (mV), with 5V on VBUS with no charger connected, the device is in host
mode. When the device is in this mode, it will not charge. Measure the resistance of ID to GND.
If it is less than 100Kohms, there is a short to GND on the line. Replace VR502.
USB Charging Issue
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
The lightning bolt in the battery meter icon represents a valid VBUS voltage, a detect. “Turbo
Charger connected” is displayed if a turbocharger is connected. It is not displayed otherwise, or
if a turbocharger is connected partially into the device, and inserted all the way in more than a
second or two later.
Ensure the phone current drain does not exceed the charger supply current capacity in the use
case where battery is not able to charge.
If the device power cycles when the battery is low and USB charger is connected, monitor the
current drain in or out of the battery as well as the battery voltage with a scope across the sense
resistor.
There is also the rare possibility of charge IC itself damaged or have damaged or intermittent
BGAs where a reflow followed by replacement of the IC might be needed as a last attempt to
recover charge operation. This should be done after exhausting all other possible root-causes
and discussing with development team.
USB Charging Issue (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
A device’s failure to wirelessly charge generally goes hand in hand with failure to charge via
USB.
Ensure the device is not in factory mode. Ensure battery temperature reading is as expected
(between 20-30C). If the battery temperature reads cold (-20C), the NFC flex is disconnected. If
the battery temperature reads hot (>60C), the thermistor lines are shorted.
If the NFC flex is disconnected, no USB nor wireless charging will occur. If the NFC flex is
connected, but wireless charging is not occurring, inspect the flex tail. A tear on the inner side of
the flex tail where it makes a 90 degree turn, would sever the wireless charging coil trace and
disconnects the coil from the board. Replace the flex.
Wireless Charging Issue
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Battery Components
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
USB Components
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
If battery level reads 0%:
• Unplug factory cable, wait at least 3 seconds, then plug the cable back in.
• If this does not work, try plugging in a charger. If battery level is below 3V,
SOC LED will blink. The blinking will stop when battery is above 3V, at which
time soon after, phone will power into Charge Only Mode, and vibrate before
displaying a battery logo.
• If charge level is 1% or higher, leave on charger until 100%.
If battery level is too low, but 1% or higher:
• Plug in charge and leave until 100% full.
Debug Procedure: Battery Level
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
SENSORS AND SIM
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Accelerometer
Gesture LED 2
Magnetometer
Prox/ALS
Hall Effect Sensor
Sensor Hub
Gesture Sensor
Gesture LED 3
Flex Connector
Top Flex
Connector
Gesture LED 1
Gesture LED 3
Top Flex
Gesture LED Flex
Sensors
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Firmware download failing/no communication with hub
– Check U6000 supply at C6000 - Should be 1.8V
– Check U6000 orientation
– If everything else looks good, try replacing U6000
• If sensor hub is continuously rebooting
– Check accelerometer (covered later)
Sensor Hub Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Proximity Sensor is part U6120.
• If reading is failing:
– Check black grommet in housing is not obscuring the top
of the part
– Verify voltage at C6122 is between 3.3 to 4.35 V
– Try replacing replacing the part
• If no reading at all:
– Verify part orientation
– Verify voltage at C6121 is 2.85V
– Verify voltage at R6000 and R6001 is 1.8V
• If voltage is missing try replacing U6120, U6000, or
U2000 in that order
Proximity Sensor Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• ALS Sensor is the same part as Proximity Sensor (U6120).
• If reading is failing:
– Check black grommet in housing is not obscuring the top
of the part
– Inspect opening in lens. It should be translucent when
holding front housing up to a light. Try swapping front
housings.
– Try replacing U6120
– Test on different fixture, bulbs in fixture may be too old
and dim.
• If no reading at all (error code):
– Check part orientation of U6120
– Verify voltage at C6121 is 2.85V
– Verify voltage at R6000 and R6001 is 1.8V
• If voltage is missing try replacing U6120, U6000, or
U2000 in that order
Ambient Light Sensor (ALS) Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Accelerometer is part U6150.
• If no reading:
– Verify U6150 orientation
– Verify voltage at C6151 is 1.8V
– Replace U6150 or possibly U6000 or U2000
• If reading is failing:
– Replace U6150, likely damaged accelerometer part
Accelerometer Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Gyroscope is part U6150 (same part as accelerometer).
• If no reading:
– Verify U6150 orientation
– Verify voltage at C6151 is 1.8V
– Replace U6150 or possibly U6000 or U2000
• If reading is failing:
– Replace U6150, likely damaged accelerometer part
Gyroscope Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Magnetometer Part is U6140.
• If no reading:
– Verify U6140 orientation
– Verify voltage at C6141 is 1.8V
– Replace U6140, if still not fixed try replacing U6150, then possibly
U6000
• If reading is failing:
– Replace U6140, likely damaged magnetometer part.
– Test at board level if radio level testing is failing to determine if
magnetic component in the housing is somehow affecting readings.
Magnetometer Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Hall Effect Part is U6170.
• If no toggling:
– Verify U6170 orientation
– Verify voltage at C6175 is 1.8V
– Make sure U6000 is placed and oriented correctly
– Replace U6170, likely damaged hall effect part.
– Can also replace U6000 if failure persists
Hall Effect Sensor Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• IR Gesture Receiver is part D6500, LED2 is D6502, LED1 & 3 are on
flexes
• If no data received:
– Verify D6500 & U6500 orientation
– Verify voltage at R6590 is 5V
– Verify voltage at C6504 is 2.85 V
– Verify voltage at C6506 is 1.6 V
– Replace U6500, D6500, then U6000 or U2000 if not fixed
• One or more LEDs have low readings:
– Check black grommet on housing is not obscuring the sensor or the
LEDs
– Verify LED orientation (refer to sensor location drawing)
– Verify Q6500, Q6501, Q6502, & Q6503 orientation
– Verify voltage on LED anode is 5V
– If LED 2, replace LED module, if LED 1 or 3, replace entire flex (do
not rework on flex)
IR Gesture Sensor Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• Check that the vibrator motor is seated properly (correct alignment and pads
are not lifted) and the counter weight is not bent and can rotate freely.
• Measure the resistance across the vibrator, it should be 14ohms +/- 4ohms.
• Check that E5101 and E5102 are not skewed or damaged.
• Check C5105, C5106, C5107 for damage or any process related defects.
• Check the motor itself by applying 2.4V across the C5105, it should spin freely
and continuously. If the motor spins when 2.4V is applied externally, but not
when driven from CQA app, x-ray U5101 for defects and replace as needed.
NOTE: If motor does not spin, or if motor stutters, but starts working normally after
turning it manually, it has a “dead-spot”. Consider it a failure and replace
the motor.
Vibrator Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
• If SIM card errors occur:
– Check orientation on ESD parts
• SIM1: D5500, D5501, D5502
• SIM2: D5510, D5511, D5512
– Inspect card reader for bent or broken contacts.
– Use multimeter to check connection between gold SIM contacts
and pins on back of connector.
– Verify a 0V voltage on Pin “tray_det” (C5803) when card is
removed.
– Verify 1.8 Volts on Pin “tray_det” (C5803) when card is inserted.
– Check for unexpected shorts to ground on M5801 and M5802
pins 1, 2, 3, 6 (factory cable, USB, and battery must be removed).
– SIM1 - Verify R5502, R5503, and R5505 are placed
– SIM2 - Verify R5510, R5512, and R5513 are placed
UIM (uSIM) Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
PROCESSOR AND MEMORY
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
If the phone is stuck at the logo screen or does not
power up completely or keeps enumerating in blank
flash mode then EMMC component could be
suspected:
1. Check the 1.8V, 2.95V supplies
2.95V accessible at C1610
1.8V accessible at C1620
2. Probe the EMMC_CLK line to measure 400Khz
first and then maximum of 177MHz.
EMMC_CLK accessible at C1011 or R1010
3. Wire our command and data lines along with
clock and put it on the scope. If the command
does not output the command information then
the EMMC controller inside the chip could be
corrupted.
CMD accessible at R1610
D0 accessible at test point
4. Note down lot code and date code.
5. Try user reset (hold power key for 10secs) and
restart the procedure.
6. If it still fails X-ray the board and reflow the part.
7. If it still continues to fail, the part might need to
go back to supplier.
EMMC (Internal NAND)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
1.8V
D0
2.95V CMD
CLK
EMMC Probe Locations (Bottom Side)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
1. Tray Det (accessible at R4208) should be low when a tray is not present and high when a tray is present. If R4208
is high and no tray is present, the Detect pin on J4200 is most likely unsoldered
2. Measure supplies VDD_SDC (at C4413), VDD_P2 (at R4412) Both supplies can toggle between 3 and 1.8V
3. R4404-R4409 should all be placed. These are series components on CLK, CMD and DATA. Be sure to probe both
sides of the part.
4. Depending on the type of card placed in the slot you can measure sdc2_clk as 12.5MHz, 25MHz, 50MHz, 100MHz,
200MHz during a read or write operation.
CLK accessible at R4408
5. Probe SDC2_DATA<3..0>, SDC2_CMD to ensure there is activity on the bus. Start with Data0. R4404-R4407 is
data and R4409 is CMD.
6. If any line is held low then measure the voltage across the ESD diodes placed on all data and detect line to ensure
you read 0.7V confirming its not shorted to ground.
Micro SDCard (Removable Memory)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Bottom side - J4200 is SIM + uSD/SIM connector
Tray Detect
Top Side
Data
CMD
CLK
VDD_SDC
Micro SDCard Probe Points
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
CAMERA
TROUBLESHOOTING
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Front Imager Schematic
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Rear Imager/Flash LED Schematic
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Camera Pinout – Rear (camera pointed at you)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Camera Pinout – Front (camera pointed at you)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Front imager
connector
on
Top Flex
LED flash
shared
cathode
contact
LED flash
Warm
anode
Front
imager
circuit
NC
If camera does not
turn on, change
camera module. If
camera still does not
power on, then it is
likely an issue on
main PCB.
Top Flex
Connector
Audio Flex
Connector
Audio
Flex
Flash
PCB
LED flash
Cool anode
Camera Troubleshooting
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Rear
imager
connector
Rear
Camera
circuit
Front flash
LED cathode
Front flash
LED anode
LED
Flash
circuit
If camera does
not turn on,
change camera
module. If
camera still
does not power
on, then it is
likely an issue
on main PCB.
Camera Troubleshooting (cont’d)
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
LED Flash Schematic
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
LED Flash circuit
LED Flash Layout
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Blemish failure due to FM. This FM is most likely beneath the lens.
Blemish Example #1
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Blemish failure due to FM. The blue box and red circle are part of the annotated
image. Annotated images end with _BLEMISH in the file name. These annotations are
drawn by the analysis software and not part of the real image. The blemish that is circled however is real and indicates FM or
a defect in the lens.
Blemish Example #2
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
Blemish failure due to noise. There are no particles or lens defects in this module, but
the noise is so bad that it is getting mistaken for blemishes. This is most likely a
problem with the sensor.
Blemish Example #3
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
This picture shows a really severe case of the focus chart not being centered within
the camera’s view. This case is most likely caused by operator error when placing
the phone into the test chamber.
Placement Error Example
Moto X Force/DROID Turbo 2
BASEBAND TROUBLESHOOTING GUIDES
MOTOROLA CONFIDENTIAL
The top side of this image is blurry. This will most likely be a problem with the lens
placement inside the module.
Focus Error Example
Loading...