[TUT] XDA Atom WM 6 and WM 6.1 ROM Cooking - iPAQ rw6828, XDA Atom ROM Development

ATOM WM 6 AND WM 6.1 ROM COOKING TUTORIAL
nb: try it at your own risk,.
WHAT DO YOU NEED?
- Hypercore Kitchen
- Garmin XDA ATOM ROM Cooking Sets (UPDATED 14/03/08)
ADD-ON
- WM 6.1 SYS files
Usage Of Hypercore Kitchen
- Creates OEM and anything related to OEM
Usage of ATOM WM6 Kitchen
- Dump your diskimage_ver.nb0
- Build your new diskimage_ver.nb0
Already have it all?? Alright, now lets start working,.
1. Extract "Garmin XDA ATOM Cooking Sets" to somewhere you like, (There will be an original OEM and SYS folder, don't erase those, it required for dumping process,.)
2. Put your diskimage_ver.nb0 into ROM folder, (overwrite the original file there,.)
3. Run "DumpFiles.cmd" , (Then you'll see a working progress, until it ask you to press any key) ---- press any key then,.
4. There will be a new window come named "Package Tool", then Open where the "dump" folder is located, (The package tool help you build your OEM and DSM,.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Go to \Tools\Build Package, you will not see a working progress, when the content of the Package tool was changed, ITS DONE!!, and your diskimage_Ver.nb0 was dumped,.
(The original OEM and SYS folder will be gone,.)
--- Now go to "dump" folder and you'll see OEM and SYS folder ---
nb : If there are some files outside OEM / SYS folder, put it where it should by reading the last line of your package tool, after building a package,.
----------> means that these file should be in \SYS\NetCF folder,.
OKAY, take a rest first, have some experience with that OEM and SYS folder,.
You may change, add or remove some folder there, but BECAREFUL, some of them are SYSTEM file!!!
Satisfied experience with OEM and SYS folder?? Lets Continue,.
6. Now move your OEM and SYS folder (inside "dump" folder), to the first page (Where the original OEM and SYS is located)
7. Run "BuildOS.cmd" (You will see a new window "BulidOS",.) press the green button,.
8. When done, (you could see on the bottom left corner, written "Done"), close the BuildOS by pressing the [X] Button, (dont close the BuildOS.cmd)
9. You will see in the BuildOS.cmd, a progress, wait till it ask you to press any key,. ----- Press any key then,.
10. There you are, your new diskimage_Ver.nb0 is inside "FLASH" folder,.
Nb: For a tutorial about building an OEM, could be seen HERE, and How To Port XIP and SYS folder, could be seen HERE,.
nb: For WM 6.1 Cooking, you couldn't DUMP your ROM, because it removes all manifest to be one,.
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -

---

STICKY IT!!

---

udayrulz said:
STICKY IT!!
Click to expand...
Click to collapse
Thanks mate,.

---

the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.

---

medkid said:
the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.
Click to expand...
Click to collapse
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.

---

@Ckaidi
Exactly , although i have no way near the knowledge required to make 1 but ...i just did a quick background check on you and figured out that you hv been cooking for a while now....so yea i understand wat you lookin at..

---

This is really different from what we used to cook for xda 2. How I wish cooking for an atom is as easy as cooking for an xda 2.
Anyway, good luck to all who would like to attempt cooking their own ROM. I'll just look at those available in here and copy those that I think will fit me best.
BTW, I hope somebody can teach me how to change the splash images. I would like to replace them with pictures of my family.

---

^welcomehead.96.png = splash image..
found in SYS folder..

---

Garmin said:
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.
Click to expand...
Click to collapse
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.

---

bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-

---

You have to add them in OEM folder mate...

---

udayrulz said:
You have to add them in OEM folder mate...
Click to expand...
Click to collapse
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-

---

serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
Yes , the files go to windows directory automatically
First download Ervius Packages Creator..
..say you want to include TCPMP in your ROM , You first need to Unzip all the files that TCPMP installs to a folder ..now open Ervius Packages Creator..navigate to folder .add a shortcut (option in the packages software..)
and click create package..now copy the folder to the OEM folder and build ROM..
Hope you get the idea..

---

yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-

---

I dont know that ....sorry...

---

You can obviously create Custom Cabs and run put em in extended ROM for installing in program files..
You can search for OEM packages on the site.. u ll find plenty...
I am still learning so do pass on the knowledge..
Going a bit OT - Are you the one who made the DSU installed for ROM installation??

---

serialzs said:
yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
you will specify it in initflashfiles.dat, but you will have a double copy. The purpose of putting it to ROM is to have all the applications you need and consume less persistent storage vis-a-vis installing the cabs after a hardreset. However, having too many files in \windows will cause your system to lag; so, this is the purpose of utilizing the extended ROM wherein the skin files (like wireless manager / htc home / mediaplus) can be placed in the extended ROM and the program files in \windows.

---

serialzs said:
bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
To add a new appz, you have to make your appz (appz that you would like to have as a default appz) as an OEM,.
How do we make an OEM? i am working on it, i'll post it here soon,.
all the files there (inside SYS and OEM folder) will go to windows directory, then if you would like to move something to program files directory, you have to make an "initflashfiles.txt",. (usually for your OEM)
for example,
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")
----- > it means that you copy file "coldinit.lnk" to \windows\startup folder,.
hope that help you,.

---

serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
It wont go anywhere, as long as we dont make a "initflashfiles.txt" for our apps (that have been changed to OEM), the shorcut of the apps wont go anywhere, it still in windows folder, (so, it wont be displayed in the main menu)

---

medkid said:
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.
Click to expand...
Click to collapse
Ow i see,. sorry missunderstanding,.
Yep, absolutely you could, i am working a new ROM with upgrade of XIP to 5.2.1933 at the moment, if it success, i'll update the thread,.
but it havent finished, so the thread just till extracting and repacking,.
Gud luck,.