I am having the same issue, just won't budge from the boot image.

I have used ROM kitchens before with no trouble. :(

I installed the CBOW patch and the .netcf2 patch. I was able to get my OEM folder to 33.7 MB before the white screen. I got the white screen, then took out 700 kB to get down to 33.7 MB, so there is the potential that you can get slightly more than 33.7 in, but so far that is the highest I have been able to get.

Remember that those numbers can be off by quite a bit. For instance, you can UPX all of your OEMs and have a OEM folder below 30MB and still get a WSONB. This is because the rom is compressed when it is compiled by CreateRom. So, the UPXing is irrelevant aside from faster loading

Good point. The only thing UPX'd in mine was TCPMP.

For those having trouble being stuck at the bootscreen, this can also happen when you use a directive inside an initflashfiles.txt that attempts to copy a file or shortcut to a nonexistent folder. For example, I was trying to copy a link into a folder that doesn't exist normally, and I had this problem until I found the directive that creates folders. Once I took out the offending entry initflashfiles.txt, my ROM worked fine.

smart dial not working
 

guys,
I've try to make my custom using kitchen+WM6+Netframework2 and most of colonel oem, plus I made my self WA2 oem,
after flash, it went ok, but smart dial not working..any idea why?
please help..


dgun

My extended rom appears to be empty. I think Kirvin's rom wipes it out. Is there any chance that the kitchen rom needs the initflashfiles.txt to be there?

Very nice ROM! I've been using it for a few days now and my phone is running very smooth. I have run into 1 issue w/ reinstalling Good Mobile Messaging. I'm getting Sprint PCS is not a supported carrier. Has anyone seen this? I've been searching through many post and haven't any luck finding info on this error.

Thanks!

Sorry, my post above has nothing to do with the Extended ROM. I'm saying that when you take an OEM off the web site here and cook it in the Unified ROM Kitchen, attempting to copy a file or shortcut into a nonexistent directory on your Pocket PC via an initflashfiles.txt entry will cause your device to hang at the boot screen.

The Extended ROM should have nothing to do with hanging at first boot after a hard reset. The Extended ROM is not touched until after you get past the boot screen and perform the welcome steps (screen calibration, date, etc.). In any case, if your Extended ROM is empty that won't have any bearing on your device at all. There is no initflashfiles.txt in the Extended ROM (at least not on Verizon; I can't speak to the other carriers but it seems unlikely).