Related
hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance
1st- for what model is that rom?
2nd did U try dutty's nbh tool?
3rd nk.nba=os.nb - try prepare_imgfs xyz.nb -nosplit
phsnake said:
1st- for what model is that rom?
2nd did U try dutty's nbh tool?
3rd nk.nba=os.nb - try prepare_imgfs xyz.nb -nosplit
Click to expand...
Click to collapse
this rom is for a himalaya xdaii (tsm 500)
i dont try dutty's nbh tool because i dont found where i download
i need extract *.nb (os.nb,extended rom.nb)files from a rom cooked
when i try extracting that files from nk.nbf,i always got that error: unknows
header format with typho5 util
and i ask you: it is possible extract files from rom already cooked?
the nk.nbf file size it is: 33,6 mb
thank you
PATRICKJ said:
this rom is for a himalaya xdaii (tsm 500)
i dont try dutty's nbh tool because i dont found where i download
i need extract *.nb (os.nb,extended rom.nb)files from a rom cooked
when i try extracting that files from nk.nbf,i always got that error: unknows
header format with typho5 util
and i ask you: it is possible extract files from rom already cooked?
the nk.nbf file size it is: 33,6 mb
thank you
Click to expand...
Click to collapse
excuse me, i forgotten ask you: what tool use for get nbh files??
thank you in advance
http://forum.xda-developers.com/showthread.php?t=296311&highlight=nbh+tool
U forgot to use HTC64_Extended_ROM_Tool.exe it makes nk.nb from nk.nbf
but once more, nk.nb nk.nbf, unless himalaya and universal have absolutely different types of flashing doesnt contain extrom. If i'm not wrong nk.nbf is only and only OS_ROM
and yes, its possible to extract files from OS_ROM as well as from Ext_ROM
no, no, no!
Himalaya roms are decompiled using xda2nbftool.exe
it needs to be supplied with the right password (different for radio, extrom and OS) for the NBF you are decompiling, this will give you a .nba that you can use with mamaich's IMGFStools
to add/delete/decompile.
nbh's, nb's and the typhoon tool have no part in himalaya roms.
sorry Midget i thought that all nbX formats are almost the same ie nbf in Uni contains same things as in Hima. Sorry PatrickJ for misleading U
Midget_1990 said:
no, no, no!
Himalaya roms are decompiled using xda2nbftool.exe
it needs to be supplied with the right password (different for radio, extrom and OS) for the NBF you are decompiling, this will give you a .nba that you can use with mamaich's IMGFStools
to add/delete/decompile.
nbh's, nb's and the typhoon tool have no part in himalaya roms.
Click to expand...
Click to collapse
thank to phsnake and to midget for your interest
then rom wich i want extract the files from it is made for himalaya
attached file txt with it configuration.
it is a rom already cooked , and when i extracting files from nk.nbf occur this
error: unknow header format
can to be that files into nb.nbf are compressed??? because size the rom it is
33,5 mb that has s.o and ext.rom files,opposite i've other rom original: Qtek_S200_220736_2207116_024721_SPA,not cooked, and it size is 77 mb. and with this rom i haven't some problems.
thank to two
Patrickj,
Search for llbasha's-WM5-AKU35pp16a1 rom in the forum. It is built in with the cooking utilities.
Maybe you can refer here and download the previous version of llbasha's rom with the cooking utilities and instructions:
http://forum.xda-developers.com/showthread.php?t=294016
thank you, i have that rom but it want is extract its files
Hi everybody,
I would like to cook Artermis rom for my own Dopod P800W. How can I do this and what about the tools for rom modification? Please suggest me and put the link for download.
Thank you very much.
Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=310076
The steps that I am using
1. Select the ROM that you want that has nbh extenstion
2. use nbhtool to extract the .nbh rom to nb files. Remane the os.nb to RUU_signed.nb
3. use the above link to get the tool to extract the RUU_signed.nb. This tool will extract all files in the rom and put them in folders--->There is a word doc in there that tells you what to do. It is a bit cumbersome but just follow it you will be fine.
4. in Sys folder, remove or add the folder you want--becareful here because there are folder interdpendent to each other so make sure you know what to add or delete.
5. use the Core tool again to build the new os.nb file. Make sure you follow the procedure in the work doc...
6. To build the nbh rom to load back to your device you will need htcrt tools. Copy the new os.nb and other nb files to the htcrt folder--this is what I do. Then run the htcrt program to build the new nbh romfile.
I hope the above will help you. I am building my own rom currently by using some component from B&Bv3.7 and the official wm6 v3.7 as the touchflow ROM. I have been playing with the above tools for sometimes now but still do not know what exactly what is required in each folder yet. Hard but fun...hihi.
attached...nbhtools and htcrt...just to save you sometimes. The core kitchen is in the above link. All programs run in DOS mode, BTW.
Thank you very much, I will try to use it for my rom cooking.
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
i hav cooked my own ROM using the artemis diamondish kitchen
its all fine n workin well
jus can ne1 tell me how to edit the ROM name in device info
i mean if i want to display my own name in ROM name
well don't run the patch when you want to complie the NBs.. open the HTCRT in the RUU folder and run it by yourself and you can find everything you need there..
and becarefull
Can be they are registry value
Enjoy
search for OEMVERSION folder on OEM folder. Then edit the file called mxipupdate_OEMVERSION_100.provxml.
Cheers
when i use HTC tool it shows the name in RUU
but not in the ROM
can u pls specify exact option tht i have to edit..............
and i found tht OEM version folder in OEM but it doesnt contain any proxml file
just one dsm file
what i mean ..
when you finished with build os and you created the OS.nb and you have all nbs you need. open the folder called RUU and in it it should be there another folder called HTCRT which you can find the htcrt.exe .. use it to compile the NBH from the nbs files.. (when using it you can modify the name)
that's all i now .
P.S. i'm not a professional in cokking just i was trying to cook a rom for me once