Hello.
I think ive been reading for the last 5 hours about this topic.
I've managed to dump the ipl spl splash gsm os .nb files using typhoonnbfdecode.pl.
Then i managed to decode os.nb using prepare_imgfs.exe -nosplit option and then make_imgfs.exe. The next thing recmod crashes.
Ignoring that crash, I've changed a folder in the dump rom and I've tried to compile it using BuildImgfs.exe and make_imgfs.exe but nothing happens actually.
Would you please give me advice on this topic? I need to replace the keyboard driver from a orange aku2 tornado rom to a i-mate rom.
its been a "long" time since i wrote this.
what have i found more? i now know to compile the files back *the nb files to one nbf file*.
so i now have a dump directory but i can't compile it.
if you have any advice on this, please help.
Hey
I'm interested in cooking a new Tornado ROM as the old AKU2.0 is, well, OLD! lol.
could you point me in the direction of a nice comprehensive guide on cooking a rom? and what software would i need?
thanx
i know like almost 80% of the process but i cant compile the .nb or .nba file after i dump it.
Hey
Do you have all the necessary files to do the rom kitchen?
------------------------------------------
Device-dependent packages:
DEV:
[li]DEV_Himalaya_v1.50.rar[/li]
ROM:
[li]ROM_Himalaya_v1.50_3.00a.00.rar - 128MB RAM[/li]
[li]ROM_Himalaya_v1.50_3.00a.32.rar - 96MB RAM / 32MB RAMDisk[/li]
[li]ROM_Himalaya_v1.50_3.00a.64.rar - 64MB RAM / 64MB RAMDisk[/li]
Independent packages: !!! Both should have the same AKU !!!
OS:
[li]OS_AKU_2.0_v1.50.rar - AKU 2.0 (Build 14847)[/li]
[li]OS_AKU_2.2_v1.50.rar - AKU 2.2 (Build 14928)[/li]
[li]OS_AKU_2.3_v1.50.rar - AKU 2.3 (Build 14955)[/li]
[li]OS_AKU_3.0_v1.51.rar - AKU 3.0 (Build 15096)[/li]
LOC:
[li]LOC_AKU_2.0_v1.50_[ WWE | GER ].rar - AKU 2.0 [/li]
[li]LOC_AKU_2.3_v1.50_[ WWE ] - AKU 2.3[/li]
[li]LOC_AKU_3.0_v1.50_[ WWE ] - AKU 3.0[/li]
------------------------------------------
basically the above but for Tornado instead
I'm assuming, because we're simply using a different AKU update, and not an actual NEW OS update, (as when people were upgrading from WM2003SE to WM5 i can understand there would be driver incompatibilities)
so, it should really be as simple as basically extracting the relevant keyboard/joystick/camera/hardware button drivers and inserting them into the SPL rom?
could you post what you have currently?
or better still, could you zip everything up and email it over to me at gmail? its duke.stix [at] googlemail [dot] com
i really wanna upgrade the AKU on the tornado! the aku 3.5 update on the pocketPC's looks a whole lot different!
ah, the thing is i dont have anything right now.
its useless all this work if you dont even know how to compile the final product.
when i will do the succesfull compiling of the dump i will do the cooking.
hello everybody
please share a simple Tornado ROM kitchen
XIP 20296 for Polaris.
two days two great contributions,
cheers
SHAYDER said:
XIP 20296 for Polaris.
Click to expand...
Click to collapse
?! Sorry but what is XIP 20296 for Polaris, what does it?
Yes Please Tell Us For What Need This Xip ????
I'm not entirely sure, but I think a XIP is the OS part of a ROM. This file is needed when a ROM cook creates a ROM.
JAYmasta said:
Yes Please Tell Us For What Need This Xip ????
Click to expand...
Click to collapse
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20296 is current XIP.
To build ROM with new XIP you must: put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
Is it worked for ya?
Some kitchens or even ROM packages already comes with most files found in msxipkernel...you should cut off one side or another. I generally keep bottu.rgu alone in XIP and move msxipkernel to sys folder...then cook...
still playing with 20275.
Where 20296 is from?
Thanks for sharing!
SHAYDER said:
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20296 is current XIP.
To build ROM with new XIP you must: put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
Click to expand...
Click to collapse
If You use "Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)"
You have 3 main folders: "SYS" "OEM" "ROM"
In "ROM":
You have "XIP" folder and "os.nb.payload" (XIP in "os.nb.payload")
In "XIP" folder you have ONLY "boot.rgu" (it is not main XIP)
In "OEM" you nave drivers and applications.
In "SYS" you have OS.
1)You must put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder.
2)Replace "os.nb.payload" in "ROM" folder. (because thet "os.nb.payload" with old XIP. You must put my "os.nb.payload" without XIP. And when you cook you ROM, new XIP copy from "MSPPCXIPKernel" and "MSXIPKernel" folders)
3)Put my "imgfs.bin" to main folder.
4)Run "BuildOS.exe"
5)Run "Build ROM.bat"
There where I took this XIP, written that it is taken from Diamond.
But i am not sure. Because i cant find official Diamond ROM with this XIP.
Thanks m8 for your contribution !! Really appreciate it.
Olioaglio
I am struggling my way through the cooking lessons...
I already succeeded using evrius kitchen for dumping a stock rom and than rebuild it (thanks twopumpchump).
In my next "lesson" I am trying to upgrade WM build (a small step - 21887 to 21895 - I use the one from Energy post). I copied SYS / XIP to (I believe) its right places and the ROM was successfully built.
Still, after flashing all is stuck on the first image screen.
Can someone advise what am I doing wrong?
giorgina351 said:
I am struggling my way through the cooking lessons...
I already succeeded using evrius kitchen for dumping a stock rom and than rebuild it (thanks twopumpchump).
In my next "lesson" I am trying to upgrade WM build (a small step - 21887 to 21895 - I use the one from Energy post). I copied SYS / XIP to (I believe) its right places and the ROM was successfully built.
Still, after flashing all is stuck on the first image screen.
Can someone advise what am I doing wrong?
Click to expand...
Click to collapse
to change builds, all you need from the new one is sys and msxipkernel...the rest come from your device dump. so if you have 21887 now, you can change the build number on rom/rhodium from 21887 to 21895. then go to rom/shared and change the build number from 21887 to 21895 and also change out the msxipkernel with new one. add 21895 sys, choose them in ervius kitchen at top and build your rom
ps...here is 21896, already setup for rhodium 2.07...all you have to do is copy and paste
http://m-s-j.net/tpckitchen/rhodium/21896_WVGA_Rhodium_Kitchen_Plugin.7z
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.