Related
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
ok, the utilityes you need are:
*** all utilities are ready to download in the end of this post!!! ***
1) nbhtool_trin.rar
2) package_tool.rar
3) nbdumper.rar
4) bepe_kichen_trinity_ita_WM-6.1.rar
Code:
6.1 bepe_kitchen.rar
5) Flash_nbh.rar (included into kitchen!)
6) rgu to xml transform an rgu or a reg file into a provxml file!!
7) dsm patcher to update also the dsms files to respect the rom's os and build version
1) nbtool from dutty is usefull to decompile/recompile nbh , decompil enbh, choose nbh to decompile, you have 1 or more .nb files, windows.nb is that you need, the rom, you should find also:
radio.nb (radio)
first/second_splash.nb (the 2 images shown as splashscreens!!!)
ipl.nb (boot of trinity...)
spl.nb
and other that now I not remember...
................
to recompile the nbh file, just select that you need (os.nb, first.nb second.nb)
for my experiences, try first times only with os.nb, choose the file and compile the nbh files,your rom is ready to be flashed into device...
2) package tools analize the dumped os windows.nb and tell about sys and oem versions, more it creates packages of dumped rom, and insert all files into the 2 system directory "oem" and "sys" with button (menu) "build packages"
3) nbdumper from tadzio, it is the important tool togheter bepe kichen, with it you are able to dump "windows.nb"
put windows.nb into the folder, dos prompt and write:
nbdump windows.nb (then press enter...)
in few minutes you have inside also the directory named: windows.nb.dump, iside you can find all files that will be in rom on your device...
4) now open package tools by bepe, search this directory, and analize, after analizing, click on build packages...
after some time, you in "windows.nb.dump" directory have: sys and oem folders...
this is the real os...
now you neeedd xip directory...
copy windows.nb into the directory named:XIP_extract (that you can find in "bepe_kichen_trinity_ita" tool...
copy it into the directory, rename from windows.nb into "os.nb"
click on "Make_XIP.bat" and then you have "xip" folder...
copy xip folder into "rom" folder in of "bepe_kichen_trinity_ita", copy os.nb too into "rom" folder, so you have rom folder and inside:xip fiìolder and os.nb...
ok...
now, oem and sys folder obtained with package tools, copy them into "bepe_kichen_trinity_ita" tools, and you have:
oem, sys, tools, xip_extract and rom folders, and the exes...
now is ready...
you have to click on "buildos.exe" and the rom will be build, ok, now there is a new folder, "temp", now you have finished, only click on createrom.bat and in few seconds you can find into \temp\ folder a file named os-new.nb, this is the new rom, build .nbh with dutty nbtools, and can flash it on your device!!!
5) to flash put nbh created into folder:Flash_nbh, flash....
next, tools and howto: create extended_roms;create own splashscreens, adding own packages (the packages are additional programs... into I left yet 3/4 packages from mine!!).....
*******************************************************************
I must make all credits also to udK, that discovered with me the right way to kook roms...
and invite all people to make some dotations to him, for the hard work that he made to have a good italian rom to mount on our devices!!!
thanks friend...
*******************************************************************
I think is better to try with udk or lasagna roms to start, they are perfext and logically structured as bepe kichen wants!!!
bye!!!
****************************************************************************************
*
* P.S.: and finally I think that if you decide to use udk rom to make experiments, you have to donate him,
* and if uou want to use lasagna rom to learn to use bepe kichen, also you have to make donations to guybrush.
* they worked hard to translate the rom, you must donete to use theyr roms I think is the only think to do
* to tell them "thanks!!!", really...
*
****************************************************************************************
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 2:
how make own splashscreen!!!
just open an image or create one, with also paint;
make it 240x320 pixels, 240 in width, 320 in height...
save it as bmp, with 24 bits...
open it with nb_image_converter
convert to "nb"
save it as first and second.nb...
now, if you don't have windows.nb use dutty's nbtools to extract from rom, reuse nbtools to compile nbh, add
in os: windows.nb
in "first splash" the file first.nb
in "second splash" the file second.nb...
compile nbh file and flash into ppc, when you finish, you can see you freferred splash screens!!
next:
create a package and/or translate the exe/mui files in your language with resource hacker!!!
try to open an exe, or first a mui files if there is into the package!!
you can see:
icon (you are able to change it , but is not important for us!!)
dialog, you can move the object inside them, rename or translate strings and other...
string table, here you can change, translate in your language tje strings of mui/exe!!!
and other, but for modify translate this basts!!
see later!!! bye!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 3:
for mui:
if you have traslated them, you have also to rename: exaple, if therer is amui xxx_409.mui, in english of couse, and you stranslated it into italian, you hace also to rename it by xxx_409.mui to xxx_410.mui!!!
and for italians mui you can use the ones from tynh wm6 Italian rom!!!
and also initflashfiles.dat must be traslate...:
and also rgu files:example:
string: "programs" must became "programmi"
string: "my pictures" must became "immagini"
etc.etc.
howto: CREATE A PACKAGE!!!
ok, download theese utility:
wince cab manager from here:
http://www.ocpsoftware.com/
(full funcional trial for 15 days!!!)
and my utility: packages creator (a little tools of mine!! )
from here:
-------------------------------------------------------------------------------
UPPED:
(new version... bugs solved... option improved!!!)
now in bilingual ITA/ENG, and with more option to personalyze your new packages!!
new beta with more and more options to create initflashfiles.txt...
flag:"simulate folder names" on wince cab manager and put reg file into package folder you choice...
example: "...\trypackage\windows\batterystatus\batterystatus.exe"
you have to put reg file into "...\trypackage\to-import.reg" ok???
and here the new beta of package creator!!!
Hi all, from a Bennec83's Idea I released this last version that works with cab analyzer, and make packages from cab files automatically...
*******************************Re-reupped 1st good working release!!! 4.1 *********************
-------------------------------------------------------------------------------
ok!!!!
P.S.: if th bepe kichen shows an error during the kook operation, it will be becouse there is another file (duplicate file) yet present in rom, delete it from other subfolder, not in the package just inserted...
next appointmant to create own extended_rom!!! and some triks on registry (modifing rgu files!!!)
see you!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 4 playing with extended rom:
howto: create and use extended roms...
ok, have to download the utility htc_extended_rom_editor
I think is all.... (for now!!!)
your knowledge about roms, its components, how to dump, build, add packages are full... rests to edit rgu and provxml...
but in next days....
bye bey and good experiments!!!
*********************************************************************************
*********************************** ******************************
*********************************** UPDATES ******************************
new version of buildos+packagetools, some imporvements, and context menu on packages to enable/disable them by default!!
new version of buildos, now:
1) xip porting for os ber updating;
2) updater for Rom Creation Date;
3) Updater for Rom version at Boot screen!!!
enjoy!!!
improved some context menus on selected package.....
xip porting for OS version and Rom's Date creations Updater!!
new version of package creator, to have own directory where place shortcuts, and some minor bugs solved
here: and added links in initflashfiles.txt for .htm files for "Help"!!!
P.S.: I need beta testing for my apps, becouse, I go on programming and there are allwais same bung into...
bye!!! ( a big thanks to guybrush and udk for testing and support, but specially to Vibranze for testing package creator!!!)
*********************************************************************************
Traduzione in italiano della guida del Kitchen
Lavori in corso..
ervius said:
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
Click to expand...
Click to collapse
thanx, let's start cook togheter
--reserved for packages--
I only hope that my 3d iwill be usefull to be better, and share togheter a lot of packages for our trinity devices!!
see lather...
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
....
3) This is possible some mirror not rapidshare? (for example www.divshare.com)
Grazie mille.
Viva il P3600.
cicciocant said:
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
Grazie mille.
Viva il P3600.
Click to expand...
Click to collapse
1) infinite greetings to bepe for the beautifull tool...
the kichen is the same, only you have os and xip for trinity (after you extrapolated oem-sys folders and xip!!!)
2) you can use all roms you want, also in other languages, but only if they , after you dumped and analyzed with bepe package tools, and have oem and sys folders (and xip folder...), but if you try with roms that have missed files, you must try to insert them into oem or sys dolder, you, after use bepe package tools must see only "oem" and "sys" folder, nothing else, to know that the rom is really ok..., in other case the rom was built in confused mode or with other utilities, that I consider oldier...
bye!!!
and my final point is also share a lot of packages....
for now I think it's all, but in few days I explain also howto build packages and other....
see you!!
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Guybrush said:
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Click to expand...
Click to collapse
yes... by attentions, use the tools at own risk, and specially use them with "brain"!!!
bye!!
Thanks ervius! you are truly "mythical". I`ll read all with much attention tomorrow, now i`m seat in one park bench to 5 meters from the sea.....
Hi...... morf3o.
added lesson 2 (how to create/modify images and create your splashscreens at ppc boot!!!)
at first post!!
see you later to build our first package!!!
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
cicciocant said:
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
Click to expand...
Click to collapse
so, you have to install also java virtual machine... with this utilities in not necessary...
thanks ciccio but i'd like to continue with bepe's kichen, do you like use it??
ok...
3 files are out, put them into \oem\oemapps\ directory, so you now have only oem and sys directory, then... extract xip etc... etc...
ok!!!
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
cicciocant said:
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
Click to expand...
Click to collapse
I don't have your error, but if finally you have oem and sys folders, then it works well...
but you can try to delete and post if it work...
bye!!
Sorry for my newbie question...
In my understanding all this tools are working with ROM files you already found "somewhere".
What I want to do first is getting a working ROM out of a Trinty device. E.g. I have a german Vodafone device with the Vodafone custom ROM. I simply want to "copy" this ROM on my Harddisk. No changes. I only want to be able to flash it back if I want to, to have the device in the same state it is now.
Which tool do I have to use?
What do I have to do?
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
A question ervius:
we suppose that I succeed to modify/create my first ROM, exists a way in order to test it without flash on my device? A way for being sure that if I flash, i do not burn my trinity....
Thanks........ morf3o.
morf3o said:
exists a way in order to test it
Click to expand...
Click to collapse
The only way is flash your trinity and hope
claros said:
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
Click to expand...
Click to collapse
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
saminegm said:
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
Click to expand...
Click to collapse
Your OS is in part2, first two parts are the XIP partition aka your boot sector.
Ciao
Here is the updated version of my Lg multidevice kitchen. It now supports :
- ks20
- ct810
- gm730
- gm735
- gm750
- gw820
- vs750
::These tools have been made thanks to: MisterJp, CopsFrance, Teoami, Bepe, Ervius, No2Chem, Da_G, Cmonex, Jayautros
This kitchen is now built around ervius visual kitchen for bepe's platform rebuilder. I don't really like write a lot, so I won't explain every option in details, nor will I write a "how to cook roms for dummies", it's already been done in the past, if you know how to search, you'll find very interesting threads on it on this forum.
Kitchen options (use "*" to switch between standard and advanced options)
SELECT DEVICE
::1-KS20 2-Incite ...
Needed for every operation below, don't forget to set it.
DUMP FUNCTIONS
::a- Extract DZ File
Extracts baserom\rom.dz file into baserom folder
::t- Extract BIN ROM File
Extracts baserom\rom.bin file into baserom folder (for vs750)
::b- Extract Flash.bin
Extracts baserom\flash.bin into builtrom\temp, creating directories if they don't exist.
::c- Dump imgfs.bin
Extracts content of builtrom\temp\part_2_imgfs.bin file to temp\dump, allowing you to edit windows files.
::d- Dump bin.bin
Extracts content of builtrom\temp\part_1_rawfs.bin to ROM\XIP
::e- Launch ErviusKitchen
Launches ErviusKitchen, allowing you to modify and generate a new rom
BUILD FUNCTIONS
::f- Build imgfs.bin
Creates new imgfs from temp\dump folder to builtrom\temp\imgfs.bin
::g- Build flash.bin
Generates a new flash.bin into builtrom folder based on builtrom\temp directory and new imgfs.bin
::h- Build rom.dz
Generates a new rom.dz into builtrom folder based on baserom mbns and new flash.bin
::u- Build rom.bin
Generates a new rom.bin into builtrom folder based on baserom mbns and new flash.bin (vs750)
::i- Build flasher
Generates a new rom.exe into builtrom folder based on rom.dz (only available for Incite)
XIP PORT
::j- Launch XipPort
Launches XipPort, allowing you to modify and generate a new xip
::k- Reloc Xip
Relocates xip after you've changed it using XipPort
::l- Use New Xip in Build functions
Allows you to use the Xip built with XipPort when building flash.bin (either from the kitchen or directly from ErviusKitchen)
::m- Restore original Xip in Build Functions
Allows you to use the original Xip when building flash.bin (either from the kitchen or directly from PkgToolsBuildOs)
Kitchen use:
Select the device you want to cook for (1=ks20, 2=incite...)
Take a dz file, and put it into baserom\(your device name) (KS20, incite, gm750...).
run start.bat
execute a, b, c, kitchen options
now copy temp\dump\sys into \sys\(your sys version), and arrange the files so that it looks like the \sys\20755 folder. Do the same with OEM folder (copy it to \OEM\(your device name).
execute d, and arrange xip folders : copy the content of your oemxipkernel into rom\(your device name)\(your ip version) and everything else into rom\shared\(your xip version)
go into tools\xipport. Launch xipport. Click "dump xip.bin"
OPTIONAL : If you want to port xip to another version click "make pkgs". Now replace modules\msxipkernel* and files\msxipkernel* with the ones from the newer xip. Click "undo".
execute Kitchen "k" and when a message tells you so, click "realloc p", "write maps", "build xip_out.bin". 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).
execute Kitchen "l" to use this xip.
execute "e" to launch ervius kitchen. Then select your device, language, ext, rom dpi, rom res, xip build and sys build. Choose the packages you want to include (for your convenience, I included a few packages tweaks and fixes in EXT\(your device name). Eventually click the "create" button.
Optional for Ks20, required for Incite : execute step h to produce a rom.dz file.
Now enjoy your new creation in builtrom\(your device name).
If you want to make a 1st rom easily, or if something went wrong and you want to verify you've done everything correctly, I'm also providing 2 packages (1 for KS20, 1 for Incite) with almost every step already done. They're very similar to the roms I made (xCite2b, KisS20.4). Download the package you want, extract it into your kitchen folder, then :
- Execute step "B" to generate a few files
- Execute step "E" to launch Ervius kitchen
- Optionnaly, try to rebuild xip part with step "K" and "L" (1st rename xipport\out.INCITE.21046 to xipport\out) (I'd suggest doing this only after building a 1st working rom)
- Click Load and select the preset for your device (INCITE_0409_20755 or KS20_409_20755).
- Click create (and for incite users, execute step "H" of the kitchen to produce a rom.dz).
That's it.
If every step was successful, you should have a flash.bin file in builtrom\(your device name) folder and optionnaly a rom.dz.
KS20 : Then just flash with lgmdp your baserom directory and just change flash.bin path from baserom\flash.bin to builtrom\flash.bin.
Incite : either use the usual way (rom.dz replacement) to flash your device or execute step "i" to produce a rom.exe with teoami tools.
Congratulations, you've just flashed your first LG <insert the name of your device here> cooked rom
Before you ask :
- I chose 20755 build because it's proven to be bugfree for Ks20 and Incite (and build is smaller too), if you understood the process, you should be able to build a rom for any wm build.
- Ks20/Incite Packages contain latest available oem parts (spanish 10e unbranded for the Ks20, 10x for the incite). (Incite is the clean version, if you want the full stock oem, just dump imgfs.bin)
- Base kitchen Ext folder contains everything to build a bugfree 20755 rom.
- If you want to make the same thing for wm6.5, just download a wm6.5 build.xip somewhere and replace the files in the kitchen.
- 20755 folder is not in the basic kitchen anymore, but I've made another archive that you can download if you need it.
- as for vs750 roms, you need to use bin (decrypted) files (not wdb). Don't forget to replace step "a" with "t" and step "h" with "u" in the tutorial above. You will need the decrypted roms available in the bottom of this post.
I'm just asking you 1 thing : if you make changes to this kitchen to improve it, please, share what you've done (and of course, if you're using it, you can also buy me a beer)
Kitchen history:
v2.3 [2011-10-13] - Added (partial: can't decrypt roms for now) support for VS750 roms.
v2.2a [2010-05-10] - Added support for GM735 WM6.5 roms, corrected a bug in GM730 rom creation.
v2.2 [2010-04-22] - Added support for many devices, updated almost every tool to latest version, build process is faster than before
v2.0 [2009-07-09] - Changed to ervius visual kitchen for bepe's platform rebuilder, multidevice support (ks20, Incite). New tools, rewrote almost everything.
v1.1 [2008-08-25] - Added Xip Port and Tools sections
v1.0 [2008-07-15] - Initial revision
Download Links:
Vogica v2.3, the LG multidevice Kitchen
Incite addon / Ks20 addon
Sys 20755
VS750 v5 decrypted rom
VS750 v7 decrypted rom
Old releases :
Vogica v2.2a, the LG multidevice Kitchen
Vogica v2.0, the LG multidevice Kitchen
Vogica v1.1, the KS20 Kitchen
Useful Links:
LG KS20 custom rom KisS20 (UC, WM6.1)
LG Incite custom rom xCite (UC, WM6.1/6.5)
Thank you MisterJP and you. You made some very good work for the coocking of the KS20.
Thanks to both.
nice tool !
but
Code:
cls
set choice=
cd BuiltROM\temp
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 imgfs.bin ..\..\BaseROM\flash.bin
cd ..
pause
GOTO :start
:9
cls
set choice=
cd BuiltROM\temp
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 imgfs.bin ..\..\BaseROM\flash.bin
:8
the new xip.bin don't Insert !!!
it shoud be
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 xip.bin -2 imgfs.bin ..\..\BaseROM\flash.bin in :9 ?
good....a nice start........and thanks
Thanks for your great job! Hoping that KS20 will have its Cook Rom & WM6.1 at last!
waiting for wm6.1 on my lovely ks20
is this the most actual thread to the ROM cooking stuff
Would like to use french 1f ROM but cook German language into it
Greet`s Erich
I have made a flash.bin with language in german for the ROM HKG 10a, which is in normally in english. So, the HKG 10a is newer than the French 10f. Why to use an older ROM? Find the flash.bin here:
http://rapidshare.com/files/131832687/flash.zip.html
Thank you itapower
many thanx!
Is there something I have to take care of?
Or can I flash it like I flashed the ROM from 10b to 10e?
Did you just change the language or also other stuff?
Is this ROM running without troubles?
Is it locked or branded?
I have unlocked KS20 with vodafone branding right now,...
Greet`s erich
changing language of ROM
don`t know why nobody from the pros is responding
Most of my questions I figured out yesterday - but I am very curious how to change the language of a ROM be myselfe
This I couldn`t figure out
Hope someone can tell me which of the 10 .mbn Files I have to change or is the language in the .bin
Greet`s Erich
Basically, you need to extract the flash.bin, replace *.409* folders with *.407* versions (407 is for germany) that you may find in another rom. That's not a trivial operation, although the kitchen helps a lot. There are tutorials here that explain this with more details (search for "translate" ou "localize" rom).
more questions
Hello spocky12!
I got really interested in cooking ROMS while playing around with the kitchen
But I don`t get the difference between "flash.bin" and "imgfs.bin"
What is included in which .bin
When the *.409* folders are replaced with *.407* and the ROM is cooked
is it enough to flash the "flash.bin" to the KS20 without the "imgfs.bin"
Another question is the Registry tweaking - which I wanna do.
You have a folder in the kitchen "Packages\OEM_Registry Tweaks Pack" there are 3 files.
Is the name random or how is the convention?
The .dsm file is Hex - what is it for?
Is it enough to edit the .rgu file?
When cooking the ROM does it include the changes I perform in the .rgu file?
Hope you help me understanding this a bit better
Greet`s Erich
@eriche : follow step by step the kitchen tutorial, you should see clearer.
- Imgfs.bin is a file contained inside flash.bin (as xip.bin and a few other).
- The files you need to modify are inside imgfs.bin
So what you need to do is:
1- extract dz to obtain *.mbn and flash.bin
2- extract flash.bin to obtain imgfs.bin, xip.bin...
3- extract imgfs.bin to obtain WM files
4- change files
5- rebuild imgfs.bin
6- rebuilt flash.bin
7- flash new flash.bin + original mbn files.
For Registry tweaks, you can directly change rgu file in OEM_Registry Tweaks Pack. When you rebuild you imgfs, it will be automatically added to system registry so you dont need to create a new package.
7- flash new flash.bin + original mbn files.
Click to expand...
Click to collapse
Isn`t it possible to flash only the .bin file
With original .mbn files you mean the one from the Base Image where I change the language or the Image where the Language is included
Greet`s Erich
You should be able to flash only flash.bin but I can assure that you won't crash your phone.
To flash, you only need partition.mbn and flash.bin but if partition.mbn differs from your actual ks20 partition (that is, if your actual rom mbn don't come from the same dz than your cooked rom), there's a chance that flash.bin overlaps something else on you phone. So it's secure only if you've already flashed the same mbn and the same partition.mbn before. If not, I can't say, maybe it is, but not for sure.
So as I wrote on first post, to flash, select baserom as rom folder. Each mbn line will automatically populate and the just change the path to flash.bin to your newly built flash.bin (which is in builtrom if you use the kitchen).
language cooking not easy - but I don`t wanna give up!
oh god - it`s not that easy
I don`t know in which step I have to replace the Language folders
With HK-ROM (newer ROM) I did step a-e = 1-8
With GER-ROM (language ROM) I also did a-e = 1-8
but then I have 77 ".0407" and 59 ".409" folders
so why is this? Different languages have different folder amount?
Or should I change the language after step "d" ??
looking forward to bring light inside
EDIT:
I used "PKGToolsBuildOS" (step e) to change the language.
But this tool brings following message
Not copied: OEMBT_Lang_0407! No \SYS\ folder corrisponding...
Not copied: OEMVVS_Lang_0407! No \SYS\ folder corrisponding...
Click to expand...
Click to collapse
Don`t know if this is critically?
I prefere to do things by my own - because I don`t trust tools that crash that often *gg*
GreeT`s
I've never succeded in using PKGToolsBuildOS to change rom language. I do it manually.
It seems that you're counting also subdirectories in your 040x folder count (ie, there's a Base_Lang_0409 folder and inside lies a commctrl.dll.0409.mui. Of course, you don't need to count it as changing Base_Lang_0409 folder will also replace its subdirectories.). Sys folder should contain approximately 30 040x first level folders. Between roms, it there may be 1 or 2 folders less or more (depending on the availability of windows_live and things like that.)
The only thing important is that in the end, every folder that was 0409 is now replaced by 0407 folder.
I did it
Jea - today I did it
I flashed HongKong 10a ROM with German language to my KS20.
I have now
ROM: v10a
Bootloader: v10a
Modem Firmware: V10e
ROM date: 2008-04-29
I don`t understand why the Modem Version is still the "old" one
How can I get the newest modem Firmware from the HongKong ROM?
ROM-Date seems also the "German 10e" date.
Who can bring light inside :I)
Greet`s erich
Informations about version are stored in registry (in HKEY_LOCAL_MACHINE\Software\LGE\VersionInfo).
As for modem version, it's in mbn files and not in flash.bin.
So does it mean I have the "modem Version" from the HongKong ROM but only it shows the "old" one
Or do I have to change a .mbn file to change Modem Version?
Whitch .mbn file is the one holding the Modem crap?
I know from my friend who owns a HTC Diamond that a new modem version can save battery and bring faster or more stable access,...
Greet`s erich
Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San
I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative
I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers
wooooooow thanks a lot buddy finally we have it also !!!
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!
You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
kitchen tools attached in the first post.
enjoy
dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers
thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!
The next post is up
cheers
dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....
trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?
well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool
good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck
Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
------------------------------------------------------------------------------------------------------------------------------------
[14-12-09]
I guess most of us p835 users have to use our own effort to build the rom for this phone.
Here i will give you some guide how I did building the ROM. Hopefully we can gather more intelligence to make a nicer ROM for this phone.
first off, I will explain how to properly extract xip/sys from the original ROM. With these only you can modify it's system.
Tools needed: p835abisplit2.exe, osnbtool.exe
1. rename the original ROM you downloaded from asus site. Rename to G5.exe. run command: "p835abisplit2 g5.exe". You will now get a file FLASH.BIN.
2. Now we need to work with FLASH.BIN. Using OSNBTOOL, put in command "osnbtool -sp flash.bin", you will get something just like below:
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
Sector size : 0x00000800
Extra data bytes : 0x00000008
OS IMAGE found.
Partitions infomation:
**************************************
Part-0 type: BOOT SECTION image
Part-1 type: XIP RAM Image
Part-2 type: IMGFS file system
Part-3 type: legit DOS partition
**************************************
Found BIN_FILE structure in source file.
Records: 0x0000036D RecordsSize: 0x06E10328
StartAddr: 0x01030200 ---------------->we need this address when we repack flash.bin. Check if yours is the same with this?
flash.bin.Header written.
3. command: "osnbtool -sp flash.bin.BIN.NB0"
4. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin" --> you'll get imgfs.bin
5. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 1 xip.bin" --> you'll get xip.bin
6. command: "imgfstodump imgfs.bin" --> with this, you'll get a "imgfs" folder. You'll need to make it into a easy to use package. rename the folder to dump.
7. command: "packagebuilder dump" --> you will see inside dump folder, you have all files packed into different folders. You wont be able to see a single file in dump folder. if you do, probably packagebuilder unable to recognize them or something wrong with the files(i'm not sure what to do then). The most important thing in dump folder are the folders with letters starting with OEMxxxx and .ROM, .VM. These few folders should be retained in the new system. Others are all replaced with new system.
assume you are able to modify everything without question, you are now in the situation where you want to repack a ROM. We will need these files in the same folder: FLASH.BIN.HEADER, flash.bin.BIN.NB0.OS.NB, IMGFS.BIN.
1. You will need to repack imgfs first. using "imgfsfromdump imgfs.bin imgfs-new.bin", you get the new imgfs-new.bin.
2. assuming you already modified xip.bin, it should be in name xip-new.bin. Using "osnbtool -c flash.bin.BIN.NB0.OS.NB 1 xip-new.bin"
3. "osnbtool -c flash.bin.BIN.NB0.OS.NB.NEW 2 imgfs-new.bin", repacking imgfs
4. "osnbtool -extra flash.bin.BIN.NB0.OS.NB.NEW.NEW"
5. "osnbtool -2bin flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA 0x01030200 -cutheader", remember when we first unpack FLASH.BIN? There's a starting address which we must use here.
6. "copy/b/y flash.bin.Header+flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA.BIN os-new.nb0"
7. "p835abisplit2 /B G5.EXE" ---> you must have the original ROM G5.exe. Output is a file named "out.exe". This is a USB flash file. For me, I'd prefer a card flashing ABI file. Which I felt safer. For generating ABI file, you will need to download a flashable ABI file, rename to G5.abi and run this command "p835abisplit2 /B G5.ABI". You will get "OUT.ABI". Rename to G5_ALL_WWE.ABI to flash with an SD card.
Btw, all these are not my original works, credits to DA_G for his ROMs and guides, BEPE and others for their great tools, zhaochengw: most of the guides above is from him.
--------------------------------------------------------------------------------------------------
[16-12-09]
SYS modification:
to upgrade a sys, all you need from original ROM is .ROM, .VM and all OEMxxxxx folders. (that's all i know of). All other folders are to be deleted and replaced with folders from new builds. After you work out a complete SYS, use G'reloc to relocate address. I've tried using WMreloc, but everytime i tried doesnt boot. I'm not sure what caused the problem but at least G'reloc worked. There might be some hiccups when using G'reloc, you'll have to google abit on that. If you encountered a problem saying that there's not enough memory on slot0, try remove some of the removable directories such as office or onenote.
Once you successfully relocated, you will have to use BuildOS to pack it back. You might encounter problems like duplicated files, just delete the one not from OEM folders. after you're done, copy the DUMP folder from TEMP directory and use imgfsfromdump(step1 from second part above).
--------------------------------------------------------------------------------------------------
[19-12-09]
I'm not going to cover xip.bin porting, but i'll mention here that you will need to use xipport to manually port xip for this rom. I've tried some kitchen tools but none working. It's the same for sys porting too, you have to manually replace the files and/or change REG. After which you'll use BUILDOS to build it. Other than that, you'll need an OEM sys/xip. I'ved used D_GA's 28002 and found that his package works pretty well. You can find it here.
http://forum.xda-developers.com/showthread.php?t=544445
I'll upload some related tools together so you'll wont have to look everywhere. You can find the upload together with the ROM downloads area.
regards.
blue.
Nice working!
Thx for blue's hard working on this poor handset.
wish ASUS can fix bugs on drivers and also hope guys like u can countinue Cooking better roms!
Thanks Guy! You're the best!
Call Key,Trackball and Volume Key cannot use
blue00mountain said:
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
Click to expand...
Click to collapse
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Sorry, How to Flash the Rom Use ABI File?
Blade0rz said:
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Click to expand...
Click to collapse
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
blue00mountain said:
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
Click to expand...
Click to collapse
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Blade0rz said:
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Click to expand...
Click to collapse
ok, now the browser problem and garmin problem solved. although not really sure what i did that made it worked. Now i'm facing another problem, asus utilities, i.e. autorotate can only work once, and then it stoped working the next time ie starts. Autocleaner does not work at all. Any ideas?
Is there anyone testing my rom anyway?
regards,
B
I have test your ROM.It is very good.Sometimes any programs can be down.
Hi Blue00mountain
Thanks for your hard work, downloading.... hunger for P835 rom,
Read form other thread and noted that WM6.5.3 build 28002 was not as stable and fast as 28003 or later, would you consider to move on to newer version, thanks so much in advance.
blue00mountain said:
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
regards.
blue.
Click to expand...
Click to collapse
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
leofong2022 said:
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
Click to expand...
Click to collapse
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Thx blue!
anyway,the solution of unpack and repack P835 ROM may have another way:
follow steps are from hdubli,and hope can help everyone to Cooking ROMs!
---------------------------------------------
@ECHO off
ECHO Preparation
del flash.bin
del os-new.nb0
del flash.bin.bin.nb0.bin
del G5_ALL_WWE.abi
pause
TOOLS\p835abisplit2 g5.abi
ren os.nb0 flash.bin
TOOLS\osnbtool -sp flash.bin
TOOLS\nbsplit -data 2048 -extra 8 flash.bin.bin.nb0
copy flash.bin.bin.nb0.payload ROM\flash.bin.bin.nb0.payload
pause
ECHO Building OS
pause
TOOLS\BuildOS.exe
ECHO Realocating Modules
pause
TOOLS\WMReloc -gtemp\dump -llog.txt
ECHO Next: Build the rom...
pause
copy imgfs.bin temp\imgfs.bin
cd temp
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
cd..
copy temp\imgfs-new.bin
pause
TOOLS\insert -i imgfs-new.bin -o flash.bin.bin.nb0.payload -d 0x00460000 -s 0x5fdfff0
pause
TOOLS\insert -i 21812.bin -o flash.bin.bin.nb0.payload -d 0x00180000
pause
TOOLS\nbmerge -data 2048 -extra 8 flash.bin.bin.nb0 -conservative
pause
TOOLS\osnbtool -2bin flash.bin.bin.nb0 0x1030200 -cutheader
pause
copy /b/y flash.bin.header+flash.bin.bin.nb0.bin os-new.nb0
pause
TOOLS\cvrtbin os-new.nb0
ECHO Check the Out Put
pause
TOOLS\p835abisplit2 /b g5.abi
ren out.abi G5_ALL_WWE.abi
pause
del flash.bin.bin.nb0
del flash.bin.bin.nb0.payload
del flash.bin.header
del flash.bin.bin.nb0.extra
del imgfs-new.bin
pause
---------------------------------
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
lizard999 said:
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
Click to expand...
Click to collapse
i found there's some problems when u use the imgfsfromdump tool to make imgfs-new.bin
imgfsfromdump can't proceed the SYS folder,it can only deal with original "DUMP" folder
that means,when u dumped out the "DUMP" folder and use pkgtool(or packagebuilder) proceed it into models(SYS、OEM...ETC),u have to use BuildOS.exe rebuild all the files in SYS OEM.the result of BuildOS's rebuild just like the original "DUMP" folder.then u can use imgfsfromdump to make a imgfs-new.bin
Sorry about my poor English...
well,i still try to show u the way i repack imgfs.bin wihtout change anything.
1st, get the imgfs.bin
2nd,use imgfstodump and get the "dump" folder
3rd,use imgfsfromdmp directly,i get the imgfs-new.bin
blue00mountain said:
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Click to expand...
Click to collapse
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
leofong2022 said:
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
Click to expand...
Click to collapse
i don't think the XIP size should be 3200kb,anyway,in the Traditional Chinese version Rom,the size of XIP is more than 4200kb.
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
blue00mountain said:
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
Click to expand...
Click to collapse
Since I saw the p835abisplit2 creator starkwong said that (若要修改 XIP，請確保重新嵌入 nb0 前的 XIP 大小是跟原來的相同，否則刷機後會開機失敗)
-> if modifying XIP, please ensure the re-embedding nb0 XIP size is same as original XIP size, otherwise it may cause turn-on (mobile) failure after flashing.
If it is ok, that's great
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.
Reserved for future use.
Awesome Tutorial Dark, thanks.
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.
trueg said:
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.
Click to expand...
Click to collapse
Use the visual kitchen. LG roms are weird. They are built differently than those from HTC.
But isn't Visual Kitchen just a front end for Platformrebuilder? I would prefer not to use Visual Kitchen if at all possible.
Hmm, I'm having the same problem when I use Visual Kitchen.
trueg said:
Hmm, I'm having the same problem when I use Visual Kitchen.
Click to expand...
Click to collapse
Idk if its the same issue, but im having problem with kitchen handling modules :\
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.
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.
Just wanted to post an update..
The issue with my provxmls not running was due to redundant DSM pointers. When Platformrebuilder creates the dump folder, it mergers all of the DSM files from the XIP & IMGFS into a single file in IMGFS. When I then used the stock xip.bin, it created redundant pointers since the same files were being referenced by the XIP and IMGFS. To correct the issue, I had to dump the XIP, delete the DSM files and then build a new xip.bin. Now all is well.
trueg said:
Just wanted to post an update..
The issue with my provxmls not running was due to redundant DSM pointers. When Platformrebuilder creates the dump folder, it mergers all of the DSM files from the XIP & IMGFS into a single file in IMGFS. When I then used the stock xip.bin, it created redundant pointers since the same files were being referenced by the XIP and IMGFS. To correct the issue, I had to dump the XIP, delete the DSM files and then build a new xip.bin. Now all is well.
Click to expand...
Click to collapse
Awesome, glad you got it worked out. Now u need to help me get Sense2.5 work on our expos xD.
This Device have only one Cookers??
And You do not want more?
Cheers
Nokser said:
This Device have only one Cookers??
And You do not want more?
Cheers
Click to expand...
Click to collapse
Dark's ROMs don't leave much to be desired.
I have a private build running (I know, I should share, but I cooked in stuff I "shouldn't" have .. another one will be forthcoming) and there's definitely other people over on lg-expo.com cooking.
I'd expect we'll see more in the coming weeks. Most of the (vocal) community is fairly new to cooking; and because of a number of factors, fairly small compared to others (lg-expo.com only has about 525 registered members at the time of this posting)
Understand.... thanks
I have been working on my own ROM since a day or two after I received my GW825. It's working very well, but it will probably be a little while before I post anything.
trueg said:
I have been working on my own ROM since a day or two after I received my GW825. It's working very well, but it will probably be a little while before I post anything.
Click to expand...
Click to collapse
same here, ive been working on getting sense to work on my expo...its being a b%$# lol.
At one point I started porting pretty much all of the HD2 code over to my IQ. Most of it worked fine. I got bored and switched back to just LG code before I made it to SenseUI. What problems are you having?
HTC stuff not linking liking my expo lol. s2.5 can get up and working minus 2 things active desktop(pictures, weather animations work) and my locations, both things i can live without. BUT its causing my internet to not be able to connect. Ital work on first boot then after that it wont. Then if i plug my phone into my computer and it establishes a async connection after that it can connect to internet fine....
very odd lol.
xdapants said:
Dark's ROMs don't leave much to be desired.
Click to expand...
Click to collapse
I would just like to clear up something about this statement. My roms are bare bones. I leave practically nothing in them so people can customize them the way they want. Some people don't like that. Apparently xdapants is one of them. Also those that want to use HTC software such as their UI, I have found that there is a lot of HTC stuff that isn't friendly with LG. There are cabs out there for those that want HTC's UI, but not all features may work. Finally, I posted the files for everything I removed so people can make cabs for any of the removed software.