Sie sind auf Seite 1von 1

6600 Boot up troubleshooting quide update 1.10.

2004
Assumed that no MMC in phone and normal mode boot
>150mA
Boot
Problems 50-100mA
30mA

0-25mA
LCD&keyboard
Current
backlights light Check clocks and voltages Probably short circuit somewhere
Battery consumption Check powerbutton(S130) HW boot failure
up when No Yes reflash sw check UI protective tape, check
connector ok? when pressing Check R132&R133 check voltages, clocks No sw in phone?
powerbutton is change D100&reflash voltages
powerbutton 0mA Might also be UEM(D190) no help->change UPP reflash sw
pressed change D314&reflash
failure which cannot be WD2(D100)
(+rebuld IMEI)
fixed
Replace/fix the
Yes No 1. The address of the failing flash can be
connector
obtained from the Rx buffer dump(FPS-8
flashing). The message is as follows
Replace D314, D315, D316 or
Yes D317. See text on the right for ...940406 06 28FFFF XXXXYYYY …
Keyboard 94 starts the actual failure message
more details
backlights turn Flashing C586 or C684 0406 indicate the actual failure code
No Reflash the phone Yes
off(=sw chksum problems? error code? 06 indicates the flash in question
ok)? Follow the instructions of the 6600 if 00 =problem at D314
BB troubleshooting document if 02 =problem at D316
No regarding flashing failures if 04 =problem at D315
No if 06 =problem at D317
Yes 28FFFF indicates the exact byte address
of the failure within one of the flashes
Phone works? XXXXYYYY X’s define the expected
Most phones should now be ok for delivery back to customer, but in some rare cases
content and Y’s the content found
there may be a problem with the flash data corruption by itself over time. If possible
Yes if the address is something else then
keep the phone unpowered for 2-3 days and check if it still boots up, if it doesn’t then
“Nokia” text replace D100(error message might be
D314-D317 should all be replaced(no reliable way to find out which flash is failing).
comes on something like ... 940406 CD 9C65F0 ...)
screen?
2. The address can be found from
UPP WD2 or flash failure? FPS8.log file(scroll to last entry) located
No Start by replaceing D100 and if that in Phoenix install folder. This method can
Yes doesn’t help then replace D314-D317 be used if FPS-4 is used for flashing. In
the logfile the address is in 0x 06 28FFFF
Phone format.
LCD “NOKIA” No
turns off
backlights turn text stays on DSP boot problems?
No exactly 3 5secs No
off for a short display replace UPP WD2(D100)
after boot
while? >1min
No variant sw in the phone? start?
Yes
Flash ppm image to the phone Check/replace N380 or
LFFS problems?
Yes IMEI lost from D314, but not from D315.
Format LFFS
If format didn’t help/work, Yes In this case the IMEI cannot be rebuilt
No before D315 has been erased/replaced.
replace D316(and format LFFS)
“contact UPP WD2 problems? ->erase/replace D315
retailer” Replace D100
LFFS corrupted/not formatted or a selftest failure Actions required after a chip has been replaced:
message?
Boot the phone to Local mode and check with Phoenix D314 replaced->Reflash and rebuild IMEI
Yes FLS-4 users can format the LFFS with the “three finger trick”. Keep D315 replaced->Reflash, rebuild IMEI&simlocks
No buttons “answer”, “star” and “3” pressed simultaneously and press the and retune RF&BB
powerbutton, The three buttons can be released after text “Formatting” D316 replaced->Reflash and Format LFFS
appears on device screen. The trick works in normal mode. If D317 replaced->Reflash
formatting doesn’t complete->replace D316 D100 replaced->Reflash
“Sim card
rejected”
message?
Simlocks active /corrupted, check with simlock test in Phoenix
If simlock test result is locked and detail data ..FFFF..
Yes
No ->Rebuild IMEI+simlocks also check/retune RF&BB settings
if detail data something else then check with correct sim If the phone gets stuck on a reset loop or If the phone behaves differently each time
if some error messages are shown it is it is booted up it is probably due to a bad
Phone turns off
possible that some files on c-drive(LFFS) UPP WD2(D100) ->replace D100, reflash
exactly 32secs
are corrupt. This may be due to a faulty the phone and retest. Ram(D312) fault
after boot
IMEI lost from Both D314 and D315 flash component(D316), unsuppotrted could also cause this king of behaviour,
start?
Rebuild IMEI, check simlocks and third party application installation or some boot to local and run RAM selftest -
Yes
RF&BB tunings interrupt during the first device boot. replace D312 if selftest fails.
not the above->change D100 Format LFFS first. If the same failure re-
No
occurs->replace D316(requires reflash
and format). Ram(D312) fault could also
Phone crashes Might be something wrong with BT module cause this king of behaviour, boot to local
right after boot Boot the Phone to Local mode and run selftests and run RAM selftest - replace D312 if
Yes
finished(within If ST_LPRF_AUDIO_LINES_TEST fails then first try to selftest fails.
60secs)? reflash and if that doesn’t help replace BT module.

Format LFFS and if that


No
doesn’t help, reflash phone.

Das könnte Ihnen auch gefallen