Develop Bugs

Flashing with Microsoft's official development images

It may be a dumb question...
I was wondering if it was possible to flash my Artemis with one of the official development image ("PPC_FRA_GSM_VR.BIN" available at the Microsoft website) that is aimed for the Device Emulator environment under Windows.
Otherwise, is it possible to cook a ROM for the Artemis beginning with such an image ?
Thank you!

those images ae missing all device specific drivers, like the GPS driver, the GSM radio driver etc. You my be able to re-use some of the very generic Windows CE components but it's not really worth the hassle.

Romano2K said:
It may be a dumb question...
I was wondering if it was possible to flash my Artemis with one of the official development image ("PPC_FRA_GSM_VR.BIN" available at the Microsoft website) that is aimed for the Device Emulator environment under Windows.
Otherwise, is it possible to cook a ROM for the Artemis beginning with such an image ?
Thank you!
Click to expand...
Click to collapse
Dump it with Tazio tool
Download here :
http://forum.xda-developers.com/attachment.php?attachmentid=35624&d=1174268295
Code :
Code:
> NBSPLIT -emu PPC_FRA_GSM_VR.BIN
(it generates two files: PPC_FRA_GSM_VR.BIN.EXTRA and PPC_FRA_GSM_VR.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BIN
Now u have modules and Files *.040C.mui Copy all files and modules in this Rom use for your Rom cooker for creat FRE Rom..
Good luck for u

Never cooked a ROM yet... I think I won't begin this way Thank you anyway. May be useful to others.

BETA: Extended Hermes Kitchen for WM6.1

New extended Kitchen for Hermes
HERMES_DEV_v2.1_Build_19199.rar
Related:
Extended Kitchen for Trinity
Extended Kitchen for Artemis
Extended Kitchen for Herald
Thanks to misar, FreePK for helping with this new set of tools!
About the Kitchen
Hermes base: TMO UK 3.60.110
OS base: VF Kaiser UK 3.08.161.0 (Build 19199)
OEM Apps removed, but you need to clean up the OEMDrivers package
I did not do any changes to the OS, because it should be a clean base Kitchen for all of you
Full XIP editing supported by the Kitchen
New tool to merge all dsm files to one big file and delete all rgu's
I think the OEM package to SYS problem should be solved... but did not try it yet
How to use it
Requires Microsoft Visual C++ 2008 Redistributable Package
OEM and SYS can be used as known
The content of ROM\XIP will be used to create a new XIP section for the OS
You don’t have to worry about relocating modules... add/remove whatever you like and the new tools will take care of relocating modules or freeing RAM
.VM and .ROM is updated automatically
Actually this Kitchen runs in auto mode, which means you only need to run BuildNB.bat to create the ROM. You can change that by editing the bat files; made it this way, because I don’t use the options in BuildOS.exe
I consider this a perfect port of the new build to this device
Replaced all XIP SYS packages (I did not just changed coredll.dll to get the new build number)
There were also boot.rgu changes my MS, those have been added too
SYS is completely untouched
Read this for download:
All donations are very welcome!
I need to buy a new device, because this time my Trinity is gone forever and I cannot use my girlfriends Artemis without being killed (by mistake I deleted all contacts last time I used it for testing... she was not very happy about that )
When you are getting money for the ROMs you cook using my kitchen, I would really appreciate a donation.
I'm not talking about 50% of you incomes, but one small donation would be fair I think.
To download the Kitchen click at "All donations are very welcome"
!!! This was only meant for ppl never donated for these tools and expecting donations for ROM's created using my Kitchen !!!
Thanks to all those who have donated already!​
Additional things
RBS_Kit.rar (RealBigStorage)
For making it clean delete "OEM\OEMDrivers\OEM_FLASHDRV.DLL"
Happy cooking!

good
thank you very much

Well done!

Code:
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\caio>cd C:\HERMES_DEV
C:\HERMES_DEV>BuildNB.bat
Creating 'dump' folder...
Impossibile eseguire il programma specificato.
Done!
BUILDXIP 0.53 Copyright (c) 2007-2008 bepe 29 Dec 2007
ERROR! (errorlevel: -1073740777)
Premere un tasto per continuare . . .
C:\HERMES_DEV\ROM>
instruction thanks

study!
thank u
第一页的位置，免费刊登广告。

Finally an easy way to edit XIP. And I think it also work for WM6, is it?
Thanks Bepe!

Welcome back Bepe.
Do you release also this kitchen for trinity?

bepe said:
What's new?
- Full XIP editing
- New tool to merge all dsm files to one big file and delete all rgu's
- I think the OEM package to SYS problem should be solved... but did not try it yet
How to use it:
- OEM and SYS can be used as known
- The content of ROM\XIP will be used to create a new XIP section for the OS, you dont have to worry about relocating modules... add/remove whatever you like and the new tools will take care of relocating modules or freeing RAM
This tools are really beta, cos of University I don’t have enough time to finish them right now... but they can be used for Hermes without any problems.
Donations are always welcome! Cooks are not the best donators since it is easy possible to count the cooks donated for my RK on one hand... should I name them? I think no... but don’t worry I'm not making this just for money, also for fun
Base ROM: Hermes_TMO_UK_3.60.110
SYS: Full WM6.1 (I did no changes to it, so it is original)
OEM: OEMDrivers is old; all the other packages should be from WM6.1
ROM\XIP: Replaced MSXIPKernel, MSXIPKernelLTK by WM6.1 files (no changes to both packages)
WM6.1 build: 100% real 19716
This kitchen should be an example ... to create the temp\os-new.nb just run BuildNB.bat
It’s late... perhaps I have time to write more tomorrow... happy cooking!
http://rapidshare.com/files/87679940/HERMES_DEV.rar
Click to expand...
Click to collapse
Thanks bepe as always - your a 100% contributor to the forum

thank you bepe!

hi,bepe,new four tool can't work,it shows Application can not be executed, because configuration is not valid. Problem can be resolved reinstalling application.

Looks like I don't know wtf I am doing. Running the BuildNB.bat I get the error:
"Creating 'dump' folder...
The application has failed to start because its side-by-side configuration is in
correct. Please see the application event log for more detail." no idea what that means.

I get a similar issue. When I run BuildNB, it tries to launch BuildOS, but it says :
Code:
Creating 'dump' folder...
The system cannot execute the specified program.
Done!
If I copy across a different version of BuildOS, it will run, however it errors with "Access to the path '723fb954-d931-4348-b672-82a188e587b5.dsm is denied" when creating the registry... Looking further into it now...

http://www.microsoft.com/downloads/...34-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en
sorry, forgot to mention that you need to install this for the case that you don't have Visual Studio 2008 installed

bepe said:
http://www.microsoft.com/downloads/...34-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en
sorry, forgot to mention that you need to install this for the case that you don't have Visual Studio 2008 installed
Click to expand...
Click to collapse
Ah ha! That would also explain why insert.exe was failing... After installing the VC++ runtimes, it all seems to be doing what it is supposed to... Let the playing begin

Bepe,thanks for your great tools,can you tell me how to use buildxip.exe to build atom life XIP?Is it possible?thanks in advance!

i just made a rom using your kitchen
unfortunately, after i corrected the date and time,
it suddenly showed up: This concludes the beta test of this software release. Thank you very much for your time.... blahblahblah
that means i have to flash another rom again

I get the same... a message to state that the beta has expired, then the phone logs off the mobile network, and that's about it. Can't do anything else with it.

I think that in BuildNB.bat tyhere is this wrong:
Code:
cd ..\FLASH_TRINITY
DROP_OS.bat ..\TRINITY_GER\temp\OS-new.nb

cicciocant said:
I think that in BuildNB.bat tyhere is this wrong:
Code:
cd ..\FLASH_TRINITY
DROP_OS.bat ..\TRINITY_GER\temp\OS-new.nb
Click to expand...
Click to collapse
You can ignore this and just pick up the new OS-new.nb in the TEMP directory. There's no real point however, as the beta has expired and is not usable.

I've just got the AKU1 rom and did not really try it, however this is meant as an example for the new Kitchen plug ins.
This is the same build the PV roms were made of and since I did not change the new OS the time bomb is still active.
Anyway, I'll remove the time bomb this evening when I find time, so that all ppl can use this RK to build AKU1 rom's.

[2011Oct13] LG Kitchen 2.3

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

Japanese WM6.1 ROM for X01HT

being tired of seeing too many protected roms floating around, i decided to make japanese wm6.1 cooking base files myself. it took me awhile, but i finally figured it out. i would like to share my experience of making a japanese wm6.1 rom for hermes here.
actually, it is not that difficult, and all i did was just assembling pieces from different official roms. so, i would NEVER call it my OWN rom or anything because every part of the original roms was developed by MS and HTC. (sorry, but i really think it's too funny many people, who know slightly better than others, put their names in the ver info, apply procection or whatever to their roms, and say "this is my own rom!" for something made out of other roms originally built by MS and HTC.... is this place for dev info sharing for similar-minded guys? donations?? c'mon!)
i will explain about the details step by step later. here's a rough tutorial.
things you need:
[tools]
Pandora Kitchen (thanks to mattk_r) for cooking and burning
http://forum.xda-developers.com/showpost.php?p=1364931&postcount=1
or
i prefer bepe's Extended Hermes Kitchen for WM6.1
http://rapidshare.com/files/88850555/HERMES_DEV_v2.1_Build_19199.rar
G'Reloc.exe as usual
http://forum.xda-developers.com/showpost.php?p=1524413&postcount=1
[roms]
bepe's kitchen (thanks to him!) for simple and working oem folder and xip (OEMXIPKernel only)
http://forum.xda-developers.com/showpost.php?p=1177762&postcount=1
x04ht (japanese softbank diamond) rom for most of the sys part
http://forum.xda-developers.com/showpost.php?p=2998164&postcount=1
htc hermes official wm6.0 rom simply for os.nb as a template
http://rapidshare.com/files/46467733/HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108.exe
htc kaiser (or opal) official wm6.1 rom for dpi_96 files
http://rapidshare.com/files/157469239/Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.rar
http://forum.xda-developers.com/showthread.php?t=441689
s11ht (japanese emobile kaiser) official rom for 0411_dpi_96
ftp://htc-jp.com/EM/S11HT_firm_V2_6_881_0_JPN.exe
[basic strategy]
[oem]
1) bepe's oem folder is very simple and clean for cooking (some modifications are necessary in *.rgu files, tho)
2) replace OEM.cer by the one from x04ht rom
[rom]
1) basically, you can take OEMXIPKernel from bepe's xip or from htc hermes official wm6.0 rom
2) MSXIPKernel and MSXIPKernelLTK are from x04ht rom or whatever you want
3) use os.nb from htc hermes official wm6.0 rom just as a template
[sys] (tricky)
1) the base is opal sys. but remove all the language specific (0409) folders.
2) take the language specific but non-vga folders from x04ht, x05ht or whatever wm6.1 japanese rom (0411 folders not including dpi_192)
3) take language specific qvga folders (the 0411_DPI_96 folders) from s11ht
4) take .vm folder, packages.* in metadata folder, and service.exe in os folder, shell32.exe and shellres.dll in shell folder from hermes official or bepe's sys. (irda is not included in opal rom. take them from bepe's rom if you wanna use irda.)
[points]
1) don't forget to copy WinCENLS_Lang_0411 into your sys. otherwise, the device does not boot since WinCENLS_Lang_0411 is not included in xip.
2) if you take sys from any newer versions, taskmgr does not work since it is not signed by softbank. remove mxipupdate_taskmgr_shell_1.provxml in base_lang_0411. it's useless, anyway.
3) this method does not create shotcuts in windows\appbuttons. you need create those shortcuts with japanese names yourself to make the buttons work properly. (does anyone know how these shortcuts are automatically created?)
4) os ver info is stored in the original files. (read here for details: http://forum.xda-developers.com/showpost.php?p=1172925&postcount=1) you can change the ver info as you want, but i REALLY hate to see ver info with someone's name or some personally customized splash screeens. so, the ver info does not reflect the actual ver you take all the files from.
5) i don't think this works only with hermes but with any other qvga devices (you have to change xip part.) hope many other qvga device users can make (assemple?) their own japanese wm6.1 roms freely.
question:
i made a shortcut file with 14 japanese (2 byte) letters and put it in the windows directory, but the hermes did not boot. i changed the name to 13 japanese letters, and then it booted... are there any filename restrictions for east asian language files??

