[Windows Mobile Software Development] volDeus:
Stock shell files

I will upload as many stock shell files here as I can .. If anyone has working stock files for a build that I haven't included yet, please let me know and I will add them here.

To find your build number, navigate to

Settings>System>Device Information>Software Information>OS Version

... or

Settings>System>About>Version

...Your build number is the 5 digit number after "5.2." or "Build" ...

For example, the build number in the following screenshot is 23554.

Files surrounded in parentheses "(...)" have been confirmed as working by users.

20757

21054 21055 21056 21647

21869 21874 21876 21882 21884 21887 21888 (21889) 21890 21891 21895 (21898) (21899) (21901)

23014 23088 23113 23506 23511 23517 23518 23529 23533 23541 23542 23544 23547 23549 23551 (23554) (23557) (23559) (23562) (23563) (23566) (23568) (23569) 23639 23640

24001

25006 25009

28002 28004 28005 28011 28014 28205 28232

If stock files for your build are not present here

There are multiple ways to obtain stock files for your build .. Please do not ask me to find them for you until you have tried to obtain them yourself.

(Most of these methods are fairly easy to understand and there are vast amounts of information on them in the forum, so I will only give brief explanations.. I will post all the tools that I mention)

If you are using a newer 6.5.X ROM, you will need to make sure your shell32.exe file has been "timebomb patched" or your device will be disabled after the beta time-limit has expired. You can ask the chef of your ROM to provide the patched files or you can try patching them yourself with THIS TOOL created by joojoobee666. (You must have "module" versions of your shell files to use the tool. Using the reversemode tool can produce them from regular files.) My good friend antaed has posted detailed instructions -HERE-.

Extract the files from your device with ROMExtractor.

This is the easiest method but is not fool-proof.

This program runs on your device and extracts files from it's ROM, saving them to it's storage. This works well on some devices/ROMs but fails on others.

Extract the files from your custom rom with HTC ROM Image Editor.

This is also very easy, but does not work correctly if your ROM was built with bepe's platformrebuilder.

If you have flashed a ROM to your device, then you will have it's .nbh file. With many ROMs, the .nbh file will be in an archive with other files required for flashing. With self-extracting ROMs (any ROM that is a single .exe file), you will need to extract the .nbh file from the executable with a program like WinRAR. You can also start the ROM update program and once it has extracted itself (the folder that it was run in fills up with files), copy the .nbh file to another location and then cancel the update. Once you have your .nbh file, open it in HTC ROM Image Editor and navigate to OS>IMGFS>SYS>MSXIPKernel .. There you will find your stock shell files and you can extract/save them for copying to your device. If the result is a folder with files names "s000", "s001", etc; use the recmod tool, as mentioned in the next option.

Copy the modules from a kitchen or SYS for your build and compile them with RecMod.

This is not difficult but you may have a hard time finding a kitchen or SYS if your build is not popular.

If you can find a kitchen or SYS (component required for cooking ROMs) for your build, look for the folders "shell32.exe" and "aygshell.dll" and drag/drop them on to the RecMod tool... RecMod will add your shell files into those same folders and you can copy them from there to your device.

Dump your device's rom.

This is difficult and I consider it a last resort ... You are better off flashing a newer ROM and using option #2 than attempting this.

This is a device dependant process and you will have to research it on your own.

Ask your ROM's Chef for copies of the files.

Self-explanatory.

If you use one of these methods to obtain your files please check the file size. If your shell files are not approximately 750-850kb for shell32.exe and 350-450kb for aygshell.dll THEY ARE CORRUPT! and will cause your device to fail at boot.