Main element versions within the release:
• Product API 2012.2.2
• Nokia property Cable USB Driver Version seven.1.69.0
• Flash Update Package 2011.50
• FUSE affiliation Manager v 2011.51
MAIN CHANGES & ERROR CORRECTIONS FROM PREVIOUS VERSION 2011.46.7.47652
Error Corrections & changes:
• New products: RM-852, RM-838, RM-843, RM-844, RM-787, RM-788, RM-789
Please note:
Energy Management activity mustn\'t be performed for product exploitation the “Quantum” engine (RM-689, RM-702, RM-704 and alternative product exploitation identical engine)
• Microsoft DOT.NET version a pair of Service Pack a pair of is currently the minimum demand. Phoenix installation can check computer for the DOT.NET version and update it mechanically once computer has on-line affiliation. while not on-line affiliation, old DOT.NET versions should be updated manually.
• New common knowledge package location in use. Please see document SR1315 in KICS info Center for additional info.
• All Nokia Service software system Applications can use following location for product specific data:
- Windows XP: Cocuments and SettingsAll UsersApplication DataNokiaPackages
- Windows 7: Crogram DataNokiaPackages
•
Please see articles SR1774 for additional info on the employment of Nokia knowledge Package manager – tool, and article SR1854 for additional info on the Nokia Service Application Manager Tool.
• throughout installation, knowledge Packages ought to be put in in these directories, if they install to the other location by default. target folder for native knowledge packages is modified within the installation wizard manually
• This version contains the newest Tucson parts. so it\'s not necessary to use Tucson Add-On Installation Packages
• Before you begin Phoenix or Care Suite installation to Windows seven the User Account management (UAC) ought to be turned faraway from Windows panel settings.
• For additional info regarding new choices in “Firmware Update” – menu and their use, Please see documents SR1313 and SR1659 in KICS info Center.
• Tucson operations combined with “flash” – possibility square measure currently handled within the same approach as “refurbishment”, which needs Mass Memory Content File to be obtainable.
• Use of Flash possibility at the same time with product code modification for USB solely phones is restricted. it\'s suggested to flash phone one by one with microcode Update. Please talk to product specific directions.
• affiliation media to FLS-5 should be designed to be “USB_FBUS”, once FLS-4 support has been removed FBUS doesn\'t work any longer with FLS-5
KNOWN ERRORS & LIMITATIONS
• FLS-5 drivers don\'t support sixty four bit OS, thus phones exploitation FLS-5 /USB_FBUS affiliation can\'t be serviceable in sixty four bit in operation systems
• software system downgrade with Tucson system is barely doable for shot five.0 product supporting the info Package a pair of thought.
• Flashing with setup FLS-5, SS-46 and merchandise specific adapter isn\'t supported any longer. FLS-5 is used with alternative product specific cables and adapters, however not with SS-46 Interface Adapter.
• If you put in previous DCT-4 knowledge packages, Flash Update Package File installation path is also wrong. this is often caused by terribly previous DCT-4 knowledge packages that contain Flash Update Package and write current info throughout installation. If you expertise issues once change FPS-x prommers, please confirm Phoenix “Prommer maintenance” is searching for the files from the right location that is “Crogram FilesCommon FilesNokiaTssFlash”. If not, Phoenix can show error “Update via ini – file failed”. during this case, choose “Update” from that Phoenix “Prommer maintenance” – UI, browse to correct directory and choose “fpsxupd.ini” for all alternative prommers except the FPS-8.
• FPS-21 flashing for RX-51 works solely with TCPIP affiliation. FPS-21 prommer with new HW version eleven has been discharged to correct this. Sales pack code is 0089J83 , previous HW version isn\'t delivered any longer
• Please talk to product specific documents and directions regarding the restrictions of the RX-51 product
• once version 2010_12_8_42304 or newer with FUSE affiliation manager is put in on prime of older Phoenix versions, there is also an extra delay of many minutes once you begin Phoenix for the primary time. Please wait patiently; Phoenix can begin once configuration is finished.
• once exploitation knowledge Package transfer functions with on-line affiliation, transfer times could sometimes be long. this is often not caused by Phoenix (or Care Suite). The transfer speed from on-line servers is sometimes is understood to be slow, looking on however knowledge is buffered on caching servers.
• once you close up Phoenix, it should not restart. To rectify this:
- Use Windows Task Manager to manually clean up phoenix.exe and FuseService.exe processes, or optionally restart your computer
• it\'s unattainable to program Mass Media Content file to some devices over direct USB cable affiliation, thanks to the massive size of the file. For these models a feature known as “Media Check” has been enforced. once this sort of product is connected to service software system / computer via direct USB cable the improvement possibility are disabled. Please use a flash prommer. Affected product exploitation Media Check are: RM-122, RM-175, RM-176, RM-186, RM-246, RM-247, RM-296, RM-297, RM-320, RM-462, RM-472, RM-484, RM-505, RM-555, RM-559
• To be ready to use the assistance files in Windows seven you wish to put in Windows facilitate program (WinHlp32.exe) for Windows seven. ways in which to find WinHlp32.exe:
- begin Phoenix with on-line affiliation to web, choose “Help” and “Phoenix help”. Click the “Microsoft facilitate and Support” web site link. transfer WinHlp32 and install it.- attend http://www.microsoft.com. kind “WinHlp32″ to “Search Microsoft.com” – field. find Windows facilitate program (WinHlp32.exe) for Windows seven and install it
• once exploitation flash prommers, only 1 affiliation kind to 1 prommer is allowed. Please use either NFPD USB or NFPD TCPIP affiliation to 1 prommer, not each connections to same prommer.
Supported in operation systems and user rights
• Windows XP Service Pack one or higher
• once putting in Phoenix into Win XP you need to have native admin rights.
• once exploitation in Win XP, user should have computer user rights.
• Windows seven thirty two Bit version
• Windows seven sixty four Bit version (Please note that FLS-5 drivers don\'t support Win seven sixty four bit OS, so FLS-5 can\'t be utilized in this in operation system).
Download
