yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] b16b:
i think you need vm numbers for HERMES is deferent from kaiser
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] indagroove:
Do you know how to get your initials in the sys build number, like the pro chef's do??
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] furb3t:
mbarvian, i have tested your method but, when I input the cmd pgktool dump from dos shell i had win error. Someone have tried this method!?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
if you do this correctly, the build numbers will change ;)

@furb3t: what errors did you get?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] furb3t:
I have understood my error. I haven't put pkgcommon.dll into the same dir of pkgtool.exe . Now cmd goes, but into dir \dump I haven't a dir \Sys but only all files (.Vm and .Rom after cmd there aren't)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] schizo:
Gee, not many people wanted to share their secret recipes nowadays. My utmost salute for you mb... i always appreciate that kind of spirit highly.

Now,what i need is time to cook, oh well...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
thank you for bringing that to my attention. I just updated the instructions with the newer, easier PackageTool
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
You'll need to manually edit the d0b41563-b345-4444-aa15-986e7c7fff99.dsm file in SYS\OS.

That is, if I am reading your post correctly. You want the about screen to show something similar to the following, correct?

CE OS 5.2.20755 (Build 20755.1.4.0 Groove Edition)

as opposed to the standard

CE OS 5.2.20755 (Build 20755.1.4.0)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Are you sure about that?

How do you manual edit a .dsm?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Sorry about that, Laurentius26. I meant "hex edit" opposed to "manually edit". I can see where that would cause confusion.

There is another discussion that deals more with this:

http://xdaforums.com/showthread.php?t=409845&page=3

(As you probably already know, Laurentius26. ;) )
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Haha... that's exactly what I needed and didn't know yet. :D

Thank you!

Grtz,

Leo :)

Edit: and this is not to fake CE OS version because I ported whole Opal OEM. ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ttran001:
create a new oem package or if you already have one add the lines under the "Example section to your oem package's rgu file.

Example of creating a new oem package:

1. Create a new folder called test.

2. Go to UUID (GUID) Generator.

3. Create two new files using your new UUID )GUID) name with the following ext.

9825f420-9d33-11dd-ad8b-0800200c9a66.dsm

9825f420-9d33-11dd-ad8b-0800200c9a66.rgu

4. Edit your 9825f420-9d33-11dd-ad8b-0800200c9a66.rgu file.

5. Add the following lines to your 9825f420-9d33-11dd-ad8b-0800200c9a66.rgu file.

Example:

REGEDIT4

[HKEY_LOCAL_MACHINE\System\Versions]

"Aku"=" By indagroove"

Make sure you leave a blank line after the "Aku"=" By indagroove".

6. Save, add to your oem folder and cook away.

Enjoy,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
@Ttran001

Great work, let me contribute the package. :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ttran001:
No problem and thanks for posting the package.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
EXCELLENT!!! This is a LOT easier to manage than hex editing the .dsm. Thanks for the info, ttran001!! :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Ameet:
Now that is what i am more interested in knowing :D I'm kind of new Diamond user and new to the world of porting XIPs without the BuildXIP.exe and Insert.exe tools :( So am waiting for you to post your manual XIP porting tut so I can then cook me a nice tasty Diamond ROM ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] b16b:
can give us the XIP tutorial?

thanks Great Job!!!!!;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
I'm still trying to figure out the XIP tutorial myself :)

If anyone knows how to do it then please PM me
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Possibly the steps in the links below are applicable to porting to our Kaisers:

http://xdaforums.com/showthread.php?t=395526&page=2

http://xdaforums.com/showthread.php?p=2263351

Hopefully, I get a chance to try those out in a couple of days.

Also, I found this while searching. Maybe someone here can test it out and post a little more concise instructions.

http://xdaforums.com/showthread.php?t=390222
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] firaX:
you sure the higher numbers automatically mean newer builds? As far as i saw, each HTC device (and also others running WM) seem to have their own range. Kaiser 19212, Opal 197xx, Something else was 20XXX. It seems at least part of the build number indicates the device it is meant for. Opal is fairly new right? Yet its build number is 197xxx, while 20xxx was out weeks before that.

This is of course based on pure logic, nothing else hehe.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
Makes sense. I was actually wondering the same.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
I THINK : it doesnt matter but the never build NO: have always something new like IE its from 20755 new version in OS but nobody actualy ported it - OPERA better :cool: the XIP always new drivers some changes so some xip's are running faster as i know from my slow hermes :D some xip are better memory .

DONT cry here about numbers the xip port second post should be finished soon :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
If anyone hasn't noticed, Ameet (ababrekar) has created a manual full xip porting guide here. I haven't tried it yet but it looks as if it should work for our kaisers. Thanks ababrekar!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
sure he created it after this thread was done and i did succesfuly ported kaiser xip yesterday so we are sure working everybody on the same thing .

