First time Chef with a few questions - Touch Pro, Fuze ROM Development

Ok so I am looking at trying to cook a ROM based on the NATF series of ROMs, but there are several things I'm looking to do that I'm not sure of.
My major question is, is it possible to entirely remove TouchFlo3D? While it's pretty, I find it slow, and I don't use it at all (it's one of the first things I disable).
I have some other things I'd like to remove to, like anything to do with the camera (because I have the camera-less version). How do I accomplish these feats?
Thanks!

To remove things out of the ROM either delete/move each respective directory out of the kitchen.
Manila: \OEM\PACKAGE_Raphael_Manila
Camera: \OEM\PACKAGE_Raphael_CAMERA_HTC_Generic
One of the things you'll need to keep testing, is when you remove something, are there other packages that depend on the one you removed. If that's the case it often easier to leave the original package in the ROM even if you don't use it. It will just take a little of the ROM space.
Prepare to flash your phone constantly! ...and welcome to the world of cooking.
-e

just an addition to era2er post,
u may need to remove 0409 (specific to rom lang) folder which contains city database for manila, ControlBlock & AudioManager folder package & remove all registry related to 'manila' in all coding (unicode, etc) for complete cleanup.

Related

New tool : Extended ROM manager

Hi - first major post so bear with me!
After 'cookin' my own extended ROM a few times, I realised that harvesting the various CABs was only the first step - I then had to trawl this (fabulously informative) forum (and wiki) and identify each CAB to see if I actually wanted it in this particular ROM – sometimes I’d find a picture (really helps), and sometimes not, either way I would always forget what something was and have to re-find it.
So I wrote a utility to help me - and I'm sharing with everybody else 'cos that's just the kinda guy I am. XtendROM scans a folder (I’m old-school so I still call ‘em directories, but I’m trying to speak windoze here) and treats that folder as the ‘library’ – it is from there one can select which CABs you want to include. I’ve set things up for the Himalaya (I have an XDAII) so the default extended ROM size is 64Mb, although it only warns you if you go over that.
The principal is simple - deliberately so. Information on the CAB files is stored in TXT files and the preview images are stored as GIFs, BMPs or JPGs (always the same name as the CAB file, with an extra file-extension). I’m thinking that we could post TXTs/images and maybe even CABs in this thread, thereby making cooking a ROM as easy as downloading the CAB/TXT/image, saving it to the ‘library’ and choosing it for your ROM.
Drag & drop should work (to some extent at least) and the ROM files can be moved up/down in the config.txt file easily enough – after all I made this for my own use and getting the information from the web-pages is sometimes the trickiest part. I’ve recently added an option to copy the selected CAB files into a separate folder, this way I can easily copy the new files into the new ROM without having to search manually (computers ARE here to make life easier – allegedly).
Um, I think that’s about it – consider this a first-release so I’ve undoubtedly missed stuff, and I’m pretty sure I’ve forgotten to save some settings into the registry (I’ve had to get on with some real work, but this version works okay – mostly). Of course, if this utility kills your system, turns into potted-plants or does anything else I’m not expecting then you’re on your own – if you have doubts then don’t use it, I ain’t getting sued just for sharing my stuff.
I'll be adding some TXTs/images/CABs here myself at some point - I'm just too busy with other stuff at the moment (patience, I'm told, is a virtue).
Any problems, comments, questions or thoughts then please post here – knowledge is a thing best shared.
:edit: - I forgot to mention above, but when a file is copied the file-extension is automatically checked and the approriate command inserted into the CONFIG.TXT - for example, copying a .EXE file will default to 'EXEC', whereas a .TXT file would generate a CPY1/CPY2 command (to copy into \Windows).
Toodz,
- StarFux -
Excellent, let's me try and I will post my feedback later.
Thank a lot.
cool program.... downloading now...
thanks
No further comments?
Just checkin'-in... so, no feedback? Must be just that good then ...
-sf
Thank you krab.. Let's me try..
Some TXT files to get things started
Attached are some TXT descriptions from xda-developers - the zip-files are named according to the username of the person who wrote the text (all credit to them, not me) - I've just compiled the data into a format that XtendROM will make use of.
yann.zip - from http://forum.xda-developers.com/viewtopic.php?t=6470
sin.zip - from http://forum.xda-developers.com/viewtopic.php?t=16916
Just unzip into your chosen library folder.
S'all - have fun.
-sf
besides of having one error on my first run .. just forgot wat it is .. i think you've done a greate job .. now its much easier to create config.txt and to avoid .. further error if i created it in notepad .. btw tnx for the tool m8 ..
...very nice looking tool )))
THANX
buzz
What a great application
Thanks for sharing
Now maybe we can create all huddle together and create a central library for all known extended ROMs so we can cook our own ExtROM
Thanks for all the positive feedback! - I'm working on some tweaks to cope with creating compressed ROMs at the moment (thanks to some great feedback) - I'll post here when I've sussed it
Thanks again!
-sf
Giving up
Hi all - well excessive demands on my time from work & home have meant I've been unable to tinker with my util, so I'm giving-up trying to find time and have decided to sleep more instead.
If anybody else wants to play with it (it's written in Delphi 7 & uses a few libraries but could be played with), then PM me and I'll send you the source so that you may continue development (if desired).
Hope everybody continues to enjoy the util anyway - L8rz.
-sf

how to modify HTCCPL reg key and .cpl???

how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
chriskay said:
how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
Click to expand...
Click to collapse
Some in reg, some in provxml Check your PM for more detail, friend !
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
chriskay said:
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
Click to expand...
Click to collapse
I'm not sure what you are talking about, but I do like the word "original".... If you are done, is it worth sharing?
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyfa does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
chriskay said:
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyda does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
Click to expand...
Click to collapse
yups, you can still run some application from extende rom.
At windows folder, you will find config.txt . You have to give some command on it.
The command there, is just a RST ( Reset ) . But If you give a command first, it will install some cabs. It all command from AutoRun
This is some command
LOCK: Enable
CAB: \Extended_ROM\TCPMP.CAB
CAB: \Extended_ROM\Cabs\ABCD.CAB
LOCK: Disabled
RST: Reset
the command will install TCPMP.cab and ABCD.cab
share at XDA is always a good one.
With Cloudyfas ROM, there is a provxml file that sets the keys for AutoRun to somewhere in the windows directory. You will have to remove/alter that for autorun from the storage card.
The point of AutoRun is to allow you to install cabs etc before the user can really use the ROM. UC is to provide users with a faster way to set up the ROM. The two can and should co exist.
so if i got it correctly: putting the common command lines of the extended rom autorun PLUS the command lines of sdautorun into this single config.txt file would make the device boot and install from both locations one by one?
so, what are your recommendations about the registry key:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
leave it or kill it??
edit: decided to remove it due to its complete redundancy. it is uc already... now i am close to finishing.
edited edit: put it back in. i think it won't hurt and maybe someone still needs it.
cheerio.
One of Cloudyfas ProvXML files overwrites that, so it is completely redundant!
It's called mxipupdate_zz_oemoperators_102_CheckAutorun.provxml
You can look at it and see what it does.
The two AutoRun files (SDConfig.txt and Config.txt) are separate files that run independently. The point of UC is User Customization. All you need to do is make sure SDAutoRun.exe is in \Windows and that the last line of your config.txt file is
Code:
EXEC:\Windows\SDAutoRun.exe
That is all that is needed for it to run.
ok. removed the redundant entries. i was just thinking there might be some way of a "dual boot". but actually this is rubbish. so i leave it as uc as it is.
The point of UC is that the two are seperate. Everything can be achieved with just one of the two systems, but with UC, you (the chef) can install cabs, and the user can install tweaks etc.

UC vs. OEM

I'm currently running DCD 3.0.1, and looking to upgrade to 3.2.2, so I'm trying to figure out whether to use UC or OEM to install my apps. I've read through lots and lots of threads related to both UC & OEM, but can't find any definitive answer as to which is the better method. I would imagine it depends, but depends on what?
From what I can come up with:
UC - pro - easy to change without having to rebuild the ROM
UC - con - need to have SD card in (yes, a minor con, but I had to write something)
OEM - pro - get back to your "optimal" setting quickly - doesn't require installation of apps
OEM - con - need to rebuild ROM to make any change, whether large or small, then reflash
note: I did try searching, so I apologize if there is a post/thread explaining this...
I think that you having a hard time finding a con for UC shows that it is the strongest most stable solution.
OEM is good for some things and installs those things a bit quicker being that they are included in the ROM. UC is a bit slow, but I know that if my sdconfig.txt file is written right things happen the way they should. It is also always there on your card when you need it. This way you can flash everything from your phone without ever needing to connect to the PC (if you have wifi or data plan).
Use UC and post your sdconfig.txt file for us to review if you need more information. Learn more here.
UC is better.
What happens when your favorite program gets updated? With cab installs, you can just overwrite the older cab.
Also, with OEM's, yes you don't have to install anything after the flash, but the more OEM's you include in the ROM, the bigger the ROM. It'll take longer to flash than a clean ROM.
If you don't know what you're doing with OEM's and initflash files, you could also end up with a crap ton of bloat in \Windows bogging down the device even further.
Once UC is setup, and your config file is written, it's very easy to make simple changes to the config. In the long run, it's much more clean, efficient, and easier to maintain.
Looks like I'll be going to UC route, then...thanks for the replies.
(and I've had Sleuth's UC thread bookmarked since he posted it )

Learning to kitchen!

Okay I have flashed my telus titan many times using the usb method and the flash card method (prefered) now I would like to learn the kitchen method, which I understand I can modify to include the programs I have to load after I do the flash. I get the buildnb and then selecting the programs I like, what I would like to know is if I want to add my tomtom 7 to the build is this possible. plus some other games that I have. What folder to I add these files to? If there is already a discussion about this could you send me a link.
Cheers
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
jc, the kitchen is quite easy to use. But you cannot just dump programs into it and have them available to select from buildnb. The programs that you have will most likely be in the form of a cab. For use in a kitchen the programs need to be in the form of an OEM. There are tools available to OEMize a cab. Just do a search here and you wiull find the tools you need. Then just dump the OEMs into the existing OEM folder inside the kitchen and then when you run the kitchen the programs will be there for you to select. They will install with the ROM, not after it.
You do have other options if you dont want to OEMize your cabs. You can search for Alex's OEMs at ppcgeeks. There are hundreds of premade OEMs for you to select from.
Another alternative is to keep your cabs and just use UC to automatically install them immediately after you install your new rom. This is the preferred method for most of us now as it leads to less problems and allows for programs to be uninstalled at a later date which OEMs will not allow.
Sleuth255 has an excellent tutorial about how to automatically install all your favorite cabs using UC. Search for it and you wont go wrong.
All you need to do is find OEM packages for the programs you want. If you use DCD's kitchen just add them to the OEM folder. If you use PPC Kitchen just add them to the User OEM folder. Then just select them once you run Build OS.
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
Click to expand...
Click to collapse
Hate to break it to you, but this uses BuildOS too, just a different version. Buildnb is just a batch file that g'reloc's and calls BuildOS among other things after BuildOS is run.
I'm trying to learn this stuff too.
Here's some of the stuff that I've found:
OEM Tutorial Thread:
http://forum.xda-developers.com/showthread.php?t=347361
there's more links at the bottom of the 1st post in the thread
Here's the link to packages - say for Kaiser - So I don't know if they can be used on Titan? Anyone knowledgeable please chime in.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_software_recs
??? All the links on Alex's thread seem to be Kaiser based - how much of this is applicable to the Titan and/or other devices?
I agree that ppcgeeks is a good resource too.
DCD's kitchens seems to be fairly easy to do a build. I'm still learning what I want, which versions to include, what everything that's there does, etc...
In theory it seems simple, I'm not finding the learning curve to be all that easy though. A lot of trial and error. But that's part of the challenge, I suppose.
It would be nice if the people with a lot of experience would chime in with tips, links, and comments that would help gather the information into one place for those of us that are learning - maybe I need to go hunt through the wiki's some more, IDK. But sometimes it seems the more threads I read the more confused I get.
My opinion to all of you...and again..this is just MY opinion...take it or leave it...
Build the rom using the kitchen as is with no added personal OEM's. Install all programs/applications/tweaks after flashing either manually, or much easier by UC.
I've converted a few so far, and they haven't turned back. OEM's can be so messy, and can be a HUGE pain in the ass if you need to uninstall/troubleshoot any problems.
My advice would be to read the entire thread on UC, as well as the threads in the Titan Upgrading forum pertaining to UC (I know I've talked about it quite a bit, as well as many others).
Sound good to me. I'm not one who likes to reinvent the wheel if I don't have to, but I am willing to go through a little extra pain to get what I want. If I can get the same results through UC vs. OEM'ing CABs, I'm game. The OEM'ing of CABs so far for me has been a real pain in the arse.
I will do some more reading on UC since I haven't totally gotten the results from that yet that I want. I'm sure my minor problem with the UC cfg file is not unique.
What about adding some of the nueTools into the DCD roms? Reading the text in the included files - some of them can only be rom'd like the ext'd rom utility. Looking that over, I haven't figured out, with any reasonable confidence, how to add this to DCD's roms. I have searched some, but not extensively on this one yet.

[RES][COOKING] rilphoneAuto: auto RIL DLL selection based on user's current radio ROM

*** MOVED! The dev thread for this app is now in Development and Hacking, HERE
---original post---
I recently got into cooking my own personal ROMs, and realized that every time I get a new kitchen/ROM or flash a new radio, I have to make sure the rilphone.dll file is the correct one for my radio. Well, more accurately, I realized how annoying it can be.
Yes, it can be done with UC and the appropriate CAB for the user's current radio, but I wanted to create an easier way to do it so that the user doesn't have to think about it. Considering how many times the TP/Fuze keyboard layout question is asked here, I'd say any kind of automation is good automation
My answer to this issue is rilphoneAuto.exe, a .NET CF 2.0 app that reads the user's current radio version, determines if the appropriate RIL DLL is available (through a configuration XML file), and edits the "DLL" entry under HKLM\Drivers\BuiltIn\RIL to point to this particular DLL.
In order for this app to work, you have to include all the RIL DLLs you'd like to support in your ROM, and change the rilphoneAuto.xml file to have an entry for each of those DLLs. It's a very simple format, don't worry
I have attached version 1.0 of rilphoneAuto in OEM and EXT formats. Both attachments contain the app, RIL DLLs version 1.12.25.19 and 1.14.25.05, and the XML config file preconfigured with the aforementioned DLLs.
*** IMPORTANT: You must add rilphoneAuto to one of your config*.txt files in order for the app to start on first boot customization. I don't know if that can be done from inside the OEM or EXT packages. The line you'll need to add is:
Code:
EXEC:\Windows\rilphoneAuto.exe
Please leave feedback. Thanks!
Looks like a good addition, i'll try it out on my ROMs.
frickin awesome!
you should post this on the development & hacking forum, a lot of other devices users could use this too!
Good idea. I'll do that.
awesome as hell for all the users into radio switching and even those who arent. they'll have improved functionality and not even know it, just by flashing their radio.
so this is in the rom i just updated to
if i change my radio after the initial boot does the phone change the necasarry settings? or is it now up to me?
thanks
rilphoneAuto should only run on first boot, so if you changed your radio, you should re-run it by executing \Windows\rilphoneAuto.exe and then rebooting.

Categories

Resources