Database Users

Creating Kitchen from Dumped ROM

This started out as a pm between hilaireg and me. i'm reposting the conversation here in order to benefit the rest of Chef Central.
I have a NEON400 which has recently been SPLed...finally.
However, there are no ROMs out there for the device and one guy who tried failed miserably. Mostly due to the fact that he doesn't own a device and can't test it.
what I'm looking for is a tutorial or some way to turn the dumped OEM ROMs we have into usable clean ROMs or upgraded to 6.5. Obviously there is no way that you can help me without having a device but is there any generic tutorial out there so I can get started learning how to do this?
Thanks for your help if you can... I appreciate anything you can do for us lowly NEON400 users.
thanks!!!

FROM: hilaireg
I'm not sure as to how much help I can be; that said ...
1) NEON Specs
I had a look at the NEON specs on the WIKI to get an idea of what is possible with the device.
From the specs, the unit is 128MB of ROM which may necessitate RECMOD'ing of module in order to achieve a bootable ROM. SLOT0 is generally the issue with WinMO 6.1 as SLOT0 should remain free of modules for the final ROM compilation. Here's some supporting information on Virtual Memory that will better explain what I am referencing:
Virtual Memory as it applies to the Windows CE 5.2 Kernel
http://forum.xda-developers.com/showpost.php?p=4268137&postcount=2
2) ROM's
I haven't conducted a search to see if an update ROM has been released for the NEON (either through BELL or HTC); I'm going to describe two possible scenarios.
Scenario 1: No update ROM
The best approach here would be to determine how to dump the ROM from an existing device. Once a device is "dumped", the dumped content could serve as the starting point for building a custom ROM. Dumping a device ROM requires a few procedures ... I recommend a forum search with these keywords:
dump device rom
The threads that will appear will not be NEON specific, you'll have a bit of reading on your hands, but may provide some insights at what may be required.
Scenario 2: Update ROM available via BELL/HTC
If an update ROM has been made available for download, it should be possible to perform a dump via a kitchen such as Ervius Visual Kitchen (EVK). Here's a link to a tutorial I put together that walks aspiring chefs through the process of dumping an official updated HTC ROM using EVK for the Raphael - but is essentially the same for any device. Once a ROM is dumped using EVK, this would serve as your starting point for building a custom ROM.
[TUT] Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=526610
3) Custom ROM
Once you have a starting point ROM, you can use it to create a net new kitchen. A net new kitchen could be a matter of copy/pasting the dumped kitchen from #2 (above). Things to keep in mind:
ROM: OEMXIPKernel is device specific and usually doesn't change until a NEON update ROM is release by BELL/HTC
ROM: MSXIPKernel is MS specific, this usually gets updated when a new O/S release is issued (ex: 6.1.21054, 6.1.21056, 6.5.23541, 6.5.23549, etc.)
OEM: this is device specific package which often are device drivers, carrier (operator) configuration, device functions, etc. and usually doesn't change until a NEON update ROM is release by BELL/HTC
SYS: this is MS specific and usually gets updated when a new O/S release is issued (ex: 6.1.21054, 6.1.21056, 6.5.23541, 6.5.23549, etc.) the MSXIPKernel & SYS should always match.
I would suggest starting with 6.1 and once you have a working build, you could look to move to 6.5. What's is important to keep in mind is:
you may need to RECMOD modules
closely review the .RGU (.REG), INITFLASHFILES.*, and .PROVXML files for any carrier (operator) specific lock downs
you will need to Cert Patch the ROM, possibly reduce the ULDR, possibly adjust the PagingPool - all selectable features in the newest version of EVK
Lastly, don't hesitate to ask questions in Chef Central ... some senior chefs may have some pointers that could help.
Chef Central: Windows Mobile/Windows Phone
http://forum.xda-developers.com/forumdisplay.php?f=612
HTH

OMG, this is so much info. you are awesome.
Okay...to get some stuff out of the way:
1.) No update ROM was ever released from Telus or Bell (the phone was released by both)
2.) the OEM ROMs have already been dumped.
1. you may need to RECMOD modules
2. closely review the .RGU (.REG), INITFLASHFILES.*, and .PROVXML files for any carrier (operator) specific lock downs
3. you will need to Cert Patch the ROM, possibly reduce the ULDR, possibly adjust the PagingPool - all selectable features in the newest version of EVK
Click to expand...
Click to collapse
This went entirely over my head.
RECMODding? How do I do this? It looks like No2Chem released some sort of EXE for this.
What am I looking for in the carrier specific files?
I don't think I can use EVK because I don't have an upgrade ROM, or can I?

