Related
Maybe I'm asking for too much here... but I just cant figure out how to cook my own ROM. I've read and read and tried and tried. Its just beyond me for some reason.
I would be forever grateful if someone could take DCD's 2.3.1 ROM for Verizon, add in no2chem's nueAUDIO and nueLED, add the OEM Cyberon Voice Dialer...
and make me a perfect ROM for my Verizon XV6800. That would be my perfect ROM.
I guess I want the "best of both worlds".... the freem RAM DCD's ROM offers, with the few cool features no2chem has incorporated.
Anyone? PLease?
I'm not understanding the obsession of adding as much as possible into ROMs... Possibly I am missing something here, but I thought that the only advantage is to not have to individually install each app upon a cooked ROM?
With the above, it's only a concern over 3 items. Is there truly a dire need to have them within a ROM rather than take the few minutes to install each of them?
Especially with evolving utilities such as nueLED is it not best to separately install its CAB version and then have the ability to remove and upgrade it without the bother of making up and installing an entirely new ROM????
Sorry, just my thoughts..
I have been working with TDial Designer and have had difficulties after 3.0.4 getting the dialer skin to look the same. Maybe someone else has overcome this problem and could give me some guidance. Here's what I have done.
Before, I was able to select BlueFrog dialer in TDial and have the keys skin to look like the screenshot20.jpg below (you can see the background transparent). Now with the recent DCD ROMs it looks like screenshot2.jpg thumbnail below where the keys remain black though the background is there for the process.
I have tried both the Old Vogue (Touch) and the New Vogue (BlueFrog) options in TDial and neither work. I have included the cabs for those if you want to test them on your phone.
I install the Kitchen using DCDs option for the new Vogue dialer checked (no OEMs replaced) and although it looks the same before I try to install the cab, it doesn't work like it used to.
I would be glad to replace the OEM with the one from 3.0.4, but I know DCD has been doing some upgrading to the functionality of the dialer and don't want to break some of the work that he has been doing (I like new and shiny stuff).
Thanks!
P.S. Disregard the top and bottom bars as one of them was using WisBar.
I don't use any third party dialers. If you have all the png files (for each number, function etc) you can simply copy them to \Windows.
gc14 said:
I don't use any third party dialers. If you have all the png files (for each number, function etc) you can simply copy them to \Windows.
Click to expand...
Click to collapse
I guess I could do that, do you copy manually or using UC?
If you use UC do you do it with XML or by copying the whole folder?
I do it via UC, but with a cab file I made. I don't use XML anymore with UC, I've cabbed everything. If you zip up all the files and post it, I'll make a cab for you.
gc14 said:
I do it via UC, but with a cab file I made. I don't use XML anymore with UC, I've cabbed everything. If you zip up all the files and post it, I'll make a cab for you.
Click to expand...
Click to collapse
Here ya go.
I used the TDial export to give to you, but I am not sure which you will need (old vogue or new). Let me know if this works or if you need something else.
REQUEST: If you are up to making another of your amazing wikis, I think a tutorial on how to make cabs for xml and file importing/copying (like this dialer for example) would be HIGHLY used and appreciated. I would definitely buy you some beer for that one (I may even take Boston Celtics as my new fav BB team).
Here you go.
If I have time, maybe I'll do a wiki.
gc14 said:
Here you go.
If I have time, maybe I'll do a wiki.
Click to expand...
Click to collapse
That would be something that would be used across the board, and may be as widely referenced as any other out there. Plus it would be valuable for anyone with WM, not just Titans. Better that it be done by a Bostonian
Thank you very, very much. I will try to take this one apart and figure out what you did.
Did it work?
gc14 said:
Did it work?
Click to expand...
Click to collapse
Yes, thank you so very much for making that.
With the re-release of 3.2.2 I was scrambling to get updated before I left work and just got a chance to sit down now to thank you. It works perfectly and will look at a few cab programs to figure out how you did it.
Is there a way that the phone popup reg entry could be affected by this cab? I have had that problem with my TDial dialers, and still needed to after this too. I wonder if some other cab I am installing has this key change as I assume you just copied the pictures I sent you to the windows dir. I will have to do some investigation to find where I am getting that change as DCD PM'd me and let me know that my bug was only on my side and not in his kitchen when it happened before your cab.
You are the man GC, I will buy you some beer next week when paychecks come in.
First off, I need to thank everyone on this site for the wealth of information that is contained here. I took my stock XV6800 and walked through several tutorials and I've put on 4 different ROM's in 2 days, all of them with the GPS functioning like a champ and everything on the phone running swimmingly.
A special thanks to mr-free for his prompt responses and dcd for his excellent guides.
Anyway, I've already used two kitchens so far to make custom roms (Titan Kitchen 6.5 Beta 4, and Titan Reloaded 1.3.2). Both create very usable ROM's but there's aspects of each that I like better than the others. Since Kitchen 6.5 uses WM 6.5, I'd like to start with that one, but there are several OEM packages that I would like to add to it from Titan Reloaded, as well as a couple of other ones that I've found from the web.
And so I'm not flamed, I have searched and found the following information about Alex's Cooking Kits helpful, but still not completely sufficient to answering my questions:
http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
http://wiki.xda-developers.com/index.php?pagename=Alex's Cooking Kits
And on to the questions:
1) Is it possible to just copy the folders from the OEM folder of the Titan Reloaded 1.3.2 kitchen into the OEM folder of the 6.5 Beta 4 Kitchen and have them show up in the "BuildOS" menu?
2) Are the instructions in Alex's Cooking Kits applicable to the Titan? Its geared towards the Kaiser, and I couldn't find anything that would lead me to believe it is compatible with the Titan. If not, is there a "Cooking Kit" suitable for the Titan?
I'm not to the point where I'm capable of creating my own OEM packages, but I'm gunning for that too eventually. No questions on that though...yet.
The only question I can help with is your first. The OEM packages from Titan Reloaded 1.3.2 should be able to be copied into pretty much any kitchen.
Note that the Manila_2d_Scott OEM from Titan Reloaded kind of depends on the SYS\dcd_UCAutorun package, as it installs the first M2D theme from CAB at boot. This may be fixed in later versions by making a seperate config.txt for m2d. That way the OEM package will be more portable.
Note that the Youtube package from Titan Reloaded also requires the YTFIX package, but those will hopefully be merged in later versions.
Other than that, you just need to watch out for conflicting packages. Usually buildos will give you errors if this happens, so you'll know.
Awesome, that's really helpful.
Actually m2d is not something I was planning on keeping anyway. I'm moving from a Samsung i760 (dreadfully unhackable) but in an attempt to make it more usable, I actually paid for SPB Mobile Shell, and SPB Phone Suite. I've gotten quite addicted to using them and I don't find m2d to be a sufficient replacement for primarily the lack of ring profiles. Ring/Vib/Silent just isn't enough for me. (And PhoneAlarm doesn't have what I need either.)
What I was looking to move though was:
Adobe Reader 2.5
YouTube (with the YTFIX, now, obviously)
HTC Album
Tweak_Volume_Higher
no2chem_nueExtROM
There aren't any dependencies there that I need to be aware of, are there?
I couldn't find Google Maps in the OEM folder from Titan Reloaded but its no big deal, I can download it I guess.
I guess I should have mentioned that to use the no2chem_nueExtROM package, you'll need to add these lines to the bottom of ROM\XIP\boot.rgu.
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ EXT_FLASHDRV]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"MountHidden"=dword:0
"Folder"="Extended_ROM"
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ EXT_FLASHDRV\FATFS]
"FormatTFAT"=dword:1
"EnableWriteBack"=dword:1
"EnableCache"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ EXT_FLASHDRV]
"DriverPath"="Drivers\\BuiltIn\\EXT_FLASHDRV"
"LoadFlags"=dword:1
"Order"=dword:12
"Bootphase"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\EXT_FLASHDRV]
"Profile"="EXT_FLASHDRV"
"Index"= dword:1
"Dll"="OEM_FLASHDRV.dll"
"Prefix"="DSK"
"Order"=dword:13
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
It's possible that this is what's causing some people problems with Titan Reloaded 1.3.2 though. If you've already used Titan Reloaded 1.3.2, you probably don't have to worry about this. It might not even be the cause though. Most people are having no problems with it.
Also, based on someone's post in the 6.5 ROM thread, you'll likely want to remove this file from the kitchen before adding in an adobe reader package:
SYS\OEMAPPS\ppc_adobereaderle.exe
Titan Reloaded installs GoogleMaps from CAB during customizations. Since Google is likely to upgrade the app often, I'd recommend that you just download it and install like you said.
Those are the only caveats I can think of for the packages that you mentioned.
DustinEarnhardt said:
First off, I need to thank everyone on this site...
A special thanks to mr-free for his prompt responses and dcd for his excellent guides.
Click to expand...
Click to collapse
Anytime you are very welcome..!!! I do what I can when I am around
bitserve said:
...I'd recommend that you just download it and install like you said.
Those are the only caveats I can think of for the packages that you mentioned.
Click to expand...
Click to collapse
x2 .. I find that loading programs as CABs or during customizations
is a damm cool and a better idea then loading it all in the ROM,
just having that options to remove something is a very good feeling lol
FYI: I got the ok from s10onn2o to upload a clean built 6.5 beta ROM
not kitchen .. the ROM is what I use .. got a few things fix and a few more stuff
cleaned up.. also has some basic missing apps, WM Office 6.1 + notes, Adobe,
sweet TF2D dialer, etc.. etc..
mr-free said:
FYI: I got the ok from s10onn2o to upload a clean built 6.5 beta ROM
not kitchen .. the ROM is what I use .. got a few things fix and a few more stuff
cleaned up.. also has some basic missing apps, WM Office 6.1 + notes, Adobe,
sweet TF2D dialer, etc.. etc..
Click to expand...
Click to collapse
So have you uploaded yet? give us the link.
mr-free said:
FYI: I got the ok from s10onn2o to upload a clean built 6.5 beta ROM
not kitchen .. the ROM is what I use .. got a few things fix and a few more stuff
cleaned up.. also has some basic missing apps, WM Office 6.1 + notes, Adobe,
sweet TF2D dialer, etc.. etc..
Click to expand...
Click to collapse
Heh, I've got a little more patience than "Give it to me now!" but yes, this does sound very nice. The omission of Office was also something that was really bugging me about 6.5.
In the meantime I ended up playing around with PPCkitchen and WOW are there a lot of packages. Too many actually. It takes me 15 minutes to go through them all. The build I'm running today is pretty good, but I still wish I was running WM6.5. I'm sure I'll come across your ROM once you've got it uploaded. XDA is rapidly becoming one of my favorite sites (and not to mention a huge time sink!!)
Anyone can add office to 6.5. Just get the oem from BuildOS and put it in the oem folder for beta 4,
Wow, its that easy huh?
I think I'll just do that then! This place rules!
To All Chef,
During flashing the ROM, when the customization job runs, is it possible to provide the list of application's that come along with the ROM and let the user choose the set of application he wants?
Also, if possible, the job can even delete the cab files of the application which are not choosen by the user. This will save ROM space i guess. I am not a developer, so i am suggestion instead of do something about it, sorry.
Thanks.
I'm not exactly a chef, but I'll respond anyway
For your first question, yes, that is possible, as long as someone develops an app to do that. Hell, I could develop it if there's enough demand.
As for deleting CABs that weren't installed, that is unfortunately not possible because they are already part of the ROM.
Yes it is available. You are talking about the Rom Kitchens available in this forum. Just take a look in the rom kitchen posts then you'll know what I'm talking about. Here are two that currently has the lastest aGPS fix. At0mAng and Da_G's Kitchen and the corresponding packages. The kitchen allows you to pick what you want in your rom, it is very easy to use and you should no doubt give it a try.
dizzyraider said:
Yes it is available. You are talking about the Rom Kitchens available in this forum. Just take a look in the rom kitchen posts then you'll know what I'm talking about. Here are two that currently has the lastest aGPS fix. At0mAng and Da_G's Kitchen and the corresponding packages. The kitchen allows you to pick what you want in your rom, it is very easy to use and you should no doubt give it a try.
Click to expand...
Click to collapse
Thats actual ROM cooking. But i was mentioning about the 'customization' program that runs right after you flash your ROM. If we have an option setup in that program to choose application before it installs, that would nice from users perspective. Just a thought. I am sure everyone will like it.
Trancecoder said:
I'm not exactly a chef, but I'll respond anyway
For your first question, yes, that is possible, as long as someone develops an app to do that. Hell, I could develop it if there's enough demand.
As for deleting CABs that weren't installed, that is unfortunately not possible because they are already part of the ROM.
Click to expand...
Click to collapse
I am glad to hear that you could develop. (I dont have that skills). If you develop, we can probably let all the Chef know to use it, if they want.
http://tiermann.net/index.php?option=com_content&view=article&id=9:tier-autoinstall&catid=2PC%20Apps&Itemid=2
aruppenthal said:
http://tiermann.net/index.php?optio...=9:tier-autoinstall&catid=2:PPC Apps&Itemid=2
Click to expand...
Click to collapse
Reading through this thread I knew it was only a matter of time until I found the post with that link
I liked that app but never really used it. Always seemed like too much of an extra step on first boot. Not to mention, some cabs require user input to install and would freeze the device temporarily requiring a soft-reset once it tries to install them.
Trancecoder said:
I'm not exactly a chef, but I'll respond anyway
For your first question, yes, that is possible, as long as someone develops an app to do that. Hell, I could develop it if there's enough demand.
Click to expand...
Click to collapse
That would be one cool ass app!
I was thinking of something like this as an xml file. Can it be done with XML? I don't know XML that well but I think it might be able to.
Can you be more specific as to what you were thinking with XML?
I wrote a simple Mortscript that generates a SDConfig.txt based on what files exist in a specific cab folder...
Simpest solution is what many chefs do: Lite and Loaded ROMs
SDconfig in the apps you want to a lite ROM or uninstall the ones you do not from a loaded ROM...
or you could always cook your own custom ROM
dharvey4651 said:
Reading through this thread I knew it was only a matter of time until I found the post with that link
I liked that app but never really used it. Always seemed like too much of an extra step on first boot. Not to mention, some cabs require user input to install and would freeze the device temporarily requiring a soft-reset once it tries to install them.
Click to expand...
Click to collapse
I'm guessing the device is not actually frozen. Generally, during customization screen input is locked to prevent the user from interfering with customization.
The device will appear to be frozen because the buttons and screen do not respond. If you were to call your phone you would see that the call comes through, but you can't answer because the buttons are locked out (trust me, a few times my wife has called my cell while I was testing ROMs and a few times she called right when it was doing customization).
You would need to unlock the screen input before running the cab to ensure the user can enter data.
example config.txt
Code:
LOCK:Enabled
TSK: \WINDOWS\Guava Bubbles.tsk
LOCK:Disabled
CAB: \WINDOWS\Microsoft_Sounds.cab
LOCK:Enabled
CFG: \WINDOWS\config_PT.txt
I get the impression that the real goal of this is to prevent the installation of a few items that the rom chef likes but others don't. For example, I personally find no use in SecondToday, but a few chefs include it with their roms.
I think that this would be a non-issue if most applications were uninstallable after setup...at least the apps that tend to be upgraded frequently (Opera, TomTom) and the ones only popular with a few users (SecondToday, TouchResponse).
The argument is "just cook your own or use a different one", but that doesn't really answer many people for whom one rom is nearly perfect, but there's just a little tweak or two to the installed apps that would make it perfect.
I'm not sure this really needs another app or any extra steps in the install process. Not when this would slow down usage for many people, and only really benefit a small percentage
aruppenthal said:
http://tiermann.net/index.php?optio...=9:tier-autoinstall&catid=2:PPC Apps&Itemid=2
Click to expand...
Click to collapse
That's what I use
Ok, so I finally did it, I flashed a cooked ROM to my Fuze. Whew! I did run into a snag or two, but all is good now and I am even ready to try another one to see some of the differences.
I do have a couple of questions though. Flame me if you must, I can take the heat. However, trust me when I say, I read everything on this site.
1. I chose a "no manilla" version...why did it still have to do the "initial setup of touchflo interface..."? I thought Manilla was TouchFlo and therefore wouldn't need to be there at all. Since I really like SPB MS3, I didn't want anything TouchFlo.
2. I would like to try an NRG ROM, but I still can't quite grasp what customRUU is. Am I free to flash one of these with just the HardSPL that I already did? Or do I need somethign else before flashing one that has this in the folder?
3. Since I am still trying to catch up with what's available out there now...what the heck is CHome? At first, I thought someone mispelled that Google browser thing, but soon figured out that can't be it.
Christine
CDnNC said:
Ok, so I finally did it, I flashed a cooked ROM to my Fuze. Whew! I did run into a snag or two, but all is good now and I am even ready to try another one to see some of the differences.
I do have a couple of questions though. Flame me if you must, I can take the heat. However, trust me when I say, I read everything on this site.
1. I chose a "no manilla" version...why did it still have to do the "initial setup of touchflo interface..."? I thought Manilla was TouchFlo and therefore wouldn't need to be there at all. Since I really like SPB MS3, I didn't want anything TouchFlo.
2. I would like to try an NRG ROM, but I still can't quite grasp what customRUU is. Am I free to flash one of these with just the HardSPL that I already did? Or do I need somethign else before flashing one that has this in the folder?
3. Since I am still trying to catch up with what's available out there now...what the heck is CHome? At first, I thought someone mispelled that Google browser thing, but soon figured out that can't be it.
Christine
Click to expand...
Click to collapse
Welcome to the wonderful and addictive world of customized ROMs. It's one of the best ways to get the most from your Raphael, but sometimes we see things that 'aren't quite right' since they haven't gone through the rigor that vendors put their ROMs through. But then again, we get to play with the new, neat stuff!!!
As I understand it, Manila is HTC's interface/Today skin for the Raphael. You don't have to use it, but most ROM's will have it cooked in, so you'll need to go through the 'setup' as the ROM is first booted on your machine. If you don't want to use it, just go to the Today screen settings and de-select the TF entry.
CustomRUU is the application you run to do the actual install from a PC. There's no need to play with it all, just run it, and everything should happen automagically. There's also an option to run the install from a loaded SD card on the unit itself, but I stick to the Activesync connection version myself.
Sorry, can't help with CHome... I have no idea what that is either.
As I said -- welcome!
Therefore you are?
drtolson said:
Sorry, can't help with CHome... I have no idea what that is either.
Click to expand...
Click to collapse
ASFAIK, CHome is the new Today interface for Windows Mobile 6.5.
CDnNC said:
1. I chose a "no manilla" version...why did it still have to do the "initial setup of touchflo interface..."? I thought Manilla was TouchFlo and therefore wouldn't need to be there at all. Since I really like SPB MS3, I didn't want anything TouchFlo.
Click to expand...
Click to collapse
Do you mean the Stylus Alignment? If so, you should always perform a stylus/screen alignment.
Do you mean the G-Sensor Calibration? If so, you should perform the calibration; although you may not use TF3D, many application can "leverage" the G-Sensor capabilities of the device.
HTH,
hilaireg said:
ASFAIK, CHome is the new Today interface for Windows Mobile 6.5.
Click to expand...
Click to collapse
I thought that was 'Titanium'
congratulations
Here ya go:
ConfettiCore is the underlying display component shared between Start Menu and Today screen.
CHome is the Today screen itself.
Titanium is the skin; alternatives are Bronze, Neo.
HTH,
* EDIT *
Thanks Da_G for your ever so wonderful wisdom and knowledge about all that is Windows Mobile ...
CHome and Titanium are somewhat interchangable. They both refer to the new 6.5 "Default" interface. If you have CHome installed on your ROM, go to Start>Settings>Today>Items and check "Windows Default". Everything else will uncheck itself. Now you can see CHome in action. CHome is new and ofcourse not yet released by Microsoft, so it is not flawless. Showaco has made a great tool for editing CHome so that you can control what is on the today screen. It takes bit of playing to figure it out, but give it a go. I really have become hooked on the simple effeciency of CHome.
As for the Initial Setup of Touch Flow, this is a left over from a previous ROM. Most of the ROM chefs, do not bother changing the set-up screens because they do not matter. They are simply something to display while the phone configures itself. Other Chefs seem to enjoy changing this screen, so results may vary. In any event, no need to worry.
RUU is the wrapper that installs your ROM image on the phone. When you download a rom and unzip it into a folder, there usually are 2 files, the RUU and the NBH file. The NBH file is the real ROM image. The RUU or Wrapper is what installs it to the phone. If you unzip a ROM and the wrapper is missing, simply copy it from a different ROM you have unzipped and add it to the folder with teh NBH file you want to flash. The RUU/Wrapper does not change from ROM to ROM, only the NBH changes. With both the RUU and the NBH in a folder, launch the RUU and it will load the ROM in that folder.
HARD SLP is the first step that will allow you to Flash Custom ROMS. AFTER you Hard SPL according to the directions, choose a ROM, download, unzip and launch the wrapper. You must be attached via activesync. After that, off you go.
Enjoy. Every ROM is like getting a new phone.
Doug M.
Showaco Editor:
http://forum.xda-developers.com/showthread.php?t=481379
Thanks Doug, that helps me understand as it makes perfect sense. I appreciate all of the help I find on this site.
Now on to the next step doing that radio flash.
Excellent, Good to see a fellow Charlottean getting hooked on flashing.
Doug M.
Charlotte?
DAMN! For months, I had been thinking "if only one of these XDA guys lived here, he could show me how to do this and I wouldn't be terrified of bricking my phone"...and here you are?!?!?
Actualy, Titanium is the base WM 6.5 user interface\homescreen, chome refers to the dll plugin being utilized by Titanium. chome was ported from the WM 6.1 slidding panels interface made for smartphones and has been optimized by Showaco and others to offer more pluggin options with Titanium!
Manila 3D is HTC's user interface it is used in conjuction with touchflo but they are different things kind of, touchflo just refers to being able to scroll with your fingers and how the physics engine operates.
RUU stands for ROM Update Utility, it creates a bridge to your bootloader from your PC to flash through Active Sync\ Device Manager.
Hope this helps some!
CDnNC said:
DAMN! For months, I had been thinking "if only one of these XDA guys lived here, he could show me how to do this and I wouldn't be terrified of bricking my phone"...and here you are?!?!?
Click to expand...
Click to collapse
Well, here I am. I am by no means an expert, but feel free to get in touch any time. My office is near Northlake mall.
Doug M.