Database Users

[NEW RELEASE] ◄ HyperCore Kitchen ► MULTIDEVICE !!!

As you can see I made a hard copy of one of the posts of anichillus!
This is his HyperCore Kitchen and I made some minor changes to make it work for our Polaris!
HyperCore
PUBLIC BETA​
The most complex KITCHEN a begginer cook may ever need.
Easy to use but also very complex, it can be usefull to anyone.
Why ask and wait for others to make the perfect ROM for you when you got the power to do it yourself ?
~. Base ROM .~​* NO BASE ROM ! but ANY ROM !
~. Best part .~​* IT USES TADZIO TOOLS
* YOU CAN OPTIMISE EXE's and DLL's, SO IF YOU WANT EVEN MORE SPACE, YOU'LL GET IT
* IT CAN BE USED ON ANY DEVICE WITH VERY LITTLE MODIFICATIONS !!!!!
* NO LONGER LIMITED BY ANYONE OR ANYTHING.
* YOU CAN COOK ANY ROM YOU LAY YOUR EYES ON VERY EASY
* IT HAS ADVANCED ERROR CHECK
~. It will install .~​Core folder on the system drive. Some tools and settings required.
HyperCore folder on the Desktop. There is your kitchen. You can move it wherever you want.
The place where you actually use it is HyperCore\Panel.
~. How To .~​- First of all edit the file named "Device.txt" located on the "Core\ACK\" folder located on systemdrive (mostly drive C:\)
Edit as following.
If you have a :
HTC Wizard : " set device=Wizard "
HTC Hermes : " set device=Hermes "
HTC Artemis : " set device=Artemis "
HTC Herald : " set device=Herald "
HTC Universal : " set device=Universal "
HTC Trinity : " set device=Trinity "
HTC Prophet : " set device=Prophet "
HTC Polaris/Kaiser : " set device=Polaris "
Click to expand...
Click to collapse
Save it and then you're good to go.
It's much similar to the old Core kitchen...so those of you who used it ...will feel comfortable with it. Regenerated batch scripts, better, and i hope bug free.
~. Guides .~​* Hermes Cookbook - THANKS to sambartle
* My Way of cooking
* How to ADD/REMOVE programs -THANKS to mfrazzz
~. Notes .~​Since this is still a public BETA, I await your problems/ideas/concepts.
If you spot a bug, i suggest to send me a PM as well as a post on the thread.
I suggest having a ROM to make a backup in case you do something wrong
I created and tested this tool for WindowsMobile 6 , but WM5 should work OK too.
~. Download .~​
HyperCore_1.02 on RapidShare
Special thanks :
* anichillus - for this kitchen
* Papamopps - for real support
* nandlal_mk - for answering questions and DSM editor
* mUn - for finding the time to answer some of my questions
* molski - for i started working on his tools and still used some of them
* Tadzio - for his tools and patience
* bepe - for his tools
* the-equinoxe - for his splash-screen tools
* naboleo - for his initflashfiles generator
* dutty - for his NBH Tool
few others that surely i forgot to mention Sorry..

Thanks for sharing this! It's a revolution for the chef's here.
I suggest working on the Polaris Project with this baby!

THX too ... i will Port it on the Niki Plattform too ... or if you can Handle it ... pls write a PM and i will help you!

thx NikMel for sharing...and happy to see that you've got an HTC Cruise...
-maybe your polaris'rom release for next ?

You never know?!?!

Very good job!!! Thank you so much for spreading this info to all of us!!!

Nice work man! Finally we have it also for Polaris

have fun!

Thanks alot for your efforts. I have to say though, the kitchen doesnt work at all for me on my Vista Ultimate x86.
I somewhat got it to work by editinig some of the paths int he BAT files (see below for examples) but it's nearly impossible to track down all paths, I get "could not be found..." and paths errors all the time...
Examples:
DUMP_ROM.BAT, when the working directory is %systemdrive%\Core\Batch\, the provided cd /../../ on line 4 leads to %systemdrive% where the batch stops because IF EXIST "Extract\Source\%rom%" etc breaks because the folders \EXTRACT\etc do - in fact- not exist in %systemdrive%
Extract.bat, the working directory is
%systemdrive%\Core\Batch\Links\ and the provided cd /../../ on line 4 leads to a path error when you try to launch the folder \Extract which doesnt exist in %systemdrive%\Core of course.
And a general question: I didnt really think it through, but it seems illogical and more prone to errors to me: why is there so much stuff doubled, once in HyperCore and once in the systemdrive\Core directory...?