FROM: hilaireg
Okay...to get some stuff out of the way:
1.) No update ROM was ever released from Telus or Bell (the phone was released by both)
2.) the OEM ROMs have already been dumped.
Click to expand...
Click to collapse
Haven't downloaded the file; ideally the download should either be an *.NBH or *.NB file. If it is, you should be able to use it in EVK.
The question to ask yourself is, has someone gone through the trouble of ... dumping the entire ROM from the phone? Or, only dumping the OEM portion?
If it's fully extracted, is there a ROM, SYS, OEM, (PACKAGES\EXT) folder structure? If so, then you should be able to use it in EVK. If there is a PACKAGES folder, they likely used the PkgBuildOS (oldstyle) kitchen to dump the ROM; Ervius released a tool to convert an oldstyle PACKAGES folder to a newstyle EXT folder.
1. you may need to RECMOD module.
Click to expand...
Click to collapse
Recoded Modules usually appear like this:
<filenameasfolder.dll>
imageinfo.txt
imageinfo.bin
S0001
S0002
S0003
...​
Included in the TOOLS folder of the EVK is a RECMOD.EXE, when you drag the <filenameasfolder.dll> folder (and contents) onto the EXE, it creates the compiled .DLL - ex: filenameasfolder.dll.
2. closely review the .RGU (.REG), INITFLASHFILES.*, and .PROVXML files for any carrier (operator) specific lock downs.
This went entirely over my head.
RECMODding? How do I do this? It looks like No2Chem released some sort of EXE for this.
What am I looking for in the carrier specific files?
Click to expand...
Click to collapse
Since WinCE is really a mobile version of Windows - being simplistic here - there are some things that are similar.
Registry changes are typically kept in .RGU/.REG files.
INITFLASHFILES.* are usually used for file copy operations on the device.
CONFIG_*.txt are usually used to launch .CAB files, copy operations, etc.
.PROVXML are usually used to configure MS and Carrier (Operator) specific settings. They can also be used for copy operations, registry changes, etc.
3. you will need to Cert Patch the ROM, possibly reduce the ULDR, possibly adjust the PagingPool - all selectable features in the newest version of EVK
Click to expand...
Click to collapse
As you are cooking a custom ROM, you need to disable the security certificate checking or the custom ROM may not boot. The reason for this is that MS/Carrier (Operator) don't want people doing what we're doing ... it's similar to HardSPL, it tells the device that "it's ok to use this ROM".
I don't think I can use EVK because I don't have an upgrade ROM, or can I?
Click to expand...
Click to collapse
Shouldn't be an issue. As long as you can obtain the ROM (OEMXIPKernel & MSXIPKernel), OEM, and SYS, you should be able to build a working custom ROM.
Have a look at my kitchen thread:
http://forum.xda-developers.com/showthread.php?t=471288
Download the kitchen and have a look through it to get a sense of what the final product should look like. The change logs will give you a sense of what had to be removed/changed/added to produce a custom ROM.
And once again, don't hesitate to ask questions in Chef Central ... that's why it was created; to help aspiring chefs learn.
Cheers,

All right, I downloaded v1.8.1 of EVK and used it to load the dumped .NBH. This seemed to work flawlessly and I now have a folder called 'dump' that contains the following folders. (I manually entered the Device name NEON400 when EVK prompted for it):
EXT
MyTools
OEM
RELEASE_NEON400
ROM
SYS
Tools
I'm guessing I've successfully extracted the ROM image.
i would like, for ease and simplicity, to just make this into a clean 6.1 version. I don't REALLY want to tackle 6.5 quite yet.
Is there a simple way to clean out the garbage? How do I know what's what?
I really appreciate your help, you've gotten me this far. I hope you don't get too exasperated with my noobness.

