Develop Bugs

[Dev Topic] Fixing a 19900 build kitchen.

Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar

CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.

Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.

I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.

This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.

dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...

CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.

Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?

A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )

just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.

Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...

About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...

I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.

Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?

CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.

I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..

It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.

Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...

The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?

CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.

19588 Kitchen

Version 3 (5.2.19588 build 19588.1.1.4) Same build as Version 2, but fixed cannot create new message and problem opening email issue.
Download here: Megaupload or Rapidshare
What's included:
-3G dialer
- Diamond new connection wizard
- 10 button black com manager
- Voice speed dial
- Camera - v4.0.build 28276
-------You can add your own package to the OEM folder to build your own custom rom.
------- This is a fully working 19588 1.1.4 kitchen.
Sample screen shot of my working cooked rom.
See link for sample image shots of a working cooked rom.
http://www.techsmarttips.com/newforum/viewtopic.php?f=6&t=637

trashcan said:
I have ported the 19588 from Diamond for the Hermes if anyone want to clean it up. XIP and SYS is from the Diamond and OEMs is a mixed of the 19213 and from the Chinese 19581. I cooked a sample rom and it's in working shape. I believe you just need to clean up the OEM portion.
http://www.megaupload.com/?d=FUG7L8OU
I will try to clean it up when I have time.
Click to expand...
Click to collapse
please make a rom that has exactly the same content as the diamond rom.. i want the chinese function as well.
if that's possible..

trashcan said:
I have ported the 19588 from Diamond for the Hermes if anyone want to clean it up. XIP and SYS is from the Diamond and OEMs is a mixed of the 19213 and from the Chinese 19581. I cooked a sample rom and it's in working shape. I believe you just need to clean up the OEM portion.
http://www.megaupload.com/?d=FUG7L8OU
I will try to clean it up when I have time.
Click to expand...
Click to collapse
please mirror to rapidshare
thanks

trashcan said:
I have ported the 19588 from Diamond for the Hermes if anyone want to clean it up. XIP and SYS is from the Diamond and OEMs is a mixed of the 19213 and from the Chinese 19581. I cooked a sample rom and it's in working shape. I believe you just need to clean up the OEM portion.
http://www.megaupload.com/?d=FUG7L8OU
I will try to clean it up when I have time.
Click to expand...
Click to collapse
Thanks for sharing...

BuildOS closes before any packages show up. Is anyones else having this problem?

mikehippe said:
BuildOS closes before any packages show up. Is anyones else having this problem?
Click to expand...
Click to collapse
edit the BuildOS launching line inside BuildNB.bat and remove /auto

I removed the -auto switch and now the DOS window says "Creating 'dump' folder....." and just hangs there and the BuildOS window doesn't load any packages and is blank.

Excellent! I was just starting to sit down and do this as well. The provided OS.nb.payload - is it standard or BigStorage?

Something's wrong. It boots fine, but it is not working OK. Can not install cab's or xml's.

CRCinAU said:
Excellent! I was just starting to sit down and do this as well. The provided OS.nb.payload - is it standard or BigStorage?
Click to expand...
Click to collapse
Provided payload looks like the old one from bepe's kitchen.
Funny thing is that I tried with other payload files but is a no go. Have no idea why so far.

trashcan said:
I have ported the 19588 from Diamond for the Hermes if anyone want to clean it up. XIP and SYS is from the Diamond and OEMs is a mixed of the 19213 and from the Chinese 19581. I cooked a sample rom and it's in working shape. I believe you just need to clean up the OEM portion.
http://www.megaupload.com/?d=FUG7L8OU
I will try to clean it up when I have time.
Click to expand...
Click to collapse
boots fine bud did not sync with active sync
i can only copy files not contacts
BR

Seems to boot ok, but it seems to have issues with the phone and other operations... tried multiple things, but can't get the dialers to work etc...
Some things are still in chinese, but I've managed to fix that up... Still far from a working ROM however...

Has a bugs???
I had tried and found this issues:
- notify.dll not running on service
- can't import (BETA, make your own rom) dsm. that's why my device can't running autorun, sync and others provxml reg updated.

I have ported the WWE Kaiser one from HTC e-club: 5.2.19209 build 19212.1.0.3 and working quite sound.
See http://forum.xda-developers.com/showthread.php?t=394369
If there is someone interested in it I can upload it.

