yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] CRACING:
Ok, its :

HKLM\System\StorageManager\ FATFS\Filters -> CacheFilt

HKEY_LOCAL_MACHINE\System\ StorageManager\Filters\ fsreplxfilt -> ReplStoreCacheSize

I used the advanced config app to change the values. It was disabled before and I have set'ed to 2MB for cachfilt and 4096 sectors for ReplStoreCacheSize, since advanced config suggested so.

Its better now but a the OS is sticky ... sticky :confused: however it was same before too.

BTW; The ROM is WinMo 6.5 build 21806 with IE6 ( Latest ) + widgets.

Best Regards
[Windows Mobile Software Development] utak3r:
well, what I can say.....

With wm6.5 on Wizard you have to have a really well made ROM - and sorry, you won't find such ROMs on xda-developers, for last few years people here started creating overbloated monsters and have no idea about optimizing them :( sad but true - too many people are trying to cook nowadays and the tools are too easy to use - hence the results.

On the other side these days I don't know any good cooker who still has their Wizard to prepare a good wm6.5 - most of them (including me) have gone to other devices.

So... you just have to try make it more lite - and that involves heavy registry editing, cutting down resources, converting libraries to XIP modules and so on... good luck :)
[Windows Mobile Software Development] CRACING:
Yeah, :)

The only thing I need LZX compressing on WinMo 6.5 was to add IE6 and widgets. However it runs fine about 75% but only a sticky issue may be its due to less space on graphics ( I don't know that it is called ).

No problem. WinMo 6.5 runs super fast in XPR compression and may be LZX compression, if I make a non IE6 ROM(s).

Best Regards
[Windows Mobile Software Development] utak3r:
well, it's somewhere around 10MB, if I can recall... go and waste it ;) People are using other browsers, so... you know.
[Windows Mobile Software Development] CRACING:
Yeah, you are right. Many ppls use opera or 3rd party browsers so IE isn't the best. :)

Best Regards
[Windows Mobile Software Development] tonio94:
I reach the opposite result :confused:

It seems to compress LZX because it's much much slower to build the rom but at the end, mw nbh file change from 95Mo to 105Mo and the free storage at first boot from 100Mo to 80Mo...

Anyone have an idea on what I'm doing wrong ?
[Windows Mobile Software Development] c_shekhar:
yes I have used the patched cecomp_nt.dll in my tools folder. As a result the crashing was saved against but the compression itself is much much slower than the XPR compression...

Do you have any method in your mind to solve this issue?
[Windows Mobile Software Development] c_shekhar:
The speed of OS in same as with XPR niether good nor bad. (My personal observation only).
[Windows Mobile Software Development] CRACING:
Hello,

Nope. Its normal. :)

I think a high performance pc can do faster.:rolleyes:

OK, mine too is running same.

Best Regard
[Windows Mobile Software Development] jwzg:
Right now I'm porting the 19214 build from the Tilt to an 8525. I want this to be a perfect port, so I'm trying to leave in all of the kernel debuggers from the 6.1 XIP that some normally take out to make room. I may have to eat my pride here if this is going to be a huge amount of trouble.

I know that the physlast address has to be increased by around .3 mb or more to make this happen since the Tilt xip.bin is 3,096 KB vs. 2,687 KB for the 8525 xip.bin. Since I'm not really good with little endian, how would I go about doing this? I will likely have to move a module or two, but I simply want a stock ROM. Yeah, I'm weird like that...

I've used boggsie's method here to figure out where the imgfs is dumped in the 8525 WM6 ROM (0x00680000 in this case). When I use this address to dump the xip.bin, it increases the size of the xip.bin that is extracted by almost 700kb over the conventional method using cRacing's xip extraction tool. However when I write maps, the map comes out much different.

Alright, I've gone this far. Is there anyone willing to step in and point me in the right direction?
[Windows Mobile Software Development] c_shekhar:
it is not fixed value. Actually it is proportionate to the ROM size your are cooking. Like in my case the cooked ROM with XPR compression was 118MB whereas it came down to 102MB with LZX.

