Develop Bugs

any idea how to activate the startup animation in the rom??

hi all
if anyone can safe the time for me to tell me how to activate the startup animation (reg and files required)
pandora kitchen has a package but its written there "can't run"
thanks in advanced

When I've used HTC animation in Pandora, it works for me

klabton said:
When I've used HTC animation in Pandora, it works for me
Click to expand...
Click to collapse
could i have the package which worked with you, the kitchen is very big

I'm running now Dopod Lite, but when i have made my rom with Pandora, when it was working, I have marked twice option to enable HTC Animation. When i will be at home, I will chceck this an make some screenshoots
Ok. So I've checked this twice: one in utilities, second in Starup Animation menu.

klabton said:
I'm running now Dopod Lite, but when i have made my rom with Pandora, when it was working, I have marked twice option to enable HTC Animation. When i will be at home, I will chceck this an make some screenshoots
Click to expand...
Click to collapse
thanks so much bro, i'm downloading the kitchen to check out

Here You go

klabton said:
Here You go
Click to expand...
Click to collapse
i meant the startup animation which animate a gif file with the booting
anyway, thanks for trying to help

It's a registry setting, if you check out Vp3G's 3.0 made with the AT&T WM6 he actually has the Animated HTC in a CAB file that you can download, it's located in the ADD-ONS file... all you have to do is run that cab and voila!

VP3G addons can be found HERE at the end of the post

Madcap180 said:
VP3G addons can be found HERE at the end of the post
Click to expand...
Click to collapse
i tried running the cab and it doesnt work.

Same here. This cab is not making this logo to work. All regs are ok. But it's not working. I even tried make this HTC.gif as a splash and i've put is via RUU, but still no results...

You can't just install my cabs on any old ROM and expect it to work. There are some ROM-specific animation components needed.
My cabs should work on any AT&T-branded WM6 or derivatives thereof, however I make no guarantees. They'll definitely work on vp3G v3.0 or v3.60.

This one has been bugging me too. There's some specific differences between the AT&T 3.57 and the T-Mo 3.60 that the cab's (and my packages) don't resolve.
I'm hoping to find the specific dependency, and I'll post once it's found. I'm sure it's something simple - just elusive What better way to spend a rainy Thursday?
Edit: I got it working, but only by copying the entire OEMDrivers folder from 5.5 (3.57). I'm narrowing down which files specifically now...
Got it down to 40 files from the decompiled dll list... ugh...

Are you trying to enable it on the dpod ROM? The Dopod and T-Mo/At&T has a different structure. Unil today I can only put it to run on T-Mo and AT&T only.

cyphol said:
Are you trying to enable it on the dpod ROM? The Dopod and T-Mo/At&T has a different structure. Unil today I can only put it to run on T-Mo and AT&T only.
Click to expand...
Click to collapse
Just a T-Mo 3.60. It works now, but I had to use a bunch of the dll's from the OEM drivers (the decompiled ones).

mattk_r said:
Just a T-Mo 3.60. It works now, but I had to use a bunch of the dll's from the OEM drivers (the decompiled ones).
Click to expand...
Click to collapse
Yes it's better for you to take all the .dlls in OEMDrivers and replace them in your own as necessary. It's for integrity also.

mattk_r said:
Just a T-Mo 3.60. It works now, but I had to use a bunch of the dll's from the OEM drivers (the decompiled ones).
Click to expand...
Click to collapse
Is it possible to get install it using a cab or does the changes have to be baked in?

chymmylt said:
Is it possible to get install it using a cab or does the changes have to be baked in?
Click to expand...
Click to collapse
My opinion is, " When there're many .dlls files affected then it's better to be cooked in."
Since Mattk_r is going to enable it on Pandora, then you can have it very soon or you can just take Schaps or my ROM. It's already been enabled since my first ROM.

cyphol said:
My opinion is, " When there're many .dlls files affected then it's better to be cooked in."
Since Mattr_k is going to enable it on Pandora, then you can have it very soon or you can just take Schaps or my ROM. It's already been enabled since my first ROM.
Click to expand...
Click to collapse
Hahaha - But I can't wait for 6.2 to get posted

