Related
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)
As promised, here are Just2Clean's kitchen files. You will need to use either JustClean's EasyBakeOven or Bepe's kitchen in order to use them. Just download either of the kitchens, delete the OEM and SYS folders and replace them with these.
This does NOT include my micro Extended ROM, but if you've flashed my ROM, you already have it installed.
Linky It's the Working_Folder
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Thanks. I will try to cast some magic with this
(for personal use, of course )
macaraballojr said:
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Click to expand...
Click to collapse
This is not my newest build, this is the Just2Clean that I had already released. If you want to get a newer build, search for EasyPortOven 2.2 and use that to port over the ROM. It will change the ROM, though, as the SYS folder has been optimized. You'll learn more about this in one of my upcoming cooking lessons.
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
macaraballojr said:
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
Click to expand...
Click to collapse
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
ivanmmj said:
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
Click to expand...
Click to collapse
What would we do without u bro but many thanks for the info
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
slimag said:
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
Click to expand...
Click to collapse
One of the packages you chose is probably not compatible with Just2Clean. To make it compatible, read the error and it will tell you. If a duplicate file is found, delete the extra file from the OEM folder or the SYS folder.
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Ghostrider said:
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
Click to expand...
Click to collapse
What do you mean by not start up. There are MANY files and batch files and programs that work together as a kitchen. You'll have to be more specific. Perhaps a screenshot of what happens.
slimag said:
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Click to expand...
Click to collapse
You can't choose packages because the packages are all stored in the OEM folder. I forgot to mention that. Don't delete the OEM folder, just the folders in the OEM folder have the same name as the files in the other new OEM folder...
when I put the new files in the OEM and SYS Folder it say's BuildOS.exe don't work anymore, The Program has an Problem, and must be Closed.
Then the same with Buildxip.exe don't work anymore.
Ghostrider
That means that there's a conflicting name on an RGU, DSM, or inside an option.xml. If you do not go through BuildOS, Buildxip will crash because it will not have something to build in the first place, as it's BuildOS's job to get the files where they need to be.
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
slimag said:
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
Click to expand...
Click to collapse
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
ivanmmj said:
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
Click to expand...
Click to collapse
I don't felt me insulted
I'm testing this now.
Ghostrider
Edit:
I have Just2Clean and MMS 3.5.1.24.R2 as UPX and non UPX deleting the UPX version did't do it. I deleted both the UPX and non UPX version in the Kitchen files for Just2Clean, and now it is working.
I don't have the Just2Clean Customization
Ghostrider
Great to hear!
There should be a Just2Clean customization there also. It's labeled "Customization - Just2Clean."
I think what he meant is that Just2Clean customization packages don't work.
I did as you suggested by deleting the .rgu and .dsm starting with Z, but that still didn't work.
The option XML file needed to be edited because it pointed to those Z files not the A files.
Not sure if just deleting the .dsm and .rgu starting with A would've worked because I didn't try that.
After deleting the UPXed packages everything works for me now.
NATF: the Kitchen
Please Read The Entire Thread Before Posting A Question.
This kitchen is based around the original KaiserKitchen. All the ingredients used in the v5 Final versions of my Kaiser ROM series are included.
Step 1: Download which build you want to work with.
KaiserKitchen - AT&T 3.57 OEM with 20755 ROM and SYS
KaiserKitchen - HTC 3.28 OEM with 20755 ROM and SYS
Step 2: CAB Files
NATF's CAB Collection
(NOTE: I did NOT create these CAB files. The original author information remains intact, but they have been edited to create shortcuts inline with the layout of my ROMs)
Step 3: OEM Packages
NATF's Customized OEM Packages
(NOTE: I created most of these packages myself from CAB files found all over XDA and the internet)
If this is your first foray into ROM cooking, please visit Alex's Cooking Wiki and take advantage of the numerous tutorials available.
Reserved...
i can't get the packages to load properly. the only ones that i am using are the ones that you uploaded in post #1.
An item with the same key has already been added
Click to expand...
Click to collapse
internetadam4657 said:
i can't get the packages to load properly. the only ones that i am using are the ones that you uploaded in post #1.
Click to expand...
Click to collapse
There are some duplicate packages in the archive (some are for the HTC build, and some are for the AT&T build). Make sure that you are not selecting any duplicates.
mirror please...
i'm not, its just attempting to load the packages so that i can select them. when i click ok on the error message it shows some of the packages but its not even half of them. i'm not sure what i did wrong. i've attempted cooking before and i looked at alex's tutorial and it shows that you put the OEM packages into a folder simply called packages which is what i did.
edit: i just tried to select my packages again, and it only loaded 14 of the 38 packages.
Todd, thank you for this great contribution to the community. Your work here will truly be missed when you move on to the Fuze!
internetadam4657 said:
i'm not, its just attempting to load the packages so that i can select them. when i click ok on the error message it shows some of the packages but its not even half of them. i'm not sure what i did wrong. i've attempted cooking before and i looked at alex's tutorial and it shows that you put the OEM packages into a folder simply called packages which is what i did.
edit: i just tried to select my packages again, and it only loaded 14 of the 38 packages.
Click to expand...
Click to collapse
Make sure you are running G'reloc immediately prior to launching the KaiserKitchen.cmd file. You do not need to change any values, just click Do It, and wait about 15 seconds.
You are correct that all you need is a folder named Packages in the same location as OEM, ROM, and SYS. Which packages are you trying to cook in? Maybe a list will help narrow down the problem.
Alternatively, you can bring up the search box when inside the Packages folder, and search for "*.rgu". Then sort them by name, and make sure they all have unique names. If they do, then search for all "option.xml" files, and open them up. Check that the GUID IDs inside them are all unique.
If you have to go to the XML step, I recommend downloading and installing Notepad++. It is a freeware Notepad replacement that allows you to open RGU, XML, and PROVXML files in 1 tabbed window.
Is it already xmas time?
That's really a nice gift.
Thank you very much indeed.
Nice work NATF!!!
I love seeing people open up their kitchens & allowing others to improve or add to them as they see fit! It the sharing of knowledge that makes the XDA community possible & improves it.
I commend you on your open roms & making them easy to moddify & disassemble. We would be much further along in dicovering the ultimate potential of WM devices if more people approached the developmental & hacking tasks as you do. You are a definite asset to our community!
Nice to see more updated kitchens popping up with more & more options!
ok i figured out the problem, on my own even! there were 4 packages that were conflicting.
Package - HTC Home 2.1.1005.722 (ATT - Disabled by Default)
and
Package - HTC Home 2.1.1005.722 (ATT - Enabled by Default)
Package - NATF Reg Tweaks (ATT)
and
Package - NATF Reg Tweaks (HTC)
Somehow those 2 sets of conflicting packages were causing several other packages to fail loading as well.
internetadam4657 said:
ok i figured out the problem, on my own even
there were 4 packages that were conflicting.
Package - HTC Home 2.1.1005.722 (ATT - Disabled by Default)
and
Package - HTC Home 2.1.1005.722 (ATT - Enabled by Default)
Package - NATF Reg Tweaks (ATT)
and
Package - NATF Reg Tweaks (HTC)
Somehow those 2 sets of conflicting packages were causing several other packages to fail loading as well.
Click to expand...
Click to collapse
That's what I mean by multiple packages with identical GUIDs. Because I would never use 2 HTC Home packages in the same ROM, I mirrored the folder and then modified the RGU files as needed. As you can tell from the names, the first package was used for ROMs that contained HTC Home, but did not enable it by default.
As for the Reg Tweaks, the only difference between the two is that the AT&T one has the keys needed to remap the Tilt's keyboard.
ohhhhh!!!! ok! i gotcha now!
by the way, i forgot to say thanks for the release! i loved using the roms, and once i get this cooking thing figured out, i'm sure i'll really enjoy this too! by the way, is there a certain radio that you can recommend to use with this kitchen and any rom that might come out of it?
internetadam4657 said:
ohhhhh!!!! ok! i gotcha now!
by the way, i forgot to say thanks for the release! i loved using the roms, and once i get this cooking thing figured out, i'm sure i'll really enjoy this too! by the way, is there a certain radio that you can recommend to use with this kitchen and any rom that might come out of it?
Click to expand...
Click to collapse
I never distributed my ROMs with a radio. Since reception can vary so dramatically from location to location, I just pointed people to AllTheWay's Ultimate Radio Thread.
On a personal note, I was using Neon 1.58.25.17 from the day it was posted, and never had a reason to dislike it.
TreoFan! You are a god.
I am glad that we have chefs willing to share their builds. This community is about sharing not gross profit!
Not sure what I'm doing wrong here - I've read the tutorials and watched the screencasts, but i'm having problems. I put all my packages in a folder named packages, ran G'Reloc before running KaiserKitchen, and I'm getting errors. The error says "Double package or .DSM found! copying only from packages folder." Could it be because I used Cab2OEM to create some of my oem packages? I went through and made sure all the RGU's hade unique names and that the options.xml had the same GUID in it. What am I doing wrong?
riot1031 said:
Not sure what I'm doing wrong here - I've read the tutorials and watched the screencasts, but i'm having problems. I put all my packages in a folder named packages, ran G'Reloc before running KaiserKitchen, and I'm getting errors. The error says "Double package or .DSM found! copying only from packages folder." Could it be because I used Cab2OEM to create some of my oem packages? I went through and made sure all the RGU's hade unique names and that the options.xml had the same GUID in it. What am I doing wrong?
Click to expand...
Click to collapse
Make sure that you only put the packages you want to cook in the Packages folder.
If you are using any of my packages, then make sure you don't have any duplicates. For example, I have several HTC Home packages, but since I only ever use one, I did not give each of them a unique GUID or RGU.
NotATreoFan said:
Make sure that you only put the packages you want to cook in the Packages folder.
If you are using any of my packages, then make sure you don't have any duplicates. For example, I have several HTC Home packages, but since I only ever use one, I did not give each of them a unique GUID or RGU.
Click to expand...
Click to collapse
I only put about 10 packages in the Packages folder, and made sure each was unique. Could it be anything else?
riot1031 said:
I only put about 10 packages in the Packages folder, and made sure each was unique. Could it be anything else?
Click to expand...
Click to collapse
I'm having the same problems with packages not showing (only listing about 30 out of 50+).
Nice work on the kitchens. Thought i'd give them a whirl and used both for my personal ROM.
I experienced some weird issues with the ATT ROM: the backlight wouldn't work, sporadic freezing right after a reset (which i suspect could be from M2D), and screen freezes (which i'm aware that is usually caused by spl, however don't think it's the case right now).
I then decided to switch over to the HTC one and check that out and had the same problems. The freezing after soft resets (which causes yet another soft reset) and sporadic freezes have led me to think that it could be because of M2D possibly? I'm running SPL v3.28 which should run great on HTC ROMs (as i've used it in the past on my own ROMs). Any ideas or thoughts would be appreciated.
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
Hey there!
Iam relatively new to this world so i have some questions.. Iam coocking a rom for my blackstone based on the stock rom .. But i have some errors..
1. I need to replace the default netcf with the newest one (3.5) .. Iam not sure if it has something to do with the package i got hold of but if i just replace the package from sys with my one, netcf won't work on the phone.. Software that needs it gives me an error if i try to open it.. What have i done wrong?
2. I have made a OEM package containing some few regtweaks.. Some of those reg tweaks simply doesn't work! If i check the registry afterwards i have flashed the rom, they just haven't been created, while some of the reg tweaks from the same oem package has.. Iam talking specifically about these:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\HTC\EnlargeMenu]
"ManilaCustomHLUp"=dword:66
"ManilaCustomHLDown"=dword:CC
[HKEY_CURRENT_USER\Software\HTC\TaskManager]
"ManilaCustomHLUp"=dword:66
"ManilaCustomHLDown"=dword:CC
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:00000001
The file here is saved as Unicode .. The last reg tweak works but the others doesn't .. I have no idea why.. They simply doesn't exist if i check afterwards i flashed the rom .. Any ideas?
3. I wanted to replace the default start menu icon.. So i went for "SYS\Base_DPI_192\shellres.192.dll" opened the DLL with reshack and went for "Bitmap -> 292" And replaced the icon with a new one.. I then saved the file and used msigner to sign the file.. But this won't work either.. What am i doing wrong?
Hmm seems like i have to post this in some other forum ?
In theory, you should be able to swap the two netCF packages, and everything should work as intended. Where are you getting you 3.5 OEM pack from? Or are you making it yourself?
What may work better for regtweaks is to make a provxml file (a plain text file with *.provxml file extension) and create a new OEM pack with that in, and use BuildDSM to add the *.provxml to make sure it gets inserted when the ROM is flashed.
RGU->ProvXML converter
BuildDSM
Hope that helps!
l3v5y said:
In theory, you should be able to swap the two netCF packages, and everything should work as intended. Where are you getting you 3.5 OEM pack from? Or are you making it yourself?
What may work better for regtweaks is to make a provxml file (a plain text file with *.provxml file extension) and create a new OEM pack with that in, and use BuildDSM to add the *.provxml to make sure it gets inserted when the ROM is flashed.
RGU->ProvXML converter
BuildDSM
Hope that helps!
Click to expand...
Click to collapse
Actually i have allready fixed the two first problems.. for the first problem i took some netcf 3.5 oem and swapped some files from a pocket pc netcf 3.5 package i found @ microsoft which seems to be working.. don't know why the oem package i was trying to use didn't work though.. For the second problem i did as you told me which is working.. Thanks!
However i still have problems getting my custom start menu icon to work .. Have you tried cooking custom icons in a rom before ?
What didn't work about the custom icon? Did it not show up, or did the ROM not boot?
If it's the first, then there may be other icons in other files that affect it.
If it's the latter, it may be the image size, or something to do with the signing.