Rom Kitchen sync with Jeffs Kitchen - MDA, XDA, 1010 Software Upgrading

Hi Everyone
The Rom Kitchen downloadable from xda-developers seems to be out of sync with Jeffs Kitchen (New security add on). I thought Jeffs Kitchen was updating itself from the xda-developers. Is this a short term thing or do I need to update my kitchen from a different source ?

Related

ROM Kitchen

From the WIKI: ROM Kitchen is a tool to cook your personal Windows Mobile ROM by the packages you need.
So this means that you can build (cook) your personal WM version using this tool.
An example of a kitchen is HyperCore.

[23July]Kitchen Windows Mobile 6.1

Hi to all,
I thing that there are very few chefs and we should share knowledge the others cookers should share them kitchens too.
Bugs
Bt headset bug (i was not able to fix it i am open to suggestions)
DeadLink V2
Kitchen WM6.1 21042
Regards
Rukako
Thanks for sharing Rukako, mm.. your Deadlink rom without manila is what I need.. as I dont use it.
I'll try and make one.. thaks again for posting it
Rukako please fix kitchen archive (Kitchen WM6.1 21042) crc error.
I need this kitchen for translate it for another language.
Build 21054
Thanks Rukako for your nice work. It will be nice and sweet from you if you could do:
- Modifying the Kitchen to include 21054 files.
- Developing simple guide lines to cook lite or naked version of your ROM.
Thanks again for your nice MW6.1 ROM Kitchen.

Newbie ROM cooker

Hello everyone,
I am Newbie here (for cooking).
I have Rhodium (aka Touch Pro2).
I have download the last 23563 from Da_G.
And i would like to know how do i manage to put the Roll-Up package of Da_G,
and use ervius kitchen to cook a rom with the new xip / sys that have we today
with ext packages of Leo 2.10 that i have download, and Rhodium 2.08 OEM.
Can someone guide me how to put it all together and make my first ROM?
Thank you all, for your time!
I suggest you to read some tutorials here on how to port a sys into EVK
You will need netframeworks 3.5 in your PC and some Visual c++ 2005 or 2008 redist pkgs installed too... then you need the Ervius Visual Kitchen (as u said) kitchen get the EXE for 1.8.2 version post your kitchen_build_rom.bat to modify it... and start setting the kitchen for your device...
there are plenty TUTs about we will update the first stickie to have all the tutorials for you in a while
so go here and read... good luck we will assit anything
http://forum.xda-developers.com/showpost.php?p=4268143&postcount=1

How to build a new WM6.5 rom base on WM6.1 ship Rom?

