Related
Hello ALL!
Here is the long awaited HTC Tornado ROM kitchen
This Kitchen is in actual fact the Molski DEVPACK kitchen but its been MODIFIED by myself, Duke_Stix in order to be compatible with the HTC tornado and to make rom editing and cooking easier for EVERYONE!
Please note, before anybody starts pointing fingers, FULL permission was obtained from molski himself before any modifications were made and full permission was obtained in order for me to release this kitchen as the initial kitchen was of course, by MOLSKI!
This was the first kitchen that i learnt to use so it was the first kitchen i modified!
There will also be a modified CORE kitchen released soon too once i can iron out any and all bugs.
Anyway:
Pretty simple to run really. heres a few instructions to get you all started:
Download the attached file: Molskis_Devpack_modified_for_tornado_by_duke_stix.exe
READ THE PDF FILE THAT IS IN C:\DEVPACK\tools\batch\readme
Here are steps:
1) RUN the executable file, you should end up with TWO folders, DEVPACK and Molski.biz Devpack. MOVE the 'DEVPACK' folder to the ROOT of your C: drive.
2) Place ANY nk.nbf that you wish to 'unpack' into the source folder of the DEVPACK folder. so.....
' C:\DEVPACK\source ' Contains your NK.NBF file
3) Go to your desktop and into the 'molski.biz devpack' folder, this has lots of little shortcuts in it.
4) first of all, click the 'dump rom' script.
5) Let it do its thing
6) in the C:\DEVPACK folder there should now be a new folder called......ROMDUMP! (<-- guess whats in here?!)
7) Edit as much as you wish, dont forget to get rid of the first two bytes in the initflashfiles.dat file before you build rom again
8) once you've clicked the 'build rom' script go back into c:\devpack\tools and in there should be nb2nbf_tornado.exe
9) open that, dont touch anything atthe top apart fro the output field, here, I would suggest selecting your desktop and you MUST issue the file name as 'nb.nbf'
10) below that click the tick box next to 'File #1:' it will allow you to select 'file #1' point it to c:\DEVPACK\ROMDUMP and to the file called 82040000-OS.nb
11) back in the nb2nbf program select 'OS' under image name
click translate
go to your desktop, move the nk.nbf file there into C:\DEVPACK\tools\RUU_2001
run the 'ROMUpdateUtility.exe'
and away you go! should start flashing
IT IS IMPORTANT THAT YOU READ THE README FILE! i will also attach it to the post
also, anyone willing to donate can send any paypal donations to [email protected] and reference them 'duke'! very much appreciated!lol
MIRROR:
http://www.megaupload.com/?d=VWCLXM6Z
ENJOY!
post any questions here
AND DO NOT FORGET TO READ THE README FILE!!!!!
ALSO READ: http:\\www.molski.biz
HAPPY COOKING!
duke_stix said:
How to use this Rom Cooking Pack:
I tried to make everything as simple as possible, still you definitely need to know what you are doing!
Step 1:
Extract the nk.nbf file from a Rom archive (all Rom archives can be opened with tools like WinRAR) into the X:\DEVPACK\source directory.
Step 2:
Execute the DUMP_ROM script when the script is finished a ROMDUMP folder is created in X:\DEVPACK, with all the .nb files found in the nk.nbf file, the 80040000-OS.nb file will be splitted into 2 template (.bin) files and the contents of the OS templates is placed in the “dump” folder.
Step 3:
When the script is finished you can start adding and deleting (watch out what you delete!) files in the dump folder.
Step 4:
Editing the initflashfiles.dat file!
Execute the EDIT_INITFLASHFILES script so the file gets copied to the ROMDUMP directory, a backup of this file is placed in the Backup folder inside the ROMDUMP directory!
This is a very important file, when the Wizard gets a hard-reset or is flashed to another Rom, this file builds the directory structure, copys files from Windows to (as example) the Program Files directory.
These are some examples from the initflashfiles.dat file:
root:-Directory("My Documents")
Directory("My Documents"):-Directory("My Pictures")
Directory("\Windows\Start Menu")ermDir("Programs")
Directory("\Windows\Start Menu")ermDir("Settings")
Directory("\Windows\Start Menu"):-File("Messaging.lnk","\Windows\tmail.lnk")
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
Directory("\My Documents\Templates"):-File("love.gif","\Windows\love.gif")
As you can see, not so tough as it looks, I am not going to explain every single line of this file, but will give you one example….just to make things a little bit easier to understand!
All files from the “dump” folder are basically placed in \Windows and get copied to other directories from this point, so when a shortcut is copied from \Windows to \Windows\Start Menu\Programs you will have a shortcut in both directories (but that’s not a big deal!).
I am going to explain this line, to let you know what this line actually does
Directory("\Windows\Start Menu\Programs"):-File("File Explorer.lnk","\Windows\fexplore.lnk")
The shortcut fexplore.lnk in \Windows gets copied to the \Windows\Start Menu\Programs directory and gets renamed to File Explorer.lnk
Very easy….isn’t it? J
So…after adding all files to the “dump” directory, adding the lines of the added files (IF needed) to the initflashfiles.dat file you can save this file, make sure the last line in this file is a blank line (otherwise your device will be stuck at the second Splash Screen)!!
Example:
When you want to add a program named ABC.exe to \Start Menu\Programs, just copy the ABC.exe file to to the “dump” folder and place a shortcut named ABC.lnk in the “dump” folder and add a line for ABC.lnk into the initflashfiles.dat file.
To create a shortcut for ABC.exe, simply open Notepad, create a line like this:
24#"\Windows\ABC.exe"
(the number can be different), save it as ABC.lnk and add this to the initflashfiles.dat file:
Directory("\Windows\Start Menu\Programs"):-File("Alphabet.lnk","\Windows\ABC.lnk")
In this example the shortcut ABC.lnk, that points to ABC.exe gets placed in Programs with the name Alphabet.
After saving the initflashfiles.dat file, open the file in WinHex and remove the first 2 bytes (FF FE)!
If you don’t remove these 2 bytes your device will also be stuck at the second Splash Screen!!
After removing the 2 bytes and saving the file you can copy it to the “dump” folder (overwrite the original initflashfiles.dat file….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 5:
Editing the HV Files!
Okay, let’s say that the application used in the example (ABC.exe) has a few Registry Values and will not work without it, therefore we will need to edit the default.hv and/or user.hv files.
Execute the script CREATE_RGU_FILES, this will copy the default.hv and user.hv files from the “dump” folder into a directory called HV Files in the Romdump directory and convert the 2 .hv files into .rgu files so we can edit them with notepad.
When editing .rgu files there are 4 things that are very important!
Turn off Word Wrap in Notepad
The 1st line is a blank line, type “REGEDIT4” (without quotes) on this line
Make sure the last line of the file is a blank line
Make sure the files are saved in Unicode and not in ANSI
The Windows Mobile Registry has 4 keys:
[HKEY_CLASSES_ROOT] à These Registry keys gets insert in the default.rgu file
[HKEY_LOCAL_MACHINE] à These Registry keys gets insert in the default.rgu file
[HKEY_CURRENT_USER] à These Registry keys gets insert in the user.rgu file
[HKEY_USERS] à These Registry keys gets insert in the user.rgu file
When you are finished editing the .rgu files, execute the CREATE_HV_FILES, watch properly of the files get converted without errors, if everything went okay, copy the default.hv files from the HV Files directory to the “dump” folder (overwite the original files….don’t worry, you still got the backup of the original file in the Backup folder)!
Step 6:
Okay, by now we have extracted and dumped the nk.nbf file, added and/or removed files from the “dump” folder, edited the initflashfiles.dat file, added registry values in default.hv & user.hv and copied the 3 edited files to the “dump” folder.
Now we are (finally…) ready to build the Rom!
Execute the script BUILD_ROM and wait till it’s finished (will take a couple of minutes depending on the speed of the computer).
This script will add the modified “dump” folder to the OS template files (.bin files) and when that is done it will build the 8004000-OS.nb file from the OS template file.
[\QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
reserved yet again
Thanks a lot for this tool i'll look that when i will go at home.
Thanks for all your job
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
ericjm said:
can't get to megaupload.
can you upload it to rapidshare? thanks for your work.
Click to expand...
Click to collapse
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
burkay said:
http://rapidshare.com/files/46589256/Molskis_Devpack_modified_for_tornado_by_duke_stix.exe.html
Click to expand...
Click to collapse
thanks dude!
anyone tried this yet then?!
\
im awaiting feedback!
When I tried to dump rom, I get this
Splitting 80040000-OS.nb into .bin files....
Unable to open source image [80040000-OS.nb]
Creating Dump directory....
Dumping Rom content into dump directory....
Please wait a couple of minutes, depending of the speed of your computer!
Dump folder is ready in ROMDUMP directory!
Press any key to continue . . .
Why is it that I am unable to open source image ?
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
jm012a9749 said:
Looks like duke stix forgot to add a rename command in the batch file.
The wizard NBF WDATA start address for the OS is 80040000 and the tornado WDATA start address is 82040000, so rename 82040000-OS.nb to 80040000-OS.nb and it should work.
Phil
Click to expand...
Click to collapse
Actually im dumping using Mozbi Devpack for Wizard, thought it is the same, it works now.
Thanks
oioi
I'll get to changing that right now. didnt notice that!
Good tools and good explanations.
I dumped I rebuilt a Qtek ROM today for my wizard, and the advices of this thread were the biggest help.
Thanks and well done.
Customized ROM hanging in spash screen
Hello Duke,
I am currently in the process of customizing my own ROMs from other user builds thanks to the tools you provided. I am having problems though...I have used multiple nk.nbf (different os) files and dumped then rebuilded without modification just to make sure I have the technique correct. That is without modifying initflash or hv files and going right to rebuilding after dumping and I am hanging on the first screen. I then need to manually go to bootloader for reinstall.
I then checked with my modified ROMs following pdf religiously (ie deleting first 2 bytes and leaving last empty line-initflash...and adding REGEDIT4 and leaving last line saving as unicode-rgu...following instructions provided) and yet I continue to hang on the first screen.
Do you have any suggestions??
Thanks again,
vjgrace
First off what program do you use to modify dsm files? Also in my OEM_Lang_0409, OEMAPPS and OEMDrivers folders after I make changes (delete unwanted files and folders) when I push the COOK buttom it goes through the buildOS program file and creates a bunch of dsm files in these folders above. My problem is when I look at the dsm files in each folder they contain all of the programs and files I have deleted and also some other files I dont want. When I try to modify the dsm files I get an error message when running buildOS program and It wont let me flash the rom. How can I modify these dsm files to get rid of the things that are no longer in the folder? What exactly does a dsm file control? Will getting rid of the names in the dsm files that are no longer in the system help me at all? When I look at other peoples cooked roms the dsm files that I am talking about match what files and programs are in the above folders. I hope this makes sence. Thanks for the help.
I have been messing around with cooking roms for a few weeks now. I have cooked up a rom (New Att Rom) that has these numbers.
Total Storage: 166.16mb (Free 164.27mb)
Total Program: 101.38mb (Free 75.28mb)
I am trying to make this Att rom as clean as possible. I have removed abosultly everything that I can. I have a few questions though as Im being kind of a perfectionist. When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom (for example transcriber or sim manager registry keys) I have edited the proxml files and they are not the curlprit. I have checked the .RGU files and there is only two in the whole rom (one is boot.rgu and the other one has only one entry in it) I have also checked the initflashfiles.dat file and edited it but it doesnt have the registry keys I am looking for either. Where is the main part of the registry in these roms?
Another question I have is why the dsm files (when opened in a text editor) show other programs or files in them. I would like to delete the microphone, clear storage and key lock app or the TTY icon in the settings screen. I have found these files in the DSM files but they cant be deleted. Is there a way to edit the dsm files or are they updated when other changes are made?
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Has anyone figured out a way to get the memory back when a memory card is placed into the phone? I would be around 79mb free program memory (before speed tweaks) if someone figures this out!
I will have a few more questions probably but I cant remember them right now. The rom I have made is working very well and is stable. I just want to make sure all of the trace files in the registry and other places are gone. Thanks for the help
All of the pros must be working on their own roms, look at how many have been updated! Someone must know the answer to a few of these questions. I dont mind doing the work I just need a few hints!
hollywood said:
When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom
Click to expand...
Click to collapse
Default.hv and User.hv are the default and user registries where you will find the entries.
hollywood said:
Is there a way to edit the dsm files or are they updated when other changes are made?
Click to expand...
Click to collapse
There's a app that does it in the general section under hacking IIRC search for build dsm that should bring it up.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
Yes.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
I beleave the answer to this is no... the dump you get is the unmodiffied ROM you have after flash it... all changes after this are not dumped.
Cheers.
Great info thanks guys
What program do you use to edit the default.hv and user.hv? Thanks again
hollywood said:
What program do you use to edit the default.hv and user.hv? Thanks again
Click to expand...
Click to collapse
You can not edit directly, you must convert from .HV format to REG (text) format using RGUCOMP.EXE (included in KaiserKitchen) to edit, and once edited, convert back to .HV with the same tool.
Code:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
Cheers.
Great info. I have cooked up a rom and I am having a hard time figuring out what is causing the screen delay in my registry settings. Does anyone know what setting is causing like the three second delay in the screen going from landscape to portrait? Thanks
SO if I understand you correctly.
I can open the files, edit in all of my reg edits (particularry the ones I can not export) and recompress it with RGUCOMP.EXE and cook my edits into my rom ?
Ok I tried this and finally figuted I have to do it from a command line.
WHen I do
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
I get fronm the txt file:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
obviously I am doing something wrong, but I have no idea what.
Hi guys,
I wanted to start cooking my own ROM and was wondering which kitchens are available that i can use. The only ones i know of are:
1) Hypercore kitchen by anichillus (http://forum.xda-developers.com/showthread.php?t=324682)
2) Beasty and Leo's Kitchen (only saw the snapshot in one of their posts, dont know where i can get it from)
What other options do i have when it comes to ROM Kitchens? And what exactly are the pro's and con's associated with each of the kitchens you mention!
A quick reference to some tutorials and how-to's would be awesome too I've already got some reading material but, the more the better!
I'd really appreciate any help i can get.
Thanks!!!
really, noone?!?
thingonaspring is offering a kitchen from his 3.2 rom, he added a cooking tutorial.
http://forum.xda-developers.com/showthread.php?t=332737
best kithen its kithen which you create by yourself .and for your own... mine for example
2 bat files ... pack and unpack
unpack
1. extracts nbf file
2. extracts nb file content
3. creates packages ...
4. extracts xip.bin and xip contents to folders near sys and oem
5.. system metafiles ( old reg ... initflash files .. and others ) place near sys as meta folder
6. all rgu files from packages hey copy near sys and oem folder as reg folder .. with mark of priority while assembling
after all
sys folder
oem folder
xip folder
xip extended folder with xip.bin and other xip related extracted stuff
reg folder with rgus
meta folder
pack.bat
1. promt .. what rgus use for assembling .. placed in packages or placed in reg folder
2. creating dump folder
3. calculate rom space .. if they exeed standart process brakes
4. injecting xip_out.bin in nb file
5. creating nb.new file
6. assembling nbf file
quadxeon said:
thingonaspring is offering a kitchen from his 3.2 rom, he added a cooking tutorial.
http://forum.xda-developers.com/showthread.php?t=332737
Click to expand...
Click to collapse
I've downloaded thingonaspring's kitchen. Will look into it as soon as i get free from work!
mo3ulla said:
best kithen its kithen which you create by yourself .and for your own... mine for example
2 bat files ... pack and unpack
unpack
1. extracts nbf file
2. extracts nb file content
3. creates packages ...
4. extracts xip.bin and xip contents to folders near sys and oem
5.. system metafiles ( old reg ... initflash files .. and others ) place near sys as meta folder
6. all rgu files from packages hey copy near sys and oem folder as reg folder .. with mark of priority while assembling
after all
sys folder
oem folder
xip folder
xip extended folder with xip.bin and other xip related extracted stuff
reg folder with rgus
meta folder
pack.bat
1. promt .. what rgus use for assembling .. placed in packages or placed in reg folder
2. creating dump folder
3. calculate rom space .. if they exeed standart process brakes
4. injecting xip_out.bin in nb file
5. creating nb.new file
6. assembling nbf file
Click to expand...
Click to collapse
Do your Pack.bat and Unpack.bat files work for ANY NBF files or only for the kitchen you use?? If they work for all NBF files, is there any chance you could provide me with those batch files?
1. any nbf file placed in source folder may be unppacked
2. its not only bat files .. primary its a complex of unreleased progs
3.. no chance .. becose this kithen i made with cooperation with 1 mad programer .. who not like freeware licence
mo3ulla said:
1. any nbf file placed in source folder may be unppacked
2. its not only bat files .. primary its a complex of unreleased progs
3.. no chance .. becose this kithen i made with cooperation with 1 mad programer .. who not like freeware licence
Click to expand...
Click to collapse
perfectly understandable ... any chance you could help me build my own kitchen? i've got over 6 years of programming experience in over a dozen languages. you'll just have to provide me with guidelines. possible??
How to clean up my windows folder
- Remove touchflo 2d
- remove Htc Home plugin
my folder size more than 136 mb :S make my deivce so heavy :S
Dr.Mazika said:
How to clean up my windows folder
- Remove touchflo 2d
- remove Htc Home plugin
my folder size more than 136 mb :S make my deivce so heavy :S
Click to expand...
Click to collapse
install a clean rom, or customize your own. the windows directory is going to be a little large regardless, the operating system is there..
what is the normal size of windows folder
any how can i customize my room to remove and add new applications
That's basically what got this community started... just about everyone here can testify to having looked into ROM Cooking... please research before asking how to do it, because I PROMISE there's a thread or two out there about it
Clean windows folder possible ?
I'm trying to cook my own rom but when I add an EXT module, all files are in Windows directory and the app.dat file only copy them in the app directory.
So is it realy possible to have a clean windows directory, how to put files directly in app folder? must I use an OEM module with initflashfile or ???
thanks all
superraoul said:
I'm trying to cook my own rom but when I add an EXT module, all files are in Windows directory and the app.dat file only copy them in the app directory.
So is it realy possible to have a clean windows directory, how to put files directly in app folder? must I use an OEM module with initflashfile or ???
thanks all
Click to expand...
Click to collapse
All files go into \windows. The first thing you need to ask is this: do I need to copy the file into another directory, like \program files? A lot of apps work just fine if you leave all of the files in \windows. The files are going to be in \windows in one form or another, so you save space by just running the app out of \windows. You need to change shortcut paths and sometimes registry key paths to get this to work, but in my experience, it works about 95% of the time. Usually, if you've got a multi-component application (several files besides just the .exe), the .exe will search for other files it needs to run in the same directory that the .exe is located in, so you're good to go if everything is in \windows. Some apps have sub-folders, so you'll have to get that folder and its contents into \windows. The best way to do this is with a .cab file or a zip file during customization (using a mortscript for the latter). Zip files are nice, because they install really quickly and are easy to make and edit.
Anyway, if you need to get files into another directory for whatever reason, I'd say that the app.dat method is probably the worst, because if you have multiple files, then you increase the file count in \windows by that amount. Put them in a zip file or a cab file, and then you'll reduce the file count to 1 for the particular package. You will also compress the files, and save some rom storage space.
You can also look into \extendir for another method to clean up the \windows directory.
You do need to be careful with some apps if they have an .ini file or an .xml file or something similar that is basically a settings file. It's usually better if these files aren't read only, so you may need to figure a way to copy the file into the \windows directory.