For making the LZX automated while cooking I have changed the XPR in the payload in folder \ROM instead of pausing the cooking at the stage of imgfsfromdump.
[Windows Mobile Software Development] Nokser:
Hello All.

I need your help.

I'm looking for a solution how to make a dump xip for WM2003.

Files based on the Alpine unit.
[Windows Mobile Software Development] utak3r:
you're right - but we were talking about the size of the new PIE ;) It's as huge as 10MB :eek:

Same with me - I've changed it in my source payload so I don't have to bother it anymore :)
[Windows Mobile Software Development] ivanmmj:
The reason why I made the walkthrough that way was because not everyone wants to use LZX and using it that way, it allowed me to be able to cook both XPR and LZX ROMs. (LZX ROMs tend to be so small, they have to be flashed through the SD card as the ruu flasher will fail from it.)
[Windows Mobile Software Development] utak3r:
So you have some strange device :p none of mine were complaining on that...
[Windows Mobile Software Development] ivanmmj:
lol. I know that the Herald, the Artemis and the Elf, amongst others, require it. :p Maybe YOU have a strange devices. :p
[Windows Mobile Software Development] !Aman!:
thats because there is minimum size protection in the SPL. but we overcame that in Elf(in) a long time ago (thx to cmonex)
[Windows Mobile Software Development] ivanmmj:
Really? Do tell! How did he do it?

I am very much interested in doing the same with the Herald! (And I'm sure that the Artemis would love it, too.)

I'd also love to merge the extrom with my main storage.... *closes his eyes and makes a wish*
[Windows Mobile Software Development] !Aman!:
she has removed that restriction for artemis also, if i'm not wrong :)
[Windows Mobile Software Development] ivanmmj:
So everyone but the Herald got the love. :(

I emailed her, let's hope she's got time to help us on the Herald forums.

On another note: I wonder if the SPL or IPL control the size requirements for the extROM... and if we can code it to be like the artemis, where flashing a smaller extrom, moves that extra storage to the main storage.
[Windows Mobile Software Development] utak3r:
:p

none of them complained: Wizard, Hermes, Himalaya and Universal :D
[Windows Mobile Software Development] utak3r:
For all those who still work with XIPPort: I've developed a small utility IITP to help you in this hard work :)

You can find it HERE.
[Windows Mobile Software Development] MAFoElffen:
Thanks! I just have a project "now" that will test this out tonight...
[Windows Mobile Software Development] d_train:
Just a question to you guru's...

If I have a xip_out.bin file instead of the actual xip.bin - am I still able to use that to create my new payload? I know the porting process creates the xip_out.bin - but I am downloading new XIP and SYS and it has the xip_out.bin instead of the full xip.bin and if I can use it great, otherwise I'll search for another XIP.

Also I would generally get the files and modules using XIPPort for the contents of the XIP folder, can I still get these if I only start with a xip_out.bin?

Thanks in advance.

DT
[Windows Mobile Software Development] mbarvian:
if the xip_out.bin is from the device you have, then you should be able to use it.
[Windows Mobile Software Development] mbarvian:
SPRX Compression

does anyone know anything about SPRX compression on the XIP?

look here:

http://xdaforums.com/showthread.php?t=488040

this might be able to compress the XIP for more RAM :)
[Windows Mobile Software Development] utak3r:
There will be some corrections, but for the most of times it should work ok :)

Unfortunately, I'm really, really busy now, so I don't know when I'll be able to work on a new version :/

It's just a filename - go for it, it's still the same XIP section :cool:

The problem is the bootloader would have to know about the compression of XIP to be able to load it...
[Windows Mobile Software Development] oldsap:
super noob question:

if i use imgfstodump on my imgfs.bin then it will create a \dump folder. and if i use the packagetoolexe on this dum folder, it will create an organised \Oem and \Sys folders, organised into "packages".