dan1967 said:
I have ported the WWE Kaiser one from HTC e-club: 5.2.19209 build 19212.1.0.3 and working quite sound.
See http://forum.xda-developers.com/showthread.php?t=394369
If there is someone interested in it I can upload it.
Click to expand...
Click to collapse
Please do!

chp said:
Please do!
Click to expand...
Click to collapse
I must say this one is a keeper; quite pleased with it.
Kitchen CE OS 5.2.19209 build 19212.1.0.3
SYS and ROM folders from Kaiser; payload from Pandora.
OEM folder is mine
There is no TOOLS folder included.
Link here:
http://rapidshare.com/files/118854971/Hermes_kichen_Ported_from_Kaiser_HTC_WWE_3.28.405.0.rar.html
Enjoy.

19588 Version 2 kitch is out. So far no issues. (see first post)

This Rom was ported to the Wizard also, http://forum.xda-developers.com/showthread.php?t=395173
I have been running this on my wizard for days and the Rom is fantastic.
I hope the same results can be optained with the Hermes....

Mirrors please.
trashcan said:
I have ported the 19588 from Diamond for the Hermes if anyone want to clean it up. XIP and SYS is from the Diamond and OEMs is a mixed of the 19213 and from the Chinese 19581. I cooked a sample rom and it's in working shape. I believe you just need to clean up the OEM portion.
http://www.megaupload.com/?d=FUG7L8OU This build is not stable and has issues.
Version 2 (5.2.19588 build 19588.1.1.4) stable working ROM kitchen. Tested and no issues found yet.
http://www.megaupload.com/?d=0MU8F6GQ
XIP and SYS from Diamond 19588 build. OEMs from the 19199 build but OEM drivers is updated with the Diamond files. Basic touch black dialer included. No CommManager/Camera app. You can add additional apps into the kitchen to customize your own rom.
Sample screen shot of my working cooked rom.
See link for sample image shots of a working cooked rom.
http://www.techsmarttips.com/newforum/viewtopic.php?f=6&t=637
Click to expand...
Click to collapse
please provide mirrors. i would love to try this. mattk_r is missing.

Kitchen has errors, cant find os.nb.payload. insert.exe crash. Can you fix this errors?

XipporterEx was born!

Hi all, cooperating with udk, and thanks to the author of the tricks into \mytools folder (I'd like to thank but I don't know who he is!), XipporterEx was born, how it works.....
easy:
you have to insert into:
old xip, new xip to port, and your payload.....
in one click you can port all xip or only MSXipkernel, done it, you can inster xip_out.bin into your os.nb.payload, and if you don't know where, the rightg offset where insert it into payload, you can find it only clicking on a button, and finally you have your new os.nb.payload updated, ported and ready to cook....
all infos and download here:
http://www.forumhtc.com/forum/showthread.php?t=3471
or here:
http://forum.xda-developers.com/showpost.php?p=2813417&postcount=9
bye!

ervius said:
Hi all, cooperating with udk, and thanks to the author of the tricks into \mytools folder (I'd like to thank but I don't know who he is!), XipporterEx was born, how it works.....
easy:
you have to insert into:
old xip, new xip to port, and your payload.....
in one click you can port all xip or only MSXipkernel, done it, you can inster xip_out.bin into your os.nb.payload, and if you don't know where, the rightg offset where insert it into payload, you can find it only clicking on a button, and finally you have your new os.nb.payload updated, ported and ready to cook....
all infos and download here:
http://www.forumhtc.com/forum/showthread.php?t=3471
bye!
Click to expand...
Click to collapse
Looks very cool, i will download it now..

danny_and_2 said:
Looks very cool, i will download it now..
Click to expand...
Click to collapse
yes, for me works well, ported all 2075x and 209xx xips and ever worked fine....
try it and report
bye!

Thanks, excellent news!!!
Public link: http://rapidshare.com/files/168872430/XipporterEx_new_find_xip_into_payload.rar

xxxelent tool it work very fine

Works good here too. Great work!

Awesome tool!!! Thanks a lot!

Hey Ervius. Using your tool (its ROCKING & AWESOME brother)
Couldnt port the 20759 XIP but maybe something is wrong with the bin that I have. Will try again on shipped XIP and check

mondilv said:
Thanks, excellent news!!!
Public link: <deleted>
Click to expand...
Click to collapse
You are probably best off to go to the thread in the op. This way you get the most recent version of the tools.
Best regards,
-boggsie