88fingerslukee said:
All right, I downloaded v1.8.1 of EVK and used it to load the dumped .NBH. This seemed to work flawlessly and I now have a folder called 'dump' that contains the following folders. (I manually entered the Device name NEON400 when EVK prompted for it):
EXT
MyTools
OEM
RELEASE_NEON400
ROM
SYS
Tools
I'm guessing I've successfully extracted the ROM image.
Click to expand...
Click to collapse
Looks like it; now take contents from the 'dump' folder and move it to the top of your kitchen folder. For example:
Move NEON400_Kitchen\dump to NEON400_Kitchen\ - Yes To All.
This was one of the steps in my Raphael Tutorial:
[TUT] Sous-Chef's Guide to XIP Porting in Ervius Visual Kitchen 9.7
http://forum.xda-developers.com/showthread.php?t=526610
Afterwards, make a copy of the kitchen as this copy ("backup") will serve as your source/baseline which you can always refer back against ... how you got started. You should never make changes to this copy; what I typically do is .RAR the copy and store it in a safe place along with the source file (ex: the download RRU from HTC, etc.)
i would like, for ease and simplicity, to just make this into a clean 6.1 version. I don't REALLY want to tackle 6.5 quite yet.
Is there a simple way to clean out the garbage? How do I know what's what?
I really appreciate your help, you've gotten me this far. I hope you don't get too exasperated with my noobness.
Click to expand...
Click to collapse
There's no quick or easy way; now comes the steep part of the climb.
If you haven't obtained a file comparison tool yet, that should be your next stop. You really should get a good one that allows binary comparisons and such ... I use BeyondCompare; it's not free but it's worth it. Once you obtain the file comparison tool, you can use it to compare an existing folder against another - such as comparing two kitchens. As an exercise, you could compare your kitchen against my last Raphael kitchen to give you an idea as to areas typically require additions/removals/changes.
WinMO6.1.21056 Raphael Kitchen
http://forum.xda-developers.com/showthread.php?t=471288
Also download the .TXT files attached to the kitchen thread as I noted all of the edits I made to the OEM, SYS, and ROM folders in those files. Examine those areas of your kitchen. Pay special attention to operator packages, '.PROVXML', and 'CONFIG_' files in the OEM folder. This is where you will usually where you will find many Carrier/Operator specific changes or lockdowns. I usually move most of this content to a 'profile' package in the EXT folder; I never use the profile directly, I copy/paste the to a 'custom profile' and use the custom profile ... this way, I can eliminate underised "Carrier/Operator" features and only apply those features that are absolutely necessary. Additionally, extra components (themes, cabs, etc.) are often installed via a series 'CONFIG_' packages; these will likely require alteration.
A few last things to remember along this part of the climb ...
stop for breaks
drink lots of coffee
have fun
and don't forget to yodel

may i ask a small Q....regardingthe OEM....
if i want to put an app in my cooke ROM i know that i can covert the app from cab--to---ext..however i can do cab--to--OME and OEM --to-- EXT...what are the different and which is better ??? really need help to understnad this

An OEM package is essentially a kitchen package. The term OEM came about partly because the ROM extraction tools - essentially, the tools extract the content of an OEM .NBH/.NB file. An OEM package usually consists of files, files as modules, <guid>.dsm, <guid>.rgu, shortcuts, *.provxml, *.txt, and *.dat.
When chefs refer to OEM packages, they are generally speaking about the folders that appear in .\OEM, .\SYS, and the .\PACKAGES (or .\EXT) folder. Here is some background for Ervius Package Builder (PkgBuildOS) & Ervius Visual Kitchen (EVK).
PkgToolsBuildOS
In the older PkgBuildOS kitchen, the OEM package had a relatively flat structure. Most OEM packages were prefixed with 'PACKAGE_' - chefs would see these folders in .\OEM and .\SYS. It was also preferable to move such folders into a '.\PACKAGES' folder structure making it easier to choose which packages to include during the ROM compilation. Ideally, chefs would only keep essential (critical) packages in the .\OEM and .\SYS. The structure of the OEM package would look similar to the following:
Code:
[B][COLOR="Blue"]<PACKAGE_oem_packagename>[/COLOR][/B]
[INDENT]<guid1>.rgu [COLOR="Purple"][I](<guid1>.rgu + <guid2>.rgu)[/I][/COLOR]
<guid1>.dsm
[COLOR="Purple"]<guid2>.dsm [I](removed)[/I][/COLOR]
files
*.provxml
shortcuts
*.txt
*.dat
option.xml
[B][COLOR="Blue"]<modulefoldername>.[[COLOR="Green"]ext[/COLOR]][/COLOR][/B] ([COLOR="green"][B]ext [/B][/COLOR]= dll, cpl, ocx, etc.)
[INDENT]imageinfo.bin
imageinfo.txt
S0001
S0002
S0003
...
[/INDENT]
[/INDENT]
Visual Kitchen
When Ervius created the Visual Kitchen, he also created a tool to convert old PkgBuildOS OEM packages into the new kitchen format. During the conversion process, the tool would read the .DSM filename information and rename the folder accordingly - sometimes a folder would be prefixed with 'PACKAGE_' and in other cases not; it depended on the internal .DSM name. The new format of the package was such that it divided the language-specific files into a sub-folder within the EVK OEM package.
Additionally, the tool would copy the OEM packages to the .\EXT folder as once again, it is preferable to have OEM packages in the '.\EXT' folder structure as it makes it easier to choose which packages to include during the ROM compilation. Ideally, chefs would only keep essential (critical) packages in the .\OEM and .\SYS. The structure of the OEM package would look similar to the following:
Code:
[B][COLOR="blue"]<oem_packagename>[/COLOR][/B][INDENT]<guid>.rgu
<guid>.dsm
app.reg
app.dat
_skip
[B][COLOR="blue"]Files[/COLOR][/B][INDENT]*.provxml
shortcuts
*.txt
*.dat
[B][COLOR="Blue"]<modulefoldername>.[[COLOR="Green"]ext[/COLOR]][/COLOR][/B] ([B][COLOR="green"]ext [/COLOR][/B]= dll, cpl, ocx, etc.)[INDENT]imageinfo.bin
imageinfo.txt
S0001
S0002
S0003
...
[/INDENT]
[/INDENT]
[B][COLOR="red"]<LANG> [/COLOR] ([COLOR="red"][B]LANG[/B][/COLOR] = 0409, 040C, etc.)[/B][INDENT]<guid2>.rgu
<guid2>.dsm
app.reg
app.dat
_skip
[B][COLOR="blue"]Files[/COLOR][/B][INDENT]*.provxml
shortcuts
*.txt
*.dat
[B][COLOR="Blue"]<modulefoldername>.[[COLOR="Green"]ext[/COLOR]][/COLOR][/B] ([B][COLOR="green"]ext [/COLOR][/B]= dll, cpl, ocx, etc.)[INDENT]imageinfo.bin
imageinfo.txt
S0001
S0002
S0003
...
[/INDENT]
[/INDENT]
[/INDENT]
[/INDENT]
The tutorials I put together for the Visual Kitchen (EVK) and Package Builder (PkgToolsBuildOS) provide some additional details about the folder structure of the kitchen so I won't get into more details about it here.
HTH,

The guy who failed miserably to cook a wm 6.5 rom,ultimately cooked the first ever wm 6.5 rom for Neon 400
http://forum.xda-developers.com/showthread.php?t=650446

damn... nothing to say just.......
if this guy wants to learn how to cook for his device... just leave him to learn, BTW why you dont leave intact the rom links?

Dump a custom ROM

Is it possibile? I heared that custom ROM are protected...is it?
So it's not possible to havea dump of a custom ROM starting from a nbh file?

modules are protected, you cant use them. But you can use anything else. Look for HTC ROM Image editor. That will be the easiest way to extract files from a cooked ROM.

I tried just now...after loading the nbh file...nothing...it seems to be nothing, even with a not cooked ROM (a stock one)

You tried what?
Protection depends on the cooking method. ROMs built with old tools could be dumped no problem, but ROMs cooked with most new tools can not be fully dumped to a rebuildable state. The real question is, what exactly are you trying to get from the dump? If you just want a few files, that should be easy enough. If you want complete packages, that's trickier.

I tried to use HTC ROM Image editor, but it seems not work...
I need a complete dump because I'm tired to reinstall everytime my favorite apps and settings after a reset, so I would like to remove programs I do not use and add my favorite ones!

The ROM editor should work with any ROM for HTC devices. I think you are out of luck with getting a full dump from a custom. If I were you, I would just learn to cook your own.

Eheh...may I could be able to do a very mine ROM, but for some features...mmm...too much time to learn too much things...
Lazy me!!!

Talk to your rom chef, and see if they will share their kitchen for personal use. Which rom is it?

Da_G put together a kitchen a while ago called Dump Kitchen (I think). There's a thread in the Raphael rom forum. It lets you dump and rebuild roms, and i you know what you're doing, it's pretty easy to add apps and a little trickier to remove them (might as well just cook your own at that point). Just search for it; I think you can re-cook roms built with newer tools.

Farmer Ted said:
Da_G put together a kitchen a while ago called Dump Kitchen (I think). There's a thread in the Raphael rom forum. It lets you dump and rebuild roms, and i you know what you're doing, it's pretty easy to add apps and a little trickier to remove them (might as well just cook your own at that point). Just search for it; I think you can re-cook roms built with newer tools.
Click to expand...
Click to collapse
I doubt you would be able to use the modules, but I could be wrong.

Here's the link. I'm pretty sure it works with newer roms.

The bottom line is that any rom built with platformrebuilder (EVK etc) cannot be dumped into complete packages. Platformrebuilder deletes the dsm files which associates the files into packages and it also deletes the rgu/reg files which are the registry entries for each package. Not to mention it also deletes the last s00? file in modules making modules impossible to rebuild. According to bepe the only function of the last s00? file in a module is to make it rebuildable so it's practically useless to the module.
Bepe designed platformrebuilder this way not to make roms "protected", but to save space in the rom and increase module speed (by decreasing module size). There's no way around it.
Edit: it appears the tool Farmer Ted posted is used to dump a rom, add files/reg entries to it, then rebuild a flashable nbh.

So it means...it's impossibile to do what I need...yuhuuu...

zat81 said:
So it means...it's impossibile to do what I need...yuhuuu...
Click to expand...
Click to collapse
Just try the micro-kitchen. You can dump roms, but all you get is the raw dump. Removing apps will be tricky-you will need to know all the files that have to be pulled out. But, it's pretty easy to edit .hv files, so you can remove reg keys or change them however you wish. You can also add anything you want, it's not that hard to do.

I think I'm going to start learning something usefull..."cook for dummies"...eheh...I've read some guide, tutorials and...maybe...could be not so difficult as I thought...I've just to start from a good base kitchen!

A good place to start....
http://forum.xda-developers.com/showthread.php?t=669414
zat81 said:
I think I'm going to start learning something usefull..."cook for dummies"...eheh...I've read some guide, tutorials and...maybe...could be not so difficult as I thought...I've just to start from a good base kitchen!
Click to expand...
Click to collapse

zat81 said:
So it means...it's impossibile to do what I need...yuhuuu...
Click to expand...
Click to collapse
Yes thats what we are trying to tell you..lol

yep in newer Kitchens roms and dumps.. there isnt a way to make what you want... you must to talk to your chef and ask him for special rom for you with that info... and or apps i didi many of them to ppl that like sthe version... but sometimes vanilla or with PIM info... if he sahres with you the kitchen... you will be so lucky, just load the rom and deselect the apps you dont want then add yours and your info, but that you must to learn how... to add that... you must to learn and read is not so simple

Just a small note to add to this:
The last S00X section in a module is the .CRELOC section. This is used to relocate the module on-device (not used to relocate the module on the PC, in the kitchen, where we do it prior to flashing)
Not having the last s00x means that you wouldn't be able to imageupdate that ROM (because the on-device read/write IMGFS driver would not be able to re-base the module since .CRELOC is missing)
But you can certainly still re-base that module on the PC side prior to rebuilding a ROM. So that function in itself won't preclude you from porting modules from one device to another

Dumping a Rom with the Vistang-Kitchen works for beginners in cooking very simple:
http://forum.xda-developers.com/showpost.php?p=6019219&postcount=499

[Q] Kitchen for HD mini

Dear developers,
can somebody answer which kitchen we can use for HD mini?????

Yup...EVK will be a good one for that...

Get the EVK kichen... find a stock HD MIni ROM... dump it using the EVK and get cooking!

Interesting.... i just want to say that you need to be carefull cause the HQVGA is an unussual size in new builds hopefully the rollup comes more often

+ Que PPC said:
Interesting.... i just want to say that you need to be carefull cause the HQVGA is an unussual size in new builds hopefully the rollup comes more often
Click to expand...
Click to collapse
com3.2 aka 231xx should come HVGA since thats the normal branch for the phone.

Johan Kraczmar said:
Dear developers,
can somebody answer which kitchen we can use for HD mini?????
Click to expand...
Click to collapse
OSKitchen should be able to dump and rebuild the ROM for that phone without any issue even if it's not in the list as long as you know how to rename the EXT packages to give them the right order (that's an issue you will also have with EVK but on EVK you'll probably have many more unless you use an adapted version for your phone with the right packages already recmodded inside).
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.

