[HD2 Windows Mobile 6.5 ROM Development] ansar.ath.gr:
An approach for the implementation of a WP7 ROM image on the HD2 device. by ansar

Dear forum members,

Due to the release of many WP7 ROMs for certain devices, many HD2 users and not only ask if, i or they or others, can "burn" the ROM's to HD2.

Yet the reply is that the possibilities are to "burn" their devices.

Even for the new coming devices the ROM upgrade will be difficult, as far as i see from the analysis of the leaked/issued ROMs.

Thus, and due to my current status of development, it is time to report some facts of some approaches to implement a WP7 ROM.

But, always there is a but, there is no time to an extensive one to cover all issues.

****************

A. The way of a direct boot.

The tools to extract the xip, the imgfs.bin and the rest are ready.

The tools to reconstruct the ruu_signed.nbh are also ready, even for HD2 cause for the rest

i.e. the HD 7 and the other known to me devices, was more strait forward.

The kitchen is also ready but platform builder is sensitive to the provided WP7 ROMs are probably built with ms platformrebuilder.

So for up to now reconstruction of the imgfs.bin, os.nb.payload, os.nb and ruu_signed.nbh takes place with additional effort.

No tools can yet be provided by me for a windows operating system like XP, Vista or 7, or other OS.

The direct flashing approach for other than HD2 devices needs development of new hard SPL's but

due to have a device, hopefully soon, more reports specifically about that will be released later.

The direct flashing approach for HD2 needs more development due to the following:

1. The previous MSFLASH50 header is no more valid (for all devices analyzed)

.. The new flashing layout is a hellout for us.

.. Also a new introduced SPL to route the device (by MS and OEM) about 25MB is included in official *.exe ROM files.

2. A small 1MB driving SPL (by OEM) is also included inside the ruu_signed.nbh (to make our lives harder).

3. The XIP is not the same as the previous known two modules assembly (cold and normal) but (up to now) of six modules.

.. These xip sections include common name modules but also are different in sizes, especially nk.exe

.. and seem to boot in an ordered way, alternate booting and/or separate booting maybe.

These are only some of the main difficulties that give the magnitude of the problems to overcome.

I was lucky enough not to brick it twice, but development will be continued.

For more info and uploaded material, if any, about this way see post #4.

****************

B. The way of an indirect boot.

It is not possible yet due to bricking results to use booting images of other devices.

For more info and uploaded material, if any, about this way see post #3.

****************

C. The way from bottom to top, from WM6.5 to Wp7, a safe but time consuming one.

I personal believe that we can drive the imgfs.bin of the WP7 ROMs on HD2 form the state we are now, i.e. from WM6.5.

For more info and uploaded material, if any, about this way see post #1.

****************

More reports about these with the provision of the developed ROMs’ for C above.

You can post to this thread but the time to reply is minimal.

Please do not ask me of how to, due to my commitments and for the shake of the safety of the development due to the known copyright issues.

Hoping that:

- the day will make all these a past is not so long

- this help other devs to make it real

and working on all ways,

Regards, ansar.