[Tilt, TyTN II, MDA Vario III General] bengalih:
In learning how to cook from the many good resources on this site I have read in several places that the contents of the mxip* provxml files will get re-written on every device boot. This means that some changes to the regsitry must be cooked in, or they will be lost on a reboot.

One such thread/post that details this is here.

Now the official thread from MSDN on these files is here, and it says this:

An Image Update Package can contain two types of provisioning files:

Cold boot files that will be processed by Configuration Manager only when the device is cold booted. The provisioning file name must have one of the following formats:

mxipcold_PACKAGENAME_*.provxml

or

mxip_PACKAGENAME_*.provxml

where PACKAGENAME is the name of Image Update package.

These files should contain settings that you intend to be applied only during cold boot.

Update files that will be processed by Configuration Manager both when the device is cold booted and, if their associated packages have been updated, during Image Update. The provisioning file name must have the following format:

mxipupdate_PACKAGENAME_*.provxml

All settings contained in these files will be re-applied whenever their associated packages are updated, regardless of whether they have or have not changed. Therefore, these files should only contain settings that you intend to be reapplied every time their packages are updated.

Microsoft recommends that you use a three-digit 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.

Note Mobile Operators should avoid using provxml files to override (shadow) entries in Microsoft-owned provxml files​

Note Mxip_*_*.provxml is imported only at cold boot when the device is initially configured. In effect, mxip_*_*.provxml and mxipcold_*_*.provxml are handled the same.

​

Note Mxipupdate_*_*.provxml files are imported after cold boot and when the package containing them is updated.
​

Now the reason I am posting is based on my experience and the underlined section above. This seems to state that a "cold boot" is equal to "when the device is initially configured."

What this means is that these mxip files DO get processed on a cold boot, but that a cold boot does not mean a reset/full-power off, but rather a CLEAR STORAGE.

My own tests show this to be the case. For instance, I have taken reg entries from several mxip, mxipupdate, and mxipcold PROVXML files which shipped with the latest AT&T stock ROM (decompiled with KaiserKitchen).

When I delete these values on my device THEY DO NOT COME BACK AFTER A REBOOT.

Based on these two facts it would seem to me that any statement which claims that these provxml files re-write the registry at every reboot is incorrect.

I would love for this to be corroborated by others or in fact, I would love to be proven this incorrect.

Not only do I want to know what it right...but I have a particular instance where a registry key is getting re-written at every boot. This value being overwritten is not defined in any XML, so my assumption is a DLL or other system service is resetting it. At this point, the particular value is not important to the discussion but if indeed there were a way to define in a provxml file a registry key which would be overwritten at reboot, that would be helpful.

Please advise!

thx