Hi all,
I try to cook rom for my device Samsung M490. I have a Ship rom in Korean language(0412) ( i cannot find the English one).
I build with new WM6.1 SYS/XIP (lang 0409) , the device boot ok, the language changed to Eng, but the setting shortcut not work. I cannot set the rington.
I build with new WM6.5 SYS/XIP (0409) and it cannot boot, the screen turn off after the Anycall logo appear.
Now can you ask me how to make it work with W6.5 build? what thing I will do, what file/folder will be change/edit?
My ship rom here:
Code:
211.189.38.83/umsvcbin/SCH-M490/SCH-M490_CI24_pda.bin
I do follow as below:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN (23662) as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build (23662), repalce initflashfiles.dat by English one. add XIP.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Thanks very much for your help
There is too little info here to help you. Does your device have a native 6.5 kernel? You will need to have one to be able to flash a 6.5 ROM and make it work on your device.
You mean ''oemxipkerner''? .Samsung didn't release the wm6.5 rom. but i found some cooked wm6.5 rom in Korean and Chinese. can I take it from these rom?
I dont think so. You will first need to dump a stock rom provided by Samsung for your device. Then replace the oemxipkernel with a patched one, which has a 6.5NK.
I dump a ship rom already, I use XIPkithen to make a new xip.bin from a new wm6.1 release, the device boot ok , I do the same way with build wm6.5 but the device can't boot. where can i find a patched oemxipkerner?
You will have to search for it. You will need a 6.5NK for WM 6.5.X to boot on your device.
If Samsung has not released a stock 6.5 ROM for your device, chances are you wont have a native 6.5 kernel.
If you don't have a native 6.5 kernel, you need to recmod a lot of files/folders. This thread @ Mobile Underground has lots of good info.
You said you dumped a stock 6.1 ROM. In this ROM, see if you have a 6.5 Native Kernel by dumping xip.bin. Open nk.exe/s000 in a hex editor. Search for the ASCII string "platform". Near this string there should be the build number that this nk.exe was compiled against.
WM 6.5 builds began around 21100. WM 6.1 and previous builds will be <=21058.
OsKitchen can import the ROM of that phone and also seems able to rebuild it correctly (but make sure the final file is correct for your phone since there are something like ten different BIN file formats) and since it can already suggest the packages to recmod it could also help with 6.5.5 porting if you don't have a 6.5 kernel (which you probably won't find anywhere: the only modded 6.5 kernels I've seen are for htc devices).
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
theanh6 said:
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Click to expand...
Click to collapse
Which EXT packages are you using?
anand12 said:
Which EXT packages are you using?
Click to expand...
Click to collapse
I don't use any EXT packages.
theanh6 said:
...-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs....
Click to expand...
Click to collapse
First of all - don't try to dump someones roms to get xip.bin or whatever!
Many guys, including me (does not matter - Chinese or not) - are deleting reloc sections and dsm files while building custom roms to save the space. So if you use such a xip - you will get non-bootable rom.
1. Take the latest OFFICIAL rom
2. Dump it to get original XIP and original OEM
3. Download new build that you want to cook.
4. Port new xip. Use the original XIP as donor of OEMXIPKernel and new xip from downloaded build as a source of MSXIPKernel & MSXIPKernelTLK
5. Take ported xip, OEM (drivers) from official rom, SYS from downloaded new build
6. Start cooking.
Very nice step by step explanation by Andrew. It doesnt get simpler than this!
The most important part - Dump the official rom released for YOUR device NOT for any other. You risk bricking your device.
Thanks AndrewSh & anand12 for your advice, i follow step by step but it only ok for a 6.1 build, and wm 6.5 fail to boot again.
Now I sucess to build an English wm6.5, my way is:
-Dump a cooked Korean ROM build 21815, I have \ROM, \OEM, \SYS, XIP.BIN.
-Remove all file/folder in \SYS but keep .ROM, .VM , Metadata, then copy all from SYS build 21815E(English-0409).
-add XIP.BIN above into OS.NB get from official rom an copy new OS.NB to \ROM.
-Now i have \ROM; \SYS; \OEM, copy them into kitchen an run. Flash new rom to phone and it work ok.
I try to cook a new ROM with last wm6.5 build, but i feel sad because it fail again.
Now i have some quesion, please spend a litle time to help me to clarify:
1. i think my problem is at "Metadata" folder. When we cook a new build, what will we do with "Metadata" (change all folder, change some file/folder or edit some thing) ?
2. I can not set the ringtone for my cook rom, both in 6.1&6.5 build. The "Ringtone" feild is empty as the picture i attached. What thing be wrong here?
Look you must have a 6.5 NK for your device. If not, you must recmod files. Are you doing that? Please be sure and clarify.
@theanh6: Can you upload your cooked here? Thank you very much.
Thank you all, It fully working now (with some small bug but no problem)
@Mrkid: Please send an email to me at [email protected] if you want to try this rom.

[Q] How to cook a bootable rom using XIP from one build and SYS from another build?

How to cook a bootable rom using XIP from one build and SYS from another build of the same branch? All my efforts resulted in non bootable roms.
What kitchen are you using?
What kitchen are you using? I make many of such ROMs for the LG KS20. Even mixing various versions of wm. (I made 1 wm6 ROM with wm6.5.3 styled menus.) Try using xipport. It solved all my bugs.
Thanks for the reply. I use EVK for HTC Gene. I was trying to cook xip from 21899 and sys from 21916. But the rom do not go beyond the first boot screen. Can u elaborate a bit more?
Did it flashed a bit brighter for a while and then went dim again? It would mean XIP started ok, if not - then it's XIP...
Are you sure you have wince.nls SOMEWHERE? (either XIP or SYS)
And another question: are you sure you're implanting XIP into image properly? Generally, mixing SIMILAR XIP and SYS is not a problem at all... some time ago it was everyday practice, as we had more SYS releases and porting XIP was a bit harder than nowadays. Find a XIP porting tutorial here on xda.
Yes it flashed bright and then went dim. the first boot screen comes but afterwards no tapping instructions and remains still. I changed only MSXIPKERNEL. I get a bootable rom with 21899 SYS and XIP as well with 21916, in the same kitchen. Thanks for all the input.

Categories

Resources