New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Tip us?
 
Dark9781
Old
(Last edited by Dark9781; 18th June 2010 at 04:47 AM.)
#1  
Dark9781's Avatar
Senior Member - OP
Thanks Meter 96
Posts: 409
Join Date: Apr 2009
Default How to Cook ROMs using Spocky's kitchen

HOW TO COOK ROMS USING SPOCKY'S KITCHEN


1. Download the kitchen and unzip it.

2. Download the eXpo or IQ base rom and place it in the folder BaseRom\GW820 (the file will have a dz extention)

3. Launch Start.bat and enter 7 and press enter. This will allow the kitchen to know you are building a rom for the for the eXpo/IQ.

4. Press a then enter. This will extract the files you need to build a rom from the .dz file.

5. Press b then enter. This will extract the files from the flash.bin file. It will also create a xip.bin file in
TOOLS\XIPPORT. If you are not porting a new build don't worry about the xip.bin file. If you are porting
a new build we will get to that soon.

6. Press c then enter. This will extract the sys files and the oem files into the temp\dump folder.

7. Now you are going to arrange your files that are in temp\dump into two separate folders OEM\GW820
and SYS\YourBuildVersion (eg. SYS\23563). Here is what you will put in each folder:

*Note: If you are porting a new build (such as a 6.5.5 build) you will be downloading the files that
match your build and will not find them in the temp\dump folder.

a. You will see a folder named OEM. Take the contents of that folder and put it into OEM\GW820.

b. Now you will create 3 folders within SYS\YourBuildNumber. DPI_192, dpi_192_resh_480_resv_800,
and SHARED.

c. Now within each of those folders you will create two folders; 0409 and COMMON.

d. Now go back to temp\dump (I recommend having two windows open. One for temp\dump and the
the other for SYS\YourBuildNumber.) Go into the temp\dump\SYS\0409 folder. Now copy every folder
ending in Lang_0409_DPI_192 into your DPI_192\0409 folder.

e. Next copy all files ending in DPI_192 from temp\dump\SYS\COMMON folder to your
DPI_192\COMMON.

f. After that copy Base_Lang_0409_DPI_192_RESH_480_RESV_800 and
Themes_Lang_0409_DPI_192_RESH_480_RESV_800 from temp\dump\0409 folder to
your dpi_192_resh_480_resv_800\0409.

g. Next copy base_dpi_192_resh_480_resv_800, MediaOS_dpi_192_resh_480_resv_800,
MediaOS_dpi_192_resh_480_resv_800, and Redist_dpi_192_resh_480_resv_800 from
temp\dump\SYS\COMMON to dpi_192_resh_480_resv_800\COMMON.

h. After that copy all files ending in Lang_0409 from temp\dump\SYS\0409 to SHARED\0409.

i. Finally copy all the rest of the files from temp\dump\SYS\COMMON to SHARED\COMMON.

*Note: If you are porting a build then do all of step 8. If you are rebuilding the stock rom do steps 8,
8d, 8e, 8m, 8n, and 8o. For some reason the kitchen won't build the rom properly if you don't.

8. Go back to the windows launched by start.bat. Press 9 and enter. This will bring up the options you will
use to port.
a. You will need a xip.bin that matches your build. It should come with the build files you downloaded.

b. Go to tools\xipport and rename the xip.bin that is in the folder. (eg. xip.GW820.bin) You will need this
file later.

c. Copy the xip.bin file you downloaded to tools\xipport. (Make sure it is named xip.bin)

d. On the start.bat windows press j and enter to launch xipport.

e. Click dump xip.bin

f. Click "make pkgs".

g. Now, you've got a "out" folder with files and modules separated in different subfolders.
Rename the out folder into something else. (eg. OUT.235xx).

h. Delete the downloaded xip.bin (or rename it if you want to save it) and rename the original
xip.bin back to xip.bin.

i. Repeat steps 8d-8f.

j. Now, you've got a out folder with files and modules separated in different subfolders from eXpo/IQ
base ROM.

k. Now replace modules\msxipkernel and files\msxipkernel with the ones from the newer xip.
(folder OUT.235xx)

l. Click "undo" to flatten out folder again.

