6600 boot problam.pdf

6600 Boot up troubleshooting quide update 1.10.2004

Assumed that no MMC in phone and normal mode boot

Boot

Problems

>150mA

50-100mA

30mA

0-25mA

LCD&keyboard

backlights light

up when

powerbutton is

pressed

Battery

connector ok?

Yes

Current

consumption

when pressing

powerbutton

Check powerbutton(S130)

Check R132&R133

Might also be UEM(D190)

failure which cannot be

fixed

HW boot failure

check voltages, clocks

no help->change UPP

WD2(D100)

No sw in phone?

reflash sw

Check clocks and voltages

reflash sw

change D100&reflash

change D314&reflash

(+rebuld IMEI)

Probably short circuit somewhere

check UI protective tape, check

voltages

0mA

Replace/fix the

connector

Yes

1. The address of the failing flash can be

obtained from the Rx buffer dump(FPS-8

flashing). The message is as follows

...940406 06 28FFFF XXXXYYYY …

94 starts the actual failure message

0406 indicate the actual failure code

06 indicates the flash in question

if 00 =problem at D314

if 02 =problem at D316

if 04 =problem at D315

if 06 =problem at D317

28FFFF indicates the exact byte address

of the failure within one of the flashes

XXXXYYYY X’s define the expected

content and Y’s the content found

if the address is something else then

replace D100(error message might be

something like ... 940406 CD 9C65F0 ... )

Keyboard

backlights turn

off(=sw chksum

ok)?

Yes

Replace D314, D315, D316 or

D317. See text on the right for

more details

Flashing

problems?

C586 or C684

error code?

Reflash the phone

Yes

Follow the instructions of the 6600

BB troubleshooting document

regarding flashing failures

Yes

Phone works?

Yes

Most phones should now be ok for delivery back to customer, but in some rare cases

there may be a problem with the flash data corruption by itself over time. If possible

keep the phone unpowered for 2-3 days and check if it still boots up, if it doesn’t then

D314-D317 should all be replaced(no reliable way to find out which flash is failing).

“Nokia” text

comes on

screen?

2. The address can be found from

FPS8.log file(scroll to last entry) located

in Phoenix install folder. This method can

be used if FPS-4 is used for flashing. In

the logfile the address is in 0x 06 28FFFF

format.

UPP WD2 or flash failure?

Start by replaceing D100 and if that

doesn’t help then replace D314-D317

Yes

LCD

backlights turn

off for a short

while?

“NOKIA”

text stays on

display

>1min

Phone

turns off

exactly 3 5 secs

after boot

start?

DSP boot problems?

replace UPP WD2(D100)

No variant sw in the phone?

Flash ppm image to the phone

Yes

Check/replace N380 or

IMEI lost from D314, but not from D315.

In this case the IMEI cannot be rebuilt

before D315 has been erased/replaced.

->erase/replace D315

LFFS problems?

Format LFFS

If format didn’t help/work,

replace D316(and format LFFS)

UPP WD2 problems?

Replace D100

Yes

“contact

retailer”

message?

LFFS corrupted/not formatted or a selftest failure

Boot the phone to Local mode and check with Phoenix

FLS-4 users can format the LFFS with the “three finger trick”. Keep

buttons “answer”, “star” and “3” pressed simultaneously and press the

powerbutton, The three buttons can be released after text “Formatting”

appears on device screen. The trick works in normal mode. If

formatting doesn’t complete->replace D316

Actions required after a chip has been replaced:

D314 replaced->Reflash and rebuild IMEI

D315 replaced->Reflash, rebuild IMEI&simlocks

and retune RF&BB

D316 replaced->Reflash and Format LFFS

D317 replaced->Reflash

D100 replaced->Reflash

Yes

“Sim card

rejected”

message?

Simlocks active /corrupted, check with simlock test in Phoenix

If simlock test result is locked and detail data ..FFFF..

->Rebuild IMEI+simlocks also check/retune RF&BB settings

if detail data something else then check with correct sim

Yes

If the phone gets stuck on a reset loop or

if some error messages are shown it is

possible that some files on c-drive(LFFS)

are corrupt. This may be due to a faulty

flash component(D316), unsuppotrted

third party application installation or some

interrupt during the first device boot.

Format LFFS first. If the same failure re-

occurs->replace D316(requires reflash

and format). Ram(D312) fault could also

cause this king of behaviour, boot to local

and run RAM selftest - replace D312 if

selftest fails.

If the phone behaves differently each time

it is booted up it is probably due to a bad

UPP WD2(D100) ->replace D100, reflash

the phone and retest. Ram(D312) fault

could also cause this king of behaviour,

boot to local and run RAM selftest -

replace D312 if selftest fails.

Phone turns off

exactly 32secs

after boot

start?

IMEI lost from Both D314 and D315

Rebuild IMEI, check simlocks and

RF&BB tunings

not the above->change D100

Yes

Phone crashes

right after boot

finished(within

60secs)?

Yes

Might be something wrong with BT module

Boot the Phone to Local mode and run selftests

If ST_LPRF_AUDIO_LINES_TEST fails then first try to

reflash and if that doesn’t help replace BT module.

Format LFFS and if that

doesn’t help, reflash phone.

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: