XDA Flame User Forum at xdaflameusers.com

thierryb wrote:

Ok concerning the different steps.
But what I do from my dump ?
What I have understood is :
1/ build packages with the bepe tool
I suppose this one
http://forum.xda-developers.com/showthread.php?t=296861
2/ then ?????
I do what with my rom ?
I add the missing packages ?

Sorry for the confusion.
The normal way to cook with this kitchen is:
1. put your ROM in ROM folder inside the kitchen.
2. in the subfolder XIP, you must put the .rgu , .dsm and boot.rgu from you XIP. This files are needed to rebuild your ROM.
3. run the "DumpFiles.cmd". The kitchen will dump your ROM and after that packages will build automaticaly. Now you have an SYS and an OEM folder.
    Unfortuately the builded packeges are not named correctly like the tool does it with an Atom ROM. I don't know why.
4. Now you can put for example folders from an other ROM in yours, edit the initflash.dat to change the folderstructure of your new ROM, edit the registry you like.
In order to relocate modules you must run the G'reloc tool before building your ROM.
5. execut the "BuildOS.cmd". the new cooked ROM will placed in FLASH folder.

As i said before,in your ROM the kitchen doesn't name the folders correct, so it's hard to compare with other ROM.
For better understanding, you can use the Atom Life ROM in the Atom Life Kitchen from XDA developers. You'll se what I mean.
Hope it's not too confusing.

Using xipport I have extracted the 2 parts
x000000 - x1BFFFF : xip1
upload : http://w13.easy-share.com/13046311.html
This section contains the kernel (nk.exe) and a file named splash.bmx (the splash screen ???)

x1C0000 - xA3FFFF : xip2
upload : http://w13.easy-share.com/13046741.html
This section contains a lot files

I have also tried with x1C0000-x572027 (before the first false imgfs section), and I get nothing.

I have cut the xip by my self using an hex editor.
Perhaps it is the difference between us.

thierryb wrote:

[Missing Manifests]
  d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
  723fb954-d931-4348-b672-82a188e587b5.dsm
  dde70581-d88d-e5f3-b04c-586ecf07ba9e.dsm
  77eaca81-6269-4146-9c0d-226ca87da7e6.dsm

What does this mean : Missing manifets ?

And OEM ans SYS folders are created in the dump directory.
All modules have been arranged inside.

It's described in Bepe's thread:

Missing Manifests
This is a list of all packages that are missing inside the dump folder.
It is normal that there are missing packages, because the packages from the boot section (XIP) are missing... don’t worry about them

I've done the following:
1.extracted the rom with kitchen.
2. unfortunately the correct names are missing.
3. make the packages manually with mamaich's tools and bepe's package tool. But bepes tool doesn't copy the os.bat. So I just copy the os.bat from dump in the created sys folder.
4. I delete the SYS and OEM folders, created from kitchen first !! and then copy instead the SYS and OEM from bepe's tool.
5. now I run the "BuildOS.cmd" and the new ROM was build in FLASH folder.

Before build, you can now place packages in SYS folder. You can find prebuild packages from programms on XDA-Developers. Or just replace folders from your ROM with folders from an other ROM.
But remember, if you replace modules, you must relocate them with G'reloc before.
I know, the way I do is a little bit "tricky", but I think it's a way to do this job. Maybe you find an other one.

Last edited by scorpio16v (2007-12-23 22:16:22)

scorpio16v wrote:

I've done the following:
1.extracted the rom with kitchen.
2. unfortunately the correct names are missing.
3. make the packages manually with mamaich's tools and bepe's package tool. But bepes tool doesn't copy the os.bat. So I just copy the os.bat from dump in the created sys folder.
4. I delete the SYS and OEM folders, created from kitchen first !! and then copy instead the SYS and OEM from bepe's tool.
5. now I run the "BuildOS.cmd" and the new ROM was build in FLASH folder.

Before build, you can now place packages in SYS folder. You can find prebuild packages from programms on XDA-Developers. Or just replace folders from your ROM with folders from an other ROM.
But remember, if you replace modules, you must relocate them with G'reloc before.
I know, the way I do is a little bit "tricky", but I think it's a way to do this job. Maybe you find an other one.

I am not sure to understand.
It this the same kitchen ?
http://forum.xda-developers.com/showthr … fe+kitchen

1/ extracted the rom with kitchen

do you mean from my diskimage.nb0 ? or from the Atom Life ?
do you mean using the dumpfiles.cmd ?

2/ unfortunately the correct names are missing

I do not understand this sentence

3/ make the packages manually with mamaich's tools and bepe's package tool. But bepes tool doesn't copy the os.bat. So I just copy the os.bat from dump in the created sys folder.

Is it the steps I have already done that makes me the dump, and the OEMand SYS folders ?
what do you mean by the os.bat ?

4. I delete the SYS and OEM folders, created from kitchen first !! and then copy instead the SYS and OEM from bepe's tool.

ok

5. now I run the "BuildOS.cmd" and the new ROM was build in FLASH folder.

I remeber you that I have had a problem with the pckg2dmp.exe
In addition, you do not speak about the copy of the .rgu and .dsm (obviously, I have deleted the one proposed by jiggs)

Unfortunately this rom does not boot and stays at the O2 screen..

thierryb wrote:

[Missing Manifests]
  d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
  723fb954-d931-4348-b672-82a188e587b5.dsm
  dde70581-d88d-e5f3-b04c-586ecf07ba9e.dsm
  77eaca81-6269-4146-9c0d-226ca87da7e6.dsm

I have not read on yet, so not sure if anyone answers it.

This is the XIP Section which can be found in the zip file link in one of our thread started by KOster.
http://xdaflameusers.com/viewtopic.php?pid=1578#p1578

