How To's For Developing Q & A

[dereknjenny04]

OMJ,
I found a thread over on XDA where Bepe describes how the version is determined.

It is the {guid}.DSM file in the \SYS\OS directory. You can use his pkgtool to view the OS Version.

[OMJ]

Originally Posted by colonel

rmactivate.exe

This is assuming that your SYS is virgin and intact.


always helps to ask others.

thanks colonel!

Originally Posted by jakdillard

My take on all this ...... I have really never like to port xip or sys . Whenever I do a rom I like to use an "official" or "original" build ..... the only reason I've done any porting here lately was for wm6.1 ... in the past when I was making titan roms I tried getting into all of this and what happened was that when I brought over a xip or sys I also brought over the problems .......

The tutorials I wrote were just the quick way that I found to do this.......... the old way is very .... well sometimes it can be time consuming

Yeah, I figured that would be the only reason.....for an upgraded OS. It sounds like when we do get a new official ROM, that it will still be 6.0. One thing that stuck in my head, is a question you asked in your challenge to chefs...... "If a new official rom was released tonight would you guys be able to clean it out yourself or would you have to wait until someone doe's it for you". Well, your tut on porting should serve much value when the new official is released....Thank you!!

Originally Posted by dereknjenny04

OMJ,
I found a thread over on XDA where Bepe describes how the version is determined.

It is the {guid}.DSM file in the \SYS\OS directory. You can use his pkgtool to view the OS Version.

cool...thanks, I'll try to find it.

[plckc]

First, Thank You all (you who post tutorials, make kitchens, strip ROMs, and the like).
Secondly I was wondering if it's possible to get WM6.1 and put it into a WM6 phone. What I want to do is keep most of my Alltel stuff and just put 6.1 on it. I am a total n00b to all this but so far I have been able to follow all the tutorials and make my own stuff. My biggest things are I want to keep my mms capabilities and keep the mp3 trimmer that comes with Alltel's touch. I was thinking the porting was going to be the answer but now you guys are talking about the XIP and now I'm totally confused. I work for an Alltel Agent and they frown upon the Sprint stuff that comes with most of the ROMs and I have to be able to show customers the basics of the Alltel version of the phone.
I have less than an hour a day to play with this and it really sucks cause I would really love to spend a couple days just figuring this stuff out. I appreciate any guidance as to how to accomplish anything.
Thanks
PC

[jakdillard]

Originally Posted by plckc

First, Thank You all (you who post tutorials, make kitchens, strip ROMs, and the like).
Secondly I was wondering if it's possible to get WM6.1 and put it into a WM6 phone. What I want to do is keep most of my Alltel stuff and just put 6.1 on it. I am a total n00b to all this but so far I have been able to follow all the tutorials and make my own stuff. My biggest things are I want to keep my mms capabilities and keep the mp3 trimmer that comes with Alltel's touch. I was thinking the porting was going to be the answer but now you guys are talking about the XIP and now I'm totally confused. I work for an Alltel Agent and they frown upon the Sprint stuff that comes with most of the ROMs and I have to be able to show customers the basics of the Alltel version of the phone.
I have less than an hour a day to play with this and it really sucks cause I would really love to spend a couple days just figuring this stuff out. I appreciate any guidance as to how to accomplish anything.
Thanks
PC

follow the porting sys tutorial then once you get your hands dirty worry about xip

[plckc]

Originally Posted by jakdillard

follow the porting sys tutorial then once you get your hands dirty worry about xip

I have been playing around with the porting. I actually have done all the tutorials. I am in the process now of playing and seeing what happens. I really just want to know am I wasting my time trying to mix ROMs. Or more specifically can I extract just the OS (WM6.1) and just replace the existing OS while leaving the core functionality of the phone. Thanks for your timely response.
PC

Edit: I did it! Thanks everyone, (I feel like I just won an oscar) there are so many people to thank but I definitely want to thank OMJ, No2Chem and CoKeman for they are the ones that I took/used their work. I Ported the sys and than copied over the ROM folder and now I have what looks like a stock Alltel Touch but with WM6.1. I plan on doing some more modifications but I will post what I have tomorrow after work. Thanks Again to all the true Chefs (I hope to be one soon.)

[monsterfly]

I successfully ported SYS, thanks to tutorial...
Now I am wondering how to port XIP?

[boggsie]

This might sound rediculous, but what if ...

I didn't want to mix and match between SYS and XIP ...

I only wanted to separate the OEMs out of the default Sprint OEM ROM ... and maybe create OEM folders for each of the components, so that when BuildOS.exe fired up, each of the OEM componenets (dialer, touchflo, biotouch, skins, etc.) were separately selectable via check-boxes ...

I have the Sprint OEM RUU_signed.nbh (OS Only) decomposed into the vogue_kitchen_tools directory structure.

Now I have OEMAPPS with about 350 items and a single *.rgu file with >3200 lines of registry entries.

Is the process as painstaking and manually sifting through the *.rgu file and moving files to their separate application folder, along with a new *.rgu file with the necessary registry entries?

[dereknjenny04]

Originally Posted by boggsie

This might sound rediculous, but what if ...

I didn't want to mix and match between SYS and XIP ...

I only wanted to separate the OEMs out of the default Sprint OEM ROM ... and maybe create OEM folders for each of the components, so that when BuildOS.exe fired up, each of the OEM componenets (dialer, touchflo, biotouch, skins, etc.) were separately selectable via check-boxes ...

I have the Sprint OEM RUU_signed.nbh (OS Only) decomposed into the vogue_kitchen_tools directory structure.

Now I have OEMAPPS with about 350 items and a single *.rgu file with >3200 lines of registry entries.

Is the process as painstaking and manually sifting through the *.rgu file and moving files to their separate application folder, along with a new *.rgu file with the necessary registry entries?

That is exactly what I did on my v17 release.

Commented out the registry entries from components as I moved from OEMAPPS/OEMDRIVERS/OEM_Lang to OEMS and made a new .RGU file in the OEM with the appropriate keys.

[OMJ]

Originally Posted by dereknjenny04

That is exactly what I did on my v17 release.

Commented out the registry entries from components as I moved from OEMAPPS/OEMDRIVERS/OEM_Lang to OEMS and made a new .RGU file in the OEM with the appropriate keys.

very nice Derek....I'm guessing this is a very time consuming task! but this is exactly what needs to be done for the ppckitchen.

[boggsie]

Originally Posted by dereknjenny04

That is exactly what I did on my v17 release.

Commented out the registry entries from components as I moved from OEMAPPS/OEMDRIVERS/OEM_Lang to OEMS and made a new .RGU file in the OEM with the appropriate keys.

Whoa ... on my way to your thread!