You did install this kitchen and not extracted?
schaggo said:
Thanks alot for your efforts. I have to say though, the kitchen doesnt work at all for me on my Vista Ultimate x86.
Click to expand...
Click to collapse
There is no call to an etc directory where do you see that?
schaggo said:
DUMP_ROM.BAT, when the working directory is %systemdrive%\Core\Batch\, the provided cd /../../ on line 4 leads to %systemdrive% where the batch stops because IF EXIST "Extract\Source\%rom%" etc breaks because the folders \EXTRACT\etc do - in fact- not exist in %systemdrive%
Extract.bat, the working directory is
%systemdrive%\Core\Batch\Links\ and the provided cd /../../ on line 4 leads to a path error when you try to launch the folder \Extract which doesnt exist in %systemdrive%\Core of course.
Click to expand...
Click to collapse
Just some file are double and this is how anichillus made it.
schaggo said:
And a general question: I didnt really think it through, but it seems illogical and more prone to errors to me: why is there so much stuff doubled, once in HyperCore and once in the systemdrive\Core directory...?
Click to expand...
Click to collapse

Oh wow, I didnt expect an answer so soon...! Thanks alot!
There is no etc directory of course, etc means and so on... I figured everybody understands etc... my bad, sorry
What I meant with \Extract\etc is if the script can't reach \Extract it cant reach any subdirectory either...
Ok, now to the kitchen. No, I didnt use WinRAR to extract it, I executed the EXE and it got extracted to C:\Core\... and the HyperCore folder gets moved to the desktop after the extraction is done. So the directories are just fine, they are how they are supposed to be. But - and that I suppose is the problem - when I check the properties of the shortcuts in the HyperCore\Panel directory, their working directory (the directory the script does its actions in) is the directory the target batch script lays at and not the directory where the shortcut is placed. So the batch tries to access empty, non-existant folders all the time...
Example: Shortcut in Desktop\HC\Panel\Extract will execute a batch script, but the working directory of the batchscript isnt Desktop\HC\Panel\Extract where it got executed from but its the directory where the BAT effectively is: C:\Core\Tools\Extract
So placing a cd \..\..\ in the batch file won't change the working directory two levels up to Desktop\HC\Panel\Extract but it changes two levels up from the folder the batch lies: to C:\Core\Tools\Extract
Do you use Vista too? It could be that the relative (and correct) paths get updated in the shortcuts when you move the directory to another place. Could it be that this new "feature" exists in Vista? I guess I have to try it in an XP installation in a virtual machine...
<edit>
I found the cause: a cd / changes to the root directory! so cd /../../ will result in C:\ which of course is wrong! I started editing the batch files and I'm replacing all cd /.. with cd .. and now its working!
Check it out and try yourself in your command line tool:
Code:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.
C:\>cd "Program Files"
C:\Program Files>cd Adobe
C:\Program Files\Adobe>cd "Reader 8.0"
C:\Program Files\Adobe\Reader 8.0>[B][COLOR=red]cd ..[/COLOR][/B]
[B][COLOR=red]C:\Program Files\Adobe>[/COLOR][/B]
C:\Program Files\Adobe>cd "Reader 8.0"
C:\Program Files\Adobe\Reader 8.0>[B][COLOR=red]cd /[/COLOR][/B]
[B][COLOR=red]C:\>[/COLOR][/B]
</edit>

Dear schaggo,
I'm in XP and it works as is.
True when you use "cd /" it gets you back to the root of drive.
C:\etc..\etc..\etc..\>cd / goes to C:\
D:\etc..\etc..\etc..\>cd / goes to D:\
etc..
The path issue is a VISTA behavior so you better try it in XP (virtually or hard installed).

Desktop\HC\Panel\Extract is a directory and all the batch file to extract a rom file are in that directory.
schaggo said:
...
Example: Shortcut in Desktop\HC\Panel\Extract will execute a batch script, but the working directory of the batchscript isnt Desktop\HC\Panel\Extract where it got executed from but its the directory where the BAT effectively is:....
Click to expand...
Click to collapse

Thanks for sharing this!

