[Walkthrough] How to Port a ROM [XIP and SYS]

[ivanmmj]

Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.


How to port a XIP:

Extract xip.bin from the build you want to port from
Download Bepe's XIPPort (http://forum.xda-developers.com/attachment.php?attachmentid=83701&stc=1&d=1209368244)
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)


Source (http://forum.xda-developers.com/showthread.php?t=388666)


How to port a SYS folder

Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell

Source (http://forum.xda-developers.com/showpost.php?p=1557525&postcount=61)


Q&A

Q: What is the XIP?
A: It's the kernel of the ROM.

Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.

Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS (http://forum.xda-developers.com/showthread.php?t=345411) thread on how to unbrick your phone. Secondly, refer to Q&A #4.

Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven (http://forum.xda-developers.com/showthread.php?p=2139575#post2139575) and the process will be automated.

Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.

[ginolin]

well done ,thanks.
:)

[N3xt2N0N3]

ivan i love you...lol just kidding silly goose but thanks a million

[le_hades]

Ivan:

Can XIP or SYS folders be ported over different language ROMS?

Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?

I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)

Thanks.

[ivanmmj]

Ivan:

Can XIP or SYS folders be ported over different language ROMS?

Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?

I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)

Thanks.

You'd have to go through every file in the OEM folder and find every misdirected link (because of the different language) as well as replace every MUI. So in short, no it's not possible unless you have a LOT of time and want to work really hard. What I would do is just use any of the readily available Spanish Herald ROMs to obtain your OEM files.

[itje]

mm this is a "fast" and dirty way:
If you use in.ex a 19199 build (0409 wwe)
you need to extract all mui files from 04xx (your langauge from another build, if you use wm6.1 you need to use mui from another wm6.1 build)
rename them from 04xx to 0409, replace all in you 19199 build with the new renamed ones

this can be done both in OEM and SYS

[le_hades]

The thing is that i'd like to make a herald spanish 6.1 ROM but I can't find none to port on kaiser forums etc, so i was thinkong about alternatives

[ttran001]

Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.


How to port a XIP:

Extract xip.bin from the build you want to port from
Download Bepe's XIPPort (http://forum.xda-developers.com/attachment.php?attachmentid=83701&stc=1&d=1209368244)
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)


Source (http://forum.xda-developers.com/showthread.php?t=388666)


How to port a SYS folder

Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell

Source (http://forum.xda-developers.com/showpost.php?p=1557525&postcount=61)


Q&A

Q: What is the XIP?
A: It's the kernel of the ROM.

Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.

Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS (http://forum.xda-developers.com/showthread.php?t=345411) thread on how to unbrick your phone. Secondly, refer to Q&A #4.

Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven (http://forum.xda-developers.com/showthread.php?p=2139575#post2139575) and the process will be automated.

Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.



Great job bro,

[N3xt2N0N3]

ivan you rock!!

I learn so much from reading your threads.

I think im almost ready to cook a rom.

I was wondering if you could be my mentor??

[homer285]

It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 5.2.1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.

[ivanmmj]

It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.

You ported the XIP AND the SYS folder?

[homer285]

Thanks for your reply, yes I did.

[ivanmmj]

Thanks for your reply, yes I did.

Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?

[homer285]

Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?yes Im using the Diskimage_Ver.nb0 from Atom in Rom folder, tried by hand and EasyPortOven same result, only build is porting not CE OS info. Perhaps I need a new XIP to try, anyway thanks for this great tool it really makes porting easy, seriously.

Edit: So the trick for me was the Atom needed porting directly, all modules must have address changed and then ported to diskimage_Ver via XIPPORT, drop into Kitchen/ROM folder along with everything mentioned here :D.

[mbarvian]

can anyone confirm if this works for the kaiser, and if it doesn't, what to use for the kaiser?

thanks in advance

[Noonski]

I've heard that Keeping your original Device MetaData hive files isn't that important as the Hive Files get created.

But just to be on the Sure side.

When you put the Hive files from MetaData folder into the New Build from the Ported Sys.

Won't that make hive files with unneeded Reg entries?

instead of sticking with your original device Hive Files?

[johnpatcher]

€dit: Wrong thread, sorry!

[rajathvsm]

What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?

So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?

BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.

I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.

[ivanmmj]

What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?

So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?

BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.

I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
Things have changed a lot since I wrote this... but:
The drivers are in the OEM folder (as well as most of the device specific stuff.)
You need the OEM, SYS and XIP in order to make ANY ROM.
You can move your OEM into your SYS but it makes it harder to port newer builds to your ROM later on.
You only need the .VM folder, not the .ROM folder. The kitchen will autoadjust itself.

[+ Que PPC]

I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP

Something about a platform rebuilder + oldschool buildOS hahaha

Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....

I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but

But now everything i install says certificates untrested... i instal sdkcerts and nothing happends

do you think i port the sys or xip wrong?

thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...

wm6.5 build 21812

[ivanmmj]

I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP

Something about a platform rebuilder + oldschool buildOS hahaha

Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....

I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but

But now everything i install says certificates untrested... i instal sdkcerts and nothing happends

do you think i port the sys or xip wrong?

thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...

wm6.5 build 21812
Keep the new wincl if you're using the newer kitchen.
ONLY use the old .VM.
I've been using the visual kitchen based on the same kitchen you're using. (It's a bit more advanced, but it's got a similar layout. So I can help.)

[hh93220]

Can I extract XIP from a cooked rom? or I must get it from a original ROM file.:confused: