JAF Glossary
JAF Glossary
JAF Glossary
another example:
RM-36_v 8.00 (mcusw 5.050407) Euro
for EURO countries
================================================================
DCT4 tab
ADSP : Advance Digital Signal Processor, flash file for DSP chips
Use INI :
When you thick this, software will detect phone connected type, and "Use INI" files setting
when exist in "Product Directory" for choosing flash files.
INI : (*.ini)
This file contains flash files setting for each "Product Code", including MCU, PPM, CNT,
PP (Product Profile), etc.
(Even in 3250, different product code may have different MCU to be flashed).
These files are extracted from firmware/data package that we have installed.
Use this option in order to avoid choosing wrong flash files, example :
- If you don't know for sure which MCU, PPM, or CNT.
- Choose right PPM for language that you want
- How to choose right CNT that suitable with your PPM
After a Product Code has been chosen automatically, you can change it manually with other
Product Code that you want to flash.
Run INI :
After flashing completed, software will upload also Product Profile according INI that has
been chosen and flashed.
Product Profile :
This file contains customization for each Product Code, example : GPRS settings, WAP
bookmarks, etc..
For Communicator Phone, this file also contains keyboard layout.
Load NFP:
NFP: Nokia File Protected
Data package (MCU, PPM, and CNT) for nokia CDMA phone was compressed as a file :
*.NFP, and it is protected by password.
Thick this option, choose *.NFP, software will extracted it automatically as MCU, PPM, and
CNT.
Easy Cable :
It’s a special cable, suitable with pop-up connector for few type phone, ex : 1600, which can
be use for flashing. Thick this if you use this kind of cable.
RPL 208 :
PM field number 208 was copied from DATA1/ IMEI flash data.
Software will back up this area as RPL(DATA1 only), that useful for recover flash IMEI if
something happen after flash (IMEI ????), or you changed flash IC, you no need to change
UEM also if you have back up for this phone. Some type don't have this field, like 1100,
2300, etc. Make sure your phone can enter Local Mode for this option.
FTD ON:
FTD : Field Test Display / Net Monitor : special menu for DCT4 and DCT4 TIKU that can
be activated with flashing, it contains many feature for testing phone and network.
Product Code :
Every Nokia phone has 7digit number that written in the back sticker.
This Product Code will differ phone that sold to one country and another, also phone that sold
with customization for an operator, will have different Product Code also.
This number also saved somewhere in PM area.
Thick "Change Product Code" will change Product Code number in PM area after flashing
completed.
Factory Set :
Reset all settings to factory default after flash completed.
Manual Flash:
this option will disable software detect the phone model and open his folder when you click
on "MCU", "PPM", etc, or thick on "Use INI"
Warranty :
When you press *#warranty# or *#92702689#, phone will display some hidden information
like Serial Number, Made, etc, including "Life Timer".
This option after flash will reset "Life Timer" back to zero after flashed.
Unlock:
Initialize sim lock after flash
SKIP tab :
Skip Erase :
normally, software will erase first some area according Flash Files needed before writing
them. If you thick this option, without erase first, software will write the Flash Files that
have been chosen. Use this option only if you already have fully erased the phone manually.
Skip AFP :
AFP : After Flash Processing
After flashing completed, software will try to put the phone into Local Mode and read some
info about it. This option will disable that process.
Use this only if you know why this process should be skip, example you flash an Erase File
that make the phone dead/ fully erase.
Not all Erase File erase whole part of flash IC, some Erase File only erase some part of flash
IC and phone still alives.
Skip MCU ID :
MCU ID is UPP (Universal Phone Processor) recognition, inside flash file, there's
recognition for MCU ID that supported (by that flash file).
Use this option only if you sure that you flash the phone with right flash file, but software
give warning that MCU ID is not supported by flash file that have you choose.
Note : usually warning about MCU ID is not supported but right Flash Files has been chosen
is caused by bad cable connection. Try restart software, reconnect F-Bus cable from phone,
and try again.
For dead phone suspected / possibility hardware problem, if MCU flashing has been
completed, continue flashing with PPM only usually will solve.
BT :
Bluetooth IC have own firmware including in MCU file.
You may skip this if you flash the phone with same version, this will save flashing time a
little.
But you have to skip this if BT IC is damage, it's indicated with when you flash a phone and
software error in the middle with warning : "Error loading additional loader.."
Operations Tab :
INF : INFO
Make sure your phone can enter Local or Test mode for this operation.
At the end of this operation, software will detect phone's Product Code and load Flash Files
according it.
If no suitable product code found, you must thick "Manual Flash" and then "Use
INI",software will ask you to "Select Phone Model".
You can sort it by "Type" or by "Name", or you can type phone code like RH-12, and all
"INI" settings for this phone will be loaded, and can be chosen.
Note : if you don't find your phone type or name in the list, but you have Data Package
installed for this phone, open "jaf_nok4models.ini" with Notepad and add it like this
[RM-307]
Description=Nokia 2505
CHK : Check
Will check phone hardware condition like
- Relation between UEM (Universal Energy Management - power IC) and UPP (Universal
Phone Processor)
- MCU ID / UPP
- Flash IC
- RAM IC
- First 16 bytes
- FAID Calculation
Remember, bad F-Bus cable also make this operation failed !!!
Service:
This button related with "Service Operations" tab
Erase Flash:
Software will try to back up RPL 208 if your phone can enter Local Mode or IMEI Flash
Data not corrupted, or RP 208 exist, and then check phone hardware like MCU ID, etc and
display Erase Flash Manager.
FULL Erase :
Full Erase will erase all Flash IC, including PM (Permanent Memory), & will make SIM
Lock Data corrupted.
Make sure that you have back up PM to be uploaded after flash and unlock after this
operation.
Click Start Erase to execute this operation.
PM : Permanent Memory, an area in flash IC that wasn't reached by flash files, means
normal flashing shouldn't change it's value.
It contains data of RF, EM, Product Code, Security Code, and so many more.
For some type it also contains backup IMEI Flash Data, even phone book and gallery content.
PM file can be opened with Notepad or Wordpad.
PM area indicates with :
Field Number 0 - xxx (some type has field numbers <200, some has <255, but newer phone
type may have 300>).
Each "Field Number" may has sub "Record Number"
Field Number indicates with : [x]
And Record Number indicates with : x=
If you fully erase a phone, you can upload PM that you have read from another phone which
same type, but make sure you have deleted field 5, 120, and 208 from it, 'caused it contains
IMEI data.
Prod Dir :
Change default Flash File detection from C:\Program Files\Nokia\Phoenix to another.
(Un)Lock:
this button related with "Unlock settings" tab
Init simlock : Initialize SIM Lock, remove Operator SIM Lock restriction
Write SIM file : write file *.SIM that contains SIM Lock settings.
Code Calculator : calculate codes from IMEI number, network code, and ASIC code, for
initialize SIM Lock, enter it with type the codes manually with keypad
Read Codes : read phone for IMEI and calculate code for initialize SIM Lock
Auto Lock: after this operation, phone will recognize network code from first SIM Card that
inserted to phone, and lock to this network.
Autolock IMSI :
IMSI : International Mobile Subscriber Identity, after this operation, phone will recognize
first SIM Card that inserted and lock phone to this SIM.
Lock to Network: enter the network code manually and phone will be lock to this network
Load JAVA :
Upload JAVA application to the phone
MMC Rst:
with special cable adapter, this will reset locked Memory Card
Make INI:
If you have chosen your flash file manually or USE INI, this operation will create your own
"INI file" for that type. After this, software will automatically load that flash files after INF
pressed.
IMEI tool:
If you changed UEM and do not want to calculated RPL, you can use "free supplied rpl" that
come with software installation, but you have to write RPL with same ASIC to your phone.
IMEI Patch:
this will "patched" IMEI Plain, IMEI that showed by pressing *#06#, with desired IMEI that
you want. Patch options only work for DCT4 ASIC2.
And this only work for normal phone, means patch WILL NOT SOLVE problem
IMEI ????????? that 'caused by DATA1 corrupted.
If you try this with phone that have problem IMEI ?????????, Watchdog timer will be
enabled, and your phone will restart after +/- 30 seconds.
Upload TUN : RF value for CDMA phone was saved with file named *.tun.
Prod. Manager :
Read or change/write some value that saved in PM area:
- Product code
- HW version : Hardware Version : please be careful edit this for RM-72 - 6230i, 'cause PPM
and CNT flash file was different between old and new HW version.
- Order Number
- Production SN
- Manufacture Month : in phone showed by typing *#warranty#
So, if software can not detect File System correctly, try making Full Factory before execute
this again.
User Code Edit:
Read Security Code which saved at PM filed number 35.
ADC Read :
Analog to Digital Converter : some Self Test about phone battery, charger, etc
Fun Explorer :
About exploring JAVA application in DCT4 phone.
Warranty Reset :
look above about Warranty.
Phone Mode:
(?) read phone status
change phone mode to
Local Mode
Test Mode
Normal Mode
Communication Mode:
F-Bus cable : flasher cable
USB: DKU-2/CA-53, when you connect DCT4 TIKU with this cable, you will be able to
make some operation like : make Full factory, Init SIM Lock, etc, but not for flashing.
--------------------------------------------------------------------
BB5 tab
BB5 phone :
BB : Base Band
Single chip : have only CMT processor. example : 6270, 62880, etc
Dual chip : have two processor, CMT (cellular Mobile telephone) and APE (Application
Processor Engine) example : 6630, 6680, N70, etc.
Communication Mode:
F-BUS cable : use only 7 pins cable for flashing with JAF box.
Make sure your phone can enter Local or Test Mode !!!
If not, maybe you need to check your cable, and then modified it, if not suitable with JAF
specification.
1. NEVER EVER try putting 9v battery in F-BUS cable though your cable has this
connector !!!
2. Resistance between BSI-GND must be 68k ohms, if less than it, maybe you will find "error
sync the phone when make "CHK"
3. Resistance in BSI serial must be 5,1k(5k1) or 7,5k(7k5) ohms. Otherwise your phone can
not enter Local / Test Mode.
4. Make sure VPP line from RJ45 connected to RX2 in phone.
Never use cable that connected VPP line in RJ45 with VPP in phone, you will get error
something like "Error APE get id"
I don't give explanation about P-KEY and UFS Box, because newer BB5 phone with
RAPIDO processor doesn't supported by UFS Box.
USB : all (alive) BB5 phone supported by USB flashing, you may use DKU-2 or CA-53, but
some types needs DKE-2/mini USB for this operation. make sure your battery fully charged,
or charge it with an original charger before start flashing.
When you flash phone and software give error warning "error getting flash id",
put sim card inside, do not select offline mode, and flash the phone.
Note : make sure you disable all connection in PC Suite (if you installed Nokia PC Suite
software in your PC) when using this service.
Dead USB :
Few types of BB5 with single chips supported by "Dead USB flashing".
Choose flash file manually, connect USB cable to phone, and when software give command
to "press the power now", press switch on/off briefly. In windows systems try, will show
"Nokia USB ROM", and windows will install the driver automatically.
For some types, successfully dead USB flashing will revive the phone, but gallery content
will be empty, so you need to flash again with USB as normally.
Downgrade :
This option based on Dejan's trick to be able to flash a working/normal BB5 phone with
lower version.
Maybe not all BB5 supported by this option. So, if you try downgrade and the phone become
dead, flash again with latest/highest firmware version.
CRT 308:
PM field number 308 contains SIM Lock data, make sure your phone can enter Local Mode
before flash, in order to make successful back up.
If something wrong after flashing process and SIM Lock Data become corrupted, use Write
PM and choose this back up to be written to the phone. Your sim lock state will back like
before flashing.
SX4 Authority :
BB5 phones have protection for writing RF(1 ) and Energy(309, 0x135 in hex) settings in
EPROM. Not having those settings in phone, is known as 'Contact Retailer Problem', or
'Security Error' in Self Test. In order to write those settings phone requires an authorization
that only SX4 Smart Card can perform.
As those cards are hard to get, software can use server support for this authorization.
To authorize, connect BB5 phone, and power it on.
Press "SX4 AUTH". If you have SX4 card connected to PC, software will use it to compute
the authorization password and send it to phone.
If you don't have card, software will connect to server to compute authorization password.
If this process have sucessfuly done, Write PM to the phone without field number 308.
===============================================================
Update Loaders:
FIA = Flash Identification Address are files that needed for flashing, to identify MCU ID and
Flash Files which suitable with phones. If you press this, software will check whether new
version from support site exist and replace your flash loaders with new one if you download
it.
===============================================================