Well yeah, I know where the files are.
But hey, if there are cd /../../ commands all over the batch files (check them yourself), it would mean that almost every batch file is trying to access the \Extract folder on C:\ at some point, which just ISNT placed in C:\ on any system!
And you say the cd / command produces the exact same behaviour on XP, then it can't be a Vista issue.

schaggo,
I don't know if it's me or you but we talk parallel and we don't listening to each other.
You better try it on a XP system.

Thanks a lot.
It works when i changed "/../" to "../" in my Vista.
It seems some ROM can't dump well, such as "Polaris_WWE_0.67_Opera_bepe"

alanxzg,
Bepe is using a method to bundle all rgu/dsm files in one.
This is the reason.
alanxzg said:
Thanks a lot.
It works when i changed "/../" to "../" in my Vista.
It seems some ROM can't dump well, such as "Polaris_WWE_0.67_Opera_bepe"
Click to expand...
Click to collapse

Hey, I just found out about this
For it to work on Vista you'll need to edit all the batch files located in C:\Core\Batch so that instead of cd /../ or cd /../../ ...and so on will be cd ../ or cd ../../
More exactly remove first / after cd.
Don't worry about how it's made...it was the only possible way to link icons and folders that are dynamic. You can move the HyperCore folder wherever you want on your harddrive. It will work.
I am guessing you added the new IMGFS tools to it so it works with WM6.1 ?
This version also works on Kaiser...since from what I know same arguments are used. Only difference is the RUU and possibly others. Anyway the HyperCore 2 is under way .
Cheers !

TNX for your input!!!
anichillus,
TNX for your input!!!

[UTILITY] Manila 3D Kitchen [BETA, with rhodium manila support]

Hi!
There a lot of kitchens avaialable for ROM building. Now this one is to ease TouchFlo3D building.
This kitchen uses the knowledge and works of 6Fg8, D-MAN666, xboxmod, chainfire and many others who are involved in Manila hacking.
If you use this kitchen and/or any of the decompiled scripts then be so kind and share back the source code of your modified scripts too!
This kitchen (v1.5) has the following utilities included:
6Fg8's mode 9 editor (v3.3.0.1)
sztupy's mode9 converter (v1.0)
chainfire's CFC compressor (v0.46)
MKT: a tool for batch converting/compressing/compiling mode9,qtc,png,xml,lua files (v1.1)
LuaDec (2.0)
A work in progress lua and xml IDE
And various other tools
In the center of this kitchen stands MKT aka manila_kitchen_tool, which is like 'make' but for manila kitchen developement.
It has the following functionality:
split hased _manila files back to their original filenames
join a bunch of files in a directory back to their hashed form
mass decompile mode9 files back to xml and save their lua scripts
mass convert qtc files to/from png files
mass compile lua files
It works like 'make' in sense that only the modified files will be recompiled/recompressed so after the firts setup it might be ideal for manila development.
The output of the kitchen was tested with the Rhodium manila (WVGA version) on a HTC raphael device and it works, so this project is no longer a prototype, but is still considered beta stuff
Kitchen set up
I uploaded a complete Rhodium2 Manila kitchen in case you want to use that as a base (download both the kitchen and the rhodium files, then copy them to the same directory), but of course you can use any other manila pakcage you get across. To set up the kitchen copy the package into the 'pkg' directory then run:
Code:
mkt split
to split the hashed files back into their filenames. (For this conversion it uses the same table as m9editor uses.)
You will get a "bin" directory. This will hold all "compiled" stuff, so here you will find all the files that don't need more preprocessing, and can be hashed/installed to the device
Next you want to get some editable files out from the luac, mode9 and qtc files, so use:
Code:
mkt -x bin frommode9
To decompile mode9 files back to XML (it will also extract the scripts out of the package)
Next:
Code:
mkt -c d,qp fromqtc
or
mkt fromqtc
Will convert all qtc files to png files. (the first type will work on cfc compressed qtc files, the second will work on non cfc compressed files)
After this only the scripts are remaining. Unfortunately these can't be decompiled easily, so grap the decompilation of someone (like me ), and put these files into the "insrc" directory. After this run
Code:
mkt -d insrc -o src split
so all the hashed _manila files will be converted back to their original filenames to ease searching through them.
After this you're ready with your prepared kitchen. These things were already done with the Rhodium manila so you might use that package to start manila modding.
Compiling
You can use tomode9, compile and toqtc commands to compile these files back to their binary counterpart. Alternatively you can use:
Code:
mkt -c pq,c,p make
to run this three command after each other. It's like a Makefile, so it will only compile things that have changed. Of course you might want to 'make all':
Code:
mkt -a -c pq,c,p make
This will build all files from the "src" directory into the "bin" directory
Creating the package
After you're done you can use
Code:
mkt -o outdir join
to hash all files from the bin directory back to hashed form, and put it into the 'outdir' directory. Next add the binaries and you're ready to flash
Alternatively I included createpkg that will create a cab package from the OEM apckage found in the 'pkg' directory
Download and other stuff: http://winmo.sztupy.hu/manilakitchen.html