chymmylt said:
Hahaha - But I can't wait for 6.2 to get posted
Click to expand...
Click to collapse
Then, try my ROM or Schaps or ..... I know that my cooked ROM is not as famous or as great as others but .......... Hmmmmm....

BETA: Extended Artemis Kitchen for WM6.1

New extended Kitchen for Artemis
ARTEMIS_DEV_v2.1_Build_19199.rar
Related:
Extended Kitchen for Trinity
Extended Kitchen for Hermes
Extended Kitchen for Herald
Thanks to misar, FreePK for helping with this new set of tools!
About the Kitchen
Artemis base: HTC P3300 WWE 3.13.405.1
OS base: VF Kaiser UK 3.08.161.0 (Build 19199)
OEM Apps removed, but you need to clean up the OEMDrivers package
I did not do any changes to the OS, because it should be a clean base Kitchen for all of you
Full XIP editing supported by the Kitchen
New tool to merge all dsm files to one big file and delete all rgu's
I think the OEM package to SYS problem should be solved... but did not try it yet
How to use it
Requires Microsoft Visual C++ 2008 Redistributable Package
OEM and SYS can be used as known
The content of ROM\XIP will be used to create a new XIP section for the OS
You don’t have to worry about relocating modules... add/remove whatever you like and the new tools will take care of relocating modules or freeing RAM
.VM and .ROM is updated automatically
Actually this Kitchen runs in auto mode, which means you only need to run BuildNB.bat to create the ROM. You can change that by editing the bat files; made it this way, because I don’t use the options in BuildOS.exe
I consider this a perfect port of the new build to this device
Replaced all XIP SYS packages (I did not just changed coredll.dll to get the new build number)
There were also boot.rgu changes my MS, those have been added too
SYS is completely untouched
Read this for download:
All donations are very welcome!
I need to buy a new device, because this time my Trinity is gone forever and I cannot use my girlfriends Artemis without being killed (by mistake I deleted all contacts last time I used it for testing... she was not very happy about that )
When you are getting money for the ROMs you cook using my kitchen, I would really appreciate a donation.
I'm not talking about 50% of you incomes, but one small donation would be fair I think.
To download the Kitchen click at "All donations are very welcome"
!!! This was only meant for ppl never donated for these tools and expecting donations for ROM's created using my Kitchen !!!
Thanks to all those who have donated already!​
Happy cooking!

bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bepe will give it a try and let you know

I'm on it too.
TNX!

bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bro

What does this Ext. ROM contains? Will it be suitable with BB5.0?

meschle said:
Thanks bepe will give it a try and let you know
Click to expand...
Click to collapse
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY

it works here too!

EazyVG said:
What does this Ext. ROM contains? Will it be suitable with BB5.0?
Click to expand...
Click to collapse
Sorry about that... did not see that the name might be confusing...
It means that this is a ROM Kitchen with an extension to edit/build XIP sections
To edit the XIP section was no easy task until now, so this means a little revolution for porting new build to our devices.
meschle said:
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY
Click to expand...
Click to collapse
NikMel said:
it works here too!
Click to expand...
Click to collapse
Thanks to both of you, great that it is working, happy cooking

Thanks bepe
Nice and great tools for Artemis.
thanks you so much.

dheewatara said:
Nice and great tools for Artemis.
thanks you so much.
Click to expand...
Click to collapse
P' Dhee ,Could you please make a tutorial ?.

Many thanks to Bepe for making the new toy
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?

mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse
First try if a ROM without OEM packages is working, next you need to add one OEM package after another... I'm sure there is something wrong with one of the packages.

You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse

Great. Will come up with some cooked stuff soon
Regards,
Carty..

Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..

NikMel said:
You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
Click to expand...
Click to collapse
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.

Most of the ROM do not include the rgu files.
You need rgu files to make your own rom.
Carty said:
Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..
Click to expand...
Click to collapse

