Related
Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar
Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!
More space for later use.
thanks. i'll give it a go later tonight
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy
I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..
the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works
I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.
i'll post the working one in a little bit.
edit... here's the one that works for me
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.
weird. intiflashfiles.dat copied over for me using 004's kitchen
I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.
Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.
Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,
You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
It does not need to be told how to do it, but told how to search ! A lot of people here know how to do it, just GOOGLE it !
sorry, I've already searched... Maybe I'm searching badly!
Could you please help me?
Basically you need to extract the ROM installer, you will find an nbf file in it, then get an NBF file converter, to convert it into some sort of editable format, then you start cooking the ROM, placing whatever you want, and in the end, convert it back into NBF
Hello,
You might find something useful here:
http://www.modaco.com/index.php?showtopic=255064
It would be more helpful if people genuinely try to help others instead of directing them to Google.
A
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
duke_stix said:
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
Click to expand...
Click to collapse
if all were like you ...
I know it isn't but in so much amount of infos it's not easy to find ones that apply to your device or even thing you wanna do!
Need help too
Yea, Please..my probs are the reconverting my data into a .nb->nbf file...after flashing My phone hangs in First Bootscreen...please help!Only Reflashing helps...i really want to cook a rom by myself.
Ive used THIS kitchen...but it is for Wizard-devices only....but i think,it can be used for Tornado,too.
as far as we tried we could not make a proper dump of the wm5 tornado...
but i did manage to build a rom kitchen with wm6 for the tornado...this was a whileago and the base rom is the same as the current available...if ther is enougth request i may be inclined to update the RK and release it.
to get you started here is some pointers.... you can use the same tools from the wizard, imgfs tools.
When I use nb2nbf_wizard.exe, is this created nk.nbf flashable for my Tornado (german XDA Phone aka HTC Douton)?
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Have you removed the first two bytes of the initflashes.dat? When not, it can't be booting correctly! That was my mistake when I started to cook my own ROM's for my HTC Prophet (XDA Neo)!
What?
really?I may think,it is only needed after a Registryedit....thank you.!
edit:did not work...
arpy said:
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Click to expand...
Click to collapse
i have the same problem like you.
I've made a nk.nbf from the *.nb files with nb2nbf_tornado.exe.
I've also extracted *.nb (OS, IPL, SPL, etc) from nk.nbf from windows mobile 6 alpha and then 'translated' those nb files with nb2nbf_tornado.exe. Same result: succesfull flash, stuck in first screen every time..
so not the "initflashes.dat" file is guilty..
...and nobody out there may help us?
arpy, it seems that if I include only OS without IPL & SPL in nb2nbf, all are OK..
But still with my modified OS does not get over the first splash screen.. maybe i've done smth wrong. In dump folder, I've added some files (some overwritten), i've removed some files, modified initflashfiles.dat (last line blank, + removed the two first bytes with winex), modified the hv files (saved in unicode standard, first line REGEDIT4, last line blank.. complied: no errors). replaced carrier_splash and shutdown
that's all what I've modified ...
edit:
arpy, try to translate only the OS module with nb2nbf_tornado. and tell me the result. also, tell me what changes you've made
edit2: found this: http://forum.xda-developers.com/showthread.php?t=298327 . improved tools
edit3: i've dumped my modified OS module with tadzio's ImgfsTools and discovered that initflashfiles.dat had the two bytes that i've removed with win hex.. what the?!
i've removed again, and run the whole build rom process again , but this time with tadzio's ImgfsTools.
Same result.. (stuck in first screen)
Maybe i've modified something wrong.
edit4: i've repeated the whole process and OS module flash and work ok . I haven't tried yet with all modules, only OS. I think I've made some mistakes when trying to replace drivers.
@DSF
Can you post a Step-By-Step Solution?I want to figure out my prob...which tools do you use?And how?May you Post your ROM?
well, i will post summary. i hope to release a "tornado romcook kitchen" and more detailed steps these days.
here is my OS module:
http://rapidshare.com/files/45915194/RUU.rar.html
right now i'm trying to figure out how to make the sd driver from iphone/other roms to work on my custom rom. every time i try other sd driver, i cannot view the card.
i'm using the tadzio's ImgfsTools (see link in my previous post).
steps:
- download typho5.exe, ImgfsTools, nb2nbf_tornado (you can get them by searching via gogole)
- copy all those files in the same folder, eg: ROMDEV
- copy nk.nbf in ROMDEV
Commands:
1) typho5.exe -x nk.nbf
2) imgfsfromnb.exe 82040000-OS.nb imgfs_raw_data.bin
3) imgfstodump.exe imgfs_raw_data.bin
Now the OS files are dumped in dump folder. Do the changes (delete, copy, modify, etc). When editing registry and initflashfiles.dat file, perform the important steps describeb at http://www.molski.biz/romcooking.html (turn off word wrap and use UNICODE in notepad, etc). If you're dune with those things do next:
4) imgfsfromdump imgfs_raw_data.bin imgfs_new.bin
5) imgfstonb imgfs_new.bin 82040000-OS.nb 82040000-OS_final.nb
if no error occured in the whole process, run 6) nb2nb_tornado.
There, chose the nb files, OS will be 82040000-OS_final.nb and not 82040000-OS.nb. Don't forget to use the correct image name. (eg: for 82040000-OS_final.nb chose OS)
The language, oem, operator version, cid can be left blank.
When you're done, press translate.
Copy the generated nk.nbf file in the rom update folder (RUU), execute ROMUpdateUtility.exe and follow the normal flash steps..
That's all.
Thanks to all those ppl that made this possible
PS: if you flash only the OS module (without IPL & SPL), even if the update proces crashes, you will not 'brick' your phone . Mine happen to crash on 2%.. i transpired instantly
kartam said:
You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
Click to expand...
Click to collapse
Actually, I have some files about how to cook a rom, but they all Chinese, and may be useless for you.
DSF: the way you describe works with the tornado. thx. ive testest
an usefull app to edit initflashfiles.dat and the registry files is "notepad2".
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.
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.
This is a kitchen based on Cracing's CRBuilder2 that I have been using for some time now.
Many thanks to him, S.V.I and the many others that have made this kitchen possible.
This is not a visual kitchen, I have not managed to do that. Instead it is a drag and drop kitchen. You create you ROM batch and then drop it into the OVEN to cook.
Please avoid spaces in file name, it will help avoid problems that may arise.
The ROM batch folder arrangement is that of platformrebuilder.
Code:
_ROM_Batch
EXT
Wizard
Extended Packages
OEM
OEM Packages
ROM
XIP
MSXIPKernel
MSXIPKernelLTK
OEMXIPKERNEL
SYS
SYS Packages
I put the _ in front of my ROM_Batch folders to find them easier.
I have as many error checks as I can think of, but they may not catch everything. Since I drag and drop pieces in and out of my ROM batch, I sometimes drop them in the wrong place. Most of these errors should get caught. This saves having to go through the cooking process to find you have a module in another module's folder.
I also have a Configurator option in my kitchen. This will merge all config.txt files in you ROM batch into one file. This is useful if you are using AutoRun, but have some packages from a RunCC version ROM. You will want to remove any CFG: lines to avoid running a config.txt twice. Also, this is how I do something similar to add2config.txt I have seen in other kitchens. For example, if you create an EXT package that has a config.txt file with some commands you want to add to the main config.txt like EXEC:\windows\myprogram.exe these lines will get added to the new Config.txt. Configurator also adds and CAB files you do not already have listed in the Config.txt files.
Here it is Wizard_Kitchen.7z
It includes Cracing's CR96 Touch HD ROM batch he recently posted.
If you drag and drop the Extended_ROM folder into the OVEN you can build an Extended ROM by itself.
For future use
For future use
For future use
For future use
Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.
I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.
n2rjt said:
Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.
Click to expand...
Click to collapse
Didyou mean CR96 Touch HD™ RC5 Reloaded w/ M2D Build 21882 Cracing recently posted? For my kitchen you can do this. Copy the sample folder under Wizard_Kitchen and rename the copy to something like _CR96_RC5 or any other name that works for you. Best to have no spaces. Then copy EXT, OEM, ROM and SYS folders from Cracing's kitchen you downloaded to your new folder _CR96_RC5. Then drag and drop the _CR96_RC5 folder on to the OVEN.exe file and the kitchen will start making your ROM.
Cracing's ROM is clean you so can answer no to the Configurator as he already has a complete Config.txt file in his kitchen. Also, you can answer no to the include an Ext_ROM question or pick yes and copy the empty extended ROM I included in the kitchen. There are a few other questions to answer and yo can try it different ways to see what you like best.
You are correct. The extended ROM only lets us add more stuff into our phone during a flash. I am still watching ShaDrac as he works on Extendir.
n2rjt said:
I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.
Click to expand...
Click to collapse
Use LZX compression. That is how I manage to fit more stuff. I do it by default now asa matter of habit.
If that alone does not help. I typically choose 0, Try Reducing, 4MB pp and include -no cert for the other question group
Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.
n2rjt said:
Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.
Click to expand...
Click to collapse
Both of his versions booted for me. Hmmm, I'll try to think of what it could be.