EasyManua.ls Logo

Nokia RM-721 - Requirements; Terms in Tucson; Tucson Troubleshooting

Nokia RM-721
160 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Tucson troubleshooting
Requirements
Latest Phoenix Service Software
Tucson add on” package if one has been released between complete Phoenix releases
FPS-10 or 21 Flash prommer updated with latest flash update package
- Latest product specific data package, supporting for the variants you want to change the phones to.
Certificate restoring without flashing does not require data packages to be installed
SX-4 or SX-4T Smart Card, which has been registered for Tucson use in Nokia Online Security Device Master,
and for which local Nokia Care has granted Tucson user rights
BB 5.0 models:SS-46 with phone specific flash adapter connected to flash prommer
DCT-4 models:JBV-1 with phone specific flash adapter connected to flash prommer
Active online connection to internet, please refer to Technical Bulletins for IP addresses
Terms in Tucson
Certificate restore BB 5 and IMEI rebuild
When certificate restoring for BB 5 products or IMEI rebuild for DCT-4 products is performed, existing data
from Nokia System is programmed in the phone. The phone will be in the same condition as it was when it
left the factory for the first time.
If “Product Code Change” has been SUCCESSFULLY performed with Tucson after the phone left the factory, it
will be restored back to the variant it was made into during Product Code change event.
It is recommended to perform “Restore” function without selecting “Flash Product” – option to avoid possible
SW downgrade which causes the phone to die.
Product code change with Tucson connection
When Product Code change with Tucson is successfully performed, phone variant will be changed. Data for
the new variant is extracted from Nokia System, and programmed in the phone.
After successful change, phone specific information in Nokia systems will match the new variant, and it can
be used for e.g. certificate restoring. If you perform several product code changes, Nokia system will always
be up to date with the latest successful event.
Failed / incomplete actions will not change the phone specific information in Nokia systems.
This function can be performed with or without flashing the phone with correct software, selection can be
made by checking / unchecking the tick box on Phoenix UI.
Options for product code change
"van2var" is Tucson operation which you can change open (i.e. not Sim Locked) terminal to another variant,
possibly creating a Sim Locked terminal. It only allows you to change to another open terminal or to locked
one, but not back. Variant itself is any variation of terminal (some may be as simple as cover color, language,
operator customization etc). Variants are either open or locked to some operator.
"var2var" is Tucson operation which allows you to create any compatible variant regardless what the source
is or whether it is locked or not. You can for example take operator locked phones and create unlocked vanilla
terminals out of them. Only few have this permission and it also requires use of SX-4T type Smart Card.
BB 5 downgrade
If BB 5 generation product is programmed with older software than already exists in the phone, it will become
“dead”. This happens if programming is done without Tucson connection.
RM-721; RM-722
BB Troubleshooting and Manual Tuning Guide
Issue 1 COMPANY CONFIDENTIAL Page 3 – 43
Copyright © 2011 Nokia. All rights reserved.

Table of Contents

Related product manuals