what if i have my oem and sys folders an want to reverse the process, unorganize them again so that i can use imgfsfromdump.exe to create a new imgfs.bin from it? what tool do i have to use?

again, sorry for the noob question in cooking roms
[Windows Mobile Software Development] utak3r:
Go for BuildOS, it's gathering all the packages into a flat dump structure. The key is, it requires quite few things to work, and not only SYS and OEM... the ROM directory is needed, also a tools directory with some tools.

Just grab some kitchen and you will get hang of it :)
[Windows Mobile Software Development] oldsap:
thank you for the quick reply. i am trying to learn about cooking for my eten dx900 phone. do you have any links for BuilOS with some tutorials for it? :)
[Windows Mobile Software Development] utak3r:
The BuildOS can be got from here:

http://forum.ppcgeeks.com/showthread.php?t=15636

the tutorial... it's not so easy to find any ;) But after you run BuildOS, you'll see this tool is pretty straight forward :) And as a result it produces a temp directory, in which you have a dump subdirectory - containing your whole new flat dump.

And... in few seconds you'll realize what's the advantage of having packages.

If you will have any further questions, ask us :)
[Windows Mobile Software Development] oldsap:
here's my question:

OEM - do i use my original dx900 oem or from a 6.5 rom?

XIP - i used XIPKitchen.exe to port one of the 6.5 xips to a dx900 xip - correct?

SYS - i use my original dx900 .ROM, .VM, WinCENLS_WWE files and use the other files from a 6.5 sys folder - correct?
[Windows Mobile Software Development] utak3r:
depends....

packages like OEMDrivers, OEMApps, OEMMisc or OEMOperators have to be from your device.

XIPKitchen? Well, I don't know it, but probably yes, correct ;)

Exactly so.
[Windows Mobile Software Development] oldsap:
thank you, i'll experiment on the BuildOS and your answers to my questions. i hope i dont kill my device :D

i'll post more questions after ...
[Windows Mobile Software Development] utak3r:
you won't kill it by flashing a bare OS, without touching bootloader :D
[Windows Mobile Software Development] oldsap:
btw, i have downloaded the BuildOS from the link you provided and it only contained the exe file. may i ask for the folder structures, wehere to put the oem, sys, temp.dat, xip, etc files and folders? :)
[Windows Mobile Software Development] boggsie:
This is really off topic in the XIP porting thread.

If you are looking for a quick way to get up and running on your device, I suggest you start with BePe's Platform Rebuilder kitchen. He even put video's together of how to use it.

http://darkforcesteam.com/showthread.php?t=569

You'll need to start with a ROM from your device, break it down and get accoustomed to the toolset by rebuilding the original rom in the kitchen. Once you've gotten comfortable, then you can start to learn how to port in a new OS. SYS, XIP and OEM pieces.

Best regards,

-boggsie
[Windows Mobile Software Development] oldsap:
thanks and sorry :)
[Windows Mobile Software Development] stevefxp:
Vzw 3.14 xip

Evening all,

This is my first foray into injecting an XIP into my build process, so please excuse the noobie questions.

I have a VZW Vogue, and I have downloaded the WinMo 6.1 upgrade, which includes the 3.14 XIP. I have split out the NBH file using the Vogue Kitchen Tools, and now have the pieces of the upgrade.

I have a folder called ROM. In this folder I have another folder called XIP, which has a file called Boot.rgu. I also have a file called 8004000-OS.nb. Based on what I have read I believe I have the basis for the XIP bin file...correct? Next do I need to split apart the 8004000-OS.nb to actually get the bin file?

Thanks,

