|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
Over-the-air (OTA) Firmware update is a way to update a device after manufacture by using the Image Update technology and OMA DM version 1.2.
A Windows Mobile device has ROM regions segmented into different ROM packages that can be individually updated. Using the Image Update technology, your OEM creates update packages for various ROM versions. The packages contain your provisioning XML file, must be signed, and are stored in the OMA DM server or in a connected database.
For a description of the OTA Firmware Update process, see OTA Firmware Update Architecture.
To see an OTA Firmware Update example, see OTA Firmware Update Example.
If you are experiencing difficulty with an update, you should first ensure that you meet the Server Requirements. For more information, see the following documentation:
- How do I know whether or not the update was successful?
The device can use firmware update final notification to send image update final result back to the OMA DM server over generic alert (1226) element. For more information, see Firmware Update Final Notification.
- How do I get the firmware update to invoke on the device?
For OTA Firmware Update to occur, Firmware Update Managed Object (FUMO) requires that the Correlator be specified in the Exec command. For an example, see OMA DM Generic Alert.
- What should the Image Update files be named?
The naming convention for Image Update files is: mxipupdate_< package name>_< version>.provxml
Microsoft recommends that you use a three-digit version number in the name of your .provxml files in ROM, such as mxip_opr_100, mxip_opr_200, mxip_opr_300, so that there is an adequate number of ordinals to identify successive versions of the file.
All settings contained in Image Update files are re-applied when their associated packages are updated. These files should contain only settings that should be applied every time the package is updated.
For more information, see Provisioning Using a ROM Configuration XML File.
- The user rebooted the device and the update failed
<GUID>.exe is part of the update process. If the user reboots the device during the time <GUID>.exe is processing, then <GUID>.exe fails and will not run again when the device is rebooted.
- How can I determine why the update failed?
A Firmware Update Managed Object (FUMO) result code is used to report status after an in-ROM update.
For information about OMA FUMO final alert result codes and their meanings, see OTA Firmware Update Result Codes.
The data field in the 1226 generic alert specifies the OMA FUMO result code. For a list of valid codes and their meaning, see OTA Firmware Update Result Codes.