yashsingh1/xdaforums huggingface dataset:
[Sable] DSwarP:
Hey all,

I downloaded your kitchen sergio, but when I cooked the rom and flashed it, it seems to say that it's a Beta that expires on 5/1/2010. Is there anyway to get rid of that?

You said kioevad cooked up a rom using your kitchen, and I noticed that his did not have the Beta problem.

Any advice on that?

Also, another problem I have run into is that I can no longer flash new updates. I am getting a message in SDLoader saying "Update error. Pls check!"

I'm hoping my SD Card is just on the fritz and can fix this problem by trying a new one, but if you've seen this before and know how to fix it that would be cool too.

Thanks
[Sable] Emrulez:
you need to edit the rgu in shell and remove the beta lines.

Abou the flashing I cant seem to reflash either, the sdloader starts but it doesnt progress, its just blanc.........
[Sable] keyx:
if sd loader stop working, you need to use dnw to flash it and sdloader should recover itself after. It happenned to me sometime ago
[Sable] Emrulez:
I have reflashed 23562 already with dnw havent tested sdloader yet.

Nice to see you again keyx ;)
[Sable] DSwarP:
Does DNW work with Windows 7? I tried installing it, but I couldn't get the driver installed properly.
[Sable] keyx:
i heard it only work in 32 bits mode. not sure if it work in vm of winxp however but it can get complicated to pass through usb device to vm
[Sable] DSwarP:
I got DWM to work, flashed it, everything went fine, except now I'm just stuck at the blue HP boot screen.

Nothing I have done will get me past it. Tried reflashing twice, tried getting into SDLoader, tried doing clean boot, nothing gets me past the blue HP screen though. Any advice?
[Sable] rikee:
you could try to flash original HP firmware, then start modding aggain
[Sable] keyx:
posted 23563 wwe kitchen
[Sable] Emrulez:
just build a rom with 23563 kitchen. HAd a lot of trouble with my phone and its sdloader. after a few times flashing woth DNW it works now atleast the phone :p

I have noticed that I have 60mb ram on first boot , with sergioruses 23562 kitchen I had 70mb ram. Anything I did wrong?
[Sable] keyx:
I haven't looked at his kitchen but it is possible that he removed some packages to save ram .etc
[Sable] Emrulez:
nope SYS is the same as far as I can see. Pherhaps the xip?
[Sable] ---UFO---:
maybe it's because of pagepool.
[Sable] keyx:
you get access denied error, may be make sure your folders are not read-only ? any error from cooking the rom mean the resulting rom is not usable
[Sable] sergiorus:
Dont know will be this info helpful for you or not, but I have issue with access denied when my antivirus program is switched on. When i turn it off all become normal as usual. (Kaspersky Internet Security)
[Sable] ahfei:
Thanks keyx and sergiorus. I got it working now. But after 30+ tries I don't know exactly what was the problem.

Keyx's message pointed me to the filesystem problem. On problem that i did have was that i extracted the directory to a deep path. Relocate the kitchen under "C:\ipaq 61x 21728 - WWE" definitely helps. (otherwise, i got "The filename or extension is too long.")

Also, my file system was down to ~500MB after many attempt of extracting the kitchen and deleting it. Empty the recycle bin gives me 2.5GB again. My suspect is that the "access deny" was due to file system full.

So as to AV. I am using symantec antivirus. But i have successfully created the ROM with its auto-protection turned on.

Anyway, here is what I will do if I have trouble.

1. make sure i have 1GB free space

2. extract "ipaq 61x 21728 - WWE\" to C:\.

3. turn off antivirus (maybe)

4. if it doesn't work (yeah, it happens), extract everything and do 1-3 again.

5. it will work eventually.

Anyway, enough ipaq 612 kitchen preparation, time to cook.... dinner.
[Sable] keyx:
23001 kitchen posted
[Sable] keyx:
-attached cecompr_nt.dll for fixing memory leak in 1st post

-LZX compression tutorial in 3rd post
[Sable] sergiorus:
Would like to try LZX Compression on my roms, thanks for tutorial.
[Sable] sergiorus:
Hi keyx

I have a problem with LZX compression.