Steve
[Windows Mobile Software Development] utak3r:
Yes, you have to dump it, because right now you have only a small piece of actual XIP - boot.rgu is only a small part of it. Get xip.bin out of this os.nb: first, if needed on Vouge, split it to get .payload file, then use for example osnbtool to get xip.bin out of it, and finally use dumprom on this xip.bin to get all its files and modules.
[Windows Mobile Software Development] stevefxp:
What is the best way to dump this? DUMPIMGFS?

Steve
[Windows Mobile Software Development] utak3r:
No.... I've wrote you what apps to use...

First - if needed! - do nbsplit -yourdevice os.nb, then get your xip.bin, probably osnbtool -d os.nb.payload 1 xip.bin, just take a look at the table it will print out and see if this red "1" is correct, and finally, do just dumprom xip.bin. That's all :)
[Windows Mobile Software Development] stevefxp:
Well I have made some progress. I was able to split the .NB file, and I got two files out of this (8004000-os.nb.payload and 8004000-os.nb.extra). After doing some reading I tried running osnbtool against 8004000-os.nb and it showed me the 4 partitions, of which part-1 was the XIP raw image. So then I ran osnbtool again and was able to extract the XIP raw image and called it XIP.bin. As you said I then ran dumprom xip.bin but was not able to extract any files. I got multiple error msgs that said: could not find pointer for ofs.

Did I do something wrong with the dumprom?

Steve

Steve
[Windows Mobile Software Development] utak3r:
Do it on your .payload file :)
[Windows Mobile Software Development] stevefxp:
So here is what I got running dumprom against both the payload and then against the nb file directly:

D:\Smartphone Software\Vogue_Kitchen_tools\ROM>dumprom 8004000-os.nb.payload

unable to determine loading offset for 8004000-os.nb.payload

D:\Smartphone Software\Vogue_Kitchen_tools\ROM>dumprom 8004000-os.nb

img 00000000 : hdr=80185adc base=80000000 commandlineoffset=7ffff000

img 0031f000 : hdr=801bbaa0 base=7fce1000 commandlineoffset=7fce0000

ERROR: could not find pointer for ofs 00000000

ERROR: could not find pointer for ofs 00800b82

D:\Smartphone Software\Vogue_Kitchen_tools\ROM>

I know I am close!!

Steve
[Windows Mobile Software Development] utak3r:
Two things:

First, I told you to use osnbtool to get xip.bin out of .payload, and then dumprom to get files and modules out of xip.bin - and that's not what you were actually trying to do ;)

And second, you have a wrong dumprom. Try the one I'm including.

Remember: first, osnbtool on .payload, then dumprom on xip.bin, ok? ;)
[Windows Mobile Software Development] stevefxp:
Sorry for my noobiness but here is what I have done. I ran osnbtool against my payload and got the following:

D:\Smartphone Software\Vogue_Kitchen_tools\ROM>osnbtool -d 8004000-os.nb.payload

1 xip.bin

OS ROM Partition Tool V1.56 By Weisun :> PDAclan.com

Can not find boot sector in the source file : 8004000-os.nb.payload

Can not find Part-1!

So I tried running osnbtool against the original nb file and got the following:

D:\Smartphone Software\Vogue_Kitchen_tools\ROM>osnbtool -d 8004000-os.nb 1 xip.bin

OS ROM Partition Tool V1.56 By Weisun :> PDAclan.com

Sector size : 0x00000800

Extra data bytes : 0x00000000

OS IMAGE found.

Partitions infomation:

**************************************

Part-0 type: BOOT SECTION image

Part-1 type: XIP RAM Image

Part-2 type: IMGFS file system

Part-3 type: legit DOS partition

**************************************

Can not find compression signature.

Part-1 de-packing...

Successfully de-packed to xip.bin

So I thought since Part-1 said XIP RAM image I was good to go. I now had a file called XIP.bin and it was about 3 meg in size. When I run dumprom against this I get a file called romhdr.bin, which is about 85 bytes in size. Thats it!

Again please excuse my noobiness but this is the first time I am undertaking this mission.

Thanks,

Steve
[Windows Mobile Software Development] utak3r:
Cool :D

