Does anyone know a good tutorial (thread) for XIP porting
Thnx in advanced
Looking for the same. Anyone please? I'm sure I'll serve the community with new ROMs if I learn..
Regards,
Carty..
If you want there is one in italian:
http://www.a1kstyle.com/ptopic17150.html&highlight=xipport
That's the same incomplete version which is similar to Garmin' English version at Atom' Section. Looking for a more detailed one. Found something in Polish at http://mobione.pl/index.php?page=porting_ROM but seems there is no online translators for polish
Anyway, as far as Ive struggled, I understood that you strip coredll from one xip, use mreloc to change v and d base, paste coredll to the xip of other device and build it. Is that it required for building a new OS? I mean, does the new OS build solely depend on coredll? Then what kind of improvements will it have?
Thanks for helping.
Regards,
Carty..
Afther patch coredll.dll yopu have to change all the SYS folder (obtained with package tool) with the newest one.
I rip a ROM and get lot of folders such as the extra packages the previous cook added. I presume those files aren't needed but the rest of the common folders such as phone,os,baseapps and so on? What about the .ROM and .VM folder? Should they also be replaced?
What do they(.ROM and .VM) folder exactly do? They just seem to have some address information inside.
Regards,
Carty..
http://forum.xda-developers.com/showthread.php?t=331094
Isn't it preferrable to move over all of msxipkernel?
Yes I looked at the G'Loc thing before but no instructions on how to use it
Regards,
Carty..
Related
Hi All
I see now we are getting quite a few custom ROM's from the likes of bepe, panosha and other.
Great Work Guys.
But i would also like to be able to build or a least edit a ROM to exactly meet my requirement. Like adding or removing certain CAB files and making reg edits.
Have been reading a lot of other threads on the site put none seem to deal directly with the Polaris.
So i was hoping some of you great cooks (grovel grovel grovel) would wight a description on how to take a nbh file and extract and edit the different nb parts and then rebuild back to a nbh file ready for flashing.
Thanks
polaris kitchen
sorry......wrong answer
I'd love that too! I want to mod an existing ROM and make it specific to my needs.
Will anyone be so kind and post a short guide how to do this? And make the topic sticky!
First, you can start with Kaiser's Kitchen...and at last, use Dark Simpson tool (htc room tool) to make nbh file (config add Polaris device in tool config)
Cheers,
ouioui
Good place to start is here http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
Yep , good one, but everything is based on Kaiser.
I don't have a Polaris Radio, neither does the HTC Rom Tool allow to cook Polaris Rom's.
Any other ideas ? Or could someone help ?
Thanks a lot in advance
The Kaiser kitchen works fine and all you need to do with the Dark Simpson ROM tool is change the Model ID from KAIS***** to POLA*****
As always read the threads before you start cooking and make sure you have Hard SPL!!
Thanks
I've been reading all night ;-)
In the HTC Rom tool there is no Polar***** , strange, although I thought I downloaded the newest ini. I've read in another thread that I could use the Kaiser one as it was basically the same device, is that so ?
Other question though:
Talking about Hard-SPL- I've Hard-SPL'd mine , but do I need to include that one in the rom as well ? Like while using the HTC Rom Tool , in the SPL section ???
Second question, where can I find the radio.....nb ?
Thanks for your help, I appreciate that.
As I said set the ROM tool to Kaiser then change the Model ID to POLA***** and use as normal to create the nbh image.
As for Hard SPL... once you´ve flashed it that´s that, no need to flash it every time you change ROMs or radio...
id love to see the guide for polaris aswell.
and oem packages as well.
i did everything as it was sowen in kaiser guide, but i got an error on building system. have no idea why..
was saying that something is missing or path is icorrect smth like that
post here exact errr.U got.
here is htcrt.ini for polaris (only Polaris Option is active) simply rewrite htcrt.ini in folder with htcrt.EXE
It's not necessary to include Radio ROM when building? Right?
nope, its up 2 U what 2 include (SPL/Radio/OS/Splash)
phsnake said:
post here exact errr.U got.
here is htcrt.ini for polaris (only Polaris Option is active) simply rewrite htcrt.ini in folder with htcrt.EXE
Click to expand...
Click to collapse
Thanks for the guidance. The tutorial is great but fails to mention specifics if you are not cooking a Kaiser Rom. For example, does the baserom have to come from a shipped Rom? I was using the 3.02 Kaiser Rom as my baserom. Can you do that when cooking a Polaris rom? How do I get the RUU_signed.nbh out of any other Rom. I thought about using the WM6.1 19716 Rom but couldn't extract anything. (Probably stupid questions but cant find answers in the wiki). BTW, I was getting same errors about half-way through compiling process. If I try again today, I will record the errors and post. Again, thx for help.
sgreenwood99M me i have 19716 WM6.1 for cooking. U can Use some part of any ROM but U have to be sure exactly what. In general U can Use OEMpackages freely, but be aware with drivers, baseapps....(i have perfect CZECH 19199 WM6.1 but w/o working SMS)
Hi,
i've read through the Kaiser kitchen guide and it all seems to make sense however i'm not sure how much is relavent to the Polaris, for example the ingredients section talks about expanding the radio file and the rom files to folders, from the Kaiser files on rapidshare etc.
Do us Polaris users do these points too? or are there specific Polaris Radio and ROM files we use?
I have my base ROM file called RUU_signed.nbh and i've also managed to use pdocread to get the RAW files too, but just not sure where to go now?
All i want to do is remove a few cabs and add a few cabs and EXEs to my rom.
can anyone post comments on exactly which parts of the Kaiser kitchen guide need to be changed to use on a Polaris?
thanks.
dont need raw's. simply put *.NBH(polaris) to BaseRom folder. Run begin.cmd(or bat?) Choose option 1.
click......... then start cook.cmd(or bat)
Do we replace the KaiserCustomRUU and the BuildOS files with ones specific to Polaris? Thanks.
yes, take udK CustomRUU & replace kaiser one, u dont need to replace anything else(except htcrt.ini ||KAIS**** replace with POLA***). And of course Polaris' *nbh
Whenever I put a Polaris nbh in the BaseRom folder, the process gives me an error that it cannot find RUU_signed.nbh.
OK, even mods need guidance on using the search function. Is there a comprehensive ROM porting tutorial out there which uses the latest tools? I've seen some for the Atom as well as the Trinity and Kaiser, but I'm working on porting a ROM for my Wizard, and I'm getting nowhere when it comes to the XIP section. It would take a full day to write down what all I've tried, so I'll try to give the short version and ask for help from there.
Anon. said:
Now, are you looking to port only the core OS? If so, it's fairly easy. The hardest part is the work to the XIP. Porting the XIP will require that you use RomMaster to extract the XIP.bin of the source ROM and the destination ROM, and then use XIPPORT to dump the XIP of both, then click "Write Maps" on both. Use the Make Packages button to separate the XIP into its packages, and in both the Files and Modules of the dump, replace MSXIPKERNEL of the destination with the source. Then use M'Reloc.exe to relocate the modules to the same as the original (if they differ) and also manually make the same changes to imageinfo.txt of each module. Click Undo to take the files out of packages, and Realloc P. If all goes well, there will be no errors. Look in Map.txt and see if there are no !!!!!.
Click to expand...
Click to collapse
When I do this using the CE OS 5.2.308 (Build 15342) as the donor ROM and CE OS 5.2.1413 (Build 17745) as the new ROM, I'm getting !!!!! due to a strange address issue with hd.dll in that m'reloc reports that the physical address is wrong and will not relocate the module. I dumped both xip.bin's using 0x00310000 as the address so this may be wrong but right now I'm pretty lost.
I hope this isn't gibberish. Any help is welcome.
OM
I have been looking for a tutorial on Rom porting..could you please list the Tools required and where is the whole Tutorial
jwzg said:
OK, even mods need guidance on using the search function. Is there a comprehensive ROM porting tutorial out there which uses the latest tools? I've seen some for the Atom as well as the Trinity and Kaiser, but I'm working on porting a ROM for my Wizard, and I'm getting nowhere when it comes to the XIP section. It would take a full day to write down what all I've tried, so I'll try to give the short version and ask for help from there.
When I do this using the CE OS 5.2.308 (Build 15342) as the donor ROM and CE OS 5.2.1413 (Build 17745) as the new ROM, I'm getting !!!!! due to a strange address issue with hd.dll in that m'reloc reports that the physical address is wrong and will not relocate the module. I dumped both xip.bin's using 0x00310000 as the address so this may be wrong but right now I'm pretty lost.
I hope this isn't gibberish. Any help is welcome.
Click to expand...
Click to collapse
If you can translate from polish - there are:
http://www.mobione.pl/index.php?page=porting_ROM_porting
http://forum.mobione.pl/index.php/topic,3319.0.html
I don't read Polish. Anyway, my test device was dropped today, and I may have to put my only good one on the line.
I have searched a lot everywhere but couldn't find any good kitchen for Omnia II or Omnia pro b7610. On every forum there are numerous threads asking for custom roms but nobody is willing to share, so it is our request to all senior chefs to kindly make one good kitchen for us so that we can cook our own roms instead of begging here or there.
Please provide us a good illustrated tutorial for the same, what tools are required, can we use any of the kitchen already available here or can somebody please modify any of it to make it compatible with Omnia Pro b7610. Also if we want to add manila 2.5 to the rom, what we have to do, as b7610 is wvga device, can rhodium manila can be used directly without porting or do we have to make some changes to make it work.
I can help in any way possible but we need somebody senior who can get us started.
Hoping for the best
Regards,
Inder
Ask somebody who knows how to use OSBuilder to adapt it to your phone: with a few batch files it should work perfectly.
anybody, Please, who can make b7610 omnia pro compatible OSBuilder and we also need a tutorial for the same
Airxtreme,,,,,please help us.........I know you can
airxtreme said:
Ask somebody who knows how to use OSBuilder to adapt it to your phone: with a few batch files it should work perfectly.
Click to expand...
Click to collapse
Please modify that for us and make it ready to go for our device........and help us understand what all is required and how to do it from scratch.
Need help ....!
Regards,
Inder
inderbrar said:
Please modify that for us and make it ready to go for our device........and help us understand what all is required and how to do it from scratch.
Need help ....!
Regards,
Inder
Click to expand...
Click to collapse
Sorry but that requires way too much work because it's not just the kitchen but it's reconstructing the original ROM that is a mess because as you probably know that phone has a multilanguage ROM that requires additional work to get working (dumping the fat, extracting all the multilanguage archives, unpacking the archives and putting back all the missing SYS and localized OEM packages, etc.).
For the kitchen I can tell you from what I remember that the final flash ROM format for that phone is NB0, a template NB0 can be obtained by using o2tool -mst_to_nb0 on the original MST file. To convert the nb0 to NB (that OSBuilder can work with) o2tool -nb0split must be used (and all the files created must be kept as copy for building), then in the OSBuilder build cmd file you insert the new partitions with osnbtool -c in the old NB file and run o2tool -nb0build to obtain the final NB0 file.
thanks airxtreme for the start....lets hope somebody else is willing to do it, no multilanguage rom is required, English only will do just fine. Till then I can start experimenting with OSBuilder
inderbrar said:
thanks airxtreme for the start....lets hope somebody else is willing to do it, no multilanguage rom is required, English only will do just fine. Till then I can start experimenting with OSBuilder
Click to expand...
Click to collapse
The multilanguage partition includes everything, even english so you can't have any working ROM if you don't get those files out.
Have you looked at:
This Link
Yeah been there, infact regularly checking any updated info regarding this particular device. Thanks mach2003 for providing the link, lot of good info there.
Ok, I came to the point where I would like to see if it's possible to cook my own rom. There is, however, so much (cluttered) information around the forum and I just have no idea where to start. I did figure some stuff out, but with everything I find out I also get more questions. I hope I'm allowed to ask these here.
Windows Mobile / Sense:
I am planning to begin flashing a rom only for my phone: Rhodium / Touch Pro 2. I just don't realy get how I can get the latest version of windows mobile (the on with the start menu at the top left) and sense (2.5.2015 ?). The stock roms I can find for Rhodium contain older versions.
Kitchens:
There are quite some kitchens out there, even those that do a lot of work for you. To understand everything, however, I would rather get a kitchen with only the essential tools. This way I am hoping to understand what steps are needed for the cooking. What kitchen would be recommended for this?
Terms
There are lots of terms around, but for some of them I can't figure out what exactly they are.
- XIP
- SYS
- OEM
Thanks!
~Sph
For WM, you should find the newest version of COM2 build, which is Build 21905 at this moment. It seems that not mentioned in XDA, but you could Google for that.
I think you should be able to use these essential tools, often refer as "old style" kitchen
ImgfsFromDump
xidump (ImgfsToDump) and DMP2PKG
osnbtool
BuildOS
EXTReloc
XIPPort
maybe there are more tools when you need to repack back to nbh format
For Terms, you should read Da_G's post here
http://forum.xda-developers.com/showthread.php?t=544445
I will tell you this....
read the tutorials... check the main stickie
read eve you dont understand nothing... then when you want to start trying things, you can ask.. with some knowledge.. the lates kitchen to date is Oskitchen by airxtreme and osbuilder.. i guess
Not to be mean but like +Que PPC said READ FIRST you should have look for information first and found this answers by your self ... Now about the systems and xip ext, sys, modules, cabs and all other stuff like that you will learn them when you start working on a kitchen.
About the kitchens there are various kitchens it just deppends which one you want to choose, all the kitchens will help you create your rom and customise it, and also one recomendation and requirement that you should have in order to create your own rom and that is patience and time, because you will need to look for alot of info and also looking for fixes and customisation and all of that.
Here is another kitchen that I recomended thanks to +Que PPC with the tutorial with videos in english made by me.
HTML:
http://forum.xda-developers.com/showthread.php?t=669535
PS. Search & read first
XIP = eXicuteInPlace -- it's the core of the entire OS. Without it you got nothing.
XIP is made up of 2 main parts:
oemxipkernel - device specific
msxipkernel - build specific to SYS version
SYS is basically all the microsoft files
OEM is basically all the device specific files, and nonMS applications
If you have a CDMA Touch Pro 2, I have a kitchen here all set up for you:
http://www.mobileunderground.info/showthread.php?t=12797
If you have GSM, you will need to change out some components of the kitchen, specifically xip and oemdrivers, plus a few other things.
Hi,
this my first time about cooking a rom and I gooogled a lot but I can't find any info about cooking rom for this device.
The only information is in this old thread: http://forum.xda-developers.com/showthread.php?t=294165
and a wm6 port here: http://forum.xda-developers.com/showthread.php?t=320686
following this post: http://forum.xda-developers.com/showpost.php?p=2729160&postcount=16 I succesfully "converted" the nbf to nb.os
The nb.os with xidump is correctly(?) dumped in two folders, XIP and IMGFS
I'd like update WM to a newer release and include/remove some apps.
Can someone help me?
Thanks,
Michele
SystemR89 said:
Hi,
this my first time about cooking a rom and I gooogled a lot but I can't find any info about cooking rom for this device.
The only information is in this old thread: http://forum.xda-developers.com/showthread.php?t=294165
and a wm6 port here: http://forum.xda-developers.com/showthread.php?t=320686
following this post: http://forum.xda-developers.com/showpost.php?p=2729160&postcount=16 I succesfully "converted" the nbf to nb.os
The nb.os with xidump is correctly(?) dumped in two folders, XIP and IMGFS
I'd like update WM to a newer release and include/remove some apps.
Can someone help me?
Thanks,
Michele
Click to expand...
Click to collapse
osKitchen can take and rebuild the NB of that phone with probably no issues but you need to figure out the rest by yourself since the older the phone is the more likely it has drivers that will break with wm6.5.
Uhmm..thats interesting,could you explain how make this?
I have an old PocketLoox 720 with .nbf and it can run with no problem WM 6.1.
I know how to use OsKitchen but where i need to put the Os.nb converted?
Other issue will be the NBH output , of course ill need nbf for flash the PDA.
airxtreme said:
osKitchen can take and rebuild the NB of that phone with probably no issues but you need to figure out the rest by yourself since the older the phone is the more likely it has drivers that will break with wm6.5.
Click to expand...
Click to collapse