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,
Hi guys,
I flashed my Wizard with the base OS ROM version 5.2.318 (build 15342.0.0.0, customization) published in this forum about a month or so...
After flashed, it just start the OS without running the Extended_ROM content, so I installed all cab files inside Extended_ROM folder by myself.
What I should modify in order this run automatically on next hard-reset?
You have a G4 Wizard looking at your signature, thus the files Autorun.exe and Config.txt (a list of all the cabs in the right format- these files can be found in the Faria Ext-rom tutorial package) need to be in the \Windows folder but they can still point to run Cabs from the Extended ROM. Check the registry before cooking to see it points to the autorun file then you're good to flash.
Thanks for the response... I did it and is working now!. Useful tip.
I think _Alex_ was the last to offer a kitchen and I think it's about time we had a new one. Everyone has their own needs and I know no ROM is perfect so here's my attempt to satisfy everyone.
I don't know if I'm going to have the time to answer everyone's questions and to help resolve all issues so I have to ask the community to please help out when you guys can.
Next, on with the thanks and I know I'm going to leave some people out so I apologize in advance. So thanks to these users for the tools and support we use to customize our phones:
-- kyphur, bepe, jerplea, jscepi, cmonex, alltheway, p1tater...
And to these people for helping me test and support my roms:
-- hang.tuah, dani31, -888-, idj1975, ecltech, kmfm$, rkrasny...
Here's what's included in the link:
OEM-3.29: my cleaned up OEM folder based off of 3.29 Dopod ROM
OEM-Packages: my packages created with help from XDA (see attachment for list)
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
SYS-20748: ported SYS from jerplea, has 20212 components
SYS-Extras: entertainment (solitaire, bubble breaker), office, onenote, windowslive
And without further ado here's what you need to do:
1. Extract Kitchen.rar to the root of your drive (i.e. c:\ or d:\)
2. Extract OEM-3.29, ROM-20755, SYS-20755 to where you extracted Kitchen.rar
3. Copy packages you want from OEM-Packages to OEM folder
4. Copy packages you want from SYS-Extras to SYS folder
5. Cook and flash, see attached DK's Instructions doc if you need more help
NOTE: The contents of "OEM\OEMXIPKernel" are REQUIRED for cooking if you want your rom to boot
To get 2DManila working you will want to include from OEM-Packages the following:
-- 2DManila, Album, AudioBooster, AudioManager, CommManager, ConcurrenceMgr, VerionInfo, YouTube, Camera, Dshow, (me thinks that's everything)...You also need GoogleMaps.cab and OperaMobile (not included, search Dev&Hack for current version)
My Supa-Clean ROM always have the following:
-- ConcurrenceMgr, OutlookEnhancement, PictureEnhancement, RingtonePlugin, VersionInfo, StartupAnimationEngine, SymbolPad, DShow and mHub
click me if wanna give me a little somethin'
http://rapidshare.com/files/146363122/DK_s_Kitchen_v1.zip <-- 99MB
http://rapidshare.com/files/146441384/OEMandPackages.zip <-- OEM and Packages Only
http://rapidshare.com/files/146425292/ROM_SYS-20748.zip <-- CE OS 5.2.20748, ROM and SYS only
http://rapidshare.com/files/148174032/ROM_SYS-20755.rar <-- CE OS 5.2.20755, ROM and SYS only
http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html <-- SYS fixed by KMFM$
TODO:
- Find and Squash bugs
- Get new Jade PhoneCanvas: Sakajati and uDK seem to have this working, but I'm stumped (HELP!!)
- Jade_VolumeControl: didn't include this because when installed you can't change the in call volume with the scroll wheel
- I got the Jade Camera working, but it doesn't seem to have autofocus so I didn't include it. Anyone have a the files for the camera floating around?
OEM Version Numbers:
RandomAccess - 4_0_18174127_0
OutlookEnhancement - 1_0_33540_4
Album - 2_5_18191330_0
BootLauncher - 1_0_34322_2
AdvancedPowerManagement - 1_5_18162126_1
RingtonePlugin - 1_00_080416_1
CommManager - 2_7_1_8
2DManila - 1_00_18183719_00
TaskManager - 2_1_34563_3
AudioBooster - 2_1_18181827_1
LargeTitleBar - 4_40_0_0
PictureEnhancement - 1_50_18141822_c2
YouTube - 1_5_1818_3522
AdobePDF - 2_5_103401_01R1
ArcsoftMMS - 5_0_31_45
HTCGesture - 1_0_30346_1
mHub - 6_54_080529_E0
SymbolPad - 1_0_29364_0
AudioManager - 2_0_18191228_0
VersionInfo - 1_0_18182525_0
ConcurrenceMgr - 1_1_18143521_0000
StartupAnimationEngine - 1_0_626715_0
DShow - 2_00_080730_0
CAMERA - 4_08_30665_00
EnlargeStartMenu - 1_2_34828_4
reserved for me again!!
Great. Really appreciate your gift.
Thank you very much indeed.
yay! Beautiful gift to our community
I will add it to my public share in few minutes...
I aim to please!
akadonny,
Thanks for sharing. Haven't done this in a very long time so maybe I'll give it go.
I downloaded your full 99mb Kitchen, and everything extracts fine. I've cooked up several ROMs so far, so I have a decent understanding of the process.
I apologize if this question has a simple answer, but I am having no luck, so here goes:
I want to use your 20748 build (you mentioned that 20753 has issues with SMS Threading) to update my NATF ROM series. Due to extensive customization I have done to my OEM folder, I would like to keep it as it, and so I extracted your ROM and SYS archives into my existing Kitchen folder. Now this is where it gets complicated...
I have tried using you Kitchen and Alex's Kitchen, both produce different results, and neither seem to work.
Using your Kitchen, the ROM appears to build fine, but OS.nb is nowhere to be found when HTC ROM Tool launches.
If I use Alex's Kitchen with BuildOS 2.7, then I get an error that it cannot find the ROM folder, but after clicking OK, everything builds as normal. However, after flashing the new ROM, my Tilt sits at the initial splash with R G D and will not go any further.
If I update the BuildOS in Alex's Kitchen to 4.3, everything builds correct and the ROM flashes OK, but UC does not run, File Explorer has an AT&T icon for some reason, and Manilla does not work.
--Ultimately, here is my question--
I want to keep the customizations that I have made to both AT&T Official 6.1 ROM (3.57) and HTC's Official WWE (3.28), but I want to use a newer OS build.
Is there a very special/exact combination of things I need to do in order to achieve this?
Thank you for absolutely any insight you can provide.
@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.
@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...
Knumb said:
@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.
@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...
Click to expand...
Click to collapse
I tried this one also...
I must be doing something wrong since these kitchen's can't all be incompatible with the 20xxx builds (can they?), but I can't seem to figure it out.
notatreofan,
You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:
C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS
After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.
All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS
akadonny said:
notatreofan,
You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:
C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS
After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.
All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS
Click to expand...
Click to collapse
Thank you for your answer. I could swear this is what I was doing, but I've tried so many things that I cannot remember... I'm going to try this method (again?) now, and I'll report back.
i have the same problem
i put your kitchen d:\Kitchen
after inside there the FOLDER sys and rom from 20755 and oem from 3.29
i push the cook
flash the new rom
and after splash screen with R,G,D no respond
My problem continues also.
I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.
Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.
I try now the older 20748
and all working grate
in ABOUT screen have the new number of OS and Build
ACADONY you must test the 20755 again
something going wrong with it
also i can inclunding package with you rom
and your package don't working with alex kitchen
NotATreoFan said:
My problem continues also.
I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.
Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.
Click to expand...
Click to collapse
I am having the same problem at NATF....any ideas????
No preblems at all with 20748... about cooking...
The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(
Black-Rose said:
No preblems at all with 20748... about cooking...
The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(
Click to expand...
Click to collapse
the 20748 is only one who working.. but activesync running on backround
20755 stack on splash screen
20753 when flash it start the boot loader screen and say something for error in core try again
For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.
KMFM$ said:
For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.
Click to expand...
Click to collapse
you found any solution?
i try to night your tip!!
tell us if you found something
-EDIT-
this tip not working
I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?
Anyone willing to spare some time to help please?
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?
OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.
I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.
If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)
I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.
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.