airxtreme said:
OSKitchen should be able to dump and rebuild the ROM for that phone without any issue even if it's not in the list as long as you know how to rename the EXT packages to give them the right order (that's an issue you will also have with EVK but on EVK you'll probably have many more unless you use an adapted version for your phone with the right packages already recmodded inside).
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.
Click to expand...
Click to collapse
Thank you for answer.
Can you help me with setting in htcrt_devices.ini ????

Johan Kraczmar said:
Thank you for answer.
Can you help me with setting in htcrt_devices.ini ????
Click to expand...
Click to collapse
osKitchen doesn't need that file because it automatically detects the NBH structure trough libNB; that's why I told you it should work even if the device is not on the supported list. As long as platformrebuilder doesn't cause some trouble (EVK is platformrebuilder-based too) oskitchen can work with any ROM as long as it can import and build the format (and NBH of course is supported).

Everything is clear.THX

airxtreme said:
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.
Click to expand...
Click to collapse
Just a small correction here: Barin's OSBuilder does not ignore that issue. In fact there in a tool in his kitchen to modify packages.sof, so that you can even modify the build order. This is important when adding new packages which have .dsm not in stock roms, to ensure that they are build in the preferred order (ie: tweaks last).
@ OP, if you do use EVK to dump and build, be sure to clean the dump of duplicate files inside modules after dump, which is an issue with EVK's dump process. Also, with EVK (and likely OSKithcne) you need to recmod NTFConfig.dll to get a bootable rom. This is also not an issue with Barin's OSBuilder, which I highly recommend to every chef. I find this kitchen to be a superb tool compared to any kitchen to date.

mmmm interesting kitchen... lets try something new... cause the winmo times are getting bored this days

indagroove said:
Just a small correction here: Barin's OSBuilder does not ignore that issue. In fact there in a tool in his kitchen to modify packages.sof, so that you can even modify the build order. This is important when adding new packages which have .dsm not in stock roms, to ensure that they are build in the preferred order (ie: tweaks last).
Click to expand...
Click to collapse
I've never tried that kitchen however I can tell you that how I've implemented shadow ordering support is pure bliss. For example as you probably know HTC ROMs rely on many virtual packages (Project Default and others) to guarantee the building order and if you delete one of them (some of these packages are completely empty) everything breaks and that the shadow dependencies are often done on localized packages so changing language could also cause havoc.
In my kitchen I normalize all the packages dependencies during import so that all the dependencies on LCID folders and on those virtual folders are gone (so those can be safely deleted), I have a package property tab to set the shadow order of any package (if the DSM is not there it will be created), it has detailed checks for short circuits (infinite dependencies loop), etc. It's really, really well done.
indagroove said:
@ OP, if you do use EVK to dump and build, be sure to clean the dump of duplicate files inside modules after dump, which is an issue with EVK's dump process. Also, with EVK (and likely OSKithcne) you need to recmod NTFConfig.dll to get a bootable rom. This is also not an issue with Barin's OSBuilder, which I highly recommend to every chef. I find this kitchen to be a superb tool compared to any kitchen to date.
Click to expand...
Click to collapse
Well the two kitchens are in two completely different leagues: OSBuilder seems to be aimed to rebuild the ROM as best as possible following the microsoft standards (for example only flat packages, no EXT) while mine is aimed at offering the most complete and easy solution indeed the autoimport, (there is no informations associated to the device names in the import list, the kitchen finds everything out by itself to rebuild the NBH/BIN/TSW for that device), batch multi-language ROMs generation, easily structured UI and also all the warnings to limit user mistakes to minimum, from an easy automatically recmodding of packages that prb dislikes to much crazier extents like checking the Radio/splash files signatures are OK or making sure the user doesn't try to import packages from the wrong folder (like C:\) destroying his filesystem. Just because my kitchen is (sadly) still platformrebuilder-based it doesn't mean it has to be trashed though: as you may know Da_G is rewriting all the tools properly (100% compliant to the original standards) and I'm adapting his LibNB functions to the kitchen as soon as those became available hence the actual ability of dump/rebuild any NBH correctly without even knowing what device it is and hopefully soon internal XIP porting so that the kitchen will be already able (with extreloc for the IMGFS) to build its own ROMs for any device without any of the platformrebuilder limitations.

[Q] Are modules not required cert but files required?