Sounds great! Downloading now. Thanks sztupy!

Yeah, good job sztupy, this will be a great addition.

nice...gotta buy a bigger house...so many kitchens

pcarvalho said:
nice...gotta buy a bigger house...so many kitchens :d
Click to expand...
Click to collapse
roflcopter

pcarvalho said:
nice...gotta buy a bigger house...so many kitchens
Click to expand...
Click to collapse
what you need is a microwave

sztupy said:
Missing functionality / bugs:
Embedded decompiled scripts can't be re-embedded into mode9 files automatically (this would need a command line mode9 editor
Click to expand...
Click to collapse
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.

6Fg8 said:
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.
Click to expand...
Click to collapse
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...

sztupy said:
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...
Click to expand...
Click to collapse
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.

6Fg8 said:
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.
Click to expand...
Click to collapse
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed

sztupy said:
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed
Click to expand...
Click to collapse
mode9 is basically binary XML, so i had no choice
The easiest way (at least for me) is byte positions just kidding ...
I'm on vacation next week, maybe i'll get struck by an ocean of light while skiing on one of the wonderful austrian mountains
CFC compressor .... I've that lying around somewhere here, shouldnt be a problem to adapt it.

an ambitious project... thank you

nice work great addition

Scripts update addon with the newest decompiled stuff.

Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.

sztupy said:
Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.
Click to expand...
Click to collapse
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.

showaco said:
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.
Click to expand...
Click to collapse
I tried to install it as a cab on NATF's ROM I'm using, and it worked flawlessly. It might break on a stock ROM though. The whole convert to cab thingy is alpha currently, but hopefully it will be solved.

sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
EDIT: never mind, left the code where it was and just searched out and fixed what it referenced. Other then the Q16.16 lines, everything is good.

Hi sztupy. Excellent work. Im poor and unemployed so although Id like to, I cant donate any cash at the moment. I like this project enough to offer body parts though, if any of yours fail
EDIT - bug report removed. was related to luaconv.exe. moving to another thread.

smotrs said:
sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
Click to expand...
Click to collapse
You can consider every function in the file as a value. It's just like a number or a string in this case, because in the main body you assign functions to some variables. So if you find something:
Code:
SomeStuff = function(foo)
lots of stuff
lots of stuff
lots of stuff
end
SomeOtherStuff = function(bar)
lots of stuff
lots of stuff
lots of stuff
end
Then in the main body this will translate to:
Code:
SomeStuff = funtion1
SomeOtherStuff = function2
And in the disassemlby to something like this:
Code:
R0 := Function(f1)
SomeStuff := R0
R0 := Function(f2)
SomeOtherStuff := R0
And of course the definitions of these functions will be put after the main body (just as with any other inlined function, the only exception is that compare/luadec and the other tools I made will handle these functions separately to ease decompiling). So if you have to fix the main body you have to only look at the part of the script which is not in a function...end body

[TOOL][21/July/10]Process imageinfo.bin&packages.cif/sof|ImgInf v1.2.0.0[ONLINE]