reserved for step-by-step guide

here is the japanese wm6.1 cooking base files for hermes
sys: 21014
xip: 21014
oem: basically based on htc oem
http://www.mediafire.com/?3almqggzvgy (OS.NB.payload is not included. place one in rom folder.)
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning. (.VM is not included. take it from another hermes rom to cook it!!)
happy new year, and happy cooking!

Congrats and welcome to hermes cooking sir. if you need a copy of a unprotected rom of mine, just let me know, PM or post
Peace sir,
Joshua

Very big thank for you...
qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
I'm Andy. Thank you very much, qtotter-san.
Lately I've been thinkin about changing my handheld (I'm using BA and MPx200 at this moment). But, despite my condition as a Japanese language student, I would love to have a Handheld powered by Japanese Windows OS. To buy Japan's handheld seems to expensive for me, so I decided to search for Japanese ROM first, then decide which one shall I buy.
I've been searching all the time for Japanese ROM (not 日本語化 ROM but 日本語版 ROM FILES), n finally, look what I found here, not only Japanese ROM, but Hermes WM6.1 Japanese cooking base (very big thanks ^o^). I've tried to search in xda-developers, and some other forum, but still unable to find Japanese ROM. I'd also sent private messages to Japanese developers here, but still I have no idea where to find Japanese ROM.
And now, I found this thread. This really helps me.
心から感謝を申し上げます。(kokoro kara kansha wo moushiagemasu)
Once again thank You very much, qtotter-san. I really appreciate your hardwork.

qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://rapidshare.com/files/178421014/hermes_jpn_wm6.1_cooking_base.zip.html
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!

could anyone tell me how to build OEM MMSLite?

antony34 said:
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!
Click to expand...
Click to collapse
it seems like it's been downloaded 10 times, already... the link has been updated.
qt

qtotter said:
it seems like it's been downloaded 10 times, already... the link has been updated.
qt
Click to expand...
Click to collapse
Thanks a lot!!!

I hope the explanation of WM6.5,please!

Opal/Diamond Dialpad
if you use opal dialpad with japanese wm6.1 rom, smart dialing stops working. i happened to find a solution while playing with my diamond. just delete the following reg key to make smart dialing work.
[HKEY_LOCAL_MACHINE\Security\Phone\PhoneKeyMatch]
"SmartFilterFlags"=dword:00000002
This entry is in the *.rgu of Base_Lang_0411.

Download won't start
Is anything wrong with the server?

Woops!
Problem solved by deleting temporary internet files

updated japanese wm6.1 base to 21014
i will update msg #3 shortly.

Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...

antony34 said:
Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...
Click to expand...
Click to collapse
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.

qtotter said:
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.
Click to expand...
Click to collapse
But I can't avaliable BT at comm manager...

antony34 said:
But I can't avaliable BT at comm manager...
Click to expand...
Click to collapse
confirmed. i will check what causes this later.

