Database Info

[RELEASE]{02/08/2007}MODIFIED Molski Devpack Kitchen for HTC Tornado [by Duke]

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

OEM Package Tutorial [Updated 2008-01-31 - New wiki layout]

Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
12-07-07 Update: Major overhaul with more content! Great read for all cooks and chefs...
OEM Package Tutorial​
If you have any comments or questions about this tutorial, please reply to this thread. Thanks!

Nice, thanks!

_Alex_ said:
Hello!
I thought I'd contribute back to the Kaiser community by starting a wiki page with what I've discovered about packages while cooking and cleaning my own ROM.
Most of the material I've read is outdated and scattered, so hopefully this will save time for novice chefs.
Please note that this is the first draft / rough outline. More content to follow...
Kaiser OEM Package Tutorial
Click to expand...
Click to collapse
Great
Really good contribution... I'll add a link in the KaiserKitchen second post...
Cheers.

Nice Work...
Its always nice to see some of the newer members active and contributing. The write-up is good and I think it will help a lot of Rom "Sous" Chefs as they start experimenting with their own creations.
BTW, thanks for the kudos. The best pay-off is seeing that my efforts have inspired others to strike-out on their own. I also want to say good work on adding a Wiki page instead of just leaving the info in a thread somewhere.

Great guide.
Makes me want to try it.​

Just go to my signature, i have wrote it too,.

Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.

_Alex_ said:
Garmin, that's a great tutorial for the manual process for converting OEM packages to cabs.
Just wanted to make sure you're aware that Ervius package creator automatically converts cabs into the following, which makes things alot easier:
initflashfiles.txt from file structure found in cab
links found in .inf and/or setup.xml
randomly generated UUID
rgu from setup.xml or .inf
option.xml
Hope this helps.
Click to expand...
Click to collapse
hehehe,.
thanks buddy,.
but many people dont understand it like you did,.

yeah agree nice one mate, Great idea.

True, i do build upon existing works to inform folks of the most efficient way to build an OEM package...
I've added your tutorial into the wiki page as a 'primer', should anyone not understand my text.
Maybe I'll find the time to write my own primer, or someone else could take up the challenge?

Folks, all in good intention but the Tutorial is fairly steep.
I don't consider myself is all thumbs but plowing through them is going to be not just a week effort and at the end it is still in monkey see, monkey do level.
To put it in a simple way, (I will stand for correction). Most people who strode around this forum is only expected to spent "Basic" level in stead of "C++" level programing effort to get what they want or solve their problem. Most will only have the ability to play with a few different ROM's but not to cook them. I really like Palm, it is much simpler and much faster machine for given same horse power. But its founders just grabbed the money and went fishing and left it to rot and we have to entertain M$.

My intent was not to write a tutorial understandable by all, as clearly stated within the preface. The tutorial is geared towards intermediates who have already dabbled.
The tutorial that's missing is the ROM kitchen one. In the ROM Kitchen thread, jcespi2005 says he has one in the works, so I didn't want to step on his toes. When that comes out, I would hope for it to be alot easier to understand than my intermediate OEM package tutorial.

I've done a major overhaul to this tutorial, knowing that more people will be reading it with the release of the Kaiser ROM Kitchen tutorial...
It should prove to be a good read for all interested in building OEM packages.

Need help for not able to convert .cab to Package
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?

jychan28 said:
I was trying to convert some .cab files into Packages using Ervius Package Creator. Following the instruction 1. Click on "Open CAB file" and select a cab file to convert.
Then I just pick a .cab file (tried different ones but same error message)
Before I could go to the 2nd step of "Extract CAB files with original names in a folder", I got the error message:
x Erreur d"insertion de ligne RichEdit
I can't read Italian ?!
What went wrong?
Click to expand...
Click to collapse
Hi... I went to google translate and translated the french error message from MSCEINF which means 'Error of insertion line RichEdit'. This doesn't mean much to me either
If you run MSCEINF.exe, click on the first icon cab with the caption 'Choose a CE installation file', open the cab and click on the icon with the caption 'Extract CAB Files with original names in a folder', does the same thing happen? If so, you may need to ask the original author. His thread is here: http://forum.xda-developers.com/showthread.php?t=347397&highlight=msceinf
Hope this helps...