m. Bring up the start.bat windows agin. Press k and enter. When a message tells you so, click "realloc
p", "write maps", "build xip_out.bin (ignore error messages in reallocp part). And finally, hit a key on
the dos prompt to finish this step (DO NOT HIT A KEY BEFORE BUILDING XIP WITH XIPPORT ELSE IT
WON'T WORK).

n. Bring up the start.bat windows and press "l" and enter to use the new xip in the kitchen
(xip_out.bin).

o. In the start.bat window press 9 and enter to go back to the normal options. (Now you have
everything you need to port. Proceed to step 9)

9. Bring up the start.bat windows and press d and enter. This will dump your xip.bin file.

10. Go to the ROM\GW820 folder. You will see a XIP folder. Go into that folder and then go into the
WinCENLS_WWE folder and copy the wince.nls file. Now go into the OEMXIPKERNEL and paste wince.nls in
there. After that copy the OEMXIPKERNEL folder. Next create a folder in ROM\GW820 and name it your
build # (eg. 23563). Now paste OEMXIPKERNEL into that folder. After that copy MSXIPKernel from
ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build # (eg. 23563). Paste
MSXIPKernel into that folder. It is important both folders are named the same.

*Note for those that are porting:
If you are porting a new build you need to go to TOOLS\XIPPORT\OUT.235xx\FILE\MSXIPKernel
and copy 723fb954-d931-4348-b672-82a188e587b5.dsm
After that paste the file in ROM\SHARED\YourBuildNumber\MSXIPKernel. This will allow the correct build
number to show in the about screen on your device

11. Bring up the start.bat window again. Press e and enter to launch the ervius visual platformrebuilder.
(Note: If building with vista or windows 7 you will need to right click on erviuskitchen, select
properties,choose the compatibility tab, check Run this program as an administrator, and click ok).
Once it is launched you will need to set a few options on the top bar of the kitchen. First select
GW820 as your device. Then select your rom res. Choose dpi_192_resh_480_resv_800. After that
select your XIP and SYS Builds. Finally you can select to leave out certain SYS files from your rom, but
do be warned that leaving out some SYS files can result in a rom that won't boot. Once you have
made all your selections click create rom. The kitchen will now build your rom. When it is done it will
launch a flashing program just exit it and the visual kitchen. Go back to the start.bat prompt.

12. Press f and enter. This will build the new imgfs.bin.

13. Press g and enter. This will build the new flash.bin.
There is an additional step for IQ owners. Download this ADD-ON FILE and place it in Baserom\GW820. Without it
you won't be able to repack the rom into a dz file.

14. Press h and enter. Then enter a name for your new rom (no spaces) and press enter. It will then create
a new dz file for you. You can find it in BuiltRom\GW820. It will be called rom.dz. This is the file you will
use to flash your phone.

Your rom is now built. Good luck and I can't wait to see what you guys cook up.

Here is the link to Spocky's Kitchen:

Spocky's LG Multidevice Kitchen 2.2


eXpo Add-on Package:
eXpo Add-on Part 1
expo Add-on Part 2

IQ Add-on Package:
IQ Add-on Part 1
IQ Add-on Part 2

Note 1: To use an add-on download all parts to the same folder and extract Part 1. Part 2 will extract automatically. Once they are extracted move the folders to your kitchen, overriding the existing folders.

Note 2: IQ users - If you are using the add-on package; remove fwua.mbn from Baserom\GW820 and place it back in there when after step 13.

Note 3: If you use the add-on only do steps 1-3, 5, 8, 8d, 8e, 8m, 8n, 8o, 9, and 11-14. If you are porting arrange your folders like in step 7 and also do all of step 8 and step 10.

Note 4: Step 9 needs to be done because there is a process in step 9 other than dumping the xip.bin that allows the ervius visual platformrebuilder to build a rom correctly.
Need Cloud storage? Try dropbox today. Just click on the link below to get started.
Dropbox
--------------------------------------------------------------
Can you see my memories?
 
Dark9781
Old
#2  
Dark9781's Avatar
Senior Member - OP
Thanks Meter 96
Posts: 409
Join Date: Apr 2009
Reserved for future use.
Need Cloud storage? Try dropbox today. Just click on the link below to get started.
Dropbox
--------------------------------------------------------------
Can you see my memories?
 
jug6ernaut
Old
#3  
jug6ernaut's Avatar
Retired Moderator / Recognized Developer
Thanks Meter 398
Posts: 2,400
Join Date: Jun 2006
Location: San Antonio, Tx
Awesome Tutorial Dark, thanks.

-Active-
- Xperia ZL -
- Nexus 7 -

-Retired- - Samsung Note 2
- Samsung Note - Motorola Wingray - Samsung Maguro - Motorola Olympus - HTC Passion - LG Monaco - HTC Raphael - HTC Kaiser - HTC Wizard -
- HP Touchpad - Motorola Xoom -

"You can lead a fool to knowledge, but you can not make them think."
 
trueg
Old
#4  
trueg's Avatar
Senior Member
Thanks Meter 44
Posts: 841
Join Date: Feb 2008
Location: Victoria, BC
I hope questions are OK in this thread (being a sticky and all)

In the process of cooking my own ROM, I figured I would start by dumping and building a stock Telus IQ ROM.

I was able to get it to build and flash, but for some reason none of my mxip*.provxml files were processed. I don't mean user created mxip*.provxml files, I haven't changed anything in the ROM yet.

This is immediately apparent because if mxipupdate_metabase_001.provxml is not processed, themes do not work.

As a test, I renamed it to mxipupdate_metabase_001.xml and loaded it with FdcSoft Taskmanager and themes started working again.

They are all there in \Windows, they just didn't get processed.

Any ideas?

Note that I used Platformrebuilder to process my packages, not Visual Kitchen.
 
Dark9781
Old
#5  
Dark9781's Avatar
Senior Member - OP
Thanks Meter 96
Posts: 409
Join Date: Apr 2009
Quote:
Originally Posted by trueg View Post
I hope questions are OK in this thread (being a sticky and all)

In the process of cooking my own ROM, I figured I would start by dumping and building a stock Telus IQ ROM.

I was able to get it to build and flash, but for some reason none of my mxip*.provxml files were processed. I don't mean user created mxip*.provxml files, I haven't changed anything in the ROM yet.

This is immediately apparent because if mxipupdate_metabase_001.provxml is not processed, themes do not work.

As a test, I renamed it to mxipupdate_metabase_001.xml and loaded it with FdcSoft Taskmanager and themes started working again.

They are all there in \Windows, they just didn't get processed.

Any ideas?

Note that I used Platformrebuilder to process my packages, not Visual Kitchen.
Use the visual kitchen. LG roms are weird. They are built differently than those from HTC.
Need Cloud storage? Try dropbox today. Just click on the link below to get started.
Dropbox
--------------------------------------------------------------
Can you see my memories?
 
trueg
Old
(Last edited by trueg; 5th May 2010 at 11:21 PM.)
#6  
trueg's Avatar
Senior Member
Thanks Meter 44
Posts: 841
Join Date: Feb 2008
Location: Victoria, BC
But isn't Visual Kitchen just a front end for Platformrebuilder? I would prefer not to use Visual Kitchen if at all possible.
 
trueg
Old
#7  
trueg's Avatar
Senior Member
Thanks Meter 44
Posts: 841
Join Date: Feb 2008
Location: Victoria, BC
Hmm, I'm having the same problem when I use Visual Kitchen.
 
jug6ernaut
Old
#8  
jug6ernaut's Avatar
Retired Moderator / Recognized Developer
Thanks Meter 398
Posts: 2,400
Join Date: Jun 2006
Location: San Antonio, Tx
Quote:
Originally Posted by trueg View Post
Hmm, I'm having the same problem when I use Visual Kitchen.
Idk if its the same issue, but im having problem with kitchen handling modules :\

-Active-
- Xperia ZL -
- Nexus 7 -

-Retired- - Samsung Note 2
- Samsung Note - Motorola Wingray - Samsung Maguro - Motorola Olympus - HTC Passion - LG Monaco - HTC Raphael - HTC Kaiser - HTC Wizard -
- HP Touchpad - Motorola Xoom -

"You can lead a fool to knowledge, but you can not make them think."
 
trueg
Old
#9  
trueg's Avatar
Senior Member
Thanks Meter 44
Posts: 841
Join Date: Feb 2008
Location: Victoria, BC
I used WinDiff to compare the dump folder created by Visual Kitchen and the one created by just using Platformrebuilder and they were nearly identical. The Visual Kitchen dump had an empty folder called \build, a file called config.old and somehow a thumbs.db snuck in there. None of these would have made a difference, which explains why the resulting ROM behaves the same.


So, I'm not sure what to look at next.
 
trueg
Old
#10  
trueg's Avatar
Senior Member
Thanks Meter 44
Posts: 841
Join Date: Feb 2008
Location: Victoria, BC
It is something to do with the XIP.

Initially, I wasn't doing anything with the XIP. I just wanted to build a stock ROM, so I dumped the OEM & SYS and then built it back up with the original xip.bin. This mostly worked except for the mxip files not running.

Then I tried using the xip.bin created by Platformrebuilder (found in \temp), but that would cause my IQ to keep rebooting.

Finally, I did all of the steps involved in porting a new XIP, even though I wasn't actually porting any new code, and that worked.


XDA PORTAL POSTS

Pearl Chen to Talk NFC Development at XDA:DevCon 2013

From HTML to LEDs or Android to Arduino, Hardware Hacking is a pastime of many people … more

Avoid Framework Bootloops on Xperias Running Jelly Bean

If you’re a Sony device owner running a stock Android Jelly Bean firmware and … more

Forum Added for the Samsung Galaxy Mega

What do you do when the Galaxy Note line is simply not big enough? You get theSamsung Galaxy Mega. … more

Voice Control Your Phone with Tasker and AutoVoice – XDA Developer TV

XDA Developer TV Producer Kevin set up his phone to respond to … more