PDA

View Full Version : Titan Forever ROM (No M2D)


kclubb
29th April 2009, 08:57 AM
Titan Forever Beta 2 (WM 6.1 Build 21042)

This is a beta, which means there will most likely be bugs. Another note is that this is my first rom compilation I've done. Please post all bugs and the beta release that you are using. Please note the 1st boot will take about 3 minutes to load (the device did not lock) as programs are being installed in the background...

*Sprint Ready
*Advanced Configuration
*Camera 5.0 (Vogue)
*YouTube Player
*WiFiFoFum
*PocketRAR
*iContact
*Google Maps (Latitude)
*HTC Album
*Audio Manager
*Phone Codes
*Network Plugin
*Vibrating Dial Pad
*Microsoft Voice Command

Beta2 Changes
*Removed PIE Plus (caused IE to not work correctly)
*Removed non functional theme

22MB Free RAM on boot

Download: Titan Forever 1.0 Beta 2 (http://tinyurl.com/pdafiles/rom/tf1b2.zip)

---------------------------------------------------------

Known Issues:

---------------------------------------------------------

If anyone knows how to add cabs to BuildOS (not listed in a module) please let me know how to add it so I can add other needed apps

---------------------------------------------------------

Is there a way to extract a ROM w/ all settings as is on a phone back to the pc (after adding cabs and configuring the device)???

kclubb
29th April 2009, 09:01 AM
This is reserved for cab addons until I can integrate them into the rom
-------------------------------------------------------------------
Device Update (http://tinyurl.com/pdafiles/rom/update.exe)
A must have - Copy to any folder on PDA and run it 1 time and tell it to install update and adds to programs menu. This program provides a list of applications you can download from several catigories (Pocket Digital Clock is the clock I use under the "Today" catagory)
Pocket Digital Clock (http://tinyurl.com/pdafiles/rom/pdc.cab)
Quick Menu (http://tinyurl.com/pdafiles/rom/qm.cab)
Music ID (http://tinyurl.com/pdafiles/rom/mid.cab)

Sprint Only
Sprint Picture Mail (http://tinyurl.com/pdafiles/rom/WinPM.cab)
Sprint Navigation (http://tinyurl.com/pdafiles/rom/snav.cab)
Pocket Express (http://tinyurl.com/pdafiles/rom/pe.cab)

kclubb
29th April 2009, 11:31 AM
http://tinyurl.com/pdafiles/rom/ss1.bmphttp://tinyurl.com/pdafiles/rom/ss2.bmphttp://tinyurl.com/pdafiles/rom/ss3.bmphttp://tinyurl.com/pdafiles/rom/ss4.bmp

tssi
29th April 2009, 03:22 PM
Great! I was just looking for something like this without M2D so I could run SPB MS3 on it.

By any chance, could you make it other carrier? or some how allow other carrier to install their own carrier .CAB?

kclubb
29th April 2009, 03:24 PM
Great! I was just looking for something like this without M2D so I could run SPB MS3 on it.

By any chance, could you make it other carrier? or some how allow other carrier to install their own carrier .CAB?

BuildOS doesn't allow for no carrier to be selected so I can't do just a no carrier however I believe you can still install your own carrier cab on top of the on that this puts to give you the right data settings... but don't quote me on that, just my assumption

mattsm
29th April 2009, 03:33 PM
I believe you can still install your own carrier cab on top of the on that this puts to give you the right data settings...

Yes that is correct.

kclubb
29th April 2009, 03:35 PM
Thanks for the verify, just look up DCD Carrier Cabs, they're all around the forums... on another question, I am stuck on getting a SDConfig.txt to hit my rom, I got all other programs but that to work... and of course that prevents the caps in my \windows\ folder from installing :S

Any Ideas

RyanMogul
29th April 2009, 07:06 PM
Here is an example of how to configure UC autorun Config.txt

CAB: \Windows\XXX.CAB
LOCK:Enabled
CAB: \Windows\XXXXX.CAB
LOCK:Disabled
EXEC: \Windows\SDAutoRun.exe

Here is a breakdown on how it executes.

So Replacing the X's with the particular CABs you want to install automatically. In the example above how it would work is while XXX.CAB is installing the device is locked so you cannot interrupt the installation other than soft reset. Then the next thing it does is install XXXXX.CAB and while its installing the device is unlocked so you could go to the start menu, etc.. The last command it runs the EXEC: SDAutoRun.exe command is to RUN CAB's from your Storage Card

You can run as many CAB's as you like but remember it takes time to install them, and also if running them from device memory (windows folder) it basically doubles the space required as the cab will remain there unless you delete them manually or create a script to delete the cabs. You also have to issue a Lock disabled or enabled command for each CAB like above. Then put SDAutoRun.exe at the end like above.

I also believe Using UC autorun also runs the sometimes nasty CAB's hidden in the phones EXT ROM.

Hope this helps you.

BTW: Nice job on your ROM looks good. Also out of curiosity, how does the new PPC Builds work out? Stability, functionality etc..

kclubb
29th April 2009, 09:52 PM
Well, since this is my 1st ROM to make on my own, I had it knocked down to runny pretty good, but like reg tweaks (Pagepool) and customization is a tad of an issue

On another note, I had an SDConfig.txt file and told it to goto windows folder but when the rom was burned it was replaced w/ the default SDConfig.txt from the SDAutorun File

RyanMogul
29th April 2009, 11:09 PM
Well I forgot to mention. I am assuming you are using the PPC Kitchen with all the files still RARed right? I am also assuming that you are using the SD autorun option from the Kitchen right? If thats the case then you can put the CAB's in any folder in the USER OEM folder and the CAB's will be copied to your windows folder. Otherwise you would have to edit the iniflashfiles.txt in the folder you copied CAB's to.

Now if you use the Kitchen UNRARed like me (requires kitchenconfig.txt edits etc..) then you can add/change anything you want without having to RAR it back up. It only makes the process cook a little slower but not a lot slower, and is a lot easier to change/merge new settings and packages.

Here is what you do for your Config.txt issue. If you use the default RARed up kitchen files you must Unrar (extract) the contents of PPC Kitchen OEM.rar and go in there and open the UC sdautorun folder. Now you will see "Config.txt" that is what its called, not sdconfig.txt. Make the changes to that file as described in my last post and save it. Now RAR the entire PPC Kitchen OEM folder so that it is a .rar file. and replace the old kitchen oem.rar with your edited one. Now re-cook.

If its still not working I zipped up an OEM package for you, all you have to do with this is Unzip it and copy the folder to your USER OEM folder in build os. Make your edits to the Config.txt like I explained in my last post. You can also put CABs in this folder, they will be copied to windows folder when cooked. Now make sure you UNCHECK PPC's SD Autorun, and then look in the OEM category and DCD SD Autorun will be in there to select. Now re-cook, you should have the tools needed for the job now.

I also included a Package Creator utility for you. Unzip it and put it anywhere you like on your Computer. Run the packagecreator.exe and then Choose where you want the package to show up in build os etc.. then select the CAB file. It will do its thing and then say "done". The OEM package will be in the same directory or folder as the CAB. You can then cut/paste the package into USER OEM folder in Build OS, and if you know how to edit the options.xml file for that package you can make it show up wherever you want in Build OS. Another note is when you make a package you may still have to look over the .rgu file and make changes/fixes. Also some CAB's use setup.dll's as well and the Package Tool will not work with those (will not copy the setup.dll or read its information) Most CABs dont have a setup.dll so thats ok.

leary
1st May 2009, 11:19 PM
I'll give it a go.
am getting 20ish free on boot with MS3

kclubb
3rd May 2009, 11:47 AM
a kind of important i found is the dialer i'm using appearently doesn't ring on inbound calls.. going to fix with standard vogue dialer and try again...

leary
4th May 2009, 01:33 AM
a kind of important i found is the dialer i'm using appearently doesn't ring on inbound calls.. going to fix with standard vogue dialer and try again...

I noticed that too. I installed the titan OEM dialer from cab and it fixed the problem.