I have triyed it using as old xip Diamond XIP 1.97 and new XIP Blackstone 1.14 20757, to port only MXKERNEL, it works without anywarning, but when I dump the xip using XIPPort some module are missing like :
cachefilt.dll
mencfilt.dll
relfsd.dll
htcfsfilter.DLL
kd.dll
and some other for which I have read that they can be deleted
Is it normal ?

try again,,

TekTonik said:
I have triyed it using as old xip Diamond XIP 1.97 and new XIP Blackstone 1.14 20757, to port only MXKERNEL, it works without anywarning, but when I dump the xip using XIPPort some module are missing like :
cachefilt.dll
mencfilt.dll
relfsd.dll
htcfsfilter.DLL
kd.dll
and some other for which I have read that they can be deleted
Is it normal ?
Click to expand...
Click to collapse
yes, its normal!!!

I got xipporting.bat error

pawaj said:
I got xipporting.bat error
Click to expand...
Click to collapse
??? what mean xipport.bat, if there is an exe to port xip???

ervius said:
yes, its normal!!!
Click to expand...
Click to collapse
Hi Ervius what should we do with cleaned modules ?
put it manualy in the xip or un rom or never take care about these modules ?
Regards

ervius said:
??? what mean xipport.bat, if there is an exe to port xip???
Click to expand...
Click to collapse
Thankyou for your respond.I fix it already i forgot to install .net
by the way How can I use with Artemis?

TekTonik said:
Hi Ervius what should we do with cleaned modules ?
put it manualy in the xip or un rom or never take care about these modules ?
Regards
Click to expand...
Click to collapse
the xip have to works better without all the unused modules (on diamond!) but you can try on other devices, and report witch are useless and witch not!

last version: 1.2 revision 6, here:
http://forum.xda-developers.com/showpost.php?p=3007615&postcount=383
use your preferred os.nb.payload and your preferred xip (old and new!)
in this release you can port xips and now, remove uldr section, move xip and reduce unused space between xip and imgfd section, and your os.nb.payload will be reduced around 3.5 Mb, ready to be used to build new smaller (so more memory avaiable into rom on device ) roms

ervius said:
in this release you can port xips and now, remove uldr section, move xip and reduce unused space between xip and imgfd section, and your os.nb.payload will be reduced around 3.5 Mb, ready to be used to build new smaller (so more memory avaiable into rom on device) roms
Click to expand...
Click to collapse
The problem with this revision is the resulting payload being only 3.8MB. For the ULDR removal and IMGFS increase to work we need to use the -conservative switch on nbmerge and ImgfsToNb tools. This switch doesnt allow the higher size imgfs to be packed into the lower size template
Also the tool doesnt modify the LBA & no of sectors of IMGFS partition and needs to be done manually, but again the payload wont work since the nbmerge has to be with -conservative switch. Hope I am sounding clear without confusions

I Used HTC Rom Tool. to make the NBH file. and it worked fine. my os.nb.payload file is now 4.11 mb. xip os is 20764. Available memory before was 203.49, size after was 203.49. So I am not sure what i did wrong. aside from the smaller os.nb.payload file. everything seems to be the same.
It does boot and everything is fine there.

[Q] Help porting SYS to new rom.

Need help porting sys folder..
I've successfully ported XIP to 20757 and now i've been trying to port the sys build folder 20757 and up, from multiple roms, such as the xperia x1 roms, the blackstone roms, and other's from the site.
But all of my attempts has fail, so was hoping someone could tell me what im doing wrong.
First sys attempt i tried was;
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
found here http://forum.xda-developers.com/showthread.php?t=389772
Second i tired, to port it from a thread on the kaiser forum, http://forum.xda-developers.com/showthread.php?t=437264
and third i tried this following guide from the elf forms, http://forum.xda-developers.com/showthread.php?t=379598
so for short
1. made 1 folder for old sys, and 1 for new system with the build number
2. copy .vm .rom WinCENLS_WWE, shell/shellresand shell/shell32 folder, with my already ported XIP
3. swap out the res folder like 800 and 640 ones for the diamond, (where ever it is needed to port the rom)
4. then ran g'reloc
so yeah finally when i tried all this, form the guide, it doesnt work

What about the easiest way?
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779

Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!

ababrekar said:
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
Click to expand...
Click to collapse
I thought that to but every time i tried to port the Blacstone sys and Greloc
the rom doesnt boot, I have tried many times and allways the same result.
havent test for a wile, the xip port I get whit your exellent manual xip port but not the sys, so now I have a rom os 20757 Build 19665