the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
mypleasure said:
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.
Click to expand...
Click to collapse

NikMel said:
the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
Click to expand...
Click to collapse
Thx again NikMel, these hints should be able to get me going...

What is the map you guys talking about? Where do i find it?
Regards,
Carty..

----【wm6.5 21210 XIP+SYS From HTC Tachi CHS offical Rom】----

- Enjoy!
- Download link:http://www.rayfile.com/files/e148b5d4-297e-11de-b80f-0014221b798a/
- Password:www.xda-china.com

Hi Childe. Can you also post the OEMs? I believe thats native VGA so it will be easier for our amazing devs to work on the manilla and other OEM stuff
Better yet post the whole shipped ROM

@Ameet: This is a CHS VGA.

Hi, can you upload rom to some other website like rapidshare or easyshare,please? rayfile.com sucks, it needs to install a client to download...

adwinp said:
@Ameet: This is a CHS VGA.
Click to expand...
Click to collapse
True but cant we simply translate the mui files to WWE? or use Topaz's WWE mui files in the OEM packages?

Sorry, it's not a NBH file, just resources copied from present rom, you should clarify that.

Ameet said:
True but cant we simply translate the mui files to WWE? or use Topaz's WWE mui files in the OEM packages?
Click to expand...
Click to collapse
Yes, for the most part you can use your 0409 muis.

for those having problems with rayfile, here is another mirror, password is the same as in first post!
http://rapidshare.com/files/221610248/21210.rar
c3ro

c3ro said:
for those having problems with rayfile, here is another mirror, password is the same as in first post!
http://rapidshare.com/files/221610248/21210.rar
c3ro
Click to expand...
Click to collapse
Thank you for the link. Much better speed.

Can someone had a 4shared mirror for it please?
Cheers
Edit : Nevermind. Thanks anyway

Ameet said:
Hi Childe. Can you also post the OEMs? I believe thats native VGA so it will be easier for our amazing devs to work on the manilla and other OEM stuff
Better yet post the whole shipped ROM
Click to expand...
Click to collapse
Bump. Someone?

is the new xip a real wm6_5 Aku5 ?
I must know to use Xipportex correctly

Röchelhilpert said:
is the new xip a real wm6_5 Aku5 ?
I must know to use Xipportex correctly
Click to expand...
Click to collapse
But why would you choose that? nk.exe exists in OEMXIPKernel

LZX Compression

