[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online) - Touch Diamond, MDA Compact IV ROM Development

[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online)
I've seen a few requests for kitchen's & rom's based on 21042 XIP/SYS so I decided to knock one up using the 2.03MRII 2.03.401.3 base and XIP/SYS from 21042 build.
This kitchen & rom is currently completely stock. Nothing removed from the OEM & SYS folders, no tweaks no addon programs just standard diamond build with newer core.
The only extra included which isn't in the original stock rom is remote desktop mobile (came with the sys not an extra) which of course you can remove from the kitchen if you wish. As it's the new sys it obviously contains the newer builds of MS apps including Windows live. Also this does not have the newer version of IE, just standard version.
Keyboard currently supports English, French, German, Greek, Italian & Spanish t9 however this should be updatable with the 14 language patch available elsewhere.
The kitchen is bepe platformrebuilder in almost stock form. No extra tools except for it runs htc rom tool to build the nbh file at the end.
XIP is not changed in anyway except updated msxipkernel & msxipkernelltk from 21042. No pagepool patching, cert patching or time/date/name changes. os.nb.payload size is reduced in the kitchen however this has no bearing on the final rom.
As this uses bepe's platformrebuilder, if you wish to change the date, build, pagepool, cert patching in the kitchen directly, these need to be done on nk.exe in the oemxipkernel. Any changes made to os.nb.payload (except uldr) will not be carried forward to the final rom as the nk.exe will overwrite changes to the payload. The payload itself is not ported so if you extract this and replace the msxipkernel folders then you will be back to a 20764 xip. There is no need to port the payload as replacing the msxipkernel & ltk folder in the xip folder properly ports the xip anyway if you are using bepe's kitchen (surface kitchen does not work properly in this way)
Also any rom's built with this tool are automatically locked as the kitchen deletes rgu's & dsm's from the cooked rom for space saving and performance. The files are extractable but then all you get is a dump of the files, without being able to seperate to packages.
Hope this helps some of you out there.
Also on the link there will be a stock diamond rom built from this kitchen - entirely stock but with latest xip/sys - even .netcf is still v2.0 that's how stock it is. It does however have more storage memory as it is cooked - original has 82Mb total and 57 available - this has 102Mb in total and 75+Mb free. Using the kitchen you could make a rom with alot more free space however.
I would recommend atleast upgrading .netcf to 3.5 in this rom if you are lightly cooking. Package for this is available on the forum
If you release a rom using this kitchen, please do not forget to credit the source.
Shaks.P Roms are free and always will be. If you like my Roms optionally send me a drink here:
​

Download Links:
http://diamond.geg0r.de/index.php?dir=Shaks%2FStock%2F
Please donate to bl0w for providing this mirror.
Important: Hard spl is required to use either the rom on this link or any rom created with this kitchen.

Basic Tutorial
As the rom is already ported & extracted, all you need to do is make your modifications then build the rom.
Step 1. Modify the sys & oem folders with the packages that you need. Make a backup of any folders you delete in case they cause issues with anything else.
Step 2. Once you are happy with the modifications, run build_rom.bat. This will create the os_new.nb file in the root of the kitchen folder. Once this is done, it will load the htc rom tool that builds & signs the final nbh file.
Step 3. Once the htc rom tool loads, select Build!, Change the version to anyversion you would like (this version only shows up when flashing). Under system, click on ... and select the os_new.nb file that has just been created. Then click on Build! ROM and this will ask where to save the nbh file and the name. Save as diamimg.nbh if you want to flash thru internal storage or any other name you like if using customruu.
Step 4. Ensure your device has hardspl, then flash the rom you just built either using custom ruu or using the internal storage method. If it doesn't work, you can allways flash another rom after getting the device in bootloader mode.

Can't wait
Thanks!

Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!

alxalx said:
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
Click to expand...
Click to collapse
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.

Thanks shaks!
Not only do you provide the best ROM around, but now also a kitchen, you rock!

sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?

shaks1979 said:
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Click to expand...
Click to collapse
Thanks man! I appreciate it!

Dynomite232 said:
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
Click to expand...
Click to collapse
This is just something I felt like doing for today. The kitchen won't get updated much (probably not at all as it's not modified). The roms will continue but will be going for the long release cycles again just like 3.20. I envisage I will probably have one more release and if that doesn't have issues then no more flashing till something big happens again (maybe stable tachi rom comes)
This kitchen is so stock that it can't replace my rom without alot of work - no tweaks, extra packages or anything for that matter except what comes in the stock as that's what some people wanted and I thought it won't take long so I did it.
P.S sorry for the delay with the upload. Having some issues

damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u

Dynomite232 said:
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Click to expand...
Click to collapse
Well 3.20 was a damn good, stable, time tested rom. I know a few people who won't change from it at all. Tested the latest but went back to it because they preferred it. 4.x series are a little bit more experimental but still go for the same stability. Next release should take of that small percentage who have corrupt memory/hard reset issues hopefully but I don't expect a big changelog as 4.10 is otherwise fine.

Should the bluetooth work well with this rom?
Thanks!

alxalx said:
Should the bluetooth work well with this rom?
Thanks!
Click to expand...
Click to collapse
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!

shaks1979 said:
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
Click to expand...
Click to collapse
Thanks man, downloading now!

hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on

Dynomite232 said:
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Click to expand...
Click to collapse
That's right - delete what you don't want, modify rgu's for packages, add your own packages e.g. using ervius package creator to turn a cab into a package or use a package already provided. You'll get lets of cooking help from here (talks about surface kitchen but basic concept the same):
http://forum.xda-developers.com/showthread.php?t=413782
Add your own packages into the OEM folder.

Downloading... In the meantime thank you!

got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it

Dynomite232 said:
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Click to expand...
Click to collapse
Add this package to your oem folder for 14 languages & edit the line in the rgu to specify languages you want

Related

vivi Kitchen for ASUS P525 : A simple Kitchen ever , modified from Scoter Kitchen.

