yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] letama:
I think I get it now. Thanks a lot for this very detailed explanation. So I guess the Phy Address tab in XipPortTools is not the same as Physical Layout in flash?

In my previous trial, I tried to edit files to move boot.hv/boot.rgu. As files are not covered by XipAddrTools, I assumed it was the right way.

I need to meditate this, experiment and maybe do a little drawing, far too much addresses for my poor head :)

Thanks again!
[Windows Mobile Software Development] ervius:
why do you spend time with XipAddrTools???
[Windows Mobile Software Development] letama:
Hi Ervius!

Well, mostly to learn and understand more about the architecture of windows mobile, and also because XipPorterEx doesn't work for me with this one.

Should I not ?
[Windows Mobile Software Development] ervius:
yes, shurelly, I thinked about an easyer way to have a working xip ;), well done then......
[Windows Mobile Software Development] d_train:
The link for Ervius's Payload Reducer doesn't work, does anyone have a link I can download it from?

Thanks

DT
[Windows Mobile Software Development] KMFM$:
Go to the Diamond ROM section and check out his visual kitchen post. I know that the payload reducer is in that kitchen; however, I'm not 100% if he has a new link for strictly the payload reducer.
[Windows Mobile Software Development] d_train:
Thanks

got it now

DT
[Windows Mobile Software Development] ivanmmj:
Sorry for not responding earlier.

Unfortunately, I had reversed engineered the process from someone else and released a ROM that used LZX compression but for some reason I have been having problems since then recreating the process.

I want to help figure it out here right now.

The speed difference is minimal.

Agreed. The Herald which I cook for has the same CPU as the Wizard. The speed difference is not noticeable in real life.

The little that I remember doing (it was a long time ago) was replacing the cecompr.dll with a LZX compatible one then since I had problems getting my own imgfs.bin convert to LZX, I used the imgfs.bin from an os.nb that another cook created in LZX. He seems to know how to do the process correctly, but unfortunately, he doesn't speak english well.

Maybe we can pool all our information together. I'll use my herald to test our theories and then we can finally get the information published officially.
[Windows Mobile Software Development] ivanmmj:
I found some more information on the subject but it's hard to understand the google translation.

Here is the original page: http://bbs.cnsmartphone.com/thread-448576-1-1.html

Here is the google translated page: http://translate.google.com/transla...448576-1-1.html&sl=auto&tl=en&history_state0=
[Windows Mobile Software Development] Kenzneth:
i was reported xip section does not fit

what can i do to solve it?

iam using bepe kitchen

thanks!!
[Windows Mobile Software Development] FormerPalmOS:
Assuming this error refers to fitting the XIP into the allocated RAM space:

First, look for things that can be removed from the phone completely. In the CDMA Touch Pro stock XIP there is a hard disk driver (hd.dll) and a debugger (osaxst0.dll) and an extra splash screen (bmui.nb0). Removing all of these saves about 680KB.

Second, check the romhdr.txt to see if physlast = ulRAMStart-1. For example I have ulRAMStart = 0x802C8000 and physlast = 0x802C7FFF. You can easily increase physlast up to ulRAMStart-1 and try to re-build. If that doesn't give you enough space then you will need to relocate the RAM for the kernel (nk.exe) and correspondingly move ulRAMFree, ulRAMStart and physlast. You can read in this thread how to move nk.exe

Now - if the error refers to fitting in the allocated flash partition, you can re-size the partition but typically have to do so in a full track increment. That isn't too hard to do and xipporterex will do this for you.
[Windows Mobile Software Development] Nixeus:
Hi,

I have difficulties to find the last build of xipporterex, have you a link please?

Thanks a lot :)

regards,