Just to make sure: there is no folder XIP? ;)

If not, then get XIPPort, run it and issue "dump xip.bin" - you'll get the OUT folder.
[Windows Mobile Software Development] stevefxp:
Ok will do and thanks for staying with me on this.

Now for what I am trying to do, and I hope you can give me some guidance. As I said I have a Vogue, and I am using the PPPCKitchen BuildOS process. So for the Vogue I have a Vogue_Core.rar which is the core pieces of the Vogue OS. At present I am running 3.08 of the core, and my whole rationale for doing what I am doing is to upgrade the core to 3.14.

Since I can unrar the Vogue_Core.rar I am assuming I would just take the OUT folder that is created from dumping the 3.14 XIP and then update the rar? Is it as simple as this and then just cook a new ROM?

Steve
[Windows Mobile Software Development] utak3r:
if it is FROM YOUR DEVICE, than just replace it :) but if not - you have to split it into two parts: OEMXIPKernel, which is device-specific, and MSXIPKernel, which is common for all devices.
[Windows Mobile Software Development] stevefxp:
Woo hoo victory is close I say.

Ok so I ran XIPPort and I got the OUT folder, which had two folders in it. These are called Files and Modules. Is this the actual 3.14 ROM? Is there anything else I need before combining this into my original Vogue core?

Steve
[Windows Mobile Software Development] utak3r:
yep. it's your XIP section dumped :)

Now... all depends on a device itself, unfortunately. The quickest way to try is this:

In XIPPort, click "make pkgs". You will get OEMXIPKernel and MSXIPKernel folders (eventually MSXIPKernelTk, too). Look at them and replace those MS ones and leave your old OEM.

After that, in XIPPort do "undo" so it will restore the normal files layout. Then - "realloc P", "write maps", have a look at map files and finally do "build xip_out.bin".

If it won't work - you'll have to go to the tutorials from the beginning of this very thread.

Good luck :)
[Windows Mobile Software Development] poifgh:
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder. I want to now have those changes incorporated into a kitchen so that I could build up the ROM to flash my phone

I replaced ws2.dll in EXT\BASE and it overwrote the default ws2 during building the ROM phase and my changes are perfectly fine .. working on the TILT

But when I change the coredll in ROM\XIP\MSXIPKernel and perform a build the phone refuses to boot up. As far as I understand I need to rebuild the XIP. Are the instructions in this page exactly what I am looking for or is there any other place I can get them?

thnx
[Windows Mobile Software Development] utak3r:
yep, it's right there :)

The problem with a coredll can be it should be from the same build as the other modules...

btw, what changes have you done?
[Windows Mobile Software Development] poifgh:
awesome. I have put in a few hooks in kernel to profile some apps. I compile it currently in platform builder which gives me an image which works well with emulator. The image is named 'diskimage.nb0' or flash.dio.

When trying to extract the xip.bin from the emulator images using osnbtool results in an error

> \osnbtool.exe -d diskimage.nb0.payload 1 xip.bin

OS ROM Partition Tool V1.56 By Weisun :> PDAclan.com

Can not find boot sector in the source file : diskimage.nb0.payload

Can not find Part-1!

[I used nbsplit to split diskimage into .payload and .extra]

Any clues on how to get xip.bin from my own code using platform builder?

thnx
[Windows Mobile Software Development] utak3r:
do nbsplit on it... the switch is something like "-emu" or "-emulator"... try it.
[Windows Mobile Software Development] poifgh:
In my NBsplit there was no -emu flag - so I downloaded ROMDonald's tool which had the -emu flag and split the os.nb0 file

C:\ROMDonalds\02-Dump\NBSplit.exe -emu diskimage.nb0

NBSplit 2.0 RC 2

Done.

but then, osnb tool still faults

osnb\osnbtool.exe -d diskimage.nb0.payload 0 xip.bin

