DllRegisterServer DllUnregisterServer
ADL Server: Data Integrity Error while sending message 0x%1!.2X!.WN ADL Server: Insufficient Data for Block Error while sending message 0x%1!.2X!.G ADL message send error code: 0x%1!.2X! while sending message 0x%2!.2X!.WWW+ Adl Loader does not start. This may happen if USB has not yet configured, in this case wait USB to configure and restart the operation.WWWu Adl Server: Unable to reboot to update mode 0x%1!.2X!. Server may not support this UPS.WWWF Adl Server: Unable to send READY_FOR_REBOOTWWWW Boot rom was not detected after phone boot up. Unable to start flashing. WJ Communication error during loader flashing. Unable to flash loader.WWWM Communication lost to UA during flashing. Unable to continue. Verify device is connected and device drivers are loadedv Communication lost to UA during negotiation. Unable to flash. Verify device is connected and device drivers are loadedZ Communication with phone is not possible. Unable to detect phone operation mode, cannot continue.W Critical error while erasing APE data. %1!s!W1 Critical error while erasing APE data. Flashing operation aborted.F Critical error while erasing CMT data. %1!s!WW- Critical error while erasing CMT data. Flashing operation aborted.B Critical error while partitioning APE data. %1!s! Critical error while partitioning CMT data. %1!s!2 Critical error while programming APE data. %1!s!W2 Critical error while programming APE data. Flashing operation aborted.[ Critical error while programming CMT data. %1!s!W1 Critical error while programming CMT data. Flashing operation aborted.F Device reported that firmware update failed error code from device = 0x%1!.4X!.WW Enables/disables production error monitor log file writing.WWW& Error decrypting flash image.W Error in FPGA memory function Error in USB driver, communication timeout6 Error in parsing image data. This means bad or unsupported file.WW2 Error in starting update mode. Software update operation could not be started.I Error in the request message format WW4 Error searching disc for %1!s! file from disc. Error when loading fpga code to chip W Error while accessing a flash file. Check that input files are available.W: Error while uploading files to the device. Software update operation could not be started.N File error while %1!s! file %2!s!W( File format error in the Algorithm file. W| File format error in the MCUSW file. Wx File format error in the Secondary boot file. File or port handling error WW Gets phone information from ADL. If normal Mcu Sw is running, error is returnedWWW* Internal Communication error W Internal error 0xF144. Phase %i Internal error occured, cannot continue. Please check the application's installation.W/ Internal error while handling smartcard. If the problem persists return card to Nokia.$ Invalid UA file. Unable to parse UA. The file is either not supported or corruptWW^ Invalid ULO file. Unable to parse ULO. The file is either not supported or corrupt( Invalid file. Unable to parse programming blocks. The file is either not supported or corrupt.R Invalid response received from UA. This image maybe incompatible with this device. Unable to continue flashingv Memory error W% No FIASCO_BB5_CODE_START sub block in the MCUSW file.W( No time stamps found in file. Unable to perform downgrade checkWWWB Nothing programmed to the phone. This error means that phone was not in flash mode when certificate was tried to program. X Nothing programmed to the phone. This error means that the values of FIASCO_PROGRAMMING_TARGET sub block (in FIASCO_PHONE_PROGRAM_REQ message) conflicts with the contents of the MCUSW file. Nothing programmed to the phone. This error means that the values of FIASCO_PROGRAMMING_TARGET sub block conflicts with the contents of the MCUSW file. WW Obsolete. Gets detailed error information matching an error code.W7 Phone has not acknowledged BB_WAIT_TASK_READY message. This error has not affect to programming of MCU. In APE flashing this means that APE side programming status was not received by CMT side. Check the USB connection. WW[ Phone returned error response. Operation cannot be continuedWWF Processing a command from application has failed due to internal error in Prommer's FPGA driver.WWC Programming Device has detected a checksum error in the received frame header.2 Programming Device has detected a checksum error in the received frame headerWy Prommer has detected a checksum error in MCUSW.WWW5 Prommer was unable to reselect the applet that PC was using before prommer selected his own.WWO Start phone recovery after last failed flash attemptWW Terminal Response error received from phone. %1!s!# The Phone MCU can not start Secondary code correctly. + The Phone does not set Flashbus TXD line high after the line has been low. The Prommer generates this error also when the Phone is not connected to the Prommer ??? WW/ The Phone does not set Flashbus TXD line low after the line has been high. The Prommer generates this error also when the Phone is not connected to the Prommer. Wb The Prommer has detected a checksum error in the MCU_CONFIGURATION_RESPONSE_DCT4 message, which it has received from the Phone. WW The Prommer has detected a checksum error in the MCU_ID_RESPONSE message, which it has received from the Phone. WWo The Prommer has detected a checksum error in the MCU_MSID_RESPONSE message, which it has received from the Phone. q The Prommer has detected a checksum error in the MCU_PROGRAM_STATUS_RESP_DCT4 message, which it has received from the Phone. W| The Prommer has detected a checksum error in the SYSTEM_ID_RESPONSE message, which it has received from the Phone. WWWr The Prommer has detected a checksum error in the message, which it has received from the Phone. WW_ The Prommer has detected an error between main processor (MMCU) and Security processor (SMCU) communication. W/ The file collection is invalid. Unable to flash. See flash log! The format error in the request message WW0 The phone flashes are not verified. This error means that the values of FIASCO_PROGRAMMING_TARGET sub block (in FIASCO_PHONE_PROGRAM_REQ message) conflicts with the contents of the MCUSW file. E.g. this error can be returned if all parameter fields in the sub ?G? The phone has sent too long message to the prommer. Error during target phone flash erasing WWS The requested feature is not supported. Error in BB5 APE Algorithm code file WZ The requested feature is not supported. Error in BB5 MCUSW file WW8 The target phone echoes data after restart but before it is forced to UEM loopback mode. WF There is a problem in MCU SW file or bug in the Programming Device. This error happens when the Programming Device cannot send data to requested ASIC. Possible reasons: MCU SW file is faulty or bug in Programming Device SW or in algorithm SWWZ There is no response from phone after loading Adl Loader. Unable to continue.W There was no APE loader data found after searching all locations. Unable to flash.B There was no CMT loader data found after searching all locations. Unable to flash.R Timeout or parity error occurred while trying to read from SC.9 UA Error - Insufficient information to flash phone. Unable to continue* Unable to communicate with product. Unable to even start flashing. Please check connection.WWWI Unable to communicate with the device after flashing. Check USB connections!WW, Unable to communicate with update serverWWb Unable to extract APE loader data from imageWW# Unable to extract CMT loader data from imageWW, Unable to format %1!s! data.WW* Unable to get board id Unable to get bootloader versionWW0 Unable to get phone info.W* Unable to select Loader from %1!s! because folder is empty.WWW' Unable to verify communication with device after flashing has finished: Unexpected error during flashing with UA. Unable to continueWWn Unknown error in FPGA driverWW' Unknown error verifying the Smart Card PIN code. Check that a Smart Card is connected.L Update server/Algorithm code did not start in target device. Unable to continueWWWv