PDA

View Full Version : Problems with KSIE 2...



byteforce
29-07-2003, 11:38 PM
Does anybody know what is the problem with my KSIE 2 which every time I unlock any Siemens it displays in log window this:

COMM_LoadBoots : selected phone family is 10
TTY_OpenCOMPort : opening COM1
COMM_IsBootRunning : bootcode does not seem to be running
COMM_LoadBoots : Waiting to power on the phone ...
COMM_LoadBoots : phone is powered on
COMM_LoadBoots : internal loader version is 00.02
COMM_LoadBoots : original IMEI is 35087470300448
SEC_BCDIMEIToNormalIMEI : invalid decoded IMEI
COMM_LoadBoots : flash IMEI (2121) is corrupt
COMM_LoadBoots : found SIEMENS MT50 lg1 v16 (1)
COMM_LoadBoots : flash ids are 002088CE [002088BA] - BA20
COMM_LoadBoots : phone ids are 4853767F [4853767F]

As you see in this output taken directly from KSIE 2 for every phone that I unlock it says the same invalid decoded IMEI and flash IMEI (2121) is corrupt. Is this a problem with me only or do you have the same problem, please help me
thanks

Norber73
30-07-2003, 08:13 AM
I have the same problem

Norber73
12-08-2003, 07:38 AM
up..

elko5
12-08-2003, 11:35 AM
I have too this problem.

algalad
22-08-2003, 10:33 PM
I've had problems with KSIE too, but not similar. I don't get even get contact with the phone! And this is a brand new cable that should be functional..

I just don't get further than this;

COMM_IsBootRunning : bootcode does not seem to be running
COMM_LoadBoots : Waiting to power on the phone ...
COMM_LoadBoots : phone is not powered on

Anyone who's encountered this? Or know how I can do anything about it? I cannot find any helpfiles regarding anything similar.

bmxfreak
28-08-2003, 05:19 AM
I've had problems with KSIE too, but not similar. I don't get even get contact with the phone! And this is a brand new cable that should be functional..

I just don't get further than this;

COMM_IsBootRunning : bootcode does not seem to be running
COMM_LoadBoots : Waiting to power on the phone ...
COMM_LoadBoots : phone is not powered on

Anyone who's encountered this? Or know how I can do anything about it? I cannot find any helpfiles regarding anything similar.

i get the same error, but with a different program (a java-activator...)