I don't know if anyone else finds this somehow useful, but here is a tool I've made (thanks to miky6682 for motivating me) for getting some information from imageinfo.bin and packages.cif/.sof.
Also since I started to use bepe's xidump in my kitchen in order to check a module's info I had to open imageinfo.bin with a hex editor since xidump doesn't generate imageinfo.txt.
So this tool gathers some of these info in one text file (output=imginf.txt).
Also if packages.cif and packages.sof are present inside the folder you selected then they will be "read" too.
Some notes:
1. Drag n' Drop (folder only-don't drop any files) works for Select [Button] - output file will be created in the directory where the application is.
2. You can select the location for your output file by clicking the SaveTo [Button]. If you don't, then by default it is created in the directory where the application is.
3. If you have "Associate dsms" ticked, then if dsms are present inside the folder you selected they will be associated with the Package's Name when reading packages.cif.
4. Command line usage is also supported!
Code:
ImgInf.exe o:<output file path> i:<Path of folder to process> -a<optional switch to associate dsms with the Package's Name>
5. You can "rewrite" your own edited packages.sof/.cif.
Well, just run it and you'll get how it works...it is quite simple!
Attached is also an example of an output file to see what to expect (This is the output when I run the tool on an entire dump (IMGFS & XIP) before converting OEM to EXT).
Best Regards!

Good Apps, this get info packages from imgfs... nice
thanks for this

Nice work thanks for posting it

Good work!
FYI here is a similar tool that works with XIP modules only (not IMGFS):
http://code.google.com/p/iitp/

Da_G said:
Good work!
FYI here is a similar tool that works with XIP modules only (not IMGFS):
http://code.google.com/p/iitp/
Click to expand...
Click to collapse
This tool is Create by a Utak3r

Thanks
This is exactly what I was looking for.

v1.1.0.0
A small but significant update to this little tool:
New version apart from doing what it was built for...
lets you edit packages.sof.
So in order to use it as a packages.sof re-writer you can for example
select "Only *.sof" option and drag a Metadata folder on [Select] button and then edit the packages.sof as you like...
A new packages.sof will be created when you click [Apply changes] button in the path you selected by clicking the [...] button.
Regards!

kokotas said:
A small but significant update to this little tool:
New version apart from doing what it was built for...
lets you edit packages.sof.
So in order to use it as a packages.sof re-writer you can for example
select "Only *.sof" option and drag a Metadata folder on [Select] button and then edit the packages.sof as you like...
A new packages.sof will be created when you click [Apply changes] button in the path you selected by clicking the [...] button.
Regards!
Click to expand...
Click to collapse
Cool. FYI, there is another packages.sof editor posted in post#6 of this thread. I'll give yours a try and see which one I like better.

toadlife said:
Cool. FYI, there is another packages.sof editor posted in post#6 of this thread..
Click to expand...
Click to collapse
The more the merrier...
But this has not actually started as a packages.sof editor.On the other side since I could fit this utility in I thought it would be for the best...
toadlife said:
I'll give yours a try and see which one I like better.
Click to expand...
Click to collapse
Ok man , give it a spin and let me know if you find anything wrong with it.
Regards!

[q] xml / pxml

Sorry for being dumb once again.
I know how to create an XML and convert reg files to PROVXML etc but :
I flashed my cooked rom and did snapshot with kheb made all my changes and got a difference .reg file.
I converted that to PROVXML cause i believe its the best way of doing it.
What I dont know is what to do with it and where to put it in order to flash it.
Ive put it under custom settings\files but iot needs to be named something specifically according to 0Kitchen . Also i have an xml file that has my exchange settings in that which i want to cook in as well but dont know how.
I do use XDA uc but id prefer to let it be done with runcc or something?
Please advise whats better and whats the difference between the differentx PROVXML file naming.
Thanx

I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.

af974 said:
I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.
Click to expand...
Click to collapse
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?

Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Grumps said:
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?
Click to expand...
Click to collapse

af974 said:
Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Click to expand...
Click to collapse
Leme just try quickly we do flash like 30 times a day in any case hey. Will revdert just now
Thanx for your help

There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.

arealityfarbetween said:
There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.
Click to expand...
Click to collapse
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?

Grumps said:
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?
Click to expand...
Click to collapse
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs

arealityfarbetween said:
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs
Click to expand...
Click to collapse
Ok lemme try
Im trying to change my timezone from dublin -8 to gmt +2. n start kheb take snapshot make the change get i difference .reg file. convert it to xml and the paste it in files folder of lastflash folder?? ill try and see what happens

[TUT] Beginers guide to cooking for the TG01