Nixeus
[Windows Mobile Software Development] ivanmmj:
I still can't get LZX to work. :/
[Windows Mobile Software Development] ivanmmj:
OK, I got it figured out. I was able to finally build a ROM with LZX compression and it runs very well, I may add. I'll post the details tomorrow. I'm going to sleep for now.
[Windows Mobile Software Development] utak3r:
AFAIR there're versions somewhere ;) which support both algorithms...
[Windows Mobile Software Development] ivanmmj:
I'd love to find one. I've heard of it but haven't actually seen it.
[Windows Mobile Software Development] itje:
dam I just succeded porting this sucker using this guide, thx ameet.
[Windows Mobile Software Development] utak3r:
6.0.22193??... :eek: what's that build? From what? Where?...
[Windows Mobile Software Development] ivanmmj:
You gotta share this one! hehe

Long time no see, itje!

Is this a real build? :p I found a few references to this and a newer version but I wonder how real they are.
[Windows Mobile Software Development] itje:
heh......when thinking of the date I posted this...uhmmm :D
[Windows Mobile Software Development] xda2_haseeb:
Can i have some screenshots of this WM7 of urs??
[Windows Mobile Software Development] ivanmmj:
Doh! I fell for it. :p
[Windows Mobile Software Development] Nokser:
WOW this is fake???
[Windows Mobile Software Development] utak3r:
April 1st? ;)
[Windows Mobile Software Development] CRACING:
Hello everyone,

Can anybody plz help me....... :o

I have released more then 20 ROM's for wizard and since from starting I have memory leaking issue. Now I feel its due to xip porting inwhich I was porting wrong or not sure but no problem in booting the os.

Is just a copy post work to port XIP or there is more to do?

Because eveytime ( in bepe's platform rebuilder ) I use to remove the OEMXIPKERNEL ( except MSXIPKernel and MSXIPKernelLTK ) in doner XIP dir; Place the wizard's OEMXIPKERNEL in XIP dir and more the XIP dir to ROM dir in my kitchen and the ROM use to work prefectly, except memory leaking.

Is this the correct way I'm doing or there is more to do and what about this.

Here is a compare bitween my ROM's and wizflo ROM's.

Atleast advice plz. I'm fully confused. :(

Thanks a advance.
[Windows Mobile Software Development] Ameet:
hi cracing. i can help with the manual porting but not with the memory leak issue. maybe xip is not the only thing related to memory leaks. will surely update the tutorials once i get me hands on that info too :D
[Windows Mobile Software Development] CRACING:
Thanks a lot.
[Windows Mobile Software Development] CRACING:
Hello everyone,

Anyhelp for me please :o .......... Waiting for Ameet too :( .................

Thanks in advance
[Windows Mobile Software Development] ivanmmj:
I think it may more likely be either a program you cook into your ROMs or a registry hack (like the one that cache's your SD card.)
[Windows Mobile Software Development] CRACING:
I don't think so, because if I cook a clean ROM and I face the same issues. As showed here

I'm very much sure that its due to XIP and not in the others.

Thanks for the reply
[Windows Mobile Software Development] spocky12:
I think I found out why. This is related to BootPhase key in boot.rgu.

According to Microsoft,

If this value is 0, then related filesystem is loaded prior to initialization of locale. But for this to work, the filesystem has to be loaded in Autoload key, like this :

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\FLASHDRV]
"DriverPath"="Drivers\\BuiltIn\\FLASHDRV"
"LoadFlags"=dword:1
"Order"=dword:0
"MountAsRoot"=dword:1
"MountAsBootable"=dword:1
"BootPhase"=dword:0

With this, autoload will regsiter access to the imgfs filesystem before wince.nls is loaded. Then, when it'll be required, if it's not present in xip, it should be found in imgfs.

I think it should work, but unfortulately, I can't tell for sure because on ks20, MSFlash driver (which is equivalent to htc Flashdrv) won't load in autoload (it seems that the driver has to handle this autoload feature in some way for this to work).
[Windows Mobile Software Development] ivanmmj:
Out of curiosity, take your sd card out for a day and tell me if the memory leak is still there.
[Windows Mobile Software Development] CRACING:
but this won't happens in wizflo rom? I have the sd card in and the memory don't leak.

Anyway, I will try for sure. :)

Thanks and regards
[Windows Mobile Software Development] ivanmmj:
I know, it used to happen in my ROMs with the memory card in. Now it doesn't. I fixed it. I'm wondering if it's the same issue.
[Windows Mobile Software Development] Ameet:
Hi spocky. Just flashed my ROM with this setting in boot.rgu :) and it truly works a charm :D