The Flame Kitchen & Atom Life Kitchen are based on Bepe & Mamaich's tool. Both concept is same, only the running batch/cmd files are different.

When you dump out the Rom, it is in DUMP directory. Which you can make your edit here. Use Dump to Package to convert the edited dump into OEM & SYS directories format. Now the XIP (still figuring) in ROM directory which was provide http://xdaflameusers.com/viewtopic.php?pid=1578#p1578 has to be used together with SYS & OEM to run BuildOS and we will get the new Rom.

Of course still got the CID unlocked mentioned by afeng.

thierryb wrote:

I will continue with the alom life kitchen, because it is easy to use and to modify. But I will switch to the one proposed if I continue to have problem.

You are probably right concerning the nosplit option. It was exactly what I was thinking doing the night.

OK, just for completeness. Here you can find the Atom / Atom Exec Kitchen:
http://forum.xda-developers.com/showthr … om+kitchen
Both kitchens are the same. Only the dump and build scripts are different.
Both are based on Scoter Kitchen:
http://forum.xda-developers.com/showthread.php?t=293296
The Scoter Kitchen contained some further good tools like an hexeditor, an tool to compare different binaries , ROMMASTER v2.3 to extract your XIP (and write it back in future) and the SRPX tools if you want to extract the Atom Life XIP section.
I think, I should stop posting now, because it causes more confusion than make the things clear, sorry.
But if you have further questions, I'll try to help.

thierryb wrote:

I will go in the scoter kitchen. In fact I have already downloaded it. But it was to complex to use, and I was less educated.
What I need now is the process to port from WM5 to WM6 a new device. What are the different steps.

Just to know now my flame kitchen based on the Atome Life works after having removed the nosplit option.
I will post it when somebody will ask me, or when I will have confirmed that I can do modification of the rom. Now I have just cooked a rom with the same content.
I will use it today and wil know if it is stable.

I have downloaded the WM6 atom life rom. But it is an exe (a ruu tool). Do you know how to extract the flash.dio from it.
What wm6 rom do you advice me to start from.
We will need sdhc support and VGA.
But perhaps I can start with a non vga one. Do you think that a pda with a non vga rom will run on a vga phone ?

The only think I know i that I will have to work on the xip. I am ready.

You can extract the Atom Life ROM easily.Just run the exe. The exe will extract and the updatetool starts. Don't stop the tool.
Go to Windows/Temp and you'll find FLASH.DIO and ExtROM.img. Grab them to the folder you like.
Now you can close the updateutility.
you can change all packages, that are not dependend of the resolution for example some named like ***_dpi96***. Thats QVGA specific.
Most what you find in OEM are device dependend drivers, i think.
How to port WM6?
I think the best is to grab an original WM5 Atom ROM and compare it with an cooked Atom WM6 ROM.
Maybe a HTC Universal WM6 port is more what you need to cook ?

One more hint.
With HyperCore Kitchen, you can extract the ROM from following devices:
HTC Wizard; HTC Hermes; HTC Artemis; HTC Herald; HTC Universal; HTC Trinity; HTC Prophet

Link:
http://forum.xda-developers.com/showthr … re+kitchen
It build Packages automaticaly. So you can grab the VGA specific parts from Universal to port in XDA Flame.

Last edited by scorpio16v (2007-12-24 13:35:03)

thierryb wrote:

Ok, lets try...
1. Dump the XIP's (WM5 & WM6) under two different folder
2. Replace WM5 XIP, keep the OEM part in the XIP intact and replace all others (with WM6).
3. Relocate and write new memory location
4. Update the base address in nk.exe
I need to understand steps 3 and 4.

Here in Atom Wiki is something about XIP editing.
http://wiki.xda-developers.com/index.ph … king_Notes

I thing the first link is the more detailed.
for relocating the given modules in XIP, you must use Bepe's XIPPort with the "relloc P" button. But you must know, that there are some modified XIPPorts and they may work better or worse.
Maybe M'reloc_nk from this thread usefull. But I'm not shure.
http://forum.xda-developers.com/showthread.php?t=331094

The heavy part is, you must build map.txt with XIPPort from both XIP and edit all by hand.
I don't know if the better way is to port imgfs first and if all is running fine to port the XIP.
Maybe in a short time you could get hands of the chinese WM6 port to learn how they are doing this job.
If you have success with XIPPorting please update your findings, because that's the step I fail.

Have you successfull flashed your recooked ROM ?

Last edited by scorpio16v (2007-12-25 20:42:23)

Wonderfull !!!
One more hint:
-the .ROM and .VM folder must be the Flame ones. All other you can change.
-if you edit the default and user.hv with notepad, you must cut the first 2 bytes with a hexeditor. Jiggs does the job with WORD and don't need to cut then.
- some .rgu in the extracted ROMs weren't extracted correct, sometimes. (they contained nothing then). Delete them or restore it with te right entries before rebuilding the ROM.
If you need something usefull to test, have a look to this:
http://forum.xda-developers.com/showpos … stcount=27
It's the OEM package for the new .NET CF
Just delete your old one.

My Trinity WM5 has increased in speed by 40% and under a WM6 by about 20% increase once you uninstall .NET 2.0 and install 3.5.

Last edited by scorpio16v (2007-12-25 22:00:19)

why some drivers are in the xip and others are in the dump?
May I move drivers from the xip to the dump? It could be an idea. because they are modules, and I have greloc to relocate them.
I do not know what I will do.

My rom: the genuine wm5 repacked from all files
I will try latter the same thing but with the xip.
Repacked means extract everything in modules, in OEM and SYS, then repack, using the files extracted from Xip: .rgu and .dsm

I am reading now a good document from cmonex here :
http://www.hpcmonex.net/izemize.htm
The link ce rom editing.
In the zip, the doc full tutorial in documents.