I made a kitchen for the Herald that creates ROMs in both XPR and LZX compressions and I was wondering if you guys wanted it ported to your phones?
If you want it, I need a few things. This ROM is compatible with Bepe's Extended ROM kitchen. It won't come with OEM, ROM or XIP folders as you can get those yourselves.
The way the kitchen work is:
Run "RunMe.bat"
Choose compression algorithm. (XPR or LZX)
Follow the normal Bepe's kitchen process.
Wait as the kitchen creates the ROM (like Bepe's kitchen, but with whatever compression you chose.)
The kitchen will automatically open up the imgfs.bin in a hex editor and automatically adjust it for the wanted compression before it builds the ROM.
It automatically inserts the proper XIP drivers.
It will automatically set the Pagepool to 4MB but give you the option to change it to something else as it does.
It then automatically creates the NBH and then finally launches whatever flasher (CustomerRUU, FlashCenter, or whatever your devices use) to flash the ROM.
For those who don't know what LZX compression is:
It's a compression algorithm that, although slower (by 1-4% in real life use) gives a good amount of free storage space. In some case (like in the Herald) it makes the ROM so small that it has to be flashed through an SD card due to the Herald's flashing size requirements. On an average 50mb ROM, it takes off about 10mb. The actual cooking itself does take a LOT more CPU and RAM to do in your PC, though. Especially the RAM. (It's because the tools that actually do the compression weren't really optimized for the job.)
Anyhow, let me know if you want it.

this sounds good. would it work with wm6.5 roms?

FCW said:
this sounds good. would it work with wm6.5 roms?
Click to expand...
Click to collapse
It should. ^_^

ivanmmj said:
It should. ^_^
Click to expand...
Click to collapse
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d

another question
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.

FCW said:
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d
Click to expand...
Click to collapse
That's not the LZX kitchen. That's an OLD and very broken kitchen. I should update my sig. ^_^
FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
I've already ported it to the Keiser using Bepe's newer kitchen so yes, it is possible. The Herald was left behind in the dust when it comes to new kitchens go. I've been porting the newer kitchen to the Herald but I haven't finished it.

FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.

So, what do you need?

HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5

ivanmmj said:
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.
Click to expand...
Click to collapse
still very interesting. im happy to test if you need a guinni pig lol

Sorry, I've just been pretty busy. I'm gonna take that kitchen you linked and modify it later today, probably. ^_^

joshkoss said:
HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5
Click to expand...
Click to collapse
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.

ivanmmj said:
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.
Click to expand...
Click to collapse
it is based off the same thing... just putting it up for anyone so you can modify

Ok, I'm done modifying the kitchen.
I need someone to test the ROM to see if it boots before I release the kitchen.
The ROM was decreased from 59,145KB to 48,983KB. That's a little over 10MB saved.
I'll post the link to the upload once it finishes uploading.

I'll definitely test it once you get it uploaded

I'm having problems with the connection in my current location so I haven't been able to upload it. I'm sorry. I'll keep trying until it gets there.

Here it is!

ivanmmj said:
Here it is!
Click to expand...
Click to collapse
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min

FCW said:
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min
Click to expand...
Click to collapse
Sounds great!

Same here! Will let you know when it's done flashing

Help For updating wm6 XIP to wm6.1

First thx for helping me
I was trying to port a XIP from Touch Cruise
Yet it cant even boot in the system [only suck at the screen with the red words at the bottom]
Any clear tutorial for me. Thank you

You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?

the.decoy said:
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
Click to expand...
Click to collapse
Yes i am using Ervius Visual Kitchen
What i do is using the xipporterex to port the xip.
I even tried to follow the bepe tutorial from darkforceteam with bepe kitchen.
Yet same error occured.
Would u mind giving me a clear step for making it workable?
thx

Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?

the.decoy said:
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
Click to expand...
Click to collapse
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]

Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?

OPzero said:
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Click to expand...
Click to collapse
Oh thats easy. The "Rom Version" (that shows on boot) just needs to be patched (it is reading it from the copied OEMXIP).
Just go back into the Porting window then click the button "Find Date/Version on \ROM\Xip\"
That will populate the Rom Date and Rom Version fields.
You can then edit those fields and click each of the "Change" buttons to patch the newer Date/Version into the OEMXIP
You can also set the PagePool value using the "Change PP to Mb" function (it is not possible to query the current PP value however it does tell you what it previously was when you change it). You could always set it to something sensible like 4 or 6 and see what it was before that.
EDIT: If you were actually talking about the CE OS build number that shows in "About Device" then that is much harder to change. It is embedded somewhere within the MSXIP (requires hex editing I am not familiar with - and that is effectively make a "fake" build anyway).

OPzero said:
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
Click to expand...
Click to collapse
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.

the.decoy said:
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
Click to expand...
Click to collapse
It's ok, would u mind pm or post some link which release those stuff?
Thank you very much!
I will still upload my rom and pm to u~
Check it when u hav time
really really thx

You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow

the.decoy said:
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
Click to expand...
Click to collapse
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx

OPzero said:
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
Click to expand...
Click to collapse
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414

the.decoy said:
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
Click to expand...
Click to collapse
1 more question
I downloaded a XIP SYS Pack from
http://forum.xda-developers.com/showthread.php?t=650783
However there are 5 Folders
How can i port them into the kitchen?
Thx for that