This may prove really really helpful for everyone hungry to save more space in the XIP :) Gained about 290kb in the prog mem

Thanks thanks thanks again and again :) Your post is surely going to the first post :)
[Windows Mobile Software Development] spocky12:
I'm glad to help improving this thread where I learned so much. Thanks to you and whoever is sharing knowledge here.

Btw, I may have a question : I've tried relocating nk.exe without success, but I'm not sure I made it correctly.

Here's a part of my working xip map:

....
802bb674 - 802bc89c L00001228 filedata b00d0fcf-0459-5ea5-d217-f50a2e1ce607.dsm
802bc89c - 802de89c L00022000 NUL
802de89c - 802de89c L00000000 End: highest physical address

802de89c - 802df000 L00000764 NUL

802df000 - 802df000 L00000000 Start: start of RAM
802df000 - 802e0000 L00001000 initialized data of region_4 nk.exe
802e0000 - 802e6000 L00006000 uninitialized data of region_1 nk.exe
802e6000 - 8030a000 L00024000 initialized data of region_2 nk.exe
8030a000 - 8030b000 L00001000 initialized data of region_5 nk.exe
8030b000 - 8030b000 L00000000 ------ start of RAM free space
8030b000 - 86400000 L060f5000 NUL
86400000 - 86400000 L00000000 End: end of RAM

Here's what I've done :

- Changed Physlast from 802DE89C to 802BC89C

- Changed Ramstart from 802DF000 to 802BD000 (=22000 before)

- Opened nk module in mreolc'nk, it gave 802E0000 as current address (=region1 address). Tried to change to 802BE000 but clicking on doit displayed "802BD000" so I changed it to 802BF000 so that it finally shows 802BE000.

- Edited nk.exe\imageinfo.txt to remove "22000" to parts 1, 2 4 and 5 (in o32[x].o32_realaddr).

- rebuilt rom (with xipport) (no errors in generated map)

Am I missing something ?
[Windows Mobile Software Development] Ameet:
1st editing the imageinfo.txt doesnt do anything. That file is only used by XIPPort.exe for reading the values and calculating the P alloc. In fact I have deleted those files in my ROMs since long

I'll try and explain in color coding, maybe someone else could also share a few bits :)

RAMStart is still showing 802DF000 (you mentioned you changed it to 802DF000)

The region_1 of nk.exe is showing 802E0000 (you mentioned 802BE000)

It wont work if you select 802BE000 for region_1 of nk.exe since the address will begin from before the RAMStart address (802DF000) changing it to 802BE000 wont work either since it has to be an address after the RAMStart (802DF000)

I could be wrong but I think all regions of nk.exe are to be aligned in serial order (yours are seen as region_4 is 1st then region_1 and so on)

If needed post your nk.exe, ROMHDR.txt and MAP.txt files so we can take a look at it :) or better yet post your XIP.bin

Really sorry for the delay in reply, also this check might take time since I am travelling right now and cant access the cooking tools from office laptop :(
[Windows Mobile Software Development] Ameet:
I'm really really sorry spocky.. Never ported for this device so I may sound a bit off. But I do insist you to post your XIP.bin so we can try our hands on it too :D It'll be great to post a XIP porting tutorial for this device too :)
[Windows Mobile Software Development] spocky12:
Hi Ameet, and thanks again for your help.

I've uploaded my xip (it's not the same addresses I was talking about in previous post, but I know for sure it's a stable one).

