[Windows Mobile] 88fingerslukee:
FROM: hilaireg

I'm not sure as to how much help I can be; that said ...

1) NEON Specs

I had a look at the NEON specs on the WIKI to get an idea of what is possible with the device.

From the specs, the unit is 128MB of ROM which may necessitate RECMOD'ing of module in order to achieve a bootable ROM. SLOT0 is generally the issue with WinMO 6.1 as SLOT0 should remain free of modules for the final ROM compilation. Here's some supporting information on Virtual Memory that will better explain what I am referencing:

Virtual Memory as it applies to the Windows CE 5.2 Kernel

http://xdaforums.com/showpost.php?p=4268137&postcount=2

2) ROM's

I haven't conducted a search to see if an update ROM has been released for the NEON (either through BELL or HTC); I'm going to describe two possible scenarios.

Scenario 1: No update ROM

The best approach here would be to determine how to dump the ROM from an existing device. Once a device is "dumped", the dumped content could serve as the starting point for building a custom ROM. Dumping a device ROM requires a few procedures ... I recommend a forum search with these keywords:

dump device rom

The threads that will appear will not be NEON specific, you'll have a bit of reading on your hands, but may provide some insights at what may be required.

Scenario 2: Update ROM available via BELL/HTC

If an update ROM has been made available for download, it should be possible to perform a dump via a kitchen such as Ervius Visual Kitchen (EVK). Here's a link to a tutorial I put together that walks aspiring chefs through the process of dumping an official updated HTC ROM using EVK for the Raphael - but is essentially the same for any device. Once a ROM is dumped using EVK, this would serve as your starting point for building a custom ROM.

[TUT] Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen 9.7

http://xdaforums.com/showthread.php?t=526610

3) Custom ROM

Once you have a starting point ROM, you can use it to create a net new kitchen. A net new kitchen could be a matter of copy/pasting the dumped kitchen from #2 (above). Things to keep in mind:

ROM: OEMXIPKernel is device specific and usually doesn't change until a NEON update ROM is release by BELL/HTC

ROM: MSXIPKernel is MS specific, this usually gets updated when a new O/S release is issued (ex: 6.1.21054, 6.1.21056, 6.5.23541, 6.5.23549, etc.)

OEM: this is device specific package which often are device drivers, carrier (operator) configuration, device functions, etc. and usually doesn't change until a NEON update ROM is release by BELL/HTC

SYS: this is MS specific and usually gets updated when a new O/S release is issued (ex: 6.1.21054, 6.1.21056, 6.5.23541, 6.5.23549, etc.) the MSXIPKernel & SYS should always match.

I would suggest starting with 6.1 and once you have a working build, you could look to move to 6.5. What's is important to keep in mind is:

you may need to RECMOD modules

closely review the .RGU (.REG), INITFLASHFILES.*, and .PROVXML files for any carrier (operator) specific lock downs

you will need to Cert Patch the ROM, possibly reduce the ULDR, possibly adjust the PagingPool - all selectable features in the newest version of EVK

Lastly, don't hesitate to ask questions in Chef Central ... some senior chefs may have some pointers that could help.

Chef Central: Windows Mobile/Windows Phone

http://xdaforums.com/forumdisplay.php?f=612

HTH