I try to cook a ROM for my Acer neoTouch S200(F1), I could finish it for me, thanks hdubli, DimICE and rafyvitto
I just use a few tools but not GUI kitchen so that I could learn more about making ROMs:
xidump.exe for dumping
osnbtool.exe for dumping and rebuild the ROM
RecMod.exe
ImgfsFromDump.exe, BuildOS.exe, EXTReloc.exe
XIPPort.exe
f1extromtool.exe for ExtROM
At the same time, I'm porting EZInput CHT form HD2 Leo...
Of cause, I want to porting EZinput CHT in cab from, for anyone who don't use custom ROM besides HTC.
Questions:
1. I'm not sure that was RecMod disadvantage or bugs, it seems that the files after RecMod would lost the cert... (#2)
2. Then it could cause a ton of problems, such as how can I indicate files needed to re-sign? Any tools could port a cert to another file?
Or have to patch a ton of files even a whole OEM packages?
3. Would the modules at Slot 61 could reduces the actual free RAM of process (shown in the memory page), even the process not using these modules? Then, how to estimate the minimum RAM used?

You can't sign the modules - only the files.

utak3r said:
You can't sign the modules - only the files.
Click to expand...
Click to collapse
Then, could the SDKcert could be hacked for changing name of signer?
or how to make the cert for it?
Moreover, the difficult problems is that how to sign all the unsign dll and exe with SDKcert easier?

You can just cert patch the nk.exe and not have to worry about the problem (with EVK, just check a box). More to the point, what errors are you getting, and are you sure it's actually a certificate error and not a 'missing component' error?

Farmer Ted said:
You can just cert patch the nk.exe and not have to worry about the problem (with EVK, just check a box). More to the point, what errors are you getting, and are you sure it's actually a certificate error and not a 'missing component' error?
Click to expand...
Click to collapse
I'm not using EVK, because I'm cooking for Acer S200, then I just use a few tools...
Emmm, no any certificate error or 'missing component' error, just the services or programs could not be able to auto start.
Patch nk.exe could be a good choice for cook, but not the best for the user, I think.
However, for patch nk.exe, it still followes this thread?
http://forum.xda-developers.com/showthread.php?t=384137

Nagato Yuki said:
I'm not using EVK, because I'm cooking for Acer S200, then I just use a few tools...
Emmm, no any certificate error or 'missing component' error, just the services or programs could not be able to auto start.
Patch nk.exe could be a good choice for cook, but not the best for the user, I think.
However, for patch nk.exe, it still followes this thread?
http://forum.xda-developers.com/showthread.php?t=384137
Click to expand...
Click to collapse
so please tell us what is exactly your trouble... cause:
1.- cert patches are now a unusual issue cause the kitchens already has certs pkg included to void this things.
2.- use the xipporterexe in EVK to patch your nk.exe thats all then readd your nk to your kitchen.
3.- certs issues are
a) when you tap... it shows a dialog saying is not trusted signed or has missing compoenents...
a1.- this means (obviously after you add the certs pkg or enable the kit5chen option or whatever to fix it) that the lnk is pointed to a non complete PKG it has missed some files, due to "maybe" it needs the app files in program files or a bad pkg creation (app.reg or app.dat) (or initflash oem pkgs)
4.- why patch nk.exe is not the best option to users??? i guess is the best cause if they use a devs app it will works with a cert patched nk
5.- the service or apps wont auto launch.... mmmm you must to xplain better cause it seems not related to certs matbe autoshortcut.. initflashfiles or app.dat troubles or corrupted PKGS.
Advice: please please... post your device model, kitchen name and version, and sys oem version if posible
once you redesign your question i will change if you wish the name of the thread just have more help
keep it up

