hy all. i have a problem (wish): i want to install a clean rom ( i have it allready) and i want to customize it with the programs that i want to, and then, to save this rom (i supose that i have to dump it and reconstruct it) exactly with my settings/applications/etc. can i do that? if I can, how? thx alll.
When you customize your polaris on the device itself, it doesn't change the ROM on it. So dumping it will not give you a new ROM. You'll have to change the ROM on the desktop, and upload it afterwards. There are a lot of topics about ROM building.
ok. thx. i will go then to that topics. thx.
Yes but the problem is that all those posts are about porting a 6.1 rom from another device to polaris.
Now that we have a 6.1 rom how exactly do we cook it and flash it back?
Here's my problem: I have the PTG 6.1 rom, but I want to replace the CF2 with CF3.5 and replace TTN6 with TTN7, and flash it back.
I already have Kitchen 1.3, extracted the 'RUU_signed.nbh' and a dump of 03_OS.nb.payload.
Now, where do I go from here?. I want a rom that's exactly the same as the official one but with the changes I mentioned above.
I'm a complete noob at this cooking rom issue. I've read lots of threads but I've only gotten more confused about all the XIPs, SYSs, OEMs and stuff, and I think the same happens with other users.
I know that some of the actual cookers were once in the same place I'm now, so can someone point me out the rigth way and if possible post a detailed tutorial on how to extract, cook and flash back a rom on POLARIS, me and lots of users would apreciate it a LOT.
Second That Thought.
What would be nice to see (if possible) the following,
as an example:
1. Download Polaris ROM Kitchen v1.3
2. Extract to c:\Kitchen
3. Copy your ROM image (*.nbh) to X:\
4. Run command
...20. Install Package (M2D.cab) by doing the following ...
21. Recombine the ROM by doing the follow commands ...
22. Flash your ROM to your Polaris
23. Hard Reset and verify that the package you installed is in your ROM
Congrats
A step by step like that, which walks a user though the process of a demo ROM and a demo *.cab for learning would be FANTASTIC!!!
Thanks in advance to whoever can help us out!
Juxtyce
bump.
Any help from the professionals out there?
Look here:
1. .Net2.0 => .net3.5
http://forum.xda-developers.com/showpost.php?p=2685138&postcount=22
2. replace the ttn.cab file in the folder "\kitchen.work\Build\OEM\OEMAPPS" with the TomTom7 cab. If it don't have the same name, rename the new cab or edit the file 'config_AP.txt' in the same folder
hope it will help you I managed it this way.
P.S. I didn't change the XIP as mentioned in the given thread. See following posts
I will dump the wm6.1 rom for you guys, and provide you with a kitchen with some packages you can use.
I will do so for all available languages that is available with official wm6.1
But,that is gonna be quite time consuming, and I hope that you understand that I ask this in return:
Any small donation for the time I use on that will be of help.
I dont say that its required, not at all. I am not doing this for money.
But the number of hours I spend on this is getting pretty high.
I will do this project either you donate or not.
cheers
thank you a lot itje. can you make in romanian also?
dunno if it's the good topic to post but let's try.
I see many fantastic people cooking excellent roms (i wish i could do the same...), and, in those roms, a lot of softwares.
Isn't it possible to just have a rom with the bare minimum?
and seperate cabs to install what you want?
for example, manilla 2d is cool, but many people like spb mobile shell better, so it's wasted memory.
May be i'm just wrong, don't understanding how it all works, so plz explain to me !
ady_uaic said:
thank you a lot itje. can you make in romanian also?
Click to expand...
Click to collapse
if the language is available; yes
taniwha913 said:
Isn't it possible to just have a rom with the bare minimum?
Click to expand...
Click to collapse
There is a large choice of ROM's, some loaded with extra's, some very minimally equiped. There are so many that your favorite must be out there already. Just search for it.
Anyone who can dump a Dutch Ipaq 614c ROM?
It would be much appreciated
If you're still looking for one, maybe I can be of some help...
charlieMOGUL
Yes, I'm still looking for a Dutch ROM or a dump of a Dutch ROM.
i am also looking for a dutch rom. if i can help with something or need to do anything just let me know, i need this ROM very bad.
sincerley locoo
Maybe this can be usefull
It is a Dutch ROM
*I will post a working image soon.
For anyone who is interested in cooking a Dutch ROM, here are the OEM en SYS files, extracted from the ROM.
http://uploading.com/files/6a1634d9/OEM_%26amp%3B_SYS_Dutch_Ipaq_614c.rar/
Also for creating a Dutch xt9 cab file, these files are usefull. Creating the cab file myself wasn't successfull. This is a package ready to be cooked for Dutch xt9 files.
http://rapidshare.com/files/278550136/Dutch_xt9_for_IPAQ_614C.zip
Darqw said:
Maybe this can be usefull
It is a Dutch ROM
http://rapidshare.com/files/278140280/Dutch_IPAQ_614C_ROM.rar.html
Click to expand...
Click to collapse
First of all i want to thank you very much for this rom, however
i downloaded this, and flashed it on my device, flashing went perfectly but as soon as the windows mobile screen pops up along with that ''trendy'' beep sound, it gets stuck on it.
i left it a couple a minutes, i stays on the screen showing the ''please wait''
spinning logo of WM 6.
i also tried to reflash it, also re downloaded it in case something went wrong downloading.
anyone else facing this problem to?
and 1 other question,
i made a dump of a hp 614 i have, wich is Dutch, now i got the following files :
- diskimage_Ver.nbo
- part2.nb0.payload
- part2.nb0.payload.part1
- part02.raw
when i whas searching forums i found out that i have to change the
diskimage_Ver.nb0 to FLASH.DIO
i tried this and the device got stuck at the ''clean boot'' part.
obviousley i don't know alot and i'm sorry to ask anyone's help.
but what do i have to do with those other files? how do i make those files to a complete working ROM?
any help appreciated,
thanks to all people that helped me comming this far
I see the problem... I didn't have time to test it thoroughly.
Here is the link for a new (and hopefully a good working) ROM image.
http://rapidshare.com/files/278647058/original_dutch_1.00.rar
The problem is that I myself am still trying to learn to cook, so don't expect any miracles... That's why the first one didn't function properly. But normally this ROM schould function, as it is an copy of a Dutch Ipaq 614c.
If anyone is interested in cooking an up-to-date Dutch ROM, all the necessary tools and dumps are (normally) available. I already posted the OEM and SYS folders separately or they can be extracted from this ROM image.
At the moment I am not able to create a good working up-to-date Dutch ROM image, hopefully somebody is able to create one with the help of this ROM image.
Darqw said:
I see the problem... I didn't have time to test it thoroughly.
Here is the link for a new (and hopefully a good working) ROM image.
http://rapidshare.com/files/278647058/original_dutch_1.00.rar
The problem is that I myself am still trying to learn to cook, so don't expect any miracles... That's why the first one didn't function properly. But normally this ROM schould function, as it is an copy of a Dutch Ipaq 614c.
If anyone is interested in cooking an up-to-date Dutch ROM, all the necessary tools and dumps are (normally) available. I already posted the OEM and SYS folders separately or they can be extracted from this ROM image.
At the moment I am not able to create a good working up-to-date Dutch ROM image, hopefully somebody is able to create one with the help of this ROM image.
Click to expand...
Click to collapse
thanks for the updated ROM link, i'll post a review of the ROM ASAP.
this will be tomorrow,
ontzettend bedankt!
could you please explain me what to do with the 4 files, how they needed to be set-up for a working ROM, im also trying to get the hang of cooking a ROM.
ill be glad to hear from you once again.
yours sincerley,
alex
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.