How To's For Developing Q & A
 

This thread will be used to answer any question you have about the tutorials found in this thread.

http://forum.ppcgeeks.com/showthread.php?t=20550

Any post(s) not relating to one of the tutorials in the link above will be deleted.

If you want to thank the person who helped you or who originally did the tutorial, please give them http://67.228.199.237/forum.ppcgeeks...ost_thanks.gif !!!

Re: How To's For Developing Q & A
 

JD....I just ported a SYS from a Kaiser ROM, everything went like cake.....is there a way to find the OS version without having to flash, then check the OS in about? That way you could quickly see if it's an older or newer version.

Re: How To's For Developing Q & A
 

The OS Version is set in the XIP, not the SYS. So if you just take the SYS folder, it shouldn't have any bearing on the CE OS Version. It is determined, depending on your setup, by the OS.nb.payload or .NBH file you are using when building the .nbh

However, I am also curious about how to find the OS Version without actually having to port the XIP and install, so hopefully someone can chime in.

Re: How To's For Developing Q & A
 

well I've been using the same donor for each ROM (OEM Sprint WM6.0) and have used 3 different replacement 6.1 Kaiser SYS folders.....all 3 have different versions.

CE OS 5.2.19716 build 19716.1.0.0
CE OS 5.2.19199 build 19199.1.0.0
CE OS 5.2.19716 build 19188.1.0.0

Re: How To's For Developing Q & A
 

Have you changed what is in the ROM folder? i.e. Where the ROM\XIP\boot.rgu resides?

This is generally where the XIP lies. The CE OS Version is set by coredll.

Re: How To's For Developing Q & A
 

no, I only ported over the SYS folder.....following JD's tutorial.


I would also like to know how to determine if a build is older/newer.

Re: How To's For Developing Q & A
 

zzzzzzzzzzzzz....what's the point of this thread, if you're not going to reply, JD?

Re: How To's For Developing Q & A
 

rmactivate.exe

This is assuming that your SYS is virgin and intact.


always helps to ask others.

Re: How To's For Developing Q & A
 

...... hmmm ..... nah never mind

Re: How To's For Developing Q & A
 

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

Re: How To's For Developing Q & A
 

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.

Re: How To's For Developing Q & A
 

thanks colonel!

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!!


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

Re: How To's For Developing Q & A
 

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

Re: How To's For Developing Q & A
 

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

Re: How To's For Developing Q & A
 

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.)

Re: How To's For Developing Q & A
 

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

Re: How To's For Developing Q & A
 

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?

Re: How To's For Developing Q & A
 

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.

Re: How To's For Developing Q & A
 

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.

Re: How To's For Developing Q & A
 

Whoa ... on my way to your thread!

Re: How To's For Developing Q & A
 

Is it possible to use BuildOS without a login? I can't login @ work because of the proxy.

Re: How To's For Developing.
 

Sup everyone,

So regardless of what I tried, I was not able to port any SYS folder from Kaiser (newer build) to my current Vogue Kitchen. Here's what I've done:

1. I used many Sprint WM 6.0 stock ROM (also tried the Alltel Stock ROM and even some Vogue Custom ROMs found in this forum).
2. Decmopiled the stock ROM (aka DONOR ROM right?) and get the OEM, ROM, SYS folder onto a working folder, ran the GReloc tool *without* clicking on the "Do It!" button. Jotted down the numbers in Slot 0, 1 and ROM size.
3. Created another working folder for the Kaiser ROM (WM 6.1 build 19701).
4. Decompiled the Kaiser ROM got my OEM, SYS, and ROM.
5. Moved the original SYS (of stock ROM) to somewhere separate, and copied over the SYS folder of the Kaiser ROM into the kitchen folder where the STOCK ROM is. At this point, I have my original stock ROM kitchen with a new SYS folder from Kaiser ROM.
6. Ran GReloc and numbers showed up different than the first run in step 2 above. Changed the number in slots 0, 1 and ROM size to match with numbers recorded in step 2 earlier. This time I clicked on DO IT button and it said done without any errors.
7. Ran Build OS, and build ROM and flash, and can't get pass the HTC screen. So the tutorial said if it doesn't get pass the HTC screen, copy the WinCE_WLS or some'n like that from the old ROM (stock ROM that is) into the new SYS copied and replaced the folder mentioned above.
8. Rebuilt and Reflashed but no go either.

At this point I'm desperately needing help!! Please give me some pointers.
TIA.

P.S: I also verified the new WM 6.1 build by using PkgTool after runing buildOS and point pkgtool to the Temp\Dump folder that BuildOS created. I did this before running the actual BuildIt.bat script.

Re: How To's For Developing Q & A
 

Vboyz......here's a tip I got from JD.....when running G`reloc the 2nd time, only change slots 0 & 1, don't change the ROM size.....that should do the trick.

Re: How To's For Developing Q & A
 

vboy,

The below 3 folders must be kept as Vogue ROM.
.ROM
.VM
Metadata

Re: How To's For Developing Q & A
 

@OJM - I have mixed result by not replacing the ROM Size on the second run and here are my findings. Tried it for on of the kaiser rom 19701 and didn't boot. Downloaded OJM's 19716 ROM in the forum here and just extract the SYS folder in OJM's ROM and replace it. Boot up just fine. So my theory is that maybe the Kaiser ROM is a custom ROM and not good for porting????? What ROM did you port your 19716 SYS from OJM?

@Arlen - Please elaborate. Do you mean that I have to copy the .ROM, .VM and Metadata folders from my old SYS folder into the new SYS folder?

Re: How To's For Developing Q & A
 

I used 19209 from AT&T leaked Kaiser ROM.

Decompile the Sprint ROM into SYS, OEM, etc.. Folders.

Rename the sys folder to sys-orig.

Decompile the Kaiser ROM into SYS, OEM, etc... in a different directory.

Copy the sys folder from Kaiser into the SYS folder from Sprint

delete the .ROM and .VM folders

copy the .ROM, .VM, WinCENLS folders from SYS-orig into SYS
( I also had to copy some of the Bluetooth Folders from sys-orig for BT to work )

Run G'Reloc and hit "do it" don't change anything.

It will pick up the correct values from the .ROM/.VM folders from SYS.

BTW, if you are getting shady results with this method, make sure you decompile the sprint ROM each time or at least make a copy of the OEM after a decompile. I have seen many times where G'Reloc can screw up the OEM folder if something goes wrong ( i.e. wrong numbers ) and will leave you with a non-bootable ROM.

Hope this helps.

Re: How To's For Developing Q & A
 

Derek,

Thanks for the tips, I will definitely have to try your method.

Re: How To's For Developing Q & A
 

Alrightey then ...

I completed (after a few tries) a straight port of:

SYS from Diamond 5.2.19588

to

Sprint OEM leaked GPS + Rev.A

Flashed back to my device and icons are messed up and the desktop appears to be setup for 640 x 480 (VGA) of the diamond.

So, I completed the port, but the finished product isn't particularly polished ... to say the least.

Is this atypical because of the resolution / video differences between the diamond vs that of the vogue (touch) ?

Best regards,
-boggsie

Re: How To's For Developing Q & A
 

I was wondering if someone could post a step by step for XIP porting, i have been trying but not quit sure that i am doing it right thanks for the help.

Re: How To's For Developing Q & A
 

Anyone care to enlighten a b00n on what needs to be done in order to have a non-VGA port of 19588 working on my touch?

XIP guidance would be delightful, too.

TIA -

Best regards,
-boggsie

Re: How To's For Developing.
 

hi
i ported touch dual rus sys, brightness and device information not worked
can anybody help me with this trouble