Cruiser v9.72 Guide

2003-2006 Cruiser Team
Cruiser User's Guide

HelpAndManual_unregistered_evaluation_copy
Cruiser
powerful * flexible * reliable
by Cruiser Team
All rights reserved. No part of this work may be reproduced in any form or by any means - graphic, electronic, or
mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the
written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author assume no
responsibility for errors or omissions, or for damages resulting from the use of information contained in this document
or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be
liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or
indirectly by this document.
Cruiser User's Guide
Cruiser User's Guide I
Table of Contents
Foreword 0
Part I The Software
2
................................................................................................................................... 2 1 Introduction
................................................................................................................................... 2 2 History of Changes - Cruiser
................................................................................................................................... 22 3 History of Changes - Fighter/Interceptor
Part II Installing the Software
36
................................................................................................................................... 36 1 System Requirements
................................................................................................................................... 36 2 Installing the Software
................................................................................................................................... 41 3 Manual SmartCard Base Components Problem Resolution
................................................................................................................................... 43 4 Checking Drivers and OS Update Installation Success Under Windows 2000/XP
................................................................................................................................... 46 5 Checking Drivers and OS Update Installation Success Under Windows 9x/ME
................................................................................................................................... 50 6 Frequently Asked Questions
Part III Working with the Software
53
................................................................................................................................... 53 1 Getting Familiar with Main Window
................................................................................................................................... 54 2 Getting Familiar with Settings Window
......................................................................................................................................................... 54 Connections Page
......................................................................................................................................................... 56 Options Page
......................................................................................................................................................... 58 Language Page
......................................................................................................................................................... 59 Authentication Page
......................................................................................................................................................... 59 Licensing Page
................................................................................................................................... 61 3 Getting Familiar with Control Window
......................................................................................................................................................... 61 Primary Page
......................................................................................................................................................... 64 Flash Page (Old Phones)
......................................................................................................................................................... 66 Flash Page (New Phones)
......................................................................................................................................................... 67 File System Page
......................................................................................................................................................... 68 Locks Page
......................................................................................................................................................... 70 Security AVR Page
......................................................................................................................................................... 71 Security RSA Page
......................................................................................................................................................... 72 GDFS Page
......................................................................................................................................................... 74 Read Flash Page
......................................................................................................................................................... 75 Extras Page
......................................................................................................................................................... 76 IMEI Page
Part IV Phones ARM 2004/2005
79
................................................................................................................................... 80 1 Change LanguagePack
................................................................................................................................... 81 2 Change LanguagePack (red CID49, non TP)
................................................................................................................................... 82 3 Upgrade Firmware
................................................................................................................................... 82 4 Unlock
II Contents
................................................................................................................................... 82 5 Unlock Red CID49 Phones without TP
................................................................................................................................... 83 6 Unlock Red CID49 Phones via TP
................................................................................................................................... 83 7 Change IMEI
................................................................................................................................... 83 8 Enable GSM/3G Selection Menu
................................................................................................................................... 84 9 Repair Keypad not Working Problem
................................................................................................................................... 84 10 Extra Files
......................................................................................................................................................... 84 EROM Files with Color Conversion
......................................................................................................................................................... 84 FOTA User Agent Repair Files
................................................................................................................................... 85 11 Testpoint Pictures
......................................................................................................................................................... 85 K300/K500/K700 CID Testpoint
......................................................................................................................................................... 85 K600/K608/V600 CID Testpoint
......................................................................................................................................................... 87 V800/Z800 CID Testpoint
......................................................................................................................................................... 89 W550 CID Testpoint
......................................................................................................................................................... 90 W600 CID Testpoint
......................................................................................................................................................... 90 W900 CID Testpoint
Part V Phones ARM 2001/2003
94
................................................................................................................................... 94 1 Unlock by Using Codes
................................................................................................................................... 94 2 Repair J210
Part VI Phones AVR 2003
96
................................................................................................................................... 97 2 Unlock
................................................................................................................................... 97 3 Rebuild Security Zone
................................................................................................................................... 97 4 Decustomize
................................................................................................................................... 98 5 Repair T630 Network Problem
Part VII Phones AVR 2001
100
................................................................................................................................... 100 2 Unlock by Codes
................................................................................................................................... 100 3 Check Security Zone
................................................................................................................................... 101 5 Convert T68m to T68i
................................................................................................................................... 101 6 Decustomize T68m and T68i
................................................................................................................................... 102 7 Convert T300 to T310
Part VIII Phones AVR 1999/2000
104
Part IX SmartPhones 2003/2004
106
................................................................................................................................... 106 1 Change Languagepack and Upgrade Firmware
................................................................................................................................... 106 2 Unlock
................................................................................................................................... 107 3 Check Security Zone
Cruiser User's Guide III
................................................................................................................................... 107 5 Convert P900 to P910
................................................................................................................................... 108 6 How to Boot an Unbootable P900?
Part X SmartPhones 2000
111
................................................................................................................................... 111 1 Change Languagepack and Upgrade Firmware
................................................................................................................................... 111 2 Unlock
Part XI Phones CR 2001
113
................................................................................................................................... 113 1 Unlock
Part XII LG 3G Phones
115
................................................................................................................................... 115 1 Unlock
......................................................................................................................................................... 115 Unlock LG U8110
......................................................................................................................................................... 115 Unlock LG U8120
......................................................................................................................................................... 115 Unlock LG U813x/U8180/U83x0
......................................................................................................................................................... 116 Unlock LG U8550
................................................................................................................................... 116 2 Testpoint Pictures
......................................................................................................................................................... 116 LG U8xxx CID Testpoint
......................................................................................................................................................... 117 LG U8380 CID Testpoint
......................................................................................................................................................... 118 LG U8550 CID Testpoint
................................................................................................................................... 119 3 Special LG Codes
Part XIII Sharp 3G Phones
121
Part XIV Siemens Phones
123
................................................................................................................................... 123 1 Unlock Siemens C62
Part XV Language Packages
125
................................................................................................................................... 125 1 Language Acronyms
................................................................................................................................... 126 2 A3618 Language Packages
................................................................................................................................... 126 3 J200i/J200c Language Packages
................................................................................................................................... 128 6 K300i/K300c Language Packages
................................................................................................................................... 130 7 K500i/K500c/F500i/K508i/K506c Language Packages
................................................................................................................................... 132 8 K600i/K600c/K608i/V600i Language Packages
................................................................................................................................... 133 9 K700i/K700c Language Packages
................................................................................................................................... 135 10 K750i/K750c/D750i Language Packages
................................................................................................................................... 136 11 P800/P802 Language Packages
................................................................................................................................... 137 12 P900/P907/P908 Language Packages
IV Contents
................................................................................................................................... 138 13 P910i/P910c/P910a Language Packages
................................................................................................................................... 138 14 R310s/R310sc Language Packages
................................................................................................................................... 139 15 R320s/R320sc Language Packages
................................................................................................................................... 139 16 R380s/R380sc/R380e Language Packages
................................................................................................................................... 140 17 R520m/R520mc Language Packages
................................................................................................................................... 140 18 R600 Language Packages
................................................................................................................................... 141 19 S700i/S700c Language Packages
................................................................................................................................... 142 20 S710a Language Packages
................................................................................................................................... 143 21 T39m/T39mc Language Packages
................................................................................................................................... 143 22 T65s/T65sc Language Packages
................................................................................................................................... 144 23 T66 Language Packages
................................................................................................................................... 145 24 T68m/T68mc Language Packages
................................................................................................................................... 145 25 T68i/T68ie Language Packages
................................................................................................................................... 146 26 T100/T100c/T102/T105/T106 Language Packages
................................................................................................................................... 147 27 T200/T202 Language Packages
................................................................................................................................... 147 28 T226/T230/T237/T238 Language Packages
................................................................................................................................... 148 29 T290i/T290a/T290c Language Packages
................................................................................................................................... 148 30 T300/T300c/T302/T306 Language Packages
................................................................................................................................... 149 31 T310/T310c/T312/T316 Language Packages
................................................................................................................................... 150 32 T600 Language Packages
................................................................................................................................... 150 33 T610/T616/T618 Language Packages
................................................................................................................................... 152 34 T628/T630/T637 Language Packages
................................................................................................................................... 153 35 V800/V802SE Language Packages
................................................................................................................................... 153 36 W550i/W550c Language Packages
................................................................................................................................... 154 37 W600i Language Packages
................................................................................................................................... 157 41 Z200/Z208 Language Packages
................................................................................................................................... 157 42 Z500a/Z500i/Z500c Language Packages
................................................................................................................................... 157 43 Z520i/Z520c Language Packages
................................................................................................................................... 159 45 Z600/Z608 Language Packages
Part XVI Additional Information
163
................................................................................................................................... 163 1 SE/LG/Sharp/Siemens Cable Pinouts
................................................................................................................................... 165 2 CID Information
Cruiser User's Guide V
Index 0
Part
I
2 Cruiser User's Guide
1 The Software
1.1 Introduction
Cruiser is ultimate, the most advanced and the most flexible service tool for
maintaining of almost all existing Ericsson and Sony Ericsson GSM phones.
Cruiser is World's First standalone service tool for Ericsson and Sony Ericsson
GSM phones that works without internet connection and uses a special USB box that
is especially designed for achieving the highest possible communication rates
while maintaining maximum reliability. No more obsolete LPT or COM ports
required!
Cruiser perfectly matches your needs. You can select which software edition you
need - either Standard or Professional. The Professional edition can handle up to 16
phones simultaneously. Perfect support you can rely on, new features coming
every month, instant access to the latest flash files!
We believe you will experience the passion of using Cruiser. You are worth using it!
Yours,
Cruiser Team.
All trademarks and registered trademarks appearing in this user manual are the
property of their respective owners.
1.2 History of Changes - Cruiser
Version 9.72 (30th May 2006, 88th release):
Added built-in system diagnostics.
Installer updated.
Updated TAC list for W700i and Z520a.
Version 9.71 (28th May 2006):
Released support for flashing files in MBN and FBN file format.
Updated built-in customizations.
Updated TAC list for J230i, W800i and Z300a.
Several applets were updated.
Minor change to UI.
Enhanced communication handshake again.
Updated TAC list for K300i, K700i, Z520a and Z600i.
Version 9.68 (21st May 2006):
Fixed a bug causing flash failure on some prototype phones.
The Repair certificate option was not enabled for CID49 empty-boards by a
mistake.
3 The Software
Version 9.67 (21st May 2006):
Added support for W300 phones. They are basically the same as W810 phones.
Added support for W700 phones. They are basically the same as K750/W800
phones.
Added support for correct handling of red CID49 Z520 phones with locked-down
EROM area.
Added support for Z525 phones.
Updated TAC list for K510i, V600i and Z300i.
Updated built-in customizations for W810, W900, Z530.
Fixed a bug in loading AVR flash files for A1018, T10, T18, T28, R320 and R380
phones.
Added several helpful hints to Cruiser code.
Minor updates to flasher code.
Slightly increased flashing speed for some phones.
Updated TAC list for J220i.
Version 9.64 (14th May 2006, 80th release):
Updated communication routines. Enhanced communication handshake in some
cases.
Increased timeout when defeating RSA protection of red CID49 phones.
Updated TAC list for LG U8130C.
Added experimental support for J220 and J230 phones.
We have decided to release separate Firmware Restoral installer.
Added Firmware restore button to the Security page. It automatically looks for
proper firmware restoral file and flashes it to the phone.
Help file updated.
Fixed Z300 booting problem.
Added support for K510 phones.
Added support for reading unlock/relock codes from Z300.
Added support for reading flash from Z300.
Updated TAC list for Z530i.
Fixed applet selection problem. Should fix the Sending applet problem.
Updated TAC list for T230i, T290i, T630, T637, V800, W800i, W810i, Z520i and LG
U8138C.
Fixed non-English language strings.
Version 9.52 (8th May 2006, gamma version):
Full support for downloading files from W810 and Z530 phones.
Help file slightly updated - more to come soon.
Version 9.51 (8th May 2006, beta version):
Some operations made faster.
Increased flasher verbosity.
Fixed minor W900-related bug.
Version 9.50 (7th May 2006, alpha version):
Added functionality for non-TP flashing red CID49 phones (including W810 and
Z530) with locked-down EROM area.
Added functionality for non-TP unlocking/relocking red CID49 phones (including
W810 and Z530) with locked-down EROM area.
Added non-TP FS functionality for red CID49 phones (including W810 and Z530)
with locked-down EROM area.
Added support for non-TP IMEI change in red CID49 phones with locked-down
EROM area.
Added support for converting red CID49 K750, W800 and Z520 phones with
unlocked EROM area to brown CID49.
Implemented Unlock RSA function for red CID49 phones.
The Repair certificate function is now disabled for red CID49 phones by default.
There is a way to enable it, though its use is deprecated.
Added support for automatic firmware identification in red CID49 phones.
Some patchers were analyzing FOTA area by a mistake (i.e. not ignoring it) and
therefore not functioning properly for some phone models.
Several applets updated.
Some built-in customizations were updated.
Version 9.23 (5th March 2006, 70th release):
Installer updated.
Updated TAC list for T290a, K300a, K750i, LG U8120 and Sharp V703SHF.
Swedish language strings updated again.
Version 9.22 (1st March 2006, stable release):
Installer updated.
Debug Log functionality updated.
Minor changes to boot code.
Slightly increased flasher verbosity.
Swedish language strings updated.
Slovak language strings updated.
Version 9.22 (1st March 2006, stable release):
Installer updated.
Debug Log functionality updated.
Minor changes to boot code.
Slightly increased flasher verbosity.
Swedish language strings updated.
Slovak language strings updated.
Version 9.21 (26th February 2006, stable release):
5 The Software
Installer updated.
EROM and FOTA files moved out from the help file.
From now on, the Format GDFS function will be unavailable. It was abused too
often.
From now on, the Flash ARM function will be unavailable in certificate recovery
mode.
Help file updated.
User manual in PDF file format released.
Version 9.20 (25th February 2006):
Minor changes to EROM area flashing code.
Updated K750/W550/W800/W900/Z520 built-in customizations.
Fixed a bug regarding Create file package option.
Minor changes to booting code.
Open/save dialog code updated.
Version 9.18 (24th February 2006, gamma version):
Restored the ability to change IMEI on Sharp 3G phones. It was dependent on the
Unlock RSA function which was removed for these phones recently.
Increased verbosity for operator's mistakes.
Changes in TP-handling code.
Version 9.17 (23rd February 2006, beta version):
Updated langpack description for W900.
Fixed bug in GDFS access code for phones with baseband IDs 0x8000 and 0x8040.
Reduced importance of Unlock RSA function. It should not be needed for brown
and blue phones anymore.
Version 9.16 (22nd February 2006, alpha version):
Minor changes in RSA phone booting and shutdown code.
Updated TAC list for J210i.
Redundancy decreased again.
Other minor bugfixes.
Note: It is recommended to fill all SE emptyboards regardless of their phone type
by brown CID49 certificate via CID49 recovery boot and certificate repair.
Version 9.15 (22nd February 2006):
Added support for unlocking several new U8180 firmwares.
Updated ARM 2004/2005 FAQ help-file section.
Added FAQ help-file section for Sharp 3G phones.
Updated LG U8110/U8120 unlock procedure descriptions. Thanks to Aamir_Zia and
DonaldDuck69.
Updated LG U813x/U8180/U83x0 unlock procedure descriptions.
Fixed bug in langpack description for K700.
Added support for unlocking several new U8330 firmwares.
Updated TAC list for Siemens C62.
Fixed minor T610 bug manifesting itself on some Windows versions.
Updated LG U8550 block list combo-box for flash reading.
Version 9.13 (19th February 2006, 60th release):
Fixed AVR flashing bug from version 9.10.
Updated TAC list for J300i and K300i.
New firmware patcher engine implemented. (Applied to LG for now, Sharp and SE
later.)
Added support for patching newer LG 3G firmwares.
Increased patcher timeout in version 9.13a.
Version 9.12 (16th February 2006, beta version):
Fixed minor RSA unlock bug.
Version 9.11 (16th February 2006, beta version):
Flasher modules updated again.
Version 9.10 (16th February 2006, alpha version):
It is possible to open more flash files at once.
Note: Just hold the Ctrl key while selecting files.
It is possible to customize filesystem automatically right after flashing raw
FS.
All flasher modules were updated.
Minor changes in CID54 configuration analysis code.
Modified default state of Extended config options.
Phone Firmware Backup (.pfb) files created in this version are not backwards
compatible (i.e. should not be used with previous versions).
The Lock to network option should not be enabled for red CID41/42 phones.
Fixed minor FS customization issue.
Fixed minor GDFS/FS bug from version 9.00.
W550 (new HW) testpoint picture updated.
Updated TAC list for T290a, K300i and K700i.
Communication code updated.
Startup code modified.
A few memory leaks removed.
Version 9.03 (9th February 2006, stable release):
Added special flashing options for new ARM phones.
Fixed RSA AVR booting bug from version 9.00.
Fixed minor security zone creation bug.
Updated V/K60x testpoint pictures.
Version 9.02 (8th February 2006, test version):
Fixed GDFS and FS access bug from version 9.00.
Fixed brown/blue CID37 booting bug from version 9.00.
Fixed Sharp 3G flashing bug from version 9.00.
Implemented LG U8550 red CID54 unlocking without using testpoint.
Fixed a bug in flashing raw FS files via EPI USB.
Fixed slow-flashing bug for ST Microelectronics chips.
Fixed occassional Sharp 3G flashing bug.
Changes in Sharp 3G functionality.
7 The Software
Changes in LG 3G functionality.
Enabled flash reading from new ARM phones for all users.
Added full support for Blue CID49 phones with baseband chip ID 0x7100.
Some operations on Blue and Brown phones were made faster.
Added support for TMS cable autodetection.
Fixed bug in Disable/Enable OTP IMEI check function for new ARM phones.
The previous code was excessively optimized
Fixed minor J300 file selection issue.
Updated TAC list for Z300i, Z300a and K750i.
Redundancy decreased again.
Version 8.11 (30th January 2006, stable release):
Released flash file for unlocking LG U8550. In this version it has to be flashed via
TP.
To repair phones damaged by other tools tick Overwrite flash certificate option.
It should be no more necessary to unlock RSA before unlocking new Sharp phones
via patching.
Installer updated.
Fixed a bug regarding P910a phones.
Updated TAC list for T630i and Sharp V703SH.
Several prototype-related updates.
Built-in customizations updated.
Version 8.10 (22nd January 2006, beta version):
Ongoing software architectural changes.
Redundancy decreased.
Added support for programming W810/Cleo/Mulan empty-boards.
Downloading files from K750/W800/Z520 enabled for all users.
Downloading files from W550/W600 enabled for all users.
Downloading files from W900 enabled for all users.
Updated TAC list for T230i and J200i.
The 'USB interference occurred' message should appear less frequently when using
nonconforming cables.
Added support for TMS cable.
Thrown away the old, sporadically working, help engine.
Updated many texts in Cruiser help file. Thanks to Muppet.
Help file completely reorganized. Now it seems to be more topologically correct.
Help file screenshots updated, descriptions updated too.
Help file EROM-files updated.
W900i testpoint picture included to the help file.
The LangPack info button should be reliable now.
The F1 key should reliably invoke the relevant help topic. It works in the Settings
window too.
Added support for CID19 EROM recovery.
Debug Log functionality modified so that it can be used with Windows Notepad.
Security I renamed to Security AVR.
Built-in customizations updated.
Version 8.00 (14th January 2006, alpha version, 50th release):
Implemented red CID49 unlocking and flashing without using a testpoint.
The real standalone way, no EMMA smartcard usage, world's first!
Supported phones are W550i/c, W600i, K600i/c, K608i and V600i. More models
coming shortly.
Loaders updated.
Version 7.16 (13th January 2006, beta version):
Installer updated. New cable driver version (2176) included.
Built-in customizations updated. Experimental FOTA support added.
Some GDFS-related changes.
Changes in unlock functionality.
Slightly changed functionality of the phone type filter.
Added support for two new flash IDs.
RSA configuration analysis code updated again.
Loaders were updated.
Minor architectural changes.
Allowed to change language to Chinese/Malay for non-Chinese and non-Malay card
users.
Version 7.15 (1st January 2006, beta version):
Several communication scripts updated.
Updated TAC list for W900i, W800c, W550i, Z520i, Z520c, Z520a, K600i, K608i,
J210i, T230i and T290a.
LG U8380 testpoint included to the help file.
Added an option to write replacement unit customization.
Btw, happy new year!
Version 7.14 (31st December 2005, gamma version):
Another K608i testpoint picture included to the help file.
J210 World Generic decustomization has been released.
J210 repair file has been released. Remember to recalculate CRCs (the phone
should be attached as J200).
Repair EROM functionality updated to reflect W900 phones. Brown CID49 phones
are supported now.
Brown CID49 FOTA (Flash-Over-The-Air) repair files for W550, W600, S600 and
W900 have been added to the help file.
Some loaders were updated.
Note: If your phone freezes right after powering on, try direct unlocking it.
Version 7.13 (29th December 2005, beta version):
Cruiser is now available in English, Chinese, Czech, Greek, Indonesian, Malay,
Polish, Russian, Slovak and Swedish languages.
Many thanks to 9Volto for preparing Greek translation.
Added Language page to the Settings window. This page is not shown for
Chinese, Malay and Indonesian cards.
Updated TAC list for T290i, K750i, Z520a, W600i, LG U8360, Siemens C62.
GDFS configuration bug fixed for Z520a. No need to attach them as Z520i/c
anymore.
Implemented several FS-related functions for brown CID49 W550/W600 phones.
Updated W600i built-in customizations.
New brown CID49 to red CID49 conversion EROM file for W550/W600 phones has
been included to the help file.
Some prototype-related updates.
Version 7.12 (22nd December 2005, alpha version):
9 The Software
Fixed EROM repair issue for brown CID49 K608.
Updated W900i langpack info.
Some changes to applet upload strategies.
Version 7.11 (3rd December 2005, beta version):
Added support for flashing CID54 phones (LG U8550) without using testpoint.
RSA configuration analysis code slightly updated to reflect CID54-related changes.
Increased robustness of RSA configuration analysis code to prevent potential
crashes on invalid flash content.
Added alternate method of replacing RSA certificates.
Fixed one bug in low-level communication code.
Fixed small bug in Repair certificate function.
Fixed one previously introduced bug in GDFS access for P910.
Updated K750i built-in customizations.
Updated TAC list for K300i, K700i, T290i, LG U8330 and Sharp V903SH.
Version 7.10 (22nd November 2005, beta version):
From now on it is possible to download files from FS to special archive files in .cfp
(Cruiser File Package) format.
From now on it is possible to upload .cfp package content to phone FS.
An LG U8550 testpoint picture added to the help file.
Fixed '5E0W' customization bug from version 7.00.
It is now possible to enable GSM/3G selection menu in SE 3G phones (K600,
K608,...).
Fixed some bugs in Polish translation.
The Customize FS button was moved to Flash ARM page.
Fixed occassional K600/K608/W900 booting bug.
Updated W550i/W550c/W600i langpack info.
Updated TAC list for K700i.
Version 7.00 (17th November 2005, alpha version):
Added support for fast direct unlock of Sharp V703SH/V903SH/SX313/
SX833 phones.
Anyway, this is the fastest way of unlocking these phones available on the
market.
The direct OTP/GDFS check enable/disable function should be much more generic -
now it handles Sharp V703SH/V903SH/SX313/SX833 firmwares too.
Support for unlocking any-CID ARM phones with baseband chip IDs 0x7000,
0x7100, 0x8000 and 0x8040. Even W900 phones.
Support for flashing any-CID ARM phones with baseband chip IDs 0x7000, 0x7100,
0x8000 and 0x8040 without changing primary certificate.
New K600/K608 testpoint picture added to the help file.
A W550 testpoint picture added to the help file.
A W600 testpoint picture added to the help file.
The fast LG 3G unlocking functionality via firmware patching was extended to
support some LG U8550 firmwares.
Added support for locking OTP area in LG 3G and Sharp 3G empty-boards.
Added an option to write new Bluetooth MAC address to RSA-protected ARM-based
SE phones. It is available among Modify GDFS options.
RSA boot options have been modified.
Certificate recovery function updated.
Repair EROM functionality updated to reflect W550 and W600 phones. Both brown
CID49 and red CID49 phones are supported now.
Fixed minor bug in RSA configuration analysis code.
Updated Customize FS function.
Updated TAC list for W600i, J300a, K750i and LG U8550.
Some changes in Chinese translation.
Version 6.10 (5th November 2005, stable release):
Added support for unlocking J210 phones.
The Recalc DCRCs button was enabled for J210 by a mistake.
Released Sharp V703SH to SX313 conversion flash file.
Notice: Please prefer using reading codes to direct unlocking when possible.
Version 6.05 (28th October 2005, beta version, 40th release):
W550 built-in customizations list updated.
Fixed an issue with unlocking some Siemens C62 phones.
Fixed a bug in direct OTP/GDFS check disable/enable function regarding LG 3G
phones with old firmwares.
Version 6.04 (26th October 2005, beta version):
Added support for GDFS identity changing for CID17 LG 3G phones. (Not available
in Legal Edition)
Added support for GDFS identity changing for CID41 and CID42 LG 3G phones via
testpoint. (Not available in Legal Edition)
Added support for GDFS identity changing for CID24 Sharp 3G phones. (Not
available in Legal Edition)
Added fast direct OTP/GDFS check disable/enable function for CID17, CID41 and
CID42 LG 3G phones and for CID24 Sharp 3G phones. (Not available in Legal
Edition)
Note: For LG U8360 and LG U8380 it is necessary to unlock phone via patching.
Added support for explicit restoring of GDFS identity.
Fixed a flashing bug that caused U8380 v10A firmwares to be unlocked incorrectly.
Another change to RSA protection unlocking code.
Slightly increased verbosity of GDFS access initialization error handling code.
K600/K608 testpoint pictures updated.
Minor change related to unlocking RSA protection of OTP CID29 phones with
baseband chip IDs 0x8000 and 0x8040.
Updated direct OTP/GDFS check removal code to support older firmware versions.
Slightly increased verbosity of applet error handling code.
Added function for fast restoring firmware OTP/GDFS check.
Added support for flashing .pfb (Partial Firmware Backup) files that are created
before every partial ARM firmware modification (direct LG unlocking or OTP/GDFS
check disabling/enabling).
Fixed a bug in Polish translation.
Fixed an issue with Sharp V703SH phone type autodetection.
Fixed a bug regarding flashing Sharp V903SH phones by certain flash files.
11 The Software
Another minor updates.
Installer updated.
Fixed an issue with C62.
Added boot support for Siemens C62 (CID27).
Added support for flashing original SSW files into AVR-based phones (e.g. Siemens
C62).
Added support for direct unlocking Siemens C62 v25, v26, v27 and v28. Many
thanks to www.PolPhone.com.
Added support for relocking Siemens C62 v25, v26, v27 and v28. Many thanks to
www.PolPhone.com.
Z520 built-in customizations list updated.
Other changes in built-in customizations.
Added GDFS identity changing for ARM phones with baseband chip IDs 0x7000,
0x7100, 0x8000 and 0x8040. (Not available in Legal Edition)
Added fast direct OTP/GDFS check removal function for new ARM SE phones. (Not
available in Legal Edition)
Minor change in file download functionality. It should copy empty directories too.
Updated TAC list for W550i, Z520i, W800i, K300i, K700i, Sharp V703SH and
V903SH.
Removed possibility to change CID41 and CID42 phones to brown color due to a
safety reason.
Added boot support for J210.
Added support for flashing J210.
T9 dictionaries removal has been separated from language files removal function.
Added displaying of flash certificate name while booting new ARM phones.
Internal FW database extended.
The Write to OTP function now allows ordinary users to choose from more CIDs.
Released Sharp V903SH testmode flash files.
Added boot support for CID49 phones with baseband chip IDs 0x7000 and 0x7100
(K608, etc).
Added Direct unlock for Brown CID49 phones.
Added Lock to network for Brown CID49 phones.
Added Reading codes from Brown CID49 phones.
Added Save security for Brown CID49 phones.
Added Restore security for Brown CID49 phones.
Added support for booting CID49 phones (red and blue via TP for now).
Added support for flashing Brown CID49 phones.
Added support for flashing Red/Blue CID49 phones via TP.
Added support for changing RSA certificate color of CID49 phones (by using TP for
now).
A brown CID49 to red CID49 conversion file for K608 has been included to help. It
is not necessary to reflash phone firmware after using this file.
Added fast LG 3G unlocking functionality via firmware patching. Automatically saves
a firmware backup file to the Data\ARM flash backups folder. Supported are
these models: U8130, U8138, U8180, U8330, U8360 and U8380.
Possibility to upgrade LG U8138 to U8180.
Possibility to upgrade LG U8130 to U8330.
Czech language strings updated.
Polish language strings updated.
Help file updated - added Siemens C62 pinout, some LG 3G secret codes, etc.
Version 5.02 (1st September 2005, stable release):
Important notice: Do not attempt to convert OTP CID37 phones to any
other CID!
Otherwise you won't be able to boot the phone anymore. Cruiser does not allow you
to do that, but other software may.
Cruiser is now available in English, Chinese, Czech, Indonesian, Malay, Polish,
Russian, Slovak and Swedish languages.
Fixed one chicken-and-egg situation with Unlock RSA.
Fixed one FS-access bug regarding K750/W800 phones that was introduced with
version 5.00.
From now on the Format GDFS option is protected by a password 'KILL THE
PHONE'.
Version 5.01 (31st August 2005):
Updated TAC list for W800i and J210i.
Fixed an OTP IMEI (non-)insertion bug in the Security I (AVR) page.
RSA unlocking functionality slightly modified.
Version 5.00 (30th August 2005, beta version):
Added function for easier replacing of flash certificates. A list of compatible
certificates is displayed in the combo box located below the Replace certificate
button.
Note: Latest EROMs require you to restore the flash certificate back to its original
state to allow the phone to be turned on.
Updated TAC list for K750i, W800c, V600i, K608i, K600c, J300i, J300c, T290i and
T290c.
W800 built-in customizations list updated.
Minor CID17-related changes.
Write bandlock functionality slightly modified.
Added theoretical support for old S988 prototypes.
Added support for flashing LG U8360.
Added support for flashing Sharp V903SH.
The user interface has been modified.
Flash BT function has been separated from Flash ARM.
Added reading codes for CID37 phones.
Recover Certificate function now supports CID37 phones.
Note: An attempt to start a CID37 phone containing working firmware in a recovery
mode will fail.
Implemented Unlock RSA function for CID37 phones.
The Unlock RSA button should not be enabled in recovery mode.
Flasher functionality modified for CID36 and CID37.
Added Customize FS function for CID37.
Added Turn camera sound on/off function for CID37.
Added Modify GDFS functionality for CID37.
Added Write to GDFS functionality for CID37.
Added Save security for CID37.
Added Restore security for CID37.
13 The Software
Added Direct unlock for CID37.
Added Lock to network for CID37.
Added Read GDFS zones for CID37.
Added Upload files to FS for CID37.
Added Language operations for CID37.
Added Write to security zone for CID37.
Lock OTP area now supports CID37.
Added Repair EROM function for CID37 phones.
Note: Reflash the main firmware when using this function for brown CID37.
Added Format GDFS function.
Added Remove RSA unlock traces function. It is located among Modify GDFS
options.
Unused code removed.
Help file slightly updated.
Version 4.30 (14th July 2005, stable release):
K600/V600 built-in customizations list updated.
K600/V600 flash file handling improved.
Help file updated - K600/V600 language pack info added.
Added support for direct handling of blue CID36 phones (recovery mode not
required anymore).
Minor changes in code accessing the FS of brown CID36 phones.
Increased verbosity of GDFS error handling code.
Conversion to brown CID36 for baseband chip IDs 0x8000 and 0x8040 has been
optimized.
Conversion to brown CID36 for baseband chip IDs 0x7000 and 0x7100 has been
optimized.
Introduced detection of data bus interferences for LG phones.
About-box information slightly updated. Now 170 phone types are supported.
Help file CID information updated.
Added Special Files topic to the Additional Info section of the help file.
Open-flash-file dialog boxes accept .erom1 and .erom2 file types where
appropriate.
The Force RSA recovery combo-box now displays manufacturer names too.
Minor changes in UI.
Version 4.24 (10th July 2005, beta version, 30th release):
Allowed direct flashing of normal flashes in recovery mode for CID41 and CID42.
Conversion to brown CID36 requires phone analysis performed. Otherwise it
displays an error message.
Minor changes in K600/V600 functionality.
Added support for S600i/S600c/W600a.
Some applets updated.
Booting code modified.
Flashing code modified.
Flash file open dialog code updated.
File-system functionality for brown CID36 phones reenabled.
Fixed some issues with prototype CID36 phones.
Fixed a bug in reset life-timer functionality.
Updated TAC list for LG U8380.
The Turn off phone button should be enabled for unidentified new ARM phones.
The Repair certificate button was disabled in some cases.
Camera focus sound is now affected by the Camera sound on/off function too.
Added support for flashing brown CID19 phones (EMP).
Added phone type filter.
Version 4.20 (29th June 2005):
Added support for converting K750 phones to W800.
Added support for Z520i/Z520c.
Increased safety when converting red CID36 phones to brown CID36.
Sharp 3G flashing speed via Fighter/Cruiser cable slightly improved.
The main executable and help file are now stored outside the installer.
Fixed one bug introduced in the previous version.
Version 4.14 (23rd June 2005):
Installer updated.
It is possible to use Z800 files for V800/V802SE phones directly.
Reading phone certificate caused problems while flashing composite flash files via
EPI USB.
Version 4.13 (21st June 2005):
Added support for unlocking LG U8330 and U8180 without testpoint via patched
flashes.
Added support for cross-CID flashing of CID41 and CID42 phones without testpoint.
Minor change in UI.
Minor change in Upload files to FS function.
K750i/D750i language pack info updated again.
New brown CID36 to red CID36 conversion file for K750/D750/W800 has been
included to help. It is not necessary to reflash phone firmware after using this file.
Flash file format modified.
K750i/D750i built-in customizations list updated.
K750i/D750i language pack info updated.
Built-in EROM recovery function for K750/D750/W800 phones improved.
It should be possible to flash more phones at once via EPI USB too.
Chinese language strings updated.
Help file extended by a description of CID36 phone operations.
Brown CID36 to red CID36 conversion file for K750/D750/W800 has been included
to help. It is not necessary to reflash phone firmware after using this file.
Version 4.10 (13th June 2005, beta version):
Added support for red CID36 to brown conversion (without testpoint, of
course).
K750/D750/W800 red CID36 phones are now fully supported.
Added Unlock RSA function for red CID36 and CID24 phones.
Added Upload SFA function for red CID36 phones.
Added Write raw FS function for red CID36 phones.
Added Customize FS function for red CID36 phones.
Added Language operations function for red CID36 phones.
15 The Software
Added Upload files to FS function for red CID36 phones.
Added Camera sound on/off function for red CID36 phones.
Added Save security function for red CID36 phones.
Added Restore security function for red CID36 phones.
Added Read GDFS zones function for red CID36 phones.
Added Modify GDFS function for red CID36 phones.
Added Write to GDFS from file function for red CID36 phones.
Added support for backup of battery calibration zone of new ARM phones.
Added support for backup of display calibration zone of new ARM phones.
Added support for backup of audio calibration zone of new ARM phones.
Added support for backup of radio calibration zone of new ARM phones.
Built-in customizations list updated and extended by J300i data.
Installer updated. EPI USB driver included to allow faster flashing of LG 3G, Sharp
3G and V800/Z800/Z1010 phones.
Added an option to flash faster via EPI USB.
Added support for EROM recovery in red/brown CID36 K750/D750/W800.
A Sharp V801SH GDFS related issue fixed.
Updated TAC list for LG U8330.
Added experimental support for Sharp V801SH.
Updated applet for Sharp 3G phones.
Added support for flash ID 0x890F.
Added support for flash ID 0x8910.
Fixed a bug causing some buttons to be disabled for LG phones under certain
circumstances.
Sharp connector picture updated.
Version 4.00 (7th June 2005, 20th release):
Released pinout for Sharp V802SH and V902SH phones.
Added Direct unlock support for Sharp 3G CID24 phones.
Added Lock to net support for Sharp 3G CID24 phones.
Added Save security and Restore security support for Sharp 3G CID24 phones.
Force RSA recovery options now include CID24, CID41 and CID42.
Added displaying of flash manufacturer when booting new ARM phones.
Added reading codes from CID41 (LG U8180) and CID42 phones via testpoint.
Cross-CID flashing extended to CID17/CID41/CID42. Cruiser automatically patches
flash files by replacing their RSA certificate.
Usage: it is possible to flash U8180 by U8138 firmware.
Fixed an issue with flashing R600.
Added support for EROM recovery in very rare brown CID16 V800/Z800.
Updated TAC list for T610, F500i, K506c, K700i, Z800i, K750i, K750c and D750i.
Help file updated.
Version 3.93 (3rd June 2005):
V800/Z800 CID testpoint released.
EMMA smartcard mutex is now released correctly.
Flash file open dialog code updated.
Due to many requests, Direct unlock and Read codes work now much faster on
new ARM phones.
Cruiser closing issue fixed.
Updated TAC list for Z200, Z600, Z608 and LG U8100.
Version 3.92 (1st June 2005, gamma version):
K300 CID testpoint released.
Built-in customizations list expanded.
Fixed an issue with handling Z800 red CID36.
Fixed a bug in EROM repair for red CID29 V800/Z800.
Fixed a bug causing the Direct unlock to be disabled for J200/Z200/T100/A3618
phones.
Repair EROM shall not be enabled in certain situations.
LG unlocking functionality was disabled by a mistake.
A baudrate-related modification regarding LG phones.
Version 3.91 (1st June 2005, beta version):
Reworked unlocking/relocking of red CID36 phones via testpoint.
Added a button for conversion from red CID36 to brown CID36 (via testpoint).
Version 3.90 (31st May 2005, beta version):
Added support for full security zone rebuild of R520/T39/T65 phones (i.e.
phones with baseband chip ID 0x5C05 and 0x5C06). Throughout last 4
years nobody else was able to manage it. It appeared to be almost
impossible. But henceforth you can repair 4 locks closed or any other
software-related problem.
The Redirect SCRC check to zone II checkbox has been removed.
The Security II page was removed as it has been made superfluous by extending
the Security I page functionality to R520/T39/T65 phones.
Updated TAC list for LG U8180, K500i, K300i, V802SH and V902SH.
Installer updated. It enables displaying hidden/nonpresent devices in Device
Manager under Windows 2000/XP.
Once again, some baudrate-related modifications.
Malay and Slovak language strings updated.
Direct unlock button was enabled for all LG 3G phones by a mistake. Use read
codes instead.
Debug Log feature released to public.
Help file updated - added info on how to boot unbootable P900 smartphones.
An error message is now shown when trying to boot an incorrectly upgraded P900
to a P910. Such phone has to be booted using a testpoint connected to GND.
Boot code modified.
A few changes in configuration analysis code.
Minor modifications to the Settings window, mostly EMMA smartcard related. Be
sure to enter correct PIN for your EMMA smartcard.
Added a possibility to boot AVR based phones starting from R520m by means of an
EMMA smartcard.
Added support for changing phone languages in red CID36 phones (J300/K300/
Z800/K750/W800/K600/V600/new K700/new V800) by means of an EMMA II
smartcard.
Added full support for brown CID36 phones (J300/K300/Z800/K750/
W800/K600/V600/new K700/new V800).
Now it is possible to specify which recovery applet (for which CID) to use when
booting the phone. This feature is intended to allow RSA unlocking via testpoint.
17 The Software
Added function to repair "no network" problem on new T630 phones that have been
damaged by downgrading firmware.
A few memory leaks removed.
Emptyboard programming of new ARM phones (including J300/K300/Z800/K750/
W800/K600/V600) released for all users.
Added function Repair certificate to simplify phone revival on flash failure.
Added function Repair EROM to simplify EROM area repair in red and brown
phones of CID29 and CID36.
Added detection of CID42 LG 3G phones.
Added support for flashing red LG U8xxx with CID42.
Fixed an issue causing R380 PDA-part boot problem.
Added experimental support for booting, flashing and cloning Hedvig prototypes.
The button-enabling system has been modified to reflect smartcard presence and
various CID options.
Corrected one progressbar update related issue.
Some obsolete flashing options removed.
Version 3.82 (14th April 2005):
Booting baudrate limited to 230400Bd for older phones. Previously the limit was set
to 115200Bd, but the version 3.80 removed the boot baudrate constraint, causing
occassional boot problems.
Removed File System tab bug from version 3.81.
Fixed two issues related to built-in customizations.
Cruiser is now available in English, Chinese, Indonesian, Malay, Polish, Russian,
Slovak and Swedish languages.
Now it is possible to put red flashes into brown and blue phones of CID16, CID17
and CID29 without converting them to red. The phone certificate is not affected.
Added full support for cross-CID flashing. It is possible to flash CID16, CID17 and
CID29 phones by any-CID flashes. The phone CID and color are not affected.
Added support for flashing red and blue LG U81xx of CID17 via simple serial cable
too.
Added support for flashing red LG U81xx of CID41.
Baudrate subsystem completely refactored.
Baudrate page from the Settings window was replaced by the Limit baudrate
combobox in the Primary page of Control window.
Baudrates used for flashing PDA part of P80x/P910 are limited to 460800Bd when
using USB cables that are not enhanced by adding two resistors. This is not related
to DSS-20 nor DSS-25.
Installer updated - minor Windows 98 issue fixed. An error message might have
been displayed when no error occurred.
Customize FS functionality slightly modified.
CS applet communication made more verbose.
Available free space is now displayed before writing user files to the phone.
Help file updated.
Version 3.70 (8th April 2005, gamma version):
This version was not meant to be released this early, the only reason was
adding support for LG(R) phones. In case of any problems, use version 3.40
instead.
Known limitation: It is not possible to flash LG phones via standard serial cable.
This will be fixed as soon as possible.
Installer updated - occassional Windows XP SmartCard service install issue fixed.
Installer updated - removed HTML help update functionality.
Built-in Z800 a Z500 customizations updated.
Added support for booting red and blue LG U81xx of CID17.
Added support for unlocking red and blue LG U81xx of CID17.
Note that Direct unlock button may be used with LG U8110 only. For all other
types use Read codes or Lock to net, and flash the Drive C file to allow manual
entering of codes.
Added support for flashing original SSW files into LG U81xx phones.
Added support for changing RSA certificate color of CID17 LG U81xx phones.
It is possible to flash CID17 files of any color to any CID17 LG U81xx phone.
It is possible to flash Z1010 CID16 flash files into Z1010 CID29 phones.
LG U8180 phones with CID41 are now detected correctly. No operation is enabled
for them, though.
The option to Download all files from the phone filesystem has been replaced by a
more general Download files from FS. Now it is possible to specify the source
folder and to optionally disable folder recursion.
The analysis of phone's RSA configuration has been made even more safe and
verbose.
RSA weakness type is monitored while flashing the phone.
Many changes in communication scripts.
Previously, the operation Write to GDFS from file always tried to backup the
security zone first. This behaviour may be disabled now.
Enhanced window font readability - the default window font is set to Tahoma, 8
pixels in size. It is also possible to change the font in registry.
Unicode visual components updated.
Smartcard subsystem refactored. Cruiser is now able to explicitly notify the user of
smartcard middleware initialization failure.
Configuration subsystem refactored.
Thread management subsystem refactored.
Introduced an option to add comments to the Cruiser log-file (located in the Data
folder).
The button Format security zone has been transformed into a checkbox. Fixed a
bug that was causing this option to be disabled in a release version.
Updated TAC list for T630.
The following options are disabled when no valid filesystem configuration is found in
the phone: Upload signed archive, Customize FS, Language operations,
Upload files to FS, Download files from FS, Camera sound on/off and
Shutdown FS.
Filesystem configuration resides in main firmware flash.
Version 3.40 (24th March 2005, 10th release):
Added an option to Download all files from the phone filesystem. The folder
structure is preserved. This option is temporarily located under Language
operations.
Updated TAC list for T290i.
Version 3.32 (22nd March 2005):
The checkbox Force to folder could not be turned off in the previous version.
Minor Customize FS dialog issue fixed.
Relock RSA option is enabled for AVR-based phones by default.
19 The Software
Implemented file download failure check (incoming data loss, etc).
An attempt to reduce input buffer overrun errors has been made. These errors may
occur when phone sends too many data in one block, usually when downloading
files from the phone.
Version 3.30 (21st March 2005):
Added built-in CDA tool.
A sporadic Unlock RSA problem fixed. It was caused by an unexplainable
behaviour of interface chip under certain circumstances.
For AVR-based phones, the RSA protection is removed immediately after boot.
Note that we recently released special flash files (compatible with Cruiser 3.20 or
later version) that allow advanced users to change the phone RSA certificate color.
This is useful for example when changing languages in developer phones.
Added button Language operations capable of downloading all languages and T9
dictionaries from the phone, uploading languages and T9 dictionaries to the phone,
and removing languages. Keep in mind that language (.lng) files vary between
different phones, firmware revisions and language zones.
Added an option to change langpack string in Software Info.
Added a checkbox that enables uploading files to a specific folder in the phone.
Added some RSA applets.
Flash ID is now displayed when booting new phones.
Updated TAC list for T237, T630, K508i, K700i and Z500a.
Updated camera shutter sound handling code.
Buttons Write raw FS and Upload Signed Archive moved to the Write flash
page.
Increased boot process and flash failure verbosity a little.
It is again possible to shutdown FS (safely turn off the phone) immediately after
uploading a raw FS to the phone.
LG cable pinout description updated and moved to the Additional Information
section.
Messages window word-wrapping turned off.
Enhanced communication error handling.
Version 3.20 (6th March 2005, beta version):
Released conversion flashes from V800 to Z800.
Added bandlock change option for new SE phones. You don't have to use .mdc files
for changing bandlock anymore.
Added support for uploading SFA (Signed File Archive) files.
Added Lock to Net functionality for new SE and LG U81xx phones.
Added Remove languages option.
It is possible to turn camera shutter sound back to on. This does not apply to
phones already affected by previous versions of Cruiser.
The Control window has been modified noticeably.
Updated flash applet for J200i/J200c.
Updated TAC list for T290i.
Help file updated.
Reading codes and direct unlock refactored (new SE phones).
Flashing module refactored (new SE phones).
Boot code modified again.
Fixed a little bug in .lng and .t9 file upload routine.
Fixed minor bug regarding interchanged CCK and SPCK codes for T100/T106
phones.
Increased the time interval to wait before hiding help hints.
Cruiser has been made available in Russian language.
Added hotkey for attaching phone: Ctrl-A
Added hotkey for turning phone off: Ctrl-O
Added support for flash ID 0x880D.
Added support for flash ID 0x880F.
Added support for flash ID 0x890C.
A Windows XP style related UI issue fixed.
The LangPack Info button should work again.
Removed log-file calculation functionality.
Version 3.00 (21st February 2005):
Cruiser has been made available in Chinese, Indonesian, Malay, Slovak and
Swedish languages.
Cruiser installer rewritten from scratch.
Help file released for Cruiser.
Cable drivers modified. New optimal settings recommended - see the help file.
As a faster alternative to reading codes, the direct unlock option has been added for
new SE phones.
Added reading codes from LG U8110, U8120, U8130 and U8138. Phones marked by
(R) are not supported yet.
Added direct unlock for LG U8110, U8120, U8130 and U8138. Phones marked by
Added support for flashing LG U8110, U8120, U8130 and U8138. Phones marked by
Released support for V800 red/brown CID29 EROM recovery.
It is possible to flash main firmware, raw filesystem and to customize filesystem
without reattaching the phone in between.
Occasionally the phone does not send an acknowledge on shutdown. This should be
handled now.
Fixed a bug in autodetecting T300 phone type.
Fixed a bug in option to reset life-time call timer in T226/T23x/T290 phones.
Fixed a bug in writing to GDFS and restoring security zone in new SE phones.
RSA phone configuration analysis has been made a little bit more safe under
Windows 98/ME. We still deprecate using Cruiser under Windows 98/ME.
Functionality of the option Using enhanced cables has been extended to RSA
ARM-based phones.
Modified smartcard communication code.
RSA unlocking code updated.
The button-enabling system has been completely redesigned to allow future UI
extensibility.
Little modifications to the Settings window.
Few resource leaks removed.
Fixed some bugs in unicode handling.
Updated TAC list for J200i, J200c, K508i, T230.
Added support for flash ID 0x200D.
Added support for flash ID 0x017E.
And many other improvements noone else will consciously appreciate...
Version 2.20 (23rd January 2005, beta version):
Fixed an issue with Z500 RSA unlocking.
Updated TAC list for red Z500a and for T637.
21 The Software
It is no more necessary to specify that S700/S710 is about to be attached.
S700/S710 can be flashed at the rate of 921600Bd with DSS20 and DSS25
deskstands.
Introduced an option to upload audio files, video files, pictures and themes. Files
are placed to the correct phone folder automatically.
Fixed a bug in CDA article/version modification code.
Added an option to change default article and default version strings.
Fixed a bug causing occasional access violations on Control Window close.
Cruiser did not allow to unlock RSA in phones with damaged security zone.
Version 2.10 (17th January 2005):
Boot code modified again.
Fixed small bug in GDFS and file system access code.
Version 2.00 (12th January 2005, gamma version):
Fixed few bugs in boot code.
Added an option to disable phone configuration analysis.
Simplified phone type selection options.
Boot process optimized.
Fixed a minor bug when booting S7xx phones with phone type autodetection turned
off.
RSA unlocking routine optimized. It works also for Z1010 and V800 of any color.
Added languagepack change for red CID29 Z1010 and V800 phones.
Added support for older GDFS format.
Fixed a minor bug in GDFS access code.
Added automatic GDFS configuration mismatch detection.
Added support for K300, T687 and Z500 phones.
Added reading unlocking/relocking network codes from K300, T687, Z1010, V800,
S710 and Z500.
Added support for conversion from T230 to T290.
Codes read from RSA-based phones are now stored into a log file (placed into the
Data folder).
Added the possibility to specify communication rate for Z500.
About-box information updated.
Updated TAC list for K700i.
Version 1.00 (14th December 2004):
Added reading unlocking/relocking network codes from K70x/K50x/F500/S7xx
phones.
Added reading phonelock code from K70x/K50x/F500/S7xx phones.
Added languagepack change for K70x/K50x/F500/S7xx phones.
Added Save security zone function for K70x/K50x/F500/S7xx phones.
Added Channel info enable/disable function for K70x/K50x/F500/S7xx phones.
(It may be unsupported by with some firmware versions).
Added Battery info enable/disable function for K70x/K50x/F500/S7xx phones.
Added SIM toolkit enable/disable function for K70x/K50x/F500/S7xx phones.
Added Reset air time option for K70x/K50x/F500/S7xx phones.
Added Enable/disable SMS capability functions for K70x/K50x/F500/S7xx
phones.
Added Change phone type descriptor function for K70x/K50x/F500/S7xx phones
- not fully tested, though.
Added Reset total call time option for K70x/K50x/F500/S7xx phones.
Added Reset life time option for K70x/K50x/F500/S7xx phones. The counter may
be accessed from the service menu.
Added Reset joystick counter option for K70x/K50x/F500/S7xx phones.
Buttons Read GDFS zones and Write to GDFS from file now work also for K70x/
K50x/F500/S7xx phones.
Added Camera shutter sound remove function.
Added Unlock RSA function for K70x/K50x/F500/S7xx phones.
Cruiser was the first standalone software to support unlocking and changing
languages in new ARM phones.
1.3 History of Changes - Fighter/Interceptor
There are going to be no more Fighter/Interceptor software updates.
Interceptor updated too.
It is possible to flash more phones at once via EPI USB too.
Sharp 3G flashing speed via Fighter/Cruiser cable slightly improved.
Chinese language strings updated.
The main executable and help file are now stored outside the installer.
Added support for full security zone rebuild of R520/T39/T65 phones (i.e.
phones with baseband chip ID 0x5C05 and 0x5C06).
The Redirect SCRC check to zone II checkbox has been removed.
The Security II page was removed as it has been made superfluous by
extending the Security I page functionality to R520/T39/T65 phones.
Added function Repair certificate to simplify phone revival on flash failure.
Added support for EROM recovery in very rare brown CID16 V800/Z800.
Added function Repair EROM to simplify EROM area repair in red and brown
phones of CID29 and CID36.
For AVR-based phones, the RSA protection is removed immediately after boot.
There is no need to reflash the phone afterwards.
Added support for flashing LG 3G phones and Sharp 3G phones.
Added an option to flash faster via EPI USB.
Added support for conversion from T230 to T290.
Added displaying of flash manufacturer when booting new ARM phones.
Updated TAC list for many phones.
Fighter installer rewritten from scratch.
Cable drivers modified. New optimal settings recommended - see the help file.
EPI USB driver included to allow faster flashing of LG 3G, Sharp 3G and V800/
Z800/Z1010 phones.
An error message is now shown when trying to boot an incorrectly upgraded
P900 to a P910. Such phone has to be booted using a testpoint connected to
GND.
It is no more necessary to specify that S700/S710 is about to be attached.
S700/S710 can be flashed at the rate of 921600Bd with DSS20 and DSS25
deskstands.
Functionality of the option Using enhanced cables has been extended to RSA
23 The Software
ARM-based phones.
Baudrates used for flashing PDA part of P80x/P910 are limited to 460800Bd
when using USB cables that are not enhanced by adding two resistors. This is
not related to DSS-20 nor DSS-25.
Fixed minor bug regarding interchanged CCK and SPCK codes for T100/T106
phones.
Boot process optimized.
Few resource leaks removed.
Fixed a bug in option to reset life-time call timer in T226/T23x/T290 phones.
Fixed a bug in autodetecting T300 phone type.
Debug Log feature released to public.
Now it is possible to specify which recovery applet (for which CID) to use when
booting the phone.
Some obsolete flashing options removed.
Baudrate page from the Settings window was replaced by the Limit
baudrate combobox in the Primary page of Control window.
Enhanced window font readability - the default window font is set to Tahoma, 8
pixels in size. It is also possible to change the font in registry.
Unicode visual components updated.
Messages window word-wrapping turned off.
The Control window has been modified noticeably.
Increased the time interval to wait before hiding help hints.
Added hotkey for attaching phone: Ctrl-A
Added hotkey for turning phone off: Ctrl-O
A Windows XP style related UI issue fixed.
Fighter has been made available in Chinese, Indonesian, Malay, Polish, Russian,
Slovak and Swedish languages.
The button-enabling system has been completely redesigned to allow future UI
extensibility.
Little modifications to the Settings window.
Simplified phone type selection options.
Fixed some bugs in unicode handling.
About-box removed.
Minor modifications to the Settings window, mostly EMMA smartcard related.
Be sure to enter correct PIN for your EMMA smartcard.
Configuration subsystem refactored.
Thread management subsystem refactored.
Baudrate subsystem completely refactored.
Smartcard subsystem refactored. Fighter/Interceptor is now able to explicitly
notify the user of smartcard middleware initialization failure.
Modified smartcard communication code.
Added a possibility to boot AVR based phones starting from R520m by means of
an EMMA smartcard.
Small modification in AVR security zone creation code.
Software is now available in English, Swedish, Chinese Traditional, Malaysian
and Indonesian languages.
Updated TAC-list for V800, F500i, T290a, T610, T618, T630 and T105.
Fixed a bug when flashing A3618/T10x phones using software versions 4.30 and
4.31.
Internal database extended to 678 firmwares.
GDFS code massively refactored.
Version 4.31 (5th November 2004):
Malaysian language issue fixed.
Updated TAC-list for S710a.
Version 4.30 (3rd November 2004):
Enabled flashing main firmware part of K70x/K50x/F500/S7xx/Z1010/V80x.
Enabled RSA certificate recovery function for K70x/K50x/F500/S7xx/Z1010/
V80x.
Corrected default bandlock setting for T290a.
Added Troubleshooting section to the help file.
Fixed a T62u write-to-GDFS error.
Chipset recognition code enhanced.
Decreased number of threads running concurrently.
Reworked baudrate handling code.
Version 4.20 (26th October 2004):
Added support for J200i and J200c.
Added option to override phone type to T290.
Released support for communication via original DSS-20 and DSS-25 USB
cradles.
Released T62u decustomization file.
T62u Direct unlock removes also WAP-lock and SOC-lock.
From now it is possible to perform multiple AVR/ARM/GDFS operations in almost
any order. The only requirement is to perform minor modification to the cable
(connect pins 1 and 2 of 74HC4053 to 3.3V via two 10k Ohm resistors) and to
enable newly added option Using enhanced cables in the Settings window.
Direct unlock, Relock to network, Recalc DCRCs and Unterminate buttons
are not enabled for T610 R1L013 and later firmwares.
Slightly enhanced the ability to turn off phones.
Possible to use another smartcard reader.
Phone shutdown functionality enhanced.
Corrected default bandlock setting for P910a.
Updated languagepack info.
Modified AVR RSA flashing script.
Fixed hint display bug when writing CDA info to the GDFS.
Fixed ocassional bug on Control Window closing.
Added option to generate random codes.
Version 4.10 (16th September 2004):
Security zone concept has been extended (to be able to restore SOC/WAP locks
and so on).
Added displaying of SOC unlocking code for T62u (even in that case it is
different from NCK unlocking code).
Added displaying of WAP unlocking code for T62u, T306, T316, T226, T230,
T237 and T238. It is now possible to unlock profiles, lock profiles, reset WAP-
lock from the service menu and change predefined data accounts much faster
than by decustomizing.
Added support for booting Z20x with new hardware (manufactured in September
2004 or later).
Updated P900/P910 PDA flashing applet.
Released support for flashing AVR and PDA parts of P910.
25 The Software
Conversion from P900 to P910 made available.
Updated languagepack info.
Internal database extended to 675 firmwares.
Added flashing of T637 ARM part which was omitted by a mistake.
Fixed an error in new error-handling routine that was disabling displaying non-
unicode messages and ocassionaly causing to display unicode messages three
times in a row.
Invalid content of network lock editbox just causes a beep and does not show an
error message anymore.
The software should not freeze on shutdown.
Read GDFS zones checkboxes were sometimes not updated correctly.
Fixed minor bug when flashing R320 ARM part (appeared in one of the previous
versions).
Increased communication security when reading ASIC ID.
Fixed some memory-deallocation issues.
Updated TAC-list for T610, T630, P910, K700, K500 and F500.
Version 4.00 (8th September 2004):
Added RSA-removal support for AVR-based phones.
Added support for flashing AVR-part of RSA-protected T61x/T62x/T63x/Z60x/
P910 phones (also without having to remove RSA lock).
Added support for flashing ARM-part of RSA-protected T61x/T62x/T63x/Z60x
phones (also without having to remove RSA lock).
Implemented function for automatic displaying firmware languagepack and
revision in 5B0702FF and 5B080201-based phones. Internal database contains
data about the most common T61x, T62x, T63x, Z60x, T226, T23x, P80x, P90x,
T20x, T30x, T31x, T68 and T62u firmwares. The present number of detected
firmwares is 587.
Since the Unlock RSA function erases the whole RSA flash region, the firmware
has to be restored afterwards. Therefore, to save your time, a special option to
reflash RSA area only has been introduced.
The phone type autodetection was enhanced. In practice it means even less
"Phone type: Unknown" messages.
Previous versions were removing the RSA lock from FLP flash files automatically,
now there is an option to disable this default behaviour - Relock RSA.
Due to some enhancements, few FLP flash files created for this version will not
be backwards-compatible with the previous software versions. It is possible to
flash both standard and RSA-protected phones using the same files.
Released a solution to upgrade P900 to P910.
Support for flashing Z20x phones with new flash chip type released to all Fighter
users for free.
Modified error-handling, separate error-message window created.
Enhanced MDC-file messaging.
Corrected bug with disabled Clear and Autodetect buttons in Settings window.
Added support for translating the software into any language. Few languages are
in beta-testing phase.
Fighter serial cable support has been removed - it was useless there. For old
phones with 5V bus use NTZ112311 cable type.
Fixed a bug regarding phone charging via UC-10 cable.
Updated help engine.
Updated TAC-list for T610 and T630.
Little gift for people who read user manuals: You can enable System Monitor
on T66/T600 phones by holding left shift key while pressing the Clear
phonelock button.
Version 3.13 (30th July 2004):
Added option to disable cable type verification.
Verbosity of cable detection code increased even more.
Fixed an occasional issue causing software exception when autodetecting cable
types with Bluetooth virtual serial ports with numbers less than 17.
The Clear button in Settings window does not clear connections that are
opened.
This software version does not (and will not) support older cable driver versions
anymore. Old cables will be supported, but only with the latest driver which is
included in the Preinstaller package.
Increased verbosity of cable detection code.
From now, Interceptor displays the following message: "Interceptor software
does not allow to change a unique device identifier, nor allows to interfere with
its operation".
The help file now contains preliminary install guide, since the new installer is
now different from the formerly used one.
Added cable type autodetection (see the Settings window).
Fixed minor bug regarding Charger ON button.
ARM-based phones research at full throttle...
Added support for flashing Z20x phones with new flash chip type.
Updated TAC-list for K700.
RSA protection feature deactivation method via testpoints was made available
for everyone by Fighter Team on 4th July 2004. We are the first!
New software branch created - Interceptor.
Added support for UC-10 Universal Cable.
Added experimental support for Windows XP ServicePack 2.
Help file is no more a component of the executable.
Reworked comm scripting engine.
Modified phone status detection code.
Booting algorithm slightly enhanced.
Flash reading can be stopped by Detach phone button from now.
Removed many unused code scraps.
Fixed internal message distribution code (needs more work).
Fixed minor file/directory naming issue of previous version regarding T610
phones (mainly causing errors when rebuilding security zone of T610 under
Win98/ME).
Standard (wait) attach option works for more models now.
Fixed UART2-port issue regarding debuglog-option.
Updated hints.
Updated TAC-lists for T610, T630, T230, T226, T106, Z1010 and K700.
Updated langpack info for P908 and Z20x.
Help file is no more included in the executable, instead it is installed by setup.
27 The Software
Fixed RSA booting script error.
RSA protection feature deactivation method via testpoints was made available
for selected Fighter users.
Fixed help file dynamic content error.
Added automatic boot type detection for 5B080201-based phones (T61x/T63x/
Z60x/T226/T23x/P90x).
Added support for booting 5B080201-based phones with activated RSA
protection feature (nothing more yet).
Added automatic patching of AVR flash files to disable activating RSA protection
feature.
Updated PDA flashing applet for P80x/P90x. P90x customization data flashing is
stable - no need to lower baudrate to 115kBd anymore.
Modified script for flashing P80x/P90x Bluetooth part.
Security zone 1 creation is a bit faster now.
Fix (critical): Automatic security zone backup could not be restored sometimes
due to missing end-of-stream marker.
Fix: Restore security button should not be affected by Protect Security Zone
option in another page.
Enhanced cable control.
Booting algorithm completely redesigned.
Removed bootstrap analysis option as it is no more necessary.
Fix: Set acoustic compensation to default option was shown twice for T610/
T618 and not shown for T616.
Fix: Enable/disable packet channels function was not working for some
models.
Fix: Default bandlock setting for T62u has been corrected - it was previously set
to EGSM900 by a mistake.
Function Reset total call time enabled for all supported GDFS-based models.
Added Reset air time option for all supported GDFS-based models. Only few of
them also display this value (T226, T23x,...).
Added Reset flip counter option for Z60x.
Added Reset joystick counter option for T226/T23x/Z60x.
Added Reset internet accounts option for Z60x.
Added option to reset hidden life timer for all GDFS-based models.
Finally added option to fix HBH-30 echo problems on T68.
Added option to enable/disable debug tools on T62u.
Added option to enable/disable permanent CLIR on T62u.
Added support for backup of battery calibration zone of T237/P90x.
Added support for backup of display calibration zone of T237.
Added support for backup of audio calibration zone of T68.
Added support for backup of audio calibration zone of T30x/T31x.
Added support for backup of audio calibration zone of T226/T23x.
Added support for backup of audio calibration zone of P80x/P90x.
Added support for backup of audio calibration zone of T61x/T63x/Z60x.
Added support for backup of radio calibration zone of R520/T39/T65.
Added support for backup of radio calibration zone of T68.
Added support for backup of radio calibration zone of T30x/T31x.
Added support for backup of radio calibration zone of T226/T23x.
Added support for backup of radio calibration zone of P80x/P90x.
Added support for backup of radio calibration zone of T61x/T63x/Z60x.
Added progress indication while reading GDFS zones.
Added Beep on booting option for 5B080201-based phones in the Settings
Window.
Updated TAC-list for T230.
Fix: Control window, about box and help file now reflect Fighter/Interceptor
configuration more accurately.
Help file update: It was necessary to add active scripting due to the previous
item.
Help file update: More detailed description of P80x/P90x flashing operation.
Further cosmetic changes.
Version 2.70 (27th March 2004, alpha version):
Added Z200/Z208 direct unlock option - no more hassling with unreliable CDA-
dependent flash files.
Added Z200/Z208 CRC recalculation function.
Added T100/T102/T105/Z200/Z208 reset phonelock function - no more need to
use large-hammered NVRAM clean file.
Released T100 Hindi language activation file.
Solved an issue with accessing GDFS in T62u.
Fix: Communication indicator timers turned on after Control Window open (bug
in release version 2.60).
Fix: Option to read AVR flash from R320 was disabled by mistake.
Fix: SPCK and CCK codes swapped when read from R600 by mistake.
Fix: In case of T100 phonelock unavailability a message is shown now.
Updated TAC-lists for T100/T102/T105.
Reenabled automatic distinction between T226 and T226s.
Flashing the AVR part of 5B0702FF and 5B080201-based phones has been made
a bit more safe.
Version 2.60 (1st March 2004, alpha version):
Added support for programming OTP IMEI in empty ST M58CR064P and ST
M58CR064Q (used in the latest T226/T230/T237/T238).
Added support for programming OTP IMEI in empty ST M58WR064ET and ST
M58WR064EB (used in the latest Z600/Z608).
Reduced ARM flashing scripts for T68, T61x, T62x, T63x and Z60x.
Modified PDA attach code. Even prototype P80x should be attached normally.
Slightly modified scripts for T66/T600 phonelock reset.
Fix: Communication indicator timers turned off on Control Window close.
CDA Article/Version TAE change disabled for models without ARM CPU.
Released T230 R4A GDFS-upgrade MDC file.
Deeper Fighter code refactoring has started.
Released unlocking files for Z200 and Z208 (although not fully working).
Added support for flashing and unlocking of T237, T637 and P907.
Modified charger line control.
Added Protect security zone option for writing to GDFS from a file.
Fixed a problem with attaching R520 and T39 phones that has appeared in one
of the previous versions.
Help file updated.
29 The Software
Flashing algorithms for A3618/T10x/Z20x significantly improved.
Released repair file for T100/T102/T105/T106 (fixes customization and system
parameter areas, clears NVRAM area).
Released repair file for A3618 (fixes customization and system parameter areas,
clears NVRAM area).
Released new decustomization file for Z200 (enables Italian and Chinese
languages).
Fixed an issue causing ARM-part unflashability of T68mc and T68ie.
Fixed an issue with reading AVR flash content from T28z.
Fixed a problem with attaching R600 phones.
Version 2.57 (2nd February 2004, not released to public):
Released GDFS decustomization files for Z200, T630, T226 and T616.
Reworked Z200/Z208 flash access to be able to upload decustomization files.
Added possibility to reset acoustic compensation to default for T610, T618 and
T616. To be used when converting T610 to T616 and "no sound" problem
occurs.
Added P800/P802 AudioPatch option.
Added possibility to flash P80x/P90x Bluetooth module. Just attach to the PDA
part and select flash ARM...
When flashing Bluetooth on P80x/P90x, baudrates up to 460kBd may be
specified.
Added displaying of flashing time for Bluetooth module.
Reworked R600 flash access.
Added possibility to specify baudrate for flashing R600 phones. They can be
flashed also at 230kBd from now.
Help file updated.
Added new Z200/Z208 ASIC support.
Added support for flashing Z200/Z208.
Updated TAC-lists for T100, T316, T602, A2638sc, A2668sc, A2218z, A2228z,
T28z, T62u.
GH768c renamed to GF768c.
Duplicate option to Enable GPRS packet channels replaced by Disable GPRS
packet channels.
Enhanced GDFS-access error handling.
Modified read flash functionality.
Further performance optimizations.
Lowered flash-file loading thread priority.
Fixed an issue from version 2.50 (concerning T68, T6xx and Z60x) that was
causing an error when flashing two or more ARM flashes in a row.
Help file updated.
Version 2.54 (29th December 2003, not released to public):
Updated T230/T238/T226 authority check bypass code.
Updated P90x PDA hardware initialization scripts.
From now, all Fighter windows should be displayed correctly also for other
display font sizes.
One of the Main Window menu items slightly extended.
Fixed an issue with Control Window height constraint.
Modified communication scripts for flashing R600 phones.
P80x/P90x phones are charged no more while accessing PDA part.
Version 2.53 (18th December 2003, not released to public):
Added option to disable phone detach confirmation.
Fixed problem with displaying help on the first Fighter startup.
Security zone redirection patches have somehow disappeared from the version
2.52.
Fixed a Pro-version related bug regarding booting code thread-safety which
could sporadically cause lock-ups while attaching more phones with different
ASICs simultaneously.
Fixed occasional GDFS IMEI reading issue. No more FF's for T610 EU6 R3C002.
GDFS zone (security, calibration,...) backups are no more saved into the Data
\Security zone backups directory. Instead, a directory Data\GDFS zone
backups is used.
Modified one of the hardware-initialization applets.
A GDFS security zone backup is made automatically before each attempt to
write data to GDFS.
TAC-list updated (P908, T610 and T106).
Added option to read OTP and GDFS from T20, T29 and A26x8.
Added option to read AVR flash areas from A10x8, T1x, T2x, A26x8 and R3x0.
Added Default button in the Settings Window.
Updated phone operations info in help file.
Updated language info in help file (added language name acronyms, etc).
The bandlock checkboxes are now automatically initialized after the phone is
attached.
Few coding bugs fixed.
Added the possibility to change default value of Autodetect type checkbox in
the Primary tab of Control Window.
Added the possibility to change default value of Directly write to GDFS
checkbox in the Security I tab of Control Window.
Updated applet for flashing P900/P908.
Added support for programming P900/P908 DiskOnChip images.
Added final checksum verification for flashing PDA part of R380/P80x/P90x.
The PDA flash files can now consist of more than one flash block. The blocks do
not have to be size-aligned to 256 bytes anymore.
Extended number of baudrates supported for accessing PDA flash in P80x/P90x.
T630/T628 phone type autodetection enabled.
From now, you can enable Italian language in T100/T105 (when flashing itself
does not suffice).
Added help system.
Added language package info button.
Modified button-enabling system. Charger ON and Charger OFF buttons are
shown no more for cables not supporting this feature.
Removed Read GDFS button. Instead use the Read AVR button with GDFS
zone selected.
Added Program OTP IMEI feature.
31 The Software
P900/P908 security zone is saved correctly now.
Fixed occasional bug in T226/T230 security zone creation.
Added displaying of flash chip ID in security zone creation.
Added checking of OTP IMEI area state.
Card activation tab in settings windows is displayed only when cardact
command-line parameter is specified.
P800 PDA part flashing made MUCH faster. Symbian part1 (16MB of data) can
be flashed in 03:24, part2 (4MB of data) in 00:52.
Added IMEI change (Disable OTP IMEI check) for T226, T230, T238, T630 and
T628.
Fighter is now able to fully rebuild security zone I in T226, T230, T238, T630,
T628.
New flashing applets for T68, T20x, T3xx, T61x, Z60x, T23x, T226, P80x.
Modified ASIC recognition code.
Fixed minor bug in AVR flash reading routine.
From now on you can enable Chinese language in T100/T105 (when flashing
itself does not suffice).
It is now possible to set cable type for each (virtual) serial port separately.
Selected cable types are shown in window captions.
Modified tabbing order of control items.
Upgrade EEPROM has been renamed to Upgrade security.
Check GDFS has been renamed to Check security.
Function Set phone type descriptor moved under Modify GDFS function.
Added CDA article string modification function (MS and TAE).
Added CDA version string modification function (MS and TAE).
Added support for backup of audio calibration zone of R520, T39, T65.
Added support for backup of battery calibration zone of T3xx, T226, T23x, P80x,
T61x and Z60x.
Added support for backup of display calibration zone of T3xx, T226, T23x, T61x
and Z60x.
Added Read GDFS zones option. Now it works only for R520, T39, T65 and
T68. Currently supported zones are: security, battery calibration, display
calibration. More phone types/zones will be added in the following versions.
Slightly modified boot bypass algorithm (it is a test version).
Fixed Security Zone I creation bug which appeared in version 2.47.
Version 2.47 (22nd October 2003):
Fixed bug in automatic recognition of T616 phone type.
Minor changes in trial card activation routines.
Added theoretical T630/T628 flashing support.
Added T230/T238 flashing support.
It is now possible to boot T68/T610/Z600 phones with freezing ARM part more
comfortably (without periodically removing battery).
Extended authority check bypass data.
Security zone II manipulation disabled for some phones.
Fighter is now able to detect some cases when SZ has been rebuilt by DIV.
Minor details changed.
Modified splash-screen.
Enabled theoretical support for flashing P900/P908.
Fixed bug in reading GDFS from T616.
Enhanced read flash functionality.
Fighter now supports remote update from Std to Pro version.
Added basic tool for remote bootstrap analysis.
Added support for trial cards.
Added displaying actual phone state.
Added autoincrement IMEI option.
Added support for Z600/Z608.
Added support for new hardware versions of T61x.
Added logfile support. (Codes read are written to a logfile in the data directory).
Added support for Disable OTP IMEI check in all T610 R3B011 and R3C002
langpacks.
Fixed SZ progress indication for R520/T39/T65.
Modified security zone manipulation for R520/T39/T65.
Create security zone I is able to write to GDFS directly now.
Added enable sounds option.
Type override -> Autodetect type
Almost all GDFS applets modified.
Fixed serious bug in T65 GDFS applet.
Added enable/disable FR/EFR/HR/AMR.
Added T200/T202 volume level fix.
Added T300/T302 audio 0/0 fix.
Added T310/T312 audio 0/0 fix.
Added rescan ports button / menu item.
Removed option to periodically check serial ports availability
Random NCK/NSCK/CCK/SPCK may be generated by double-clicking the
corresponding edit box.
Added full support for T226.
Extended automatic recognition of T610.
Added button Restore security (it has the same functionality as Write GDFS)
Added audio trim option for T610.
Added reset internet accounts option for T610.
Added set descriptor option.
Fixed bug that was causing delay after AVR and Z80 flash. Mostly noticeable
when uploading larger flash files.
Fixed bug in automatic recognition of CA638 and T106.
Safe communication and Disable Xon/Xoff turned off by default after first
install.
Fixed bug with baudrate setting when using manual ignition.
Fixed serious LED timer bug causing too high processor usage.
Version 2.00 (7th August 2003):
33 The Software
Added full IMEI change and IMEI/SP-zone rebuild support for T610 R1L013.
Reduced the number of phone attach/detach operations while working with the
phone. It is possible to create more security zone files at once. The created
security zone may be written to the GDFS without reattaching the phone. The
phone can be flashed immediately afterwards.
Added reading of GDFS IMEI for T68/T2xx/T3xx/T61x/P80x. In the case GDFS
IMEI differs from the OTP IMEI, Fighter displays a warning.
Added generic patcher for T610 R1L013 OTP IMEI check removal.
Added generic patcher for T610 R1A081/R1F001 OTP IMEI check removal.
Added autodetection of IMEI/SP-zone type for T610.
Clear total time function now works for T3xx too.
Added fuel-gauging enable/disable function for R520/T39/T65.
Added cipering indication enable/disable function for T3xx/T610.
Authority check bypass algo setting is now saved to Windows registry.
Added support for clearing phonelock in T66/T600.
Added the possibility to enable/disable network (ETSI) lock menu for T68/T3xx/
T610.
Added function to enable/disable WAP picture saving for T68.
Changed the way to access the GDFS in the Modify GDFS function.
Fixed minor bug in Write GDFS function.
Slight optimizations made in A3618/T100 flashing routines.
Extended timeout for starting GDFS applets.
Modified thread priorities.
Fixed About-box bug.
Version 1.34 (21st July 2003):
Writing to GDFS made faster.
Extended timeout for conversion from T68m->T68i (some phones have slower
flash chips).
Added the option to disable IMEI change.
Updated dynamic menu system.
Added T610 decustomization.
Added support for clearing the joystick counter and clearing the total time on
T610/T618.
Added separate baudrate setting for T610/T618.
Fixed bug recognizing few T618.
Added full support for T610 (complete rebuild).
Added reading codes from A3618/T100.
Added reading codes from R600.
Added reading codes from T66/T600.
Fixed minor bug in security zone 1 creation routine (few non-relevant product
settings bytes were incorrectly initialized).
Fixed minor bug in R380 WORLD recognition.
Fixed confusing UI behaviour (incorrect progress display, etc).
Modified settings window.
Many internal code enhancements.
Version 1.32 (3rd July 2003):
ARM flashing made safe on crippled OS like Win98/WinME.
Added option Force Safe Communication.
Fixed bug in construction of MNC2 locked security zone I.
Added automatic directory creation for saving of GDFS, flash and security zone
backups.
Added test whether the phone has been damaged by TotalTool.
Version 1.30 (29th June 2003, first public version):
Added the option to specify number of attempts in network lock menus
Added support for GSM850 bandlock.
Added security zone autosave feature.
Few icons modified.
Fixed bug that was causing card lock-up after few card logins.
The development started in the middle of May 2002 as version 0.01.
Fighter was the first software to support full security zone rebuild on AVR-based
phones with baseband chip ID 0x5B07 and 0x5B08.
Part
II
2 Installing the Software
2.1 System Requirements
Minimal System Configuration:
Intel Pentium 60MHz
64MB RAM
800x600 display resolution
about 20MB of free harddrive space (but a CD-ROM drive present)
two free USB ports (USB hub may be used)
Microsoft Windows 98SE/ME/2000/XP
Recommended System Configuration for Cruiser Standard (or Pro 2):
Intel Pentium III 1GHz or better CPU
512MB RAM
about 3GB of free harddrive space
DVD-ROM drive present
two free USB ports (USB hub may be used)
Microsoft Windows 2000 SP4 or Microsoft Windows XP SP2
Internet connection available
Recommended System Configuration for Cruiser Pro 16:
A very fast CPU.
1GB RAM.
about 10GB of free harddrive space
DVD-ROM drive present
as many USB ports as possible
Microsoft Windows 2000 SP4 or Microsoft Windows XP SP2
Internet connection available
2.2 Installing the Software
This is the correct procedure to install Cruiser on a Windows 2000 or Windows XP
machine. While Cruiser will also work on Windows 98 and Windows ME, this is not a
supported configuration.
CAUTION: Do not connect the smartcard nor the USB cable to the PC at this
time!
Download the latest software installer package from the support area using
your login ("cruiser") and password ("cruiser"). The installer package file is
usually named Cruiser_vX. XX_installer.exe, where X.XX is the actual
version of the software included. Start it and the following window will appear:
Press the Next button and you will be asked to review the License Agreement
. If you accept the terms of the agreement, select the first option below. Only
then you may continue installing the software by pressing the Next button.
You will be prompted which components you wish to install. If you are installing
Cruiser for the first time, select Full for the type of install. You have to untick
Identity Change Support if IMEI changing is not legal in your country.
Choose a location to install Cruiser. The preferred choice is already selected for
you - "c:\Program Files\Cruiser" - and click next.
Choose the name of the Start Menu Folder and click next. Cruiser will then
install itself.
If you have chosen to install the Schlumberger e-gate smartcard driver
automatically, the following window will pop-up under Windows 98/ME. Press
Yes.
You will be probably asked to provide e-gate smartcard driver files. The folder
should be already set up correctly, in that case just press OK. Otherwise press
Browse button to locate the files manually. The default folder should be "c:\Program
Files\Cruiser\Cyberflex Access e-gate Drivers", unless otherwise defined.
Alternatively you may use drivers from the installation DVD.
CAUTION: Wait few seconds until Windows updates its driver database.
You will be given the option to reboot your PC. Before following anymore of the
steps below, please reboot your PC.
Plug in your USB Smart Card. Windows will give you the "Found New Hardware"
message and start to install Drivers. It will ask if it is allowed to search
Windows Update for drivers, select no. It will then ask you to install drivers
automatically, or if you have a disk to install them from. DO NOT let windows
install automatically, choose Have Disk and in the dialog box that appears,
naviagate to "c:\Program Files\Cruiser\Cyberflex Access e-gate Drivers
" and click OK. Windows will then install the drivers for your SmartCard.
Plug in your Fighter/UC-10 cable. Again, follow the same procedure as above
but the drivers for the cable are located in the "c:\Program Files\Cruiser
\Cable Drivers" folder.
Now that all drivers are installed correctly, reboot your PC again, then run
Cruiser!
Hopefully Cruiser is now running and your SmartCard has been correctly
detected. Check in the bottom left hand corner than your serial number is
displayed. If not, read the "HELP!" section below.
Look in the Windows device manager to find out what Port Number your cable
was assigned. If it is something higher than 16, you will have to change it to a
lower number.
Select the Settings Menu in Cruiser. Now click on the COM number that
corresponds to the number your cable was assigned. Click on the far right of the
box that says "Not connected" and from the pulldown menu, choose the type of
cable you have which will either be a Fighter USB Cable or a UC-10 cable.
Click on OK.
Click on the Rescan button.
The COM Port your cable is plugged into should now be lit up. Click on it to get
started with Cruiser!
HELP!
The most common problem is the SmartCard is not detected. This often happens if
you let Windows install the SmartCard Driver itself. To correct this, go into the
Windows Device Manager, Select one of the SmartCard devices, right click and select
"Properties", select the "Driver" tab and click on "Update Driver". The point Cruiser to
the SmartCard driver directory, usually
"c:\Program Files\Cruiser\Cyberflex Access e-gate Drivers".
However, there are still some situations where the SmartCard service fails to work
correctly. This is not a Cruiser problem, but rather a Windows one. Ensure you are
running the latest Service Pack for your OS and try again. Also try looking the Service
for your PC to ensure the SmartCard service is started (and if not, manually attempt
to start it).
2.3 Manual SmartCard Base Components Problem Resolution
Thanks to Invisible and to Muppet for pointing to the right direction.
Description:
The Microsoft SmartCard Base Components (further referred to as MS SCBC) are
necessary for the operation of PC/SC based smartcard readers. They are already an
integral part of the Windows 2000 and Windows XP operating system, but for
Windows 9x, Windows ME and Windows NT they have to be installed separately.
Installing them under Windows 2000 or Windows XP destroys already available
functions and thus the system will not be able to access the PC/SC smardcard reader
anymore. Deinstallation of the MS SCBC will not fix the system!
Sometimes the MS SCBC does not function properly. It may be caused by one of
these reasons:
Trying to install the MS SCBC 9x/ME/NT package under Windows 2000 or
Windows XP.
Upgrading from Windows 2000 to Windows XP SP1.
After installing a clean copy of Windows 2000 or Windows XP the MS SCBC is
sometimes not installed correctly.
Other reasons not covered by previous possibilities.
To reestablish correct functionality of the operating system refer to following
solutions:
Solution for Windows 2000:
Login as an user with administrative rights.
If possible, install the latest Windows 2000 Service Pack and then restart the
computer.
Under Start | Run successively type in and confirm with OK button the
following two commands:
o regsvr32 %windir%\system32\scardssp.dll
(You should receive a message that the DLL server was registered
successfully)
o scardsvr reinstall
Have a look in Start | Settings | Control Panel | Administrative Tools |
Services and locate the entry Smart Card. Check its current status. If it should
not be started, try to start it (click right mouse button, and press Start).
Independently of whether the service can be started or not change the startup
type from Manual to Automatic.
Restart the computer.
Solution for Windows XP:
Login as an user with administrative rights.
If possible, install the latest Windows XP Service Pack and then restart the
computer.
Under Start | Run successively type in and confirm with OK button the
following two commands:
o regsvr32 %windir%\system32\scardssp.dll
(You should receive a message that the DLL server was registered
successfully)
o scardsvr reinstall
Locate the scard_xp.reg file and then doubleclick on it. The registry will be
updated.
DO NOT DO THIS UNDER WINDOWS 2000!
You may find the scard_xp.reg file in the "c:\Program Files\Cruiser
\SmartCard Diagnostic Tool" folder.
Have a look in Start | Settings | Control Panel | Administrative Tools |
Services and locate the entry Smart Card. Check its current status. If it should
not be started, try to start it (click right mouse button, and press Start).
Independently of whether the service can be started or not change the startup
type from Manual to Automatic.
Solution for Windows 98:
Install MS SCBC.
Solution for Windows ME:
Install MS SCBC.
2.4 Checking Drivers and OS Update Installation Success Under
Windows 2000/XP
Be sure to have both smartcard and the USB cable connected to the PC.
Now start the USB View Utility which can be found in the Diagnostic Tools
folder of the Windows start-menu. If everything works fine, you should see a
configuration similar to that shown in the following picture.
Both e-gate USB Smart Card and UC-10 USB Composite Device (or Fighter
USB Composite Device) strings should be visible (i.e. the respective devices
are properly connected to the USB bus).
Click at My Computer icon on your Windows desktop using the right mouse
button, then select Properties. The System Properties window will appear.
You can achieve the same result also by using Win+Break key combination.
In System Properties window go to Hardware tab (1) and open Device
Manager (2).
As the Device Manager appears, try to locate the e-gate Virtual Reader
Enumerator driver (1), e-gate USB Smart Card reader driver (2), e-gate
USB Smart Card driver (3), UC-10 USB Composite Device driver (4), and the
Universal Cable UC-10 driver (5). If at least one of the mentioned drivers is
missing, the software will probably not work correctly. Also keep in mind, that if
you have the old Fighter cable, the respective driver names (4) and (5) will be
different - Fighter USB Composite Device and SphereGSM Fighter Cable.
At this point check (and remember) what COM port number (5) is assigned to
the USB cable (it is displayed next to the device name, inside brackets). The
COM port number has to be in range between 1 and 16, otherwise Cruiser will
not be able to recognize it.
Now start the SmartCard Diagnostic Utility which is located in the same folder
as the previous tool. Click the Smartcard Base Components item on the left
pane and you should see something similar to the following picture:
Now doubleclick the Connected Readers item and it should unroll so it would
contain the Schlumberger e-gate 0 string. If the Connected Readers list is
empty, there will be probably a problem with e-gate virtual reader driver.
2.5 Checking Drivers and OS Update Installation Success Under
Windows 9x/ME
Be sure to have both smartcard and the USB cable connected to the PC.
Now start the USB View Utility which can be found in the Diagnostic Tools
folder of the Windows start-menu. If everything works fine, you should see a
configuration similar to that shown in the following picture.
Both e-gate USB Smart Card and UC-10 USB Composite Device (or Fighter
USB Composite Device) strings should be visible (i.e. the respective devices
are properly connected to the USB bus).
Click at My Computer icon on your Windows desktop using the right mouse
button, then select Properties. The System Properties window will appear.
You can achieve the same result also by using Win+Break key combination.
In System Properties window go to Hardware tab (1) and open Device
Manager (2).
As the Device Manager appears, try to locate the e-gate Virtual Reader
Enumerator driver (1), e-gate USB Smart Card reader driver (2), e-gate
USB Smart Card driver (3), UC-10 USB Composite Device driver (4), and the
Universal Cable UC-10 driver (5). If at least one of the mentioned drivers is
missing, the software will probably not work correctly. Also keep in mind, that if
you have the old Fighter cable, the respective driver names (4) and (5) will be
different - Fighter USB Composite Device and SphereGSM Fighter Cable.
At this point check (and remember) what COM port number (5) is assigned to
the USB cable (it is displayed next to the device name, inside brackets). The
COM port number has to be in range between 1 and 16, otherwise Cruiser will
not be able to recognize it.
Now start the SmartCard Diagnostic Utility which is located in the same folder
as the previous tool. Click the Smartcard Base Components item on the left
pane and you should see something similar to the following picture:
Now doubleclick the Connected Readers item and it should unroll so it would
contain the Schlumberger e-gate 0 string. If the Connected Readers list is
empty, there will be probably a problem with e-gate virtual reader driver.
2.6 Frequently Asked Questions
Question:
When installing Cruiser, I get a message displaying "Failed to register IOPCOM3.DLL".
Answer:
This is usually caused by a missing DLL that is IOPCOM3.DLL dependent on. Most
likely it is the MSVCP60.DLL library. After resolving this problem, you have to reinstall
Cruiser again, with smartcard-related options ticked.
Note: You may use the Dependency Walker software to track DLL dependencies. The
IOPCOM3.DLL can be found in the SYSTEM32 subfolder of your Windows folder.
Instead of repetitively reinstalling Cruiser you may try registering this DLL by the
following command: REGSVR32 IOPCOM3
Question:
Cruiser does not start but can be seen in Task Manager (accessible via ctrl-shift-
esc key combination under Windows XP and Windows 2000).
Answer:
Usually the Microsoft Smart Card Base Components is not working properly, therefore
they have to be reinstalled by means of Cruiser software installer and restart PC. For
an alternative resolution follow this link: MS SCBC Problem Resolution
Question:
Cruiser is unable detect smartcard which is properly connected to the PC, and the
serial number shown is ????-????.
Answer:
Usually the Microsoft Smart Card Base Components is not working properly, therefore
they have to be reinstalled by means of Cruiser software installer and restart PC. For
an alternative resolution follow this link: MS SCBC Problem Resolution
Question:
When starting Cruiser, one of the following error windows pops up:

Answer:
The IOPCOM3 smart card middleware COM server is not registered correctly.
Reinstall Smartcard Middleware by means of Cruiser software installer and restart
PC.
Question:
Old Fighter/Cruiser cable drivers cannot be updated.
Answer:
This problem occurs under Windows XP with Service Pack 1 installed. This is due to
Windows XP Update trying to automatically install XP certified but obsolete VCP
drivers. This problem can be overcome by temporarily disconnecting from the
Internet while installing new drivers or by upgrading to Service Pack 2.
Part
III
53 Working with the Software
3.1 Getting Familiar with Main Window
When you start the Cruiser software, the Main Window appears:
Software edition (either Standard or Pro) is displayed in the left of the bottom status
bar (1). The Cruiser smartcard serial number is displayed to the right (2) of the
software edition.
The toolbar (3) contains an icon for every serial port from 1 to 16, either standard or
virtual. Available ports are marked by yellow color, the rest is marked by grey color.
Connected cable types have to be selected in the Connections Page of the Settings
Window. In Cruiser Standard edition you may open only one port at a time, but in
Cruiser Pro edition you may open up to 16 ports simultaneously depending on the
licence. That means you can operate with more phones at once.
The Rescan button (4) can be used to recheck ports for their availability. If you
connect a cable while running Cruiser, you should click this button to reflect changes.
Never disconnect a cable while Control Window for the respective port is opened.
Otherwise, to enable that virtual port again a system restart will be necessary - this is
a system driver issue.
The Settings button (5), as its name says, opens the Cruiser Settings Window.
By clicking at one of the enabled toolbar port buttons inside the Main Window a
Control Window will appear. Cruiser Pro users are allowed to open more Control
Windows at once. Notice that by opening the first Control Window (5) the Main
Window menu (6) gets extended automatically.
3.2 Getting Familiar with Settings Window
3.2.1 Connections Page
In this page you have to select what cable types you plan to use with Cruiser and
which serial ports (either real or virtual) they will be connected to.
Let us assume, for example, that you are a Pro-edition user and you have the
following cables connected to the PC:
one original Ericsson NTZ112311 cable connected to COM1,
one original Ericsson NTZ112334 cable connected to COM2,
Sony Ericsson SyncStation DSS-20 connected via virtual serial port COM4,
Sony Ericsson SyncStation DSS-25 connected via COM5 (virtual),
Fighter USB Cable connected via COM6 (virtual),
and UC-10 Universal Cable connected via COM7 (virtual).
In such case, you should setup your connections this way:
For each serial port you have eight options:
Fighter USB Cable - The standard USB cable with communication rates up to
3Mbit/s.
UC-10 Universal Cable - The new USB cable.
TMS Cable - TMS cable.
SEMC DSS-20 SyncStation - The original Sony Ericsson synchronization
cradle. Relatively rare.
SEMC DSS-25 SyncStation - Another original Sony Ericsson synchronization
cradle, usually shipped with P900 and P910 smartphones.
Simple Serial Cable (NTZ112311) - The original Ericsson 5V flashing device,
so-called old grey flashing adapter. Non-original cables may be used too, but be
careful to the flash pin voltage.
NTZ112334 Programming Interface - The original Ericsson 3V flashing
device (for T28 and newer phones), so-called green flashing adapter. This device
does not support flashing T66/T600 phone series.
Not connected - Cruiser will completely ignore this port.
3.2.2 Options Page
Use the Options page of the Settings Window to specify your configuration
preferences.
Connection options:
Check box When checked
Force manual ignition (1)
Sometimes you may encounter phones
that cannot be attached (booted)
automatically. This may be caused by
damaged ignition line of the phone
system connector. In this case, select this
option, reopen the respective control
window and keep pressing the power
button periodically. Optionally you may
combine this technique with repeated
battery removal.
Force safe bypass mode (2)
This option is valid for new phones (R520
and up). Phones with damaged system
connector may cause Cruiser to fire the
ignition too frequently. Use this option to
force Cruiser firing the ignition line in 10
second time intervals.
Force safe communication (3)
Safe communication is always selected
when running under Windows 98 or
Windows ME. You may force it when using
Windows 2000 or Windows XP too.
After changing any of these options close and reopen the control window to take
effect.
Special options:
Check box When checked
Enable sounds (4)
Completely enable or disable beeping at
the end of some phone operations like
flashing or uploading data to GDFS.
Auto write zone 1 to GDFS (5)
This is the default setting for Directly
write to GDFS checkbox in Security
AVR tab of Control Window. Check/
uncheck this if you wish to have that box
checked/unchecked when you open the
Control Window.
Disable detach confirmation (6)
Check this if you want to get rid of the
confirmation message-box when
detaching the phone.
Using enhanced cables (7)
Select this if you have cables modified for
use with new Sony Ericsson phones
(K700i and on). To convert your Fighter/
UC-10 cable to an enhanced one, just add
two 10kOhm resistors to the phone
connector, one between pin 4 and pin 11,
the second between pin 6 and pin 11.
Hide unused tabs (8)
When ticked, Cruiser hides Control
Window tabs containing no enabled
buttons.
Beep on booting (5B08...) (9)
Enable or disable beeping just before
sending hardware initialization applet to
5B080201-based phones.
Disable cable type verification (10)
Only for people who are lazy enough to
reinstall their cable drivers to the latest
version.
Generate random codes (11)
An option related to the Control Window
| Security AVR page.
Default button (12):
Use this button to set the options on this page to default settings.
3.2.3 Language Page
Allows changing Control Window language. Cruiser restart is necessary for the change
to take effect.
Indonesian cards are an exception. Users are not allowed to change language from/to
Indonesian.
3.2.4 Authentication Page
e-gate Smartcard Reader (1):
Choose the smartcard reader the Cruiser smartcard will be connected through.
Software restart will be necessary afterwards. This will sometimes be necessary when
you are using more than one piece of software that uses an e-gate Smartcard and
you have both dongles plugged in at the same time.
Authority check bypass algorithm:
You may choose one of the available phone bootstrap bypassing algorithms (2-7).
The selected algorithm affects the speed of phone attaching process.
EMMA Smartcard PIN:
Available for original EMMA card users.
3.2.5 Licensing Page
Use the Licensing page of the Settings Window to change Cruiser SmartCard
parameters. They include the following:
Cruiser software edition - either Standard or Pro,
SmartCard serial number,
maximal allowed number of simultaneous phone connections,
a Trial limit - maximal number of Control Window openings.
To change Cruiser SmartCard parameters an activation key has to be sent to the card.
This key is calculated from the actual card ID and the parameters specified. A new
card ID is generated on every Read card ID button (1) click. Moreover, the card ID
is invalidated by the card automatically after the key is entered to the card. This
means the key is valid only once, what strenghtens SmartCard security against
unauthorized parameter manipulation. Of course, by entering an invalid key or a key
that has been already used with this card before, the card automatically locks
itself (the number of allowed simultaneous phone connections is reset to zero) and
Cruiser Control Window will display a message "Box login failed!".
The activation procedure should look like this:
Be sure to have Cruiser SmartCard connected to your PC.
Press the Read card ID button (1) once. The actual card ID will be displayed in
the box above (2).
DO NOT CLICK THAT BUTTON AGAIN UNTIL YOU RECEIVE AND ENTER THE
ACTIVATION KEY!
Send the card ID together with your requirements to support team via e-mail. You
may shutdown Cruiser software or turn off PC now, if you wish, the activation
procedure will not be affected.
Support team will decide whether your request is valid. If it is, you will receive
an activation key within few hours. You should enter the key into the box (3)
above the Activate button (4) and press this button.
NEVER ENTER ANY ACTIVATION KEY MORE THAN ONCE!
If everything went fine, a message "Activation successful." should be displayed.
Otherwise you have done something wrong and you have to ask for activation again,
or else you will not be able to use Cruiser for working with phones.
3.3 Getting Familiar with Control Window
3.3.1 Primary Page
Phone to be attached (1):
Selects what target is to be attached. You should select one of the four available
options before attaching phone.
Option When checked
Standard (wait)
Use this option for attaching original Sony
Ericsson phones, such as R520m, T39m,
T68i, etc. If the phone booting process
stalls, you should use the "Standard
(don't wait)" option instead.
Standard (don't wait)
To be used with OEM branded phones or
phones that fail to be attached as
"Standard (wait)". Use this option with
R600, T100, T230, etc.
P80x/P90x (PDA-part)
Select this if you want to flash PDA or
Bluetooth part of P80x/P90x/P910.
R380 (PDA-part)
Check this if you want to flash PDA part of
R380s/R380sc/R380e/R380 WORLD.
Select exact phone type (3):
Usually you should leave this at Autodetect and Cruiser will automatically detect
which phone you are trying to attach. If Cruiser is unable to detect it correctly or you
wish to manually force it, you can use the list on the right to select the phone. You
can type some letters into the filter box (2) on the left to narrow down the choices in
the right list. For example, type in T61 into the left box will only show T610, T616
and T618.
Note: If Cruiser can not detect the phone type automatically please write down the
first 6 digits of the IMEI (known as the TAC number) and post a message in the
Support Forum.
Limit baudrate to (4):
Use this to limit the maximum baudrate Cruiser will use when working the phone to
be be attached. This is useful when flashing certain phones at higher speeds does not
work correctly, either due to the phone being unable to accept higher flash speeds or
a faulty cable. Leave this at the default unless you have problems.
Attach comment (5):
This is used only for your own personal records and does not affect Cruiser operation
in any way. Whatever you type in here will be stored in the cruiser.log file that is
created when you attach to the phone. You type anything you like in this field.
Phone connection:
To attach the phone to be able to work with it, you should do the following:
Open the Control Window.
Ensure you have selected correct target to be attached.
Press Attach to phone button. This button starts the phone attaching process.
A phone has to be detached when you finish working with it. To correctly detach a
phone you should:
Preferably press the Turn off phone button, but you may also use the Detach
phone button.
Disconnect phone battery.
Disconnect the cable from your phone.
Boot options:
Options that are specific to phones requiring authority check bypassing - for
engineering use only.
Option Description
ACB parameter (6)
Special parameter affecting the random
number generator used for generating
authority check challenge bytes.
Automatic search (7)
When unchecked, the ACB parameter can
be modified manually.
Use EMMA smartcard (8)
When checked, it allows to use EMMA
smartcard on some occassions. However,
it is not used to its full potential in release
versions of the software.
RSA Boot options:
Used when attaching to a new RSA protected ARM-based phone (K700 and above).
Option Description
Analyze configuration
Tells Cruiser to perform firmware
configuration analysis to prevent damages
to the phone caused by selecting
incompatible phone type. Applicable to
K700 and later phones only.
Force RSA recovery mode
Skips uploading standard flash applet to
the phone and assumes the phone
contains no RSA certificate. Applicable to
RSA protected phones only.
Normal Boot
Usually you would use this, unless there
is a problem with the phone. In this mode
Cruiser will auto detect the CID of the
phone and boot it accordingly.
Normal Boot, any CID, use TP
Use this option when encountering a CID
that's unsupported by Cruiser but using
one of the these chip ID's: 0x7000,
0x7100, 0x8000 and 0x8040. You will
need to attach a Test Point to boot the
phone.
Recovery Boot, Autodetect CID
Use when the phone does not contain an
RSA certificate. Cruiser will auto detect
which CID to boot the phone as.
Recovery Boot, CID=X
Use this when you want to force the
recovery CID Cruiser uses.
Recovery Boot, CID=X, TP
Use this when you want to force the
recovery CID Cruiser uses, you will need
to attach a Test Point.
Phone state (11):
Displays the actual phone state.
Phone type/IMEI (12):
Be sure to have correct phone type displayed here, otherwise Cruiser may refuse to
communicate with phone, or may upload applets targeted for another phone types -
this might have fatal consequences to the internal phone data (e.g. some GDFS
blocks might be erased).
If the IMEI is FFFFFF-FF-FFFFFF-F, it means the flash chip (or EEPROM) does not
contain IMEI. This is common for empty-boards or for phones after flash chip replace.
A similar IMEI, but not containing all F's, for example FEFEFE-FE-FEFEFE-F or
090909-09-090909-0, may signalize damaged flash (or EEPROM) chip, but also
possibly bad soldering, etc.
Current operation status (13):
The actual operation status is shown here.
Operation progress bar / LED indicators (14):
Displays the actual phone operation percentual progess. Red LED lights when
software is waiting for data from the phone. Green LED lights when software is
sending data to the phone.
Messages window (15):
This window displays status of operations.
Error messages window (16):
This window is used for displaying error messages and messages that are very
important to the user.
3.3.2 Flash Page (Old Phones)
LangPack Info:
Before you flash a firmware into the phone you may check which languages it
contains. A table of all available firmwares for the attached phone will be shown, for
each firmware you may read a list of available languages.
Flash AVR:
Write a flash file into the AVR flash chip. Supported formats are FLP and SBN.
Flash ARM:
Write a flash file into the ARM flash chip. Supported formats are FLP and ARM. This
button may be used for P80x/P90x Bluetooth module flashing.
Clear NVRAM:
This button is used to clear the NVRAM in A3618/T100/Z200/J200/J210 phones. The
NVRAM area contains data which may often get messed up due to a not-very-clever
design of these phones. It should usually be cleared after a firmware upgrade.
Clearing NVRAM has a similar effect as performing a master reset. Often, the phone
may get relocked to the network it was previously locked to. This is not to be
considered harmful.
Flash PDA:
Write a flash file into the PDA flash chips. Supported format is FLP. To be able to flash
the PDA part of the smartphone, you need to select the PDA-part to be attached to.
Flash BT:
Use this to flash the Bluetooth part of a P80x/P90x/P910 phone. This button will only
be highlighted when you are attached to the PDA part of a Symbian phone, not when
you are attached to the Phone part.
Flash CR:
Write a flash file into the CR flash chip. Supported format is FLP.
Flash Z80:
Write a flash file into the Z80 flash chip. Supported format is SHX.
Special flash options (6):
Option When checked
Do not erase flash (1)
Disables erasing flash chip before writing
the actual data.
Disable OTP IMEI check (2)
T61x, Z60x, T226, T23x, P90x firmwares
have a feature that checks whether GDFS
IMEI and OTP IMEI are the same. If not,
the phone becomes tampered.
Relock RSA (3)
Cruiser removes the RSA lock when
flashing an AVR-based RSA protected
phone. By checking this option you may
tell Cruiser to not do so.
Flash RSA area only (4)
Tells Cruiser to flash the RSA area only. It
takes a significantly shorter time than
flashing a full firmware. Applicable to
AVR-based phones only.
Turn on charger while flashing (5) Not enabled in this version.
3.3.3 Flash Page (New Phones)
Repair EROM
This is used to repair the EROM (Extended ROM) in V800/Z800, K750/W800/Z520,
W550/W600 and later phones. If Cruiser displays the following message when
attaching to the phone you should use this button:
The phone contains recovery certificate!
You MUST repair EROM!
Flash ARM:
Use this to flash the ARM (Main firmware) into the attached phone.
Write raw FS:
Use this to upload a File System (a raw flash image) into the phone.
Using this option will erase all user data in the phone. After upgrading the firmware in
a phone (using the Flash ARM option) it is necessary to write an updated File System
to the phone using either this option or a Signed File Archive (SFA)
Upload signed archive:
Use this to upgrade the File System of a phone without erasing the user data
contents. There are not many SFA (Signed File Archive) files available at the moment
however.
Customize FS:
After writing a raw FS file to the phone, the File System has to be (usually)
customized.
The customization process enables specific phone languages and performs many
small tasks to make the phone usable.
There are two options that should be specified before customizing the phone - Region
(4) and Firmware version (5). Both of them should match the previously flashed raw
FS parameters.
If the phone displays a "Configuration error..." message, the File System
must be customized.
Option When checked
Flash via EPI USB (1)
Tick this to flash phones via the mini USB
cable that comes with the phone (only
some phones have this). This is usually
faster than the standard method of
flashing the phone, but only functions for
writing the Main firmware and Raw FS
to the phone.
After you have flashed via the EPI
interface, you will have to remove and
replace the battery to be able to reattach
to the phone.
Overwrite flash certificate (2)
By default Cruiser tries to avoid potential
problems caused by overwriting the
certificate that is located in phone flash
chip. Especially writing a certificate
having a CID lower than the OTP CID
causes booting problems. By ticking this
option you turn off this safety feature.
Remove RSA certificate (3)
Completely removes the flash certificate
when flashing. This option is made
available upon request.
3.3.4 File System Page
Upload files to FS:
This button may be used to upload files into phone's file system.
Unless you tick Force to folder (2) and type in a correct target folder to the box (1)
above, Cruiser will decide itself where to upload the files to. This automatic feature
should be used for user files like MP3, JPG, etc only. In other cases you need to tick
the Force to folder (2) option and type in the target folder.
If you tick the Upload files from file package option, Cruiser will ask you to select
a CFP (Cruiser File Package) file that will be unpacked and the files will be put to their
correct positions in phone's file system.
Download files from FS:
This function allows you to download files from phone's file system located in the
folder specified by the box (4) right to the button.
To download all subfolders just tick the Recurse subfolders option.
To let Cruiser create a single CFP (Cruiser File Package) file instead of many
individual files, tick the Create file package option.
Language operations:
This function allows you to upload/download/remove language files and to remove T9
files according to what is selected in the box (7) to the right.
Camera sound on/off:
May be used to disable/enable the annoying camera shutter sound.
Shutdown FS:
At the end of modifying the phone file system area press the Shutdown FS button to
keep file system in a consistent state and to turn the phone off. Alternatively you
may click the Turn off phone button in the Primary page or press Ctrl-O key
combination.
3.3.5 Locks Page
Read codes:
Use this button to read all unlocking/locking codes from the phone. For T66 and T600
phones, the phonelock is not displayed, use the Clear phonelock button in the case
you want to remove it.
Clear phonelock:
Removes the user's phonelock and sets it to 0000. For a T66/T600 you need to have
a cable with proper autoignition.
Direct unlock:
Directly unlocks the network locks and user's phonelock.
Lock to network:
Relocks the phone to a network specified by the respective MCC/MNC codes in the box
(1) below. A three digit long MNC code may be used too, just check the MNC3 box (2)
before clicking the button.
Unlock by patching: This button enables unlocking of new LG and Sharp phones via
patching of the firmware. Use it to unlock new LG and Sharp phones.
Upgrade security:
Upgrades security zone to the latest format to be able to flash the latest firmwares
provided. This option is available for older phones like GH688, SH888, A1018, T1x,
T28 and R3x0.
Save security:
Backups the GDFS security zone to a file. To restore it use the Restore security
button or the Write GDFS button.
Restore security:
Restores the security zone created using the Save security function.
Check security:
Checks the GDFS security zone for potential damages. It can find out what is wrong
with the security zone and what was it caused by.
Recalc DCRCs:
DCRCs are some kind of digital signatures protecting the security zone against
unauthorized modifications. They are part of the GDFS security zone and if they
contain invalid data, the phone becomes tampered (or four-locks-closed).
Unterminate:
This function repairs the tampered problem (4-locks-closed problem) caused
intentionally by Zulea's Terminator software (with box at LPT, cable at box). The
SoftMobile's Terminator (with box at LPT, but cable at COM) does not cause the four-
locks-closed problem.
The Ignore marker checkbox (3) can be used to force security zone decryption when
the marker is not present.
However, this function is obsolete and Rebuild security zone function should be
used instead.
3.3.6 Security AVR Page
This page can be used to fully rebuild GDFS security zone of T68, T62, T20x,
T3xx, T61x, T63x, Z60x, P80x, P90x, T226 and T23x phones by either writing the
new GDFS security zone into an .MDC file or directly into the GDFS area (default).
The GDFS security zone of these phones consists of:
phone IMEI, so called GDFS IMEI,
frequency band lock,
network personalization data (MCC+MNC, GID1, GID2,...),
network unlocking/locking keys (NCK, NSCK,...) and
some kind of digital signatures (DCRC1, DCRC2, SCRC) that protect the security
zone against modification. The SCRC signature is bound also to the main AVR
ASIC ID.
An invalid security zone content results in a tampered phone - so called four-
locks-closed problem. Note that newer phones (T61x, T63x, Z60x, P90x,
T226 and T23x) also perform checking whether the GDFS IMEI matches the
OTP IMEI (One Time Programmable) stored in the OTP area of the AVR flash
chip. If these numbers are not equal, result is again a tampered phone. In
this case you might consider flashing the AVR firmware using the Disable
OTP IMEI check option selected. To rebuild the security zone, just
fill in the desired zone parameters (1-10),
select whether you wish to write the newly created zone directly to GDFS (12) or
into a MDC file that can be written to the GDFS later and
press the Create security zone button.
You may create more different security zone files in a row, if necessary.
If the OTP IMEI was not programmed already (i.e. the OTP IMEI is FFFFFF-FF-FFFFFF-
F, which is common for empty-boards or for phones after AVR flash chip replace), you
have also the option to program the OTP IMEI (13). An attempt to rewrite an already
programmed OTP IMEI will be simply ignored.
3.3.7 Security RSA Page
This tab will only appear when attaching to new RSA protected phones (K700 and
above).
Unlock RSA:
The heart of Cruiser. Use this button to remove the phones RSA protection. Once the
RSA protection is removed you will be able to flash Raw File System, perform GDFS
modifications and other functions that are not allowed when RSA protection is active.
GDFS Security Zone
Bandlock:
Use this to change the bandlock of the phone (what networks it thinks it can connect
to). This should not be changed unless you are fully aware of what you're doing,
mostly changing this would also require hardware and firmware changes.
Format Security Zone:
Ticking this will format the security zone in the phone. This is useful to repair damage
after a bad unlock with another tool or if the phone is unable to find network after
flashing.
Write Bandlock:
Ticking this will write the selected bandlock (above) to the phone.
Recalculate CRCs:
Ticking this will recalculate the CRCs in the phone that are used to verify the security
zone is valid and has not been tampered with. Use this to repair damage after a bad
unlock or something else.
Write to security zone
Will write the perform the above selections on the phone's security zone.
Flash Certificate
Repair Certificate
This must be used if the phone has no valid certificate in it. This is usually the case
when you have had to boot to the phone with Recovery Boot option selected.
This function overwrites EROM in phones that have an EROM area present or the
beginning of the main firmware of phones that haven't an EROM area.
After successful certificate repair you'll have to turn the phone off and reattach it in
Normal mode. Then you'll have to either repair EROM or to reflash main firmware.
Replace Certificate:
This is used to change the primary certificate in the phone. Using this you can change
the CID and the colour of the certificate. Phones with CID36 or higher must be
converted to brown before unlock/code read is possible. CID37 or higher phones must
also be converted back to red once servicing is finished, otherwise they will not power
on. Alternatively, instead of conversting them back to red it is possible to repair
EROM to make them functional again.
3.3.8 GDFS Page
The GDFS may be logically divided into few separate zones (1):
Security data
Battery calibration
Display calibration
Audio calibration
Radio frequency calibration
Phonebook
SMS/e-mail/MMS data
Picture data
Sound data
Organizer data
To read a subset of these zones you may use Read GDFS zones button. To select
which zones will be saved to the file you should check or uncheck items in the GDFS
zone selection list (1).
To write data into GDFS (for example a GDFS backup created using Read GDFS
zones button or an upgrade data) you should use the Write to GDFS from file
button. This function protects the GDFS security zone content by default. To enable
writing data to security zone, untick the box below (4). To disable backing up the
security zone before writing anything to the GDFS, you may untick the
Automatically backup... box below (5).
To modify the phone GDFS content by one of the built-in functions you should use
the Modify GDFS button. Before clicking it you have to select which modification you
wish to apply. To do so, use the modification select box (2). Optionally you may
specify a textual parameter in the box (3) below.
For example, if you would like to change the phone descriptor, simply select the Set
phone descriptor item and to the parameter box type the desired phone descriptor
string. Note that the list of available GDFS modifications depends on the
attached phone model. For example, in case of an R520m phone type attached, a
part of it may look like this:
To finish GDFS content manipulation you should press the Finalize GDFS button.
It flushes the internal GDFS applet cache and turns the phone off. Alternatively you
may press the Turn off phone button on the Primary page or to press Ctrl-O key
combination.
Format GDFS:
This will format the GDFS of new RSA based phones. Use this only as a very last
resort when GDFS corruption has occurred in the phone - it irreversibly erases all
phone calibration data (charging, RF,...).
The password is "KILL THE PHONE" without quotes. You will need to flash a new GDFS
to the phone and directly unlocking the phone after using this option.
Be sure to check the support area has GDFS for the phone, before using this
option.
3.3.9 Read Flash Page
Read AVR:
Read an AVR flash region defined by AVR flash zone selection box and save it to a FLP
file. You can save the whole GDFS into a FLP file using this function. If you wish to
write such file back to the phone, use Flash AVR button instead of Write to GDFS
from file button that handles writing of MDC files instead of FLP files.
Read ARM:
Read an ARM flash region defined by ARM flash zone selection box (1) and save it to a
FLP file. The created flash file can be written to the phone using Flash ARM button.
Currently not released to public.
Read PDA:
Read a PDA flash region defined by PDA flash zone selection box and save it to a FLP
file. The created flash file can be written to the phone using Flash PDA button.
Currently not released to public.
Read CR:
Read a CR flash region defined by CR flash zone selection box and save it to a FLP
file. Currently not implemented.
Read Z80:
Read a Z80 flash region defined by Z80 flash zone selection box and save it to a SHX
file. Currently not implemented.
3.3.10 Extras Page
Charger ON:
Turns on charging by providing 5V to phone's charging pin. If the phone has damaged
firmware or GDFS, no charging will occur.
Charger OFF:
Turns off charging voltage.
Measure Batt. Voltage:
Not implemented.
Start Debug Log:
A very useful phone diagnostic tool. Forces the phone to send out many debug
messages that can be used to trace phone problems. Read below.
Stop Debug Log:
Stops logging debug messages.
Debug Log Usage:
Connect a turned off phone to the cable.
Press Start Debug Log button and choose an output text file.
Press phone's power-on button. The phone should then turn on.
Wait about cca 1 minute, then turn the phone off.
Press Stop Debug Log button.
Open the file from step 2 in any text-editor and read it.
3.3.11 IMEI Page
Note: This page is shown only if you have the Identity Change support installed.
OTP Area Programming:
Use these three fields only when programming an emptyboard RSA phone.
IMEI (1):
The IMEI you wish the phone to have.
CID (2):
The CID you wish the phone to make. Make sure it is correct for the phone type you'll
be programming.
Product Flag (3):
Can either be Developer or Retail. This should almost always be set to Retail when
programming an emptyboard.
Lock OTP area:
Irreversibly writes previously defined values (1-3) to the flash OTP area.
GDFS IMEI Programming:
This area is used to change or rebuild the IMEI of new RSA phones.
GDFS IMEI (4):
Insert in here the IMEI you wish to program to the phone, or tick the button labelled
Use OTP IMEI instead (5) to program the IMEI from the OTP into the GDFS.
Write GDFS IMEI:
This will write the selected IMEI into the GDFS
Disable OTP IMEI check:
Click this button to disable (via patching) the phone firmware's built in OTP
IMEI=GDFS IMEI check. This can be used to change IMEI on phones without getting
all locks closed.
Enable OTP IMEI check:
Click this to remove the patch and reenable OTP IMEI=GDFS IMEI checking.
Question:
Why Cruiser does not work with Remote Desktop under Windows XP?
Answer:
Remote Desktop redirects smartcard calls to the client. Therefore do not use Remote
Desktop. Use Remote Admin, VNC, RealVNC, NetOp Remote or whatever else instead.
Question:
Strange communication errors occur.
Answer:
You are probably using a bus-powered USB hub which cannot supply enough power to
the phone. Try connecting the cable directly to the PC or via a self-powered USB hub.
Question:
I am using an USB cable or an original DSS-25, but it only works with a baudrate
limited to 460800Bd.
Answer:
This problem is very rare, but when it happens it usually occurs when the user has
connected the cable to a USB hub. Try connecting the cable directly to the computer
to see if it makes any difference.
Question:
Why cannot be CHM files (like Cruiser help file) viewed under Windows 98/ME?
Answer:
This problem should not occur on healthy systems, but if it does, you may get
necessary updates by means of service packs or Windows Update. Earlier installers
provided the HTML help update functionality, but we decided to remove it.
Windows XP and 2000 users can get updates from Microsoft Windows Update.
Windows ME users can get updates from Windows ME Update.
Windows 98 users can get updates from the 811630 Security Update page.
Part
IV
79 Phones ARM 2004/2005
4 Phones ARM 2004/2005
This group consists of the following sets:
K600i, K600c, K608i, V600i, V800, V802SE, Z800i, Z800c, W900i, W900c,
Z1010i, Z1010c,
F500i, J300i, J300c, J300a, K300i, K300c, K300a, K500i, K500c, K506c, K508i,
K508c, K700i, K700c, S700i, S700c, S710a, Z500i, Z500c, Z500a,
D750i, K750i, K750c, K758c, W550i, W550c, W600i, W800i, W800c, W810i,
W810c, Z520i, Z520c, Z520a.
Phones of the first set are based on a baseband chip (CPU) with ID of 0x7100 (and
rarely 0x7000).
Phones of the second set are based on a CPU with ID of 0x8000.
Phones of the third set are based on a CPU with ID of 0x8040 (and rarely 0x8000).
Almost all phones that started to be produced during the year 2005 contain a special
flash area called EROM (Extended ROM).
These include all phones from the third set and the first set except Z1010 phones.
The latest phones (like W550i, W550c, W600i, W810i, W810c, W900i and W900c)
support firmware upgrading from the phone menu (unless the phone provider has
disabled to do so).
For this purpose, they contain a software part called FOTA User Agent (Flash Over
The Air).
All these phones are protected by an RSA-based security scheme. It is difficult to
overcome this security, we have to search for implementation bugs in original
loaders.
Much more important than the phone type is a feature called CID (Customer ID).
Higher CID value usually means less bugs in loaders and therefore stronger security.
So far, these CIDs have been issued for Sony Ericsson phones: 16, 29, 36, 37, 49,
50, 51, 52 and 53.
To see a complete list of allocated CIDs take a look here.
Another parameter, one should know of, is the flash certificate color:
Blue - indicates factory usage,
Brown - indicates developer usage,
Red - indicates product usage.
The security is strongest with Red flash certificate color, that is why we usually
convert "Red phones" to "Brown ones".
Another issue worth noting is that phone manufacturers took some countermeasures
against us and disabled firmware startup when certificate change is detected.
This is usually the case with CID37 and later phones. Such phones manifest by a
blinking charging LED when attempting to power them on.
It is therefore necessary to restore the flash certificate, to repair EROM or to
flash EROM files prepared by us.
4.1 Change LanguagePack
Please remember a Full flash will delete all user data stored in the phone (but not
data on the Sim Card or MemoryStick).
Attach to the phone and check what CID and Color Cruiser reports the phone as
being. If you are unsure what this means, read the FAQ in this manual about it.
If the phone is CID29 or lower please skip to step 5.
If the phone is CID36 or greater you will need to convert the phone to Brown
before RSA can be unlocked. Go to the Security RSA tab and pull down the
menu under Replace Certificate. Find the SAME CID as your phone currently
has but brown. Click on Replace Certificate. Once this operation has
completed, you will need to reattach the phone.
If you have not already done so, reattach the phone. Confirm the Flash
Certificate in the phone is now Brown.
Go to the Security RSA tab and click on Unlock RSA. This button is a key part
of the Cruiser system, RSA must be unlocked before most operations can be
performed on the phone. Once RSA has been unlocked, Cruiser will
automatically detach the phone.
Reattach to the phone and go to the Flash tab.
Read the How-To entitled Choosing Flash Files if you are unsure what files you
should be flashing to the phone.
Never attempt to flash files into a phone that are not for it, for example
DO NOT flash S700 files into a S710.
Just because the numbers are almost the same does not mean the hardware in
the phones is. Doing this without being sure it will work (and for very few
phones it does work) will result in a dead phone that can be hard to fix.
Click on Flash ARM and flash an ARM file specific to that phone.
If you have a phone with a EPI connector (little USB plug) you may also plug
that in and click on Flash via EPI USB for faster flashing times. You do not
remove the current cable to flash via EPI; you leave the Cruiser cable plugged in
and add the EPI cable to the phone so there are two cables.
If you flashed via EPI you will need to detach the phone, remove the battery and
replace it, then reattach to the phone. If flashed via the normal cable, you will
not need to do this.
Now click on Write raw FS and flash a matching Raw File System to the phone.
Now you must Customize the phone. Customizing loads important settings and
certificates into the phone, without this step you will usually receive the
"Configuration Error" when you try to use the phone.
From the menu under the Customize FS button, select an option that matches
the Langpack you choose for the Raw FS. So if you are flashing a Z800 and you
flashed Raw FS EU5 into the phone, you would select Z800 EU5 as the
customization. In the text entry field to the right, type in the Firmware version
you have flashed to the phone, for example R1AB014.
Click the Customize FS button and wait for it to complete.
If you wish, you may go to the File System tab and disable the Camera Sound
by clicking the Camera Icon.
From the File System tab, select the Shutdown FS button.
Alternatively you may click the Turn off the phone button or simply press Ctrl-
O key combination.
Cruiser will automatically detach the phone.
To fully complete the job, you should convert the phone back to Red. This step is
necessary if the phone is CID37 or higher (otherwise the phone will not power
81 Phones ARM 2004/2005
on) but should be done anyway to complete the job professionally.
Reattach to the phone. To go the Security RSA tab and under Replace
Certificate find the same CID as the phone is, but Red certificate. Click on
Replace Certificate.
The phone is now fully flashed, insert a SIM Card and wait for it to boot up (it
will take a few minutes after the Raw File System has been flashed to it).
How do I choose which Flash File to Flash?
There are many different files in the Support Area and it can be hard to know which
to choose. The main thing is to pick the latest version as this almost always will
perform better on the phone in terms of bugfixes etc. The SE Firmware numbering
system goes like this R-number-letters-numbers. For example, R1Y005 is a valid
Z800i firmware. R1AB014 would be a later version, because AB is greater than Y in
SE terms. A later still firmware would be R2Y004, because the first number is now 2.
R1A003R1J003R1AB013R2Z005 is an example of firmware upgrade paths.
Once you have looked and found the latest version on the support site, you then need
to select if you want the standard Unbranded SE Firmware or if you want to keep the
branding the phone has. All EU1 Main Firmwares (except for V800/V802SE) are the
Sony Ericsson unbranded firmwares.
Once you've picked which type of main firmware you want, you then have to select
which languages you want the phone to support. Please look at the langpack page to
choose which langpack has the correct language.
In the end you should end up with 2 files downloaded. The Main Firmware, for
example
Z800_CXC1250046_EU1_R1AB014_Red36.cz8sw
and the Raw File System file,
Z800_CXC1250055_Europe3_R1AB014_Red36.cz8fs
4.2 Change LanguagePack (red CID49, non TP)
Newer phones with locked-down EROM area:
Connect the phone to the cable and select Normal boot.
Attach Cruiser to the phone.
Go to the Security RSA page and press the Unlock RSA button. Remove
battery when asked by Cruiser.
This will overwrite part of main firmware by special code thus causing the phone
to appear "dead".
Reinsert the battery and reattach Cruiser to the phone.
Go to the Security RSA page and press the Restore firmware button. Cruiser
will search for a restore file then. It does not matter if it fails.
Now flash main FW and raw FS files to the phone.
Remember to customize the FS too, otherwise you would get a "Configuration
error..." message on phone startup.
Turn the phone off.
Note: You may use the Ctrl-A key combination to attach the phone and the Ctrl-O
key combination to turn the phone off.
4.3 Upgrade Firmware
Note: You will need a SFA file for the Firmware you are using! There are not many
SFA files available, so usually a Change LanguagPack is required (which deletes all
user data).
To upgrade the Firmware of the phone without removing all user data, please follow
the procedure for a Change LanguagePack, but do not follow steps 10, 11 or 12.
Instead, replace those steps with this step:
Go to the Flash tab, select Upload signed archive and select the SFA file that
matches the Main Firmware you flashed to the phone. Once finished, please continue
from step 13 below.
4.4 Unlock
Direct Unlock
Attach to the phone and check what CID and Color Cruiser reports the phone as
being. If you are unsure what this means, read the FAQ in this manual about it.
If the phone is CID16 or CID29, please skip the following 2 steps.
If the phone is CID36 or greater you will need to convert the phone to Brown
before you are able to unlock it.
Go to the Security RSA tab and pull down the menu under Replace Certificate
. Find the same CID as your phone currently has but brown. Click on Replace
Certificate. Once this operation has completed, you will need to reattach the
phone.
If you have not already done so, reattach the phone. Confirm the Flash
Certificate in the phone is now Brown.
Go to the Locks tab and click on Direct Unlock. If you prefer you may instead
click Read Codes to retrieve unlock codes from the phone.
If the phone was CID37 or higher, you must convert it back to Red before it will
power on.
How do I Unlock via Codes?
If you prefer to unlock via codes, once you have followed the steps above and
retrieved the codes from the phone, you must then insert a SIM Card into the
phone and power it on.
When the phone is on, either at the "Insert Correct SIM Card" message or the
standby screen, press <**< on the phone's keypad (where < means press left on
the joystick).
This will bring up a menu from which you can enter the correct unlock code into
the phone.
4.5 Unlock Red CID49 Phones without TP
Older phones with unlocked EROM area:
Go to the Security RSA page and replace the certificate by Brown CID49.
Remove battery when asked by Cruiser. If this process fails, the phone has a
locked-down EROM area and therefore it cannot be converted to Brown CID49.
83 Phones ARM 2004/2005
Now press the Direct Unlock button.
Newer phones with locked-down EROM area:
Be sure to have installed the latest Cruiser firmware restoral package from our
support area.
Go to the Security RSA page and press the Unlock RSA button. Remove
battery when asked by Cruiser.
This will overwrite part of main firmware by special code thus causing the phone
to appear "dead".
Reinsert the battery and reattach Cruiser to the phone.
Go to the Security RSA page and press the Restore firmware button. Cruiser
will search for a restore file then. If it cannot be found, you will also have to
reflash main FW and raw FS and to customize the phone.
Now go to the Locks page and press the Direct unlock button. Remember, if
you encounter any new firmware it is wise to make a security zone backup too
(or a full GDFS backup).
Note: You may use the Ctrl-A key combination to attach the phone and the Ctrl-O
key combination to turn the phone off.
4.6 Unlock Red CID49 Phones via TP
Note: This method works for newer K600, K608, V600, W550, W600 and W900
phones. It doesn't work with W810/Z530 phones.
Connect the phone to the cable and select Normal boot, any CID, use TP.
Attach Cruiser to the phone using TP.
Replace the certificate by Brown CID49.
Reattach the phone without testpoint by selecting Normal boot and press the
Repair EROM button.
Now press the Direct Unlock button.
4.7 Change IMEI
Be sure to have the Identity change support installed.
Attach the phone and convert it to brown.
Reattach and Unlock RSA.
Reattach and go to the IMEI tab. Press the Disable OTP IMEI Check button.
If the operation succeeds, change last 6 digits of the IMEI in the GDFS IMEI
edit box. Then press the Write GDFS IMEI button.
4.8 Enable GSM/3G Selection Menu
Attach the phone.
Go to the GDFS page.
Choose Enable GSM/3G selection menu from the Modify GDFS options list
and then press the Modify GDFS button.
4.9 Repair Keypad not Working Problem
Attach the phone.
Go to the GDFS page.
Choose Apply Language Lock patch from the Modify GDFS options list and
then press the Modify GDFS button.
4.10 Extra Files
4.10.1 EROM Files with Color Conversion
File Name Description
DB2000_EROMRed36_signed_by_Brown3
6.erom1
An EROM file for conversion from brown
CID36 to red CID36. This file may be used
with V800, Z800, K600, K608 and V600
phones.
7.erom1
with K608 phones.
9.erom1
with K608 phones.
6.erom2
with K750, D750, W800 and Z520
phones.
DB2010_W550W600_EROMRed49_signe
d_by_Brown49.erom4
An EROM file (with FOTA support) for
conversion from brown CID49 to red
CID49. This file may be used with W550,
W600 and S600 (not Mulan) phones.
DB2000_W900_EROMRed49_signed_by_
Brown49.erom3
An EROM file (with FOTA support) for
conversion from brown CID49 to red
CID49. This file may be used with W900
phones.
DB2010_W810_EROMBrown49_signed_b
y_Brown49.erom4
A brown CID49 EROM file (with FOTA
support). This file may be used with
W810 phones.
These files are usually located in the "c:\Program Files\Cruiser\Special Flashes
\EROM" folder.
4.10.2 FOTA User Agent Repair Files
Link (local) Description
DB2010_W550W600_FOTAUserAgent_R2
B012_Brown49.erom4
A brown CID49 FOTA User Agent repair
file for W550, W600 and S600 (not
Mulan) phones.
DB2000_W900_FOTAUserAgent_R2B022
_Brown49.erom3
file for W900 phones.
85 Phones ARM 2004/2005
DB2010_W810_FOTAUserAgent_R3B004
_Brown49.erom4
file for W810 phones.
These files are usually located in the "c:\Program Files\Cruiser\Special Flashes
\FOTA" folder.
Note: FOTA stands for Flash Over The Air.
4.11 Testpoint Pictures
4.11.1 K300/K500/K700 CID Testpoint
Just connect the testpoint to GND when asked by Cruiser. Then simply disconnect it
when Cruiser prompts you to do so.
Figure 1. Larger PCB view
Figure 2. K300/K500/K700 testpoint detail.
4.11.2 K600/K608/V600 CID Testpoint
This testpoint may be used to unlock red CID49 phones and to convert them to brown
CID49 to allow langpack change without utilizing an EMMA II smartcard.
Figure 2. K600/K608/V600 testpoint #1 detail.
Figure 3. K600/K608/V600 testpoint #2 and #3 detail.
87 Phones ARM 2004/2005
Figure 4. K600/K608/V600 testpoint #4 detail.
Note: Thanks to tiri piri and to MOBICOM for providing new V/K60x testpoint
pictures (the last two) that were clean enough.
4.11.3 V800/Z800 CID Testpoint
Just connect the testpoint TP1 to GND when asked by Cruiser. Then simply disconnect
it when Cruiser prompts you to do so. The testpoint TP2 may be used only when TP1
is covered by glue.
Figure 1. Larger V800/Z800 PCB view
Figure 2. V800/Z800 testpoint detail
Figure 3. V800/Z800 opening hint - just examine the joint
89 Phones ARM 2004/2005
4.11.4 W550 CID Testpoint
Figure 1. Larger W550 PCB view
Figure 2. W550 testpoint detail
91 Phones ARM 2004/2005
Question:
What does "Configuration Error..." message mean and how do I fix it?
Answer:
This means that the phone's File System has not been customized. Customization
uploads settings and certificates required by the phone. Go to the Flash tab, pull
down the Menu under the Customise FS button and select the option closest to the
File System contained in the phone. Then press the Customise FS button.
Question:
I unlocked my phone, but now it will not power on.
Answer:
If the phone is CID37 or higher, you must convert back from Brown to Red otherwise
the phone will not power on. It is because the new EROMs check whether the flash
certificate has been changed. If yes, instead of starting the phone firmware up, they
just let the charging LED blink. Alternatively you may use the Repair EROM function
as well.
Question:
When I try to attach to the phone, it just powers on.
Answer:
This is either a problem with your cable, or the phone itself. At first for a couple of
times try this:
Press the Attach to phone button,
then insert the cable connector to the phone,
and finally insert battery to the phone.
If this does not work, open the phone up and check for signs of corrosion on the
connector.
Question:
I unlocked RSA but the phone still will only accept some SIM Cards (it's still locked!)
Answer:
This is a common mistake first time Cruiser users make. RSA Unlock is not related to
removing SIM locks. RSA unlock removes the Sony Ericsson protection on the phone,
so that Cruiser is able to perform operations on the phone such as flashing a new Raw
File System or performing GDFS modifications. You do not need to Remove RSA to
Remove SIM Locks.
Question:
I need a recovery certificate for X type of phone! Where can I download it?
Answer:
All available recovery certificates are now built into Cruiser. You do not need to
download them. Under RSA Boot Options on the Primary tab, you can select Boot
Type. Instead of Normal Boot select one of the Recovery Boot options. Once
attached, go to the Security RSA tab and click on Repair Certificate. Click on the
Repair Certificate button is exactly the same as flashing a Recovery File to the
phone.
There is a common misunderstanding that Recovery File will magically fix a badly
flashed phone. This is not the case, the Recovery File just contains a special
certificate that allows the phone to then be reflashed with a properly signed flash file.
It is not a magic "Recover Broken Phone" file.
After using this function you will have to repair EROM or to reflash main firmware (in
phones that do not have EROM area).
Question:
What does CID/Color mean?
Answer:
CID stands for Customer Identity.
Red = normal phone
Brown = developer phone
Blue = usually means phone in unfinished state. You should not change the
phone to this unless you have good reason to.
The combination of CID and Color determines (is determined by) what certificate is
stored in your phone. Almost all retail phones are Red in color, with a CID number of
either 16, 29, 36, 37 or 49 (for Sony Ericsson phones) though others do exist.
As the CID numbers gets higher, the security protection on each certificate has been
made harder and harder. CID29 phones are very easy to work with/unlock, while
CID49 phones have only just been cracked and still have to be converted to brown
before unlock is possible.
Question:
My phone reports No Color/CID! What is the problem?
Answer:
If the Repair Certificate function does not work or the phone can not be booted
even in Recovery mode, it is almost always caused by hardware/flash chip failure in
the phone.
Question:
I unlocked a Z520 and it cannot be turned on anymore.
Answer:
Detach the phone from cable, remove battery for 20 seconds, insert it back and try to
turn the phone on.
Part
V
5 Phones ARM 2001/2003
This group consists of the following models:
A3618s, A3618sc, R600s, R600sc, T100, T102, T105, T106, Z200, Z208, J200i,
J200c, J210i and J210c.
5.1 Unlock by Using Codes
Note: Applicable to A3618, R600, T10x and J210.
Check phone locking status using the <**< key sequence. For every network lock
you can see an icon describing its lock status (either locked or unlocked). If you
will see all four locks closed, the phone probably cannot be unlocked this way.
Turn off the phone and attach Cruiser to the phone.
Go to the Locks page of the Control Window, press the Read codes button.
Wait a while. All unlocking codes will be then shown. The phone will be detached
and turned off automatically.
Turn the phone on again and by using the <**< key sequence enter the
respective codes.
5.2 Repair J210
If possible, use original DSS-25 or DSS-20 cradle instead of Cruiser cable.
Flash the file J210i_Repair_v2.ARM.flp to the phone.
Reattach as J200i (this is important) and press the Recalc DCRCs button.
Part
VI
6 Phones AVR 2003
This group consists of the following sets:
T226, T226, T230, T237, T238, T290i, T290c and T290a,
T610, T616, T618, T628, T630, T637, Z600 and Z608.
Phones from the first set contain only one processor (AVR),
whereas phones from the second set contain two processors (AVR and ARM), and
therefore their firmwares consist of two respective parts.
Another difference between these sets lies in GDFS (Global Data Flash Storage) area
location.
Phones of the first set have GDFS area located in the AVR flash chip.
Phones of the second set use a dedicated GDFS flash chip of 4MB.
If the phone is a T22x/T23x/T290, follow these steps:
Check phone firmware version using the >*<<*<* key sequence.
Go to the Flash page of the Control Window. You may see what languagepacks
are available for the phone by clicking the LangPack Info button in the Control
Window.
Click Flash AVR button, select the file containing the AVR firmware with the
desired languagepack and press OK. Wait until the flash file gets transferred
into the phone.
Detach the phone by clicking the Detach phone button in the Primary page of
Control Window, removing the battery from the phone and disconnecting the
phone from cable.
If the phone is a T61x/T62x/T63x/Z60x, follow these steps:
Check phone firmware version using the >*<<*<* key sequence. If the phone
menu freezes, there is usually something wrong with the ARM part of phone
firmware.
Go to the Flash page of the Control Window. You may see what languagepacks
are available for the phone by clicking the LangPack Info button in the Control
Window.
Click Flash AVR button, select the file containing the AVR firmware part with
the desired languagepack and press OK. Wait until the flash file gets transferred
into the phone.
Click Flash ARM button, select the file containing the ARM firmware part and
press OK. Wait until the flash file gets transferred into the phone.
phone from cable.
97 Phones AVR 2003
6.2 Unlock
Go to the Security AVR page of the Control Window.
Ensure yourself the option Directly write to GDFS is checked (otherwise an
MDC file would be created instead of direct writing to GDFS).
Press the Create security zone button.
Detach the phone by clicking the Finalize GDFS button in the GDFS page of
phone from cable.
6.3 Rebuild Security Zone
You may change any of the AVR security zone parameters. These include: phone
IMEI, network unlocking codes, network code, number of unlocking attempts,
frequency bandlock and a few other options.
phone from cable.
6.4 Decustomize
menu freezes, there is usually something wrong with the ARM part of the phone
firmware.
Go to the GDFS page of the Control Window. Press Write to GDFS from file
button, a file-open dialog appears.
Choose the decustomization file according to the phone type and press OK.
Phone type File to be used
T226 T226_decustomize.mdc
T230
T230_WorldGeneric_CDA102265_R
2A.mdc
T237 T237_decustomize_v2.mdc
T238
T230_WorldGeneric_CDA102265_R
2A.mdc
T290i
T290i_World_Generic_CDA102352-
1_R3A.mdc
T610
T610_WorldGeneric_CDA102215-
1_R26A.mdc
T618
1_R26A.mdc
T628
7_R2A.mdc
T630
7_R2A.mdc
Z600
Z600_WorldGeneric_CDA102233-
1_R8A.mdc
Wait until the GDFS file gets transferred to the phone.
phone from cable.
6.5 Repair T630 Network Problem
This problem may arise after downgrading an R7A011 firmware version to R6C005 or
lower.
Flash phone with R7A011 firmware
Then go to the GDFS tab, choose Fix no network problem from the Modify
GDFS options list and then press the Modify GDFS button.
Part
VII
7 Phones AVR 2001
R300z, R520m, R520mc, T200, T202, T300, T302, T306, T310, T310c, T312, T316,
T39m, T39mc, T61z, T62u, T65s, T65sc, T68i, T68ie, T68m, and T68mc.
Go to the Write Flash page of the Control Window. You may see what
languagepacks are available for the phone by clicking the LangPack Info
button in the Control Window. The page describing all possible languagepacks
for the phones should open.
Click the Flash AVR button, select file containing the AVR firmware with the
desired languagepack and press OK. Wait until the flash file gets transferred
into the phone.
If your phone is a R520, T39, T65, or T68, you'll also need to flash the ARM
firmware part to the phone. In that case click Flash ARM button, select the file
containing the corresponding ARM firmware part and press OK. Wait until the
flash file gets transferred into the phone.
phone from cable.
7.2 Unlock by Codes
Go to the Locks page of the Control Window.
Press Read codes button and wait a while. All unlocking codes will be shown.
phone from cable.
Turn the phone on again and using the <**< key sequence enter the respective
codes.
7.3 Check Security Zone
Press Check security button and wait a while. The GDFS security zone will be
analyzed.
phone from cable.
101 Phones AVR 2001
phone from cable.
7.5 Convert T68m to T68i
To convert a T68m/T68mc into T68i/T68ie a special data should be uploaded into the
GDFS first, then the T68i/T68ie firmware has to be flashed into AVR/ARM flashes.
firmware.
button, a file-open dialog appears. Select the file "T68m to T68i.mdc" and
press OK. Wait until the GDFS file gets transferred to the phone.
Go to the Write Flash page of the Control Window. Select the corresponding
firmware from the page describing all possible languagepacks for T68i.
Click Flash AVR button, a file-open dialog appears. Select file containing the
AVR firmware part with the desired languagepack and press OK. Wait until the
flash file gets transferred into the phone.
Click Flash ARM button, a file-open dialog appears. Select file containing the
ARM firmware part and press OK. Wait until the flash file gets transferred into
the phone.
phone from cable.
7.6 Decustomize T68m and T68i
firmware.
button, a file-open dialog appears. Select the file "T68m to T68i.mdc" and
phone from cable.
7.7 Convert T300 to T310
To convert a T300/T300c/T302 into T310/T310c/T312 a special data should be
uploaded into the GDFS first, then the T310/T310c/T312 firmware has to be flashed
into AVR/ARM flashes.
button, a file-open dialog appears. Select the file "T300 to T310.mdc" and
Go to the Write Flash page of the Control Window.
Click Flash AVR button, a file-open dialog appears. Select file containing the
AVR firmware with the desired languagepack and press OK. Wait until the flash
file gets transferred into the phone.
phone from cable.
Part
VIII
8 Phones AVR 1999/2000
A1018s, A1018sc, A2218z, A2228z, A2618s, A2618sc, A2628s, A2628sc, A2638sc,
A2668sc, R310s, R310sc, R320s, R320sc, T10s, T10sc, T18s, T18sc, T20s, T20sc,
T20e, T20ec, T28s, T28sc, T28w, T29s and T29sc.
Part
IX
9 SmartPhones 2003/2004
P800, P802, P900, P907, P908, P910i, P910c and P910a.
9.1 Change Languagepack and Upgrade Firmware
Check phone firmware version using the >*<<*<* key sequence in flip-closed
mode. If your phone has no flip mounted, enable virtual flip and use that
instead. In case the phone menu freezes or displays incomplete information,
there is something wrong with one of the firmware components. Also note that
empty Bluetooth software ID itself does not necessarily mean Bluetooth software
malfunction.
Turn off the phone and Cruiser to the AVR-part of the phone.
Go to the Flash page of the Control Window.
Click Flash AVR button, select the file containing the respective AVR-firmware
part and press OK. Wait until the flash file gets transferred into the phone.
phone from cable.
Put the battery back to the phone and attach Cruiser to the PDA-part of the
phone.
You may see what languagepacks are available for the phone by clicking the
LangPack Info button in the Control Window. The page describing all possible
languagepacks should appear. The PDA-part firmware consists of two parts:
o Symbian OS - represents drives A: and Z:.
o Customization Data Area (CDA) - represents drive C:, the internal storage
(user data).
Now press the Flash PDA button, select file containing the desired PDA-
firmware part and press OK. Wait until the flash file gets transferred into the
phone and, if needed, repeat this step.
If you would like to flash the Bluetooth software too, press Flash BT button,
choose the corresponding flash file and press OK. Unless you are experiencing
IrDA/Bluetooth problems, this step is not necessary and you may skip it.
Detach the phone by clicking the Detach phone button in the Primary page
of Control Window, removing the battery from the phone and disconnecting the
phone from cable.
9.2 Unlock
The P800 and P802 phones may be unlocked by reading codes:
will see all four locks closed, the phone usually cannot be unlocked this way.
Detach the phone by clicking the Detach button in the Primary page of Control
Window, removing the battery from the phone and disconnecting the phone
from cable.
codes.
The P900, P907, P908, P910i, P910c and P910a phones may be unlocked by
rebuilding GDFS security zone:
phone from cable.
9.3 Check Security Zone
Note: Applicable to P800 and P802 only.
Press Check security button and wait a while. The GDFS security zone will be
analyzed.
phone from cable.
phone from cable.
9.5 Convert P900 to P910
Attach to phone part
Flash Phone Image (P910u_Phone_CXC162022_R4A006.AVR.flp)
Detach from phone part, remove and reinsert phone battery.
Attach to PDA Part
Flash Symbian file (using Flash PDA button):
P910u_Symbian_CXC162041_R2A17.PDA.flp
Flash Symbian file (using Flash PDA button): P910u_Italy_Swiss_CDA162005-
2_R2A16.PDA.flp
Detach phone, remove and reinsert phone battery.
9.6 How to Boot an Unbootable P900?
This problem may arise after flashing an original P910 AVR flash which has not been
specially prepared for uploading into a P900 phone. The problem will not occur if you
disable the Relock RSA option before flashing.
The solution is to use a testpoint. There is no software-only way because of a CID-
mismatch. Just connect the testpoint to GND while booting the phone and wait until
Cruiser finishes bypassing boot authority check. Then simply disconnect it.
Figure 1. The whole PCB
Figure 2. P900 testpoint detail.
Question:
Why am I getting a "Final checksum error" when flashing P900/P910 PDA part?
Answer:
Use an original DSS-25 to flash the PDA part or lower the communication rate to
460800Bd. Alternatively you may add two resistors as shown in the picture here.
Part
X
111 SmartPhones 2000
10 SmartPhones 2000
R380s, R380sc, R380e, R380ec and R380w.
10.1 Change Languagepack and Upgrade Firmware
Remove the SIM-card from the phone, if there is any.
Turn off the phone and attach Cruiser to the AVR-part of the phone.
Press the Upgrade security button and reattach the phone.
Click the Flash AVR button, select the file containing the respective AVR-
phone.
Then turn the phone off.
Now attach to the PDA-part of the phone - select R380 (PDA-part).
Click the Flash PDA button, select the file containing the respective PDA-
phone.
Now remove battery from the phone and detach.
10.2 Unlock
Turn off the phone and attach Cruiser to the AVR-part of the phone.
Press the Upgrade security button.
Now you may unlock the phone by any free tool as if it was a T10 or T18.
Part
XI
113 Phones CR 2001
11 Phones CR 2001
T66m, T66mc, T600 and T602.
11.1 Unlock
The phone will be detached and turned off automatically.
codes.
Part
XII
115 LG 3G Phones
12 LG 3G Phones
U8100, U8110, U8120, U8130, U8138, U8180, U8330, U8360, U8380, and U8550.
12.1 Unlock
12.1.1 Unlock LG U8110
This phone should be brown CID17 by default. To unlock this phone follow these
instructions:
Attach the phone.
Press Read codes, unlocking codes will be shown.
Turn the phone off and disconnect it from the cable.
Then turn it on and press 2945#*88110# to enter unlocking codes.
For LG U8120 you have to check what firmware version is in the phone before
continuing further.
So, at first enter this code 277634#*# (SIM card removed from the phone) and goto
SW Version phone submenu. If the software version is lower than 105, unlock the
phone by reading codes like a U8110. Newer software versions like 105 or above do
not allow entering unlocking codes, so you need to downgrade the phone firmware to
version 101 (at least its drive_c part) and then continue as you would for older
U8120 firmware.
Note 1: U8120 firmware version 104A may be unlocked by patching like U8130 and
newer models. For version 104C read codes.
Note 2: Sometimes it may be useful to relock the phone to some provider before
attempting to enter unlocking codes.
12.1.3 Unlock LG U813x/U8180/U83x0
To unlock these phones you have to follow these instructions:
Attach the phone.
Press Unlock by patching button and wait for a while to let Cruiser remove
firmware locks.
Turn off the phone by pressing Ctrl-O, your phone should be unlocked now.
There are several different types of firmware locks. Some of them may be left unused
for particular phone type.
SIM-lock check - processes GDFS operator locks
Operator check - represents operator check hardwired to the firmware source
code
Incomplete SIM-card init - prevents 2G SIM-card usage
Antitamper code - prevents unauthorized firmware modification
OTP restriction code - checks whether the firmware is allowed to run in the
phone
The more recent phone model or firmware, the more locks are employed. If
antitampering or OTP restriction code is present in the phone, and Cruiser fails to
patch it properly (yes, this may happen), the phone becomes dead. In this case just
restore partial firmware backup by flashing it back to the phone. This backup file is
made by Cruiser automatically before patching. Usually you may find it in the folder
named
"c:\Program Files\Cruiser\Data\ARM flash backups\LG U8xxx\<Phone
IMEI>"
You should also report the offending phone type and its firmware version in Cruiser
support forum.
This phone should be red CID54 by default. To unlock this phone follow these
instructions:
Attach the phone.
Press Unlock RSA and wait until Cruiser asks you to remove battery from the
phone. Then do it.
Reattach the phone and flash one of the unlocked flash files from the support
area. Version 0.9b is the latest firmware version with 2G SIM card support.
12.2 Testpoint Pictures
12.2.1 LG U8xxx CID Testpoint
This testpoint may be used to repair phones damaged by other tools.
Figure 2. Testpoint detail
117 LG 3G Phones
12.2.2 LG U8380 CID Testpoint
This testpoint may be used to repair phones damaged by other tools.
Figure 2. LG U8380 testpoint detail
12.2.3 LG U8550 CID Testpoint
This testpoint may be used to repair CID54 phones damaged by other tools.
Figure 2. LG U8550 testpoint detail
119 LG 3G Phones
12.3 Special LG Codes
Phone Service Menu Code
8110
277634#*#
8120
277634#*#
8130
47328545454#
8138
47328545454#
8180 v10A
49857465454#
8180 v11A
492662464663#
8330
637664#*#
8360
*6*41*12##
8380
525252#*#
8550
885508428679#*#
Phone Unlock Menu Code
Older phones
2945#*88110#
Part
XIII
121 Sharp 3G Phones
13 Sharp 3G Phones
V801SH, V802SH, V902SH, V703SH, V703SHF, V903SH, SX313, SX813 and SX833.
Question:
When I try to attach to the phone, it just powers on or simply does not attach.
Answer:
At first for a couple of times try this:
Press the Attach to phone button,
then insert the cable connector to the phone,
and finally insert battery to the phone.
Optionally you may try pressing phone's power button.
If this does not work, open the phone up and check for signs of corrosion on the
connector.
Part
XIV
123 Siemens Phones
14 Siemens Phones
C62 and C62c.
14.1 Unlock Siemens C62
The only supported C62 firmware versions are v25, v26, v27 and v28. For unlocking
previous firmware versions you need to use available free tools.
Attach the phone
Press Direct Unlock
Part
XV
125 Language Packages
15.1 Language Acronyms
Language Acronym
Albanian SQ
Arabic AR
Brazilian Portuguese BP
Bulgarian BG
Canadian French CF
Chinese traditional ZC
Chinese traditional Hong Kong ZH
Chinese traditional Taiwan ZT
Chinese simplified ZS
Czech CS
Croatian HR
Danish DA
Dutch NL
English EN
Estonian ET
Finnish FI
French FR
German DE
Greek EL
Hebrew HE
Hindi HI
Hungarian HU
Indonesian-Bahasar IN
Icelandic IC
Italian IT
Japanese JA
Latin American Spanish XL
Latvian LV
Lithuanian LT
Macedonian MK
Malay MS
Norwegian NO
Persian-Farsi FA
Philippine-Tagalog TL
Polish PL
Portuguese PT
Romanian RO
Russian RU
Language Acronym
Albanian SQ
Arabic AR
Serbian SR
Sesotho (South Africa) ST
Slovakian SK
Slovenian SL
Spanish ES
Swedish SV
Thai TH
Turkish TR
Ukrainian UK
US English AE
Vietnamese VI
Zulu ZU
15.2 A3618 Language Packages
Package Software ID Menu Languages
A3618 MTI0012 R1S
en/in/ms/zs/zh/zt/de/ru/tl/
th/tr/vi
15.3 J200i/J200c Language Packages
Package AVR Software ID Languages
J200i Config1 CXC125966 en/sq/ar/hr/cs/el/he/sr
J200i Config2 CXC125967 en/hu/pl/ro/sk/sl/st
J200i Config3 CXC125968 en/ar/fa/fr/tr/hi
J200i Config4 CXC125969 sv/no/fi/da/en/de
J200i Config5 CXC125970 en/es/pt/fr/nl/de
J200i Config6 CXC125971 ae/cf/bp/xl
J200i Config7 CXC125972 en/ru/ro/bg/et/lv/lt/uk
J200i Config8 CXC125973 en/de/it/fr
J200i Asian CXC125974 en/ms/tl/vi/th/id
J200c China CXC125975 en/zs/zt
Note: J200i/J200c phones are not RSA protected.
J210i EMEA1 CXC1250103 en/et/lv/lt/pl/ru
J210i EMEA2 CXC1250104 en/hr/cs/sr/sl/sk
J210i EMEA3 CXC1250105 en/el/sq
J210i EMEA4 CXC1250106 en/hu/ro/bg/[ru]
J210i EMEA5 CXC1250107 en/iw/[ar]/[fa]/[fr]
J210i EMEA6 CXC1250108 en/ar/fa/fr/[ru]
J210i EMEA7 CXC1250109 en/ru/tr
J210i EMEA8 CXC1250110 en/ru
J210i Europe1 CXC1250111 en/pt/es/[fr]
J210i Europe2 CXC1250112 en/de/fr/st/zu/pt
J210i Europe3 CXC1250113 en/fr/nl
J210i Europe4 CXC1250114 en/fi/sv/no/is
J210i Europe5 CXC1250115 en/it/de/fr
J210i US1 CXC1250116 ae/cf/xl
J210i US2 CXC1250117 ae/bp/xl
Note: J210i/J210c phones are not RSA protected.
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
J300i EMEA1 CXC1250001 EU1 CXC1250002 EMEA1
en/en/et/lv/lt/pl/ru/
uk
J300i EMEA2 CXC1250001 EU1 CXC1250002 EMEA2 en/hr/cs/sr/sl/sk
J300i EMEA3 CXC1250001 EU1 CXC1250002 EMEA3 en/el/sq
J300i EMEA4 CXC1250001 EU1 CXC1250002 EMEA4 en/ro/hu/bg/ru
J300i EMEA5 CXC1250001 EU1 CXC1250002 EMEA5 en/ar/he/ru/fr/fa
J300i EMEA6 CXC1250001 EU1 CXC1250002 EMEA6 en/fr/ar/fa/ru
J300i EMEA7 CXC1250001 EU1 CXC1250002 EMEA7 en/tr/ru
J300i EU1 CXC1250001 EU1 CXC1250002 EU1 en/pt/es/fr
J300i EU2 CXC1250001 EU1 CXC1250002 EU2 en/fr/de/st/zu/tr
J300i EU3 CXC1250001 EU1 CXC1250002 EU3 en/da/nl/fr/de
J300i EU4 CXC1250001 EU1 CXC1250002 EU4 en/da/sv/no
J300i EU5 CXC1250001 EU1 CXC1250002 EU5 en/fr/de/it
J300i EU6 CXC1250001 EU1 CXC1250002 EU6 en/fr/de/it
J300i APAC1 CXC1250008 China CXC1250002 APAC1 en/...
J300c China CXC1250008 China
CXC1250002
Chinese
en/zs
J300i Thai CXC1250008 China CXC1250002 Thai en/...
J300i India CXC1250001 EU1 CXC1250002 India en/...
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
J300i EMEA1 CXC1250001 EU1 CXC1250002 EMEA1
uk
J300i EMEA2 CXC1250001 EU1 CXC1250002 EMEA2 en/hr/cs/sr/sl/sk
J300i US1 CXC1250001 EU1 CXC1250002 US1 en/...
J300i US2 CXC1250001 EU1 CXC1250002 US2 ae/pb/xl
J300i HongKong
CXC1250009
HongKong
CXC1250002
HongKong
en/zh
J300i Taiwan CXC1250010 Taiwan CXC1250002 Taiwan en/zt
15.6 K300i/K300c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
K300i EMEA1 CXC125978 EU1 CXC125979 EMEA1
uk
K300i EMEA2 CXC125978 EU1 CXC125979 EMEA2 en/hr/cs/sr/sl/sk
K300i EMEA3 CXC125978 EU1 CXC125979 EMEA3 en/el/sq
K300i EMEA4 CXC125978 EU1 CXC125979 EMEA4 en/ro/hu/bg/ru
K300i EMEA5 CXC125978 EU1 CXC125979 EMEA5 en/ar/he/ru/fr/fa
K300i EMEA6 CXC125978 EU1 CXC125979 EMEA6 en/fr/ar/fa/ru
K300i EMEA7 CXC125978 EU1 CXC125979 EMEA7 en/tr/ru
K300i EU1 CXC125978 EU1 CXC125979 EU1 en/pt/es/fr
K300i EU2 CXC125978 EU1 CXC125979 EU2 en/fr/de/st/zu/tr
K300i EU3 CXC125978 EU1 CXC125979 EU3 en/da/nl/fr/de
K300i EU4 CXC125978 EU1 CXC125979 EU4 en/da/sv/no
K300i EU5 CXC125978 EU1 CXC125979 EU5 en/fr/de/it
K300i APAC1 CXC125985 China CXC125979 APAC1 en/...
K300c China CXC125985 China CXC125979 Chinese en/zs
K300i Thai CXC125985 China CXC125979 Thai en/...
K300i India CXC125978 EU1 CXC125979 India en/...
K300i US1 CXC125978 EU1 CXC125979 US1 en/...
K300i US2 CXC125978 EU1 CXC125979 US2 ae/pb/xl
K300i E-Plus CXC125978 EU1 CXC125979 EPlus en/...
K300i Rogers CXC125978 EU1 CXC125979 Rogers en/...
K300i Vodafone1 CXC125980 EU2
CXC125979
Vodafone1
en/nl/el/pt/es/sv
CXC125979
Vodafone2
en/fr/de/it/ar/hu/tr
CXC125979
Vodafone3
en/fr/nl/de
K300i Orange CXC125981 EU3 CXC125979 Orange en/fr/nl/da/ro/sk
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
K300i EMEA1 CXC125978 EU1 CXC125979 EMEA1
uk
K300i HongKong
CXC125986
HongKong
CXC125979
HongKong
en/zh
K300i Taiwan CXC125987 Taiwan CXC125979 Taiwan en/zt
CDA Numbers:
CDA Number Phone Model Customization
CDA102317/1 K300i Generic EMEA1
CDA102317/9 K300i Generic EU1
CDA102317/15 K300i Generic US1
CDA102317/101 K300i Generic APAC1
CDA102317/102 K300i Generic THAI
CDA102317/103 K300i Generic CHINA
CDA102317/104 K300i Generic HK
CDA102317/105 K300i Generic TAIWAN
CDA102317/106 K300i Generic EMEA8 CIPH
CDA102317/107 K300i Generic US1 CIPH
CDA102317/108 K300i Generic US2 CIPH
CDA102317/109 K300i Generic EMEA6 CIPH
15.7 K500i/K500c/F500i/K508i/K506c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
K508i AsianLatin1 CXC125873 EU1
CXC125879
AsianLatin1
en/ms/id
K508i AsianLatin2 CXC125962 China
CXC125961
AsianLatin2
en/tl/vi
CXC125961
AsianLatin3
en/ms/id
CXC125961
AsianLatin4
en/ms/id
K500i EMEA1 CXC125873 EU1 CXC125879 EMEA1 en/et/lv/lt/pl/ru/uk
K500i EMEA8 CXC125873 EU1 CXC125879 EMEA8 en/ru
K500i US1 CXC125873 EU1 CXC125879 US1 ae/cf/xl
K500i US2 CXC125873 EU1 CXC125879 US2 ae/bp/xl
F500i Vodafone1 CXC125900 EU2
CXC125879
Vodafone1
en/nl/el/pt/es/sv
CXC125879
Vodafone2
CXC125879
Vodafone3
fr/nl/en/de
K500i Orange Ch CXC125901 EU3
CXC125879 Orange
Ch
en/fr/it/de
K500i Orange
Generic
CXC125901 EU3
CXC125879 Orange
Generic
en/fr/nl/da/ro/sk
K500i T-Mobile IntA CXC125902 EU4
CXC125879 T-Mobile
IntA
en/de/nl/cs/pl/tr
K500i T-Mobile IntB CXC125902 EU4
CXC125879 T-Mobile
IntB
en/hu/hr/sk
K500i HongKong
CXC125885
HongKong
CXC125879
HongKong
en/zh
K500c Chinese CXC125962 China CXC125961 Chinese en/zs
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
CXC125879
AsianLatin1
en/ms/id
CXC125961
AsianLatin2
en/tl/vi
K506c CMCC CXC125888 CMCC CXC125961 CMCC en/zs
CDA Numbers:
CDA102309/1 K500i AsianLatin1 Generic
CDA102312/1 K508c Generic Trade China
CDA102312/2 K508i Generic Trade Hong Kong
CDA102312/6 K508i Generic Trade Australia
CDA102312/7 K508i Generic Trade Thailand
CDA102309/8 K500i EU1 Generic
CDA102309/13 K500i EMEA1 Generic
CDA102309/21 K500i US1 Generic
CDA102309/22 K500i US2 Generic
CDA102307/14 K500i Generic Trade Hong Kong
CDA102307/33 K500i Generic Trade Netherlands
CDA102307/34 K500i Generic Trade Italy
CDA102307/35 K500i Generic Trade France
CDA102307/41 K500i Generic Trade Belgium
CDA102307/43 K500i Generic Trade UK
CDA102307/53 K500i Generic Trade Morocco
CDA102307/54 K500i
Generic Trade United Arab
Emirates
CDA102307/55 K500i Generic Trade Russia
CDA102307/56 K500i Generic Trade India
CDA102307/64 K500i Generic Trade Norway
CDA102307/65 K500i Generic Trade Brazil
CDA102307/66 K500i
Generic Trade United
Kingdom
CDA102307/69 K500i Generic Trade Ireland
15.8 K600i/K600c/K608i/V600i Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
K600i APAC1 CXC1250079 China CXC1250017 APAC1 en/ms/id/tl/vi/zs
K600c Chinese CXC1250079 China CXC1250017 China en/zs
K600i Thai CXC1250079 China CXC1250017 Thai en/th
K600i HongKong
CXC1250080
HongKong
CXC1250017
HongKong
en/zh
K600i America1 CXC1250014 EU1
CXC1250017
America1
ae/cf/xl
CXC1250017
America2
ae/bp/xl
K600i EMEA1 CXC1250014 EU1 CXC1250017 EMEA1 en/pl/lv/lt/ru/et/uk
K600i Europe1 CXC1250014 EU1
CXC1250017
Europe1
en/pt/es/fr
CXC1250017
Europe2
en/fr/de/st/zu/tr
CXC1250017
Europe3
en/nl/fr/de
CXC1250017
Europe4
en/fi/da/ic/sv/no
CXC1250017
Europe5
en/fr/de/it
15.9 K700i/K700c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
CXC125822
AsianLatin2
en/tl/vi
CXC125822
AsianLatin3
en/ms/zs
CXC125822
AsianLatin4
en/th
K700i EMEA1 CXC125821 EU1 CXC125822 EMEA1 en/et/lv/lt/pl/ru/uk
K700i EMEA8 CXC125821 EU1 CXC125822 EMEA8 en/ru
CXC125822
AsianLatin1
en/ms/id
K700i US1 CXC125821 EU1 CXC125822 US1 ae/cf/xl
K700i US2 CXC125821 EU1 CXC125822 US1 ae/bp/xl
CXC125822
Vodafone1
en/nl/el/pt/es/sv
CXC125822
Vodafone2
CXC125822
Vodafone3
fr/nl/en/de
K700i Orange Be CXC125898 EU3
CXC125822 Orange
Be
en/fr/nl/de
K700i Orange Ch CXC125898 EU3
CXC125822 Orange
Ch
en/fr/it/de
K700i Orange
Generic
CXC125898 EU3
CXC125822 Orange
Generic
en/fr/nl/da/ro/sk
K700i T-Mobile IntA CXC125898 EU4
CXC125822 TMobile
IntA
en/de/nl/cs/pl/tr
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
CXC125822
AsianLatin2
en/tl/vi
K700i T-Mobile IntB CXC125898 EU4
CXC125822 TMobile
IntB
en/hu/hr/sk
K700i T-Mobile US CXC125898 EU4
CXC125822 TMobile
US
ae/xl
K700i HongKong
CXC125882
HongKong
CXC125822
HongKong
en/zh
CDA Numbers:
CDA102286/1 K700i Generic AsianLatin1
CDA102286/5 K700c Generic China
CDA102286/6 K700i Generic HongKong
CDA102286/107 K700i Generic Taiwan
CDA102298/34 K700i Generic Trade Sweden
CDA102298/38 K700i Generic Trade China
CDA102298/41 K700i Generic Trade Belgium
CDA102298/42 K700i Generic Trade Netherlands
CDA102298/83 K700i
Kingdom
CDA102298/84 K700i Generic Trade Morocco
CDA102298/85 K700i
Generic Trade United Arab
Emirates
CDA102298/93 K700i Generic Trade Indonesia
CDA102298/94 K700i Generic Trade Philippines
CDA102298/96 K700i Generic Trade Malaysia
CDA102298/98 K700i Generic Trade Singapore
CDA102298/104 K700i Generic Trade Brazil
15.10 K750i/K750c/D750i Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
K750i APAC1 CXC125954 China CXC125953 APAC1 en/ms/id/tl/vi/zs
K750i Thai CXC125954 China CXC125953 Thai en/th
K750i HongKong
CXC125955
HongKong
CXC125953
HongKong
en/zc
CXC125953
America1
ae/cf/xl
CXC125953
America2
ae/bp/xl
K750i EMEA1 CXC125952 EU1 CXC125953 EMEA1 en/pl/lv/lt/ru/uk
K750i Europe1 CXC125952 EU1 CXC125953 Europe1 en/pt/es/fr
K750i Europe2 CXC125952 EU1 CXC125953 Europe2 en/fr/de/st/zu/tr
K750i Europe3 CXC125952 EU1 CXC125953 Europe3 en/da/nl/fr/de
K750i Europe4 CXC125952 EU1 CXC125953 Europe4 en/fi/da/ic/sv/no
K750i Europe5 CXC125952 EU1 CXC125953 Europe5 en/fr/de/it
K750i Vodafone 1 CXC1250035 EU2
CXC125953
Vodafone 1
en/nl/el/pt/es/sv
CXC125953
Vodafone 2
CXC125953
Vodafone 3
en/fr/nl/de/hr/sl
K750i Orange CH CXC125952 EU1 (?)
CXC125953 Orange
CH
en/fr/it/de
K750i Orange Gen CXC1250036 EU3
CXC125953 Orange
Gen
en/fr/nl/ro/sk/pl
D750i T-Mobile IntA CXC125952 EU1
CXC125953 TMobile
IntA
en/de/nl/cs/pl/tr
D750i T-Mobile IntB CXC125952 EU1
CXC125953 TMobile
IntB
en/hu/hr/sk
K750i E-Plus CXC125952 EU1 CXC125953 E-Plus en/nl/fr/de/es/tr
15.11 P800/P802 Language Packages
Package
AVR
Software ID
Symbian ID CDA ID Bluetooth Languages
P800 lang1
CXC162002
R2F
CXC162001
R2D002
CDA1620011
R5A02
CXC12529
R5A
sv/da/fi/no
P800 lang2
CXC162002
R2F
CXC162001
R2D002
CDA1620012
R5A02
CXC12529
R5A
it/de/fr
P800 lang3
CXC162002
R2F
CXC162001
R2D002
CDA1620013
R5A02
CXC12529
R5A
nl/de/fr
P800 lang4
CXC162002
R2F
CXC162001
R2D002
CDA1620014
R5A02
CXC12529
R5A
es/el/pt/tr
P800 lang5
CXC162002
R2F
CXC162001
R2D002
CDA1620015
R5A02
CXC12529
R5A
en
P800 lang6
CXC162002
R2F
CXC162001
R2D002
CDA1620016
R5A02
CXC12529
R5A
ae/xl/cf
P800 lang7
CXC162002
R2F
CXC162001
R2D002
CDA1620017
R5A02
CXC12529
R5A
ae/xl/bp
P800 lang8
APAC4
CXC162002
R2F
CXC162001
R2D002
CDA1620018
R5A02
CXC12529
R5A
en
P800 lang9
CXC162002
R2F
CXC162001
R2D002
CDA1620019
R5A02
CXC12529
R5A
hu/ro
P802
Chinese1
CXC162002
R2F
CXC16209
R2A07
CDA162091
R2A03
CXC12529
R5A
zs
P802 Taiwan
CXC162002
R2F
CXC16210
R2A07
CDA162101
R2A03
CXC12529
R5A
zt
P802
HongKong
CXC162002
R2F
CXC16211
R2A07
CDA162111
R2A03
CXC12529
R5A
zh
P802
Chinese2
CXC162002
R2F
CXC16212
R2A07
CDA162121
R2A03
CXC12529
R5A
zs
Note 1: Always use a fully charged battery!
Note 2: The CDA flash area contains also the user data. Flashing it causes losing all
user data.
Note 3: Bluetooth firmware can be flashed using the flash BT button. When attaching
the phone, use the PDA-part option.
Note 4: Do not try to use Bluetooth firmware designed for P900/P908 as the BT
protocol has changed.
15.12 P900/P907/P908 Language Packages
Package
AVR
Software ID
P900 EMEA1
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
1 R5A07
CXC12529
R5D
sv/no/da/fi
P900 EMEA2
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
2 R5A07
CXC12529
R5D
it/fr/de
P900 EMEA3
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
3 R5A07
CXC12529
R5D
nl/fr/de
P900 EMEA4
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
4 R5A07
CXC12529
R5D
el/pt/es
P900 EMEA5
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
5 R5A07
CXC12529
R5D
en/fr
P900 EMEA6
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
9 R5A07
CXC12529
R5D
ro/hu/tr/ru
P900 LAM1
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
7 R5A07
CXC12529
R5D
ae/xl/bp
P900 LAM2
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
14 R5A07
CXC12529
R5D
ae/xl
P900 LAM3
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
15 R5A07
CXC12529
R5D
ae/xl/fr
P900 NAM
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
6 R5A07
CXC12529
R5D
ae/xl/cf
P908 China
CXC162022
R3D011
CXC162023
R5A09
CDA162003/
10 R5A09
CXC12529
R5D
zs
P908 APAC1
CXC162022
R3D011
CXC162024
R5A09
CDA162003/
11 R5A09
CXC12529
R5D
zh
P908 APAC2
CXC162022
R3D011
CXC162025
R5A09
CDA162003/
12 R5A09
CXC12529
R5D
zt
P908 APAC3
CXC162022
R3D011
CXC162026
R5A09
CDA162003/
13 R5A09
CXC12529
R5D
zs
P900 APAC4
CXC162022
R3D011
CXC162021
R5B02
CDA162003/
8 R5A07
CXC12529
R5D
en
P907
CXC162022
R3D006
CXC162052
R1A06
CDA162003/
16 R1A05
CXC12529
R5D
en
Note 2: Do not try to use these firmwares with P800/P802, since P900/P907/P908
phones have larger PDA flash chips than P800/P802 phones.
Note 3: The CDA flash area consists of two parts, 1. read-only (ROLF/img) and 2.
user data (bin). Flashing the second part causes losing all user data. It is necessary to
flash the first part when changing the Symbian version in the phone.
Note 4: Bluetooth firmware can be flashed using the flash BT button. When attaching
the phone, use the PDA-part option.
15.13 P910i/P910c/P910a Language Packages
Package
AVR
Software ID
P910i Nordic
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
1 R2A16
Blueberry
R2C
sv/no/da/fi
P910i Italy/
Swiss
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
2 R2A16
Blueberry
R2C
it/fr/de
P910i EMEA/
APAC
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
3 R2A16
Blueberry
R2C
nl/fr/de/el/tr
P910i East/
EMEA
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
4 R2A16
Blueberry
R2C
hu/ru/tr/pl/cs
P910i Iberia/
NAM
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
5 R2A16
Blueberry
R2C
ae/xl/es/pt/cf
P910i APAC/
LAM
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
6 R2A16
Blueberry
R2C
ae/xl
P910i France
CXC162042
R4A006
CXC162041
R2A017
CDA162005/
7 R2A16
Blueberry
R2C
fr
P910a NAM
CXC162050
R4A006
CXC162041
R2A017
CDA162005/
8 R2A16
Blueberry
R2C
ae/xl/cf
P910a LAM
CXC162050
R4A006
CXC162041
R2A017
CDA162005/
9 R2A16
Blueberry
R2C
ae/xl
P910c China
CXC162042
R3E008
CXC162044
R1A17
CDA162005/
10 R1A17
Blueberry
R2C
zs
P910i APAC1
CXC162042
R3E008
CXC162044
R1A17
CDA162005/
11 R1A17
Blueberry
R2C
zh
P910i APAC2
CXC162042
R3E008
CXC162045
R1A17
CDA162005/
12 R1A17
Blueberry
R2C
zt
P910i APAC3
CXC162042
R3E008
CXC162046
R1A17
CDA162005/
13 R1A17
Blueberry
R2C
zs
P910c CMCC
CXC162042
R3E008
CXC162043
R1A17
CDA162006/
28 R1B02
Blueberry
R2C
zs
Note 2: Do not try to flash P910 Bluetooth part using a P900 firmware.
15.14 R310s/R310sc Language Packages
R310s EU1 CXC112175 R7B(010627) en/???
R310s EU2 CXC112177 R7B(010627) en/???
R310s AP1 CXC112178 R7B(010627) en/???
R310s AP2 CXC112184 R7B(010627) en/???
R310sc China1 CXC112176 R7A(010314) en/???
R310sc China2 CXC112183 R7B(010627) en/???
15.15 R320s/R320sc Language Packages
Package AVR Software ID ARM Software ID Languages
R320s EU1
CXC125193 R4J
(010628)
CXC125188 R4J
(010628)
en/ar/bg/hr/et/he/
lv/lt/ro/ru/sr/sl
R320s EU2
CXC125229 R4J
(010628)
CXC125188 R4J
(010628)
en/nl/fr/de/el/it/pt/
tr/ru/es
R320s EU3
CXC125235 R4J
(010628)
CXC125188 R4J
(010628)
en/ar/cs/nl/fr/de/
hu/el/it/pt/pl/ru/sk/
es/tr
R320s EU4
CXC125230 R4J
(010628)
CXC125188 R4J
(010628)
en/???
R320sc ???
CXC125226 R4J
(010628)
CXC125188 R4J
(010628)
en/???
R320sc ???
CXC125232 R4J
(010628)
CXC125188 R4J
(010628)
en/???
R320sc ???
CXC125239 R4J
(010628)
CXC125188 R4J
(010628)
en/???
Note 1: R320s/R320sc phones have two firmwares and both should be of the same
software revision. Otherwise firmware freezing may occur.
Note 2: For CO-WAP phones, CXC125283 has to be used instead of CXC125188.
15.16 R380s/R380sc/R380e Language Packages
Package AVR Software ID EPOC ID Languages
R380e lang5
CXC112146 R2A02
(010830)
CXC112159/5
R5C01
en/sv/da/no/fi/sv
(Finnish)
R380e lang9
CXC112146 R2A02
(010830)
CXC112159/9
R5C01
en/tr/ru/el/hi/ms
R380e lang10
CXC112146 R2A02
(010830)
CXC112159/10
R5C01
en/fr(Swiss)/de
(Swiss)/pt/it(Swiss)
R380e lang11
CXC112146 R2A02
(010830)
CXC112159/11
R5C01
en/cs/sl/sk
R380e lang12
CXC112146 R2A02
(010830)
CXC112159/12
R5C01
en/fr/nl/nl(Belgian)/
fr(Belgian)
R380e lang13
CXC112146 R2A02
(010830)
CXC112159/13
R5C01
en/de/es/it/de
(Austrian)
R380e lang14
CXC112146 R2A02
(010830)
CXC112159/14
R5C01
en/hu/pl/ro
Note: The CDA flash area contains also the user data. Flashing it causes losing all
user data.
15.17 R520m/R520mc Language Packages
R520m AP1 CXC125306 R4A008 CXC125147 R4A008 en/ms
R520m AP2 CXC125307 R4A008 CXC125147 R4A008 en/in
R520m AP3 CXC125340 R4A008 CXC125147 R4A008 en/tl
R520m AP4 CXC125341 R4A008 CXC125147 R4A008 en/vi
R520m AP5 CXC125349 R4A008 CXC125147 R4A008 en/th
R520m AP6 CXC125350 R4A008 CXC125147 R4A008 en/zs
R520m EMEA1 CXC125295 R4A008 CXC125147 R4A008 en/et/lv/lt/pl/ru
R520m EMEA2 CXC125296 R4A008 CXC125147 R4A008 en/cs/hr/sr/sk/sl
R520m EMEA3 CXC125303 R4A008 CXC125147 R4A008 en/bg/el/hu/ro/tr
R520m EMEA4 CXC125304 R4A008 CXC125147 R4A008 en/fr/ar/fa/he/ru
R520m EMEA5 CXC125305 R4A008 CXC125147 R4A008 en/fr/ar/fa/ru
R520m EU1 CXC125168 R4A008 CXC125147 R4A008 en/fr/pt/es
R520m EU2 CXC125291 R4A008 CXC125147 R4A008 en/fr/de/it
R520m EU3 CXC125292 R4A008 CXC125147 R4A008 en/da/nl/fr
R520m EU4 CXC125293 R4A008 CXC125147 R4A008 en/fi/sv
R520m EU5 CXC125347 R4A008 CXC125147 R4A008 en/no/sv
R520m US1 CXC125294 R4A008 CXC125147 R4A008 ae/cf/xl
R520m US2 CXC125348 R4A008 CXC125147 R4A008 ae/xl/bp
R520mc China CXC125308 R3B006 CXC125147 R3B006 en/zs
R520mc HongKong CXC125309 R3B006 CXC125147 R3B006 en/zh
R520mc Taiwan CXC125297 R3B006 CXC125147 R3B006 en/zt
Note 1: R520m/R520mc phones have two firmwares and both should be of the same
Note 2: Sometimes after upgrade from firmware R1x/R2x to R4A008 the motion
detector stops functioning correctly. It has to be recalibrated again then.
15.18 R600 Language Packages
Package Software ID Languages
R600 AP CXC125354 6.015 en/in/ms/th/tl/vi/zs
R600 China CXC125355 6.014 en/zs/zt
R600 EU CXC125356 6.014 en/da/es/fi/nl/no/sv
R600 EMEA1 CXC125357 6.014
en/ar/bg/cs/de/el/fr/he/hu/
hr/it/lt/nl/pt/ro/ru/sr/sk/sl
R600 EMEA2 CXC125358 6.014
en/ar/et/fa/fr/xl/lt/lv/pl/ru/
st/tr/vi/zu
15.19 S700i/S700c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
S700i AsianLatin1
CXC125945
AsianLatin1
CXC125941
AsianLatin1
en/ms/id/tl/vi/th
S700i HongKong
CXC125945
AsianLatin1
CXC125941
HongKong
en/zh
S700i Taiwan CXC125946 Taiwan CXC125941 Taiwan en/zt
S700c AsianLatin2
CXC125947
AsianLatin2
CXC125941
AsianLatin2
en/ms/zs
S700c China
CXC125947
AsianLatin2
CXC125941 Chinese en/zs
S700i EMEA1 CXC125935 EU1 CXC125941 EMEA1 en/et/lv/lt/pl/ru/uk
S700i EMEA2 CXC125935 EU1 CXC125941 EMEA2 en/hr/cs/sr/sl/sk
S700i EMEA3 CXC125935 EU1 CXC125941 EMEA3 en/el/sq
S700i EMEA4 CXC125935 EU1 CXC125941 EMEA4 en/ro/hu/bg/ru
S700i EMEA5 CXC125935 EU1 CXC125941 EMEA5 en/ar/he/ru/fr/fa
S700i EMEA6 CXC125935 EU1 CXC125941 EMEA6 en/fr/ar/fa/ru
S700i EMEA7 CXC125935 EU1 CXC125941 EMEA7 en/tr/ru
S700i EU1 CXC125935 EU1 CXC125941 EU1 en/pt/es/fr
S700i EU2 CXC125935 EU1 CXC125941 EU2 en/fr/de/st/zu
S700i EU3 CXC125935 EU1 CXC125941 EU3 en/da/nl/fr/de
S700i EU4 CXC125935 EU1 CXC125941 EU4 en/da/sv/no
S700i EU5 CXC125935 EU1 CXC125941 EU5 en/fr/de/it
S700i EU6 CXC125935 EU1 CXC125941 EU6 en/fr/de/it
S700i US1 CXC125935 EU1 CXC125941 US1 ae/cf/xl
S700i US2 CXC125935 EU1 CXC125941 US2 ae/bp/xl
S700i Vodafone1 CXC125936 EU2
CXC125941
Vodafone1
en/nl/el/pt/es/sv
CXC125941
Vodafone2
en/fr/it/de/ar/hu/tr
CXC125941
Vodafone3
en/fr/nl/de
Note: S700 phones can not be upgraded to S710 due to hardware differences.
CDA Numbers:
CDA102300/1 S700i Generic AsianLatin1
CDA102300/55 S700i Generic Chinese
CDA102300/56 S700i Generic HongKong
CDA102300/57 S700i Generic Taiwan
CDA102300/7 S700i Generic Taiwan
CDA102300/8 S700i Generic EMEA1
CDA102300/16 S700i Generic EU1
CDA102300/21 S700i Generic US1
CDA102300/22 S700i Generic US2
CDA102310/18 S700c Generic Trade China
CDA102310/22 S700i Generic Trade Netherlands
CDA102310/25 S700i Generic Trade Australia
CDA102310/32 S700i Generic Trade Belgium
CDA102310/37 S700i Generic Trade France
CDA102310/40 S700i
Kingdom
CDA102310/44 S700i Generic Trade Hong Kong
CDA102310/49 S700i
Kingdom
15.20 S710a Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
S710a Argentina CXC1125952
CXC1125954
Argentina
en/cf/xl
S710a Cingular CXC1125952
CXC1125954
Cingular
en/cf/xl
Note: S700 phones can not be upgraded to S710 due to hardware differences.
CDA Numbers:
CDA102323/1 S710a Argentina
CDA102323/12 S710a Cingular
15.21 T39m/T39mc Language Packages
T39m AP1 CXC125270 R4A008 CXC125147 R4A008 en/ms
T39m AP2 CXC125314 R4A008 CXC125147 R4A008 en/in
T39m AP3 CXC125337 R4A008 CXC125147 R4A008 en/tl
T39m AP4 CXC125338 R4A008 CXC125147 R4A008 en/vi
T39m AP5 CXC125345 R4A008 CXC125147 R4A008 en/th
T39m AP6 CXC125346 R4A008 CXC125147 R4A008 en/zs
T39m EMEA1 CXC125310 R4A008 CXC125147 R4A008 en/et/lv/lt/pl/ru
T39m EMEA2 CXC125311 R4A008 CXC125147 R4A008 en/cs/hr/sr/sk/sl
T39m EMEA3 CXC125312 R4A008 CXC125147 R4A008 en/bg/el/hu/ro/tr
T39m EMEA4 CXC125313 R4A008 CXC125147 R4A008 en/fr/ar/fa/he/ru
T39m EMEA5 CXC125272 R4A008 CXC125147 R4A008 en/fr/ar/fa/ru
T39m EU1 CXC125137 R4A008 CXC125147 R4A008 en/fr/pt/es
T39m EU2 CXC125268 R4A008 CXC125147 R4A008 en/fr/de/it
T39m EU3 CXC125269 R4A008 CXC125147 R4A008 en/da/nl/fr
T39m EU4 CXC125274 R4A008 CXC125147 R4A008 en/fi/sv
T39m EU5 CXC125342 R4A008 CXC125147 R4A008 en/no/sv
T39m US1 CXC125271 R4B003 CXC125147 R4B003 ae/cf/xl
T39m US2 CXC125344 R4A008 CXC125147 R4A008 ae/xl/bp
T39mc China CXC125138 R4A008 CXC125147 R4A008 en/zs
T39mc HongKong CXC125315 R3B006 CXC125147 R3B006 en/zh
T39mc Taiwan CXC125273 R3B006 CXC125147 R3B006 en/zt
Note: T39m/T39mc phones have two firmwares and both should be of the same
15.22 T65s/T65sc Language Packages
T65s AsianLatin1
CXC1122219
R6A006
CXC1122043
R6A006
en/ms
T65s AsianLatin2
CXC1122220
R6A006
CXC1122043
R6A006
en/in
T65s AsianLatin3
CXC1122221
R6A006
CXC1122043
R6A006
en/tl
T65s AsianLatin4
CXC1122222
R6A006
CXC1122043
R6A006
en/vi
T65s AsianLatin5
CXC1122304
R6A006
CXC1122043
R6A006
en/th
T65s AsianLatin6
CXC1122210
R6A006
CXC1122043
R6A006
en/zs
T65s EMEA1
CXC1122214
R6A006
CXC1122043
R6A006
en/et/lv/lt/pl/ru
T65s EMEA2
CXC1122215
R6A006
CXC1122043
R6A006
en/cs/hr/sr/sk/sl
T65s EMEA3
CXC1122216
R6A006
CXC1122043
R6A006
en/bg/el/hu/ro/tr
T65s EMEA4
CXC1122217
R6A006
CXC1122043
R6A006
en/fr/ar/fa/he/ru
T65s EMEA5
CXC1122218
R6A006
CXC1122043
R6A006
en/fr/ar/fa/ru
T65s EU1
CXC1121980
R6A006
CXC1122043
R6A006
en/fr/pt/es
T65s EU2
CXC1122211
R6A006
CXC1122043
R6A006
en/fr/de
T65s EU3
CXC1122212
R6A006
CXC1122043
R6A006
en/da/nl/fr
T65s EU4
CXC1122213
R6A006
CXC1122043
R6A006
en/fi/sv
T65s EU5
CXC1122306
R6A006
CXC1122043
R6A006
en/sv/no
T65s EU6
CXC1122434
R6A006
CXC1122043
R6A006
en/fr/de/it
T65sc China
CXC1122223
R6A006
CXC1122043
R6A006
en/zs
T65sc HongKong
CXC1122224
R6A006
CXC1122043
R6A006
en/zh
T65sc Taiwan
CXC1122225
R6A006
CXC1122043
R6A006
en/zt
T65s US2
CXC1122424
R6A006
CXC1122043
R6A006
ae/xl/bp
Note: T65s/T65sc phones have two firmwares and both should be of the same
15.23 T66 Language Packages
Package Core Software ID LP ID Languages
T66 NorthernEU A460029 R4A460 A46010 R4A460 en/fi/no/sv/da
T66 EU1 A460029 R4A460 A46011 R4A460 en/fr/nl/es/pt
T66 EU2 A460029 R4A460 A46012 R4A460 en/de/fr/it
T66 Baltics1 A460029 R4A460 A46013 R4A460 en/lv/pl/et/lt/ru
T66 Eastern EU1 A460029 R4A460 A46014 R4A460 en/bg/ro/ru/hu
T66 Eastern EU2 A460029 R4A460 A46015 R4A460 en/hr/sl/cs/sr
T66 Eastern EU3 A460029 R4A460 A46016 R4A460 en/tr/el/ru
T66 MidEast-Africa A460029 R4A460 A46017 R4A460 en/ru/ar/fr
T66 Israel A460029 R4A460 A46018 R4A460 en/he/ru/ar/fr
T66 US A460029 R4A460 A46019 R4A460 en/es/fr/pt
T66 Asian A460029 R4A460 A46020 R4A460 en/ms/tl/th/in/zs
T66 China A460029 R4A460 A46021 R4A460 en/zs
T66 HongKong A460029 R4A460 A46022 R4A460 en/zh
T66 Taiwan A460029 R4A460 A46023 R4A460 en/zt
15.24 T68m/T68mc Language Packages
T68m AsianLatin1 CXC125411 R2D005 CXC125418 R2D005 en/ms/in
T68m AsianLatin2 CXC125413 R2D005 CXC125418 R2D005 en/tl/vi/th
T68m AsianLatin3 CXC125414 R2D005 CXC125418 R2D005 en/zs
T68m Braz CXC125499 R2D005 CXC125418 R2D005 ae/xl/bp
T68m EMEA1 CXC125406 R2D005 CXC125418 R2D005 en/et/lv/lt/pl/ru
T68m EMEA2 CXC125407 R2D005 CXC125418 R2D005 en/cs/hr/sr/sk/sl
T68m EMEA3 CXC125408 R2D005 CXC125418 R2D005 en/el/tr
T68m EMEA4 CXC125409 R2D005 CXC125418 R2D005 en/bg/hu/ro
T68m EMEA5 CXC125410 R2D005 CXC125418 R2D005 en/fr/ar/fa/he/ru
T68m EMEA6 CXC125412 R2D005 CXC125418 R2D005 en/fr/ar/fa/ru
T68m EU1 CXC125398 R2D005 CXC125418 R2D005 en/fr/pt/es
T68m EU2 CXC125399 R2D005 CXC125418 R2D005 en/fr/de/it
T68m EU3 CXC125401 R2D005 CXC125418 R2D005 en/fr/da/nl
T68m EU4 CXC125402 R2D005 CXC125418 R2D005 en/sv/no/fi
T68m US1 CXC125404 R2D005 CXC125418 R2D005 ae/cf/xl
T68m US2 CXC125405 R2D005 CXC125418 R2D005 ae/xl/bp
T68mc China CXC125415 R2D005 CXC125418 R2D005 en/zs
T68mc HongKong
Taiwan
CXC125416 R2D005 CXC125418 R2D005 en/zh/zt
Note 1: T68m/T68mc firmwares are obsolete and therefore they should be upgraded
to T68i/T68ie by first uploading the respective data into GDFS and then flashing the
latest firmware for T68i/T68ie.
Note 2: T68m/T68mc phones have two firmwares and both should be of the same
15.25 T68i/T68ie Language Packages
T68i AsianLatin1 CXC125320 R8A015 CXC125326 R8A015 en/ms/in
T68i AsianLatin2 CXC125383 R8A015 CXC125326 R8A015 en/tl/vi/th
T68i AsianLatin3 CXC125386 R8A015 CXC125326 R8A015 en/zs
T68i EMEA1 CXC125377 R8A015 CXC125326 R8A015 en/et/lv/lt/pl/ru
T68i EMEA2 CXC125378 R8A015 CXC125326 R8A015 en/cs/hr/sr/sk/sl
T68i EMEA3 CXC125379 R8A015 CXC125326 R8A015 en/el/tr
T68i EMEA4 CXC125380 R8A015 CXC125326 R8A015 en/bg/hu/ro
T68i EMEA5 CXC125381 R8A015 CXC125326 R8A015 en/fr/ar/fa/he/ru
T68i EMEA6 CXC125382 R8A015 CXC125326 R8A015 en/fr/ar/fa/ru
T68i EU1 CXC125265 R8A015 CXC125326 R8A015 en/fr/pt/es
T68i EU2 CXC125319 R8A015 CXC125326 R8A015 en/fr/de
T68i EU3 CXC125323 R8A015 CXC125326 R8A015 en/fr/da/nl
T68i EU4 CXC125324 R8A015 CXC125326 R8A015 en/sv/no/fi
T68i EU5 CXC125515 R8A015 CXC125326 R8A015 en/fr/de/it
T68i NAM1 CXC125450 R8A015 CXC125449 R8A015 ae/cf/xl
T68i NAM2 CXC125544 R8A015 CXC125545 R8A015 ae/cf/xl
T68i US1 CXC125375 R8A015 CXC125326 R8A015 ae/cf/xl
T68i US2 CXC125376 R8A015 CXC125326 R8A015 ae/xl/bp
T68i Telenor CXC125777 R8B006 CXC125326 R8B006 ???
T68ie China CXC125278 R8A015 CXC125326 R8A015 en/zs
T68ie HongKong CXC125387 R8A015 CXC125326 R8A015 en/zh
T68ie Taiwan CXC125388 R8A015 CXC125326 R8A015 en/zt
Note 1: R6 and higher revision firmwares cannot be downgraded due to different file-
system used.
Note 2: T68i/T68ie phones have two firmwares and both should be of the same
15.26 T100/T100c/T102/T105/T106 Language Packages
Package Software ID Menu Languages SMS Languages
T100 Asian CXC125637 R9D en/in/ms/tl/th/vi abc/en/th
T100c/T102 Chinese CXC125638 R9D en/[zs]/[zt] abc/z/en
T100 Hindi CXC125887 R9D en/[hi] abc/en/hi
T100 Std1 CXC125639 R9D
en/sq/ar/hr/cs/el/
he/sr
abc/en/ar/hr/cs/el/
he/sr/cyr
T100 Std2 CXC125640 R9D
en/hu/pl/ro/sk/sl/st/
zu
abc/en/pl/cyr/hu/sk/
sl
T100 Std3 CXC125641 R9D en/tr/ru/ar/fa/fr
abc/en/ar/fr/tr/ru/
cyr
T100 Std4 CXC125667 R9D
en/de/fr/[it]/sv/da/
no/fi
abc/en/da/ic/fi/de/
fr/it/no/sv/cyr
T100 Std5 CXC125668 R9D
en/de/es/fr/[it]/nl/
pt
abc/en/nl/de/fr/it/
pt/es/cyr
T100 Std6 CXC125768 R9D en/pt/es/cf abc/en/fr/pt/es
T100 Std7 CXC125769 R9D
en/ru/bg/et/lt/lv/ro/
uk
abc/en/ru/cyr/uk
T106 CXC125701 R5D en/pt/es/cf abc/en/fr/pt/es
Note 1: Before flashing other languagepack to the phone, reset language to English,
please. In case the display is empty, use code <0000> to reset language to automatic.
Note 2: T100/T102/T105 R8 and higher revision firmwares cannot be downgraded.
Note 3: T106 R4 and higher revision firmwares cannot be downgraded.
Note 4: Chinese, Italian and Hindi languages have to be enabled separately.
15.27 T200/T202 Language Packages
T200 AsianLatin001 CXC1122339 R7A006 en/fr/ar/fa
T200 AsianLatin002 CXC1122340 R7A006 en/in/tl/vi
T200 AsianLatin003 CXC1122341 R7A006 en/ms
T200 AsianLatin004 CXC1122342 R7A006 en/th
T200 EMEA001 CXC1122334 R7A006 en/et/ru
T200 EMEA002 CXC1122333 R7A006 en/lv/lt/ru
T200 EMEA003 CXC1122343 R7A006 en/pl/ru
T200 EMEA004 CXC1122335 R7A006 en/hr/sr/sl
T200 EMEA005 CXC1122344 R7A006 en/cs/sl/hu
T200 EMEA006 CXC1122446 R7A006 en/tr/ru
T200 EMEA007 CXC1122447 R7A006 en/el/sq
T200 EMEA008 CXC1122336 R7A006 en/ro/hu/bg
T200 EMEA009 CXC1122337 R7A006 en/ar/he/ru
T200 EMEA010 CXC1122338 R7A006 en/fr/ar/fa
T200 EMEA011 CXC1122448 R7A006 en/ar/fr
T200 EMEA012 CXC1122330 R7A006 en/pt/es
T200 EMEA013 CXC1122483 R7A006 en/fr/de
T200 EMEA014 CXC1122449 R7A006 en/st/zu
T200 EMEA015 CXC1122331 R7A006 en/da/nl/fr
T200 EMEA016 CXC1122332 R7A006 en/fi/sv/no
T200 EMEA017 CXC1122329 R7A006 en/fr/de/it
T200 US001 CXC1122418 R7A006 ae/cf/xl
T200 US002 CXC1122419 R7A006 bp/xl/ae
T202 China CXC1122345 R7A006 en/zs
T202 HongKong CXC1122346 R7A006 en/zh
T202 Taiwan CXC1122347 R7A006 en/zt
15.28 T226/T230/T237/T238 Language Packages
T230 AsianLatin1 CXC1122641 R4A011 en/in/ms/tl/th/vi
T230 AsianLatin2 CXC1122642 R4A011 en/zs/hi/ms
T230 EMEA1 CXC1122646 R4A011 en/bg/et/lv/lt/pl/ro/ru/uk
T230 EMEA2 CXC1122647 R4A011 en/hr/cs/sr/sk/sl
T230 EMEA3 CXC1122648 R2A007 en/sq/bg/el/hu/ro
T230 EMEA4 CXC1122649 R2A007 en/ar/fa/fr/he/ru
T230 EMEA5 CXC1122650 R4A011 en/ar/fa/fr/ru
T230 EMEA6 CXC1122659 R2A007 en/ar/ru/tr
T230 EU1 CXC1122651 R4A011 en/fr/de/pt/es
T230 EU2 CXC1122652 R4A011 en/fr/de/zu
T230 EU3 CXC1122653 R4A011 en/da/fi/no/sv
T230 EU4 CXC1122658 R4A011 en/fr/de/it
T230 LAM1 CXC1122657 R4A011 en/bp/cf/xl
T238 China CXC1122643 R3A003 en/zs
T238 HongKong CXC1122644 R3A003 en/zh
T238 Taiwan CXC1122645 R4A011 en/zt
T226 US2 CXC1122654 R4A008 ae/[xl]/[cf]
T226 US1 (Cingular) CXC1122656 R3A006 ae/[xl]/[cf]
T237 CXC1122716 R5A013 ?
15.29 T290i/T290a/T290c Language Packages
T290i AsianLatin1 CXC1122893 R7A015 en/id/ms/tl/th/vi
T290i AsianLatin2 CXC1122894 R7A015 en/zs
T290i EMEA1 CXC1122898 R7A015 en/bg/et/lv/lt/pl/ro/ru/uk
T290i EMEA2 CXC1122899 R7A015 en/hr/cs/sr/sl/sk
T290i EMEA3 CXC1122900 R7A015 en/sq/bg/el/hu/ro
T290i EMEA4 CXC1122901 R7A015 en/ar/fa/fr/iw/ru
T290i EMEA5 CXC1122902 R7A015 en/ar/fa/fr/hi/ru
T290i EMEA6 CXC1122908 R7A015 en/ar/ru/tr
T290i EU1 CXC1122903 R7A015 en/fr/de/pt/es
T290i EU2 CXC1122904 R7A015 en/nl/fr/de/st/zu
T290i EU3 CXC1122905 R7A015 en/da/fi/no/sv
T290i EU4 CXC1122907 R7A015 en/fr/de/it
T290i LAM1 CXC1122906 R7A015 en/bp/cf/xl
T290a NAM/LAM CXC1122910_R6A011 en/bp/cf/xl
T290c China CXC1122895 R7A015 en/zs
T290i HongKong CXC1122896 R7A015 en/zh
T290i Taiwan CXC1122897 R7A015 en/zt
Note: This firmware may be uploaded into T230 phones. Be sure to upload also a
customization file into GDFS.
15.30 T300/T300c/T302/T306 Language Packages
T300 AsianLatin1 CXC125509 R1G001 en/ms/in/ar
T300 AsianLatin2 CXC125510 R1G001 en/tl/vi/th
T300 AsianLatin3 CXC125511 R1G001 en/zs/ms
T300 AsianLatin4 CXC125630 R1G001 en/th
T300 EMEA1 CXC125503 R1G001 en/et/lv/lt/pl/ru
T300 EMEA2 CXC125504 R1G001 en/cs/hr/sr/sk/sl
T300 EMEA3 CXC125505 R1G001 en/el/sq
T300 EMEA4 CXC125506 R1G001 en/bg/hu/ro
T300 EMEA5 CXC125507 R1G001 en/fr/ar/fa/he/ru
T300 EMEA6 CXC125508 R1G001 en/fr/ar/fa/ru
T300 EMEA7 CXC125547 R1G001 en/tr/ru
T300 EU1 CXC125422 R1G001 en/fr/pt/es
T300 EU2 CXC125423 R1G001 en/fr/de
T300 EU3 CXC125424 R1G001 en/fr/da/nl
T300 EU4 CXC125425 R1G001 en/sv/no/fi
T300 EU5 CXC125546 R1G001 en/fr/de/it
T300 US1 CXC125501 R1G001 ae/cf/xl
T300 US2 CXC125502 R1G001 ae/xl/bp
T300 Voicestream/T-mobile CXC125636 R2D001 ???
T302 China CXC125512 R1G001 en/zs/ms
T300c HongKong CXC125513 R1G001 en/zh
T300c Taiwan CXC125620 R1G001 en/zt
T306 CXC1122436 R1B005 ae/xl
T306 CXC1122547 R1B005 ae/cf
Note: T300/T300c/T302 firmwares are obsolete and therefore they should be
upgraded to T310/T310c/T312 by first uploading the respective data into GDFS and
then flashing the latest firmware for T310/T310c/T312.
15.31 T310/T310c/T312/T316 Language Packages
T310 AsianLatin1 CXC125509 R3B003 en/ms/in
T310 AsianLatin2 CXC125510 R3B003 en/tl/vi
T310 AsianLatin3 CXC125511 R3B003 en/zs/ms
T310 AsianLatin4 CXC125630 R3B003 en/th
T310 EMEA1 CXC125503 R3B003 en/et/lv/lt/pl/ru
T310 EMEA2 CXC125504 R3B003 en/cs/hr/sr/sk/sl
T310 EMEA3 CXC125505 R3B003 en/el/sq
T310 EMEA4 CXC125506 R3B003 en/bg/hu/ro
T310 EMEA5 CXC125507 R3B003 en/fr/ar/fa/he/ru
T310 EMEA6 CXC125508 R3B003 en/fr/ar/fa/ru
T310 EMEA7 CXC125547 R3B003 en/tr/ru
T310 EU1 CXC125422 R3B003 en/fr/pt/es
T310 EU2 CXC125423 R3B003 en/fr/de/st/south af
T310 EU3 CXC125424 R3B003 en/fr/da/nl
T310 EU4 CXC125425 R3B003 en/sv/no/fi
T310 EU5 CXC125546 R3B003 en/fr/de/it
T310 US1 CXC125501 R3B003 ae/cf/xl
T310 US2 CXC125502 R3B003 ae/xl/bp
T310 Telenor CXC125778 R3C005 ???
T312 China CXC125512 R3B003 en/zs/ms
T312 China CMCC CXC125672 R3D003 ???
T310c HongKong CXC125513 R3B003 en/zh
T310c Taiwan CXC125620 R3B003 en/zt
15.32 T600 Language Packages
Package Core Software ID LP ID Languages
T600 NorthernEU 0293323M sw47 02910 sw47 en/da/fi/no/sv
T600 EU1 0293323M sw47 02911 sw47 en/fr/pt/es/nl/de
T600 EU2 0293323M sw47 02912 sw47 en/fr/de/[it]
T600 Baltics1 0293323M sw47 02913 sw47 en/et/lv/lt/pl/ru
T600 Eastern EU1 0293323M sw47 02914 sw47 en/pl/ru/bg/hu/ro/tr
T600 Eastern EU2 0293323M sw47 02915 sw47 en/cs/hr/sr/sk/sl
T600 Eastern EU3 0293323M sw47 02916 sw47 en/el/tr/bg/ru
T600 MidEast-Africa 0293323M sw47 02917 sw47 en/fr/ar/ru
T600 Israel 0293323M sw47 02918 sw47 en/fr/ar/he/ru
T600 US 0293323M sw47 02919 sw47 ae/xl/bp
T600 Asian 0293323M sw47 02920 sw47 en/ms/tl/th/in/zs
T600 Singapore 0293323M sw47 02921 sw47 en/zs
T600 HongKong 0293323M sw47 02922 sw47 en/zh
T600 Taiwan 0293323M sw47 02923 sw47 en/zt
15.33 T610/T616/T618 Language Packages
T610 AsianLatin1 CXC125579 R6C005 CXC125562 R6C005 en/in/ms
T610 AsianLatin2 CXC125580 R6C005 CXC125562 R6C005 en/tl/vi/th
T610 AsianLatin3 CXC125581 R6C005 CXC125562 R6C005 en/zs/ms
T610 EMEA1 CXC125572 R6C005 CXC125562 R6C005 en/et/lv/lt/pl/ru
T610 EMEA2 CXC125573 R6C005 CXC125562 R6C005 en/cs/hr/sr/sk/sl
T610 EMEA3 CXC125574 R6C005 CXC125562 R6C005 en/el/tr
T610 EMEA4 CXC125575 R6C005 CXC125562 R6C005 en/bg/hu/ro
T610 EMEA5 CXC125576 R6C005 CXC125562 R6C005 en/fr/ar/fa/he/ru
T610 EMEA6 CXC125577 R6C005 CXC125562 R6C005 en/fr/ar/fa/ru/hi
T610 EU1 CXC125565 R6C005 CXC125562 R6C005 en/fr/pt/es
T610 EU2 CXC125566 R6C005 CXC125562 R6C005 en/fr/de
T610 EU3 CXC125567 R6C005 CXC125562 R6C005 en/fr/da/nl/de
T610 EU4 CXC125568 R6C005 CXC125562 R6C005 en/sv/no/fi
T610 EU5 CXC125569 R6C005 CXC125562 R6C005 en/fr/de/it
T610 EU6 Vodafone CXC125599 R6C005 CXC125596 R6C005 en/nl/el/pl/es/sv
T610 EU7 Vodafone CXC125598 R6C005 CXC125596 R6C005 en/fr/de/it/ar/hu/tr
T610 US1 CXC125570 Rxxxxx CXC125562 Rxxxxx ae/cf/xl
T610 US2 CXC125571 R6C005 CXC125562 R6C005 ae/xl/bp
T610 US3 T-mobile CXC125600 R6C005 CXC125586 R6C005 ae(VoiceStream)/xl
T610 HongKong CXC125583 R6C005 CXC125562 R6C005 en/zh
T610 Taiwan CXC125584 R6C005 CXC125562 R6C005 en/zt
T618 China1 CMCC CXC125582 R6C005 CXC125597 R6C005 en/zs
T618 China2 CXC125585 R6C005 CXC125562 R6C005 en/zs
Note 1: R1L and higher firmware revisions cannot be downgraded (without rebuilding
security zone) to lower versions due to new GDFS security zone format.
Note 2: R6B021 and higher firmware revisions (in an unpatched form) activate
special security feature of AVR ASIC, so the phone can't be booted in the old way.
Note 3: T610/T618 phones have two firmwares and both should be of the same
Note 4: For those who might be interested, here is the list of customization data IDs:
Customization Respective CDA ID
Vodafone EU6 A CDA102222/11
Vodafone EU6 B CDA102222/6
Vodafone EU6 C CDA102222/24
Vodafone EU6 D CDA102222/40
Vodafone EU6 E CDA102222/41
Vodafone EU7 A CDA102222/9
Vodafone EU7 B CDA102222/10
Vodafone EU7 C CDA102222/7
Vodafone EU7 D CDA102222/8
Vodafone EU7 E CDA102222/39
Vodafone EU7 F CDA102222/46
Vodafone EU7 G CDA102222/44
Vodafone EU7 H CDA102222/45
Vodafone EU7 I CDA102222/56
Vodafone EU7 J CDA102222/130
TMobile US3 A CDA102222/25
CMCC China1 A CDA102222/51
CMCC China1 B CDA102222/132
CMCC China3 A CDA102222/125
15.34 T628/T630/T637 Language Packages
T630 AsianLatin1 CXC125795 R6C005 CXC125802 R6C005 en/in/ms
T630 AsianLatin2 CXC125796 R6C005 CXC125802 R6C005 en/tl/vi/th
T630 AsianLatin3 CXC125797 R6C005 CXC125802 R6C005 en/zs/ms
T630 EMEA1 CXC125789 R6C005 CXC125802 R6C005 en/et/lv/lt/pl/ru
T630 EMEA2 CXC125790 R6C005 CXC125802 R6C005 en/cs/hr/sr/sk/sl
T630 EMEA3 CXC125791 R6C005 CXC125802 R6C005 en/el/tr
T630 EMEA4 CXC125792 R6C005 CXC125802 R6D003 en/bg/hu/ro
T630 EMEA5 CXC125793 R6C005 CXC125802 R6C005 en/fr/ar/fa/he/ru
T630 EMEA6 CXC125794 R6C005 CXC125802 R6C005 en/fr/ar/fa/ru/hi
T630 EU1 CXC125779 R6C005 CXC125802 R6C005 en/fr/pt/es
T630 EU2 CXC125780 R6C005 CXC125802 R6C005 en/fr/de
T630 EU3 CXC125781 R6C005 CXC125802 R6C005 en/fr/da/nl/de
T630 EU4 CXC125782 R6C005 CXC125802 R6C005 en/sv/no/fi
T630 EU5 CXC125783 R6C005 CXC125802 R6C005 en/fr/de/it
T630 EU6 Vodafone CXC125784 R6C005 CXC125805 R6C005 en/nl/el/pl/es/sv
T630 EU7 Vodafone CXC125785 R6C005 CXC125805 R6C005 en/fr/de/it/ar/hu/tr
T630 EU8 T-mobile CXC125806 R6C005 CXC125807 R6C005 en/de/nl/cs
T630 EU9 TIM CXC125876 R6C005 CXC125877 R6C005 en/fr/de/it
T630 US1 CXC125786 R6C005 CXC125802 R6C005 ae/cf/xl
T630 US2 CXC125787 R6C005 CXC125802 R6C005 ae/xl/bp
T630 US3 T-mobile CXC125788 R6C005 CXC125804 R6C005 ae(VoiceStream)/xl
T630 HongKong CXC125800 R6C005 CXC125802 R6C005 en/zh
T630 Taiwan CXC125801 R6C005 CXC125802 R6C005 en/zt
T628 China1 CMCC CXC125798 R6C005 CXC125803 R6C005 en/zs
T628 China3 GoTone CXC125808 R6C005 CXC125810 R6C005 en/zs
T628 China4 GMCC
GoTone100
CXC125809 R6C005 CXC125863 R6C005 en/zs
T637
CXC1122714
R3A025
CXC1122715
R3A025
en/???
Note 1: T628/T630/T637 phones have two firmwares and both should be of the same
Note 3: T637 is a newer phone and has another DSP circuitry than the previous
models.
15.35 V800/V802SE Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
V800 EU5 CXC125839 EU1 CXC125840 EU5 en/nl/el/pt/es/sv
V800 EU6 CXC125839 EU1 CXC125840 EU6 en/fr/de/it/ar/hu/tr
V800 EU7 CXC125839 EU1 CXC125840 EU7 en/fr/nl/de/si/hr
V800 EU8 CXC125839 EU1 CXC125840 EU8 en/nl/de
V800 EU9 CXC125839 EU1 CXC125840 EU9 en/fr/de/it/ar/hu/tr
V802SE Japan CXC125842 Japan CXC125840 JP1 en/jp/es/pt
Note 1: All these firmwares are customized for Vodafone. The least customized one is
EU9 firmware.
Note 2: You may also convert V800 into a Z800 phone. Language packages
description for Z800 is available here.
CDA102295/7 V800 Vodafone United Kingdom
CDA102295/9 V800 Vodafone Spain
CDA102295/12 V802SE Vodafone Japan
CDA102295/17 V800 Vodafone Sweden
CDA102295/18 V800 Mobilkom A1 Austria
CDA102295/19 V800 Swisscom Switzerland
CDA102295/20 V800 Proximus Belgium
CDA102295/21 V800 Vodafone D2 Germany
CDA102295/23 V800 Vodafone United Kingdom
15.36 W550i/W550c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
W550i APAC1 CXC1250086 China CXC1250032 APAC1 en/ms/id/tl/vi/zs
W550c Chinese CXC1250086 China CXC1250032 China en/zs
W550i Thai CXC1250086 China CXC1250032 Thai en/th
W550i HongKong
CXC1250087
HongKong
CXC1250032
HongKong
en/zc
W550i Taiwan CXC1250088 Taiwan CXC1250032 Taiwan en/zt
W550i America1 CXC1250031 EU1
CXC1250032
America1
ae/cf/xl
CXC1250032
America2
ae/bp/xl
W550i EMEA1 CXC1250031 EU1 CXC1250032 EMEA1 en/pl/lv/lt/ru/uk
W550i EMEA2 CXC1250031 EU1 CXC1250032 EMEA2 en/hr/cs/sr/sl/sk
W550i EMEA3 CXC1250031 EU1 CXC1250032 EMEA3 en/el/sq
W550i EMEA4 CXC1250031 EU1 CXC1250032 EMEA4 en/ro/hu/bg/ru
W550i EMEA5 CXC1250031 EU1 CXC1250032 EMEA5 en/ar/he/ru/fr/fa
W550i EMEA6 CXC1250031 EU1 CXC1250032 EMEA6 en/fr/ar/fa/ru
W550i EMEA7 CXC1250031 EU1 CXC1250032 EMEA7 en/tr/ru
W550i Europe1 CXC1250031 EU1
CXC1250032
Europe1
en/pt/es/fr
CXC1250032
Europe2
en/fr/de/st/zu/tr
CXC1250032
Europe3
en/da/nl/fr/de
CXC1250032
Europe4
en/fi/da/ic/sv/no
CXC1250032
Europe5
en/fr/de/it
Note: Never upload these files to a W600i phone!
15.37 W600i Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
W600i America1 CXC1123106 NAM1
CXC112307
America1
ae/cf/xl
W600i America2 CXC1123106 NAM1
CXC112307
America2
ae/bp/xl
W600i LAM1 CXC1123106 NAM1 CXC112307 LAM1 en/xl
W600i Cingular CXC1123106 NAM2 CXC112307 Cingular en/xl
W600i Rogers CXC1123106 NAM1 CXC112307 Rogers en/cf/xl
W600i Telcel CXC1123106 NAM1 CXC112307 Telcel en/bp/xl
W600i TIM Italy
CXC1123106
Generic
CXC112307 TIM
Italy
en/???
Note: Never upload these files to a W550i/W550c phone!
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
W800i APAC1 CXC1250174 China CXC1250093 APAC1 en/ms/id/tl/vi/zs
W800c Chinese CXC1250174 China CXC1250093 China en/zs
W800i HongKong
CXC1250175
HongKong
CXC1250093
HongKong
en/zc
CXC1250093
America1
ae/cf/xl
CXC1250093
America2
ae/bp/xl
CXC1250093
Europe1
en/pt/es/fr
CXC1250093
Europe2
en/fr/de/st/zu/tr
CXC1250093
Europe3
en/da/nl/fr/de
CXC1250093
Europe4
en/fi/da/ic/sv/no
CXC1250093
Europe5
en/fr/de/it
W800i E-Plus CXC1250092 EU1 CXC1250093 E-Plus en/nl/fr/de/es/tr
Note: You may upload these files to a K750i/K750c phone.
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
W810i APAC CXC1250317 China CXC1250324 APAC en/ms/id/tl/vi/zs
W810c China CXC1250317 China CXC1250324 China en/zs
W810i Central Asia
CXC1250316
Generic
CXC1250324
CentAsia
en/ar/ru/tr/uk
W810i Thai
CXC1250316
Generic
CXC1250324 Thai en/th
W810i Hong Kong
CXC1250318 Hong
Kong
CXC1250324
HongKong
en/zh
W810i America1
CXC1250316
Generic
CXC1250324
America1
ae/cf/xl
W810i America2
CXC1250316
Generic
CXC1250324
America2
ae/bp/xl
W810i Baltic
CXC1250316
Generic
CXC1250324 Baltic en/et/lt/lv/ru
W810i Central
Europe
CXC1250316
Generic
CXC1250324
CentEurope
en/cs/hu/pl/sk/uk
W810i
Mediterranean
CXC1250316
Generic
CXC1250324
Mediterr
en/bg/el/mk/ro/sq
W810i Middle East,
North Africa
CXC1250316
Generic
CXC1250324
MidEast_NorthAfr
en/ar/fa/fr
W810i South Asia,
Levan
CXC1250316
Generic
CXC1250324
SouthAsia_Levan
en/ar/fa/fr/he/ru
W810i Europe1
CXC1250316
Generic
CXC1250324
Europe1
en/pt/es/fr
W810i Europe2
CXC1250316
Generic
CXC1250324
Europe2
en/fr/de/st/zu/tr
W810i Europe3
CXC1250316
Generic
CXC1250324
Europe3
en/da/nl/fr/de
W810i Europe4
CXC1250316
Generic
CXC1250324
Europe4
en/fi/da/ic/sv/no
W810i Europe5
CXC1250316
Generic
CXC1250324
Europe5
en/fr/de/it
W810i EMEA Med
CXC1250316
Generic
CXC1250324 EMEA
Med
en/bg/el/ro/sq
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
CXC1250058
America1
ae/cf/xl
CXC1250058
America2
ae/bp/xl
CXC1250058
Europe1
en/pt/es/fr
CXC1250058
Europe2
en/fr/de/st/zu/tr
CXC1250058
Europe3
en/da/nl/fr/de
CXC1250058
Europe4
en/fi/da/ic/sv/no
CXC1250058
Europe5
en/fr/de/it
W900c China CXC1250252 China
CXC1250058
Chinese
en/zs
W900i APAC1 CXC1250252 China CXC1250058 APAC1 en/zs/id/ms/tl/vi
W900i HongKong
CXC1250253
HongKong
CXC1250058
HongKong
en/zh
15.41 Z200/Z208 Language Packages
Package AVR Software ID Languages SMS Languages
Z200 Config 1 CXC125718 R6C
en/sq/ar/hr/cs/el/
he/sr
abc/en/ar/hr/cs/el/
he/sr/cyr
en/pt/hu/xl/pl/ro/
sk/sl/st/zu
abc/en/hu/pl/sk/sl/
cyr
Z200 Config 3 CXC125720 R6C en/ar/fa/fr/hi/tr ???
Z200 Config 4 CXC125721 R6C en/sv/no/fi/da/de ???
Z200 Config 5 CXC125722 R6C en/es/pt/fr/nl/de ???
Z200 Config 6 CXC125774 R6C en/fr/pt/es ???
en/ru/ro/bg/et/lv/lt/
uk
???
Z200 Config 8 CXC125776 R6C en/de/[it]/fr ???
Z200 Asian CXC125723 R6C en/ms/tl/vi/th/in ???
Z208 Chinese CXC125724 R6C en/[zh] ???
Note 1: Z200/Z208 R1G and higher revision firmwares cannot be downgraded (to
R1E or lower).
Note 2: Chinese and Italian languages have to be enabled separately by flashing the
Z200 decustomization file.
15.42 Z500a/Z500i/Z500c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
Z500a LAM1 CXC1122854 NAM1 CXC1122755 RELA1 en/xl/pb/ae
Z500a Cingular CXC1122854 NAM1
CXC1122755
Cingular
???
15.43 Z520i/Z520c Language Packages
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
Z520i America1 CXC1250143 EU1
CXC1250151
America1
ae/cf/xl
Z520i America2 CXC1250143 EU1
CXC1250151
America2
ae/bp/xl
Z520a America2 CXC1123021 NAM1
CXC1250151
America2
ae/bp/xl
Z520i EMEA1 CXC1250143 EU1 CXC1250151 EMEA1 en/pl/lv/lt/ru/uk
Z520i EMEA2 CXC1250143 EU1 CXC1250151 EMEA2 en/hr/cs/sr/sl/sk
Z520i EMEA3 CXC1250143 EU1 CXC1250151 EMEA3 en/el/sq
Z520i EMEA4 CXC1250143 EU1 CXC1250151 EMEA4 en/ro/hu/bg/ru
Z520i EMEA5 CXC1250143 EU1 CXC1250151 EMEA5 en/ar/he/ru/fr/fa
Z520i EMEA6 CXC1250143 EU1 CXC1250151 EMEA6 en/fr/ar/fa/ru
Z520i EMEA7 CXC1250143 EU1 CXC1250151 EMEA7 en/tr/ru
Z520i Europe1 CXC1250143 EU1
CXC1250151
Europe1
en/pt/es/fr
CXC1250151
Europe2
en/fr/de/st/zu/tr
CXC1250151
Europe3
en/da/nl/fr/de
CXC1250151
Europe4
en/fi/da/ic/sv/no
CXC1250151
Europe5
en/fr/de/it
Z520i Vodafone 1 CXC1250144 EU2
CXC1250151
Vodafone 1
en/nl/el/pt/es/sv
CXC1250151
Vodafone 2
CXC1250151
Vodafone 3
en/fr/nl/de/hr/sl
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
Z530i APAC CXC1250455 China CXC1250290 APAC en/ms/id/tl/vi/zs
Z530c China CXC1250455 China CXC1250290 China en/zs
Z530i Central Asia
CXC1250454
Generic
CXC1250290
CentAsia
en/ar/ru/tr/uk
Z530i Thai
CXC1250454
Generic
CXC1250290 Thai en/th
Z530i Hong Kong
CXC1250457 Hong
Kong
CXC1250290
HongKong
en/zh
Z530i Taiwan CXC1250458 Taiwan CXC1250290 Taiwan en/zt
Z530i America1
CXC1250454
Generic
CXC1250290
America1
ae/cf/xl
Z530i America2
CXC1250454
Generic
CXC1250290
America2
ae/bp/xl
Z530i Baltic
CXC1250454
Generic
CXC1250290 Baltic en/et/lt/lv/ru
Z530i Central
Europe
CXC1250454
Generic
CXC1250290
CentEurope
en/cs/hu/pl/sk/uk
Z530i Mediterranean
CXC1250454
Generic
CXC1250290
Mediterr
en/bg/el/mk/ro/sq
Z530i Middle East,
North Africa
CXC1250454
Generic
CXC1250290
MidEast_NorthAfr
en/ar/fa/fr
Z530i South Asia,
Levan
CXC1250454
Generic
CXC1250290
SouthAsia_Levan
en/ar/fa/fr/he/ru
Z530i Europe1
CXC1250454
Generic
CXC1250290
Europe1
en/pt/es/fr
Z530i Europe2
CXC1250454
Generic
CXC1250290
Europe2
en/fr/de/st/zu/tr
Z530i Europe3
CXC1250454
Generic
CXC1250290
Europe3
en/da/nl/fr/de
Z530i Europe4
CXC1250454
Generic
CXC1250290
Europe4
en/fi/da/ic/sv/no
Z530i Europe5
CXC1250454
Generic
CXC1250290
Europe5
en/fr/de/it
Z530i EMEA Med
CXC1250454
Generic
CXC1250290 EMEA
Med
en/bg/el/ro/sq
15.45 Z600/Z608 Language Packages
Z600 AsianLatin1 CXC125742 R6C005 CXC125760 R6C005 en/in/ms
Z600 AsianLatin2 CXC125743 R6C005 CXC125760 R6C005 en/tl/vi/th
Z600 AsianLatin3 CXC125744 R6C005 CXC125760 R6C005 en/zs/ms
Z600 EMEA1 CXC125735 R6C005 CXC125760 R6C005 en/et/lv/lt/pl/ru
Z600 EMEA2 CXC125736 R6C005 CXC125760 R6C005 en/cs/hr/sr/sk/sl
Z600 EMEA3 CXC125737 R6C005 CXC125760 R6C005 en/el/tr
Z600 EMEA4 CXC125738 R6C005 CXC125760 R6C005 en/bg/hu/ro
Z600 EMEA5 CXC125739 R6C005 CXC125760 R6C005 en/fr/ar/fa/he/ru
Z600 EMEA6 CXC125740 R6C005 CXC125760 R6C005 en/fr/ar/fa/ru/hi
Z600 EU1 CXC125725 R6C005 CXC125760 R6C005 en/fr/pt/es
Z600 EU2 CXC125726 R6C005 CXC125760 R6C005 en/fr/de
Z600 EU3 CXC125727 R6C005 CXC125760 R6C005 en/fr/da/nl/de
Z600 EU4 CXC125728 R6C005 CXC125760 R6C005 en/sv/no/fi
Z600 EU5 CXC125729 R6C005 CXC125760 R6C005 en/fr/de/it
Z600 EU6 Vodafone CXC125730 R6C005 CXC125759 R6C005 en/nl/el/pl/es/sv
Z600 EU7 Vodafone CXC125731 R6C005 CXC125759 R6C005 en/fr/de/it/ar/hu/tr
Z600 EU8 T-Mobile CXC125749 R6C005 CXC125760 R6C005 en/de/nl/cs
Z600 EU9 TIM CXC125750 R6C005 CXC125751 R6C005 en/fr/de/it
Z600 US1 CXC125732 R6C005 CXC125760 R6C005 ae/cf/xl
Z600 US2 CXC125733 R6C005 CXC125760 R6C005 ae/xl/bp
Z600 US3 T-mobile CXC125734 R6C005 CXC125765 R6C005 ae(VoiceStream)/xl
Z600 HongKong CXC125747 R6C005 CXC125760 R6C005 en/zh
Z600 Taiwan CXC125748 R6C005 CXC125760 R6C005 en/zt
Z608 China1 CMCC CXC125745 R6C005 CXC125764 R6C005 en/zs
Z608 China2 CXC125746 R6C005 CXC125760 R6C005 en/zs
Note 1: Z600/Z608 phones have two firmwares and both should be of the same
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
Z800i EMEA1 CXC1250046 EU1 CXC1250055 EMEA1 en/uk/ru/pl/lv/lt/et
Z800i EMEA2 CXC1250046 EU1 CXC1250055 EMEA2 en/sr/sl/sk/hr/cs
Z800i EMEA3 CXC1250046 EU1 CXC1250055 EMEA3 en/sq/el
Z800i EMEA4 CXC1250046 EU1 CXC1250055 EMEA4 en/ru/ro/hu/bg
Z800i EMEA5 CXC1250046 EU1 CXC1250055 EMEA5 en/ru/he/fr/fa/ar
Z800i EMEA6 CXC1250046 EU1 CXC1250055 EMEA6 en/ru/fr/fa/ar
Z800i EMEA7 CXC1250046 EU1 CXC1250055 EMEA7 en/tr/ru
Z800i EU1 CXC1250046 EU1 CXC1250055 EU1 en/pt/fr/es
Z800i EU2 CXC1250046 EU1 CXC1250055 EU2 en/zu/tr/st/fr/de
Z800i EU3 CXC1250046 EU1 CXC1250055 EU3 en/nl/fr/de/da
Z800i EU4 CXC1250046 EU1 CXC1250055 EU4 en/sv/no/fi/da
Z800i EU5 CXC1250046 EU1 CXC1250055 EU5 en/it/fr/de
Z800i AsianLatin CXC1250047 China
CXC1250055
AsianLatin
en/zs/vi/tl/ms/id
Z800i Thai CXC1250047 China CXC1250055 Thai en/th
Z800i HongKong
CXC1250048
HongKong
CXC1250055
HongKong
en/zh
Z800i Taiwan CXC1250049 Taiwan CXC1250055 Taiwan en/zt
Note: This firmware may be uploaded into V800 phones.
CDA Numbers:
CDA102371/1 Z800i Generic EMEA1
CDA102371/9 Z800i Generic EU1
CDA102371/101 Z800i Generic AsianLatin, CI off
CDA102371/102 Z800i Generic Thai, CI off
CDA102371/104 Z800i Generic HongKong, CI off
CDA102371/105 Z800i Generic Taiwan, CI off
Package
Main Firmware ID
(zone)
File System ID
(languagepack)
Languages
Z1010i China CXC125680 China CXC125677 China en/zs
Z1010i Hong Kong
CXC125681
HongKong
CXC125677
HongKong
en/zh
Z1010i AsianLatin2 CXC125432 EU1
CXC125677
AsianLatin2
en/zs/ms
Z1010i EMEA1 CXC125432 EU1 CXC125677 EMEA1 en/cs/hu/pl/sk
Z1010i EMEA2 CXC125432 EU1 CXC125677 EMEA2 en/el/tr
Z1010i EMEA3 CXC125432 EU1 CXC125677 EMEA3 en/fr/ar/fa/he/ru
Z1010i EU1 CXC125432 EU1 CXC125677 EU1 en/da/nl/fr/de
Z1010i EU2 CXC125432 EU1 CXC125677 EU2 en/fr/pt/es
Z1010i EU3 CXC125432 EU1 CXC125677 EU3 en/fi/no/sv
Z1010i EU4 CXC125432 EU1 CXC125677 EU4 en/fr/de/it
Z1010i EU5
Vodafone
CXC125689 EU2 CXC125677 EU5 en/nl/el/pt/es/sv
Z1010i EU6
Vodafone
CXC125689 EU2 CXC125677 EU6 en/fr/de/it/ar/hu/tr
Z1010i EU7 Orange CXC125688 EU3 CXC125677 EU7 en/fr/de/it/ar/hu/tr
Z1010i TIM CXC125686 EU4 CXC125677 TIM en/fr/de/it
Z1010i O2 CXC125687 EU5 CXC125677 O2 ???
Z1010i THREE CXC125685 EU6 CXC125677 THREE en/fr/de/it
Note: Z1010 firmwares of version R1K010 and higher ignore bandlock setting.
Part
XVI
163 Additional Information
16.1 SE/LG/Sharp/Siemens Cable Pinouts
These pinouts apply to FastPort Sony Ericsson (K750), old Sony Ericsson (from T28 to
K600), LG 3G (U8xxx) and Sharp 3G (V802SH and V902SH) phones.
Figure 1. Sony Ericsson FastPort pin numbering
Figure 2. Ericsson and Sony Ericsson old pin numbering
Figure 3. LG 3G pin numbering
Figure 4. Sharp 3G video connector pin numbering
Figure 5. Siemens C62 pin numbering
C62 pin: Connect to:
1 IGN
2 GND
5 CFMS
7 CTMS
9 3.0V (or 12V via 10kOhm)
Note 1: Resistors R1 and R2 are intended to reduce noise levels on CTMS and DTMS
lines to allow higher flashing speeds (up to 921600Bd even with S700 phones). If you
connect them to your SE cable, don't forget to enable Using enhanced cables option
in the Settings window.
Note 2: For Sharp phones it is necessary to use an external power supply of 3.0V. Do
not use voltage higher than 3.3V.
Note 3: Sharp cable does not have autoignition functionality, therefore you have to
power the phone on manually (either by inserting a battery, by plugging-in a charger
or by pressing the power button).
Note 4: The acronym CFMS stands for "Control From Mobile Station" and CTMS
stands for "Control To Mobile Station".
16.2 CID Information
CID Licensee Phones Unlock Flashing
original
data
Flashing
non-
original
data
May be
converted
to
CID16
(10hex)
Sony
Ericsson
Z1010,... Full
support
Full
support
Full
support
CID36/37/
49/...
CID17
(11hex)
LG
Electronics
U8110,
U8120,
U8130,
U8138,...
Full
support
Full
support
Full
support
CID41/42
CID19
(13hex)
Ericsson Wakaba
prototype
Via TP Full
support
Via TP -
CID22
(16hex)
Siemens Xelibri
Series
N/A N/A N/A -
CID24
(18hex)
Sharp V801SH,
V902SH,
V903SH,...
Full
support
Full
support
Full
support
-
original
data
Flashing
non-
original
data
May be
converted
to
CID27
(1Bhex)
Siemens C62,... Only FW
v25-v28
Full
support
Full
support
-
CID29
(1Dhex)
Sony
Ericsson
K700,
V800,...
Full
support
Full
support
Full
support
CID36/37/
49/...
CID35
(23hex)
??? N/A N/A N/A N/A -
CID36
(24hex)
Sony
Ericsson
K300,
Z800,
K750,...
Full
support
Full
support
Full
support
CID37/49/.
..
CID37
(25hex)
Sony
Ericsson
K608,... Full
support
Full
support
Full
support
CID49/...
CID41
(29hex)
LG
Electronics
U8180,
U8380,...
Full
support
Full
support
Full
support
CID42
(partially)
CID42
(2Ahex)
LG
Electronics
U8330,... Full
support
Full
support
Full
support
-
CID46
(2Ehex)
Sharp N/A N/A N/A N/A -
CID47
(2Fhex)
??? N/A N/A N/A N/A -
CID49
(31hex)
Sony
Ericsson
K608,
W550,
W900,...
Full
support
(mostly)
Full
support
Full
support
-
CID50
(32hex)
Sony
Ericsson
N/A N/A N/A Via TP -
CID51
(33hex)
Sony
Ericsson
CID52
(34hex)
Sony
Ericsson
CID53
(35hex)
Sony
Ericsson
CID54
(36hex)
LG
Electronics
U8550,... Full
support
Full
support
Full
support
-
CID73
(49hex)
Sharp V903SH
(2006),...
Via TP N/A Via TP -
CID80
(50hex)
Sony
Ericsson
N/A N/A N/A N/A -
CID81
(51hex)
Sony
Ericsson
N/A N/A N/A N/A -
CID82
(52hex)
Sony
Ericsson
N/A N/A N/A N/A -
CID83
(53hex)
Sony
Ericsson
N/A N/A N/A N/A -
original
data
Flashing
non-
original
data
May be
converted
to
CID84
(54hex)
Sony
Ericsson
N/A N/A N/A N/A -
CID85
(55hex)
Sony
Ericsson
N/A N/A N/A N/A -
The security becomes stronger with higher CID numbers.

Cruiser v9.72 Guide

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cruiser v9.72 Guide

Încărcat de

Drepturi de autor:

Formate disponibile

2003-2006 Cruiser Team

Cruiser User's Guide

S-ar putea să vă placă și