Please note that I never had problems porting xips (I've done this countless times for 1 year), no problems optimizing them by changing romhrd.txt (procedure is exactly the same for ks20 than for htc devices), the only thing I can't manage to do i relocating nk (thus, preventing me from gaining a little more ram), so if you can find a way to do so and keep the ks20 bootable (and why not, also put nk region in the right order), I'm really interested.
[Windows Mobile Software Development] ADB100:
G'Reloc and the values to use for a Kaiser?

I have been using G'Reloc to relocate modules in my Kaiser kitchen, however I have just been using the default values that come up:

Slot 0: 01F90000
Slot 1: 03DD0000
Size of rom: 83400000
Unknown: 00000000

Is this correct for a Kaiser ROM.

The version of G'Reloc says 'v1 beta' is this the latest and are there any known bugs in this version?

I have some odd issues when certain packages are re-moduled and cooked in - the applications works but a couple of other applications seem to act weirdly and all I can put it down to are these other packages that have been re-moduled.

Thanks

Andy
[Windows Mobile Software Development] DaveShaw:
Andy, I'm moving this to Ameet's ultimate porting thread hoping you'll get a bit better coverage.

Ta

Dave
[Windows Mobile Software Development] CRACING:
Hello,

Been removed memory card since many days but still same problem. Those backend exe's ( services.exe, shell32.exe, gwes.exe, device.exe ) are taking doubled the memory when compared to wizflo or svi's roms or any other roms. :(

Thanks and regards
[Windows Mobile Software Development] Quarx:
Hello,

I have read a lot of manuals, but did not understand how to port XIP: (

Please help us to port the XIP for RoverPC P7

Original WM6.1 (19208) http://ifolder.ru/11661858

Donor: WM 6.5 (21501) http://ifolder.ru/11661834

Thanks in advance:)
[Windows Mobile Software Development] Ameet:
Which part did you not understand? :) Never worked on that device so wouldnt wanna get my hands dirty with a bricked device :D Sorry brother
[Windows Mobile Software Development] Quarx:
I ported through the XIP-Kitchen (XIP_AutoPort), the OS is loaded successfully and works fine, but the driver does not work .... to the camera, SD, audio ..

The problem is related to exactly XIP ...

Where could be wrong?
[Windows Mobile Software Development] CRACING:
I think its not related to xip but may be missing drivers in oemdrivers.
[Windows Mobile Software Development] Quarx:
It is in XIP, because if the WM6.5 firmware, I pasted the original XIP, all very much askew works, but all drivers have to work!
[Windows Mobile Software Development] Ameet:
This thread's been a lil less updated from some days. Adding to the fun in learning, I'll be starting to add a few more tutorial, not for porting (as and when updated with more info though) but for editing and understanding Manila files and LUA scripting :D

Updated the 1st post currently as a head start with a few links to learning threads. Will be adding more posts in between after porting posts with this new tutorials / guides :)

Would appreciate and will be of great help in growing this thread if you all could post all the info that you may have about this new stuff :)
[Windows Mobile Software Development] ivanmmj:
I gotta remember to post everything that's needed to make a kitchen LZX compatible.

At the moment, I'm working on released modded kitchens for all devices that support both compressions.
[Windows Mobile Software Development] Ameet:
I'm still waiting to make that tutorial with you for the LZX compression :D
[Windows Mobile Software Development] ivanmmj:
Do you want the "diy" understand what happened version? Or the scripts that I prepared do it for you version? lol I suppose that this thread is about understanding, so diy would be best, wouldn't it?
[Windows Mobile Software Development] coolsac32:
does anyone know how to port an xip using the xipporterex tool. it looks like it can do some tight things but i couldnt find a tutorial for it. im trying to use da_gs new 5.1 kitchen and i need help porting and xip. if anyone can help i would be greatful.
[Windows Mobile Software Development] anryl:
i'm still waiting :cool: is it gona be compatible to kaiser and touch hd ? :rolleyes:

