I apologise up front if this has been answered elsewhere, but I have searched high and low without any luck...
A number of ROMs are so-called "chef friendly" ROMs, i.e. they can supposedly be extracted with the .dsm and .rgu files intact, packages neatly in folders, etc.
I would like to customise one of these for myself, but I'm not having any luck.
I am using Alex's kitchen to extract the ROM, and I've tried these methods:
1. ruu_signed.nbh in the BaseROM folder, option 'a' on the Extraction menu.
2. Cooked ruu_signed.nbh in the BaseROM folder, and dumped part01.raw and part02.raw from the cooked ROM, using option 'b' on the Extraction menu.
3. Shipped ruu_signed.nbh in the BaseROM folder, and dumped part01.raw and part02.raw from the cooked ROM, using option 'b' on the Extraction menu.
I manage to get OEM, ROM and SYS folders which look fine. Initially I am just trying to recook these using the kitchen, with no changes. I am including the splash from the cooked ROM as well, but my NBH is about 3MB smaller than the cooked NBH I extracted from. There are no errors in the build process, flash works 100%, but the phone refuses to boot fully, it just gets stuck at the splash screen with the RGD numbers.
I have read the dumping and reconstructing threads, but obviously I am missing something important, I just cannot see what it is.
Can anyone point me in the right direction?
Please identify the ROM you are trying to extract so we can help.
I am trying this using gullum's TF2D II.
I can't find it now, but I definitely saw gullum state in a previous thread that all his ROMs are chef friendly, so I just chose that ROM because of that. Ultimately though, I'm not particularly fussed which ROM I use for this, it's just for my own use.
I know for sure that mine works because I do that a lot since the initflashfiles.dat changes after cooking the ROM, and I could try out gullum's for you. If you want I can put the folders in a RAR file and upload them for you . Oh and whenever I was cooking and my phone didn't boot the culprit was a registry error with opera, just in case you want to know.
kaiserII101 said:
... I could try out gullum's for you. If you want I can put the folders in a RAR file and upload them for you
Click to expand...
Click to collapse
That would be awesome. Or you could just let me know what additional steps I am missing. I don't mind getting my hands dirty, I'm just a bit stumped, being relatively new to all this.
no what you are doing sounds right. I'm not sure what the problem is. I will just re-cook the ROM to make sure it works and then put up the folders. I'm about to go on vacation though so expect it mabye by Mon. or I may do it on vacation since I have an unlimited data plan for my phone and I am bringing my laptop
Not to worry, for some reason it's working now. I have already ripped out a few bits that I don't want and added a few that I do want, and so far my phone has been stable for about 4 hours.
Thanks for the offer anyway.
you do NOT need to rebuild the Part01 and Part02 raw files. All you need to do is set the .nbh as your base
Related
Hi all, I've been trying for quite some time to cook my first rom. I've now read a lot on the subjects here on these forums but it seems the vox is not the easiest device to start with I've successfully extracted all files from an .nbh rom upgrade. I've then extracted everything to /dump folder using prepare_imgfs.exe and imgfstodump.exe. Here I can delete/change/add files in the directory and rebuild the rom with buildimgfs.exe but it is not a very clean cooking... I'd like to be able to use Package tool. Actually I can use it and get the two folders /OEM and /SYS but then I really don't know how to rebuild the rom using Buildos.exe. Does anyone know how to do this ?
Tell me if my english is not very understandable..
I've finally been able to use these tools after a lot of trials and errors. But there is a lot of fixing to do in the building process. For exemple after running OEM and SYS folders through BuildOs a lot of files are missing in temp\dump
It seems every important file is missing in each of the subfolders. Missing dll's, missing exe's...
For example if I look in the zlib.dll\ directory I can see 5 files : imageinfo.bin, imageinfo.txt, S000, S001, S002, S003 BUT no zlib.dll ?! So I have to manually reimport those files... Is this a known issue with buildos and if so is there any solution to it ?
Thanks for any help
My bad, just realised reimporting the dlls is not at all needed
Still speaking alone ?
Perhaps this thread from the Kaiser forum helps you.
Dr Gonzo.... i would have lied to said something but my knowledge of cooking ROMs is zilch.... but i was hoping someones cooks a ROM for the Vox ... so wanted to ask u how its going?
I've been able to build an awkward "kitchen" for the Vox but I don't know yet if the roms built with it are really stable. Awkward because I don't really know how to write batch files and because I had to add a .dsm taken from Bepe's kitchen for Buildos.exe to work (but I delete it once the dump folder is rebuilt). But I have been able to add/remove packages and it seems to work.
I am currently building my rom from the Arabic one with smarttoolkit included, custom system screens, commanager and homescreen, office and HTC audio manager removed, windows live updated, Jbed instead of Jeodek etc... It seems to be stable but some things don't work yet (I still need to edit the registry)
But what I'd really like would be the possibility to add Bigstorage to the rom as it increases free memory from what I've read.
Maybe I can release this kitchen with some instructions and someone better than me could improve it ?
RE
Yeah that would be awesome to get some Vox Rom cooking happening when can you post your kitchen?
I'm in the process of writing a quick guide to go along my very dirty kitchen to show how to use it. For the moment only with HTC_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90 as a base rom because I haven't tested anything else yet.
Hi guys....
I've been a member of this comunity for 2 years now, but posted very litle, because I would be mostly spamming, re-interating what others have said, with" wow, this is fast...nice job"...and such..so i only post when I realy have to.
I downloaded the hypercore kitchen, and after some reading of the contained links and txt files, decided to have a go at it...
I would like to target Tomal's v8 but although very fast, it seems to have a significant number of com bugs...So maybe I'll go with v7.7...
I copied the nk.nbf file to the correct directory, and ran the decoder, but it errors on the next step saying that there is no OS.nb file...
Should this file be extrated from the nk.nbf?
Is this a problem with the nk.nbf file I'm using?
I would apreciate some help on this, as I'm looking for a full flavored cake, but to my taste...see I'm "diabetic" so I have to be extremly caution with what I cook...
When you decoding nk.nbf, decode it to OS.nb (change second line) instead nk.nba.
Something else to be aware of with Tomal's ROMs is that he ships all his RGUs in a single RGU.cab file.
You'll need to extract the contents of this file into the dump directory AFTER the imgfstodump and BEFORE the pkgtool step.
-PJC
Thanks for the quick answers, guys...
Something pop-up as a doubt...can I cook from an usb stick?(installing the kitchen, and workind directly trought the usb stick)???
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
psapg said:
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
Click to expand...
Click to collapse
With HTC Extender Rom Tool you must extract nk.nbf not ext_rom, and when extracting name it OS.nb (i thing it is 2nd line in tool)
Perhaps the would-be chef should read a cookery book?
There's a very, very good guide in this forum, which is what I started off with and had no problems whatsoever, but I can't for the life of me remember if it was beasty or thingonaspring who wrote it (apologies to the real author if I missed them out!). It also includes some fixes for the batch files.
Remember - the wiki and search are your best friends...
PJC
Hi Again...
The construction workers finaly had done some real work, so now my kitchen is properly furnished with all the CABinets i need...so now to try to cook me a simple meal, and try to learn from it....
Can't rebuild Ranju 7.7
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
jandevries12 said:
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
Click to expand...
Click to collapse
imgfstonb doesn't seem to support the FLASH disk that's in Tomal's ROMs. I don't know what he uses, but when I've based things on his work, I use a different 'donor' OS.nb for the imgfstonb stage. Obviously, I lose the FLASH disk, but as I don't use it anyway, that's not an issue for me.
^^ yup, exactly, it is due flash disk.
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
jandevries12 said:
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
Click to expand...
Click to collapse
As I understand it (and I'm sure someone can correct me if I'm wrong), the donor OS.nb is used as a 'template' for storing the IMGFS into an NB structure. As far as I've been able to tell, pretty much *any* OS.nb from *any* ROM can be used as the template.
Basically, imgfstonb takes 3 arguments - the imgfs file itself, a 'donor' OS.nb, and the 'target' OS.nb final output. This is all hidden by the scripting, but is what I've found by playing with the underlying utilities.
The only restriction I've found is that ROMs that contain Flash disk can't be used as the donor OS.nb.
PJC
Could one of the senior members of this forum please comment on pjc007's statements above?
Is it correct that the donor os.nb is only used to determine the right structure for the ROM?
(I'm asking because I got the impression from other posts on this excellent site that the donor os.nb is used as source for the XIP part, but I don't know for sure)
Well, I have the same matter now, I really want to cook sth to use the way I want a rom to be and share with others as I feel really bad just to download, I hope to upload my own rom and share but I read the instructions again and again , look for sth on the internet, download all the things to my PC that will be used to cook, still not certain what I'm going to do.
My question is if I cook a bad rom, then I up it to my EXEC, Is there any chances for it to die ? Or simply just install another well-known rom to rescue it if my rom jail to boot?
Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks
go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.
Yep, looks like you didn't set it to Herald when you built it.
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?
Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.
After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks
Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.
I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help
Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.
The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.
The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.
working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.
Hi all,
Perhaps it is a newbie question so please bear with me.
I have an i-mate K-Jam flashed with TNT rom (build 20273). It works perfect and nice, however (frankly speaking) I don't like or want some of the APPs installed with this ROM, but I can't uninstall them.
I've searched this forum to find a way to extract the OS (OS only) from TNT rom so that I can flash my wizard and then install all the APPs I want, with no luck. Perhaps my search skills are a little poor...
So would someone please explain if it is possible or not? and if yes, how?
Thanks in advance.
Regards.
You cannot remove apps from a cooked rom. Search for Vanilla roms if you just want the base rom without any extras and then you can install you own apps.
well you can, but for that u'll have to dump the ROM first, remove the apps you dnt like and recook it
you can not dump the TNT roms. when you try, there are no RGU'S or DSM's.
You can dump my rom if you like, but you will get some missing files you will have to put back into the oem.
the missing files come from me not editing the rgu's when I cook.
try dumping Hornet5. for the most part you will get complete packages, but also some "missing files". just put them back into the oem/sys and recook.
Thanks for info. Saved me a lot of time.
I finally managed to cook my own rom. Everything works perfect except that:
1) I've used XIP, SYS and OEM files/folders of different builds. Am I going to have problem later?
2) "CommManager.exe" was missing. I've searched the files used in kitchen and the only thing I found is "commmanager.htm". Later I managed to download and install HTC CommManager but I can't assign in to its button (button 6). Is there any solution for that?
3) How may I extract the "splash screen" from one build, and upload it to my phone?
4) Bluetooth is not working. It says there is no bluetooth hardware on device. Also WLAN disconnects after a few seconds. How may I extract the drivers from original ROM and upload it?
I know the above questions are too much, but actually I'm so excited that my first attempt to cook a rom was successful (almost). I hope one of you experts be kind enough to help me solve the above issues and have a perfect phone.
Thanks in advance.
you will have some problems with the initflashfiles.dat in the oem, as well as the "oemtranslation.prvxml" or something which controls your icons for programs and control panel.
The best thing to do is use the same build OEM SYS & ROM folders.
If you dumped hornet 5, then your best bet ist to work with everything in it. I was working at this rom after Sleurhut for about a month or two.
mixing builds of those folders makes you start from scratch again fixing up your oem again.. and again.
as far as the missing files, try using the Xdump method; or use the searcher on your PC to find the missing files folder and the contents.
Dear S.V.I
Thank you so much for your ongoing support and help.
As I've mentioned before, I'm a total newbie trying to have a clean WM6.1 on Wizard. I've searched and read lots of tutorials here and there, but there are still lots of questions remained.
I tried to play with HyperCore (multi-device) today and I failed in the first step. I've extracted the "nk.nbf" from official i-mate KJam ROM using WinRAR. HyperCore is installed and I've a "C:\Core" folder as well as a "HyperCore" folder on my desktop.
The "DumpRom" is asking me to make sure the "nk.nbf" is in "HyperCore\Extract\Source" folder. Well it is there. Press Enter and the error message says: "There is no nk.nbf in Core\Extract\Source".
No it is not. First, it asked me to put it in "HyperCore\Extract\Source" not "Core\Extract\Source". Second, there is no "Extract" folder under "C:\Core". Even after creating Extract\Source under C:\Core and copying nk.nbf there, the same error message appears again.
So, what I'm missing here?
Same
I'm also scratching my head on this problem too. I've even tried creating extract\source folders in locations C:\core\ and desktop\hypercore\ but still no luck.
I'm wondering however that the issue could be caused by vista/7's change from Documents and Settings\user\desktop (2000, XP) to Users\user\desktop.
It may change the way the batch files are called but i'm really rusty on batch commands these days
I would start with the sticky "How to cook a ROM" thread, focusing on CRACING's kitchen, then move to Nekid Angel (Post #3)
where you will find a more updated ROM ready to cook. If you want to try WM6.5 a good ROM and kitchen is at [WM Kitchen] Wizard Kitchen or CRACING's RC6. I have been playing around with that.
You might move your discussion to one of the cooking or kitchen threads mentioned above, too, since that is where others will look.
Perfect
That's what i was looking for thanks for the heads up N2rjt!
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.