Welcome to my tutorial in cooking for the TG01.
I shall no longer be updating this thread, so please feel free to post and make any contribution you see fit.
This is meant to be a very simple, plain English guide to cooking.
With this in mind i will not be showing you how to port a new sys/xip or any of the more advanced features like sense
lets just see if we can dump, modify, build then flash a working, booting ROM for now.
This tutorial is only what i have learnt whilst beginning to cook my own ROM, so if you find a mistake or have something to offer feel free to post
If you have a question that your going to post, please please search the forum first, i learnt a lot of what i know from threads that have nothing to do with the TG01 or even the type of kitchen we're using. So as the rules state - Search before posting, Thank you.
Modifying the ROM of a Windows Mobile is dangerous to your devices health. If you mess it up it can be fatal.
The information contained in this tutorial is only as far as i am aware. Don't blame me if you brick it.
Having said that, i have never had a problem the short pin method couldn't fix.
You will need the attached .zip file, it contains the kitchen and associated applications.
In this tutorial i am using L3V5Ys kitchen, cab converter by Jason8, Package converter by Total Fire and Package Creator by Ervius.
So thanks to them and everyone in the XDA community for making this kind of thing possible.

1. Dump a ROM
1.1. Download the ROM you wish to modify. I suggest Miros miROM4, its clean and fast without any clutter.
1.2. Extract the ROM and place the resulting .tsw file in the BASE folder in the kitchen. Then rename it "TG01WP_5005000176.tsw"
1.3. Run dump.bat and wait for it to finish, this could take a little time depending on you PC, it may be worth making a tea as it seems to take longer if you watch it.
1.4. You should now have some new folders in your kitchen, for now the only one were interested in is SYS.
2. Modify a ROM (Removal of packages)
2.1 Open your kitchen folder then open the SYS folder,
2.2 You should now be faced with a window with lots of folders in it. The folders are called packages.
2.3 Delete the package Entertainment and its associated packages (Entertainment, Entertainment_DPI_192, Entertainment_Lang_0409 and Entertainment_Lang_0409_DPI_192)
2.4 This has effectively deleted the games that ship with your chosen ROM,
2. Modify a ROM (Adding packages)
2.1 Open your kitchen folder then open the SYS folder.
2.2 Copy the package from its source to the SYS folder. Remember that for this kitchen it must be an OEM\old type package (see post #4)
2.3 Thats it, you added software to your custom ROM.
2. Modify a ROM (modify existing package)
2.1 Open your kitchen folder then open the SYS folder.
2.2 Open the folder titled "Redist_dpi_192_resh_480_resv_800"
2.3 Replace welcomehead.192.png with the one in the downloaded zip.
2.4 That's it, when you boot your new ROM it should show the new welcome screen.
3. Building and flashing a ROM
3.1 Run "2. build no XIP port_no auto.bat" (this is the original build.bat, modified by myself to skip the port xip and BuildOS/auto parts)
3.2 When the cmd prompt opens press any key
3.3 When BuildOS opens check the packages you wish to install then click the green arrow in the top left.
3.4 When BuildOS has finished, close it and the cmd window will carry on opening and closing other programs as it goes. You do not need to touch any thing till it has finished and it asks you to hit enter.
3.5 Assuming you pressed enter when it asked, the cmd window will have now closed.
3.6 Go into your kitchen folder and you should have a new file called "TG01WP_00.tsw" This is your ROM.
3.7 Copy "TG01WP_00.tsw" to a folder called PRG on your storage card (if its not there then create it) and then run SDDL+ or use the short pin method to flash it.
3.8 That should be it, you should now have the rom you started with but minus solitaire.

The Kitchen:
In your "Kitchen" you will find some folders and some files. They all relate to either the ROM ityself,
or the tools used to edit/dump/create the ROM.
BASE - This is the folder in which you put the rom you are dumping
OEM - This is the folder where the Toshiba part of the ROM would be if it was an official Rom that was being dumped,
however when dumping a cooked ROM this folder will be empty as a cooked ROM cannot be dumped correctly by the tools available
and all packages are put in the SYS folder. This will not affect the output, and the OEM packages can be left in the sys folder.
If you dump a cooked ROM you will need to create the OEM folder as BuildOS panics without it, even if its empty it needs to be there.
SYS - This folder contains the dumped ROM separated into packages
ROM - This folder contains the xip, boot.rgu and boot.hv. For this tutorial we won't be working with anything here.
TOOLS - This is where the exe's are that make up the kitchen, you don't need to touch these, the .bat files do it all for you.
Temp - This is the kitchens working folder, you don't need to go here unless there are problems building the ROM but that is beyond the scope of this tutorial.

Packages: (there are 2 types, EXT and OEM, our kitchen can only handle OEM so thats what i'll be discusing)
Each package contains an element of the ROM. For example the BROWSING package contains the parts of the ROM required for internet browsing.
For a package to be usable it requires certain things
Required:
.dsm file - This is to complicated for the scope of this tut so for now just accept that this file is necessary and should never be deleted. All dsms must have a unique name.
That is all a package needs to be a package, though without any files in it won't actually do anything.
Optional:
.rgu file - This file contains the reg entries for the package in question and its name will be the same as the .dsm file in your package.
initflashfiles.txt / initflashfiles.dat - This file tells the PPC where to put the files that are within the package, ie. a short cut to a program in the start menu.
NOTE without an initflashfiles.txt all items within the package will go to the Windows folder.
option.xml - Holds information relevant to the package
The files you wish to install, without them its pretty pointless.
Packages often have other packages associated to them, for example the Entertainment package also has Entertainment_DPI192, Entertainment_Lang_0409 and Entertainment_Lang_0409_DPI_192.
Where Entertainment is the package, Entertainment_DPI_192 has the files specifically for our screen size, Entertainment_Lang_0409 has the files for our language (0409 is WWE)
and Entertainment_Lang_0409_DPI_192 has files that are for our lang and our screen size.

Modifying a .rgu file:
.rgu files contain registry information for the package they are in. If you wish to modify this data then you can do so with notepad, though i recommend downloading Notepad2. If you open a .rgu file and don't understand what's in it then you need to go learn about windows registry editing first. I am assuming that if you are looking at building a custom ROM you already know about reg editing.

CAB Converter:
This program is used to convert a .cab file into a package to be cooked into a ROM
1.Open CAB_Converter.exe
2.Click "add a cab" and browse to your cab or drag and drop your cab into the window
3.Click on the text representing your cab at the top of the window so its selected.
4.Click CAB->OEM, and wait till its finished. Should only be a few seconds.
5.Your package will be in the CAB Converter folder in the converted OEM folder

Package Converter:
Our kitchen only supports OEM\Old type packages, so what if we want to use an EXT\Visual type package? Well Total Fire kindly made and distributed a tool that converts from one to another.
The program is fairly self explanatory but i'll quickly cover converting from a visual to an old package.
1.Open the converter, then click "select" where the greyed text say package,
2.Browse to and open your visual package.
3.click "Convert VTO", now wait till you see "Conversion Complete".
4.Your now usable package will be in the same directory as the visual package with the text "PACKAGE TF" added to the title.

Package Builder:
If you wish to create your own packages, this is the tool to do it.
1.Create a folder named whatever you want your package to be named
2.Add to it the files you want
3.Add to it a .reg file if required
4.Open package Creator, in the bottom right you can choose ITA or ENG.
5.Click open package and browse to the folder you created.
6.Now the initflashes.txt options page appears, here you can select the .exes in your package and choose where to create short cuts. You will need to click apply on each one.
7.Now click complete package.
8.The creator will now create a .dsm file, a .rgu file with your .reg file settings in, an initflases.txt file and an option.xml file within the folder turning it into a package.
9.This package can now be used in your kitchen.

Reserved...

Reserved....

leeston2379 said:
CAB Converter:
This program is used to convert a .cab file into a package to be cooked into a ROM
1.Open CAB_Converter.exe
2.Click "add a cab" and browse to your cab or drag and drop your cab into the window
3.Click on the text representing your cab at the top of the window so its selected.
4.Click CAB->OEM, and wait till its finished. Should only be a few seconds.
5.Your package will be in the CAB Converter folder in the converted OEM folder
Click to expand...
Click to collapse
Thanks for a lovely tutorial! Makes sense!
I am continuously facing this attached error! Any ideas how to solve this! :s

Wich cab do you use ?
What is your Operating System ?

EVEALEX62 said:
Wich cab do you use ?
What is your Operating System ?
Click to expand...
Click to collapse
I used Opera.cab (opera 10) and with windows 7

EVEALEX62 said:
Wich cab do you use ?
What is your Operating System ?
Click to expand...
Click to collapse
chek property of your folder in c: or test to reinstall this program with administrator right (clic right).
Can you send me MP with your cab, I'll test tomorow morning
Have a good night

drupad2drupad said:
Thanks for a lovely tutorial! Makes sense!
I am continuously facing this attached error! Any ideas how to solve this! :s
Click to expand...
Click to collapse
Its better to grab hold of one of the existing opera packages on the forum, I never successfully converted it to a working package. Just seemed to be the opera cab as i have no problems with any other. I think ninjaduck does a nice version with flash and the like already in.
I never saw that particular error myself though. Sorry I can't be more help.

So long and thanks for all the fish.
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.

leeston2379 said:
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.
Click to expand...
Click to collapse
i have one samsung galaxy tab and next week i get also one HTC Desire HD of my company. Android is really good- but more fun i have with WinMo.
today i have get my second "new" tg01!
you were ever friendly and helpful. thank you for your activity and cooking for our tg01 community.
i wish you all best, good luck and cheers, miro

leeston2379 said:
I will no longer be updating this or any of my ROM threads as its upgrade time and I've got a shiny new Desire HD, my trusty TG01 has been retired and i'm off to have a bodge with Android.
The TG01 forum is a nice little place with only a hand full of regular contributors/posters but its always friendly and development seems to move along at a steady pace, so thanks to all its members for that.
To those who PM me, feel free to continue as i will still be around here somewhere and will help in anyway i can.
See you later.
Click to expand...
Click to collapse
Hi Lee!
TG01 community will miss your contributions! In case your retired TG01 lures you back to development, I will keep my eyes peeled. I hope you like your new android, but in case, Winmo is missed (I wish!), do come back!

Hi.
Leeston2379 will not be doing any changes here any more so I allow myself to upload my version of his kitchen here without creating new thread.
What has been changed ?
"Virgin" kitchen was only for packages modification without any pagepool changes or xip porting. Leeston2379 was basing on l3v5y kitchen which have certain bug. Interestingly this bug was "not active" as far as old ( original ) xip.bin was taken in .tsw file creation.
There are 4 batch files for new system building:
a) 2. build_without_xip_port.bat - the same as original leeston2379 batch but with fixed bug although here it is not "active"
b) 2. build_without_xip_port_pagepool_set.bat - allows to set pagepool size
c) 2. build_with_xip_port.bat - like original but allows to port new xip
d) 2. build_with_xip_port_pagepool_set.bat - like original but allows to set pagepool size and port new xip
I did not utilize automatic execution via for example
AutoExecAndClick.exe /launch "xipport.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
In my oppinion it is buggy . There are any timing races or something other causing any strange errors from time to time. User has to like in original l3v5y kitchen press different buttons in xipport software.
Thanks Mangasora for his post concerning porting xip
Regards
fxdjacentyfxd