Alex, I downloaded all you files and setup all the file directories as described. I downloaded more packages.
I want to add a few more .cab and needed to convert them into packages.
It was frustrating for hours. I have re-download the MSCEinf.exe file a few times.
I Unziped it and renamed it to MSCEinfen.exe as instructed.
Then click on packages creator 5.4.exe, check the boxes as instructed.
Click on Open cab file, select a .cab file in one of the directory, then it automatically execute MSCEinfen.exe and the error message poped
I even tried to execute packages creator 5.4.exe in a DOS black box. Same problem and same result.
Click on anything else will eventually cancel the procedure and back to square zero.
What could be the problem?

I Got The Same Problem.
I'm confidence that I strictly follow the instruction of converting cab to OEM package, and got the same error message like you do.
I try to translate the message with google, looks the language is French translated to English as "Error inserting line RichEdit".

Good News, I just solved this problem in my machine.
I changed the "Language for non-Unicode Program" to "English (United State)", the error message gone, and my MSCEInfEn works well now. I not sure it works for everybody, welcome to post with your result, maybe in other language. Thanks.

Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike

ecltech said:
Anyone getting an Unhandled exception error after clicking on "Go"? I've done the following:
1) DL and Extract kaiserkitchen
2) Extract the build/package tools (3 files) to the folder where I installed kaiserkitchen
3) DL and Extracted AT&T Ultraclean ROM folders (3 folders) to the kaiserkitchen folder
4) DL and extracted AT&T OEM packages
When I start up the program I can select the AT&T OEM Packages. I left at default and hit Go but get the unhandled exception error.
Also, it doesn't seem like the AT&T OEM Packages contains any Registry Tweaks. Is there a separate package to dl that contains the registry tweaks? A few days ago I know there was an AT&T OEM package that had the registry tweaks.
I'm attaching a capture of the error. Appreciate any feedback.
Thanks.
Update:
I tried doing this again with ROM Folders and AT&T OEM Package I downloaded on 12/8/07 and it works fine. No error when building as outlined above.
-Mike
Click to expand...
Click to collapse
See these posts: http://forum.xda-developers.com/showpost.php?p=1745239&postcount=105, http://forum.xda-developers.com/showpost.php?p=1747265&postcount=117 & http://forum.xda-developers.com/showpost.php?p=1747298&postcount=119. Alot more info can be found in that thread, so you might want to read up there...
Hope this helps...

OEM Package making question

I have a cab with the following extentions
_setup.xml
JETBTC~1.001
JETBTH~1.000
JetBTHFix.002
JetBTHFix.999
I added the .dsm & .rgu files
I edited the _setup.xml file to redirect the Shortcut to a different folder.
Is that all I need to do?
Will it work puting it into an OEM folder now?
Can I remake it back into a cab file? (How do I make a cab file)
Thank you

You can't open a cab with a simple unzip program (which appears what you have done). You have to use a program that can pull a cab apart. In HyperCore there is a free utility that will do this (sorry, not on my computer with a kitchen so I don't remember what its called, but its in the tools and/or panel area of HyperCore). You can use Cabwuz (demo version) to see what I mean also.

MSCEinf
Its a tool called MSCEInf.exe, Windows CE CAB Analyser. It opens up Windows Mobile .CAB files and creates the original files and installation options (registry changes, shortcut creation etc).
http://www.codeppc.com/telechargements/msceinf/msceinf.htm
Andy

Ok I got the program up and running, but not sure how to use it. There seems to be no help files.
Anyone know how to use this. Can you give me a quick run though.

All that MSCEInf.exe does is extract the original files and settings from the .CAB file. What you should do is extract the files to a folder, then if the XML button is available click it and then look at the Registry Keys and Shortcuts tabs to see what shortcuts you need to create and what settings you need to add to the .RGU file. If the XML button isn't available then click the 'RTF Document' tab, this contains all the settings but is a bit harder to cut-&-paste from.
It is probably a good idea to look at on existing OEM package to see what files are included, what the shortcuts look like and what the .RGU file looks like.
HTH
Andy