When i am trying to report XIP with replacing yours cecompr.dll file, appears message "Not enough space". I noticed that yours cecompr.dll is 35.1 kb, old one was 5.85 kb. Any solution?

PS Do you have file giisr.dll in your XIP?
[Sable] keyx:
Here are the files I have in modules folder, also I think the ceompr.dll I posted is from here anyway, I have attached my map.txt for your reference:

29/06/2009 09:45 PM <DIR> busenum.dll

29/06/2009 09:45 PM <DIR> trueffs.dll

29/06/2009 09:45 PM <DIR> cachefilt.dll

29/06/2009 09:45 PM <DIR> relfsd.dll

04/07/2009 07:44 PM <DIR> cecompr.dll

29/06/2009 09:45 PM <DIR> regenum.dll

29/06/2009 09:45 PM <DIR> ceddk.dll

29/06/2009 09:45 PM <DIR> pm.dll

04/07/2009 07:05 PM <DIR> certmod.dll

29/06/2009 09:45 PM <DIR> nk.exe

29/06/2009 09:45 PM <DIR> coredll.dll

29/06/2009 09:45 PM <DIR> mspart.dll

29/06/2009 09:45 PM <DIR> crypt32.dll

29/06/2009 09:45 PM <DIR> mencfilt.dll

29/06/2009 09:45 PM <DIR> device.exe

29/06/2009 09:45 PM <DIR> initvmmap.exe

29/06/2009 09:45 PM <DIR> devmgr.dll

29/06/2009 09:45 PM <DIR> imgfs.dll

29/06/2009 09:45 PM <DIR> diskcache.dll

29/06/2009 09:45 PM <DIR> giisr.dll

29/06/2009 09:45 PM <DIR> fatfsd.dll

29/06/2009 09:45 PM <DIR> fsreplxfilt.dll

29/06/2009 09:45 PM <DIR> fatutil.dll

29/06/2009 09:45 PM <DIR> fsdmgr.dll

29/06/2009 09:45 PM <DIR> filesys.exe

04/07/2009 07:45 PM 252 filesys.exe.txt

04/07/2009 07:45 PM 252 fatutil.dll.txt

04/07/2009 07:45 PM 251 fsdmgr.dll.txt

04/07/2009 07:45 PM 251 fatfsd.dll.txt

04/07/2009 07:45 PM 256 fsreplxfilt.dll.txt

04/07/2009 07:45 PM 254 diskcache.dll.txt

04/07/2009 07:45 PM 250 giisr.dll.txt

04/07/2009 07:45 PM 251 devmgr.dll.txt

04/07/2009 07:45 PM 250 imgfs.dll.txt

04/07/2009 07:45 PM 251 device.exe.txt

04/07/2009 07:45 PM 254 initvmmap.exe.txt

04/07/2009 07:45 PM 252 crypt32.dll.txt

04/07/2009 07:45 PM 253 mencfilt.dll.txt

04/07/2009 07:45 PM 252 coredll.dll.txt

04/07/2009 07:45 PM 251 mspart.dll.txt

04/07/2009 07:45 PM 252 certmod.dll.txt

04/07/2009 07:45 PM 247 nk.exe.txt

04/07/2009 07:45 PM 250 ceddk.dll.txt

04/07/2009 07:45 PM 247 pm.dll.txt

04/07/2009 07:45 PM 252 cecompr.dll.txt

04/07/2009 07:45 PM 252 regenum.dll.txt

04/07/2009 07:45 PM 254 cachefilt.dll.txt

04/07/2009 07:45 PM 251 relfsd.dll.txt

04/07/2009 07:45 PM 252 busenum.dll.txt

04/07/2009 07:45 PM 252 trueffs.dll.txt
[Sable] sergiorus:
I see, you have giisr.dll file. OK

Map, you posted, has overlapped modules :confused: OK, i think you posted it just to show me files, isnt it?

Your newer build include lzx compression?

I tryed lzx compression with removing one module from XIP. Just to try it in kitchen, not boot.

So what i can say, it is so slow (5 min to build rom) and result was about 3 mb less. You say about 13%, strange...:confused:

So i need to think, include it to my rom or no...
[Sable] keyx:
Only the CHT build use LZX because I want to include a 10mb font. I guess the compression would depend on the content.

