I'm pretty new to this cooking but learned a lot in the past week. I got a slimmed down rom running without problems, compressed some stuff. It works great.
However I can't figure out the registry. For example, I can edit the .rgu files directly with success. But if I add a .rgu myself, the values get overwritten with the defaults. I know they get added because I created some check values.
So basically my question is, can I add my own .rgu or .provxml file and where or do I need to edit the default .rgu files each time when cooking a new rom?
roufneck said:
I'm pretty new to this cooking but learned a lot in the past week. I got a slimmed down rom running without problems, compressed some stuff. It works great.
However I can't figure out the registry. For example, I can edit the .rgu files directly with success. But if I add a .rgu myself, the values get overwritten with the defaults. I know they get added because I created some check values.
So basically my question is, can I add my own .rgu or .provxml file and where or do I need to edit the default .rgu files each time when cooking a new rom?
Click to expand...
Click to collapse
Under SYS, I normally create my own customization folder which gets executed last (alphabetically).. e.g. folder called zzz_Customization. I then put my customization RGU and provxmls there. Nothing in the OEMs or SYS can overwrite them except for provxmls.
Actually I think the RGUs in the XIP can overwrite them but I have not tried it.
Forgot to say thanx for the tip. I got it working now.
Better use provxmls, since they get implemented last.
You can also resort to mortscripting, as it's becoming more and more popular.
A.
Related
OEM supplied by Schaps. This version already integrated in his last ROM.
Not like previous version, this version Profile Tab already work correctly. No need to do anything. I have use it for several days and I dont notice any notifications queue issue or wild vibrate at all.
But I do change the following:
-Installation directory change to \HTCHome instead of \Windows
-To get Brightness shortcut working, the same patch as previous version applied.
-The same patch applied to enable the Tab Setting through registry.
Other than that Nothing. Much better version than v1.5
Color version uploaded!!!!
If you are ROMcooker, download the htchome.dll for rom cooker .
Install sdkcert.cab if you have not done so.
There are about 100 pages of discussion about v1.5. Lets not repeat what have been discussed over there like: Clicking left most mail icon will take you to MMS, how to change music tab tolaunch HTC Audio Manager, and so on and so on. I dont plan to follow up closely on these thread as I think this version is very good already. Should there be any fix, change, etc please refer to the respective post.
Enjoy
Is this better than the one you had released with your kaiser skin?
Currently i am using that, is it worth me updating?
Thanks
Bennec, the one you are using is v1.5.xxxx. Very earlier and uncomplete version that has been tweaked to make it reliable enough to be used. This version is a new build with the profile tab working and additional features in the contact tab thatenable you to select what number ina contact for the speed dial. Definately worthed.
Can you post a version where the files do go in the windows directory? I want to cook this in, but not have duplicates.
TooSharp said:
Can you post a version where the files do go in the windows directory? I want to cook this in, but not have duplicates.
Click to expand...
Click to collapse
you can, just use windiff on the SYS and OEM folders of your kitchen, the dump folder is created by processing these 2 folders, so any file dups will be in there BEFORE you run buildos.exe.
add you package, then run windiff ont he SYS and OEM folders, it will find the file duplicates, and delete the ones that ARE NOT from your new package!!
bennec83 said:
you can, just use windiff on the SYS and OEM folders of your kitchen, the dump folder is created by processing these 2 folders, so any file dups will be in there BEFORE you run buildos.exe.
add you package, then run windiff ont he SYS and OEM folders, it will find the file duplicates, and delete the ones that ARE NOT from your new package!!
Click to expand...
Click to collapse
Maybe I should have been more clear.
When creating a rom, all files will be placed in the windows directory, if you need files in a different directory like the cab posted above you will have to use initflashfiles which just copy the files to a new folder, then you will have duplicates. I just don't want 2megs of photos in two spots.
Garphical Anomolies
@schen you need to swap some of the icons for my fixed ones!!
please Download this Original Icons Fix and add it to you package. 2 of the black and white icons (Music and People) dont react properly when you select them.
that link fixes them!! (it is not just yours, it is a common problem with all htc home plugins!!!)
TooSharp said:
Maybe I should have been more clear.
When creating a rom, all files will be placed in the windows directory, if you need files in a different directory like the cab posted above you will have to use initflashfiles which just copy the files to a new folder, then you will have duplicates. I just don't want 2megs of photos in two spots.
Click to expand...
Click to collapse
Your question makes no sense then!
When you COOK this in obviously you would remove the version you already have in the ROM therefore you would not have the duplicates.
Also if you just created an package out of the cab above you will get NO initflashfiles therefore the package will install to the windows directory!!!
bennec83 said:
Your question makes no sense then!
When you COOK this in obviously you would remove the version you already have in the ROM therefore you would not have the duplicates.
Click to expand...
Click to collapse
You still don't understand. My problem is NOT buildos failures. I don't want duplicates when the rom is complete. Any time you use a initflashfile you will have duplicates in the finished rom. That is what they are for. Again the problem is not with duplicates in the OEM and SYS. If you go back and check my posts you will see I helped you with this exact problem. I know how to create a rom!!!! What I don't know how to do is edit the dll file to redirect it to look in the windows directory for the png files. Hence why I'm posting.
bennec83 said:
Also if you just created an package out of the cab above you will get NO initflashfiles therefore the package will install to the windows directory!!!
Click to expand...
Click to collapse
Yes you do get a initflashfile that copies all the png files to HTCHome. See attached.
schen, installed & everything working fine, except for one, am unable to use the hardware navigational pad when accessing music tab, from there u can't proceed to go up, go to ff, rw or play button.
Touchscreen function (for all of the above ff, rw & play tabs) in music tab is working though.
thanks anyway.
TooSharp said:
You still don't understand. My problem is NOT buildos failures. I don't want duplicates when the rom is complete. Any time you use a initflashfile you will have duplicates in the finished rom. That is what they are for. Again the problem is not with duplicates in the OEM and SYS. If you go back and check my posts you will see I helped you with this exact problem. I know how to create a rom!!!! What I don't know how to do is edit the dll file to redirect it to look in the windows directory for the png files. Hence why I'm posting.
Yes you do get a initflashfile that copies all the png files to HTCHome. See attached.
Click to expand...
Click to collapse
Funny, i created the package and i didnt get that!!!
il have to look into the flashfile generator in using (im not using the core one that you are!!)
Thanks for the heads up and apologies for the confusion!!!
bennec83 said:
Funny, i created the package and i didnt get that!!!
il have to look into the flashfile generator in using (im not using the core one that you are!!)
Thanks for the heads up and apologies for the confusion!!!
Click to expand...
Click to collapse
No problem. Thanks for the help. Sometimes it's hard to convey what you are thinking in words, especially about something so confusing.
TooSharp said:
No problem. Thanks for the help. Sometimes it's hard to convey what you are thinking in words, especially about something so confusing.
Click to expand...
Click to collapse
Well then my answer to your question would be to remove the initflashfile, then everything would get installed to the windows directory and since you have no need for shortcuts, this would be fine!!!
been using this for a while and saw the new version a while ago. has option of more when u go to the 4 day detail in weather. fonts seem nicer and all. looks like a good upgrade to 1.5 Bennec83 irc bro
schen said:
OEM supplied by Schaps. This version already integrated in his last ROM.
Not like previous version, this version Profile Tab already work correctly. No need to do anything. I have use it for several days and I dont notice any notifications queue issue or wild vibrate at all.
But I do change the following:
-Installation directory change to \HTCHome instead of \Windows
-To get Brightness shortcut working, the same patch as previous version applied.
-The same patch applied to enable the Tab Setting through registry.
Other than that Nothing. Much better version than v1.5
I will create a separate Cab based on Schaps color version as well in a minute after a few try this cab with no problem.
Enjoy
Click to expand...
Click to collapse
Thank you for the new version, and tab setting is essential. Thanks again!
bennec83 said:
Well then my answer to your question would be to remove the initflashfile, then everything would get installed to the windows directory and since you have no need for shortcuts, this would be fine!!!
Click to expand...
Click to collapse
Just tried that. It doesn't work without the png files in the HTCHome directory. I guess we can't have everything.
The special dll for installing n Windows directory uploaded. Use that dll.
On the subject of weather plugin.
I am not sure why is there a need for a pre-configured xml file. Anyway, you need a gui to choose the city. Why not have a gui where you could enter the data which is stored on xml file. I suppose rather than sending an entire xml line when communicating with xml service, build an xml file base on the data entered via gui.
As I understand it, the DLL was just edited using a hex editor as \HTCHome and \Windows has the same number of characters, it sounds like it wasn't a decompile thing or something like that.
I'm not at home at the mo so I can't check but if you load the DLL up into a hex editor (winhex?) then replace all the \HTCHome text with \Windows, you should be good to go.
This is just my uderstanding though of what I've read in the previous....saga
Smiffy.
schen said:
The special dll for installing n Windows directory uploaded. Use that dll.
Click to expand...
Click to collapse
Thanks for the fix!!
I am planning to use the Core/Hypercore and/or Pandora's Kitchens to play around with the latest AT&T ROM.
The following is something that has always confused me to some extent in the past.
If I want to delete or change the files that are part of any particular package, I imagine that I need to create a new .DSM file to go along with the changes/deletions I might make.
The HyperCore kitchen provides a utility to rebuild the .DSM file, but from what I can see, the new .DSM file created is nothing like the original. It seems to be lacking a lot of binary information that exists in the original...prior to the file listing.
First...Is it safe to NOT create a new .DSM file if I simply want to delete files from a particular package?
Second...If I merely change some icon/bmp resources in any of the files, and the name remains the same...do I need to create a new .DSM for that package?
And finally...as there seem to be differences between existing .DSMs and the ones that are created by the Core utility, can I really trust the new ones I generate?
Any help/guidance would be appreciated...thank you.
-pvs
Hi. I've read hundreds of posts and followed dozens of tutorials. I'm aiming to gain an understanding of what actually happens during the rom cooking process and I think I'm getting there. I've used loads of different toolkits and kitchens and most recently I've been using 'romdonalds' which has given me a better understanding.
However I'm a bit confused about the difference between the dump directory with loads of files and folders, and the OEM/SYS versions of these which I've seen when using packagetool and buildos. I know how to go from the 'flat' structure to the oem/sys structure, but I don't know how to go back again.
I'd also like is to know what really happens behind the scenes when you click the go button in buildos.exe.
TIA
Matt
I could really use a little help to understand what's going on here. If there's some clear explanation of what actually happens during cooking that I've missed, could someone point it out to me please? I've searched thoroughly, read extensively, and pulled my hair painfully... but I just don't get it. I've analysed batch files in just about every kitchen there is but I've reached a point where I need some help.
If there's some unwritten quid-pro-quo requirement that I've missed before I can ask a question then tell me that too - I'm no freeloader, I've just donated to Slither2006 for his cube, and when I've fully grokked the process I'll write up everything I've learned in a really clear guide, I promise.
I'm not an idiot either - I was a technical architect at a large UK ISP until recently, doing stuff like building a huge virtualised server farm with custom management tools and a homebrewed iSCSI /LVM2 snapshot system that blows away anything commercially available, and now I work for myself... I've used HTC devices since the Blue Angel, also an Exec and now a hermes... but I could really use a hand here.
Thanks!
I suspect you are quite a bit ahead of me here, but here goes.
The OEM/Sys folders are just part of the Dump folder, but extracted and turned into a more logically arranged order for manipulation.
When you run buildos it just takes these and a few other bits such as the XIP section and puts it back in a format for rebuilding.
Best I can do I am afraid.
Thanks for your reply crazyc. It's getting a little clearer now. Can anyone else shed any light? Ideally I'd like to know exactly what buildos does to turn the organised folders back into the dumped ones.
Piecing it all together:
A: I know how to get the dump folder from a source rom (nbhextract->nbsplit->imgfsfromnb->imgfstodump).
B: I know how to make changes to the dump directory manually (add/delete files; extract/convert .hv files to .rgu; edit .rgu files and reconvert to .hv; edit initflashfiles.dat to create shortcuts on first boot)
C: I know that instead of all that I could convert the dump directory to the organised oem/sys pair (pkgtool) and know that in theory I could manage that with BuildOS.exe to integrate oem packages with the option.xml file in them - but I don't understand what's happening here relative to (B) above
D: I can turn the dumped folder (but not the oem/sys folder) back into a flashable rom (imgfsfromdump->imgfstonb->nbhtool)
Can someone who really understands what's going on explain where I'm confused?
Thanks
Matt
Here is my take about cooking....
When the dumped OS has all the rgu files in tact then spliting the dump folder as OEM and SYS will work.
Where as some OS do not have rgu file in them (some cooks prefer to cook this way...all OEM OS have rgu files). In this case you would have to use only the dump folder and edit default and user.hv to add and delete stuff. You cannot use package tool for this method.
You sure can turn OEM and SYS back to ROM, just use the right kitchen (Pandora, Bepe Kitchen, etc)
Hope this helps.
Hey guys. I've done some UPXing on my ROMs, but in my next ROM build, I want to UPX everything that is UPX'able. I've read about issues with certain DLL's causing the device not to boot when UPXed. I've had issues with programs when MUI files are compressed. I know I can pretty much compress any EXE that I want, but which DLL's are safe and which aren't? Which DLL's should I avoid compressing? I need your personal experiences to find out which DLL's didn't compress without problems. Thanks for your contribution guys!
Also, does anyone know of a way to UPX a module? Can you just UPX the file within it? Can I convert it to a file, UPX it and then convert it to a module again?
Herald Owners:
This is all for a Herald ROM I'm working on.
New OEM, new SYS, new laguage MUI packs, all compatible with my current kitchen.
(Done, now present in 1.31) Internal search system (search file names and file contents, edit the text files directly from the kitchen or launch an external editor)
Automatic localization (support for folder variables in initflashfiles.dat/app.dat to create entries valid for all languages (Done, now present in 1.31), using those variables during import to make ROM translation easier, automatic generation of new OEM_Lang_XXXX folders with a corrected initflashfiles.dat and renamed MUIs as soon as a compatible SYS is added, automatic fixing of all the packages' initflashfiles entries to match the new languages start menus, automatic package To CAB conversion to test all your packages on the phone (Done, now present in 1.32))
(Done, now present in 1.32) Total integrity check (checking the validity of every REG file and app.dat file, checking for broken module folders, checking for invalid SYS/OEM/EXT packages to reduce the hard to track ROM building issues to minimum)
Advanced file attribute management (setting the ROM file attributes according to the DSM file, adding an interface in dialog properties to change the DSM file list and applying file attributes automatically to the files that are not present in the DSM file list)
Internal ProvXML engine (much more accurate CAB to EXT conversion, provxml to REG and APP.DAT conversion)
Batch ROM import (adding long paths (up to 32000 characters) support to oskitchen to allow using the kitchen from any folder no matter where and adding a new internal tool that takes a folder of multilanguage ROMs of similar versions and builds a final Sources folder with all the localized files merged to start working on multilanguage ROMs much more easily)
EXT2 Package Replacement (an EXT format replacement that supports MNGE modules (no more module folders around) and folders with conditional names (for resolution, language, device, windows mobile builds, etc.) to make multidevice packages much easier))
Advanced ROM versioning (allow setting the version in the splash screen and in the RUU)
(Done, now present in 1.31) Manila management support (deleting unneeded localized manila files while building, adding a whitelist-based manila files compression to improve manila speed and free space on the ROM)
Improved UPX support (adding a file cache to remove the delays caused by the UPX compression during cooking process, switching UPX file selection to opt-in, UPXing all the files according to an online whitelist that can be updated/submitted from the kitchen)
Kitchen distribution tools (generating a XML file to allow changing the kitchen titlebar/about/help entries, to automatically load a selected device profile and to add an additional customizable tools menu, adding a "Temporary OS.NB" shrinking tool and a SYS cleanup tool to delete unneeded resolutions and languages)
I vote #9, then #5
so many great ideas .. can't we have all of them?
i guess you will work out on them sooner or later
thanks for all you effort
nosedive said:
so many great ideas .. can't we have all of them?
i guess you will work out on them sooner or later
thanks for all you effort
Click to expand...
Click to collapse
Exactly what I was thinking I love all of these ideas I love the direction this kitchen is heading great work airextreme!
if possible i'd vote for all as well
oh well let the voting begin
"Manila management support" would be great!!
I think you should include something to make different ROM Builds in one shot, to make all the .nbh files just by pushing the cook button once. (like a MaxSense version, CHT Version, Plain Version etc..) Also, an autimated compression + upload feature would be nice, too.
EcoROMchef said:
I think you should include something to make different ROM Builds in one shot, to make all the .nbh files just by pushing the cook button once. (like a MaxSense version, CHT Version, Plain Version etc..) Also, an autimated compression + upload feature would be nice, too.
Click to expand...
Click to collapse
Can it turn on my coffee maker in the morning as well?
WoZZeR999 said:
Can it turn on my coffee maker in the morning as well?
Click to expand...
Click to collapse
then it would have to be called the easy automated kitchen
I voted for deployment tools since I like control but would have also voted for integrity.
This seems like a better place to add other simple requests rather than in the kitchen thread here is a simple one
Add the full version number to "Help About".
I have 3 versions running and am current naming the folder to keep up with it.
OS kitchen
I will vote for #6 and #9
if wish a possibility to select back for easy folder structure (old kitchen). the separation for language, sys-versions, oem-versions ... is not realy nessassary (for me) and the overview of cooking would better.
integrating emulator/simulator for testing cooked rom.
you make very good job.
jjblaster3 said:
if possible i'd vote for all as well
oh well let the voting begin
Click to expand...
Click to collapse
I second the motion. All are great future additions. Good work Air.
Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.
the_scotsman said:
Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.
Click to expand...
Click to collapse
+1. I also miss that feature the most after making the shift to osK. Great job Air!
I Vote For the following:
#1
#3
#5
And thanks for this absolutly great Kitchen!
the_scotsman said:
Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.
Click to expand...
Click to collapse
hello,
i confirm with you. i use totalcommander and pspad for more comfort.
totalcommander is good for listing all files from kitchen-root (without directories) with sorting by filetypes and pspad for searching by keywords.
How about the ability to build a dumpable rom
hoho.hello every one!
Well, I really nead a good PROVXML parser/validator, because straight app.reg editing is inactual now.