Share via


Build a mobile image using a hybrid method

You can take advantage of the benefits offered by both the Windows provisioning framework and MCSF by using a hybrid method to build your customized mobile image. This means that:

To build a customized mobile image using a hybrid method

Here's the high-level steps you need to take to build a customized mobile image using the Windows ICD CLI:

  1. Choose how you define the packages and features contained in your image.

    • You can use BSP.config.xml file - If you select this method, you should already have this as part of your BSP kit or you can generate your own using the configuration tools from the SoC vendor.

    • You can use an OEMInput.xml file and OEMDevicePlatform.xml to define your platform. To do this, follow steps 1-4 in the high-level list of steps in Build a mobile image using ImgGen.cmd.

  2. Create your answer files to define the settings that you want to configure for your image.

    If you are adding multivariant settings in both answer files, verify whether the multivariant rules in both answer files are consistent. See the section Target, TargetState, Condition and priorities in Create a provisioning package with multivariant settings for a list of supported conditions but be sure to follow the schema for the answer file you are creating when you specify your Targets within the answer file.

    Also, make sure there are no duplicated settings in both answer files. You can use the MCSF to Windows Provisioning settings map to help you identify the settings that correspond to each framework.

  3. Run the Windows ICD CLI to build the image. For more information, see Build an image for Windows 10 Mobile.

  4. Sign the image so that it can be flashed to a device. For more information, see Sign a full flash update (FFU) image.

Building and flashing mobile images

 

 

Send comments about this topic to Microsoft