I have attached the proper map.txt (6.5 23001)
[Sable] Samhain77:
I'm trying to build a WM6.5 rom for 91x but I continue to have windows errors when trying to extract xip from Montecristo's 2.4 (or even 2.3) rom.........

Using your 21921 kitchen..... HELP PLEASE!!!! ;)
[Sable] Montecristo:
I upload the kitchen during the day.
[Sable] Samhain77:
Have you used flex kitchen? Is this why I can't get out your XIP?
[Sable] Montecristo:
Nop, I use the standard kitchen.
[Sable] Samhain77:
Where have you find the original XIP to make your own rom?

Sorry for all these questions but I'd like to learn how to cook a rom... ;)
[Sable] keyx:
what do you mean by can't get xip out?

you just use this command to pull xip out:

osnbtool -d flash.dio 1 xip.bin
[Sable] Samhain77:
Keyx, this is what I've done till now:

Using your 21921 WWE Kitchen and Montecristo 2.4 rom (based on 21921) as TEMPLATE.ROM.... I've extracted the XIP and the boot.rgu file (I'm cooking for 914c).

Replaced the boot.rgu in the original XIP folder and built the rom with "iPAQ61x-91x flex kitchen" (option 2).... all seems to go without any error and at the end I got the FLASH.DIO file. I flash it on my phone and when it's going to Clean boot it stucks on white screen with blue stripes (as the one when you have the wrong version XIP).

I've not replaced any file in the kitchen (except for the TEMPLATE.ROM and cecompr_nt.dll).... I'm trying to recreate a simple rom before trying to change it in Italian language

I can't figure out why it isn't working.... :(
[Sable] keyx:
you didn't change the OEM folder right?
[Sable] Samhain77:
You're right.... I haven't change it
[Sable] keyx:
ya you still need correct drivers and other stuff in OEM folder as my kitchen only contains those for 61x.

also boot.rgu should be replaced under ROM/XIP (I think you did that but remind you just in case)
[Sable] Samhain77:
ops....... I've changed the boot.rgu but not the driver on OEM folder..... is there a way to extract drivers from other roms?
[Sable] Samhain77:
if I try to extract with your kitchen I got XP memory error.....
[Sable] Samhain77:
I've worked it out on extracting files (just tried on 3 different pcs and on the last it works without XP system errors) but now on the final extraction process I got a lot of error like these:

ERROR: could not find pointer for ofs 805aa001

ERROR: could not find pointer for ofs 805aa000

Then it says extraction successful..... I build the rom and the result is WM6.5 is loading but without the graphic! I can only see few things on the screen and all seems to run very slowly..... but I'm sure the rom I used as template was working fine on my phone.....
[Sable] Montecristo:
I'm up the Keyx kitchen with my files so you can work from there.

Wait 1 hour aprox.
[Sable] gkleding:
imageinfo.bin error

Keyz

Trying to run RK for 23001, keep getting an error message that says

'Could not find file C:\ipaq61x23001-WWE

Kitchen\temp\dump\7b54519d-760a-422d-9c77-cf834db47b4\imageinfo.bin'

Ran it same as always. Any ideas?

Thank-you

Sunday
[Sable] gkleding:
Nevermind, my mistake

I got it, sorry to trouble you.

Sunday
[Sable] keyx:
added FCC information link in 2nd post for 610c and 910c (contains internal photos .etc)
[Sable] chucknican:
Hy!

I've got a question keyx..

so I've downloaded the german Windows Mobile 6.5 Developer Tool Kit and unpacked it...now I want to cook a rom with it, but I don't know how to do it....

can I easily take the SYS-files from the developer-kit and the OEM- & XIP-files from your ROM(with the same kernel) and put it together and cook it?

Greets

chucknican
[Sable] Verticalx:
How should I make RUS version of this kitchen?

I've downloaded 2 russian MUI's (probably for 6.5 version), first, I should overwrite files in MUI archive with files in SYS folder (*lang*) folders. That's all or there are something else to do?
[Sable] chucknican:
arn't there russian boards, where you can download russian roms?

here's a tutorial...but I don't come along with that...

http://xdaforums.com/showthread.php?t=311078
[Sable] keyx:
you need to remove all 0409 folder with russian lang folder, also you need to at least remove OEMLANG_XXXX and replace with russian OEMLANG folder and possibly the OEMAPP folders too
[Sable] Verticalx:
thanks! :)
[Sable] Montecristo:
Keyx.

