GSM-Forum - K800 Connection problem.

GSM-Forum (https://forum.gsmhosting.com/vbb/)

- Cruiser Suite (https://forum.gsmhosting.com/vbb/f569/)

- - K800 Connection problem. (https://forum.gsmhosting.com/vbb/f569/k800-connection-problem-634839/)

K800 Connection problem.

Trying to upgrade cid52 to cid53.

Code:

  21:31:23  SE Ultimate Unlocker v3.05 by Cruiser Team

  21:31:23  - Fast & Full - Unlock, Relock, Show codes, Sec.zone rebuild, EROM repair, CID change

  21:31:23  Initializing...

! 21:31:23  1. Please see the documentation first (the tab 'Info' or attached .pdf file)

! 21:31:23  2. Choose the phone model

! 21:31:23  3. Select the desired options

! 21:31:23  4. Please connect the phone either via USB while holding 2-5…

! 21:31:23  - or via a serial cable and double-click on it in the device list

  21:31:53  Selected phone: K800

  21:31:53  Connecting via Generic FTDI Cable (COM3)…

  21:31:53  Device driver version: 2.4.6.0

  21:31:53  Device driver date: 3-13-2008

  21:31:54  Connecting to the baseband CPU...

  21:31:54  Entering baseband CPU service mode...

  21:31:54  Detected chipset: DB2020

  21:31:54  Boot mode: ROM

  21:31:54  Sending loader...

E 21:31:55  Error: 0xA7AB9E28

E 21:31:55  Error data: 0xA7AB9E28 - 00000003:004513

E 21:31:55  Error: 0x82285E14

E 21:31:55  Error: 0xFF68B257

E 21:31:55  Error: 0x35A52603

E 21:31:55  Error: 0x45A1D7E8

E 21:31:55  Error: 0xD6E193F2

E 21:31:55  Failed!

! 21:31:55  To report errors right-click this window

Can anyone please explain errors. Have tried using DCU-60 and Com cable

marty

post an identify log by Cruiser 13.20.

for db2020 better u use dcu60. post the log as king filip said.

13.20 log. Any help in teaching, as to how to identify problem, will be appreciated.

System diagnostics passed.
Version 13.20 ready!
Do NOT connect the phone at this time!

[ --- Attach to Phone --- ]
Connecting via SEMC DCU-60...
Connect the phone while holding its C button!
USB connection established.
Baseband chip ID: 0x9900
Protocol version: 3.1
Booting via EROM...
Sony Ericsson phone detected.
Phone CID: 52
Phone color: Red
EROM version: R3A022
Trying CID52 recovery applet...
Sending applet prologue...
Sending applet body...
Time spent entering bootstrap: 0s
Initializing phone hardware...
Applet ID: 061220 1711 NPA4_CXC1329130_DB2020_...
Flash manufacturer: Intel
Flash ID: 0x897E
OTP Security Level: 1 (Retail)
OTP CID: 51
Phone CID: 52
Phone color: Red
Sending applet...
Applet ID: 061205 1523 HANCXC9876543210_DB2020...
Sending applet...
Applet ID: 061201 1314 HANCXC1329129_DB2020_FL...
RSA protection state cannot be determined for this CID.
Phone hardware initialized OK

With Com

[ --- Attach to Phone --- ]
Connecting via Fighter USB Cable...
Powering on the phone...
Baseband chip ID: 0x9900
Protocol version: 3.1
Baudrate = 460800Bd
Booting via ROM...
Trying CID53 recovery applet...
Sending applet prologue...
Sending applet body...
Time spent entering bootstrap: 2s
Initializing phone hardware...
Terminating threads...
All threads terminated.

The applet has intentionally turned the phone off!
Script error: Unspecified [13.20.90]

Quote:

Originally Posted by Phoneze (Post 3880418)

The applet has intentionally turned the phone off!
Script error: Unspecified [13.20.90]

Of course phone will be turned off - you must use DCU-60 cable with this phone. If you really need to upgrade the CID (I don't see any reason) then use DCU-60 cable with ultimate unlocker and post result.

Quote:

Originally Posted by ronandaly (Post 3882395)

Before posting, please read my question. First post is your answer.

Marty