OS ROM Partition Tool V1.56 By Weisun :> PDAclan.com

Sector size : 0x00001000

Extra data bytes : 0x00000000

OS IMAGE found.

Partitions infomation:

**************************************

Part-0 type: XIP ROM Image

Part-1 type: IMGFS file system

**************************************

ERROR - partition table wrong!

Am I using old versions of the tools? I am usnig WM 6 for my emulator. Anyone any guesses? I want to implant my coredll [hence my XIP] into my kaiser
[Windows Mobile Software Development] utak3r:
hmmm.... how about imgfsfromnb?
[Windows Mobile Software Development] poifgh:
>ImgfsFromNb.exe diskimage.nb0.payload imgfs.bin

ImgfsFromNb 2.1rc2

Input file 'diskimage.nb0.payload' has no valid boot sector! Aborting.
[Windows Mobile Software Development] utak3r:
dumprom? (of course you have to use the one from ervius)
[Windows Mobile Software Development] utak3r:
...and if not, then just get this xip section manually out... it's really easy.
[Windows Mobile Software Development] jianwei87:
May i know what is the value that i should insert to my Xperia?

Currently i'm using

1. APP_SW_X1i_GENERIC_UK_CDF1215-1832_KOV_R3AA010_2

2. WM65-23004-lang-0409-dpi-192-resh-480-resv-800

So what value i should insert?

I have try insert the command "insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 -s 0x004C0000" and the result that i get is
[Windows Mobile Software Development] poifgh:
THat would be cool. Could you point me how to do it?
[Windows Mobile Software Development] boggsie:
http://xdaforums.com/showthread.php?t=453722

Best regards,

-boggsie
[Windows Mobile Software Development] poifgh:
Rommaster fails on the generated payload file. It is not for images generated for emulators

[Info] It is a common ROM.

[Error] Load nb00 failed.
[Windows Mobile Software Development] !Aman!:
A few chefs have asked me how i've managed to get such a high file system index as shown here in my ROM Topaz Essential. most of us know that if you remove the flreplxfilt.dll in XIP, we can get that high file system index. but it has a side effect that Outlook Notes sync stops working. i found a way out to get high file system performance without Notes Sync issue.

In boot.rgu you can see:

[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"NumDirsToExclude"=dword:f
"DirsToExclude"=multi_sz: "\\mxip_initdb.vol",
"\\mxip_system.vol",
and so on...

just change it to the following:

[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"NumDirsToExclude"=dword:d
"DirsToExclude"=multi_sz: "\\mxip_initdb.vol",
"\\mxip_system.vol",
"\\mxip_notify.vol",
"\\mxip_lang.vol",
"\\cemail.vol",
"\\pim.vol",
"\\Documents and Settings\\",
"\\Program Files\\",
"\\Windows\\",
"\\Application Data\\",
"\\ConnMgr\\",
"\\mxip_swmgmt.vol",
"\\Temp\\"

then cook and see the file system performance :). i've released ROM based on this for a month almost and everything is running fine.

PS: forgot to mention that htcfsfilter.DLL can also be deleted. keep fsreplxfilt.dll and change the boot.rgu as mentioned above.

EDIT: in case you can't see the file system index getting better, please read the posts on 1st page of this thread to check out which other modules can be removed from XIP and its possible that you might not have removed the junk from XIP.
[Windows Mobile Software Development] bobsbbq:
So are you still removing the fsreplxfilt from the XIPKernel?
[Windows Mobile Software Development] CRACING:
Nope, it shouldn't be removed. :)

If removed, the filter doesn't work. In this case fsreplxfilt!

Best Regards
[Windows Mobile Software Development] RoryB:
So, you are basically switching from some of the individual files or folders to the root folders, like \windows instead of \windows\Activesync, etc. Is this correct?
[Windows Mobile Software Development] !Aman!:
no, by doing so i'm disabling the Replication of unnecessary files/system files coz we only need to sync files from My Documents folder.