I'm trying to use the new cecompr.dll but to make the "write maps" the xipport says:

There is already an entry with the same key.
[Sable] keyx:
you need to re-map the address, use xip address tool to reallocate the first DLL addr
[Sable] Montecristo:
What xip address tool?

I use xipport:

1 - realloc

2 - write map Here is where it says: "There is already an entry with the same key."

3 - build xip_out.bin
[Sable] Montecristo:
Any idea, Keyx.... please....:rolleyes:?
[Sable] keyx:
you got the error because the (LZX) cecompr.dll is much bigger than the (XPR) one and xipport couldn't relocate the memory address automatically. You need to use xip address tool(XIPAddrTools.exe in TOOLS folder) to relocate the first DLL addr section or manually relocate them. To use Xip address tool, launch the exe and then set working folder to your OUT folder then you wiill see some red line in the first DLL addr tab . You need to change the start address of the dlls to fit them such there are no overlap(red line), see step 5 of this post on xip porting. Xipport is NOT an fully automatic xip porting tool, it can only relocate properly if the replacement modules are similar in size , if you replace a small module with a big module then you will need to manually relocate the address

Why do you use LZX anyway? Even with XPR you should still have around 5 -6 mbs space to include custom software in the ROM I believe.
[Sable] Montecristo:
The program tells me "Connot Open M'Reloc"

:(

The new roms, 23009, is occupied 83 megs, not include anything new.
[Sable] keyx:
you may want to compare to the old version to see what cause the big file size increase.

Did you run XIPAddrTools.exe under tools folder? MReloc should be in the same folder
[Sable] Montecristo:
Yes, is the same folder...:(:(
[Sable] chucknican:
Hy!

So, I tried to build my first ROM, but it doesn't work..

so, what I've done:

1) extract the emulator ROM

2) put the SYS FROM the emulator, OEM(driver, lang, misc, dpi only the files I need) and XIP(kernel, all files) from a rom you created with the same kernel.

3) keep .ROM from the emulator but use .VM (full folders!!) from your rom(with same kernel) and the WinCENLS_WWE(full folder!!)

4) keep the flashinitfile.dat from the emulator-rom

5) didn't changed anything else!!

so, now the problem is, that the flash.dio file is successfully written, but after that, it does a cleanboot and there it hangs. what have I've done wrong?

Greets and thanks for your help!

chucknican
[Sable] keyx:
what's the size of the flash.dio? (cannot be greater than 81920 kb)

Which rom kitchen version did you use? The ROM folder should come from 21234 (although non-matching sys/xip would usually works but you should start with 21234 xip since you use emulator image.

initflashfile.dat should come from 61x instead of emulator image.

When you copy the SYS from emulator image you didn't copy the OEM* stuff right? your OEM should always come from 61x ROM.

I suggust using .ROM folder from my 61x ROM. Although I am not sure if it matters
[Sable] chucknican:
Hy!

1) my ROM is about 54272 KB

2) ok...I changed it

3) ok...I changed it

4) yes, I use OEM from the 61x

5) Here they say, that only .VM and the WinCENLS_WWE have to be ported...but if you say, that it would work if I youse the .ROM file from the 614c, I use it..and I've copied the two shellfolders too...

so now it comes forward!! Now it doesn't hang by cleanboot, now it hangs betweetn the HP-logo and the WM-bootscreen....the W-LAN-LED blinks...

another question...what kitchen do I have to use? the flex or the other?

greets

chuck
[Sable] keyx:
do not overwrite shell folders from other build(unless you have a good reason to do so)...you should use the sys as whole, mix and match can easily cause boot problem. (especially for critical components)

I wonder why don't you just use one of my kitchen as a starting point? It would be easier than you try to mix & match stuff. You can use the batch file with "flex" , just that when you decompose the rom some dll aren't placed correctly and need to manaully relocate them
[Sable] jirif:
I can extract any image properly with this extraction sequence i using in my testing kitchen for 91x based from your 0.3:

