Related
I've been thinking lately... I've been thinking of creating a new multidevice kitchen. The kitchen would support every current device, be based on the newest version of Bepe's kitchen or maybe the visual kitchen. It would add certain things like:
Automatically insert the cecompr.dll needed for both LZX and XPR compressions
Automatically hex edit the imgfs.bin during the cooking process to allow to LZX compression
It would come with an empty payload file for every device
It would support multiple languages and come with language packs
It would use the standard layout of bepe's kitchen/the visual kitchen so it would be easy to also keep build packages that would apply to every kitchen.
If I could get enough cooks involved from other devices, we could even have base STRIPED OEMs from every device that people can easily download.
We can make it automatically be able to dump any ROM and easily extract its XIP or SYS and import them into the kitchen or make the files into a package compatible with the kitchen that people could upload for everyone else to use. (Easier to spread new builds leaked by other people.)
I need more ideas as to what we could make this kitchen do.
I also need to know if any cooks would be willing to help out as it would be a MASSIVE project.
I would start it as soon as I'm done with two ROMs that I'm currently working for and a few kitchen that I'm modding for some people for LZX/XPR multicompression.
No comments, yet.
I'm working with ervius to add the LZX compression to the kitchen itself.
If no one helps, then it's going to be a little hard to do since I will have to download the default ROM for each and every device and then strip down the OEM. Then create bigROM packages to release as well. And then I can't test it since I don't have every device, so it's going to be a little bit of a slow process.
What I will end up doing will be more like just taking ervius kitchen, add a few things here and there and make all the packages and builds and whatnot available. Or at the least create a thread where people can post packages left and right. A repository of sorts. (A lot like the PPCgeeks's BuildOS but compatible with every device and using ervius awesome kitchen.)
Sounds like what Anchilus had one time! I think it was named as hypercore. But great idea though. I am not an expert cook or programmer, but I do cook ROM for myself sometime. My biggest thing is porting the ROM, doesnt matter what tutorial I read, I just dont get it LOL
Take a look in the raphael forums. Already done.
Will Help You
Ivan,
You know that I am willing to do anything I can to help you. Problem is that we have the same devices and you are my mentor so I am not sure how much help I would be, but whatever you need, you name it and I will do my best to help you out however I can.
GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I looked. I couldn't find a multidevice kitchen...
GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I think you mean this? http://forum.xda-developers.com/showthread.php?t=505800
Would be a great idea one kitchen for all devices, although I think the extra devices should be added in the form of plug-in, because nobody likes to dl a 20 GB kitchen . I would help but I'm not that great at dumping but especially not with the still changing structure of ervius visual bepe's kitchen. Is there a wiki or tutorial somewhere that properly explains where to put which folders? 12
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
To get the attention of the cooks I think you should start sending email to the chefs and maybe a couple of mods too. I don't think it should be much of a problem on the raph forum, we are blessed with kind and sharing chefs, 12
i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore
mbarvian said:
i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore
Click to expand...
Click to collapse
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry
ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
qsqa said:
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry
Click to expand...
Click to collapse
You mean like an kitchen appstore or a bat to move everything into the right folders? 12
That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.
ivanmmj said:
That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.
Click to expand...
Click to collapse
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
ivanmmj said:
Replace the FIRST one and FIRST ONE ONLY with "LZX". Save the file, close the hex editor. Let your kitchen do it's thing.
That's it.
http://www.4shared.com/file/101370353/b7650aff/Compression.html
Click to expand...
Click to collapse
do we need to do this step on the "mythical" cecompr.dll?
thanks
mbarvian said:
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
do we need to do this step on the "mythical" cecompr.dll?
thanks
Click to expand...
Click to collapse
Already answered there.
But,
Yes.
The cecompr.dll is what tells the XIP how to read the LZX compressed imgfs.bin. The hex editing is what tells the kitchen tools to write the imgfs.bin in LZX compression.
I worked with evirus and now his kitchen has an option for LZX compression. It will do everything automatically. ^_^
That's a great idea. Not sure it could work on my device (ks20) as bepe's kitchen crashes on my nk.exe so I have to build xip part the old way (using xipport). Anyways, if you need french 96dpi resources, I can give you mine.
And for this project, instead of a special software to download packages, why not using a svn repository ?
Although a SVN repository would be awesome, I wonder if there would be a legal problem just like there was with the XDA FTP server used to host ROMs and stuff for building ROMs?
Yes, that's possible... perhaps we should ask a moderator, what was the exact reason it was removed (because after all, everything is still present on this forum, it's just not grouped in 1 place, but I think legal issues remain).
I also know that somewhere on the web, there is a svn server for winmo builds (I had once a wm build that had .svn folders).
Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.
DestructDez1 said:
Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.
Click to expand...
Click to collapse
PM sent. Thank you!!
Hi,
I have been on the forums for sometime now and have seen how the HP9xx HP6xx roms have developed, particularly by Montecristo and Keyx and i have to say thank you and really good work guys.
I wanted to know if a program existed like nLite for windows but appicable for phone romshttp://www.nliteos.com/nlite.html so i can strip out and install programs i use the most personally
Having independent developers like Keyx and Monticresto developing roms for such large communities everyone wants something else someone else does not want and vice versa.
do you think it is possible?
If you want to add or remove something use kitchen provided by keyx, then build your own custom rom
I know of kitchen but its clearly not for the faint hearted, while nLite requires common sense and just a bit of know how.
Kitchen on the other hand just seems way too complicated for the average user.
Hopefully someone can do a video like Sesame Street to teach us how to cook !
the raw kitchen itself actually is pretty simple, sure it does not have much gui other than buildos, but you really just move folder in/out in SYS or OEM folders to customize the ROM.
anyhow I have written a small tool to generate option.xml for SYS package which allow one to select sys packages / language easier .
Due to 61x is not a htc device and platformrebuilder does not work for our device, we won't be able to use any kitchen out there so until someone have time to write a better kitchen we will have to use the current kitchen which use batch file to connect different tools and involve a lot of manual file edit/ folder management
Thanks Keyx
I have to start doing some home work into the heart of cooking...
Well, I guess I will contribute with something...
There are way too many kitchens out there (all scattered in the different device forums). Now, since this is "Chef Central", I figured that we needed the kitchens for the Chefs to cook. Without further ado, I present you with... the kitchens.
[highlight]PPCKitchen.org:[/highlight]
Easy to use for the beginner...
http://www.ppckitchen.org
[highlight]Ivanmmj SuperJust Kitchen (thanks +QuePPC and kokotas):[/highlight]
Multi-Device Kitchen
http://justkitchen.info/main/index.php
[highlight]osKitchen:[/highlight]
New kitchen based on bepe's work (thanks mwalt2)
http://forum.xda-developers.com/showthread.php?t=628948
[highlight]Ervius Visual Kitchen (EVK)thanks mwalt2)[/highlight]
http://forum.xda-developers.com/showthread.php?t=469420
[highlight]Wallaby (Peter Poelman):[/highlight]
http://forum.xda-developers.com/showthread.php?t=219037
[highlight]Blue Angel:[/highlight]
Latest: 28230 by sun_dream
http://forum.xda-developers.com/showthread.php?t=428030
Swampy395 Porting Kitchen
http://forum.xda-developers.com/showthread.php?t=587446&highlight=porting
[highlight]Himalaya:[/highlight]
Latest: 28230 by sun_dream
http://forum.xda-developers.com/showthread.php?t=519129
[highlight]Wizard:[/highlight]
Not really a single kitchen but xda2_haseeb made a nice guide with links to some kitchens for the Wizard.
http://forum.xda-developers.com/showthread.php?t=501941
[highlight]Universal: (thanks orb3000)[/highlight]
ROM Kitchen v2.0 by Tomal: Next generation Kitchen for Universal
http://forum.xda-developers.com/showthread.php?t=476544
[highlight]Raphael:[/highlight]
Resources and kitchens lumped together by hilaireg
http://forum.xda-developers.com/showthread.php?t=582134
[highlight]Polaris:[/highlight]
Not really a single kitchen but cruiserrr made a nice guide with links to some kitchens for the Polaris.
http://forum.xda-developers.com/showthread.php?t=648171
Now, I am not going to scan the whole site for kitchens, so this is where we all have to pitch in. I know I am missing a few of the multi-device kitchens, but if we all contribute with kitchens for different devices, we can have a nice little resource for many new aspiring chefs...
Let's get cookin'!
Opinions
I decided to make post #2 as an Opinions Page. I will link the posts from each and every one of you that talks good or bad about a kitchen over here.
[highlight]Visual Kitchen[/highlight]
player911
[highlight]Polaris Chef Corner[/highlight]
cruiserrr
One more for the road...
NRGZ28 said:
I think we'll need to neatly catergorize these kitchen collections later on. Maybe we'll them all in the first post of this thread, or we can create another one.
Click to expand...
Click to collapse
I can update the first post as needed. I actually left two more posts after that just in case I run into space issues. I am thinking, one or two posts for device specific kitchens and one for generic kitchens. What do you think?
dXsL said:
excellent initiative, tnx!
wouldn't mind more pro's/con's per kitchen but also realize that is subject to personal experience and/or (strong) opinion
so perhaps only mention the pro's?
Click to expand...
Click to collapse
+1 on this.
PRO's/CON's can be easily worded such that it isn't considered a personal attack.
I would rather know about the CON's and how to work-around them than spend hours in trial-and-error. If a member decides to select a certain kitchen, at least they know what they are "getting into".
M2C's Worth,
* EDIT *
@egzthunder1:
BTW; if you need extra empty posts near the top of your thread, let me or another moderator know and we'll make it happen.
hilaireg said:
+1 on this.
PRO's/CON's can be easily worded such that it isn't considered a personal attack.
I would rather know about the CON's and how to work-around them than spend hours in trial-and-error. If a member decides to select a certain kitchen, at least they know what they are "getting into".
M2C's Worth,
* EDIT *
@egzthunder1:
BTW; if you need extra empty posts near the top of your thread, let me or another moderator know and we'll make it happen.
Click to expand...
Click to collapse
Thanks hilaireg, I might have to bother you regarding the extra posts if this grows as much as I fear it will .
As far as the pro/cons... well, we could do this in such a way that only people who have used the kitchens in question can post them in this thread, so they can give their points of view. I personally have had time to play with 3 of the kitchens that I have posted and used a few tools of another one, but I guess I can add this to the first post and you guys let me know what you think:
"If you are going to post a kitchen in this thread, please be kind enough to give your opinions on it (likes, dislikes, hard to use, buggy, best kitchen ever... well, you know what I mean). This way, new coming chefs will not have to go through the pain of trial and error"
egzthunder1 said:
Thanks hilaireg, I might have to bother you regarding the extra posts if this grows as much as I fear it will .
As far as the pro/cons... well, we could do this in such a way that only people who have used the kitchens in question can post them in this thread, so they can give their points of view. I personally have had time to play with 3 of the kitchens that I have posted and used a few tools of another one, but I guess I can add this to the first post and you guys let me know what you think:
"If you are going to post a kitchen in this thread, please be kind enough to give your opinions on it (likes, dislikes, hard to use, buggy, best kitchen ever... well, you know what I mean). This way, new coming chefs will not have to go through the pain of trial and error"
Click to expand...
Click to collapse
No worries ... let me know once you decide on the format for this thread. Have a look at this thread; might give you some ideas of what could be done for this:
Sous-Chef's Kitchen Utensils & Appliances Review
http://forum.xda-developers.com/showthread.php?t=651026
I use Visual Kitchen
I chose visual kitchen because that was what Da_G used and started me out on. Here are my thoughts:
_________PRO_________
- GUI interface to visually select/deselect packages
- Expandable with Programmable Extra Buttons to ease sorting and cooking stuff
- Allows users to select multiple builds, Lanuages, packages, etc using drop down boxes
- Save/Load configurations and settings
- Robust, Organized and Complete
_________CON_________
- File structure has to be intact or it will fail
- Have to know the building procedure to make sure custom files aren't overwritten
- Packages are in folders, so finding a specific file can be tedious
- Can be overwhelming and confusing to get it setup initially from scratch
I would recommend using this kitchen as it pretty nice. Now of course I say that without using any other kitchen to compare it to... but it does everything I need thus no need to look elsewhere.
_________TIPS_________
EXT folder = Packages (Games/HTC Apps/HTC Dialer/Etc). Additional apps outside of stock MS stuff
OEM folder = Phone specific stuff, OEM customizations, tweaks (usually left alone)
ROM folder = Basic building blocks for WM builds. Has basic device and WM drivers (MSXipKernel updated when SYS gets updated)
SYS folder = WM Build. Contains all the stuff that is stock MS products (updated to change to newer builds)
- Starting out as a new chef... I would suggest that you find a Fully working kitchen designed for your device that is fairly new and updated. Once you can create a working rom, you can then slowly start to expand it by adding more packages and features.
- Don't add too much at once. If you do, and it fails... you'll have to troubleshoot what you added and that can be tedious. It helps to add new packages in groups of 5... so you can test specific parts of the rom before continuing. You'll be surprised that 1 screwed up file can keep your kitchen from completing the building process. Keep that in mind.
- The "EXT" folder is optional and gets updated the most. OEM, ROM, and SYS folders are the only folders really required. Knowing this can allow you to build a very very basic stock Windows build designed for your device. If you have any problems building or flashing, try disabling all of the packages in the EXT folder. If your very very very basic rom still doesn't work... then your "base" kitchen is screwed up. This can be harder to fix.
- Make frequent backups of your "Base" kitchen in the event you screwed something up. I usually will remove the EXT folder and ZIP up the rest in an archive on a memory stick. I update my backup archives after a successful upgrade/edit/tweak of the "base".
player911 said:
I use Visual Kitchen
I chose visual kitchen because that was what Da_G used and started me out on. Here are my thoughts:
Click to expand...
Click to collapse
Updated post #2. Thanks player911!
Hi man!
I think you could add vistang's multidevice kitchen too :
http://forum.xda-developers.com/showthread.php?t=573778
I'm not the right person for a review, but I'm sure one of the guys who used it will be up to the task
Best Regards!
Hi, if you check the link in my signature (Polaris chef corner) you will find quite a few polaris specific kitchens
cruiserrr said:
Hi, if you check the link in my signature (Polaris chef corner) you will find quite a few polaris specific kitchens
Click to expand...
Click to collapse
Thanks cruiserrr for the links. I updated the first post.
Can you give us some insights (in the format in the first page) of pros/cons for some of these kitchens? I don't have a Polaris, so I cannot write any comments about them. Thanks.
i dont have the link but there is a Superjust kitchen for sooo much devices in the net...
+ Que PPC said:
i dont have the link but there is a Superjust kitchen for sooo much devices in the net...
Click to expand...
Click to collapse
Is that the name of the kitchen?
egzthunder1 said:
Is that the name of the kitchen?
Click to expand...
Click to collapse
Here is the link : ivanmmj's SuperJustKitchen
(Supported devices : Artemis , Elfin , Herald , Hermes , Opal)
Regards!
kokotas said:
Here is the link : ivanmmj's SuperJustKitchen
(Supported devices : Artemis , Elfin , Herald , Hermes , Opal)
Regards!
Click to expand...
Click to collapse
Thanks for the link. I will update the first post. Any pros/cons opinions about this?
egzthunder1 said:
Thanks for the link. I will update the first post. Any pros/cons opinions about this?
Click to expand...
Click to collapse
Well it is a kitchen based on OsKitchen by OndraSter&airxtreme!
ps:check post #10 too
egzthunder1 said:
Thanks cruiserrr for the links. I updated the first post.
Can you give us some insights (in the format in the first page) of pros/cons for some of these kitchens? I don't have a Polaris, so I cannot write any comments about them. Thanks.
Click to expand...
Click to collapse
Well, I am not a seasoned cooker but I have updated the polaris chef corner 1st post with my view of each kitchen. Please feel free to take the text if you find it interesting. Most of polaris kitchen's are 26016 EVK kitchens with old kernel, I guess based on gullum's kitchen the first one the share the polaris kitchen for wm6.5. Most of them are based on mega packages. There is one from amenatis based on leo packages but is not 100% completed in english since it is a french kitchen (however, is the one I used as the basis).
For the rest, there are a few other kitchens like vistangs but it seems ondraster kitchen is growing each day. The best one for me is TomAngel's Ondraster kitchen: like any Ondraster's kitchen it has an easy set up of splashscreen and this kinds of things and allows you to cook in several languages at a time. It also has a nice documentation of packages. Additionally TomAngel included a 6.5 native kernel that we are currently testing a few cookers in Polaris but that seems to work and my end with our recmodding hobby.
I personally like better EVK UI but I must say ondraster is also a good solution (and I have "stolen" the kernel from there). I would be glad to share my kitchen I use my own method of cooking shortcuts and tweaks with cmd and mortscript scripts both in the ppc and the pc, so my packages have no app.dat and no png and very few reg files.
cruiserrr said:
Well, I am not a seasoned cooker but I have updated the polaris chef corner 1st post with my view of each kitchen. Please feel free to take the text if you find it interesting. Most of polaris kitchen's are 26016 EVK kitchens with old kernel, I guess based on gullum's kitchen the first one the share the polaris kitchen for wm6.5. Most of them are based on mega packages. There is one from amenatis based on leo packages but is not 100% completed in english since it is a french kitchen (however, is the one I used as the basis).
For the rest, there are a few other kitchens like vistangs but it seems ondraster kitchen is growing each day. The best one for me is TomAngel's Ondraster kitchen: like any Ondraster's kitchen it has an easy set up of splashscreen and this kinds of things and allows you to cook in several languages at a time. It also has a nice documentation of packages. Additionally TomAngel included a 6.5 native kernel that we are currently testing a few cookers in Polaris but that seems to work and my end with our recmodding hobby.
I personally like better EVK UI but I must say ondraster is also a good solution (and I have "stolen" the kernel from there). I would be glad to share my kitchen I use my own method of cooking shortcuts and tweaks with cmd and mortscript scripts both in the ppc and the pc, so my packages have no app.dat and no png and very few reg files.
Click to expand...
Click to collapse
I am putting your review with the others (not that it follows the format that I want, but it is good enough for me )
egzthunder1 said:
I am putting your review with the others (not that it follows the format that I want, but it is good enough for me )
Click to expand...
Click to collapse
Hi, I think it is interesting to share: I can confirm that cooking for Polaris with the kernel shared by TomAngel requires not any recmodding at all !!!
http://forum.xda-developers.com/showpost.php?p=6135182&postcount=27
Do not know if it works for other devices with old kernel, To try import in your kitchen and tell the machine is true kernel
Hi all,
so I am new to the world of Windows Mobile - use to be a Symbian fan and then got the HTC Touch Diamond recently due to my Nokia dieing of old age.
I want to learn how to cook ROMs so I can customize what I want as I want. I tried sending Da_G a PM as he seems to be quite knowledable about cooking - although he seems to be MIA (his last post was a long time ago) and I have not gotten a reply yet.
So now onto some questions which are probably stupid, but I do not know the answers to.
So I have an HTC Touch Diamond which originally comes with Windows Mobile 6.1, I am using osKitchen as it seems really popular and it looks easy enough to use. I followed the guide which is here but it does not give me the complete info I want.
So in order to cook a ROM you first need to have an original ROM (so in my case an original ROM for the HTC Touch Diamond off the HTC site?)... I got that(RUU_Diamond_HTC_WWE-AFK_2.03.421.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe)
Then you open it up with osKitchen, it extracts it blah blah blah.
I then get a popup about a new ROM has been imported and it asks me if I want to automatically configure the project to use the ROM. I click yes.
Then it says the device profile currently selected uses a pre 6.5 kernel, module allocation space will be extremely limited. Do I want to auto enable module to file conversion for a list of files? Now I read somewhere that if you are using pre 6.5 kernel you want files, if you are using the 6.5 kernel you want modules? I am not sure what to click here as I want to upgrade to windows mobile 6.5 ...
So do I enable the conversion or not?
Then it pops up with the project settings, under SYS Packages I can see all of the phones services. OEM packages, I am not too sure what that is... One thing which is worrying is that there is a red circle with an X in it infront of OEM Drivers... If I hover over it, it says there are issues detected in the OEMdriers. They all seem to be errors detected in the registry and the registery key path entry is invalid due to 2 adjacent backslahes? So is this normal? What do I do?
Also there is a block "RecMod" under OEM Packages. What does that do and what is it used for?
EXT Packages, over here we have all of the applications which will be preinstalled when you flash the ROM? I know how to add .cab packages to it and it seems simple enough. Once again there is a RecMod with a tick box?
ROM Tweaking I have not really bothered with yet, would first like to learn the basics. Anything I should know about in ROM Tweaking?
Now back to SYS Packages. This is where you update/port/upgrade ? to newer windows mobile versions? Now I think if you are changing between window mobile major build versions or what ever you want to call it (like from 6.1 to 6.5) kernel changes perhaps? You call it porting? Anyways, so now I want to change to the latest build in WM6.5 .
I took a look at this thread: http://forum.xda-developers.com/showthread.php?t=650783
Now it seems like the first 3 digits indicate something, what exactly I am not too sure. Perhaps someone could explain?
There is HTC HTC which is made by HTC I think and possibly meant for HTC?
Then there is COM 2 and LG. Now since I have an HTC do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
Anyways, I downloaded the HTC one. Now I want to port / upgrade to it. It is WM6.5 now as well. So I click Import, then goto Import a new WM build. Select the appropriate build dump, then click on start importing. It will import it and then what? Is there anything else I need to do?
I am assuming go back to Project Settings and under SYS build change it to the newer one which I have just imported? Although is this really all I need to do? Will I now have a proper functioning cooked ROM running WM6.5 with the new build?
Thanks
If you're cooking a 6.5 rom, and you have a 6.5 native kernel (there should be one out there, unless you're using a cdma diamond), then DO NOT RECMOD (convert to files). If you have to use a 6.1 kernel, then you have to recmod a lot of modules. Look around, there are threads with native kernels for many older devices. I'm not going to dig up a link, I'll let you find it. Just get the Diamond native kernel and use it.
If you have a cdma diamond, then I believe that people use the cdma raphael native kernel, but supposedly it's buggy.
OEM Drivers has an .rgu that usually has a few mistakes in it; that's probably the error you're getting. I wouldn't worry about it, but the kitchen may tell you which line the error appears in, and you can fix it.
As far as rom tweaking goes, all you need to know is that manila sucks, and Sense is blight on humanity. Good luck and have fun.
Real Beginners Stuff Please.
PsyCLown89 said:
Hi all,
so I am new to the world of Windows Mobile......
I want to learn how to cook ROMs so I can customize what I want as I want.....
So now onto some questions which are probably stupid, but I do not know the answers to......
...... I followed the guide which is here but it does not give me the complete info I want.....
..... What do I do?
..... What does that do and what is it used for?
..... would first like to learn the basics......
..... so now I want to change to the latest build in WM6.5 .
..... do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
.....and then what? Is there anything else I need to do?
.....Thanks
Click to expand...
Click to collapse
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
It all comes down to the basics. If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
Kitchens available today make a lot of things heaps easier than they were several years ago.
Try starting with this thread.... it is not for your device, but you get to learn the basics and actually understand what happens in the background.
http://forum.xda-developers.com/showthread.php?t=335631
Cooking is not just clicking around with your mouse.
pkoper said:
.... If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
..... Cooking is not just clicking around with your mouse.
Click to expand...
Click to collapse
This may be new to me, but it also was to EVERY cook there is, or has been at sometime. We all learn something new at some time, and all I was asking for is a little starter to get me going. I realaise it isn't a point and click exercise, otherwise I would have made a ROM by now, and not asked for help. I didn't write the software for the kitchen, so I don't know how it works.
http://forum.xda-developers.com/showthread.php?t=335631
Click to expand...
Click to collapse
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Please, give me a break.
Fish-Man said:
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Click to expand...
Click to collapse
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Fish-Man said:
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Click to expand...
Click to collapse
Thats exactly what I meant. Do you know what the kernel actualy is?
pkoper said:
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Click to expand...
Click to collapse
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Thats exactly what I meant. Do you know what the kernel actualy is?
Click to expand...
Click to collapse
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Fish-Man said:
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
Click to expand...
Click to collapse
I don't think what you're looking for exist, persay. There are several kitchens out there to choose from. The only thing that helped me when starting out was frequenting the thread of the kitchen that I was using. It's in the kitchen's thread that you'll find all the nitty gritty answers you're looking for and other people that are in the same boat as you, and more experienced users of the same kitchen who would probably be more apt at answering questions about specific kitchen.
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
Nice quick knowledge drop on kernel. It sounds to me like you already have a better grasp on things then some!
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Click to expand...
Click to collapse
Thats because there is no stock 6.5 for the Kaiser. Not sure what "those WM6.5 files" are, but you do need the drivers for your device. Any leaked build will not contain those.
Dumping a stock rom will give you insight as to what is actually in the rom. When you then download one of the leaked builds you can you will recognize the files and hence see what needs replacing in order to upgrade.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
What kitchen are you using? As there are obviously slight differences as to what is where.
I would just get a ready kitchen and study it.
http://forum.xda-developers.com/showthread.php?t=517957
for your reference maybe you should read this....
http://forum.xda-developers.com/showthread.php?t=901712
i had made the tutorial how to cook ROM, step by step. it has different device and different OS but worth to read.....
i don't have enough capability to Cook but i try to....
also in this http://forum.xda-developers.com/forumdisplay.php?f=385
some of members also made tutorial as well.......
i hope it can help.
Hi all.
I'm creating a Windows Mobile Rom.
1)---I want to create a rom modifying my smartphone's rom and NOT creating a rom from a clean one (it will be almost impossibile).
2)---Which kitchen can i use?
3)---Where can I download the latest Windows Mobile 6.1 and 6.5 Builds? (Da-G's download don't work anymore on Mediafire)
Thanks
Try OS Builder as this is the most advanced and all in one solution. But be aware that if you start from an already cooked ROM you may face many kinds of problems because many cooks have applied methods to prevent dumping their ROMs.
Good luck!
tobbbie said:
Try OS Builder as this is the most advanced and all in one solution. But be aware that if you start from an already cooked ROM you may face many kinds of problems because many cooks have applied methods to prevent dumping their ROMs.
Good luck!
Click to expand...
Click to collapse
Thanks for you reply!
But, to pass from Winmo 6.0 to Winmo 6.1 or 6.5, do I need 6.1 or 6.5 builds (xip,sys)?
Where can I download these build?
Mich-C said:
Thanks for you reply!
But, to pass from Winmo 6.0 to Winmo 6.1 or 6.5, do I need 6.1 or 6.5 builds (xip,sys)?
Where can I download these build?
Click to expand...
Click to collapse
Oh well - you are much on your own with this old stuff now. Usually you cannot do much to the XIP (Kernel) parts as they are largely HW dependent. SYS is part of the ROM anyway and so part of regular cooking. Lookup the forums for your device and download what you can get. If it is an exotic device your chances are ~zero to get anything useful. If you have no experience in cooking it is a very long way to succeed (talking in weeks and months of learning!) - and there no others fighting the same problems any more. Look up the introduction link from my signature to get an idea of how things are connected.
What is your starting point (HW, ROM) and where do want to go?
TOBBIE, in practice I want to use Os Kitchen (http://forum.xda-developers.com/showthread.php?t=628948) because it's very simple to use.(I can alredy use it).
I downloaded but when I open it, I have the first screen (that showed in the thread). Is written: "....please, select an official rom update file..." It refers to an update Windows Mobile Build for cook the Rom.
So I searched Windows Mobile 6.1 and 6.5 Builds. I found 2 very good Builds from Da_G :
-6.1 http://forum.xda-developers.com/showthread.php?t=547314
-6.5 http://forum.xda-developers.com/showthread.php?t=544445
But ALL Links don't work and I ABSOLUTELY need this Build, without it, I can't cook...
Sorry, I have no experience with OS Kitchen. I have only used OS Builder finally and a very old device specific batch-kitchen before this.
Thanks, Can i give you "THANKS"?
But with wich build did you used to cook?
Mich-C said:
Thanks, Can i give you "THANKS"?
But with wich build did you used to cook?
Click to expand...
Click to collapse
Well first you need to split smartphone (no touchscreen) from touchscreen devices.
I have cooked only for smartphone -> see my signature kitchen and stuff is all there.
Then find a stock ROM for the right type (smartphone or touchscreen) with largely similar properties (screen resolution, maybe also CPU/Chipset).
Can't you tell which device you want to cook for?
I want to cook for my Toshiba Portege G910 with WinMob 6 Professional.
It's touchscreen, it has Qwerty Keyboard, it has Wvga Resolution 800x480. There is not even a rom for this device.
But I want to cook in Italian language, (I'm italian )
This will be tough I guess. Mind that a new ROM will not change the kernel, so any of the new memory schemes introduced with W6.1 and WM6.5 will not apply even if you put a new OS on top of it. So basically you will not gain speed with a new ROM. Adding a language is a tricky thing but is possible, see my signature, even without cooking an all new ROM. So is there no Italian on the device at all?
Oh, I'm sad for this: no extra speed
When I bought, my phone had italian language.
The Toshiba Portege G900 is very very similar to my G910. Also the G900 has WinMob 6.0 Pro.
An Italian guy made a Winmo 6.1 rom for the G900 (in italian language), and now the G900 is very very fast. http://www.youtube.com/watch?v=N4h23pR6JbI
I want to this with my G910, IT'S possible. Salvyc83 do this
(But now he can't help me)
Search for speed tweaks on WM6 if you are happy with the device otherwise. The effort to cook a well running 6.1 is enormous and it is not guaranteed if you get it faster on the UI then.
There are various registry settings to play with which can make the UI faster responding (cache for icons or fonts).
Good luck!
I need too to learn cooking roms. I will follow this thread.