WM system ROM template customization tutorial

I. What is a template?

WM templates are basically the same as Microsoft's platform builder,

We use third-party products.

Ii. Benefits of templates

It is better, faster, and cleaner than the dump method to customize the Rom. There are many files but not miscellaneous, so it is convenient to add software.

4. Description of the three folders in the template

The template must have three folders: Rom, OEM, and SYS !!

1. Rom Folder:

The Rom folder contains the xip folder, which is required by the template!

The xip folder must contain the file boot. rgu.

Boot. rgu is the basis for creating *. HV registry files

The boot. rgu file can be extracted from xip,

You can also extract boot. HV from the brushed host and convert it to the rgu format.

Download the HV conversion TXT tool and convert it to txt.rar.

How to Use: Put boot. HV to convert it to TXT. bat, boot.txt will be automatically generated,

(Or run the command in command line mode, that is, cmd. Run the command to convert it to TXT. Bat boot. HV)

Rename boot.txt to boot. rgu and the encoding format must be Unicode.

We recommend that you use notepad2 for editing. Do not use the notebook that comes with the system !!

2. OEM Folder:

(OEM can be empty)

OEM is the abbreviation of the original device manufacturer.Program, Such as the driver.

That is, oemdrivers is the driver folder, which is usually put in the SYS folder,

OEM folders are usually named after OEMs.

This folder can be used to store your own OEM software package (see Figure 5 for how to create it)

3. sys Folder:

Required in sys

. Rom folder

. VM folder

The above two folders store the slot0 and slot1 values. Be sure to use the original version of your model!

Oemdrivers folder (this folder can be placed in OEM)

PS: only these three folders are required for transplantation! Others are not necessary. By the way, there are some manufacturers' OEM programs, that is, the folder named oemapps. Sometimes programs such as cameras are placed here.

3. Create a template. For models that already have a template, skip pai_^)

1. First, find the unpacking tool corresponding to the model.

PS: it is best to use the official Rom to create the template pai_^

2. Decompress rominto A dumpfolder and then use pkgtool.exe or dmp2pkg.exe to split it into OEM and sys

The two folders (pkgtool.exe or dmp2pkg.exe are different, which are described below)

(Q: Why is there no rom folder? A: The Rom folder must be created by yourself, and the xip folder in the ROM folder is also. Copy boot. rgu to the xip folder)

Note the following:

First: *. DSM is a file classification table file used to record files in a folder. *. DSM file also records the system version number.

Example: DSM is named 42dff48a-939a-457b-ada7-3098c46cdb61.dsm.

. The 42dff48a-939a-457b-ada7-3098c46cdb61 in front of DSM is the guid, which is the globally unique identifier.

*. Rgu is the Registry File (detailed below)

Second, for some rom, the DSM file is processed by all in one (that is, only one DSM file) for some reasons. As a result, it cannot be classified into three folders, therefore, you cannot create a template! Copy the DSM files of the same version number and compare them one by one.

Third: for some rom, if the RoM does not contain the *. rgu file (that is, the Registry file), it cannot be created as a template,

(Q: Isn't there two registries: Default. HV and user. HV? What else do I need the *. rgu file? A: *. rgu files are used to generate *. HV files. *. HV files cannot be converted to *. rgu, so they cannot be made into templates! Of course, manual creation is excluded. (Khan)

3. Okay. It has been classified into three folders. How can I dump files in the folder? This rom has been customized (modified) by others using the dump method, and there is no corresponding *. DSM file.

Differences between pkgtool.exeand dmp2pkg.exe:

If pkgtool.exe is used for classification, it cannot be classified if a DSM error occurs.

Dmp2pkg.exe can also be classified when a DSM error occurs, but it cannot be completely classified.

So the error *. the DSM file cannot be used *. the DSM file is modularized, so it is wrong *. the DSM file does not understand whether it is Rom or a tool.

In addition, mongodmp2pkg.execan generate a missing.txt text file from the files stored in the dumpfolder after classification. Files not written to DSM are not recorded in missing.txt.

Pkgtool.exe will prompt in the program.

Example:

T9

T9imeres. dll.0419.mui (file)

T9russianldb. dll (file)

T9 is a folder

These two files are missing from the T9 folder.

T9imeres. dll.0419.mui (file)

T9russianldb. dll (file)

The following (File) indicates a general file, not a module

If it is a module, it is a modular file.

Just move them to the corresponding folder.

For example, if the template is decompressed for the second time and the classification is correct, you must rewrite the *. DSM file,

For example, to rewrite 42dff48a-939a-457b-ada7-3098c46cdb61.dsm

Delete it, create a new text file, and rename it to 42dff48a-939a-457b-ada7-3098c46cdb61.dsm.

The disadvantage is that the version description in the *. DSM file is removed, but the version description is unnecessary.

PS: Does mybuildos.exe have the rewrite function?

V. Production of OEM software packages

I will not repeat the tutorials written by Mr. Chen.

Generation 4. OEM package (OEM package) Part1
Http://www.thinkagain.cn/archives/412.html

Put the prepared OEM software package in the OEM folder.

Vi. Modifications to sys

Highlights ~ Hey, it seems that there are not many -_-~!!

First, let's talk about how to modify the Sys part!

It is best not to add or delete values in the system's original *. rgu file! Yes, of course.

(PS: do not trust this sentence too much, but be careful not to make a big mistake, as long as the system value is not deleted .)

Otherwise, the system will have a variety of spiritual events,

For example, adding or deleting the rgu value in oemmisc will cause the first time the machine is started slowly.

(PS: This statement is verified only on sp)

Okay, as I already said above

DSM is a file classification file that cannot be deleted

Rgu is a registry file. It must start with regedit4 and be unicode encoded. (After buildos, dump merging can be deleted without any need, saving space .)

The rest are normal files.

Template customization is to modify this condition.

VII. Synthesize Rom

In this case, mybuildos.exe is made independently by Xiaoqiao, which is better than buildos.exe in the original version, at least in the Chinese version.

Pkgcommon. dll is required for running mybuildos.exe.

Put the mybuildos.exe and SYS folders in the same level directory

Run mybuildos.exe and click the green button in the upper left corner!

If an error occurs in the middle of the process, it is basically a duplicate of the file. Just delete one.

After execution, the temp folder is generated, which contains the dump folder.

(Mybuildos.exe is to restore the template to the dump Mode)

Here, g'reloc.exe is used to rearrange modules.

Copy g'reloc.exeto temp, rename the dumpfolder to sys, and run g'reloc.exe

After running g'reloc.exe, click doit! Button!

Close g'reloc.exe and rename the Sys folder back to dump

After that, you don't need to talk about the dump synthesis.

Use dump in the temp folder to synthesize

Other problems solved:

1. When mybuildos.exeis used, fewer files are generated. The Tools Folder must exist in the directory of mybuildos.exe at the same level.

There are some tools in it (I don't know why)

2. After the migration, the files in the oemdrivers folder are duplicated with those in SYS. The oemdrivers folder should be preferentially deleted from sys. Although some duplicate files seem to be common. Such as Bluetooth.

3 ,.................