[TUT] Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7

Search This thread

sureshot007

Senior Member
Mar 24, 2008
155
19
Sorry for the newb question, but I didn't notice the answer to my question in the thread (or else it's there and I didn't recognize it).

How do I take .cab files and add them to the kitchen?
 

hilaireg

Moderator Emeritus
Jan 20, 2009
2,948
237
Hi sureshot007,

You are correct. The tutorial doesn't get into the details of converting .CAB files into OEM packages for use in a Visual Kitchen or how to integrate a .CAB as part of the "first boot" process.

Package Conversion: converting .CAB to OEM packages requires a substantial amount of knowledge. There are tools "floating" around on the forum that assist in the conversion process; however, most converted .CAB applications require some additional manual work for them to function.

.CAB In ROM: this alternative installs .CAB applications as part of the "first boot" process. This is typically accomplished by placing the .CAB files into OEM Operator package that is usually present and adding the .CAB file name to the CONFIG or AutoRun/RunCC processing engine. Here again, there are pitfalls such as interactive .CAB installers, improperly engineered .CAB, etc.


So in short, I've been too busy to write a comprehensive .CAB <-> OEM tutorial.

:eek:
 
G

GuestK00433

Guest
Hi, awesome tutorial, but i cant find a RUU_SIGNED.NBH file, i got a Win 2003 Rom and i got a NK.nbF file not NBH, it might be a noob question but i really want to cook a ROM
 

hilaireg

Moderator Emeritus
Jan 20, 2009
2,948
237
Hi, awesome tutorial, but i cant find a RUU_SIGNED.NBH file, i got a Win 2003 Rom and i got a NK.nbF file not NBH, it might be a noob question but i really want to cook a ROM

Hi zainuintel,

The tutorial was built around extraction of an official HTC WinMO 6.x ROM. Have a look at the Chef Central and possibly post your question in there.

You'll likely need to provide some info as to what device you're trying to chef a ROM for so that fellow chefs can provide you with some relevant guidance.

Cheers,
 

Farmer Ted

Senior Member
Nov 30, 2008
2,373
90
Hi, awesome tutorial, but i cant find a RUU_SIGNED.NBH file, i got a Win 2003 Rom and i got a NK.nbF file not NBH, it might be a noob question but i really want to cook a ROM

I think you're going to have trouble finding the tools you need to cook (and flash) a 2003 rom. That would be cool, though. I've got an old 2003 device that I still use for some things, and would love to cook a simple rom for it. You may find a thread or two in the chef forum, but I don't think there's much help there. The best bet may be to look around the old forums here for 2003 devices and see what you can find. A lot of the tools may not be available to download anymore, though.
 

MMbiehn

New member
Dec 9, 2023
1
0
Version: 31/05/2009

Intro

Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is. Hopefully, this guide will help you work your way up the ranks to Chef … let’s begin!

There are many chefs that provide quality ROM's for you to use. However, if you've gotten excited about the idea of cooking your own ROM's, you've probably felt overwhelmed by the volume of Forum Threads and Wiki pages at your disposal to learn how to do this.

The sections are intended to be followed in sequence as the last section should provide you with a final product that can be flashed to your device – so you may want to read this guide once over before going through the motions … who am I kidding? You’re going to follow along aren’t you? ;)

In case you're wondering ... I chose Sous-Chef because Commis or Chef De Partie just didn't have the same appeal :)


Applying Original/Cooked ROM's

You probably won't be able to apply an Original or Cooked ROM to your device as your Cellular Carrier has most certainly locked your device. You'll need to unlock your device before venturing into the world of ROM installation. These activities are beyond the scope of this guide; you can however, go to this Wiki page to learn more.

HTC Raphael
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael


Original VS Cooked ROM's
HTC periodically releases Official Generic ROM's that you can apply to your device. You can find a list of Original Shipped WM6.1 ROM's at this Wiki page.

Original Shipped WM6.1 ROMS
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_WM6.1_ROMs


There are essentially two types of Cooked ROM's; those that another Chef makes available for you to use, and those that you cook yourself. You can find a list of Available Cooked WM6.1 ROM's at this Wiki page.

Available Cooked WM6.1 ROMS
http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_Cooked_WM6.1_ROMs


Outro

Lastly, this guide only covers the ROM cooking process; changing your device Startup Splash Screen and Radio or flashing a HardSPL are beyond the scope of this guide; you can however, go to these Wiki and/or Forum pages to learn more.

Radio
http://wiki.xda-developers.com/index.php?pagename=Raphael_ExtractedRadioRoms
http://xdaforums.com/showthread.php?t=439566

Startup Splash Screen
http://xdaforums.com/showthread.php?t=431161

Hard SPL
http://wiki.xda-developers.com/index.php?pagename=Raphael_HardSPL