just run the xipporterex select os.nb.payload use old xip extracted select new xip port it and write it to os.nb.payload

for new kitchen platformrebuilder it just ports the MSXIP part to rom folder or from tools u use dumpxip.bat xip_new.bin it creates the XIP where u use only MSXIP part that u create with packagebuilder on dsm file :)

i associated dsm with packagebuilder.exe so just hitting them creates the package :cool:
[Windows Mobile Software Development] utak3r:
of course we want a diy description, not the scripts :D

So... did you find a library supporting both at once? Or are you replacing it?
[Windows Mobile Software Development] ivanmmj:
I already ported a kaiser user's kitchen to it, but strangely enough, the gains weren't very large with his ROM.

No, that's what I'm still trying to do. Right now, it's just either manually replacing the files and hex editing the file. My kitchen modifications so far have actually been to allow the cook to choose either compression when creating a ROM and having the kitchen do the actual replacing of modules and hex editing by itself.

Anyhoo, here's the process (on the next post.)
[Windows Mobile Software Development] ivanmmj:
Making a LZX compressed ROM is very simple.

First, you need a cecompr.dll that supports LZX compression. There are three cecompr.dll's out there. The one supporting XPR, the one supporting LZX and the mythical one supporting both XPR and LZX which I have yet to see. If anyone has this one, PLEASE tell me.

I have attached both the LZX and XPR versions incase you want to go back and forth between them.

After that, the process is simple. First, you stop your kitchen process right after it extracts the imgfs.bin but before it inserts the files into it. (A simple PAUSE in the batch file will suffice). Then open up your imgfs.bin and search for the string "XPR". Replace the FIRST one and FIRST ONE ONLY with "LZX". Save the file, close the hex editor. Let your kitchen do it's thing.

That's it. :p

http://www.4shared.com/file/101370353/b7650aff/Compression.html
[Windows Mobile Software Development] utak3r:
hmmm..... erm..... :D where?

As a side note: I think it would be more convinient to edit os.nb, so you don't have to do it again and again.
[Windows Mobile Software Development] ivanmmj:
ROFL. Yes, it's here now.

I edit the imgfs.bin just because it's easier to batch script into a multicompression kitchen. :p
[Windows Mobile Software Development] utak3r:
ok, if it's automated in the kitchen - then yeah :cool:
[Windows Mobile Software Development] Zecanilis:
Thank you. Working in my love. :D

Just won 10 MB or so in my ROM... :eek:
[Windows Mobile Software Development] Ameet:
Hi ivanmmj. Will check out all the latest posts tomorrow night :) Am travelling right now, will try your compression on my Diamond ROM :)
[Windows Mobile Software Development] CRACING:
Interesting :)

BTW; How to verify that which cecompr.dll file supports LZX or XPR or both?

Edit 1: WOW, This is amazing man. 7.7 MB

However my pc went very slow while cooking but its OK :)

Edit 2: Just now flashed cooked ROM and the ROM is fine mean no problems due compression so the ROM is run normal.

Thanks, Thanks, Thanks, Thanks a lot.
[Windows Mobile Software Development] gguruusa:
Expect an increase in load time due to increase in cpu consumption needed for the decompression. Probably not tremendously noticeable between the two, given the typically tiny file sizes.
[Windows Mobile Software Development] anryl:
thnx its working :cool:

again something checked :D
[Windows Mobile Software Development] utak3r:
it's normal - LZX is thought in such a way you are compressing quite slowly - but decompression is really fast.
[Windows Mobile Software Development] CRACING:
ok thats great!.

