Related
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
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Thanks hope udK will use this version in R5 release
I wonder which is the difference between this and 20931 build
Sorry to ask, How to add wince.nls manually
suaaa said:
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Click to expand...
Click to collapse
Wow! but where is the \SYS ?
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
chavonbravo said:
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
Click to expand...
Click to collapse
Isn't real or?
The experts out there...
Does it make sense to mix most recent XIP (like this one) with older SYS
e.g. 19965.1.2.3 because of the lack of native (german) translated newer SYS?
I mean, can you have overall (speed) gain from newer XIP though you use it
with an older SYS?
I really would appreciate an experts reply on this
Olioaglio
Seems, the SYS 21109 is again chinese hex magic according to:
http://forum.xda-developers.com/showthread.php?p=3104209#post3104209
Hmn, AKU 5.0 or 5000 instead of 1.5.0 or 1500 ?!? seems a fake
WOndering, if XIP is also hex edited or real...
Olioaglio
Nice!!
so its fake or not???
where can i get sys / xip for polaris???? the lastest release
Post 1: The Basics
* Ervius Visual Kitchen - THANKS Ervius
* Using and Installing EVK a Pictorial - THANKS + Que PPC
* Tutorial - Sous-Chef's Guide - THANKS hilaireg
Post 2: Documents
* [GUIDE] 49 Universal Tutorials for Customizing any Device and Cooking- mrmakk
* Hermes Cookbook - THANKS to sambartle
* My Way of cooking - THANKS to Anichillus
* How to ADD/REMOVE programs -THANKS to mfrazzz
* How To Manually Make your own OEM Package from a .cab - THANKS to Noonski
* How to change the PagePool before flashing
* Replace Graphics in Exe Files and DLL's
* [TUT] Manual Full XIP Porting - THANKS to Ababrekar
* Home to Various Guides (HTC Tutorials) - THANKS to Ababrekar
Post 3: Kitchen, ROM, OEM and SYS
Basic components
1. Visual Kitchen thread by Ervius
2. If you want to choose your own base rom to extract (e.g. if you want to cook in another language) get your rom here (THANKS l3v5y).
3. WinCE CAB Manager to create your service packs.
4. CeRegEditor to edit the hives.
OEM package repository kwbr
* An example to store all your registry tweaks
More OEM packages
* Raphael OEM Package Repository - THANKS to aruppenthal
* {FOR COOKS ONLY } OEM Packages - THANKS to Ather
Advanced tooling
* IDA Pro Disassembler and Debugger
* Itsme tools and info - Willem's klaphek
Special thanks
Ervius - for Visual Kitchen and packages creator
Noonski - for support and the Elfin cooking class
Dutty - for his NBH Tool
udK - for CustomRUU
dark simpson - for htc rom tool
kwbr - for sharing his Thread with me
bepe, cmonex, itsme, mamaich, oli, pof, tadzio, theblasphemer, the-equinoxe, Anichillus, ayyu3m, r0p3, Ababrekar, Kokotas, htctouchp, and all the others on xda for the wonderful tools and tutorials.
kitchens
Look here *for the last Ervius.build kitchen - Thanks Ervius
Look here *for the last Vistang build kitchen - Thanks Vistang
Look here *for the last OndraSter build kitchen - Thanks OndraSter
Kitchen PASSWORD = sparkienl
WWE_WVGA_Huashan_EXT_OEMS.7z Read the .txt file
LEO_2.11_External_Packages Leo_1_5_TMOUS_2.11.531.T1_EXT_PACKS
LEO_2.09_External_Packages
New Manila _____ Ext packs with Telstra Manila_Core_2_5_20121431_1
New Topaz 2.53 packs _____ Topaz packs out 2.53 different than 2.54
New Manila _____ Ext packs with Manila_Core_2_5_20113030_0
All_New SYS_16 _____ New Sys 22013/21651
OS Kitchen 24011 ____ OSKitchen SYS 24011 base 2.11 updated with Huashan Ext packs
OS Kitchen 23547 ____ OSKitchen SYS 23547 (BETA removed) Multi Quicklinks
OS Kitchen 23545 ____ RapidShare OSKitchen SYS 23545 base 2.10 BETA removed
OS Kitchen 23632 ____ RapidShare OSKitchen SYS 23632 base 2.10
OS Kitchen 23540 ____ MegaUpload OSKitchen SYS 23540 base 2.10
Ervius kitchen 21892 Dumped 2.07 test rom updated with SYS 21892
OS Kitchen 21892 ____ OSKtchen with SYS 21892 and Manila_Core_2_5_20121225_0
DIY kitchen SYS 24001 _____ DIY kitchen SYS 24001 Manila_Core_2_5_20113030_0
Ervius kitchen 23518 _____ updated with the packs from 166
Ervius kitchen 28205 _____ sys 28205 oem 1.48 ext 2.02
I don't need donations
Great to see the new format with all the information for new users.
Thank's Bob,
This setup is with parts from the thread of kwbr as you can see, it's ok by him.
bobsbbq said:
Great to see the new format with all the information for new users.
Click to expand...
Click to collapse
This looks very cool, thanks guys.
I will try to contribute as well whenever possible.
Grtz Leo
@Laurentius26,
Thank's Leo, we do our best to help the new rom builders
Yeah great, visual kitchens are nice but I've learned everything by hand without a visual kitchen and I still do.
I always followed Bepe and Mamaich because they created most of the tools we are using today in our kitchen.
Offcourse there are many more people but they are my big examples.
An example to dump a rom by hand, the tools you find in most visual kitchens today:
Open a CMD window in the directory with this tools and your Ruu_signed.nbh and type te following commands:
nbhextract ruu_signed.nbh [ENTER]
nbsplit -kaiser os.nb [ENTER]
imgfsfromnb os.nb.payload imgfs.bin [ENTER]
imgfstodump imgfs.bin [ENTER]
Dump created....
Now drag the dump folder on Bepe's packagebuider and your packages are created.
There's so much to read about it, here's a old thread from Mamaich,
offcourse the tools are much more improved today thanks to these great guys.
http://forum.xda-developers.com/showthread.php?t=249836
I show you this and you probably know to but it's good to know these tools if you start cooking I think.
Now I will let you guys do your job but feel free to ask if you need any help.
Cheers, leo
Hi Laurentius26,
I use a by me changed version from this guys (JugglerLKR and JCEspi2005) for dumping of a signed rom, now I get at least SPL, Radio and so on out of it.
*removed due to my oversight*
Leo-1.66 ext packages in 4th post
base 1.66
Hello sparkien and Thanks for you help . I try to build my rom with the 1.66 base but after boot run CC kepp running do you know wy , and sory for my english i'm french .
mouss57 said:
Hello sparkien and Thanks for you help . I try to build my rom with the 1.66 base but after boot run CC kepp running do you know wy , and sory for my english i'm french .
Click to expand...
Click to collapse
check your txt files in OEM.
I don't understand what did you change, your tools?
sparkienl said:
Hi Laurentius26,
I use a by me changed version from this guys (JugglerLKR and JCEspi2005) for dumping of a signed rom, now I get at least SPL, Radio and so on out of it.
Click to expand...
Click to collapse
Laurentius26 said:
Yeah great, visual kitchens are nice but I've learned everything by hand without a visual kitchen and I still do.
I always followed Bepe and Mamaich because they created most of the tools we are using today in our kitchen.
Offcourse there are many more people but they are my big examples.
An example to dump a rom by hand, the tools you find in most visual kitchens today:
Open a CMD window in the directory with this tools and your Ruu_signed.nbh and type te following commands:
nbhextract ruu_signed.nbh [ENTER]
nbsplit -kaiser os.nb [ENTER]
imgfsfromnb os.nb.payload imgfs.bin [ENTER]
imgfstodump imgfs.bin [ENTER]
Dump created....
................................
Click to expand...
Click to collapse
bepe xidump make these steps with only one command
Indeed that could be thrue but for a newbie these steps are good to know because you can do everything with pushing one button.
Essential is that you know what the kitchen (visual) is doing to my opinion.
jojordy said:
bepe xidump make these steps with only one command
Click to expand...
Click to collapse
Hi Laurentius26,
As you can see I use more than one kitchen to build, basicly they all use the same tools.
Laurentius26 said:
I don't understand what did you change, your tools?
Click to expand...
Click to collapse
There are a lot of stockage website WHY USING RAPIDSHARE??????????
It's impossible to download something with that ****!!!
sparkienl said:
Look here *for the last Ervius.build kitchen - Thanks Ervius
Look here *for the last Vistang build kitchen - Thanks Vistang
Look here *for the last OndraSter build kitchen - Thanks OndraSter
download the kitchens from the following url adres:
Kitchen PASSWORD = sparkienl
LEO_1.66_External_Packages
Ervius kitchen 23518 _____ updated with the packs from 166
Vistang kitchen 21889 _____ updated Sys 21889 1 time boot problem solved
Vistang kitchen 21888 _____ updated Sys 21888
Vistang kitchen 23518 _____ the config_AP.txt error removed
Ervius kitchen 23518 _____ update sys 23518, oem 1.61, ext 2.02 and in tools imfgsfromdump turbo
Ervius kitchen 28205 _____ sys 28205 oem 1.48 ext 2.02
Click to expand...
Click to collapse
bowow said:
There are a lot of stockage website WHY USING RAPIDSHARE??????????
It's impossible to download something with that ****!!!
Click to expand...
Click to collapse
Not with a premium account But i agree, RS is not so great..
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
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.