Little more help.
Ok need a little help still.
This is what I have done.
1) created a folder with in the OEM folder called JETBT
2) Opened Msceinf
3) Loaded my cab file
4) Changed "Use Folder Name" to NO
5) Pressed "Extract Cab files with original names to a folder"
6) Extracted them to the JETBT folder I credated.
Now this is where I am at.
I have the following 5 files.
_setup.xml
BT HFP Extension 1.31.inf
JetBTConfig.exe
JetBTHFx.999
JetBTHFx.dll
I know I need to create a .dsm and .rgu file
the .rgu file is where I add reg entries
I also know I need to make a inirflashfile.dat
which is where I have it move the .ink file.
First how do I make a .ink file.
Then is this all I need to do?
Does the OEM folder us the info inside _setup.xml ?
If it does can I simply edit that file. Inside I see where it makes and moves the .ink file
And where it adds the reg info.
I could simply just add the info into that file.
and then create empty .dsm and .rgu files.
So what do I need to do? Am I missing any steps.
there are other cabs I need to edit aswell.
Thanks for your help.

? Anyone? PLEASE

Read my OEM package tutorial. 95% applies to all phones and Ervius Package Creator is the greatest thing to OEM packages since sliced bread

Thank Man!

Create OEM Packages

Hey guys I would love to make some OEM packages from Cabs, but when I try InitFlashFiles Generator it just exits and doesn't work. So how do I create initflash and .rgu s ?
Important is how do I create the .rgu names? Just random? The initflash is not a problem!
Problem solved: http://www.famkruithof.net/uuid/uuidgen

you could try ervius package creator

Yeah I tried that before, but it exits with an error! It's ok now, I just create the initflash manually!

I would love to use it, but when I extracted the cab with MSCEInfen.exe and close it, I get an error and the initflashfiles tab doesn't open when I click continue and I can't open it manually! It looks like the same error you get when you open it! Any ideas?? It is a pain to create all by yourself!

http://forum.xda-developers.com/showpost.php?p=1761005&postcount=405
try that link, i think it might be his latest creator judging by the date
so here is what i do to use the program
i run the creator in its folder or by a link
i place my cabs in a different folder
click on open cab
browse for the cab
click on extract cab (zip icon without any extras on it)
click ok
click msce icon (running green man icon)
change options or click done
change options or click complete package
and that should be it hopefully

Thank you very much, this one works very good. With the last version I had an error with this one it works!

[20931 SYS/ XIP Ported]Improved PackageTools and BuildOS now for Wizard [29/11/2008]