OK, this technically requires more time than I can spare to explain thoroughly ... but maybe if I just outline the steps you can do some google searching to work out exactly how to do it:
- First you need to clean up the SYS for you needs. For Trinity you need to have QVGA sys structure so that means only 96DPI and 320x240
- That means sorting the SYS package folders into an EVK SYS structure and removing the other DPI and resolution folder structures.
- Go get XIPDumpSoter (or whatever it is called now) by teh penguin so that you can use it to automatically sort the folders. Then delete any that are for other DPI or RES (eg: 192DPI or 640x480, etc). You _only_ want 96DPI and 320x240 (and of course any that are non-res specific)
- That should give you the folder structure to put into \SYS\NEWBUILD#\
- You will need to copy over the WINCENLS sys package from your existing SYS as that will not be in the new SYS (there are other replacement folders like SQM_DUMMY, and also some that we often just delete but you can learn that stuff later)
- We have already discussed what you need to do with the MSXIP
- Lastly, (and this is really very much the "art vs sicence" part), you will need to go through and "recmod" a certain number of "modules" within certain sys packages.
I simply don't have the time right now to get into recmod but if you google you will find plenty of helpful posts explaining it. I think there is even a basic recipe of what to recmod for 64M users done by JooJooBee ... that would get you going.
Put simply, at this stage you need to read read read read read lots of chef threads to pick up the finer details. Sorry I am too busy at work to be any more help than this.
Good luck.

Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!

OPzero said:
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
Click to expand...
Click to collapse
I'm actually going to bed before 3am tonight, so I will not be long here, but I just had a thought. When you cook the ROM, are you checking "Real WM 6.5 AKU" in the Kitchen? Don't do that. You cannot actually use a Native 6.5 Kernel on the Trinity as one does not exist. Also, as mentioned by the.Decoy before, you MUST have 'wince.nls' in your Kitchen somewhere or it will not boot. Thirdly, try cooking a version without ANY Extended packages. Only the original XIP and SYS and see if that boots. When you get that going smoothly, start adding EXT packages. Good Luck!
I'll check back in a couple days to see if you've made any progress. If you'd like to send your kitchen to me also, I'd be happy to look it over and see if I can find anything wrong in there.

Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Update:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx

OPzero said:
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
Click to expand...
Click to collapse
Ummm are you trying to use a freshly extracted OEM from an official ROM?
If so then yes, there is a massive amount of conversion that must be done to it before you an cook it into a rom. Even before you break it up in to components and edit all the reg and dat files ... you first need re-sign everything with an SDK cert because you won't have the official cert that HTC built them with.
Seriously. If you are just starting out then use an existing chef's OEM (use mine or anyone else who has posted a kitchen).
Even I have not yet ever had the time to complete build an OEM from scratch (not that I don't want to one day). I was always just adapting the OEM that Chanvi had provided us in his kitchen, primarily because he had already done all the work to make it mesh with WM6.5
OPzero said:
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Click to expand...
Click to collapse
I am bit confused by what you said there
As Supersport explained, we do not have a Native 6.5 kernel for Trinity.
So that option should not be checked.
OPzero said:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
Click to expand...
Click to collapse
Again, this is why I said to try "Load ROM" and see what happened
Those are just simply EXT packages which contain 1 single provxml. Each one sets the registry value for "ROM Version" (the info that comes up in "About Device" in Settings). There is one for every type of "Saved ROM" you can build from that kitchen.
I created them so that people could build each of the several types of rom from my kitchen but never need to edit the provxml files to change what the version info was.
If you are going to try cooking your own roms, the best advice I can give you is find a text editor you like and just start opening up ALL of the REG DAT RGU and PROVXML files you can find and see what they are doing.
You can even do it from within EVK. Select the type of file on the left panel called "Editors" (or just select "All") then click "Show Editor". You can open the files it finds by double clicking them in the panel on the right.
Anything custom that ever happens in the setup of a rom is controlled by these files.
If you want to see how something works (or what it does), just open up the files and read them

Sorry, wt i mean is that my rom become bootable after unchecking it
~~ That is so amazing ~~
Now i am Reading the horrible, endless.....etc tutorial, [I can finally have my own rom ]
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~

Sorry can't help you there.
I have never ventured beyond WWE lang for my kitchens.
OPzero said:
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Click to expand...
Click to collapse