May I ask some one to upload a COOKED Japanese rom?
I am far from to play with Hermes, have switched to Raphael.

qtotter said:
confirmed. i will check what causes this later.
Click to expand...
Click to collapse
qtotter sann,
Wifi & Camera seem also have problem.
Wifi & Camera sometime got error when avaliable.
I will keep report if still have problem or bug.
Thanks!

ubiquio (mwg) 501 XIP ported, need help for SYS+OEM

All,
I own an MwG (formerly ubiquio) 501 and eventually started looking for software updates for it. The device is mostly ditto to the imate JAQ3, so I proceeded as follows:
1- get a WM6.1 ROM for JAQ3 (as linked in a thread of this very forum)
2- try to flash it (fail)
3- disassemble the ROM with tools from chinese website (osnbtool.exe)
4- port XIP merging with the ROM of my own device (thanks to the wonderful manual full xip porting thread!)
5- insert my original IMGFS of SYS and OEM
6- success!
the current situation is (settings -> about)
CE OS 5.2.20269 (Build 17936.0.3.0)
The performance boost obtained by upgrading the XIP is significant (keyboard is usable and video playback is ~ 15fps @ full screen), but I would like to perform more optimizations (e.g. switch to .NET CF 3.5) but as soon as I start to work with the dumped SYS and OEM I have troubles, it seems that every kitchen is expecting to work on the XIP (or on .nb and .nb.payload) but such files are not compatible with the one I get from osbntool.exe (but the dump folder is).
Do someone have advice on how to proceed? I would like to either
1-find a kitchen that works with my device
2-go for manual cooking
For 2 I achieved to split the dumped folder to packages and removed some of them, then - as far as I understood - I would need Greloc (got it) and bepe's buildos.exe (nowere to be found )
Is someone willing to help me? Thanks a lot.
Rest assured I am going to share the obtained ROM (I am already willing to share the current one, of course, just drop me a line!)
Best,
DAniele