.
.
.

echo.
echo Dumping partitions ...
echo 0 BOOT
echo 1 XIP
echo 2 IMGFS
msflshtool.exe TEMPLATE.ROM -d

echo.
echo Extracting IMGFS partition ...
IMGFSTODUMP TEMPLATE.ROM.part2
PKGTOOL.exe dump

.
.
.

There is problem using IMGFS generated by "prepare_imgfs" to extract with "imgfstodump" because "imgfstodump" end with lots of errors or simply crash. IMGFS extracted with "msflshtool" do not cause those problems, and i can use contens of extracted image without problems :)
[Sable] keyx:
well actually is not that the current way doesnt dump the file, the problem is some dlls does not go into sys folder when using pkgtool, I think recemod seem to mess up something and cause those dlls left in the root folder

-----------------

btw 23016 kitchen is posted
[Sable] keyx:
21854,23047 kitchen posted
[Sable] Verticalx:
thanks

i'm gonna try 23047 on my HP IPAQ 914c. I have my language MUI (0419 - Russian). I will overwrite 0409 folders with 0419 ones.

But In MUI there are several folders with different DPI & resolution.

'dpi_96_resh_240_resv_320' is for 914c?

Do I need to change boot.gru?
[Sable] Verticalx:
When I'm trying to extract Montecristo's 23407 ROM with your 23047 kitchen ImgfsToDump.exe perfoms incorrect operation (program will be closed... blablabla). At the end I receive a lot of errors like

ERROR: could not find pointer for ofs 505c3000, 505c3001, 505c3002... etc

is it ok? :confused:

p.s tried other kitchen versions - the same thing happen.
[Sable] keyx:
you simply remove 0409 folder and use 0419 folder instead and yes you use 240x320

that looks odd for the imgfstodump error..try downloading only the kitchentool in this thread instead (the 1st link in 1st post). for the file pointer error is fine because xip has empty space in between so nothing is found in those region during extraction of xip
[Sable] Verticalx:
Hi

I tried downloading only kitchentool, moving template.rom there and tried again.. the same thing. I thought it happened cause of something is wrong with .net frameworks or c++ runtimes. I removed all of them, tried again, reinstalled, tried again - nothing:confused:
[Sable] Verticalx:
*.dsm files - what are they for? is it safe to remove them?
[Sable] Jackos:
Use SEARCH!

http://xdaforums.com/showpost.php?p=1295647&postcount=4

http://wiki.xda-developers.com/index.php?pagename=dsm
[Sable] keyx:
i have posted the answer to extract his rom in his thread
[Sable] Verticalx:
10x keyx

Ok, so I need to move dsm file from every *****0409 folder to my ******0419 lang folder?
[Sable] keyx:
no you are deleting 0409 folder and copying 0419 folder to SYS instead
[Sable] Verticalx:
in my 0419 there are no DSM files. is it normal?

I took your kitchen 23047. Overwrited all LANG 0409 folder with my 0419 folders. Totally 39 folders. Overwrited boot.gru from 914c WM 6.1 to kitchen. Overwrited wince.nls.

I receive couple of errors, attached in file

At the end there are temp folders and no FLASH.DIO file..
[Sable] keyx:
if you look carefully there is this error: the filename or extension is too long

it failed for the command: move temp\dump dump

try make your folder path shorter like put in C:\kitchen insteaod of under doucments and setting .etc

also make sure you use 91x OEM
[Sable] Verticalx:
I made the short part and eveything is now ok :)

but, at the end of making new ROM kitchen requires TEMPLATE.ROM. At first time there was no template.rom, and program told something like 'can't insert...' and there was no FLASH.DIO at the end

After that I put TEMPLATE.ROM (Montecristo 4.2) to ROM folder and everything was ok at the end
[Sable] keyx:
ya it need a exisiting rom to work
[Sable] Verticalx:
did it

First by mistake I put Montecristos ROM into your kitchen.

Now it's ok

I'm using your kitchen 23047 + MUI 23047 + OEM from original HP ROM.

My ROM runs :) but VERYYYYY slow :confused:. Don't know why. system always hangs for about 30 secs than comes out for 3, than hangs again. screen doesn't correctly functions..

