Repair Hints:
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
Repair hints
Service Level 3 & 4
&
Latest R & D solutions
Communicator
9210/9210i
RAE-3/RAE-5
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
1 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
2 (55)
1. GENERAL
How to use this document
Put the schematics behind this manual.
Now you are able to follow these specifictions with graphical layouts and it is easier for you to find the components
and measuring points.
Component charactaristics
Some components contain important data.
Several steps described are only feasible if you are able to reflash/ realign the Communicator 9210/9210i and/ or
rewrite IMEI/ SIMlock in certain cases. Please pay attention to separate notes.
General handling
All screws must be screwed with a torque of 16Ncm. If a higher torque is used, the cover might be damaged.
If it is necessary to make a backup, be sure that the data are ok, otherwise it is possible that the corrupt files are
responsible for the same faults as before reinstalling the backup.
Broken balls, µBGA
All replaceable µBGA-components must be renewed after removing. Reflow with hot air fan is strictly forbidden!
Check soldering points, remove oxidated solderings (broken balls) carefully; by enclosing a few new solder joints before
placing new components.
µBGA must be soldered only with NMP approved µBGA-rework maschines (e.g. ZEVAC/ OK International).
Only use recommended Fluxtype and an appropriate amount of it.
PCB handling & cleaning
To avoid damages of PCB and/or components through electrostatic discharging, handle the module in
ESD-suitable cases only. Always wear ESD-bracelets, which must be connected to earth bonding point.
Do not make any loose wiring connections or do any other unqualified rework anywhere.
For cleaning use only appropriate materials, use tools e.g. that not scratch or rubber the surface.
Because of organic surface protection (OSP) cleaning must be done only with a lint-free cloth which may be moistened
with DI-water. IPA or other solvents such as ethanol should only be used to clean gold pads for spring contacts without
affecting the surrounding copper layers.
Check tuning values after repair
Characteristics of replacement parts may vary.
To prevent additional faults after repair (e.g. low standby time, losing network etc.) it is necessary to check phone
tuning values after repair, but never try to cover up a fault by justing the phone.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Customer Care Europe, Middle East & Africa
SCCE Training Group
Date 10.07.2003
Repairhints
Version 3.1
3 (55)
IMPORTANT:
This document is intended for use by authorized NOKIA service centers only.
The purpose of this document is to provide some further service information for Communicator 9210/9210i.
It contains a lot of collected tips and hints to find failures and repair solutions easily.
It also will give support to the inexperienced technicians.
Saving process time and improving the repair quality is the aim of using this document.
We have built it up based on fault symptoms (listed in " Contents " ) followed by detailed description for further analysis.
It is to be used additionally to the service manual and other service information like Service bulletins, for that reason it
does not contain any circuit descriptions or schematics.
All measurements are made using following equipment:
Nokia repair SW:
WinTesla 6.46.002
Service SW DLL version:
04.20.00
Flash SW:
4.13 (RAE-3) / 6.00 (RAE-5)
Memory Card Image for 9210:
All_memory_card_data.SIS for SW 4.13
Application SW for 9210i:
All Nokia 9210i Data XX.SIS (XX = Language package)
Nokia Jig:
MJS-14
Digital Multimeter:
Fluke 73
Oscilloscope:
Fluke PM 3380A/B
Spectrum Analyser:
Advantest R3162 with an analogue probe
RF-Generator / GSM Tester:
CMU 200
While every endeavour has been made to ensure the accuracy of this document, some errors may exist. If the reader
finds any errors, NOKIA should be notified in writing, using following procedure:
Please state:
Title of the document + issue number/date of publication.
page(s) and/or figure(s) of error.
Please send to:
Nokia GmbH
Services & Competence Center Europe
Meesmannstr.103
D-44807 Bochum / Germany
e-Mail: training.sace@nokia.com
Copyright © 2001-2003 Nokia. All rights reserved.
Copyright © Nokia. This material, including documentation and any related computer programs, is protected by
copyright controlled by Nokia. All rights are reserved. Copying, including reproducing, storing, adapting or translating,
any or all of this material requires the prior written consent of Nokia. This material also contains confidential
information which may not be disclosed to others without the prior written consent of Nokia.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
4 (55)
Contents
1.
2.
General ........................................................................................................................................................................................................2
Prechecks....................................................................................................................................................................................................5
2.1
Drop faults ........................................................................................................................................................................................6
2.2
Network cases .................................................................................................................................................................................7
2.3
Startup/shutdown cases ..............................................................................................................................................................8
2.4
Contact service cases.....................................................................................................................................................................9
2.5
SIM card cases............................................................................................................................................................................... 10
2.6
Data lost cases.............................................................................................................................................................................. 11
2.7
Charging functionality ............................................................................................................................................................... 12
2.8
SW cases ......................................................................................................................................................................................... 13
2.9
Audio functionality ..................................................................................................................................................................... 14
2.10 Keypad functionality .................................................................................................................................................................. 15
2.11 Displays functionality................................................................................................................................................................. 16
2.12 Clock functionality issues.......................................................................................................................................................... 17
2.13 SW update cases .......................................................................................................................................................................... 18
3.
Fault descriptions, measurements and service actions........................................................................................................... 21
3.1
Absorber pad................................................................................................................................................................................. 21
3.2
System connector........................................................................................................................................................................ 22
3.3
Coaxial cable ................................................................................................................................................................................. 24
3.4
Screw tightening ......................................................................................................................................................................... 25
3.5
Board to board connector ........................................................................................................................................................ 26
3.6
Memory failures ........................................................................................................................................................................... 27
3.7
Production data check............................................................................................................................................................... 29
3.8
Self test status check.................................................................................................................................................................. 31
3.9
A/D converter check.................................................................................................................................................................... 32
3.10 Device/memory card SW version match.............................................................................................................................. 33
3.11 Memory card with old data in 9210i device....................................................................................................................... 34
3.12 EEEMU corrupted.......................................................................................................................................................................... 36
3.13 DOC corrupted............................................................................................................................................................................... 38
3.14 Oscillator related measurements........................................................................................................................................... 40
3.15 RF powering related measurements .................................................................................................................................... 41
3.16 RF ASIC related measurements ............................................................................................................................................... 43
3.17 Keypad (CMT or PDA) case......................................................................................................................................................... 46
3.18 Audio related service actions .................................................................................................................................................. 47
3.19 Flex failure ..................................................................................................................................................................................... 48
3.20 Broken PDA display module..................................................................................................................................................... 50
3.21 Broken CMT display module..................................................................................................................................................... 51
3.22 Piezo or CCFT (tube/lamp) broken ......................................................................................................................................... 52
3.23 Broken mechanics....................................................................................................................................................................... 54
Change History.................................................................................................................................................................................................. 55
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
2. PRECHECKS
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
5 (55)
Table 1. Symptom code list for prechecks
Symptom
Precheck item
Page
Drop calls
No network
Poor network
Poor network quality
Network cases
7
Device shuts down / switches off
Device dead (CMT and/or PDA)
Device dead (CMT display backlight blinking)
PDA frozen (white display or jams into startup picture)
Startup/shutdown cases
8
“Contact service” message on CMT display
Contact service cases
9
“SIM card rejected” message
SIM card cases
10
Manufacturing data lost (IMEI, PSN, power management values, tuning values etc.)
Data lost cases
11
Not charging
Charging functionality
12
PDA SW error messages (Kern-Exec 3)
PDA SW error messages (Application closed)
PDA SW error messages (Messaging Watcher)
PDA SW error messages (EtelServer)
Applications may be different language
Missing applications or files from PDA
SW cases
13
Earpiece does not work
HF speaker does not work
Microphone does not work
Audio functionality
14
CMT keypad does not work
PDA keypad does not work
Lid keypad does not work
Keypad functionality
15
CMT/PDA display does not work
Stripes on CMT/PDA display
Lines missing from CMT/PDA display
Dark areas on CMT/PDA display
PDA backlight does not work
Displays functionality
16
CMT clock stops
Device time/date incorrect
Date/time asked every time after main battery removal (with SW 5.54 or newer)
Clock functionality issues
17
Flashing fail (Erasing fail)
Flashing fail (Phone NAK message)
Flashing fail (Failed to read data from phone)
Flashing fail (Set power on)
Flashing fail (PPM validity)
Flashing fail
SW update cases
18
Attention!!! At first interchange all moduls (PDA, CMT, UI) with working ones to find out, which module is faulty.
Table 2. Common drop faults (see page 6)
Device dead (CMT and/or PDA) Device shuts down / switches off
PDA backlight doesn't work (dark display) Dented / scored covers
“Contact Service” note on CMT display Hinge / Screen Frame broken
Broken mechanics / displays / components
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
6 (55)
2.1 Drop faults
Symptoms: Device dead (CMT and/or PDA)
PDA backlight doesn't work (dark display)
“Contact Service” note on CMT display
Device shuts down / switches off
Dented / scored covers
Hinge / Screen Frame broken
Broken mechanics / displays / components
Prechecks: Board to board connector (page 26)
Screw tightening (page 25)
Broken mechanics (page 54)
Service actions:
Faults depend on height of drop, drop angle and hitting surface. Sometimes there are no visible marks seen on the
surface but still the device is broken after a drop out off height. After prechecks check following items if needed:
-
Insert battery and check if " Contact Service " note appears on CMT display, if yes then
o See Self test status check, page 31
There are problems with CMT display
o See Broken CMT display module, page 51
Device dead / Device shuts down / switches off
o See Startup/shutdown cases, page 8
When lid is opened a dim picture can be seen on PDA display but the PDA backlight is off state all the time
o See Piezo or CCFT (tube/lamp) broken, page 52
No picture or messed-up picture on PDA display
o See Broken PDA display module, page 50
Note! Clear dropping failures (e.g. PDA display cracked, broken A-cover lens) are always not covered
by Nokia warranty.
See also:
Page 16, Displays functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
2.2 Network cases
Symptoms: Drop calls
No network
Poor network
Poor network quality
Prechecks: Screw tightening (page 25)
System connector (page 22)
Absorber pad (page 21)
Coaxial cable (page 24)
Service actions:
See section 3.16 RF ASIC related measurements on page 43.
See section 3.15 RF powering related measurements on page 41.
See section 3.14 Oscillator related measurements on page 40.
NOTE! No problem (or very very rare!) with HAGAR, COBBA, PA or RF tuning values!
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
7 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
8 (55)
2.3 Startup/shutdown cases
Symptoms: Device shuts down / switches off
Device dead (CMT and/or PDA)
Device dead (CMT display backlight blinking)
PDA frozen (white display or jams into startup picture)
Prechecks: Board to board connector (page 26)
Screw tightening (page 25)
Memory failures (CMT display backlight blinking) (page 27)
Production data check (page 29)
Service actions:
If the above-mentioned checks do not help, try to update to the latest software version (SW 6.00 or later). If the device
is dead due to corrupted production data, it may be corrected by flashing new SW, but it may require flashing the same
software twice. After the first flashing the phone corrects the production data and does not respond to flash prommer,
causing an error message. The second flashing will correct this. See section 2.13 SW update cases on page 18 for more
possible causes.
If the flashing fails, check the flash IDs. See section 3.6 Memory failures on page 27 for more information on flash IDs.
- If one of the IDs is 0000-0000 (in RAE-5 at third position this is ok), check that Vcore = 1.8 VDC and VBB = 2.8 VDC
at following components:
RAE-3
Flash Vcore at
VBB at
D351 C360/C361 C353/C354
D352 C362/C363 C355/C356
D353 C366/C370 C364/C365
D354
--C369
-
-
RAE-5
Flash
Vcore at
VBB at
D351 C353/C354/C360/C361
D352 C355/C356/C362/C363
D353
C366/C370
C364/C365
-------
If Vcore is not ok, check Vcore = 1.8 VDC Pin 4 of V105 and Vbatt = 4 VDC (supply voltage at the workbench) at
Pin 3 of V105. (Note! VBatt = VB) Also check surrounding components for shorts or disconnections and resolder
or change faulty ones if necessary.
If VBB is not ok, check VBB = 2.8 VDC at C111. If not ok, check VB = 4VDC at Pin 6 of N102.
If VB is ok, check N102 and surrounding components for shorts or disconnections and resolder or change the
faulty ones if necessary.
If all voltages are ok, change the faulty Flash and flash the phone.
If the flashing is OK, but only backlight can be seen on PDA side, or PDA side hangs at startup image, there might be
problems with the DOC contents, see section 3.13 DOC corrupted on page 38 for more details. It is also possible that the
EEEMU data may have corrupted, see section 3.12 EEEMU corrupted on page 36.
If the flashing is OK, but both the CMT and PDA sides remain dead, measure the current consumption of the device. If
the device draws more than 150mA (not including the current peak instantly when service battery is inserted), there is
a short circuit or a faulty circuit somewhere. If the current consumption varies between 25-40mA in a loop, see section
3.12 EEEMU corrupted on page 36. The EEEMU data may have corrupted.
See also:
Page 6, Drop faults
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
9 (55)
2.4 Contact service cases
Symptoms: “Contact service” message on CMT display
Prechecks: Production data (page 29)
Self test status (page 31)
Service actions:
If Contact Service note is on CMT display it means that phone is able to run CMT software but there is something wrong.
Wintesla can be used to check which is causing the Contact Service note. First do the following two prechecks:
- Production data: One reason for this can be the corrupted production data. Use Wintesla to check the production
data. Refer to section 3.7 Production data on page 29.
- Self Tests: If the production data seems to be correct then check Self Tests status. Refer to section 3.8 Self test status
on page 31.
If the problem is not solved in previous prechecks then try to update the phone Software. Remember that the memory
card must be updated in 9210. See section 2.13 SW update cases on page 18 and (from Nokia Partner Web Site SB Rae-3
043 / SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document if you have problems in software update.
Note: If memory corrupted phone is updated to SW 6.00 version it is possible that this new SW cleans corrupted
memory area and all EEEMU values (IMEI, power management values, tuning values etc.) may vanish right after first
start-up. This is not an error because the only way to fix this kind of corrupted phone is to use Erase only option in
WinTesla flashing (see section 3.12 EEEMU corrupted on page 36) and this will also erase all EEEMU values.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
10 (55)
2.5 SIM card cases
Symptoms: “SIM card rejected” message
Prechecks: Production data (page 29)
Service actions:
SIM Card rejected means that the dataline signal levels are wrong or factory set values are not correct.
After precheck check first if Wintesla shows SIM lock closed -message. If this is the case then you should erase
production data. See section 3.12 EEEMU corrupted on page 36 how to erase EEEMU area.
After EEEMU erase restore the production data follow steps 2-8 in section 3.12 EEEMU corrupted on page 36.
If the problem is not solved in previous steps then try to update the phone Software. Remember that the memory card
must be updated in 9210. See section 2.13 SW update cases on page 18 and (from Nokia Partner Web Site SB Rae-3 043
/ SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document if you have problems in software update.
Note: If memory corrupted phone is updated to SW 6.00 version it is possible that this new SW cleans corrupted
memory area and all EEEMU values (IMEI, power management values, tuning values etc.) may vanish right after first
start-up. This is not an error because the only way to fix this kind of corrupted phone is to use Erase only option in
WinTesla flashing (see section 3.12 EEEMU corrupted on page 36) and this will also erase all EEEMU values.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
11 (55)
2.6 Data lost cases
Symptoms: Manufacturing data lost (IMEI, PSN, power management values, tuning values etc.)
Prechecks: Production data (page 29)
Service actions:
First try to flash newest software version (SW 6.00 or newer). If this does not help and the manufacturing data is still
corrupted or completely lost, you have to erase production data to ensure that the flash chip is correctly initialized. See
section 3.12 EEEMU corrupted on page 36 how to erase EEEMU area.
After EEEMU erase restore the production data follow steps 2-8 in section 3.12 EEEMU corrupted on page 36.
If the problem is not solved in previous steps then try to update the phone Software. Remember that the memory card
must be updated in 9210. See section 2.13 SW update cases on page 18 and (from Nokia Partner Web Site SB Rae-3 043
/ SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document if you have problems in software update.
Note: If memory corrupted phone is updated to SW 6.00 version it is possible that this new SW cleans corrupted
memory area and all EEEMU values (IMEI, power management values, tuning values etc.) may vanish right after first
start-up. This is not an error because the only way to fix this kind of corrupted phone is to use Erase only option in
WinTesla flashing (see section 3.12 EEEMU corrupted on page 36) and this will also erase all EEEMU values.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
12 (55)
2.7 Charging functionality
Symptoms: Not charging
Prechecks: Screw tightening (page 25)
System connector (page 22)
A/D converter check (page 32)
Production data (page 29)
Service actions:
If you have found some wrong in charge values or Battery values (A/D converter check on page 32) then do EM
Calibration using Wintesla.
If EM Calibration fails then try EEEMU erase (see page 36).
If calibration didn’t fix the problem then try to update software if it helps to solve the problem. Remember that the
memory card must be updated in 9210. See section 2.13 SW update cases on page 18 and (from Nokia Partner Web Site
SB Rae-3 043 / SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document if you have problems during software
update.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
13 (55)
2.8 SW cases
Symptoms: PDA SW error messages (Kern-Exec 3)
PDA SW error messages (Application closed)
PDA SW error messages (Messaging Watcher)
PDA SW error messages (EtelServer)
Applications may be different language
Missing applications or files from PDA
Prechecks: Device/memory card SW version match (page 33)
Memory card with old data in 9210i device (page 34)
Service actions:
After memory card SW has been checked ensure that all applications and files exist on the device. Use the normal
battery to boot up the device and check that all application exist and use file manager to check system folder.
It is possible that user has deleted some files (e.g. under system folder) unintentionally or intentionally, removes
battery before all data are stored to memory, uninstalls pre-installed applications, formats the device, stores too much
data to the device, installs not Nokia OK signed 3rd party software etc.
If you cannot find or or correct the root case of the problem then format the device:
In 9210: Device can be formatted manually when PDA side is booting up so that the welcome screen is shown (see
page 38). Format the memory chip by pressing Ctrl+Shift+F immediately after the welcome screen appears. Note that
different language variants will have different keymats, but key locations do not change.
Another way to initialize User data area is do normal flashing using Wintesla. See (from Nokia Partner Web Site SB Rae3 043 / SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document for more detailed information.
In 9210i: Formatting can be done manually the same way than in 9210 or by flashing DOC format image. See section
3.13 DOC corrupted on page 38 for more detailed information.
If the problem disappears after formatting the most probably the problem was in the User Data, in missing or
corrupted file/files or because of Third party SW.
To ensure that XIP flash content is not corrupted then update the phone Software. Remember that the memory card
must be updated in 9210. See section 2.13 SW update cases on page 18 and (from Nokia Partner Web Site SB Rae-3 043
/ SB Rae-5 024) SOFTWARE UPDATE GUIDE BY USING FPS-8 -document if you have problems in software update.
If the SW error message disappeared after previous actions it means that the problem was on the SW side of the phone
otherwise the problem is on the HW side.
After Flash programming restore User data from Memory card if it is available. Check if the SW error message reappears
or not. If the problem reappears after restoring, repeat the previous steps without restoring User data.
NOTE! Obvious intentional damages are not covered by Nokia warranty.
See also:
Page 6, Drop faults
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
2.9 Audio functionality
Symptoms: Earpiece does not work
HF speaker does not work
Microphone does not work
Prechecks: Screw tightening (page 25)
Board to board connector (page 26)
Service actions:
See section 3.18 Audio related service actions on page 47.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
14 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
2.10 Keypad functionality
Symptoms: CMT keypad does not work
PDA keypad does not work
Lid keypad does not work
Prechecks: Screw tightening (page 25)
Board to board connector (page 26)
Service actions:
See section 3.17 Keypad (CMT or PDA) case on page 46 .
See also section 3.19 Flex failure on page 48.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
15 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
16 (55)
2.11 Displays functionality
Symptoms: CMT/PDA display does not work
Stripes on CMT/PDA display
Lines missing from CMT/PDA display
Dark areas on CMT/PDA display
PDA backlight does not work
Prechecks: Screw tightening (page 25)
Board to board connector (page 26)
Drop faults (page 6)
Service actions:
PDA display module may break because of dropping or other mechanical stress. The breakdown may occur behind the
metal frame of the PDA display module so there may not be any clearly visible breaks/damages.
See section 3.20 Broken PDA display module on page 50.
See section 3.21 Broken CMT display module on page 51.
See section 3.22 Piezo or CCFT (tube/lamp) broken on page 52.
NOTE! Obvious dropping damages are not covered by Nokia warranty.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
17 (55)
2.12 Clock functionality issues
Symptoms: CMT clock stops
Device time/date incorrect
Date/time asked every time after main battery removal (with SW 5.54 or newer)
Prechecks: Screw tightening (page 25)
Service actions:
Occurs:
In all versions but mainly in 9210i/9210NUx/9290. Partially fixed in 9210i SW 5.54.
Description:
Rechargeable backup battery has discharged (main battery has been disconnected for several days). It causes CMT clock
to stop after one hour and PDA clock runs the same hour again and again.
Repair instructions:
First flash the latest software if it is not up-to-date. Backup battery is automatically charged, when main battery is
inserted. Note! The charger has no effect in this case. Insert charged main battery and wait at least two hours. This
charges the backup battery. After this, take the main battery off (and the charger if it is connected) and keep it off at
least one minute. Put the main battery on. Set time and date (even if it is correct)!!!
If this does not help (CMT clock stops after one hour), open the device and measure the backup battery voltage. If the
backup battery voltage is below 2.3 volts after two hours charging from main battery, replace the backup battery (I027,
4700125).
Note: CMT/PDA time inconsistecy or CMT time jamming is SW related problem. No backup battery replacement is
needed, unless the backup battery has totally died.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
18 (55)
2.13 SW update cases
Symptoms: Flashing fail (Erasing fail)
Flashing fail (Phone NAK message)
Flashing fail (Failed to read data from phone)
Flashing fail (Set power on)
Flashing fail (PPM validity)
Prechecks: Board to board connector (page 26)
System connector (page 22)
Service actions:
Erasing fail:
Flashing can give erasing error if Board to board connector is open or one of XIP flashes is broken. See section 3.6
Memory failures on page 27 to fix flash problem. See also Flash programming troubleshooting from Service manual for
more detailed information.
Picture: Error message if erasing fails
Phone NAK fail (typically only in RAE-3):
An error message saying " The Phone has sent NAK signal " (see picture) is caused by either faulty flashing hardware or a
faulty serial flash. If the error message appears at the start of flashing process, it is probably caused by flashing
hardware. Check the flashing equipment (faulty cables or connections, service battery) and try to flash other phones. If
the error message appears near the end of flashing process, then the serial flash may be faulty. Change the serial flash
(D354, code 4341031).
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
19 (55)
Picture: Wintesla Error message when the Phone has sent NAK signal
Failed to read data from phone:
If EEEMU is in mode that any tuning values cannot be saved Wintesla gives message " Failed to read data from phone "
when trying to flash the phone.
In this case if you try to run factory value settings “All (UI and call counters)” (or “Full Factory”) separately Wintesla
gives the following error message:
The only way to solve the problem is initialize EEEMU and rewrite the production data. See section 3.12 EEEMU
corrupted on page 36.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
20 (55)
Set Power On:
The factory settings (EEEMU area = IMEI, SIM locks, RF tuning values etc.) are corrupted and phone fails to boot up
properly. Note: the EEEMU is D353 in RAE-3 and D352 in RAE-5, RAE-3NUx & RAB-3.
Picture: Error message if the Phone doesn’t boot up after actual flashing
In this case if this happens always the most likely reason (if flashing cables have not disconnected) is that the
production data is corrupted and EEEMU needs to be initialized and rewritten. See section EEEMU corrupted on page 36.
PPM Validity:
This error message appears near the end of flashing when running startup self test. The message appears if Factory
setting failed after actual data writing. In this case if the phone is started up with normal battery and the phone is
searching Network then the phone reboots.
Note: The phone may appear to work well after this, but factory settings have not been done properly. The phone MUST
BE successfully flashed before it is OK.
Note: There is no problem in phone hardware side.
Picture: Error message when PPM validity self test is failed.
First check that you have the latest Service Software RAE-3/RAE-5 driver version (4.30.00 or later) for Wintesla. If not
then update the Service Software drivers. If you have the latest Service Software drivers in use then try to solve the
problem by closing the Wintesla and reboot the Flashing station PC and FPS-8 and try to reflash phone again. If
rebooting didn't solve the problem then use different flashing station if possible.
See also:
Page 8, Startup/shutdown cases
Page 9, Contact service cases
Page 10, SIM card cases
Page 11, Data lost cases
Page 12, Charging functionality
Page 13, SW cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
21 (55)
3. FAULT DESCRIPTIONS, MEASUREMENTS AND SERVICE ACTIONS
3.1 Absorber pad
Occurs:
Only before IMEI 350149/10/327502/1 (part of RAE-3 HW version HWID 3119).
Fixed in all other versions.
Symptoms:
Drop calls
Description:
Device drops the call randomly (during the call). This problem is only to be reported in the early production models of
the handset (part of RAE-3 HW version HWID 3119). This problem cannot be seen when measuring TX phase difference/
frequency error from RF-connector (system connector) by using Service Car Kit. It can be seen only when TX Phase
difference/ frequency error is measured from antenna. This problem comes only when the TX is on full power, so the
phone has to be in weak field reception if this problem occurs at end user.
Root cause: Phones own TX is interfering the VCO when TX is on full power. Caused of skewed chassis (leakage in
shielding).
Repair instructions:
Add the Absorber Pad 9470225 to the chassis 9547013 if it's not already in there. See following picture for correct
positioning of the part.
See also:
Page 7, Network cases
NOTE! No problem (or very very rare!) with HAGAR, COBBA, PA or RF tuning values!
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
22 (55)
3.2 System connector
Occurs:
In all HW versions.
Symptoms:
Field strength is poor
No network
Drop calls
External audio faults (with headset / car kit)
Communication faults with computer via data cable
Not charging
Description:
Cracked guidance pins of the system connector can cause charger faults, communication faults with computer via data
cable or external audio faults because the springs of the system connector do not line up with the PWB contact pads.
External RF connector and RF switch (located inside the system connector) can cause poor RF sensitivity (10 – 20 dBm
loss in RF signal) if it is damaged physically (because of e.g. rough insertion to the car kit) or if there are dust inside the
connector.
Also all symptoms mentioned above can occur when moisture damages system connector and/or PWB pads.
Repair instructions:
Change the system connector (5460047) and clean the PWB contacts if possible.
NOTE! Obvious liquid damages are not covered by Nokia warranty.
See also:
Page 7, Network cases
Page 12, Charging functionality
NOTE! No problem (or very very rare!) with HAGAR, COBBA, PA or RF tuning values!
See pictures on next page.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Customer Care Europe, Middle East & Africa
SCCE Training Group
Date 10.07.2003
Picture: Guidance pin collapsed (left side of the pin)
Repairhints
Version 3.1
Picture: Guidance pin cracked
Corrosion damages (non-warranty case)
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
23 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
24 (55)
3.3 Coaxial cable
Occurs:
In all HW versions.
Symptoms:
Field strength is poor
No network
Drop calls
Description:
Wrongly assembled coaxial cable is crushed against the PWB. If the damaging is big enough the cable can be partially
or totally broken and can cause poor RF sensitivity (10 – 20 dBm loss in RF signal). Note that totally broken or
disconnected hinge may cause breakdown of a coaxial cable so in these cases check the state of the coaxial cable at the
audio holder end too.
Repair instructions:
Change the coaxial cable (9780276) or the frame assembly (9467039). Be sure that the cable is in correct position (see
following pictures).
See also:
Page 7, Network cases
Wrongly assembled coaxial cable
Copyright © 2001-2003 Nokia.
All rights reserved.
Correctly assembled coaxial cable
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
25 (55)
3.4 Screw tightening
Occurs:
In all HW versions.
Symptoms:
Drop calls
No network
Poor network
Poor network quality
Device shuts down / switches off
Device dead (CMT and/or PDA)
PDA frozen (white display or jams into startup picture)
“Contact Service” note on CMT display
Not charging
Description:
In normal use the back cover screws, especially the two screws near the system connector, may eventually get loose.
This allows the system connector to move and the contacts to be lifted off the pads, causing various network problems.
If the screws near SIM card or memory card are loose, “Insert SIM card” or dropped call problems may occur. The system
connector guidance pins may get damaged, if the device is used when the screws are loose. See System connector on
page 22.
Solution: Tighten all the back cover screws correctly to 15 Ncm and check that board to board connector is closed (see
page 26).
See also:
Page 6, Drop faults
Page 7, Network cases
Page 8, Startup/shutdown cases
Page 12, Charging functionality
Page 14, Audio functionality
Page 15, Keypad functionality
Page 16, Displays functionality
Page 17, Clock functionality issues
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
26 (55)
3.5 Board to board connector
Occurs:
In all HW versions.
Symptoms:
Device dead (both sides, CMT and PDA)
Device shuts down / switch off
CMT keypad doesn't work
Lid keypad (next to PDA display) failures
PDA keypad doesn't work
Picture failure in PDA display
Dark areas in PDA display
Dark areas in CMT display
Dark lines/areas flashes in CMT display
Pixels missing in CMT display
CMT display not working sometimes
Earpiece doesn't work
HF speaker doesn't work
PDA freezed (white display etc.)
Description:
The most common failure is that board to board connector is open when the back cover screws have opened in use, or
the phone is poorly assembled or it has opened by hit or drop etc.
Repair instructions:
Press PDA keyboard with thumb on right spot (see following picture) and you may feel little “click” when board to
board connector attach. Check that all screws in the back cover are tight. See 3.4 Screw tightening on page 25.
See also:
Page 6, Drop faults
Page 8, Startup/shutdown cases
Page 14, Audio functionality
Page 15, Keypad functionality
Page 16, Displays functionality
Page 18, SW update cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
27 (55)
3.6 Memory failures
Occurs:
In all hardware versions.
Symptoms:
Device dead, CMT display backlight blinking
Description:
Boot self-tests have failed. One or more of the memory chips may be physically faulty, or old software in the phone
does not support newer memory chips.
Repair instructions:
Check the CMT display blink count. The blinks come with 1 second interval to indicate the fault, and with two second
interval between fault codes. More than one fault may be reported. After reporting, the cycle starts over. Note that the
watchdog kills the device after 30 seconds. After this the main battery has to be kept off so that all internal
capacitances can be drained. This can take up to one minute.
The blink codes are as follows:
2 – XIP flash fault (D351/D352/D353 in 9210, D351/D352 in 9210i/9210c/9290)
3 – SDRAM fault (D350)
4 – Serial flash fault (D354, only 9210)
5 – DiscOnChip fault (D353, only 9210i/9210c/9290)
If the blink codes indicate SDRAM fault, SDRAM chip (D350) can be changed without further indications. In all other
cases, flash the device first. Check the flash ID codes at Wintesla flash window (see following picture).
In the flash window a flash ID string is given in the following format:
" Flash ID: aaaa-aaaa, bbbb-bbbb, cccc-cccc, dddd-dddd "
In 9210 the first three codes (aaaa-aaaa, bbbb-bbbb and cccc-cccc) represent Intel flash chips D351-D353. The last code
(dddd-dddd) represents the serial flash device D354.
In 9210i/9210c/9290 the first two codes (aaaa-aaaa and bbbb-bbbb) represent Intel flash chips D351-D352. The third
code (cccc-cccc) is not used and is always 0000-0000. The last code (dddd-dddd) stands for the DiskOnChip, D353.
0089-8896
Intel 28F320B3T
0000-0030
Atmel AT45DB321
0089-8864
Intel 28F640W18
0020-8810
ST M58WR064
3030-0130
DiskOnChip MD2212-D16
4141-4141
Mobile DiskOnChip, MD3830-D16
0000-0000
Invalid code. Indicates not used or faulty device
Table 1. Currently used device ID codes
Note: If blink codes give DiskOnChip fault, always flash latest SW (6.00 or later) first.
Note: If D353 on 9210 or D352 on 9210i/9210c/9290 is changed, all factory settings must be set. See instructions in
EEEMU corrupted on page 36.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
RAE-5 - & gt; Third code not used
Flash ID's OK
Flash D351 faulty
Flash D352 faulty
DiskOnChip D353 faulty
Examples of incorrect Flash ID's
See also:
Page 8, Startup/shutdown cases
Page 18, SW update cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
28 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
29 (55)
3.7 Production data check
Occurs:
In all hardware versions.
Symptoms:
SIM card rejected
“Contact service” note on CMT display
Description:
Insert the service battery and check if the phone boots up or not. If the device is running the current consumpion is
continously bigger than 45mA and it is possible to check the production data with Wintesla. Also Test picture should be
visible on the PDA display.
But if the device is dead and cannot connect with Wintesla, Wintesla can display the " Failed to read data from phone " message on PCs screen.
In this case it is possible that the production data is corrupted and needs to be initialized. Jump then directly to section
2.6 Data lost cases on page 11.
If the phone is running check first SIM lock status with Wintesla. After initialization Wintesla will show automatically
the following window if SIM locks are closed.
Figure: Quick Info message when IMEI missing and SIM locks are closed
Then check the Product information with Wintesla. If Wintesla cannot read correct IMEI, HW, Original Serial number etc.
from the device then manufacturing data is lost and you have to rebuild it. In this case first erase EEEMU and then
rewrite the production data. Jump then to section 2.6 Data lost cases on page 11.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
30 (55)
Picture: Example of Phone Identity Information when the production data is empty or erased
Finally check if you can change and save a new PDA display contrast value or not. If you are not able to rewrite any
tuning values or production data you have to erase production data and rewrite all data back. Jump then to section
3.12 EEEMU corrupted on page 36 to correct the problem.
See also:
Page 8, Startup/shutdown cases
Page 9, Contact service cases
Page 10, SIM card cases
Page 11, Data lost cases
Page 12, Charging functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
31 (55)
3.8 Self test status check
Occurs:
In all hardware versions.
Symptoms:
“Contact service” note on CMT display
Description:
Seft tests are executed when power is switched on and software is started from XIP flash. In the most cases if the self
tests fail the " Contact Service " is shown on the phone display.
Self test information can be used for diagnosis. The most common failures are listed below:
Item no. 3 RTC battery:
If this test fails the real-time clock is not functioning correctly. The backup battery may be empty, or missing. See Empty
backup battery section how to measure RTC battery (viitaus Empty backup battery).
Item no. 9 EEPROM Tune checksum:
See Data lost cases, page 11
Item no. F EEPROM Sec Checksum:
See Data lost cases, page 11
Item no. G PPM Validity:
See SW Update cases - & gt; Flashing failed (PPM validity) (page 18)
Picture: Example of MCU Self test status –window (PMM/EEEMU area is empty)
Note! If PMM/EEEMU area is empty MCU Self -tests “9 EEPROM Tune Checksum” and “F EEPROM Sec
Checksum” are always failing (see picture above).
See also:
Page 6, Drop faults
Page 9, Contact service cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
32 (55)
3.9 A/D converter check
Occurs:
In all hardware versions
Symptoms:
Not charging
Headset doesn’t work
Phone boots to test mode with normal battery (BLL-3)
Description:
Insert Normal battery BBL-3 into phone and turn the CMT on. Initialize phone to normal
mode with WinTesla. Select Testing - & gt; ADC Readings from WinTesla.
WinTesla pops up a window like picture 1.
Value should be near this
value if voltage is
3.7Volts.
Value should be near this
value if temperature is
24°C
Value is zero if charger is
not connected. During
charging value varies.
If value is zero charger is
not connected. When
phone is charging value
varies.
If value is 1023 there is
no
accessories
connected
(can
be
tested only in module
jig)
Picture 1.
With Normal battery
value should be near this
value. With Test Battery
value is 310-380
Hook information: When e.g. headset button is pressed the value change to 1. (Can be tested only in module jig)
Cover Detection: When lid is open value is 1.
Card Cover detection: When card cover is open value is 1.
Battery Remowal Switch: NOT IN USE (no affect to any functions).
NOTE! If phone has some wrong values in charge values or Battery values then try to Calibrate values with WinTesla EM
Calibration. If calibration doesn’t fix the problem you can find tips from Service Manual Troubleshooting section.
See also:
Page 12, Charging functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
33 (55)
3.10 Device/memory card SW version match
Occurs:
All 9210 devices
Symptoms:
PDA SW error messages (Kern-Exec 3)
PDA SW error messages (Application closed)
PDA SW error messages (Messaging Watcher)
PDA SW error messages (EtelServer)
Applications may be different language
Missing applications or files from PDA
SW hangs
Description:
Check that phone PPM language and Memory card SW versions matches. Phone Identity Information shows the version
read from the phone. Check picture bellow:
Note: Application memory card is used only in 9210 variants.
Picture: SW versions read from the phone
See also:
Page 13, SW cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
34 (55)
3.11 Memory card with old data in 9210i device
Occurs:
All 9210i devices
Symptoms:
PDA SW error messages (Kern-Exec 3)
PDA SW error messages (Application closed)
PDA SW error messages (Messaging Watcher)
PDA SW error messages (EtelServer)
Applications may be different language
Missing applications or files from PDA
SW hangs
Description:
A memory card that has 9210 data should not be used in 9210i device. A 9210 memory card contains applications that
are installed in 9210i device memory. Having same applications in two places causes instability.
Check the contents of the memory card with either a memory card reader, or with a phone.
First check the memory card \system\data directory for an empty file named “MMC 4.13(A)” or similar,
depending on software version and language variant. Wintesla shows this version information of the system data on
memory card, but it does not check applications. Check \system\apps directory for the following subdirectories:
- calc
- cword
- ppview
- sheet
- voicerecorder
If any of the previously mentioned files or folders are present, delete the \system folder. This way the applications do
not cause problems and some memory is freed from the memory card. If there are user-installed applications on the
memory card, rename the \system -directory to something else. If checked with Wintesla, no version information
should be found from memory card (see picture on next page).
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
See also:
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
Page 13, SW cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
35 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
36 (55)
3.12 EEEMU corrupted
Occurs:
In all RAE-5, RAE-3NUx and RAB-3 versions. EEEMU problems fixed in SW 6.00 and newer.
Description:
The production data area (EEEMU area = IMEI, SIM locks, RF tuning values etc.) is corrupted and phone fails to boot up
properly. The EEEMU is D353 in RAE-3 and D352 in RAE-5, RAE-3NUx & RAB-3.
See also:
Page 8, Startup/shutdown cases
Page 9, Contact service cases
Page 10, SIM card cases
Page 11, Data lost cases
Page 18, SW update cases
Repair instructions:
In 9210i: First update SW 6.00 or newer. It is possible that new SW cleans corrupted memory area and restores the
production data (IMEI, power management values, RF tuning values etc.) automatically after flashing. Wintesla may
give an error message (PPM validity or Failed to read data from phone) after first flashing. Then you MUST DO the phone
flashing again to ensure that all factory settings are correct.
If flashing didn't solve the problem then you have to erase EEEMU area. Production data area can be erased and correct
settings can be re-programmed. It is very rare that flash chip itself (D353 in RAE-3 or D352 in RAE-5 & RAE-3NUx & RAB3) has to be changed. Note that this erase will wipe out all factory settings, including IMEI, SIM lock data and RF tuning
values.
Note: This procedure requires that Service Point must have Nokia permission to do IMEI and SIM lock re-build!
Step 1. Erase production data area with Wintesla UI:
- Use Flash phone -dialog by selecting Dealer - & gt; Flash Phone -menu (see picture below).
Picture: Wintesla UI when N92XX is not running or cannot communicate with PC
Note: Remember to mark Erase Only (see picture below)!
If Erase Only is dimmed in RAE-3: Download RAE-3.exe from Nokia Partner Web Site / Software (RAE-3), the name of the
file is “XIP Flash memory (D353) corruption repair INI-file”, run it and copy extracted rae-3.ini file to \wintesla\rae-3 –
directory. Similar files are delivered with the latest RAE-5/RAE-3NUx/RAB-3 MCU software packages.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
37 (55)
Picture: Flash Phone -dialog and marked Erase only
Production data erasing takes about 10 seconds if selected images are already loaded into the Prommer.
If phone wakes up after erasing, it will show " Contact Service " on CMT display and the Quick Info -window appears on
PC screen. This is the same situation than in Data lost cases (See page 11).
Step 2. Run Full Factory Set
Step 3. Re-build Production data (=Product code HWID etc.), IMEI and SIM lock data
Step 4. Do RF tunings etc.
Step 5. Do Energy Management (EM) calibration
Step 6. Do PDA display Tuning
Step 7. Run Accessory factory set
Step 8. Flash the latest software in the phone, even if the phone has had the latest SW!
See the programming instruction refer to (from Nokia Partner Web Site SB Rae-3 043 / SB Rae-5 024) SOFTWARE UPDATE
GUIDE BY USING FPS-8 -document.
Note! Every time when it is necessary to change D353 in RAE-3 or D352 in RAE-5/RAE-3NUx/RAB-3 or
erase the factory setting area all steps 2 to 8 above must be done, and in the order shown!
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
38 (55)
3.13 DOC corrupted
Occurs:
In all RAE-5, RAE-3NUx and RAB-3 versions.
Description:
User Data is corrupted, or the memory chip has physically failed.
See also:
Page 8, Startup/shutdown cases
Page 13, SW cases
Repair instructions:
First check if CMT backlight leds are blinking. If yes, see separate chapter for memory failures (page 27). If no, follow
these instructions:
Note: Formatting DiscOnChip (D353) or changing it will erase all user data + some pre-installed applications (e.g. Word
Processor)!
Step 1, Option
A: Format DOC manually (if it is not possible see next page for Option B)
If PDA side is booting up so that the welcome screen is shown, format the memory chip by pressing Ctrl+Shift+F
immediately after the welcome screen appears. Note that different language variants will have different keymats, but
key locations do not change.
Open the lid. When you see the welcome screen, immediately press and hold down the 'Ctrl+Shift+F' keys. The 'F' key
should be pressed last. If Format menu did not appear then remove & insert the battery and try again.
Select Format. Formatting starts. NOTE! Do not remove battery before the Select Home City –menu appears!
Step 2: Flash program the official phone sw
Flash the latest phone software. See the programming instruction refer to (from PWS) RAE-3 / RAE-5 SOFTWARE UPDATE
GUIDE BY USING FPS-8 –document.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
Step 1, Option
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
39 (55)
B: Flash program DiskOnChip low level format image (for formatting DOC)
If PDA side is not booting up enough to show the welcome screen, reflash special low level format image to erase user
data. After formatting remember to reflash the latest official phone sw.
Preparing step:
Download self-extracting archive file DOC_D353.exe (DiskOnChip low level format package) from Nokia Partner Web Site
/ Software (RAE-5) and run it if you haven’t run it before. It will extract DOC_D353.fia and DOC_D353.fi0 files to
\wintesla\rae-5 –directory.
1) Select DOC_D353.FIA to MCU Image File by pressing upper ‘…’ and DOC_D353.FI0 to PPM File by pressing lower ‘…’
and then press ‘Flash’ button. Note! Erase Only is not selected.
2) After succesfully flashing remove BBL-3B Service Battery and SCH-8 cable
3) Open the lid
4) Boot up the opened device with the normal battery BLL-3 and look at the PDA display: If PDA boot up and after a
while PDA display is green and shows " Ready " -text in white box that means D353 Flash is successfully formatted.
PDA display after successful format (=D353 OK)
But if PDA display is red then D353 is faulty → Change D353 (very rare case)
Step 2: Flash program the official phone sw
Flash the latest phone software. See the programming instruction refer to (from PWS) RAE-3 / RAE-5 SOFTWARE UPDATE
GUIDE BY USING FPS-8 –document.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
40 (55)
3.14 Oscillator related measurements
Occur:
In all RAE-5, RAE-3NUx and RAB-3 versions.
Symptoms:
Drop calls
No network
Poor network
Poor network quality
Description:
Check TX I/Q EGSM, Ch: 60 with WinTesla menu Tuning/ TX I/Q. (See picture below)
The G800 SHF Oscillator is working well
The Oscillator is not working
If right hand side picture is appearing on spectrum analyser, check following voltages:
Check Vsynte line (VSYN_2/VCC) = 2.8 VDC at R808 - & gt; If Vsynte is OK, check G800 SHF oscillator and surrounding
components for shorts or cold soldering and change or resolder the faulty ones.
If Vsynte is NOT OK, remove R808 and measure the voltage on the pad to HAGAR`s side.
If Vsynte (VSYN_2/VCC) is NOT OK on Hagar side pad after removing R808
Check VC = 2.2 VDC at R802.
If VC is NOT OK, check components R801, R802, R807, C801, C802, C803, C807. If components are OK refer to RF ASIC
related measurements (on page 43).
Check Vchp = 4.7 VDC at C560.
If NOT OK, check VCP = 4.9 VDC at N600 Pin 6. If NOT OK, refer to RF powering related measurements (on page 41).
If VCP is OK, check N600 voltage regulator and surrounding components for shorts or disconnections and change the
faulty ones. If the surrounding components are ok, change G800 SHF oscillator.
See also:
Page 7, Network cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
41 (55)
3.15 RF powering related measurements
Occur:
RAE-3 HW versions HWID 3119, 4000 and 4010.
CCONT soldering related problems fixed in HW version HWID 4200 (IMEI: 350149/10/387204/1- & gt; ) and all
RAE-5/RAE-3NUx/RAB-3 -versions.
Symptoms:
Drop calls
No network
Poor network
Poor network quality
Description:
If the antenna bar is fluctuate, put the BL8/KL8 mudule into the repair jig MJS-14. Try to make a connection with e.g.
Wave Tec, CMU or CMD .
Check VRX=2.8V at C133 and VSYN_1=2.8V at C135 and also Check Vsynte at C561= 2.8 VDC
If the voltages fluctuate it’s possible that CCONT has broken solder joint. Change CCONT like in following instructions:
Solder balls in the corner of CCONT (4370719) (ball no H1/H2, affect to VSYN_1/VSYN_2) may break because of dropping
or other mechanical stress. This can be seen as an " Black pad " problem in these pads. This has been fixed by taking new
PWB BL8_20 into use (see occur field). This new PWB version has OSP plating on solder area. After this change there has
not been any problems in CCONT solder ball interface to PWB. So in new versions (HWID 4200 or newer) it's very rare to
have any kind of broken solder joints. 9210i version (and 9210c & 9290) has always had this OSP plating, as well as in
9210 after HWID 4200.
Repair instructions:
Devices which have this kind of failure can be fixed by changing the CCONT (4370719) but before changing you have to
be sure that PWB surface is not damaged. Please see attached pictures to be sure that everything is ok.
Any kind of re-heating is prohibited. In the newer version of PWB (BL8_20) re-heating may cause serious damage to
solderings because of OSP layer fades out and doesn't protect PWB after that.
Here you can see so-called " black pad " . Solder doesn't attach to pad easily anymore. This is usually the corner of H1/H2
of the CCONT where the broken solder joints are.
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
Lightly tin the pads of the CCONT. Do not scratch the
pad surface or apply any mechanical stress to the
pad. If you can't tin the pads with solder you have to
scrap the whole module.
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
After you manage to tin the pad, clean the pad once
again and make sure that pad looks like in this
picture (the pad is totally covered with solder).
After this you can put the new CCONT into it's place.
If the fault persists, refer to RF ASIC related measurements (page 43).
See also:
Page 7, Network cases
Copyright © 2001-2003 Nokia.
All rights reserved.
42 (55)
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
43 (55)
3.16 RF ASIC related measurements
Occur:
All HW versions
Symptoms:
Drop calls
No network
Poor network
Poor network quality
Description:
Check VTCXO (VXO) = 2.8 VDC at C553.
If NOT OK, go to RF powering related measurements section on page 41.
Check 26MHz (Vpp = 800mV AC) at R835, frequency deviation ±100Hz (See picture below).
If NOT OK, check G830 oscillator and surrouding components.
Check RFC = 13MHz (Vpp = 800 mVAC) at L800, frequency deviation ±50Hz (See picture below)
If NOT OK, check V800 and surrounding components for shorts or disconnections and change the faulty ones, otherwise
probably N505 HAGAR circuit is faulty.
Check Vsynte (VSYN_2) = 2.8 VDC at C561. If NOT OK, refer to RF powering related measurements (page 41).
Check VREF_2 = 1.5 VDC at R564. If NOT OK, refer to RF powering related measurements (page 41 ).
Check Vchp = 4.7 VDC at C560. If NOT OK, refer to section (Oscillator related measurements) on page 40.
Check Vrxrf (VRX) = 2.8 VDC (RX active). If NOT OK, refer to RF powering related measurements (page 41).
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
44 (55)
Check Reset = 2.8 VDC (in Local Mode) and 2.8V pulse (in Normal Mode / one part (RX/TX) active) at R800 (See picture
below)
Check Vmod (VTX) = 2.8V at R700. If NOT OK, refer to RF powering related measurements (page 41).
Check TXC (TX active) at power level 5 (picture on left side) and at power level base (Picture on right side) at R792. If
NOT OK, check N200 COBBA and line TXC from Cobba to R792.
Check SCLK at J501, SDATA at J500 and SENA at J502. (See picture below)
If one or all three signals are NOT OK, probably the D300 MADLINDA is faulty or PWB via is broken.
SCLK
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
SDATA
SENA
See also:
Page 7, Network cases
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
45 (55)
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Customer Care Europe, Middle East & Africa
SCCE Training Group
Repairhints
Version 3.1
Date 10.07.2003
46 (55)
3.17 Keypad (CMT or PDA) case
Occur:
All HW versions
Symptoms:
CMT keypad does not work
PDA keypad does not work
Lid keypad does not work
Description:
If some of the keys or all keys doesn’t work on PDA or CMT side please check first Board to board connector (see page
26). If CMT keypad is still not working check also connector from UI side.
Also check contact areas because there might be some dust/dirt that may cause keypad problems.
If connector is OK try to change QWERTY-flex module and test the keypad after the change.
If CMT keypad is still not working check from device which keys doesn’t work. From table below can be seen which col
or row lines are not working.
Row1
Col0
cmt
soft1
Send
Row2
Row3
Row4
cmt 1
cmt 4
cmt 7
Row5
Row6
Row7
Row8
Row9
ESC
Row0
1
Tab
Caps
Col1
cmt Up
Col3
Soft 3
Col4
Soft 1
cmt
Down
cmt 2
cmt 5
cmt 8
Col2
cmt
Soft2
End
Soft 4
Soft 2
cmt 3
cmt 6
cmt 9
Profile
cmt *
cmt 0
Power
cmt #
App1
Ctrl
2
Q
A
App2
V
3
W
S
App3
X
4
E
D
app4
6
5
R
F
Col5
App6
App5
7
T
G
Col7
Space
Col8
Info & lt;
Col9
/ & gt;
Z
Menu
:;
Col6
Shift
C
B
Chr
Up
+-
M
Down
,@
Left
Enter
App7
N
Right
Backsp
ace
App8
8
Y
H
9
U
J
0
I
K
P
O
L
See following table to see which lines go through each EMI filter:
Z401
Z402
Z403
Z404
Col0
Col4
Col1
Row1
Row0
Col5
Col2
Row2
Col6
Col3
Row3
Col8
Col7
Row4
Col9
Row5
Row7
Row9
Row6
Row8
Change that filter which is affecting to non-working row or col lines.
More information can be found from Service Manual.
See also:
Page 15, Keypad functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
47 (55)
3.18 Audio related service actions
Occur:
All HW versions
Symptoms:
Earpiece does not work
HF speaker does not work
Description:
If Earpiece or HF speaker doesn’t work please check first section 3.5 Board to board connector on page 26 and also 3.4
Screw tightening on page 25.
If earpiece sound quality is poor or sound is low check first if there are some dust/dirt on the earpiece element. Change
the earpiece if needed, do not touch to the film of the earpiece element or to the springs. Check also the condition of
the earpiece gasket. If it is curved change it.
Picture: Erapiece element with earpiece gasket
Check solderings of AF8 Audio PWB to FL1 Qwerty-flex board. Qwerty-flex might be cracked near by audio PWB AF8.
These failures can be seen from pictures below.
Picture: Earpiece via cracked/delaminated
HF speaker via cracked
More information can be found from service manual
See also:
Page 14, Audio functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Customer Care Europe, Middle East & Africa
SCCE Training Group
Date 10.07.2003
Repairhints
Version 3.1
48 (55)
3.19 Flex failure
Occurs:
In all versions.
Symptoms:
Device dead (both sides, CMT and PDA)
Device shuts down / switch off
CMT keypad doesn't work
Lid keypad (next to PDA display) failures
PDA keypad doesn't work
Picture failure in PDA display
Dark areas in PDA display
Dark areas in CMT display
Dark lines/areas flashes in CMT display
Pixels missing in CMT display
CMT display not working sometimes
Earpiece doesn't work
HF speaker doesn't work
PDA freezed (white display etc.)
Description:
Most common failure is that board to board connector (70 way) is just open, see Board to board description on page
26.
Solder joints of the board to board connector (70 way) in the UL8 QWERTY flex module may break because of dropping
or other mechanical stress (see following picture). The UL8 can also be damaged if UL8 and flex cover (I022, 9460357) is
exposed to dirt/dust. As well PDA keypad contact problems are caused by dust/dirt on the contact area. Earpiece and HF
speaker failures might be caused by broken traces on the UL8 (usually near the audio end of UL8). Lid side failures
might be caused by broken solder joints of the 50 way connector in UL8. Note! Oxidation of the silver jumpers (see
following picture) in UL8 are not sign of any kind of failures.
Repair instructions:
Change UL8 QWERTY-flex (I024, 0201667) and if needed also flex cover (I022, 9460357).
See also:
Page 15, Keypad functionality
Broken flex
Oxidated silver jumpers (NOT a problem)
50-way connector
70-way connector
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
Damaged flex cause failures in PDA display
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
49 (55)
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
50 (55)
3.20 Broken PDA display module
Occurs:
In all versions.
Description:
PDA display module may break because of dropping or other mechanical stress. The breakdown may occur behind the
metal frame of the PDA display module so there may not be any clearly visible breaks/damages.
Repair instructions:
Change the PDA display module (I009, 4850225). NOTE! Obvious dropping damages are not covered by Nokia warranty.
See also:
Page 6, Drop faults
Page 16, Displays functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
51 (55)
3.21 Broken CMT display module
Occurs:
In all versions.
Description:
CMT display module may break because of dropping or other mechanical stress. The breakdown may occur behind the
metal frame of the CMT display module so there may not be any clearly visible breaks/damages. Also the flex of the CMT
display module may also break because of mechanical stress (see following pictures).
Repair instructions:
Change the CMT display module (I007, 4850177). NOTE! Obvious dropping damages are not covered by Nokia warranty.
See also:
Page 6, Drop faults
Page 16, Displays functionality
CMT display flex failures
Pixels missing from CMT display
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
52 (55)
3.22 Piezo or CCFT (tube/lamp) broken
Occurs:
In all RAE-3 (9210) versions and in RAE-5 HW versions 32xx, 3305, 5005. Fixed in RAE-5 HW version HWID
5105 and in all 9210NUx/9290 versions (LED version of backlight already in use).
Symptoms:
No backlight on PDA display
Description:
Piezo or CCFT may break because of dropping or other mechanical stress.
Repair instructions:
If the PDA starts up (startup logo is seen), but the illumation is off, probably the piezo is broken or the backlight circuit
is faulty. Check Piezo_in frequency around 135kHz (Vpp = 10 VAC) at L151 and Feedback frequency around 135kHz (Vpp
= 2.7 VAC) at R158. (See picture below)
Piezo_in
Feedback
If Feedback frequency is around 0Hz or Piezo_in frequency is around 100kHz, change CCFT (See SB-014), because the
piezo is broken (see pictures below)
If changing the CCFT, do not forget to paste the damper (9480703) on the CCFT Lamp and Piezo unit to prevent noises
and damages. (See picture below)
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
53 (55)
If the fault persits, probably the UL2 module can also be faulty. (Refer to Service Manual/ Troubleshooting/ BL8 related
PDA UI problems
Change CCFT lamp and piezo unit (I078, 4850183) and report broken part (if CCFT lamp is broken, report I078; if piezo is
broken, report I079; if you don't know which is broken, report I078). Check also the state of the backlight connector
(X006, 5469153).
NOTE! Obvious dropping damages are not covered by Nokia warranty.
CCFT lamp and piezo unit
Backlight connector
See also:
Page 6, Drop faults
Page 16, Displays functionality
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
Customer Care Europe, Middle East & Africa
SCCE Training Group
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Date 10.07.2003
Repairhints
Version 3.1
54 (55)
3.23 Broken mechanics
Occurs:
In all versions.
Broken A-cover snaps
Broken hinge (see page24)
Broken locking latch
Broken A-cover lens
Broken card cover
Note! Clear dropping failures (e.g. PDA display cracked, broken A-cover lens) are always not covered
by Nokia warranty.
See also:
Page 6, Drop faults
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE
CONFIDENTIAL
RAE-3/RAE-5 9210/9210i
Customer Care Europe, Middle East & Africa
SCCE Training Group
Date 10.07.2003
Repairhints
Version 3.1
55 (55)
Change History
Originator
CC Training
Group
CC Training
Group
CC Training
Group
CC Training
Group
R & D Group
Status
Draft
Version
0.1
Date
02.10.2001
Comment
First version for the repair group
Approved
1.0
30.10.2001
First approved version
Draft
1.5
01.03.2002
Approved
3.0
28.10.2002
Chapter Flash faults comments changed, information
MMC modified
RAE-5 part added
3.1
10.07.2003
Layout changes & R & D solutions added
Copyright © 2001-2003 Nokia.
All rights reserved.
Checked by:
SCCE Training Group
Approved by:
SCCE