This guide is intended to help you learn how to cook your own ROM's; it will walk you through the process of extracting the contents of an Official ROM, adjusting the Page Pool, changing the Data Cache Size, and Patching the ROM to remove Certificate verification. The guide does not cover the steps required to add/remove ROM packages or port an XIP from a different ROM version or device ... not yet anyway ;)

Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk. If you spot mistakes or inaccuracies in the guide however, please let me know so that I may correct them. Now, read on if you still feel that this is your choice career path ;)

Oh, one last thing ... to the following folks for sharing their knowledge with the rest of us ... thank you!

Da_G
Ameet
Bepe
Cmonex
Ervius
JCEspi2005
JugglerLKR
mskip
Olipro
Aruppenthal
NRGZ28
Noonski

If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
Hi,
How can I access the linked site wiki.xda-developers? There's only login option but no sign-up. Impossible to access your links. Thank you in advance.
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,985
2
10,009
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
Hi,
How can I access the linked site wiki.xda-developers? There's only login option but no sign-up. Impossible to access your links. Thank you in advance.
Not sure about access, but you can view wayback machine backups here
https://web.archive.org/web/*/http://wiki.xda-developers.com/index.php

Screenshot 2023-12-10 074319.png

There were a lot of changes from 2004-2009, then stopped.

I think it may have been moved to
Code:
http://forum.xda-developers.com/wiki/
That was discontinued in Dec 2020
You can view a backup on the Wayback Machine
https://web.archive.org/web/20190805103640/https://forum.xda-developers.com/wiki/

Screenshot 2023-12-10 074835.png
 
Last edited:
  • Like