I have been using many kitchens over the past year. Cooking horrible roms, decent ones and now a pretty good one. My problem was always the various tools lying all over my hard drive. Luckily I came across this litte gem by Ervius
Package Tools and BuildOS rolled into one. I also noticed that it handles rgu files much better than the previous BuildOS, it choked on an incorrect rgu file. Which in turn allowed me to get Video working in HTC Album 2
I have modified the batch files for our Wizards and have been cooking and im loving it
PackageTools+BuildOS (Latest combined version)
rgu-2-xml : Convert .rgu to provxml files
SYSVersion : Generates a version list of your SYS Folder
All the usual build tools :G'Reloc, M'Reloc, ImgFS Tools
AllPackagesToOne - Protect your rom from being ripped apart and the whole world being able to share in your utter cooking brilliance, via a tickbox ofcourse
Automatic Find and Fix duplicate file errors during BuildOS process
More features which I am either too lazy to list or dont use at all
Just add SYS,ROM and OEM folders. It also have a nice feature which allows you to select OEM Packages and save it as a preconfigured rom. Extra OEM packages can be placed in a Packages folder. BuildOS will load those files also (No more OEM's all over your hard drive).
BuildOS also runs G'Reloc during the dump process, but for good measure I also included it in the batch file.
Also added -conservative to the Imgfs Tools portion of the script to protect against overcook
BuildOS generates pretty log files which shows where stuff went wrong
Extract the zip file. Run Kitchen.exe and watch the magic at work.
Note
For some reason the output window text is black on a black background, but at the top is a nice running status. If not sure just hilight the output window.
If you start up and It complains about folders just create them
Download
Ported 20931 SYS/XIP without PIE 6 download
Microsoft Visual C++ 2008 Redistributable Package (x86) is need to be installed in your PC
[URL="http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en]Get it here[/URL]

Hi,
Nice kitchen.
But its little bit difficult compare to hypecore.
Thanks for great kitchen.

Nice release ..i think im gonna start cooking too

Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?

Noonski said:
Does it also have my favourite tool "Alpackagestoone" to remove and merge DSM and RGU files from Rom?
Click to expand...
Click to collapse
It does, in the prettiest little tick box you have ever seen, just below the Output Window. One of the really cool features of this version of BuildOS is the ability to scan for and fix duplicate files

sounds really impressive! downloading...
I'll recook my rom with it and let you know how it went

where should I extract this kitchen?
Error: pkgdll is missing
Never mind. copied it to the same folder as the kitchen.exe

I cant cook... .net problems
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.

+ Que PPC said:
Many problems with the kitchens... why I cant install .net frameworks more than 2.0 that i have why... cause It said on every reinstalation missing file the installer will be quit! GOD DAmn... I think I need to reformat my PC and almost backup 40 GB info or... does anybody has an utiliti that erase all of anay program that stucks on uninstall or repair or install? i need to kill those .Net frameworks.
Click to expand...
Click to collapse
What OS are you running on your pc ? .net 2.0 and higher really like XP Sp2. Do a google search for CCleaner and "Uninstall Utility" this might help before you format dude.

Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.

S.V.I said:
Errors I am facing:
can not find \ROM folder
Windows can not open this file: OS.NB.Payload
Windows can not open this file: OS.NB.extra
BuildOS: Error, can not find ROM Folder!!!
Where are these files supposed to go? can you provide a tree map?
Can you also tell me what exe opens what file?
I'm almost having to pour cold water over my self
The main issue is not knowing where the ROM folder is supposed to go.
Also, not being able to see what the thing is doing (black on black) is really frustrating me also.
When you get a chance, let me (us) know how to use this cooker. it looks like it can do a lot more than I'm used to... but at the moment I am finding it useless.
Click to expand...
Click to collapse
I really wish I could decompile and just fix the black on black issue. Coz it is a simple case of just changing the font. Unfortunatly it is not written in .net like the previous BuildOS, so no luck there
This should be your default layout:
Base Folder-
->Compile Tools (OS.nd encoding tools)
->Flash (Created by Batch file, your new OS.nd ends up here)
->OEM (I like to put the BASE OEM Folders in here OEMAPPS etc)
->Packages (This is where I drop my custom OEM folders)
->ROM (OS.nb XIP,romhdr.bin lives here)
->SYS (Yeah well we know this one)
The error you are getting is when you try and extract a rom with Package Tools in the kitchen. Here is the procedure:
Create a base folder, I normally use Base_Buildnumber_Device
Select your Dump Type in the bottom check boxes, either a folder where you have already dumped a rom or an *.nb,*.nbf type file
Start your kitchen and select Open on the Package Tools tab.
Browse to the folder you have just created select the folder of rom file based on the above selection
Package tools will now extract the rom and create OEM and SYS Folders if possible
In case of cooking which I believe you are after:
Create the above folder structure with all files in place
Select BuildOS tab
Click Load Rom
Edit OEM's etc and just press Go

thank god u placed this tut, i thought i was the only one with theis prob oO
I'm almost having to pour cold water over my self
Click to expand...
Click to collapse
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S

ather90 said:
thank god u placed this tut, i thought i was the only one with theis prob oO
you were "almost" but i already did several times, what more do you expect if your working on Core,Improved Pakagetools, Molski Devpack,tnt kitchen and Porting :S
Click to expand...
Click to collapse
Dude I battled to get the whole thing running as the tut's where for Kaiser and the tools were abandoned by the looks of it. But once i started using the cool right click and import package features I was sold.

Sorry. double post.

->ROM (OS.nb XIP,romhdr.bin lives here)
That may be what I am missing. how do I extract that?
I Have OS.nb; XIP.bin XIPfolder

@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread

->ROM (OS.nb XIP,romhdr.bin lives here)
Click to expand...
Click to collapse
should the XIP be in the bin extension or in a folder the one which Hyper Core Generates) ?

ather90 said:
@S.V.I Here is the romhdr.bin : http://forum.xda-developers.com/attachment.php?attachmentid=131286&d=1227164342
@cornelha i think u need a break lol you attached te file in the siff thread
Click to expand...
Click to collapse
OMFG dude I think you are right. Dev by day ... cook by night ... hey wtf is my gf ?!?!?

how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??

fachry said:
how to use this kitchen??
i run Kitchen.exe from desktop, but error(installation error)
any help me??
Click to expand...
Click to collapse
Yeah I realised now that when I zipped up the Kitchen I left pkgcommon.dll in the Tools folder, this should be copied to the same folder as Kitchen.exe.
Your error however comes from me not stating the .net Framework 2.0 or highers is required. I take these for granted since I have Visual Studio installed on my machine anyway