fxdjacentyfxd said:
Hi.
Leeston2379 will not be doing any changes here any more so I allow myself to upload my version of his kitchen here without creating new thread.
What has been changed ?
"Virgin" kitchen was only for packages modification without any pagepool changes or xip porting. Leeston2379 was basing on l3v5y kitchen which have certain bug. Interestingly this bug was "not active" as far as old ( original ) xip.bin was taken in .tsw file creation.
There are 4 batch files for new system building:
a) 2. build_without_xip_port.bat - the same as original leeston2379 batch but with fixed bug although here it is not "active"
b) 2. build_without_xip_port_pagepool_set.bat - allows to set pagepool size
c) 2. build_with_xip_port.bat - like original but allows to port new xip
d) 2. build_with_xip_port_pagepool_set.bat - like original but allows to set pagepool size and port new xip
I did not utilize automatic execution via for example
AutoExecAndClick.exe /launch "xipport.exe" /clickbutton "dump xip.bin" /clickbutton "write maps" /clickbutton "make pkgs" /kill
In my oppinion it is buggy . There are any timing races or something other causing any strange errors from time to time. User has to like in original l3v5y kitchen press different buttons in xipport software.
Thanks Mangasora for his post concerning porting xip
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
2. build_without_xip_port_pagepool_set.bat is my mod based
on leestone 2. build_without_xip_port.bat. bug?
please explain a little bit better: what you have do, what changed, the method for xip porting and how works? i hope is testet from you