Related
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.
Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I have tested it and it worked ok. However you perform it on your own risk and I take no responsibility if you stuff it up. Do not remove everything at once. Remove 2-3 application and see if it works. If yyou unsure just leave it alone. When you are confident you can remove the rest of apps. Also if you want to remove Opera and TouchFlo you need to change a setup files so lets leave it for now.
You need a Kitchen and the ROM file.
Video Tutorial (rigt click and Save target as)
Extract kitchen files directly to C drive (not to desktop as shown on the screen shot)
IMAGE
Extract rom files into BaseROM folder in the kitchen.
IMAGE
Open !BEGIN and choose option 1
IMAGE
Just follow the prompts and press ENTER when asked. When you get to screen below just wait till asked to press ENTER again. This might take a while.
IMAGE
When you arrive to this screen
IMAGE
your rom preparations are complete.Hit the ENTER to close window.
Go to Kitchen folder and you notice that rom files and packages are extracted.
IMAGE
To remove unwanted applications from rom look into OEM and SYS folders. You need to delete all folders related to paticular application. (create separate folder and move all packages there instead deleting. Later on you can convert them to .cab files and install them if needed)
IMAGE
If you have some cab files and would like to add them into the rom you will need THIS application. Just start it, make sure that Remodule option is deselected, open cab file and program will create new folder containig packagage file. Make shure that PACKAGE_Diamond_ is in front of the filename. For example if you converted TomTom cab you should rename it to PACKAGE_Diamond_TomTom. Now copy the folder to OEM folder in the kitchen. Repeat process till you add everything you would like to have in the ROM.
When you delete/add everything you want start !Cook file
IMAGE
This will start OS building application. Just hit a green button and wait till it finishes. It will create os-new.nb file needed later. Close window on top (never close a DOS window) and rom building application will start.
IMAGE
Fill all the info as shown on the screenshot.
IMAGE
Use apropriate version rom (ie FR, ME etc...). As for the system select os-new.nb which is in the kitchen folder. Also you can select boot images and radios but for now we leave as it is. When ready hit Build ROM button.
Name your new rom (anything you want).
IMAGE
And hit SAVE.
A while later you should see screen below
IMAGE
Hit OK. Wait till everything finishes. Just press ENTER when asked. On the end you get message that rom is ready to flash. Hitting ENTER closes a window. All you need to do is flash it to your device.
PS Everyone is welcome to help. I need information how to update Framework and OS and where I can download it. Please post suggestions, registry tweaks and links to updated cab files for the apps removed from the rom. I will make a video tutorial after I have all info needed. I want to make easy for everyone who wants to have personalized rom.
Credits: Thank you to all who provided these great tools and these that helped in this thread.
EDIT: If you manage to create your own ROM please do not flood forum with new ROMs (unless it is something we never seen). There are experienced cooks that created really nice ROMs. Lets keep this forums clean.
There is a thread in this forum which has a simple to use kitchen. Using it is just easy as Steps 1-2-3.. But it doesn't work for some ROMs, atleast for me. By far, it is a great tool simplified in batch files.
Are you using the same tool or your own customised one?
Regards,
Carty..
lolek74 said:
Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I'm off to bed now. I'll post screenshots and info tomorrow. Please register your interest.
Click to expand...
Click to collapse
Could do my... i just finished my one yesterday a perfect clean rom not staffed wth litter....i used the surface kitchen and based on ce 0s 5.2 20273 wwe a bit customized the manila that's all....
Is it a clean ROM with most apps removed? Do you want to share please.
Good initiative!
I really want to know what is the true performance of the Diamond, running it with just the minimum required.
Even when disabling TF3D and other extras, I find it so slow compared to other WM phones having less MHz... I just don't understand why.
Uploading my ROM now. It is slow. I will post the link tomorrow.
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers
Thanks, this is great.
salada2k said:
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers
Click to expand...
Click to collapse
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Perfect
I was hoping/loocking fopr a thread like this! BUT
Could anybody explaine to me how to dump a rom?
The one I am using right now is pretty good and I want to modify
it and loose all the unwanted programs...
But what happens to all the .cab programs I have installed at the moment?
Do they "get dumped" as well so I can preserve them as OEM? Or do I only dump the "base ROM"?
And what about the Reg tweaks? Do they get dumbed aswell?
Thanks for the help...
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
Thanks for the reply, so what is the reason behind that... How can that 1MB be shaved off? Is it compression?
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.
Just a short notice, lolek:
I see you've extracted the kitchen to your profile folder.
You'd better extract it to the root of your drive, like C: or D:
batch files have a tendency to disliking spaces in file/folder names as well as names longer than 8+3.
surface_rom said:
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.
Click to expand...
Click to collapse
exactly also if you look at some of the benchmarks as well the lite roms are not much better or even some of the full roms are faster, so its all about what u really need in the rom, if your going to install everything back in your rom with cabs, its better to go with a full rom
Thanks for the input. This is what I was hoping for. The aim is to have simple tutorial for anybody to create their own ROMs. I'm off to work tonight but I'll update 1st post tomorrow.
I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.
lolek74 said:
I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.
Click to expand...
Click to collapse
very nice man, keep it up!
this is very good idea to put together a tutorial to cook the ROM! cant wait to cook my own ROM with this.
thanks a lot man!
Having a Slight problem with the surface kitchen.
During the process of extracting a rom at the stage of '2a.ExtractDumpIMGFS.cmd'
'Recmod.exe' crashes.'
anyone know why and how i can solve this?
Thanks in advance
I made a kitchen for the Herald that creates ROMs in both XPR and LZX compressions and I was wondering if you guys wanted it ported to your phones?
If you want it, I need a few things. This ROM is compatible with Bepe's Extended ROM kitchen. It won't come with OEM, ROM or XIP folders as you can get those yourselves.
The way the kitchen work is:
Run "RunMe.bat"
Choose compression algorithm. (XPR or LZX)
Follow the normal Bepe's kitchen process.
Wait as the kitchen creates the ROM (like Bepe's kitchen, but with whatever compression you chose.)
The kitchen will automatically open up the imgfs.bin in a hex editor and automatically adjust it for the wanted compression before it builds the ROM.
It automatically inserts the proper XIP drivers.
It will automatically set the Pagepool to 4MB but give you the option to change it to something else as it does.
It then automatically creates the NBH and then finally launches whatever flasher (CustomerRUU, FlashCenter, or whatever your devices use) to flash the ROM.
For those who don't know what LZX compression is:
It's a compression algorithm that, although slower (by 1-4% in real life use) gives a good amount of free storage space. In some case (like in the Herald) it makes the ROM so small that it has to be flashed through an SD card due to the Herald's flashing size requirements. On an average 50mb ROM, it takes off about 10mb. The actual cooking itself does take a LOT more CPU and RAM to do in your PC, though. Especially the RAM. (It's because the tools that actually do the compression weren't really optimized for the job.)
Anyhow, let me know if you want it.
this sounds good. would it work with wm6.5 roms?
FCW said:
this sounds good. would it work with wm6.5 roms?
Click to expand...
Click to collapse
It should. ^_^
ivanmmj said:
It should. ^_^
Click to expand...
Click to collapse
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d
another question
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
FCW said:
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d
Click to expand...
Click to collapse
That's not the LZX kitchen. That's an OLD and very broken kitchen. I should update my sig. ^_^
FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
I've already ported it to the Keiser using Bepe's newer kitchen so yes, it is possible. The Herald was left behind in the dust when it comes to new kitchens go. I've been porting the newer kitchen to the Herald but I haven't finished it.
FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.
So, what do you need?
HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5
ivanmmj said:
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.
Click to expand...
Click to collapse
still very interesting. im happy to test if you need a guinni pig lol
Sorry, I've just been pretty busy. I'm gonna take that kitchen you linked and modify it later today, probably. ^_^
joshkoss said:
HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5
Click to expand...
Click to collapse
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.
ivanmmj said:
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.
Click to expand...
Click to collapse
it is based off the same thing... just putting it up for anyone so you can modify
Ok, I'm done modifying the kitchen.
I need someone to test the ROM to see if it boots before I release the kitchen.
The ROM was decreased from 59,145KB to 48,983KB. That's a little over 10MB saved.
I'll post the link to the upload once it finishes uploading.
I'll definitely test it once you get it uploaded
I'm having problems with the connection in my current location so I haven't been able to upload it. I'm sorry. I'll keep trying until it gets there.
Here it is!
ivanmmj said:
Here it is!
Click to expand...
Click to collapse
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min
FCW said:
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min
Click to expand...
Click to collapse
Sounds great!
Same here! Will let you know when it's done flashing
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..
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