vivi ROM Kitchen for ASUS P525
Mainly modified from Scoter Kitchen​
Introduction
I've made this ASUS P525 ROM Kitchen for ASUS P525 because I think someone can make it,but no one makes it till now. So I made it myself and share.
Though it is not the best and complex Kitchen with many features but I'm sure it is the good first step for us.
The main aim of this ROM Kitchen is easy using, so this ROM Kitchen is only one click and follow the screen.
You will have a new ROM for ASUS P525 at ease.
Aims
1.For easy modifying private ROM.
2.For helping new user to easy start cooking ROM.
3.For sharing OEM Packages.
4.For someone makes it better.
Let's see
Before using it just let us understand in the same way as follows.
1.This ROM Kitchen is made for using with ASUS P525 only,but it can be used with any other device if modified a little.
2.This ROM Kitchen is modified mainly from Scoter Kitchen.
3.The commands modified from DoubleOFour ROM Kitchen , edhaas ROM Packer Kitchen and some parts from Excel @AsusMobile.ru
Credits should give to them , not me.
Tools use
1.Tools in Scoter Kitchen included bepe package tools and mamaich tools.
2.P525ROMTool from Ingvarr.
Ingredients
There are 3 parts.
1.Program Part : The Kitchen itself.
vivi.exe
2.ROM Part.
3.OEM Part.
Download
You have to download all 2 of these and Base ROM supplied in Packages.
1. The Kitchen in executable file vivi.exe
http://www.zshare.net/download/398685039d2949/
2. OEM Packages
http://www.zshare.net/download/397176124ce74d/
You can find other OEM Packages or create your OEM Packages by looking at this thread.
http://forum.xda-developers.com/showthread.php?t=303195
Base ROMs
1.OLD :
Alex UltraLite 2
SYS and OEM from Alex
{This is Alex ROM (added Powerpoint and WLM files) in packages not ROMGalaxy.NB0.}
http://www.zshare.net/download/3987487fd85cf9/
2.NEW : Add 10 Oct 2007 :
SYS and OEM from Alex,plus settings pages from official ROM. !!!NEW!!!
Add files and settings from official back into Packages.
This packages of Base ROM will create official like unofficial WM6 ROM for your ASUS P525,since I add back official 3 settings pages from official ROM,include official system tray icons.
http://www.zshare.net/download/41190946d9bc4b/
How to cook
1. Place vivi.exe from download 1 in Root of C: and execute it.
You will see a new folder named vivi , this is your Kitchen.
2. Enter Kitchen , replace OEM and SYS folders with OEM and SYS folders from Base ROM provided from download 2.
3. In ROM folder , replace ROMGalaxy.NB0 (0 KB) with any ROMGalaxy.NB0 you want its size.
eg. if you want to build a new ROM with a huge size, place official CHS or Russian ROMGalaxy.NB0 here.
Or if you want small size ROM , place Alex UltraLite ROMGalaxy.NB0 here.
I think you guys already have ROMGalaxy.NB0 so no need to support this file.
4. Place OEM Packages you choose from download 3 in OEM folder.
5. Click Start.cmd.
6. Follow on screen.
That's all.
Thanks
@ Xda-developer.com
Thanks bepe for BuildOS.exe and Packages Tools.
Thanks mamaich for ROM Tools.
Thanks Ingvarr for ASUSP525Tool.
Thanks JKR for Scoter Kitchen.
Thanks DoubleOFour , edhaas for Kitchen I use as command guide.
Thanks sp3dev or Alex for Ultralite WWE ROMs as Base ROMs.
Thanks Owners of OEM Packages I collected(forget where I downloaded them).
And thanks my friends : Vibranze , AndrewSH , Jackleaung , guitarz for sharing knowledges.
@AsusMobile.ru
Thanks Excel for some parts of command line.
Thanks RN21, LiquidStrom , Zoff for sharing knowledges.
Thanks Alex for Ultralite WWE ROMs as Base ROMs.
Tips
1.Before you Exit BuildOS,you can go to temp/dump and delete all rgu files and nearly all html files except these 9 files.
1.compose_mtgreq.htm
2.compose_note.htm
3.compose_sms.htm
4.compose_vcard_sms.htm
5.default_0409.htm
6.read_mtgreq.htm
7.read_note.htm
8.read_sms.htm
9.read_vcard_sms.htm
Or you can edit welcomehead.96.png or another files as you want.
Regards,
vivi
PS
1.I know there are many experts here.This is my attempt to help us, ASUS P525 users, to make our devices better as best as I can.
2.I don't want any credits for this Kitchen , only named it vivi Kitchen since it is my attempt and only want to give this community back the thing I can do.Credits should go to the names I stated in Thanks Part above.
3.I hope you will develop this Kitchen better and share.Or share your OEM Packages or knowledges.
4.All feedbacks are welcome.
Thanksss
New OEM Packages
ASUS P526 Phone Skin (Thanks Jackleung)
woowww...cooool
Vivi,
Congrats! Finally I can see ROM Kitchen for P525 and now everybody can cook their own ROM
Btw, what do you mean by putting base ROM into OEM and SYS folder? Did you mean Romgalaxy.nb0?
I've put romgalaxy.nb0 into ROM folders and BOS failed to execute.
Cheers,
vibranze
vibranze said:
Vivi,
Congrats! Finally I can see ROM Kitchen for P525 and now everybody can cook their own ROM
Btw, what do you mean by putting base ROM into OEM and SYS folder? Did you mean Romgalaxy.nb0?
I've put romgalaxy.nb0 into ROM folders and BOS failed to execute.
Cheers,
vibranze
Click to expand...
Click to collapse
No, Vibranze.
You have to download Base ROM I provided here.
http://www.zshare.net/download/3987487fd85cf9/
It is not NB0 but splitted in 3 Package folders.
ROM , SYS and OEM.
Place them in the corresponding place in Kitchen.
Images attached.
And you have to place your old ROMGalaxy.NB0 in ROM folder.
This is to use as template for new ROM only.
Vibranze,
Check your PM.
vivi
Hi Vivi,
Thanks for all your work. Is it possible for you to make a similar ROM kitchen for the HP iPAQ HX4700?
bub
Thanks for your work ... once again
Vivi, congrate. Glad to see someone finally take this job over.
Great work vivi.
Now maybe it's possible to bulid TouchFlo in P525? If anyone could help me with the OEM version of this, please help me.
Thanks
EDIT:
I would like to make my own OEM packages, but I don't know how. Anyone can help me with this too? I saw that I need the files from the program, and I saw some files like .DSM, .RGU. That is it do? How can I make this files, to my programs?
Thanks fot helping me
jackleung said:
Vivi, congrate. Glad to see someone finally take this job over.
Click to expand...
Click to collapse
Jack,
This is why I want your rgu.files.
The ROM with no rgu can't be dumped and Packed as Base ROM.
I try to use P526 Modules from your ROM,but I can't use it since no rgu files.
Could you please give me all files and tell me how to replace Phone Module as your ROM?
HyperMalac said:
G
I would like to make my own OEM packages, but I don't know how. Anyone can help me with this too? I saw that I need the files from the program, and I saw some files like .DSM, .RGU. That is it do? How can I make this files, to my programs?
Thanks fot helping me
Click to expand...
Click to collapse
From this thread.
http://forum.xda-developers.com/showthread.php?t=303195
I add Tips in first post.
Tips
1.Before you Exit BuildOS,you can go to temp/dump and delete all rgu files and nearly all html files except these 9 files.
1.compose_mtgreq.htm
2.compose_note.htm
3.compose_sms.htm
4.compose_vcard_sms.htm
5.default_0409.htm
6.read_mtgreq.htm
7.read_note.htm
8.read_sms.htm
9.read_vcard_sms.htm
Or you can edit welcomehead.96.png or another files as you want.
bub181 said:
Hi Vivi,
Thanks for all your work. Is it possible for you to make a similar ROM kitchen for the HP iPAQ HX4700?
bub
Click to expand...
Click to collapse
bub,
I will look at it when I have time, not too long since I am also using HX4700 and modifying kozhura ROM for my personal use.
vivi said:
bub,
I will look at it when I have time, not too long since I am also using HX4700 and modifying kozhura ROM for my personal use.
Click to expand...
Click to collapse
Thank you so much vivi, I saw you posting in kozhura's topics a few times so I thought you must have a HX4700 too. I've been trying to modify kozhura's ROM for a long time, but all I have managed to do so far is add some themes and a few programs which don't need any registry entries. It will be great to be able to add full packages.
bub,
I have a look.
It's not hard.
Just modify some command line from vivi Kitchen for P525.
And create Base ROM.
I will make it for you.Not too long.
But I wonder how many users want it?
Touchflo on P525
HyperMalac said:
Great work vivi.
Now maybe it's possible to bulid TouchFlo in P525? If anyone could help me with the OEM version of this, please help me.
Thanks
EDIT:
I would like to make my own OEM packages, but I don't know how. Anyone can help me with this too? I saw that I need the files from the program, and I saw some files like .DSM, .RGU. That is it do? How can I make this files, to my programs?
Thanks fot helping me
Click to expand...
Click to collapse
great work guys. yeah, i would love to see TouchFlo working on the P525 as well.
Anybody? Vivi?
vivi said:
bub,
I have a look.
It's not hard.
Just modify some command line from vivi Kitchen for P525.
And create Base ROM.
I will make it for you.Not too long.
But I wonder how many users want it?
Click to expand...
Click to collapse
Thanks vivi, I think there are at least 3-4 people that have posted in the HX4700 thread asking for a ROM kitchen, and I think many more people will start using it once it is made available. The HX4700 seems to have a set amount of reserved space for the base ROM and the user space always has 82.59 MB free regardless of how much you put in the base ROM, so it's a good idea to fill the space in the base ROM, which leaves more space available to install applications in the user space.
Will the ROM kitchen you make work with kozhura's latest WM5 build? I'm still using his WM5 build because it's more stable than his WM6 build and it's almost as fast as WM6.
Thanks for all you work, I really appreciate it.
bub.
bub181 said:
Will the ROM kitchen you make work with kozhura's latest WM5 build? I'm still using his WM5 build because it's more stable than his WM6 build and it's almost as fast as WM6.
Thanks for all you work, I really appreciate it.
bub.
Click to expand...
Click to collapse
Yes , I think so.