have you tried replacing all except the Metadata folder ?
for your XIP which is the base used 1.93, 1.96, 1.97 ?
I have tried the xiportereex tool but some modules are missing, so I tryied to add it by myself, it boot but sometime touch screen doesn't responde at first tap, very strange, I have also a pb with default ringtone witch is not the one it should be by mxipupdate

hi
thank you for your reply everyone but several attempts trying you methods but none has worked ; ;
UPDATE; i give up trying to port sys build, thnx for you help everyone.

Same problem for me, if I try all these method in order to port the sys 20764 ( blackstone) to me ELF, the phone don't boot :-(

if the problem is running poutlook, please check if you have custsat.dll in your rom.
if removed, poutlook won't run.

This is the sam exact problem i'm running into. I can't just not port the SYS because the XIP i'm using opens the windows in a tiny little corner in the top left hand corner. Has anyone figured out how to actually port the SYS since none of the tutorials seem to work.

Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !

Bxsteez said:
a tiny little corner in the top left hand corner
Click to expand...
Click to collapse
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder

Vic5870 said:
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Click to expand...
Click to collapse
In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs

omaga said:
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Click to expand...
Click to collapse
I had this problem when i was porting the Touch HD ROM to the Xperia X1 and thats wvga to wvga. I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there

Bxsteez said:
I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Click to expand...
Click to collapse
Ye I thought that sys is the easy part I got so many sys port that the rom doesnt boot. Now i get 2 in a row 21109 and 21014 sudden and If I remember right I have allways done the same way

Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?

Bxsteez said:
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Click to expand...
Click to collapse
Maybe you should post in the X-Peria ROM dev. forum!?

I have but as we all know the xperia doesn't get as much attention as to the full blown htc devices. I figure that the porting method should be about the same with the exception of changing some things based on resolution. Am i wrong?

Have you deleted some folders from official HD SYS??
If yes, notice that the rom doesn't boot without SqlCeMobile and SqlCeMobile_Lang_0409 folders. I'm speaking from my experience with HD.
And I remember I've ported these official builds to Toshiba G900 without problems. Then, make attention to these things too.
And control if into your original SYS, you have some different folders in comparison to the new SYS.
Another thing, Ervius xipporterex rev-35, deletes some things from xip, but it works perfect in that way. The only thing you have to notice, is that it deletes WinCENLS_WWE from xip, then you have to add it into SYS folder.
@Bxsteez,
chek your 21109 SYS, and change mxip_system.vol(into Shell), with your original and see if mxipcold_wpc_2.provxml is into Base_DPI_192 folder, if not, copy your original one there. Change MobileCalculator.exe into baseapps folder too.

Just gave this a shot and nothing works again.... I can't even port the XIP and use the standard SYS and get it to boot. I wonder if i'm using a some corrupted build of 21109. Can someone point me in the direction of where to get OS CE 21109 and 21109 build?

Search on ppcgeeks the calkulins kitchen for diamond, then extract the xip from os.nb.payload and use that to port, worked for me with ervius xipporterex-35.
And make those changes into SYS folder, they are needed to boot properly.

6.5 21159 hangs on welcome screen.

Can anyone give me some insight on this problem. I am porting 21159 to the Treo 700wx, and it keeps stopping on the WM 6.5 startup screen. I can turn off/on the display, but it never progress onto screen calibration or anything else.
I have replaced the gwes.exe file in order to get the rom to boot, as well as wincenls_wwe, but it doesn't seem to make any difference. At the moment, I'm stumped. Any help would be greatly appreciated.
86 views so far, and no replies. That can't be good...

I think I might need a gwes.exe for 240x240 screen on a 211xx build. Does anyone have one?

Any progress?

untarded said:
Any progress?
Click to expand...
Click to collapse
Nope. No responses. I did find a 6.5 rom for the treo 750, but they removed all of the dsm files, so I can't port it. I have to try to manual piece it back together.

This is really a good build, but believe me that stabilniejszy is 21,109, this is fast

stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also

cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.

!Aman! said:
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.
Click to expand...
Click to collapse
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere

cruzzmz said:
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere
Click to expand...
Click to collapse
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.

!Aman! said:
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.
Click to expand...
Click to collapse
sad to say dude of of the rom now have protection on it including urs so i cant use package tool to make it to SYS folder ....

cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
Already tried this. Both are correct. It's not hangs on the boot screen. It's hanging on the welcome screen. Well it's not exactly hanging. I can still power it on and off. I still get the press the middle button to unlock thing. I can turn the radio on and off. It just never moves on from the welcome screen.

I pieced some of the 750 rom into my SYS. I noticed they had modified some of the .cpr files for 240x240, so I included those as well. Flashing now, we'll see what happens.
Update: Same problem. It stops at the welcome screen.

Tryed using my existing .rom folder, and shell32.dll and shellres.dll. Still no luck.

same problem since 21xxx builds with welcome-center
I'am a german rom-cooker for glofiish m800-device.
i work since over one week on windows mobile 6.5.
I'am not success today.
The Problem is:
- No Calibration (Welcome.lnk) is launched by initflashfiles.dat
but in the file the entry is included
the biggest problem, becouse the device is unusable
- The Startmenu is wrong, only a white screen open. (very small) no solution with gwes.exe from wm61 20924 sys.
- the grey taskbar on the today-screen
i have replaced gwes.exe from working windows mobile 6.1 sys 20924
i have changed shell.exe and shellres32.dll in shell-directory from sys
to change user.hv and default.hv from metadata
to delete user.hv and default.hv from metadata
to replace folder for shell
to replace folder for phone
to replace folder for redist.
to include wince.nls in sys-folder too
The wince.nls is in my xip (rom-directory) (my kitchen need the extracted version of xip.bin)
I don't know what the problem is.
I have ported XIP 21159 from Diamond, from TouchPro, from glofiish m700, from glofiish m500 and much more. I'am sure i use actually an VGA-XIP (from Diamond, 1.post in this Thread)
but i don't know which version this is (21139 or 21159 ???)
all the same problem.
i use my kitchen based on windows mobile 6.1 and included the g'reloc.exe from WM65 Kitchen (forwarder) and the wmreloc.exe.
since my kitchen is ready for wm65. all works great by compiling the new temp.dat (the flash-file for glofiish devices)
I read i must use the same sources for XIP and SYS !!!
But what are the same Sources ???
Can anyone send me an working 21159 XIP for VGA ???
When i try to port "Diamond Payload 21159" from XDA-Developers with Xipport and Xipporterex the xip is ok, but when i insert in my kitchen, the prog "buildos" stop their working, nothing happens in command-window.
So i'am very pleasent when you can send me an working source 21159 SYS for VGA and an working Source 21159 XIP for VGA...
i have big problem with windows mobile 6.5
acutally i try windows mobile 6.1 21114 there are the same problem.
the problem is, after os-logo no calibration screen come.
big problems to call "welcome.lnk"
only whenn i insert in wrong path to welcome.lnk the today-screen display ???
do you know this bug ???
here is the rgu of the welcome-center, i think it's not compatible with m800 ???
is this welcome-center new in the 21xxx-builds ???
over one week and no succed with wm65.
at the moment the same problems with wm61 21115
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:M SWelcomeCenter]
"0"="MSWelcomeCenter" ; class name
"1"="wcsan.exe" ; exe to launch
"2"=dword:1 ; perf hint (RAI_PERF_*)
"3"=dword:0 ; app type (?)
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome\CWelco meCenter]
"Disabled"=dword:0
[HKEY_CLASSES_ROOT\.wcml]
@="wcmlfile"
"Content Type"="text/html"
[HKEY_CLASSES_ROOT\wcmlfile\DefaultIcon]
@="browsres.dll,-6703"
[HKEY_CLASSES_ROOT\wcmlfile\Shell\Open\Command]
@="iexplore.exe file:%1"
[HKEY_CLASSES_ROOT\welcomecenterapp\DefaultIcon]
@="coreres.dll,-20797"
[HKEY_CLASSES_ROOT\welcomecenterapp\SelectIcon]
@="coreres.dll,-20798"
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Redirect"=":MSWELCOMECENTER"
[HKEY_LOCAL_MACHINE\System\WelcomeCenter]
"CmdLine"=""
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Group"=dword:1
hope you can help...
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Thanks
Everal

everal said:
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Click to expand...
Click to collapse
I had issues with it as well. I had to go back to using g'reloc.

hey guys any solution to this problem? I've been facing it on my Samsung i780.. damn this won't move past the Windows mobile logo.. yet it plays the welcome screen sound.. what a shame..

chef raven,
not trying to hijack your thread but can you please answer my PM.
i've been waiting for weeks now.
thanks