Mobile update

Updating a device

To update your devices, you'll submit an update to Microsoft. The mobile operator (MO) can help test the updates. When approved, the update goes to the production update server, where customer phones can download and receive the updates through a cellular or a Wi-Fi connection. With the users consent, the device updates automatically, with most of the update processes working in the background.

Before you begin

Prior to submitting updates, complete the following tasks:

  1. Sign up to submit firmware submission and update requests. For more information, see the “Sign up for retail package signing and update submissions” section in Ingestion Client.

  2. Review the update scenarios that apply to you in Update scenarios.

  3. Review the update requirements that apply to you in Update requirements.

  4. Obtain the successfully signed firmware submission ticket IDs for the firmware that devices will be updating from and the firmware that devices will be updating to. For info about how to perform this task, review Submit binaries to be retail signed.

Types of updates

  • Microsoft updates. These updates target Microsoft code in the image, including the Microsoft packages in the ESP (EFI system partition) and the Main OS partitions, and Microsoft packages for the system loaders.

  • OEM updates. These are also referred to as Board Support Package (BSP) updates. OEMs can develop packages for their components in reserved regions and the partitions that they provide packages for, including the Main OS and MMOS partitions. The user data and SD cards cannot be updated. All user data and settings must be preserved when these updates are applied.

These types of updates can only be submitted individually.

Refurbishing a device

Use the topics in this section to learn more about refurbishing a mobile device running Windows 10 Mobile.

Topic Description

Resetting a mobile device

Resetting the device addresses a number of key scenarios:

  • A user may want to reset a device to transfer it to another owner.
  • The device has been lost or stolen and the owner wants to remotely reset the device
  • The device belongs to an organization, and the organization wants to remotely reset the device. For example, when an employee leaves the organization.
  • The device has malfunctioned and the user wants to reset the device.
  • An OEM has completed factory testing and wants to reset the device (optionally preserving preloaded map data).