Hi XDA-Developers!
First of all: you did a really great job and thanks a lot for ROM 1.1!!
I just want to ask you to explain initobj.txt, files1-dir and files2-dir a little bit more, so i can make my own ROM, and maybe a german ROM.
i'm little bit confused with the format of initobj.txt corresponding to the files in dirs files1 and files2. not every file in the file dirs is listed in initobj.txt. Why? How are these files arranged in the filesystem? ie. how do your scripts know where to put 'vxutil_cl.htp' - it's not in initobj.txt in cfg.
Maybe you could explain it a little bit more....maybe there is already some manual beside 'readme' ???
Thanks a lot.... Jabba
all files in rom can be found in the \windows directory. the initobj.txt files specifies for certain files that copies to other places should be made..
so if a file is not mentioned in initobj.txt, it is only visible in \windows.
also the name of a file in \windows does not nescesarily correspond to the name in wherever it was copied to by initobj
initobj.txt has 2 types of lines ( there are more, but I never looked at them )
Code:
Directory(..dir..) :- Directory(...subdirname...)
to create a subdirectory in 'dir'
Code:
Directory(..dir..) :- File(..filename.. , ...source...)
creates copy of 'source' as 'filename' in directory 'dir'
the reason there are 2 'files' directories, is that there are 2 empty spaces in the rom (1M before the bootsplash, 5M after the bootsplash). I could have made the mkrom script more advanced, and have it automatically figure out how to optimally sqeeze files in either space 1, or space 2. but I didn't , so I'll leave it to the rombuilder to decide how large to make each region.
thanks for your answer!
will it be a true copy from source ? I mean will there be two identical files in the rom then or is it more like a link to the source-file?
another question: is there something in your scripts which is language-dependant ? like the altered welcome.exe ??
in the german rom there are some dirnames different - so i would have to alter the reg-file and the initobj to fit them. Do i have to alter other files as well? Like operator or the welcome.exe ?
Jabba
By the way, would be developers so kind to explain the ways how to extract initobj.txt and default.reg files from the ROM? Or perhaps "original" Qtek ROM files could be published?
I would be of a great help in my ROM-building...
thanks
we based everything on an english qtek rom. if you start with a german rom, you will have to pay attention to differing directory names.
you can get initobj.txt from initobj.dat, by converting the file from unicode
to plain ascii. I usually load it in vi, then do ":%s/^@//g" to strip all NUL characters, and then save it as .txt.
the default.reg you get by converting 'default.fdf' found in the rom, with
Code:
perl fdf2reg.pl default.fdf default.reg
and I wrote this tool (bottom of page) to extract files from a rom image. for most roms you type
Code:
dumprom nk.nbf -d files >nkinfo.txt
to extract the files to the directory 'files' ( which must exist ), and dump lots of info about the rom to nkinfo.txt
Hi, I was trying to make a Korean Rom for Hermes for quite some time... can you share your sorce for making one and how to? This is what I've tried till now and the qusetions I have...
The Question:
1. How do I install and change the default font of the ROM?
2. How to change the dictionary in your language, settings for your language, t9 dictionary for your language, keyboard layout?
Here is the tutorial I've found: (originaly written by a member of XDA-Developers: Tna)
Step 1
(a)Download your language emulator Files from
(b) install the downloaded file
(c)Take the emulator image that you want from the installation folder.
For example, if you have downloaded the images for Korean language look in the folder "C:\Program Files\Windows Mobile 6 SDK\PocketPC\Deviceemulation\0412":
The image for Hermes is: PPC_KOR_GSM_VR.BIN
(d) extract the emulator files in a new folder.
to extract files from the emulation rom follow this direction:
- Download Tadzio's imgfs
- Unzip the tools along with the emulator image(PPC_KOR_GSM_VR.BIN) in any folder.
- Rename the image to A.BIN (to make the next commands easier to type).
- Open a D.O.S. command window and perform these commands:
Code:
> NBSPLIT -emu A.BIN
(it generates two files: A.BIN.EXTRA and A.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BIN
(Now the extracted files are dumped in /Dump directory)
(e) Rename ALL the 4xx files to 412 (e.g. 0412.mui -> 0.409.mui) Apply this to all files and folders (an eyasier way to do that is to search from windows for all *412* files and then rename them)
Step 2
Find your BASE ROM. (e.g. Hermes Black Rom)
Step 3
Download your Kitchen. (e.g. Anichullus Core Professional Kitchen)
Step 4
Dump the BASE ROM (If you use Anichullus Kitchen , follow the manual but Stop BEFORE using Bepe's Package TOOL)
Step 5
Go to DUMP folder (e.g. C:\core\extract\dump) and paste ALL the language files you have
renamed from step 1e. ATTENTION you have to copy and paste ALL files from your
language folder AFTER you have renamed them to 409 . REPLACE duplicate files
Step 6
Continue with kitchen steps . For instance if you were to use Bepe's Package TOOL , go on and build the packages.
Step 7
Edit Initflashes.dat file . Information on how to do that are in every cooking tutorial. In
Intflashes.dat file you will have to translate all the links and directories according to your
language files. CAUTION if you make mistakes in translation your WM6 will be crappy and
programs may not start
->In order to make a good translation check your original rom, or try the WM6 emulator with your language files and check the directory names.
Step 8
Save Initflashes.dat in unicode and remove first two bytes with a hex editor
Step 9
Choose your OEM packages.
about keyboard, you must add with a oem package also:
- dictionary in your language
- settings for your language
- t9 dictionary for your language
- for keyboard layout make this registry mod:
Code:
Registry Editor:
HKCU >> ControlPanel >> Keybd
Create a string "Locale" with "0412" vale. Everything without "Where 0412 is your country value.
Step 10
build your rom according to your kitchen manual
Hi, I have the same dubiousness, where I find the keyboard packages? I'm looking for Keyb Portuguese Brazil(Dictionary, settings, etc)... If anybody know please help me.Thank's.
hi~ nice to meet u. rom cooking is hard to me so i just wondered how to add t9 korean language pack to my english rom. I use my htc t3050 with win mobile 6.5 english rom.
so there are no korean font and no korean locale. how can i do?
I also have blackjack1 and m480(mirage) but that rom is korean rom. if u can help me, please let me know how to find t9 korean language pack and how to install to my english rom. thanks a lot for your text and hope to answer about my text.
if u dont mind, you can answer with korean, that is better for me.. kk
try to find a korean rom with T9 dictionary in your native lang... then dump it using wichever kitchen in the Chef central subforum... dump the rom get the t9 files and replace the ones in the rom of your phone
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
Hello everyone,
I have a problem, to create my rom, when I edit in default.hv some changes, such as the 4 columns, the modes camera .... when installing rom, disappear are changing, as if it had not changed anything.
I do not know if it will be for sometime provxml overwrites something, or is not that.
thank you all!
sorry for my english google translate
you should not edit default.hv.
Make a .rgu (name it for example tweaks put it in the SYS folder) file and set your settings there.
I usualy make a .reg file and put all my settings in there. Then I make that a .cab file (with QuickCab 1.0) and convert it to a package (with Ervius Package Creator v2). Works like a charm
whyen you edit the hive. any RGU or provxml files would over write the settings. thus why they do not stick.
iXiR said:
you should not edit default.hv.
Make a .rgu (name it for example tweaks put it in the SYS folder) file and set your settings there.
I usualy make a .reg file and put all my settings in there. Then I make that a .cab file (with QuickCab 1.0) and convert it to a package (with Ervius Package Creator v2). Works like a charm
Click to expand...
Click to collapse
wow!
run ok!
thx!