Rom cooking on Vox - HTC Vox

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.

Related

Need Kitchen Help

Ok I need a few opinions.
I am wanting to find out who has the easy and the best Kitchen.
I want to take a "nk.nbf" and edit it.
I want to remove packages that are in there and add others.
I have "TNT.1933_Professional___HTC_Home_Wizard" Rom I have tryed to use "HyperCore Kitchen" but could not get the rom to work.
I took the original ron, extracted it and then re made it (With out changing anything) to see if I was doing it the correct way, but after I loaded the rom it locks up after it posts the ver screen.
Is this the rom I am using or the way I am using it. Or is it the kitchen.
I really want to learn to make my own. So if some one has time to walk me though it I would be ever so greatfull.
I have searched and search the site and most walkthroughs apply to old vers of kitchens. I still tryed to follow them but cant get a rom to work. I know I must be missing something somewhere.
- Albert
I don't think you have the .rgu's
If the chef deletes the .rgu files you can't rebuild his rom the easy way. You should either seek a rom that has all the files or ask the maker to share them.
Ok thank you
Yep, a lot of the roms have the .rgu files removed. You can use my cooking pack or I recall that there was a Lite version of TNT that was meant for cooking that would still ahve the .rgu files (but then you'll have to get the packages to put in it what you want). Then of course there is theloon's kitchen stuff which has tons of packages and all.

Can anyone help me to debug my first rom

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.

Extract pure OS from cooked ROM

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!

µkitchen to add custom files into protected rom

Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
What is the difference in extracting ngh file, adding cab file to dump folder, updataing config.txt and recooking compared to installing the cab file using UC?
Can we add visual kitchen packages to this dump folder? If we can add do we need to just copy all the files in all the folders of the package to dump folder?
eg: in the package there are some files in 0409 and some in files folder , _skip, app.reg, all these goes to dump folder?
Thanks
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
arnoldl said:
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if http://forum.xda-developers.com/showthread.php?t=503112posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
Click to expand...
Click to collapse
Thats a nice idea. Thanks for the updated version.
DarkRenegade said:
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
Click to expand...
Click to collapse
Thanks again
works very well
arnoldl said:
Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
Click to expand...
Click to collapse
You have a Trojan horse in first post!!!
All this to add a couple of cabs to a ROM ? Isn't it a whole of a lot easier to just... you know... install them after ? Or maybe even UC them to make it even lazier ?
Does this work with other roms from other devices? Or just Raphael roms?
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
jagan2 said:
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
Click to expand...
Click to collapse
Use the latest version of extractor, place the .nbh file in BaseROM, rename it to RUU_signed.nbh and run the extractor.
That worked for me.
A little late reading this, but I downloaded it to rip a rom from a little known site & guess what... Theres a trojan in that 1st post, virus software just riped it out of 2 kitchens recently downloaded as well as that 1st post file.
file namned Win32/Delfsnif.dx
I used your extractor but when i use old (1,2mb) i have problem with rom (sense 2.5 crash , windows menu crash), when i use new extractor (1,9mb) i don;t have a bootable rom (.nbh is very small 15mb-100mb) Is there any solution?
Sorry for my english I hope you can understand me.
I think there are more usefull tools that could help you.
Let's have a look here : http://forum.xda-developers.com/showthread.php?t=411915
And I believe that this tool is used by most roms makers.
Sorry but this tool is traying to rebuild protected rom into kitchen (with folders - ext, rom, sys etc.) but this is impossible.
Worked Great ! !
It worked great for me!
Moving to general section
You should just move this to the cooking forum. People are always asking if you can modify cooked roms. Then others are always answering that you can't dump and modify a protected rom, which clearly isn't true. So this would work ok in the Cooking forum (can't even remember the name of the forum, even though I'm a mod there, lol).
If this works, than this is pretty kick ass! I was recently trying to simplify the process as you did but your work looks flawless to me! I'll post as soon as I can confirm it works putting the rom back on an HTC rose (htc s743).
After the rom is dumped, what says what files go in what directories? In the dump directory ALL files are in the dump directory and not in the folder structure they would be after the ROM is flashed to the phone. Where would I find what determines the folder structure?

Porting XIP from Kaiser 6.1 Rom

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.

Categories

Resources