Much BIG THANKS for your reply
Because I am not use any GUI kitchens, at this time, it seems that no GUI kitchens for Acer S200, then I don't try EVR before.
(BTW, it seems that we lack of Universal GUI kitchens for any device? Because the process to make ROM could be much similar, except decompose and assemble back the ROM files. I'm trying to use osKichens... )
In my case, there no any dialog saying not trusted signed or has missing compoenents... It just doesn't run for apps.
For services, they could not be able to start automatically, but I could start them manually though Dotfred's TaskMgr, no any dialog happen also, but they could run correct functionally !
Then I sign with SDKcert, they work normally.
For patching nk.exe, it could be very difficult for users who just want to use official ROM, but want to use apps form dev. But sign the cert and import the sign could be much easier...
Then it leads the second question. I'm seeking any effect ways to Recmod and sign them with sdkcert ...
Of cause, I want sign them much look like OEM ones (subject's and issuer's names), but just using SDKcert only for running.
Moreover, XipporterEx for patching nk.exe, it seems that there is no standalone one for porting WM 6.5.x one. And also I'm not sure that besides EXTReloc, Is there any Reloc programs compatible for Acer S200/WM6.5?
p.s. I could try to modify my questions later, but if someone help could be much nicer. So, +Que, please feel free to change my topic for better one

[Q] [PROBLEM][HERMES-TYTN]Default.hv cooked ROM

Hi,
I have a really strange problem.
I have two HTC HERMES, one good that I use and a second that I use only fot test purposes because it's not in good conditions.
I cook ROMs with "ROMDonalds Kitchen" and I have neved had any problem.
Since yesterday, every new ROM I cook, I have this problem:
if I don't edit "default.hv" the cooked ROM goes well in both my HERMES, but if I edit it, the ROM can only be loaded on the second HERMES (the one not in good conditions).
In the other HERMES after flashing, when I make the reset or even the hard-reset, the ROM begins to boot but then stops after the first splash-screen and the screen becames white.
I always flash from SD (hermimg.nbh).
What can be the problem?
Can be a problem of the good HERMES of the two I have?
Can be a difference in hardware between the good HERMES, even if they are identical from outside?
Many thanks !

Hi,
I don't understand why you need to edit default.hv but probably you have your reason.
It's better to leave it untouched to my opinion.
To edit the registry you can edit the .rgu in the specific package or create
a new package with the new registry overwriting the first package registry.
The second suggestion you can keep your tweaks in every rom you cook and switch the stock packages more easy.
What you are writing is indeed weird but this way you avoid errors in the .hv files.
Edit; btw, because Hermes is a pretty old device I'm asuming the kitchen you use is still using .rgu instead of .reg in the packages, latest kitchens mostly use .reg
.rgu and .reg files are same and containing the registry.
Grtz,
Laurentius26

yeah its true, what do you change in the d.hv? maybe you can tell us, what about to use another kitchen? or do your changes in app.reg ext pkgs or in oem packages to void edit it

I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks

Airxtreme's Oskitchen or Barin's OSbuilder, they are both in Chef Central here.
You don't need to edit .hv files as when you remove the package all registry of that package will be gone too.
eryunt said:
I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks
Click to expand...
Click to collapse

I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.

Wow, that's gotta be a huge pain in the butt.

ai6908 said:
I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.
Click to expand...
Click to collapse
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?

eryunt said:
...Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?...
Click to expand...
Click to collapse
If you mean the fixed address - the answer is No. *.hv are files and files do not have the fixed address.

I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!

Hi,
I don't know what you are doing to setup Ervius?
Are you importing a new stock rom into the kitchen?
The errors you can check:
Ervius kitchen/Rom/Shared/'Sys build'/MSXipkernel/
boot.rgu and the .dsm should be there.
Without boot.rgu and the dsm the rom won't boot.
Are all your desktop system files unhidden and vissible?
eryunt said:
I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!
Click to expand...
Click to collapse

The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...

I advise you to use a stock rom as you can test if everything is working ok.
After this you can do your modifications.
I know it's a bit of work but the advantage is to use a new kitchen which is much more configurable.
Editing .hv files isn't that good, but we talked about that already.
Another tip, I always zip my kitchen after I know a configuration is working and I flashed the rom succsesvol, before I continue to the next step.
eryunt said:
The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...
Click to expand...
Click to collapse

eryunt said:
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?
Click to expand...
Click to collapse
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...

ai6908 said:
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...
Click to expand...
Click to collapse
That's the point...It's a nonsense..
I've already tried to flash stock ROM on both devices before flashing the cooked ROM, but It's always the same nonsense, one loads the ROM, the other doesn't...
At this point only a malfunction or a difference in hardware between my two devices could explain this strange behaviour
Don't know how to solve...

are you trying to recook my roms? hahaha just kiddin
everybody knows that we don thave bootable and full dumped roms from customized ones, due to DSMsif you want to make a roms looks like or be something like a... i recommend to ask for the kitchen many retired chefs on Legacy devices can share it to you or just dump the rom and xtract the things you want
but make your own Stock OEM an set good your Native Kernel