Ok.. I'm able to dump the rom.. Have anothe issue though.. When I try creating a rom... I get a error saying "FOUND MODULE ON DUPLICATE MODULE.. Can anybody explain what is this ??.. Cheers..
[TUT] Sous-Chef's Guide to Da_G's Ervius Visual Kitchen 9.7
- Thread starter hilaireg
- Start date
Can you attach a copy of the kitchen BUILD_LOG for me to look at?
My first guess is that you have some packages with the same modules (filenames). During the build, the first file (from the duplicates) encountered is usually the one that will end up in the build.
Cheers,
My first guess is that you have some packages with the same modules (filenames). During the build, the first file (from the duplicates) encountered is usually the one that will end up in the build.
Cheers,
Yeah I think you are right.. I have in a way messed up the entire kitchen.. I extracted a 6.1 Rom.. And then added some packages (mainly all the ones realated to Manila) from the a 6.5 rom kitchen.. And thus the problem !!.. Anyways.. I'm not able to find the BULD LOG in the kitchen.. I guess the log file is created only when a process is completed.. The problem in my case is.. When I try to build the rom, it gives me the error and then gets stuck..
.. SO NO BUILD LOG !!!Could you tell me what I could do ??.. Sorry to be a pain.. CHEERS !!
Yeah I think you are right.. I have in a way messed up the entire kitchen.. I extracted a 6.1 Rom. ... I'm not able to find the BULD LOG in the kitchen.. I guess the log file is created only when a process is completed... The problem in my case is.. When I try to build the rom, it gives me the error and then gets stuck..
The tutorial kitchen tools are version 9.7; Ervius had not included logging capabilities to the kitchen at that time. A few posts back in this thread, I attached a .ZIP file that contains modifications which will provide logging.
If you have gotten comfortable with the workings of the kitchen in this tutorial, I suggest one of the following paths:
Path 1: Download the 6.1 kitchen from the RAPH thread and use it as a starting point.
Path 2: Dowload the last Da_G 6.5 kitchen from his RAPH thread and use it as a starting point.
Path 3: Upgrade the tools in your kitchen to version 1.8.1 found on Post 1 of the Ervius kitchen thread.
I suggest using the OEM's from the Manila thread in the Dev & Hacking forum as opposed to porting the packages from the 6.5 kitchen. Porting packages used in a 6.5 kitchen can be challenging as there are significant differences such as HTC files.
For example, HTC released a new HTCScroll2 for WinMO 6.5 whereas WinMO 6.1 uses HTCScroll - porting packages often requires awareness that additional files from another package may be needed.
Cheers,
Last edited:
Thanks!
Hey Hilaireg,
Thank you very much for this awesome guide. I didn't want to make the switch over from legacy but I figured while I was waiting for HardSPL for Rhodium I would make the switch. Your guide made it a lot easier than I thought
One question...
Your tips in posts 5-10, I prefer to do them with XIPPorter & ROM Tools. I am guessing I can just remove the lines or not add them so they are not done at the end of ROM creation with no ill side effects?
Thanks!
Hey Hilaireg,
Thank you very much for this awesome guide. I didn't want to make the switch over from legacy but I figured while I was waiting for HardSPL for Rhodium I would make the switch. Your guide made it a lot easier than I thought
One question...
Your tips in posts 5-10, I prefer to do them with XIPPorter & ROM Tools. I am guessing I can just remove the lines or not add them so they are not done at the end of ROM creation with no ill side effects?
Thanks!
Hi At0mAng,
I put the tutorial together during a time when the Visual Kitchen required manual editing of the BAT file to pass those parameters during ROM compilation. So yes, you could use the built-in XIPPORTEREX & ROM Tools to achieve the same results. That said, changing the values via BAT ensures that the source files remain "untouched" - copies are placed in the TEMP folder and modified.
Also, newer versions of the Ervius Visual Kitchen now include an "Other" button which permits chefs to set the parameters via the kitchen instead of editing the BAT file.
Cheers,
I put the tutorial together during a time when the Visual Kitchen required manual editing of the BAT file to pass those parameters during ROM compilation. So yes, you could use the built-in XIPPORTEREX & ROM Tools to achieve the same results. That said, changing the values via BAT ensures that the source files remain "untouched" - copies are placed in the TEMP folder and modified.
Also, newer versions of the Ervius Visual Kitchen now include an "Other" button which permits chefs to set the parameters via the kitchen instead of editing the BAT file.
Cheers,
Last edited:
The Visual Kitchen included in this tutorial is version 9.7; which did not include the "Other" button and logging. Ervius updated the kitchen several times during the period that I was writing the tutorial, so I can't recall exactly which version started having the "Other" button and logging.
Around version 9.9, he decided to roll the version number back to 1.0 (aka 10.0). Currently, the latest version of the kitchen tools are on the first post of his thread (http://xdaforums.com/showthread.php?t=469420) - version 1.8.1 (aka 10.8.1).
I suggest you download that set of tools as it sports the most recent set of bug fixes (and there were many) as well as: logging, Other button, package color coding, etc.
Confused yet?
Around version 9.9, he decided to roll the version number back to 1.0 (aka 10.0). Currently, the latest version of the kitchen tools are on the first post of his thread (http://xdaforums.com/showthread.php?t=469420) - version 1.8.1 (aka 10.8.1).
I suggest you download that set of tools as it sports the most recent set of bug fixes (and there were many) as well as: logging, Other button, package color coding, etc.
Confused yet?
Attachments
Last edited:
The Visual Kitchen included in this tutorial is version 9.7; which did not include the "Other" button and logging. Ervius updated the kitchen several times during the period that I was writing the tutorial, so I can't recall exactly which version started having the "Other" button and logging.
Around version 9.9, he decided to roll the version number back to 1.0 (aka 10.0). Currently, the latest version of the kitchen tools are on the first post of his thread (http://xdaforums.com/showthread.php?t=469420) - version 1.8.1 (aka 10.8.1).
I suggest you download that set of tools as it sports the most recent set of bug fixes (and there were many) as well as: logging, Other button, package color coding, etc.
Confused yet?
LOL Just a bit...the other button was right in front of my face
What exactly does ImgStart do? Is -PP the pagepool size? And what is unlock folder?
Thanks...
<g> my 1,000 post
Congrats on your 1,000th post
If you set IMGSTART to zero (0), the kitchen will automatically determine the appropriate value. You can look in the BUILD_LOG to see what value was set.
PP is indeed the PagePool size, I usually leave it at 6MB. I'd suggest a bit of forum searching as there are mixed opinions on what the size should be.
The UNLOCK option was introduced to address issues where permissions on the TEMP folder would deny access to the compilation tools - I haven't personally experienced this issue.
HTH,
If you set IMGSTART to zero (0), the kitchen will automatically determine the appropriate value. You can look in the BUILD_LOG to see what value was set.
PP is indeed the PagePool size, I usually leave it at 6MB. I'd suggest a bit of forum searching as there are mixed opinions on what the size should be.
The UNLOCK option was introduced to address issues where permissions on the TEMP folder would deny access to the compilation tools - I haven't personally experienced this issue.
HTH,
Congrats on your 1,000th post
If you set IMGSTART to zero (0), the kitchen will automatically determine the appropriate value. You can look in the BUILD_LOG to see what value was set.
PP is indeed the PagePool size, I usually leave it at 6MB. I'd suggest a bit of forum searching as there are mixed opinions on what the size should be.
The UNLOCK option was introduced to address issues where permissions on the TEMP folder would deny access to the compilation tools - I haven't personally experienced this issue.
HTH,
Thanks, I just wanted to make sure I had the equivalent settings for what I do manually. I personally keep my pagepool to 16 and now that I see the Rhodium OEM 6.5 ROMs are at 20 I bumped it up. I am not sure what IMGSTART is, maybe it goes by another name in XIPPorter? Will look it up
Is there a way to turn off the those settings in VK? If I put in 0 for PP it won't accept it and I have not discovered a way not apply any settings to payload...
AFAIK, the default PP size is 6MB. You will want to Cert Patch the ROM and the default is to perform ULDR reduction.
As for IMGSTART, I would suggest leaving it as-is and the kitchen should take care of it for you. AFAIK, this is equivalent to XIPPORTEREX -> ROM Tools, Give From XIP_OUT -> Write IT -> Done. You can always post the question in the Ervius VK thread for confirmation.
Cheers,
As for IMGSTART, I would suggest leaving it as-is and the kitchen should take care of it for you. AFAIK, this is equivalent to XIPPORTEREX -> ROM Tools, Give From XIP_OUT -> Write IT -> Done. You can always post the question in the Ervius VK thread for confirmation.
Cheers,
19/08/2009: Tutorial Update
Had a few requests for this now.
Added .ZIP which contains each thread post of the tutorial for folks who want to create a similar tutorial format in other device forums. All I ask is that folks not blindly copy the contents of each post file - please proof-read your final product to ensure that it applies to the device in question.
Cheers,
Had a few requests for this now.
Added .ZIP which contains each thread post of the tutorial for folks who want to create a similar tutorial format in other device forums. All I ask is that folks not blindly copy the contents of each post file - please proof-read your final product to ensure that it applies to the device in question.
Cheers,
Last edited:
Boot RGU
Followed the directions up to Post #7. Not easy but made it that far. I'm trying to go through the directions with the recommended files as shown in the directions as a learning experience.
Can't find Boot.RGU in the location indicated and can't find it anywhere in the XDA directory.
Any suggestions where it might be?
CalifDan
Followed the directions up to Post #7. Not easy but made it that far. I'm trying to go through the directions with the recommended files as shown in the directions as a learning experience.
Can't find Boot.RGU in the location indicated and can't find it anywhere in the XDA directory.
Any suggestions where it might be?
CalifDan
Hi CalifDan,
BOOT.RGU should be present in:
C:\XDA\My_Visual_Kitchen\ROM\Raphael\#####\OEMXipKernel
Not sure which O/S you are using, but did you make sure to change the following Folder Options?
- Show Hidden Files And Folders (Selected)
- Hide Extensions For Known Files Types (unchecked)
- Hide Protected Operations Systems Files (Unchecked)
HTH,
BOOT.RGU should be present in:
C:\XDA\My_Visual_Kitchen\ROM\Raphael\#####\OEMXipKernel
Not sure which O/S you are using, but did you make sure to change the following Folder Options?
- Show Hidden Files And Folders (Selected)
- Hide Extensions For Known Files Types (unchecked)
- Hide Protected Operations Systems Files (Unchecked)
HTH,
Last edited:
mxipupdate_oemoperators_100.provxml?
i have gotten this far but now that im at changing unsigned cab policies i cant find this file; mxipupdate_oemoperators_100.provxml. i have looked exactly where u specified but cant find it. i even redownloaded the kitchen to see if a file was corrupted during download but that wasnt it. i cant find this file anywhere. Help?
i have gotten this far but now that im at changing unsigned cab policies i cant find this file; mxipupdate_oemoperators_100.provxml. i have looked exactly where u specified but cant find it. i even redownloaded the kitchen to see if a file was corrupted during download but that wasnt it. i cant find this file anywhere. Help?
Hi gundamstrike315,
Few things to check:
- make sure that you workstation is set to display Hidden & System files as well as file extensions
- The .provxml files are usually found in the following location after extracting an official ROM:
C:\XDA\MY_VISUAL_KITCHEN\OEM\<device>\<lang>\Operator Pkg\
HTH,
Few things to check:
- make sure that you workstation is set to display Hidden & System files as well as file extensions
- The .provxml files are usually found in the following location after extracting an official ROM:
C:\XDA\MY_VISUAL_KITCHEN\OEM\<device>\<lang>\Operator Pkg\
HTH,
further along, not quite there yet...
alright, i really appreciate your help so far hilaireg. im almost to the end of the process as you explained, just got a couple more questions. first off, should i be using the generic kitchen u link in the first part of the tut. or Da_G's kitchen? second, when i get through the whole process and get my finished rom loaded on my touch pro it wont boot. it just shows the TP splash screen for a while then reboots. i noticed that the bunch of red letters that show up at the bottom dont appear. what am i doing wrong?
alright, i really appreciate your help so far hilaireg. im almost to the end of the process as you explained, just got a couple more questions. first off, should i be using the generic kitchen u link in the first part of the tut. or Da_G's kitchen? second, when i get through the whole process and get my finished rom loaded on my touch pro it wont boot. it just shows the TP splash screen for a while then reboots. i noticed that the bunch of red letters that show up at the bottom dont appear. what am i doing wrong?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Version: 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=4453962Extracting 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.
- Copy the RUU_SIGNED.NBH file to the C:\XDA\My_Visual_Kitchen\BaseROM\ folder.
- Navigate to the C:\XDA\My_Visual_Kitchen\ folder.
- Launch ErviusKitchen.exe.
- 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
- Click the Dump NBH/NB/PAYLOAD button.
- Navigate to the C:\XDA\MY_VISUAL_KITCHEN\BaseROM\ folder.
- Select the RUU_signed.nbh file and then click Open.
- At the All Done... Nbh/nb/payload Dumped and ''Kitchen'' created Successfull!!! message, close the Ervius Visual Kitchen application.
- Navigate to the C:\XDA\MY_VISUAL_KITCHEN\DUMP\ folder.
- Move the sub-folders (and content) to the C:\XDA\MY_VISUAL_KITCHEN\ folder.
- At the Confirm Folder Replace message, click Yes To All.
- 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.
2Reducing 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