the guide its already on the net from chinies translated on htcgeeks

but we still need it for kaiser tested as i was working on it the last week as i did get my kaiser .

SORRY if nobody yet was able to put the guide here -------- now will be 2 threads about it .:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
So which guide did you use to fully port a xip?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Ameet:
It wil work for Kaisers too since even this device is not supported by buildxip tool

There wont be double threads since my guide is based off on a full port to be done manually. Since the HTCGeeks Wiki, by Lennysh, was a translate from CHS version, few things got lost in between :) Like I mentioned few threads here talk of replacing the dsm while a few talk of replacing the coredll.dll. Mine is related not only for numbers but a full port ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
what do u think i am doing the whole time i am full porting xip with XIPAdrrTOOL -- this means realoc all adresses as u know

-- modify the size of ram the start of free ram ( wont boot if u move the nk from 31 ) and so on

i NEVER partialy ported XIP always the FULL MS ( shi+ ) :D

i was manualy porting for hermes first few months ago but then found bepe buildxip which is not working here so returned to full relocking remapping play :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] crazyC:
OK - anyone who understood the last page of posts, could you please explain and summarize for those with less knowledge to start off with.

MBarvian's first post was an excellent example of breaking it down for the less technologically advanced amongst us.

Cheers
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
i wont post it y'al have to wait for mbarvian's guide

he got to get used to it then he will post the guide :cool:

actualy everything's working as they posted in the hacking-dev thread just i'm using xipaddresstool and the chineese guide

is the right way + abusalzas removing not needed files .

Just need if there is some rom with much more memory then usual to hack his xip freeram mapping :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
Ok I do have one question. I downloaded the 20759 SYS but it is Chinese 0804 and I need 0409. I do need to convert this right? If so can anyone point me into the right direction for instructions on how to do this? I have looked around but haven't came up with anything yet. Thanks in advance.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
wow, these new multi-quotes are NICE :)

Again, as soon as I can fully comprehend it, I will post a tutorial

I believe you can just replace it with the 0409 file from an English ROM
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
Is that how you go about doing it? Not sure if you had to or not for your 20755 sys in your solace rom or not. Or was that already 0409?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
u get every directory 0804 replace with 0409 all files from the best build u can get so 20759 804 - 409 from 20755 last nike kitchen fixed translated new muis

then u have to compare all rgu's for chinese symbols and change to eng. or if not different just replace rgu . thats all :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
Thanks Anryl.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Well, I'm going through the steps and think I'm starting to get the hang of it. If I complete a successful full XIP port, I'll PM you my steps and then maybe you can turn that into a nice guide.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] b16b:
thanks KMFM for your Help ;)

we waiting the guide

-EDIT-

I want the same PM :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
thanks man, that would really be helpful :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] yardie.spike:
Awesome Tutorial Bro!

Definately the easiest to follow, at last someone has written it in plain English!!! Looking forward to your XIP tutorial.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] b16b:
we waiting the xip tutorial we have something new?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Actually, I should have it completed here in a few minutes (maybe 30min or so). I'm simply reusing ababrekar's guide and simplifying the terminology. Some things will be out of the scope of this guide and can be simply looked up at the original thread.

So, expect the tutorial soon. :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] b16b:
you are great :eek:

keep walking

i waiting for this..

i try also to fix the 209xx sys and xip is not first time for you :p
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
[MANUAL] XIP Porting for Kaiser, Part 2

Putting it all back together

======================

Now click “build xip_out.bin” to create the resulting XIP to be inserted into the ROM .payload file (xip_out.bin).

Now with the BASE 'OS.nb.payload' file in the same folder as XIPPort and the xip_out.bin, replace the name “nk.nb” with “OS.nb.payload” and the address to “00320000” all without quotes in the fields at the bottom of XIPPort and press "write xip_out.bin to:".

Now to create the 'OS.nb' with the new XIP for use in a kitchen's ROM folder, open a command line and type:

nbmerge.exe –kaiser OS.nb

Now put this 'OS.nb' file in the 'ROM' folder of you kitchen, put the BASE ROM's 'boot.rgu' into the '\ROM\XIP' folder and do not include any of the 'OEMXipKernel' or 'MSXipKernel' folders in the 'OEM' or 'SYS' folders while cooking.

Cook the new ROM with your favorite kitchen (whichever doesn’t do anything with the 'XIP') and use this 'OS.nb' file as base template for the ROM with the new XIP.

***IMP: For the ROM to function properly after boot, you need to either have:

XIP & SYS of the same builds, or

XIP and the OS\Gwes.exe and \Base_Lang_0XXX\Gwes.exe.0xxx.mui files from same build***

With this note, I hope this guide will serve many as a guiding light and answer many questions on manual full XIP porting. Happy porting.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Guide Credits

