Develop Bugs

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..

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.

Samsung SGH-i780 (and any other WM device for that matter!): Learn how to cook ROMS

Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San

I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative

I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers

wooooooow thanks a lot buddy finally we have it also !!!

when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus

benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!

You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.

Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers

kitchen tools attached in the first post.
enjoy

dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program

benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers

thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!

The next post is up
cheers

dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great

i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?

benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....

trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?

well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool

good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck

Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P

My kitchen wm6.1 (based on crc's 20270 v13.5)

I thought about doing another rom release, but I figured it would be just as well to release the kitchen and let you all make your own!
This is based on crc's v13.5 big storage, in ervius visual kitchen 1.8.1.
It should have everything you need to create your own rom. The dump is a cross between crc's naked and normal, but there are a lot of extra packages. It also has things like button 5 fix built in, and if you build with alt tab, it will automatically assign itself to button 5, and voice dial will assign itself to button 5 (press and hold).
If you build with glossy black bars, preconfig.txt will be used from the glossy black bars ext folder. If you don't cook in ftouchflo, make sure to remove the entries for it from preconfig (either in oem, or in glossy black bars).
Thank utaker for the batch in the release folder for setting up splash screens.
crc, ervius, bepe, anryl, and others did all the hard work, so if you want to donate, give to one of them, I just packaged it all here.
Happy cooking!
http://www.4shared.com/file/141614505/f359da83/boog_kitchen.html
or
http://www.filedropper.com/boogkitchen

downloaded. thanks!

Been looking for a 6.1 kitchen I can try out. Thanks for sharing!!

You guys are welcome! It's got a good base being from crc's, and I have been loving the new ervius kitchen!

is it possible to cook with newer build? i wanted a clean stock-like 6.1.4 version

Tabbe said:
is it possible to cook with newer build? i wanted a clean stock-like 6.1.4 version
Click to expand...
Click to collapse
If you can find a rom to download, you can attempt to dump it using this kitchen.

Hey boog thanks a lot!!! do you think that there is a way to merge 6.1 and 6.5 in the same kitchen?
I mean if the kitchen is multibuild... multi lang, multidevice... why not to be multi core??? but i guess its not due to the change of the kernel but... maybe switching betwen the builds and OEMXIPKERNEL...
Thnaks again for the kitchen i will take a look at this.

+ Que PPC said:
Hey boog thanks a lot!!! do you think that there is a way to merge 6.1 and 6.5 in the same kitchen?
I mean if the kitchen is multibuild... multi lang, multidevice... why not to be multi core??? but i guess its not due to the change of the kernel but... maybe switching betwen the builds and OEMXIPKERNEL...
Thnaks again for the kitchen i will take a look at this.
Click to expand...
Click to collapse
I don't see why it couldn't be multi core! Or build 6.1 with a 6.5 xip. I just ran a test, but I don't have time to flash it (yet), I need my phone for work today.
6.1 built just fine with a 23017 xip from utaker's dv5 kitchen, as long as you left the real 6.5 aku unchecked (it will error, I believe utaker has the real 6.5 nk.exe in there). I renamed my original rom folder to ROM_61, then just dropped the ROM folder from utaker's kitchen in. That way it has all the files to make it happy in 6.1 or 6.5, now I just need to try loading the 6.5 pieces in.
It appears the rom will not boot using a 6.5 xip.

Looking at the differences in the rom folders, the os.nb.payload files are different size, and there are different files. I'm still not totally sure what they all do.
I may have to experiment to see if there is a happy combination.

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