However my pc 4 gb ram is on replacement and now I'm using old one thats 1gb so this might cause the problem. Anyway its ok. :D
[Windows Mobile Software Development] xda2_haseeb:
Worked for me :p THNX alot!!
[Windows Mobile Software Development] ivanmmj:
What about adding a section in how to merge extrom's with the main storage for those devices that it's possible with? Maybe it will help other people with other devices (like me) figure out how to do it in their device, if possible.
[Windows Mobile Software Development] CRACING:
Yeah, thats the good idea. Coz I'm sucking around extrom/space. :o
[Windows Mobile Software Development] d_train:
Hi

I have searched, but my searching skills aren't the best :(

Can someone help me to find out how to extract the SYS from an i900's PDA.bin file? I want the SYS version to port it, but can't seem to extract it.

Thanks in advance.

DT
[Windows Mobile Software Development] Ameet:
Hi ivanmmj. I'm using Bepe's kitchen for Diamond ROMs. These are the lines in CreateROM.bat file and I edited the IMGFS-new.bin after the red pause. Right? Coz if I edit the imgfs.bin then the "ImgfsFromDump" tool crashes :( Replaced the dll in XIP too

..\TOOLS\IMGFS\ImgfsFromNb OS.nb.payload imgfs.bin
if not "%errorlevel%"=="0" goto error
..\TOOLS\IMGFS\ImgfsFromDump imgfs.bin imgfs-new.bin
if not "%errorlevel%"=="0" goto error
[COLOR=red][B]echo Edit imgfs-new.bin, if needed for LZX compression[/B][/COLOR]
[B][COLOR=red]pause[/COLOR][/B]
..\TOOLS\IMGFS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb.payload -bigstoragemove
if not "%errorlevel%"=="0" goto error

Ok The right way doesnt work either :( The tool crashes :( I have attached my imgfs.bin before editing, in case if anyone can check what the hell is wrong :(

Would love to add it up, but I dont have a device to test this one out. So you will need to write up a working tutorial bit or provide some info on it and then I'll locate the post the the tutorials ;)
[Windows Mobile Software Development] !Aman!:
try again as i said (in red color in quoted text)... or simply edit the payload if u dont want to mess with the batch files.
[Windows Mobile Software Development] Ameet:
Hey Aman. Good to read from you brother :D What did you say about this compression thing? Found a lot many references to XPR in the payload but found the correct one at the last 1 in the payload :) Is that the one to be edited? Will try again on payload :)
[Windows Mobile Software Development] Ameet:
It crashes there at that point :(

EDIT: The RAM usage reaches about 93% and IMGFSFromDump.exe crashes :( Combined size of my OEM & SYS is around 157MB but I have 4 GB RAM on 3 Ghz PC :( Guess I'll wait till I upgrade my PC more than this to get LZX compression :D
[Windows Mobile Software Development] !Aman!:
:) yeah.. i have had some personal problems of late, getting normal now..

XPR is near the imgfs signature. so u can forget rest of them.
[Windows Mobile Software Development] CRACING:
Ya it happens to me also sometimes and most of time my pc gets too slow and might require force reboot. :(

I have 1GB RAM and AMD 2.2ghz dual core cpu. :o
[Windows Mobile Software Development] ivanmmj:
You want to edit the imgfs.bin not the imgfs-new.bin.

The process does take HUMONGOUS amounts of memory. The tools aren't very efficient with LZX.

As far as merging, it depends on the device. I've seen three different ways. It depends on whether the phone has DOC storage, whether the extrom and the imgfs is on the same partition, etc.

I need more info on my phone to figure it out, but I can't seem to find the information about the Herald's internal storage structure.
[Windows Mobile Software Development] Ameet:
I figured :D Left the LZX compression for now :( Till some kind soul recodes the IMGFSFromDump tools :rolleyes:
[Windows Mobile Software Development] maja:
Same here.... but I did an experiment..I have removed all ext ( only for purpose) and process is finish correct.. in this moment the EXt = 96,2Mb....My PC is a intel quad Q9300 2.5GHz with RAM 4Gb Os windows7 build 7100.
[Windows Mobile Software Development] udK:
The same here, Win7 RC1 onboard.