Any idea why rom runs slow?

After making ROM I get error about nothing is patched. Sounds like I'm getting FLASH.DIO same as original TEMPLATE.ROM?

P.S By the way, why XIP folder after extracting ROM always empty?
[Sable] Verticalx:
I'm not sure but feel like missing something.

I can't get things about XIP. Do I need manually port something from original HP ROM to your kitchen instead of boot.gru?
[Sable] keyx:
you just need Montecristos ROM (TEMPLATE.ROM) in the ROM folder and also the boot.rgu under ROM\XIP

the patching thing is not important, it suppose to put a build date into the ROM but does not always work.(although it works for 61x)

your OEM folder is for 0419 right?

as far as empty xip folder, i think it is because the script i have cannot automatically extract custom rom properly. if you extract the original hp rom it will probably works normally.

you don't need to port xip when you are not porting to a different build (different build like from 23047 to 23052), Montecristos 's rom already have the proper xip for 23047 so you can just reuse it

for slow rom..i don't know, may be you want to try to build a english rom first and see if it works normally?
[Sable] Verticalx:
BTW Will you post 23052 version of your kitchen?
[Sable] keyx:
just posted 23052

also what the rom kitchen really doing when building rom is rebuilding the imgfs(filesystem) section of the TEMPLATE.ROM(FLASH.DIO), it doesn't touch xip. xip need to be manually ported when needed
[Sable] Verticalx:
Had no luck at all with kitchen 23047

Now I'm playing around with 23052. In OEM folder is strange-organized, for example camera apps and some other stuff are placed in folder "OEMApps" but not in "OEMCamera", etc... Is it original path or you changed something?
[Sable] Jackos:
It's the original path. Blame HP ;)
[Sable] Verticalx:
I built rom 23052 with Rus lang

good news that it started ok it doesn't freezes, greetings keyx! :) But External keyboard doesn't work. No programs on START and many many more bugs

Wish I could get Montecristo's kitchen in my hands because I feel I'm missing some very important things that makes output ROM to be workable on 914c.

I mentioned that kitchen works very strange. Sometimes it gives errors with xipbuild, imgfsto, sometimes no in case that nothing was changed. It depends on if temp files are present or not, etc..

command TOOLS\IPAQBUILD FLASH.DIO always gives this result:

Trying to open FLASH.DIO

Patching build date to:....

No valid file given, nothing patched!
[Sable] Verticalx:
strange things. In 914c ROM all files are organized to each folder
[Sable] keyx:
the ipadbuild error can be ignored, like i said it just try to put a build date on the rom. it does not always work so that's fine.

did you use montecristo's oem when building the rom?
[Sable] Verticalx:
No I used my original Russian HP OEM. Also I tried to use Your original oem while playing with your Kitchen 23052, overwriting only LANG folders with my HP Russian OEM.

Also I'm unable to properly extract Montecristo's 4.2 ROM. I tried almost everyting: mixing OEM, Langs, etc., and getting dissapointed a little bit.. that is why I'm asking him to upload his extracted kitchen, but he's keeping silent
[Sable] Verticalx:
I'm sorry

I was able to extract Montecristos 4.2 OEM but I can't build it with my langs.

I overwrited his OEM with my (all folders were the same) and and all LANG folder with my LANG (total 39 folder - as in my MUI). Thats all.

But then I run build in kitchen BuildOS doesn't process folder with my LANG files, saying something like these:

the file 'temp\dump\mxipupdate_taskmgr_shell_1.provxml' already exists

If I delete LANG folder which belongs to this error, BuildOS finds error in next LANG folder.

But with your (keyx) kitchen 23047 everything builds smoothly and these errors do not appear. Only the cooked ROM doesnt work :D

I think Montecristo mixed something in his ROM. Like he put 3rd party OEM stuff to sys folder.
[Sable] keyx:
you can't have duplicate file when building rom

umm using my oem wouldn't work as the device are different.

so what happen when you use your original russian hp oem?

i think you could at least replace the OEMDrivers with the latest hp WWE one as it is language independent.

I think what you could do is take the latest hp WWE OEM, replace OEM_Lang with your language.

and replace all 0409 with your language in SYS.