First and foremost, give all credit, thanks, praise, and donations to ababrekar who took the time and tenacity to poke all the Master Chef's to ask how this is done. :D

Secondly, this write up is ababrekar's guide taken and slightly modified for simplicity and specifically for our Kaiser's. I am in no way wanting or attempting to take any credit for this guide. Remember everyone, this was ababrekar's undertaking and his good will to share this knowledge with the rest of the community. This is how XDA-Developers should be. I, for one, am greatful beyond expression for this guide; for I have been failing at XIP for a long time.

Also, let's not forget the others involved in monumental project as well. Cmonex, htctouchp, Abusalza, Noonski, and the others named in the original thread. With teamwork a and willingness to help, these guys (and gals ;)) have exemplified the spirit of this community.

So... THANKS!!!! To everyone who made this possible.

----

For further discussion and queries into the specifics of XIP porting (or to just give thanks), please check out the original thread:

http://xdaforums.com/showthread.php?t=438676
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DupinBJK:
And many thanks as well to you for this great post, KMFM$. :)

BJK
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kendzlic:
Awesome, thanks KMFM$. This should be a sticky.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
No problem, but also thank ababrekar. Also, this is already a sticky at the top of the Dev & Hacking Forum, so I think it would be kind of redundant (though I know this is more specific to the Kaiser and could get lost in the other threads).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mbarvian:
thanks for this one man, I finally just ported the Opal build and the HD build :)

Where's the SYS tutorial? :)

thanks again for wrapping it all together
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
You have already taken care of the SYS tutorial, mbarvian. It works flawlessly for me. ;)

Also, per specification of the main (Dev & Hacking) XIP port post; I recommend (as well as all of the chiefs (cmonex, htctouchp, etc.) that you use insert.exe instead of XIPPort to import the xip_out.bin back into OS.nb. It has been found that using XIPPort to import the xip_out.bin is sometimes "buggy". If you download the porting tools from the dev & hacking post, insert.exe is in there.

Also, you will need M$ VC++ 2008 redistributable for insert.exe to work. One last note, to find the imgfs offset use imgfsfromnb.exe to dump the os.nb. On the CLI screen you will see text that says "imgfs start 0x00320000 end 0x006c0000. Imgfs offset 0x00700000". You want to use the "Imgfs offset 0x00700000" as your value. :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
I have the same problem. I succesfully ported xip 20924 to my kaiser using the original SYS...but when I use exact same xip with ported 20924 SYS It won't boot.

I tried replacing original .VM / .ROM / METADATA and used G'Reloc to relocate files. It still won't boot...

Ideas someone?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Make sure that wince.nls in the ROM\XIP folder, or that you have WINCENLS_WWE folder in your SYS directory.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
I have done that. Is het best to use new nls file or old one?

Other suggestions?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KMFM$:
Use the wince.nls that comes with your base rom just to be safe.

Also, you say that the XIP is working with your base rom's SYS, correct? That should narrow down the problem. Set your successfuly XIP port aside and test your SYS port with your base rom's XIP.

With the 20924 SYS, did you remove any modules? What values did you use when you G'Reloced?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
I use the following values:

G-Reloc:
Slot 0: 01F90000
Slot 1: 03DD0000
Size of Rom: 8340000
Unknown: 0000000

I will start from crap again to see what I did wrong.

Does SYS have to be compatible with XIP. Some people mention that. Or can you use every working (ported) XIP with any working (ported) SYS?

p.s. The 20924 XIP I succesfully ported from a touch pro 20924 rom appears to be a 20758...:(

Trying again with a genuine 20924 xip but can not get it to boot for now... even not with my 'old' sys, hense the question above...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Ameet:
Any build XIP can be combined with any build SYS and anything else. Thats the fun and talent of cooking ROMs :D

This is actually required for VGA screens that you need to have the same build XIP and the same build Gwes.exe, Gwes.exe.xxxx.mui but you can keep this combo just for a safer side :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Thnx!

Can you take a look at the following xip.bin. It's based on kaiser shipped xip but I ported the mskernel and mskerneltk from 20924 XIP like in you manual porting guide. I realocated all neccesary files in 032 and e32 adresses as needed (was a big mess....) but after 2 hours I was done....no more !!!!!!!!!

Then I used insert.exe to merge it in os.nb.payload and build the rom. I used the shipped SYS. But when booting it shows the red version numbers and is stuck there (I hard reset before and after flashing..)

Damn this is more tricky than I thought. I did however succesfully port 20758 xip the exact same way....:confused:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Ameet:
I've had a lot people report the 20924 XIP having problems in porting. 1 suggestion is to check the RAM space, if it has the nk.exe (region_1 & 2) listed. If its there and device still wont boot, then there might be a problem with the XIP. I feel so since the one posted in Elf forum (I presume, you got it from there) has been optimised for use on Elves. I'll up my 20924 xip.bin somewhere, coz I am using the full port of this build (SYS & XIP) since it was found

Another suggestion is to check if the ported xip has the wince folder. I found if you remove it from xip & add it to sys to save space then the device doesnt boot

Have you modified the dllfirst, dlllast, physfirst & physlast values? If yes then I advice keep them the original and try. Just for a safer check, try extracting your original xip and build the xip_out.bin from it unedited and re insert and flash. If that works then there's some problem with the xip.bin or the porting ways
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Thnx Againg for the very quick reply!!

Did it and it has the 2 regions...

Yep got it there...but all device specific info is stored in oemkernel as I recall or did they change more?

Anyway, are there other sources for usable XIP and SYS 20924? Can you post/pm me a link so I can continue my quest in porting XIP/SYS?

I got it from the elf forum and looked at the chinese sites....

did not touch it....

Also did not touch those...:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Ameet:
Hmm. I'll post the working xip.bin based on which I ported mine and you can try on that one ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
okay, here's the deal....

I'm getting to the source of my headaches, trying to port XIP on my kaiser but I need help:

Fisrt I used the EXACT same ingredients:

I took the same working os.nb

I used nbsplit -kaiser os.nb to create os.nb.extra/os.nb.payload (did this same proces each try)

I exctracted xip.bin (3096 kB) with kitchen from same os.nb and renamed to xip_out.bin

I tried merging xip_out into payload file on different ways (then rebuild rom and flashed):

1) insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 -s 0x004C0000 ---> not booting

2) insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 -s 0x006C0000 ---> not booting

3) insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 -s 0x00700000 ---> not booting

4) xipport (to os.nb.payload at adres 00320000) ---> booting !!

5) insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 ---> booting !!

Then I changed xip_out with a WORKING 20924 one which I extracted the same way a before from a kaiser 20924 build rom.

This new xip-out.bin is a bit smaller (2821 kB) then the original one used above.

merging again:

4) xipport (to os.nb.payload at adres 00320000) ---> not booting

5) insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 ---> not booting

My guess is that by replacing the larger xip with a smaller one, a part of the payload will not be rewritten and that keeps some bits from the original xip. That is maybe causing the boot issue.

I tried to avoid that by using insert.exe with the -s values (see above). but that did not even work for the original xip....I looked at the payload for the offset of the imgfs.bin (0x006C0000).

Anybody has a better -s value (also need one in a few weeks for the raphael by the way;)).

Or does anybody have a another (fail-prove) way to merge a different xip to a payload??

Thanks a million for help guys, this is really beginning to be a big pain in the *ss!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
Xip insert . BAT

del os.nb.payload
copy os.nb.payload.org os.nb.payload
insert -i xip_out.bin -o OS.nb.payload -d 0x00320000 [U][SIZE="5"][B]-s 0x003DFFFF[/B][/SIZE][/U]
nbmerge -kaiser os.nb -conservative
pause
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Will give it a go tonight! Thanks!

by the way how did you know which value to use for the -s? I'm still learning... And my touch pro is waiting for me at home. So I want to figure out the -s value for the touch pro too.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
with hexeditor u know where the xip starts and where the imgfs starts so if u extract xip then u know the size :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Thnx Man, but it does not work. Not even with the original xip.bin But when I remove the -s value the original one boots but the ported one does not...

I tried the hexedit way before but then your value would be way too small:

0x003DFFFF - 0x00320000 = 0x00BFFFF = 768 kB

768 kB is way smaller then a xip.bin which my smallest is 2.821 kB

So that won't fit...

Thnks for the effort.

More suggestions people or does the porting work with all you guys?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
:confused: -s > size off xip to insert

0x00320000 + 0x003DFFFF = size to be inserted from adress

0x00320000 to adress 0x006FFFFF

IMGFS usualy starts at 0x00700000 if u use original os.nb.payload

:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Ok, I got it all wrong then...my bad! Why do you use that value anyway?

And why won't my rom boot even if i use the value.... I really do not know what I'm doing wrong.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] anryl:
dont know what are u porting what modules and so on .

get working xip and sys from here and compare what is different . this is my 20924 ported xip sys and oem working .:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] merten3000:
Thnx a million again... will give it another try.

But I still don't get it:

I use a kaiser original 19012 SYS and extracted a WORKING kaiser 20924 XIP. And no way I get those two to work...:(

I will try yours but want to learn porting myself...but again thnx for all the effort. I'll keep you posted!!

EDIT: used your xip and again no luck. I took a look at my os.nb and my imgfs starts at 0x006c0000.

So 0x00320000 + 0x0039FFFF = 0x006bffff

but even if I use -s 0x0039FFFF no booting.... without -s no booting...

But if I do not change a thing or put back original xip (without -s) it boots. Could it be something with m os.nb (but it does boot unchanged...?)

I am pulling my hair out!!