Artemis Diamondish 6.1 Build 20721.1.4.0 + Build 20273/19965 (ROM + Kitchen)

Hi,
I would like to share the kitchen that I use to build my personal ROM. It's SYS and XIP were ported from the stock Diamond 1.93.456.2 WWE ROM that Tom made available and the kitchen is Bepe's kitchen.
Here it is (Build 19965.1.2.3):
http://rapidshare.com/files/130210385/Artemis_Diamondish_6.1_Build_19965.1.2.3.zip
UPDATE1: I have made a few changes in the OEM folder, I have added Advanced Config, added a patched htc home for the weather and made some changes to the registry. The changed files are in the attached zip.
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/130466202/Artemis_Diamondish_6.1_Build_19965.1.2.3_NBH_ROM.zip
(Usual rules for cooked roms, i.e. USPL etc.. - http://forum.xda-developers.com/showthread.php?t=331845)
UPDATE2: I have uppdated the XIP and SYS to use build 20273.1.3.3 and use .NET CF 3.5 as suggested, thanks xvx45
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/133908594/Artemis_Diamondish_6.1_Build_20273.1.3.3_NBH_ROM.zip
Kitchen:
http://rapidshare.com/files/133917390/Artemis_Diamondish_6.1_Build_20273.1.3.3.zip
UPDATE3: I have uppdated the XIP and SYS to use build 20721.1.4.0
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/142121757/Artemis_Diamondish_6.1_Build_20721.1.4.0_NBH_ROM.zip
Kitchen:
http://rapidshare.com/files/142132785/Artemis_Diamondish_6.1_Build_20721.1.4.0.zip
Fix for the SMS inbox issue can be found in post #99 http://forum.xda-developers.com/showpost.php?p=2616507&postcount=99
Here are some screen shots (of build 19965, mainly the same as build 20273 and 20721 but version numbers changed):
Nice work bro, nice to see new "faces" on Artemis forum.
Cheers.
Thanks, been here a while, just learning as I go. I thought it was a bit quiet on the new ROM front.
Thank you very much for you sharing!
Maybe this was the push i needed to start also cooking.
Who knows...
Cheers
Thanks for share man!
Do you have some screenshots of this ROM?
INFO
Hi,
Just extracted, saw all the separate files, did i miss the full .nb rom image or is this post to cook yourself with the htc romtool?
I know there are a look of cooking-guides, but can anyone explain simple which files tot select from the extraction when running the htc rom tool you have to fill in :
G3 IPL
G4 IPL
SPL
Splash
Radio Ext.Rom
OS
Can i add also .cab files for example somewhere to add to this rom?
Would like to cook first rom.
Thanks,
Innovator
Hi, just run the batch file "BuildNB.bat" and that will generate the .nb and .nbh files, they were removed to reduce the size of the archive.
You may also need to install the VC8 Runtime first, that can be found in the archive:
"tools\vcredist_x86.exe"
There is a tool from Ervius (I think that it is called "packages creator") that will convert cabs to OEMs suitable for cooking with.
Thank you mate, I'll try to make it compatible with Orange France SPV M650 AGPS
Maybe my starting element to come with Artemis community more often (actually my phone but Icook on my old Prophet at this time).
Good job
Hey guys,
This seems promising. I've just installed Tom's latest but have been troubled by bugs (it happens) since he's no longer responding to queries I decided I needed to learn to cook one myself (should be fairly straightforward).
Perhaps we should pool experience & resources and work together, I mean if you look at the activity in the Kaiser forum, you'd be forgiven for feeling a bit left out.
One person could design gfx the other sounds etc. Otherwise I might swap my Artemis for a Kaiser (yes I've been begged!!)
Forgive me if this seems like a pipe dream...
More screen shots....
Here are some more screen shots:
daniel.bigred said:
Hey guys,
This seems promising. I've just installed Tom's latest but have been troubled by bugs (it happens) since he's no longer responding to queries I decided I needed to learn to cook one myself (should be fairly straightforward).
Perhaps we should pool experience & resources and work together, I mean if you look at the activity in the Kaiser forum, you'd be forgiven for feeling a bit left out.
One person could design gfx the other sounds etc. Otherwise I might swap my Artemis for a Kaiser (yes I've been begged!!)
Forgive me if this seems like a pipe dream...
Click to expand...
Click to collapse
I agree, it would be nice to have an "open" ROM that the community contributes to, I hope that this would keep the Artemis platform alive for future releases of Windows Mobile.
P3350
Hi all... i am very new to cooking and still thinking of getting my feet wet... have a couple of questions...
1. I have a P3350 (Artemis with out GPS) and when i install all these roms they are sluggish when compared to P3300s. My friend has a P3300 and the same ROM is fater ... I tested it immediately after flashing by opening the windows folder and other apps... should i be doing any thing different to get my device up to speed?
2. The ROM on the rapid share (http://rapidshare.com/files/13046620....3_NBH_ROM.zip) is this a directly installable ROM?
3. What should i be doing with the 'changed files'.
Sorry if i am sounding noob...
veereshpm said:
1. I have a P3350 (Artemis with out GPS) and when i install all these roms they are sluggish when compared to P3300s. My friend has a P3300 and the same ROM is fater ... I tested it immediately after flashing by opening the windows folder and other apps... should i be doing any thing different to get my device up to speed?
Click to expand...
Click to collapse
I don't know of any, but I am looking into a similar issue that I see with my orbit, I think that I am going to look at the XIP region of the ROM to see if there is something device specific there, sorry for not being much help.
veereshpm said:
2. The ROM on the rapid share (http://rapidshare.com/files/13046620....3_NBH_ROM.zip) is this a directly installable ROM?
Click to expand...
Click to collapse
Yes, this contains everything but assumes that your device is already running the SPL and only contains the OS portion and not the radio. Look at the link in the first post for help on flashing cooked roms.
veereshpm said:
3. What should i be doing with the 'changed files'.
Click to expand...
Click to collapse
These files in the zip should replace the existing ones in the kitchen on rapidsahre.
veereshpm said:
Sorry if i am sounding noob...
Click to expand...
Click to collapse
No problem, we were all like that, I am still learning as I go.
please inform - this pre-built rom, what is it contains of?
set of programms, etc...
And what about memory leaks?
Thank you
Freshup Roms...
Good try for this new rom, but i find the home-skin not stylish enough (dated too soon).
Why not create a rom with Greatball's today screen, see http://forum.xda-developers.com/showthread.php?t=402021
This is the most stylish skin (with SPBMobile 2.1) i have ever seen (last one with analog clock).
Together with Greatball's Samurai Diamond Weather + Night
http://forum.xda-developers.com/showthread.php?t=402124
Would be the most fresh looking rom ever
In combination with latest msn, SPB-backup,PPCBackupcontacts,...
Who can do this & freshup our Artemis for a long time ?
Thanks,
Cheers!
Innovator
mpattman said:
Hi,
I would like to share the kitchen that I use to build my personal ROM. It's SYS and XIP were ported from the stock Diamond 1.93.456.2 WWE ROM that Tom made available and the kitchen is Bepe's kitchen.
Here it is:
http://rapidshare.com/files/130210385/Artemis_Diamondish_6.1_Build_19965.1.2.3.zip
I hope that it will be useful to some of you.
Matt.
UPDATE: I have made a few changes in the OEM folder, I have added Advanced Config, added a patched htc home for the weather and made some changes to the registry. The changed files are in the attached zip.
Pre-Built ROM (NBH) can be downloaded from here:
http://rapidshare.com/files/130466202/Artemis_Diamondish_6.1_Build_19965.1.2.3_NBH_ROM.zip
(Usual rules for cooked roms, i.e. USPL etc.. - http://forum.xda-developers.com/showthread.php?t=331845)
Here are some screen shots:
Click to expand...
Click to collapse
When an Italian version?
I have no plans to produce any other languages, but the source to the kitchen is all there for someone to translate to suit thier needs.
Ok, I've tested and make my first Artemis ROM (for test use for the moment).
I've been implemented Orange AGPS drivers but no luck no automatic connexion at the moment when GPS is activated so, I'll make more try. So I've removed some components (Adobe flash & reader, Diamond Keyboard and some little thing) that I don't want and this ROM is stable and fast...very fast coocked with NETCF3.5 Now I'll translate it to French if I've time to that more than my future release
Just one thing mpattman : why to release this kitchen with NETCF 2.0 and not directly 3.5 ?
And the last Word : Thank you mpattman !!!
I can not down your ROM and MYkitchen,please get it to FTP,thank you.
Thanks a ton...
Thanks MPattMan...
I am downloading the kitchen, and will try understanding stuff... will post if i have any doubts... do u have any guide on how to do stuff like adding the programs that i want ? ... i will be more than willing to help, test and learn.

New Old style kitchen based on Bepe's tools

Hi here i release an OLD style kitchen based on Bepes tools
I have taken bepe's kitchen and created some batch files to make it a one click extract and one click build and flash
I was so used to the old style kitchens and when they stoped working (failing at xip extract) i was looking for something that worked that i could use easly.
I found bepes kitchen, and it was nearly the same so i ported the batch files from diamond kitchen 0.4 to make this.
this kitchen uses the new style packages but has the look and feel of the diamond kitchen 0.4
I am still looking for the package creater that makes these NEW style packages but can't seem to find it now so if anyone has it please drop me a link so i can include it in the kitchen tools
download link ---->
http://rapidshare.com/files/217781904/Kitchen.rar
Instructions
1 place you RUU_Signed.nbh in the baserom folder
2 click on !Begin
3 Dont touch anything until extraction is finished (approx 5-10minutes)
4 Modify your packages
5 click on !Cook
6 wait until the htc rom tool loads
7 select diamond in device, os.new.nb as the source OS and save as kitchen/RUU_Signed.nbh
8 close htc rom tool and Custom RUU flash tool will load
9 flash and enjoy
......
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Is the Rom dump protected after cooking?
DefJamz said:
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Click to expand...
Click to collapse
this dumps the rom into the OEM, SYS and ROM Folders if you want the EXT folder download Bepe's tool below OEM2EXT
RideTheTube said:
Is the Rom dump protected after cooking?
Click to expand...
Click to collapse
not had time yet to try and test if i can rebuild a cooked rom, will have a go tonight and post my findings.
This is Bepe's Kitchen automated by batch files so he is the best person to talk to about protection
sorry to be a little blunt but i am a noob when it comes to cooking that why i found something that worked for me and made it a little easyer to use,
Protected Rom? Almost Rom when rebuilding, it will delete all dsm file, so you can't use package tool.
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
garymeg said:
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
Click to expand...
Click to collapse
I had the same problem and it was a XIP "mess-up". however I can't help you more than this.
try asking here: http://forum.xda-developers.com/showpost.php?p=3575850&postcount=131
i simply do NOT understand why build a tool that deletes stuffs that are important for cooking. isnt rom cooking supposed to be an open project for ALL? i mean some chef have the donate button in their sigs. but their rom's locked. it isnt fair to those (like myself) trying to learn how to cook a rom. i mean, i try to compare official roms and custom roms insides. what are the difference. it's by comparing that people learn to differenciate. and i would say BAHHH to missing rgu and dsm files!!
My thoughts exactly... Alas...
it is ironic, that NONE of the chefs who lock roms/doesn't supply kitchen/ask for donation wrote the code themselves. In short - everybody operates on stolen/leaked or any other way obtained code.
Ok, there are authors who created tools. And those guys have full right (and reason) to ask for donations fro that - TOOLS.
Otherwise - it's just funny. it's like stealing a car, and then asking police to protect it....
no panic.
at normaly old style kitchens never delete dsm'S.
and if you delete manualy dsm'S, you get all files in folder.
i think, with protect rom it means, no recookable roms.
it stops at point 1 or in the first step by using BEGIN! with a message like
"rom is smaller/bigger than/at starts" or so. excuise me, i've forgot the exactly words.
for checking of recookable rom i checked it with "htcRIE_0.5.0.12.exe".
it shows you all files with oem/sys - folders. but the oem can be empty. you find the oem-files than in sys-folder.
these points are my thinks that i see/learned by beginning flashing and cooking until now. other people can see/learn other thinks so dont dismiss me, if you are not my oppinien - but you can dismiss my english
Htc rom tool
Is it possible to use this for the Fuze?
EDIT: I found HTC tools with support for more phones on this thread a couple posts down

[Release] [Kitchen] - SuperJustKitchen v0.9 - Engage!

SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
​ SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
​
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!​
Well ... I have repaired my Hermes yesterday and now I'm trying ROMs here and none of them really suits me.
So your SJK came in the right time. I did few ROMs for myself last year, so I'm gonna try your SJK probably this evening.
And if it will work flawlessy, I'm considering donation.
Impressive..
Downloading and will hopefully be trying this out soon.
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
ivanmmj said:
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
Click to expand...
Click to collapse
I am cooking a 23529 native build now and will know here soon
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
pajousek said:
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
Click to expand...
Click to collapse
You have to actually add them in the EXT packages. They are not built in so that you can choose your own. I stripped the OEM and created packages of all required programs and made them into EXT packages.
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
I must be doing something wrong then cause mine won't go past the boot screen using native. I used everything default. Will try again.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
pajousek said:
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
Click to expand...
Click to collapse
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
Click to expand...
Click to collapse
I'm not sure what you mean. Can you please post a screenshot?
ivanmmj said:
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
I'm not sure what you mean. Can you please post a screenshot?
Click to expand...
Click to collapse
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
pajousek said:
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
Click to expand...
Click to collapse
Fixed for next build. ^_^
For now, just remove the preconfig.txt file.
Please report any future bugs to the bug tracker. (There are way too many threads to keep track of all of them.)
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
pajousek said:
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
Click to expand...
Click to collapse
I activated you manually. I'm not sure why it's not sending out the emails. I'll look at the code of the site.
I take it this isn't bigstorage? If not do you plan to have one bigstorage? I'd like to be able to do bigstorage in 6.1 and 6.5 and this looks like my best option..
thanks
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
pajousek said:
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
Click to expand...
Click to collapse
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
well, i'll try the not-native kernel (what disadvantages it has anyways?)
about bigstorage & clearstorage & dialer - i'll do some searching and testing and send you working links (since you don't have testing device).
ivanmmj said:
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
Click to expand...
Click to collapse
I have yet to get a ROM past the boot screen So I dunno..

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

Categories

Resources