Operation finished successfully. Unknown error. Try to reset the loader and if problem still exist, report it. Check the input parameters in the command that you try to execute. Repeat operation. Report if problem is not solved. Try to reset the loader and if problem still exist, report this error. Try to reset the loader and if still exist the problem, report this error. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Internal malicious state detected in IO layer. Report this problem. Check the communication cable and restart the loader. Try to reset the loader and if still exist the problem, report this error. Try to reset the loader and if still exist the problem, report this error. Try to reset the loader and if still exist the problem, report this error. Try to reset the loader and if still exist the problem, report this error. Possible hardware problem. Communication device do not respond and try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Reset the loader. Report if problem still exist. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Current transfer is not finished. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. Try to reset the loader. If the problem still exist, report this error. USB bulk transfer in DMA mode 1 is only supported. Check the input value of the command that you try to execute. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Some internal error occurred and you need to reset the loader to avoid further unpredictable behaviour. Possible error in zip format.Verify that the zip is not corrupted,otherwise report the problem. Possible error in zip format.Verify that the zip is not corrupted,otherwise report the problem. Possible error in zip format.Verify that the zip is not corrupted,otherwise report the problem. Internal error.Reset loader.Report if problem still exist. Verify that archive is successfuly flashed.Reset loader. Report if problem still exist. Check the authentication type. The loader supports authentication with CA certificate and control keyes.Repeat authentiacton. Report if problem still exist. Default system time is used.Set the Time properly. Report if problem still exist. Report this problem You must erase the flash before flashing archive with different flashlayout. Check files in flash archive. Empty files not allowed. Try to restart the loader and if still exist the problem, report this error. Try to erase flash and restart the loader and if problem still exist, report it. Try to erase flash and restart the loader and if problem still exist, report it. During previous flashing some fail condition occurs. Reflash same archieve again before try a new one. Try to use loaders with support for memory device attached to DBB. If loaders does not exist, fire CR in FIDO to get loaders that support that memory. Check MEMCONF settings in flash archive. Check MEMCONF settings in flash archive. Very likely flash archive is built for ME with flash device with larger capacity Check CABS settings in flash archive. Very likely flash archive is built for ME with flash device with larger capacity Entry stated in manifest file is not found in flashlayout file. All entries in manifest must be defined in flashlayout file. Entry start address in manifest and flashlayout are not equal. SUBTOC parameters are not valid. Reading SUBTOC from flash failed. Overlapping partitions found in the archive. Partition not found in TOC. Flashlayout data equals NULL. Loader internal error. Report this issue to loaders team. Input buffer in create TOC list functionality is filled from empty location. Report this issue to loaders team. Erase flash and try all procedure once again. If problem still exist report it to loaders team. Flash archive first before using some TOC operations. There is no boot area on flash, nor in the archive you are trying to flash. Entry start address or flash device in manifest are not equal to TOC. The file is too large to be placed in the partition. Increase the partition size and try to flash the file again. If problem still exist, report it The file is too large to be placed in the boot area. The requested dump size is outside of the flash range, available flash range is dumped. Please use physical erase configuration for this command. For more details please consult the user manual. Archive contains image marked for enhanced area, but enhanced area is not set on eMMC Image marked for enhanced area has start and/or end address out of enhanced area eMMC driver returned error while setting enhanced area Verify that supplied path is valid. Repeat operation. Report if problem still exist. Repeat operation. If still doesn't work reset loader. If that does not resolve problem report it. Use Volume Properties command to check if enough memory space exists. Report problem in case of information mismatch. Check the access of the file. Repeat operation. If problem still exist possible file system corruption and you need to reset the loader. Report if problem is not solved. Check the access of the file. Repeat operation. If problem still exist possible file system corruption and you need to reset the loader. Report if problem is not solved. Use Volume Properties command to check if enough memory space exists. Repeat operation or reset loader. If problem still exist possible file system corruption. Report the problem. Check the access of the file. Repeat operation. If problem still exist possible file system corruption and you need to reset the loader. Report if problem is not solved. Use Volume Properties command to check if enough memory space exists. Report problem in case of information mismatch. Repeat operation or reset loader. Report if problem still exist. Internal error. Possible file system corruption. Repeat operation or reset loader. Report if problem still exist. Internal error. Repeat operation or reset loader. Report if problem still exist. Check the access of the file and check input parameters. Repeat operation. If problem still exist possible file system corruption and you need to reset the loader. Report if problem is not solved. Internal error. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Internal error. Repeat operation or reset loader. Report if problem still exist. Internal error. Repeat operation or reset loader. Report if problem still exist. In order to perform operation first change file access permissions and than repeat operation. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Check input parameters. Use Volume Properties command to check if enough memory space exists. Repeat operation or reset loader. Report if problem still exist. Operation is not allowed. Internal error. Reset loader. Report if problem still exist. Repeat operation with correct input parameters. Report if problem still exist. Internal error. Repeat operation or reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. Requested volume not exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Internal error. Repeat operation or reset loader. Report if problem still exist. Internal error. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Internal error. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Change the access and repeat operation. If problem still exist possible file system corruption and you need to reset the loader. Report if problem is not solved. Check input parameters. Repeat operation or reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Correct the file name. Repeat operation or reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. First check the defined number of volumes in the flasharchive. If it is lower than maximum allowed volumes repeat the operation or reset loader. Report if problem still exist This message can be issued in case when is detected that loader is trying to unmount zero mounted devices. Internal limitation. Wait some time and then try again. Reset loader. If problem still exist report it. Check your authentication level. Some command need authentication. Verify that you are sending correct command. Check your authentication level. Verify that you are sending command from existing group. Check the command payload. If payload is fine, report this problem It is not allowed more than 5 commands to be registered. It is not allowed the command to be registerd more than once in execution queue You should be authenticate with appropriate permission level in order to execute this command. Internal error.Report this problem Internal error. Report this problem Internal error. Report this problem short="Timer interrupt configure failed.">Internal error. Report this problem Check input parameters. Repeat command. Internal error. Check input parameters. Repeat command. Try to reset the loader and repeat operation. If problem still exist, report it. Try to reset the loader and repeat operation. If problem still exist, report it. Possible error in flash driver configuration. Try to reset the loader and if problem still exist, report it. Possible wrong configuration or memory corruption. Try to reset the loader and if problem still exist, report it. Internal error or memory corruption. Try to reset the loader and if problem still exist, report it. Internal error. Try to reset the loader and if problem still exist, report it. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Check input parameters. Repeat command. Check input parameters. Restart loader and if problem doesn't solved, report it. Reset loader. Report if problem doesn't solved. Check input parameters. Reset loader and if problem doesn't solved reset loader. There's no more space available. Check input parameters and try to repeat same operation. Report if problem does't solved. Internal error. Try to repeat command. Report if problem still exist. Internal error. Try to repeat command. Report if problem still exist. Internal error. Try to repeat command and reset loader. Report if problem still exist. Internal error. Try to repeat command and reset loader. Report if problem still exist. Internal error. Try to repeat command and reset loader. Report if problem still exist. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Check input parameters. Retry command. If problem doesn't solved reset loader. Report this problem if this not help. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Reset loader. If problem doesn't solved report it. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Loader internal problem. Report this issue. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Write something to GD before attempting to read from it. Report this problem if you are shore that GD is not empty. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Internal error. Reset loader. Report if problem still exist. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Writing was attempted when compiled as read-only. Junking was attempted when compiled as read-only. Garbage collection was attempted when compiled as read-only. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Error returned when using os-free code when calling any other method then resume or shutdown when BDM is in the paused state. Returned when calling resume when BDM is not in the paused state (In the os-free case). Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Possible error in flash archive. Check the archive. Flash the correct archive. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Internal error. Reset loader. Report if problem still exist. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Possible error in flash driver. Try to reset the loader and if problem still exist, report it. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Internal error. Reset loader. Report if problem still exist. Repeat operation. If problem still exist reset the loader. Report if the problem is not solved. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Internal error. Reset loader. Report if problem still exist. Possible missing configuration for BDM. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Report the problem. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Possible missing configuration for BDM. Check is archive was flashed. If not, flash archive. If problem still exist reset loader and report the problem. Repeat operation. If problem still exist reset the loader. Report if the problem is not solved. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input arguments. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Perform Authenticate before executing current operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. This could either be because the challenge was signed with the wrong certificate, or the presented control keys were incorrect. Repeat the operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check the key. Repeat operation. Report if problem still exist. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check the file that you want to bind. Repeat operation. Report if problem still exist. IMEI in the OTP differs from the IMEI in the COPS data. It is not allowed to write in already locked OTP area Restart loader. Report if problem still exist. Be sure that authentication is performed with valid data.(Correct Certificate, Domain, Control Keys) Execute Bind Properties command first and than repeat operation. Report if problem still exist. Check if IMEI changeable is set in OTP. Report this issue if IMEI changeable is set and requested operation can not be executed. lock is disabled or already locked. Check the validation of the certificate or control keys. Control keys that you try to authenticate and control keys from Default Data missmach. Valid length is 8-16 bytes. Repeat operation with valid control keys. Report if problem still exist. Valid length is 8-16 bytes. Repeat operation with valid control keys. Report if problem still exist. Check the control keys. Repeat operation with valid control keys. Report if problem still exist. For the appropiate LockType timer is already running. Check that the SIM is active. If the SIM is active be sure that you are entering correct SIM Pin. Report if problem still exist Be sure that the SIM data conatains valid data for IMSI, GID1 and GID2 IMEI in the OTP differs from the IMEI in the COPS data. IMSI on interface doesn't match SIM IMSI Check the input parameters. Repeat operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check the input parameters. Repeat operation. Report if problem still exist. Check the input parameters. Repeat operation. Report if problem still exist. Verify the input parameters. Repeat operation. Report if problem still exist. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Repeat operation. Report if problem still exist. Repeat operation. Report if problem still exist. Repeat operation. Report if problem still exist. Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. If T_PD_NAND_CONFIG_FLAG_BLOCKING_MUTEX is not set, a call to NAND PD may return with this busy flag. Repeat operation. Report if problem still exist. Repeat operation. Report if problem still exist. Repeat operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Repeat operation with the correct input parameters. Report if problem still exist. Possible wrong or missing configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Check input parameters. Repeat operation with the correct input parameters. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. No data was written in the specified unit. Write data to the unit and than perform read operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Check input parameters. Requested unit is not supported. Repeat operation with the correct input parameters. Report if problem still exist. Reset loader. If problem doesn't solved report it. Reset loader. Reset loader. If problem does'n solved report it. Reset loader. If problem does'n solved report it. Check ZIP archive. Reset loader. If problem doesn't solved, report it. Check input parameters. Repeat operation with correct input. Possible damaged elf file. Retry operation and reset loader. If problem doesn't solved report it. Check input parameters. Retry operation. Some information in boot image doesn't agree. Check software that you flash. Internal error. Reset loader. If problem doesn't solved, report it. Invalid boot image. Check software that you flash. Internal limitation. Report this problem. The boot record with that ID is never written. The boot record with that ID was not written. For successfully writing in flash boot record must be a multiple of four bytes. Check manifest file from flash archive. Repeat operation with correct flash archive. Report if problem still exist. Check manifest file from flash archive. Repeat operation with correct flash archive. Report if problem still exist. Internal error. Reset the loader. Report if problem still exist. Internal error. Reset the loader. Report if problem still exist. Check the module number and try again. Use List Cases command to see available modules for testing. Use List Cases command to see available test cases. Use List Cases command to see available test cases. Use List Interface command to see available internal groups. Use List Interface command to see if is any available internal group. Use List Interface command to see if specified internal function exist. Use List Interface command to see if there's any available internal function. Precondition is already set. If you want to change it, recover precondition, and than set it again. You cannot recover condition that is not set before. There's no need of any further activities in order to resolve this problem. Loader will work fine. Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist Internal error.Possible hardware malfunction. Please report this problem immediately The value for CID must be in the range from 19 to 16384.0 value is also alowed CID value Internal error. Reset loader. Report if problem still exist It is not allowed to write in already locked OTP area If specified property cannot be found by COPS module. If user try to change IMEI in COPS while IMEI is set as non - changeable in OTP area. If some security operation cannot be accomplished due to various reasons. . Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. If you are trying to install flash patch ,please make sure that version of ROM patch is greater than already installed. Reinstallation of OTP patch is not allowed. ROM Patch in Flash is successfuly reinstalled. .Please make sure that version of Root key is the same with already installed Root Key is successfuly reinstalled. Check input parameters. Repeat operation with the correct input parameters. Report if problem still exist. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Possible wrong configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Check input parameters. Repeat operation with the correct input parameters. Report if problem still exist. Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist No data was written in the specified unit. Write data to the unit and than perform read operation. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist Check input parameters. Repeat operation with the correct input parameters. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Possible wrong or missing configuration in flash archive. Check the archive. Flash the correct archive. If problem still exist report the problem. Init request is twice called and state is changed. Should be sent Update request then can be used Init request again. Use the implemented change operation. Internal error. Reset loader. Report if problem still exist. It is possible that part of the operation has been carried out. Internal error. Report the problem. Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Check input parameters. Repeat operation. Report if problem still exist. Possible hardware malfunction, or error in HW configuration.Reset loader,report if problem still exist. Operation is completed. NOR memory is not present or some hardware malfunction occurred. It is possible to failed to initialize the communication device.Reset loader.Report if problem still exist .Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Implementation it is not supported anymore. Buffer with unaligned length is requested to be transfered or device driver is confiured to use unsupported frame size. Current transfer is not finished. Simultaneous data and flag transaction. Incorrect number of bits received. .Reset loader.Report if problem still exist. Reset loader.Report if problem still exist. Reset loader.Report if problem still exist. Wrong value passed as state for the communication relay and hence it can't be used. Try setting some of predifined communication relay states. Communication relay is set in error state or it is not configured properly. Check the relay state. If error occured restart the loader, otherwise try reconfiguring the relay. It is possible to failed to initialize the communication device.Reset loader.Report if problem still exist .Check input parameters. Retry operation. If problem still exist reset loader. Report if problem doesn't solved. Implementation it is not supported anymore. Buffer with unaligned length is requested to be transfered or device driver is confiured to use unsupported frame size. Current transfer is not finished. Incorrect number of bits received. .Reset loader.Report if problem still exist. Reset loader.Report if problem still exist. Reset loader.Report if problem still exist. . . . . . . . . . . . . . . . . . . . . . . . The verification of ChipID list failed. The function that was called did not have correct parameters passed. Some unexpected error occurs.Reset the loader.If problem does'n solved report it The verification of hash list in Loader Security Library failed. The verification of the header has failed. Successful verification of the header. Internal error. Reset loader. Report if problem still exist. Restart the loader. Restart the loader. Restart the loader. nternal error. Reset loader. Report if problem still exist. nternal error. Reset loader. Report if problem still exist. Try to use the appropriate authentication type (control key or CA certificate). Restart the laoder and use the correct control keys or CA certificate to authenticate. Possible error in hardware configuration, or hardware malfunction.Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Internal error. Reset loader. Report if problem still exist. Verify that authentication is performed with correct control keys, otherwise report this error. Verify that CA certifiacte which is used is valid and appropiate for the HW on which authentication is performed,otherwise report this error. An error ocured while parsing X.509 certificate. Check that certificate structure is valid. Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exis Verify that Bind properties is already performed. Report if problem still exist Verify that the data is correct and flash is not corupted. Report if problem still exist Internal error.Please reset the loader and try again.Please report if problem still exist. Internal error. Possible hardware malfunction. Please report this problem immediately. Internal error.Possible hardware malfunction. Please report this problem immediately. Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist> You are not allowed to write in already locked OTP area. The value for CID must be in the range from 19 to 16384.0 value is also alowed CID value. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist Internal error. Reset loader. Report if problem still exist Check the authentication level and try again. Report if problem still exist Internal error. Reset loader. Report if problem still exist. Check if IMEI changeable is set in OTP. Report this issue if IMEI changeable is set and requested operation can not be executed. Check the authentication level and try again. Report if problem still exist If boot block is corrupted or do not exist, processFile command should be used to flash the new boot record or recovery domain data to generate the boot record template. If domain data are corrupted or do not exist should be use the bind properties command or recover domain data to generate the new domain data. Select appropriated domain. Verify that challene data block is created properly. Cuurent opertaion can be executed only on Debug HW. Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. Reset loader. Report if problem still exist. Reset loader. Report if problem stil exist. Possible error in HW configuration. Try to reset the loader and if problem still exist, report it. Possible error in HW configuration. Try to reset the loader and if problem still exist, report it. Verify that the flash image is valid, otherwise report the problem. Reset loader. Report if problem still exist. The loader will start with the default settings. . The selected property is not supported by the loader. . .Property value does not exist. . . Internal error. Reset loader. If problem doesn't solved, report it. Specify the correct time. Check if property id exists. . This command is not supported. Internal error. Reset loader. . Check if input parameters are in the correct format. The command group is not supported. Check the command documentation. Reset loader. If problem doesn't solved, report it. . . Restart loader, if the problem still exists report it. Restart loader, if the problem still exists report it. . Restart loader, if the problem still exists report it. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffer is not big enough. . . . . Error encountered when loader tried to change MMU setting. Error encountered when loader tried to startup on invalid Hardware. . . . . . . . Loaded file does not contain a valid partition table. Please load a file containing partition table. . . . . . Non fatal error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Request for recovery condition for condition that is not changed.