Reactions: Oswald Boelcke

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Version: 31/05/2009

    Intro

    Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is. Hopefully, this guide will help you work your way up the ranks to Chef … let’s begin!

    There are many chefs that provide quality ROM's for you to use. However, if you've gotten excited about the idea of cooking your own ROM's, you've probably felt overwhelmed by the volume of Forum Threads and Wiki pages at your disposal to learn how to do this.

    The sections are intended to be followed in sequence as the last section should provide you with a final product that can be flashed to your device – so you may want to read this guide once over before going through the motions … who am I kidding? You’re going to follow along aren’t you? ;)

    In case you're wondering ... I chose Sous-Chef because Commis or Chef De Partie just didn't have the same appeal :)


    Applying Original/Cooked ROM's

    You probably won't be able to apply an Original or Cooked ROM to your device as your Cellular Carrier has most certainly locked your device. You'll need to unlock your device before venturing into the world of ROM installation. These activities are beyond the scope of this guide; you can however, go to this Wiki page to learn more.

    HTC Raphael
    http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael


    Original VS Cooked ROM's
    HTC periodically releases Official Generic ROM's that you can apply to your device. You can find a list of Original Shipped WM6.1 ROM's at this Wiki page.

    Original Shipped WM6.1 ROMS
    http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_WM6.1_ROMs


    There are essentially two types of Cooked ROM's; those that another Chef makes available for you to use, and those that you cook yourself. You can find a list of Available Cooked WM6.1 ROM's at this Wiki page.

    Available Cooked WM6.1 ROMS
    http://wiki.xda-developers.com/index.php?pagename=HTC_Raphael_Cooked_WM6.1_ROMs


    Outro

    Lastly, this guide only covers the ROM cooking process; changing your device Startup Splash Screen and Radio or flashing a HardSPL are beyond the scope of this guide; you can however, go to these Wiki and/or Forum pages to learn more.

    Radio
    http://wiki.xda-developers.com/index.php?pagename=Raphael_ExtractedRadioRoms
    http://xdaforums.com/showthread.php?t=439566

    Startup Splash Screen
    http://xdaforums.com/showthread.php?t=431161

    Hard SPL
    http://wiki.xda-developers.com/index.php?pagename=Raphael_HardSPL


    This guide is intended to help you learn how to cook your own ROM's; it will walk you through the process of extracting the contents of an Official ROM, adjusting the Page Pool, changing the Data Cache Size, and Patching the ROM to remove Certificate verification. The guide does not cover the steps required to add/remove ROM packages or port an XIP from a different ROM version or device ... not yet anyway ;)

    Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk. If you spot mistakes or inaccuracies in the guide however, please let me know so that I may correct them. Now, read on if you still feel that this is your choice career path ;)

    Oh, one last thing ... to the following folks for sharing their knowledge with the rest of us ... thank you!

    Da_G
    Ameet
    Bepe
    Cmonex
    Ervius
    JCEspi2005
    JugglerLKR
    mskip
    Olipro
    Aruppenthal
    NRGZ28
    Noonski

    If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
    3
    [TUT] Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7 ... continued

    Location, Location, Location

    There are many fine Kitchens out there to use; Semi-Automated Kitchens (Raphael, Da_G), Automated Kitchens (Bepe), and Visual Kitchens (Ervius). This guide uses the Ervius Visual Kitchen to assist you in learning the basics of operating a Kitchen; which ultimately, allows you to produce your own ROM.

    References

    Ervius..: http://xdaforums.com/showthread.php?t=469420
    Da_G....: http://xdaforums.com/showthread.php?t=471288
    Raphael.: http://xdaforums.com/showthread.php?p=2453788
    Bepe....: http://xdaforums.com/showthread.php?t=467488




    Inspecting the Facility

    It’s important to get acquainted with any new facility; last thing you want to find out is that you don’t know where to plug your utensils or appliances. Here’s a brief tour of the facilities to get you on your way.


    EXT Folder

    The External packages (EXT) folder is divided into Device Specific folders and a Shared folder. The Shared folder is typically used for files (packages) that can be installed on any device. Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device – for example, the Raphael device.

    Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder. The Common folder is typically used for files (packages) that can be installed on any Operating System build version. Operating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System – for example, build version 20764.

    Operating System Build Version Specific folders, the Common folder, and the Shared folder can be further divided into sub-folders making file (package) management simpler – for example, .\Raphael\20764\Raphael_External_Packages.

    Tip
    • The EXT Build drop-down box in the Visual Kitchen permits selection of different Operating System Build Version Specific folders.


    OEM Folder

    The OEM folder can contain multiple Device Specific folders. Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device – for example, the Raphael device.

    Each Device Specific folder is further divided into Locale Specific folders and a Common folder. The Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language. Locale Specific folders are typically used for files (packages) that should only be applied to a specific locale – for example, 0409 (English).

    Tip
    • The Language drop-down box in the Visual Kitchen permits selection of different Locale Specific folders.


    ROM Folder

    The ROM folder is divided into Device Specific folders and a Shared folder. The Shared folder is typically used for kernel system files that are compatible amongst devices. Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device – for example, the Raphael device.

    The Shared folder is further divided into Operating System Build Version Specific folders. Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System – for example, build version 20764.

    Each Device Specific folder is further divided into Operating System Build Version Specific folders. Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System – for example, build version 20764.

    Tip
    • The XIP Build drop-down box in the Visual Kitchen permits selection of different Operating System Build Version Specific folders.
    • Advanced OEMXipKernel and MSXipKernel operations can be performed using the XIPPORTEREX & ROM tool.


    SYS Folder

    The system (SYS) folder is divided into Operating System Build Version Specific folders. The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.

    Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.

    The ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder. The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language. Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).

    Tip
    • The ROM DPI and ROM Resolution drop-down boxes in the Visual Kitchen permits selection of different Operating System Build Version Specific resolution and bit depth.
    2
    [TUT] Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7 ... continued

    Preparing Your Facility

    Before you can begin to cook your own ROM, you need to equip your facility with some Kitchen utensils. Your Kitchen is going to require a good Unicode & UTF-8 text editor; I personally use ConTEXT & Notepad. Another handy utensil to have is a comparison utility for date/file/binary comparisons; I use WinDiff & BeyondCompare. Some other utensils that you're going to require are: Microsoft ActiveSync, .NET Framework 2.x/3.x. You will also need an archive extraction utensil; I use IZArc, WinRAR, and WinZIP. You’ll also need a good Hexadecimal calculator; I use Windows Calculator (Scientific Mode).

    It's also a good idea to ensure that your Kitchen remains "pest" free; common pest control services include AVG, McAfee, and Symantec anti-Virus. You'll need to add the RaphaelWrapper (OSNBTOOL.EXE) tool to your list of anti-virus exclusions as it may be detected as a "Generic Dropper (Trojan)".

    References

    CustomRUU for Raphael
    http://xdaforums.com/showthread.php?t=410761


    To assist you in your apprenticeship, I have included a link to the Generic Visual Kitchen that I used to prepare this guide - the kitchen also includes a .DOC and .PDF format of this guide. The procedures were tested against a GSM Raphael device. I can’t confirm that these procedures will work on CDMA device ROM’s. Additionally, other device ROM’s may not be compatible with this kitchen format. Make sure to review the _README.TXT before you begin.

    Generic Visual Kitchen, 17 MB


    You’re going to need a RUU_SIGNED.NBH file; I used the following HTC Official Generic ROM – you’ll need to extract the contents of the .EXE and .RAR/.ZIP using an archive utensil.

    [ROM] [WWE] Raphael HTC 5.05.405.1 Radio Signed (52.58.25.3 0,1.11.25.01)
    http://rapidshare.com/files/1939660...igned_Raphael_52.58.25.30_1.11.25.01_Ship.rar
    http://www.megaupload.com/?d=0F50UM5K


    For the purpose of this guide, I will assume that you have added the C:\XDA\ folder, sub-folder, and files to your anti-virus exclusion list – at the very least RaphaelWrapper.exe – and that the contents of the Generic Visual Kitchen were extracted to the following folder.

    C:\XDA\MY_VISUAL_KITCHEN


    The guide is divided into the following sections:

    Extracting the RUU_SIGNED.NBH Contents ....... 4
    Reducing the .PAYLOAD File ................... 5
    Extracting the XIP.BIN Contents .............. 6
    Increasing the Data Cache .................... 7
    Unlocking the Paging Pool .................... 8
    Disabling Certificate Checking ............... 9
    Reducing the Update Loader (ULDR) Partition .. 10
    Changing the Unsigned CAB Policies ........... 11
    Changing the Unsigned Themes Policies ........ 12
    Changing the Remote API (RAPI) Policies ...... 13
    Compiling the New RUU_SIGNED.NBH File ........ 14
    Flashing the RUU_SIGNED.NBH File ............. 15

    Advanced Topic: XIP Porting .................. 16

    Sous-Chef's TIPs ............................. 17




    I will attempt to provide an overview, the list of tools required, and the process to follow in each section. As you become more comfortable (and familiar) with the activities, you will find that you can consolidate (or skip) certain outlined steps. Incidentally, you'll probably want to keep these web links open in case you need to lookup some of the terms or concepts in the guide.

    Acronyms
    http://wiki.xda-developers.com/index.php?pagename=Acronyms

    Glossary
    http://wiki.xda-developers.com/index.php?pagename=Glossary

    Development Resources for Windows Mobile
    http://xdaforums.com/showthread.php?t=445396
    2
    Extracting the RUU_SIGNED.NBH Contents

    An .NBH is a signed group of modules or packages; they are typically comprised of .NB files. An .NBH can contain any combination of .NB files. An .NB file is a block of code that can be a Radio ROM, Operating System packages (XIP and IMGFS), Startup Splash Screen (or SPL).

    The file we will be working with is the OS.NB file; it contains the ULDR, XIP, and IMGFS (OEM, SYS). To extract the contents of an .NBH file, we initiate the Ervius NBH/NB/PAYLOAD Dumper tool from within the Generic Visual Kitchen.

    Upon completion, the following files will have been extracted: OS.nb, OS.nb.payload. Additionally, the Ervius NBH/NB/PAYLOAD Dumper tool creates a DUMP folder that contains all the files required.


    Tools Required:

    The following Ervius Visual Kitchen tool will be used for the RUU_SIGNED.NBH extraction activities.

    Dump NBH/NB/PAYLOAD



    Procedure

    The following procedure initiates the ROM extraction activity via the Ervius NBH/NB/PAYLOAD Dumper tool built into the Generic Visual Kitchen. The extraction process can take a significant amount of time to complete.

    1. Copy the RUU_SIGNED.NBH file to the C:\XDA\My_Visual_Kitchen\BaseROM\ folder.

    2. Navigate to the C:\XDA\My_Visual_Kitchen\ folder.
    3. Launch ErviusKitchen.exe.
    4. At the multiple warning messages, click OK.

      Warnings that may appear include:

      Folder Not Found
      Could Not Find A Part Of The Path
      You Need To Specify … First


    5. Click the Dump NBH/NB/PAYLOAD button.
    6. Navigate to the C:\XDA\MY_VISUAL_KITCHEN\BaseROM\ folder.
    7. Select the RUU_signed.nbh file and then click Open.
    8. At the All Done... Nbh/nb/payload Dumped and ''Kitchen'' created Successfull!!! message, close the Ervius Visual Kitchen application.
    9. Navigate to the C:\XDA\MY_VISUAL_KITCHEN\DUMP\ folder.

    10. Move the sub-folders (and content) to the C:\XDA\MY_VISUAL_KITCHEN\ folder.

    11. At the Confirm Folder Replace message, click Yes To All.
    12. At the Confirm File Move message, click Yes To All.

    Tip

    • The C:\XDA\MY_VISUAL_KITCHEN\BaseROM\Dump\ folder should be empty at this point – and can be removed.
    2
    Reducing the .PAYLOAD File

    At this point, the Ervius NBH/NB/PAYLOAD Dumper tool has removed the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file reduces the size of the .PAYLOAD file making it easier to work with.

    The Ervius NBH/NB/PAYLOAD Dumper tool has placed a copy of the reduced .PAYLOAD file in the C:\XDA\My_Visual_Kitchen\ROM\Raphael\ folder.


    Tip
    • Advanced .PAYLOAD file operations can be performed using the XIPPORTEREX & ROM tool.


    References

    [TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
    http://xdaforums.com/showthread.php?t=438676