yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] c_shekhar:
I beg to disagree from you here.

The basic purpose of this forum is to enhance, improve and share the knowledge. By nature most of us are a kind of hackers who ripps new features from other devices and put into our old devices. We lay hands on new builds from M$ and try them on our devices before any official release takes place. Therefore, we dont need to protect our work at all. We want others to improve whatever we release and thats how chain of improvisation goes on. If you visit the Polaris Forum you shall find 80% guys are releasing unprotected ROMs. And I feel proud to be a member of such a sub-forum.

So IMHO, to continue a healthy and co-operating environment we must shun the protection system, At least on this great forum.

You are a great developer, we all know. You can definitely find ways to keep intact the DSMs and RGUs.
[Windows Mobile Software Development] ervius:
you don't have to tell about it with me, the tools are all by "bepe", you have to tell with him, about, for me, is better, and thank him for all that he produces for all us.
[Windows Mobile Software Development] ervius:
visual rom beta1 released (with also all rom\ structures to respect to can use the visual kitchen!)

here:

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

try and report...

bye!
[Windows Mobile Software Development] Bxsteez:
Can someone help me out. Everytime i try and use this program i get an error saying that it could not find part of "XipporterEx_1_2_Revision_35\MYTOOLS\xip.bin_out\xip.'"

Everything that is needed is in the folder. I followed the tutorial exactly and i keep getting this error. Is there something i'm doing wrong
[Windows Mobile Software Development] texture:
I have same error...all works fine if i return to the revision 32 of XIPPorterEX
[Windows Mobile Software Development] Bxsteez:
Do you know where i can get revision 32 from?
[Windows Mobile Software Development] texture:
Only exe rev. 32 of XIPPorter:

http://rapidshare.com/files/178946533/XipporterEx_revision_32_only_exe.zip
[Windows Mobile Software Development] Bxsteez:
This doesn't seem to work either. I get a different error saying "The system cannont find the file specified" once i open the program. And when i try and port the xip i get the same error and it just hangs.
[Windows Mobile Software Development] ervius:
try at my own page....

http://ervius.altervista.org/others/index.html

I posted also xipporterex with "old way"!, old tools, xipport.exe and etc....

bye!!!
[Windows Mobile Software Development] Ameet:
You have to rename the resulting xip_out.bin in the ported XIP folder to xip.bin ;) try it and check

@Ervius. Any way you can make the tool auto rename the final xip_out.bin to xip.bin?
[Windows Mobile Software Development] texture:
Same problem,when i click on Port it a messagge inform the platformrebuilder is used,click ok then have an error "Could not find a part of path...." appear.

The old way (on your site there is rev. 32) function at all.
[Windows Mobile Software Development] CRACING:
Hello,

I also got the same problem and also got the solution. The problem is due to v-i-s-t-a which is not supported by the XipporterEx 1.2 Revision 35. I have dual OS in X-P, it works fine but in V-i-s-t-a it give this type of error.;)

Thanking You
[Windows Mobile Software Development] Bxsteez:
I was using it under XP and had the same issue but when i used the old tools it seemed to work great.
[Windows Mobile Software Development] ervius:
http://rapidshare.com/files/183089278/XipporterEx_1_2_Revision_37.zip

try this other one, and remember it works only with:

.NET framework 2.0 and vc++ 2005/2008 Redist installed!
[Windows Mobile Software Development] texture:
Now there is another type of error:

I'm loading XIP-old,XIP-new and payload file to properly folders,click on Port IT,a messagge appear " Xipkernel's DSM not found! I'll create new...",then I have this error "Could not find a part of path....\mytools\xipbin_old\xip\723fb954-d931-4348-b672-82a188e587b5.dsm"

but this dsm file is present on my XIP folder.

I have installed .net 2.0 and vc++ 2008 on my pc,i use XP Pro SP3 and i try to use your tool on Touch HD rom.
[Windows Mobile Software Development] ervius:
no error with and without dsms on xip.....

post me old and new xips.
[Windows Mobile Software Development] texture:
http://rapidshare.de/files/41355813/XIPs.rar.html

Thanks..
[Windows Mobile Software Development] ervius:
only a click to build new xip with this last version...

http://rapidshare.com/files/183089278/XipporterEx_1_2_Revision_37.zip

and xip ported here!

http://rapidshare.com/files/183225245/XIP_new_ported.zip
[Windows Mobile Software Development] texture:
Thanks Ervius

The problem is my PC...i'll investigate...thanks again.
[Windows Mobile Software Development] CRACING:
Hi,

How to change the pagepool?

I changed the pp in XipporterEx and ported to my HTC Wizard but still its 5MB. I wanted to change to 4MB.

Please help.....

Best regards
[Windows Mobile Software Development] anryl:
FOR everybody ALL ERVIUS TOOLS tested ON VISTA 64 AND w7 32 AND w7 64

BY ME so any error not the tools its u did not install all updates and requirements :cool:
[Windows Mobile Software Development] :
anyone know the steps or a good tutorial for a full kernal port?
[Windows Mobile Software Development] Bxsteez:
I would like to know this too. I've read all the tutorials out there but i still have software crashing and i can't compilie anything. My imgfsfromdump crashes everytime i run it. I have no idea why.
[Windows Mobile Software Development] itje:
replace imgfsfromdump with the attached, works for me :)
[Windows Mobile Software Development] Ameet:
meaning? you mean the tutorials on 1st page are not enough? :eek::eek:
[Windows Mobile Software Development] :
what i mean is doing a full kernal, the tutorials you have here are great. but unless i am mistaken. you can not port over the oemxipkernal? or can you. because say you take a 19xxx build, and port over the xip to 21xxx. your kernal is still going to be 19xxx. right?

so is there anyway we can port over the oemxipkernal so we would have a true 21xxx build? or will it not work like that?
[Windows Mobile Software Development] anryl:
OEM - means DEVICE SPECIFIC

MS - means probably Microsoft Specific

HOW WOULD U LIKE ? PORT Ferrari OEM ENGINE TO SAY KIA :D

I THINK THIS SHOULD BE ENOUGH M8
[Windows Mobile Software Development] :
okay, very true, i was just thinking there was some way to port nk.exe. but i guess i was wrong.
[Windows Mobile Software Development] Ameet:
As far as I cook, if the donor ROM is from same device then you can port the whole OEMXip. Like I ported the entire XIP from 2.03 Diamond ROM for my Diamond :)
[Windows Mobile Software Development] omaga:
Hmmm..have you read the first post?! you can find any fuller port than that:rolleyes:

71 pages of the best stuff i ever read in xda forums.
[Windows Mobile Software Development] :
yeah, i was just mistaken, I have ported many xip for the CDMA Titan, Vogue, Diamond and Touch Pro. I mean any OS from 19208-21114. I have all the xip for all of these devices. So i was just mistaken.

This is a very great thread, and very good tutorial on how to port anything you would want. I am glad Ameet created this. and Ervious for his great tools that make all of this 100 times easier.
[Windows Mobile Software Development] Ameet:
Glad to know tutorial was of help brother ;) Credit also goes to all mentioned in first post :D They are the ones coz of who I started with the research :)

Although can you pm me 21114 xip & sys? (if you have, else only gwes.exe :))
[Windows Mobile Software Development] ervius:
hi all.

[BETA 3] of visualkitchen (ITA_WWE_GER based on 2.03 diamond rom!) Is reay to download, with all included, also nbh/nb/payload dumper!!!

bye!!!

here:

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

bye!!!
[Windows Mobile Software Development] anryl:
TOTALY AGREED :cool:
[Windows Mobile Software Development] chavonbravo:
I as well, agree, ervius, it was not my intention to make dumpable roms. Was just a suggestion for someone else. I think if you want a dumpable rom, stick with other kitchens.

A side note, I'm interested in what exactly is done by this new bepe kitchen to modules to prevent them from being dumped and ported to another device, yet they still work fine on original device when flashing. Seems to modify only the last s00x file of module. Do you know how this is done, ervius? or anyone else for that matter.
[Windows Mobile Software Development] Ameet:
Even I'm interested in knowing more on this Ervius :) But only if I can openly document it in this thread as a guide (not that everyone prefers to do that but just for knowledge sharing sake :))
[Windows Mobile Software Development] CRACING:
Hello,

I have ported 21139 XIP/SYS ( WM6.5 ). On the 2nd splash screen some text shows, IPL, SPL, GSM and OS versions. Inwhich the OS version still show 6.1.0.0, Is there anyway to change this to version 6.5.0.0? May be there is some editing in files in XIP but I don't know.

Please help

Thanks and regards
[Windows Mobile Software Development] RideTheTube:
Hi if i choos the old xip.bin the programm wants to overwrite the files and if i choose yes the programm crashs.. And another problem is if i get the xip.bin from payload the old works fine but if i take the new from new xip.bin and want to "port it" the programm crashs again Thanks for help.

NetFramework and everything is installed

Here is a pic:
[Windows Mobile Software Development] FormerPalmOS:
The OS version comes from one of the .DSM files in the SYS folder, not from the XIP. Not sure which one though - potentially SYS\shell...

Have you posted your 21139 XIP anywhere? I just finished optimizing 21109 and 21139 would be my next project, though I'm in no hurry. I want to hear a) that the 21139 is stable and b) see someone with a solid kitchen for VZW Touch Pro phones.

Thx,

FPOS
[Windows Mobile Software Development] CRACING:
Hello,

I have ported 21139 build to htc wizard using source from here and also some help from conflipper.

No, OS version doesn't take from dsm or rgu. I know its from nk.exe (XIP file) but don't know how to edit.

Best regards
[Windows Mobile Software Development] anryl:
second splash its welcomehead.xx.png so dont know what u want to change ?

where ipl spl and rom version not os version as kaiser ROM version 3.29 or 3.57 or 3.65.0.1 :D
[Windows Mobile Software Development] FormerPalmOS:
I re-read your post and realized that you were mentioning a second splash screen that I don't think exists on < 21114. I'm working with 21109 and the only splash screen with any ROM version info (on the Touch Pro - Raphael CDMA) I get is the one loaded during early boot. There is a ROM version shown there in red letters on the lower right corner of the screen - and it DOES get its version info from NK.EXE. The only other places I can see a version are after boot, Settings --> About or Settings --> Device Information. I am fairly sure neither of those get the base OS version from NK.EXE. I recently changed from one SYS version to another, but using the same XIP, and the OS version as displayed on the Settings --> About screen changed.

If you want to edit that early boot info, do a unicode search for the string kernel in NK.EXE and you will find it.

FWIW, other version string sources I know of:

There is a string in the RUU_Signed.nbh that shows in Settings --> Device Information - ROM version.

There is a folder in SYS called OSVER but all it sets is the AKU field (what comes in parentheses after the base version)- not the base version number itself.

Each .DSM file has an OS version string - I'd be surprised if the Device Information screen didn't get it from there.

Have you tried running sysversion.exe on your SYS folder to see which modules report the version number you are trying to change from? Thay may help narrow it down a bit.
[Windows Mobile Software Development] bitserve:
It's kind of ironic, because I reverse engineered what the new bepe kitchen was doing just so that I could dump your ROM.

He's changing the header for each file, and also changing the GUID header of the image itself. I'm surprised that it still functions myself, and it likely won't work if you actually need to relocate a module. I modified imgfstools to work around these mods.

Since no one would share the new iolite ROM, which I planned on porting on my holiday, I had nothing better to do. Anyone wants them, they can be downloaded here:

http://xdaforums.com/showthread.php?t=476034
[Windows Mobile Software Development] CRACING:
Hi,

You are correct. It does not exists on the SYS or the XIP. You know that nk.exe is used for porting. So I am getting the old os version thats 6.1.0.0.

There is OS version in nk.exe but I don't know hex editing. What info is on device info is fully different and its taken from rgu or the registry but no the dsm. DSM has only build version, aku and etc ( i.e 5.2.21139 aku 5000 ) inwhich it displays in about window. I have also tried to change OS version or the ROM version in ervius packagetools+buildos but still no change. I know that "its right" had changed the OS version in his's TNT Rom's. The only way is to dump the TNT rom and check the nk.exe file:).

Anyway, I have attached the nk.exe file/module. If you can, please edit it.

Thanks a lot

Srikanth.K
[Windows Mobile Software Development] FormerPalmOS:
Took a quick look - couldn't find anything resembling 6.1.0 in the module. Can you post a string or screen shot showing me exactly what you see that you want to change? May help narrow down what I'm looking for.
[Windows Mobile Software Development] bitserve:
Since changing the version in the nk.exe doesn't actually change the version of nk.exe, why not leave it alone? I only change the ROM version in the ROM image header and in the registry to show in deviceinfo. That's sufficient enough for people to see what ROM they're running.

Do you really need to lie about the kernel version? It's like Red Hat releasing RHEL 5 and changing the kernel to show 5 instead of 2.6.18, because they don't want people seeing 2.6.18 in the boot messages.

Edit: Nevermind. I see that you're trying to change the version that shows in device info. This nk.exe doesn't show that version. It's probably being set in boot.rgu or boot_ms.rgu in your XIP boot image, provided you've looked everywhere else.
[Windows Mobile Software Development] chavonbravo:
http://xdaforums.com/showthread.php?t=476828 :)
[Windows Mobile Software Development] FormerPalmOS:
Found what I think you are looking for. The Settings --> About screen is generated by shell32.exe. Much of the text comes from shellres.dll.{lang}.mui where {lang} is your language code - 0409 for US-English. Problem is, the string in shellres to display the OS version gets the number from somewhere else, so it is most likely coming from shell32.exe. It's not obvious where though.
[Windows Mobile Software Development] CRACING:
Hello,

I think you have misunderstood me.

Redhat did opposite me. I have ported wm6.5 to my wizard and everything is will. No problem in OS. When the device start, on the 2nd splash screen some text shows version about IPL, SPL, GSM and OS. In the OS version its still showing 6.1.0.0. I don't want to change this if its for me only. As I am cooker of CR86 Touch HD ROM's. If its shows 6.1.0.0, user thinks that I hacked the OS and made to show wm6.5 in about windows.

BTW; I am not talking about device info in CP but the OS version shows on 2nd spash screen. May be this will not show in other devices or is ROM version in other devices.

No, anyfiles in the SYS folder is not related to startup or I have ported all the sys to wm6.5. The kernal loads at the startup and its the XIP. The OS version is writen on somewere in XIP. I will try to take a screenshot of the 2nd splash screen info.

Thanks very much

Edit: Ok, I have attached the screenshot. Due to taken from digicam its not so clear but its good to see.
[Windows Mobile Software Development] FormerPalmOS:
OK - this is a different splash screen than what I see with 21109 XIP. I have no idea where this info is coming from - would check in NK.EXE and COREDLL, but assuming the numbers are stored as numbers, this will be like finding a needle in a hay stack.

And chances are that it comes from NK.EXE, which unless you got a WM6.5 build specifically for your device, you had to port from something else that was WM6.1. I understand your reason for wanting to change it - but since I'm not working with 6.5 I can't be of any more help.
[Windows Mobile Software Development] CRACING:
Thanks a lot for taking time for me to solve this problem. For your kind info I have changed the splash screen to at&t and thats the different. Anyway, I will PM to "its right" about the problem and lets see what he says:)

Thanks once again.
[Windows Mobile Software Development] c3ro:
hello,

would someone be so kind and attach here the last xipportex Rev optimized for bepes platformrebuilder.

thanks in advance as i cannot find it anymore and the authors downloadlink seems to be dead.

c3ro

**edit**

TY ANRYL
[Windows Mobile Software Development] anryl:
xipporterex 22 - 37

atached as per requests xipporterex colection :cool:
[Windows Mobile Software Development] Nokser:
THX to link new version
[Windows Mobile Software Development] At0mAng:
I am trying to learn to do this on a Touch Pro. From the screen shot would anyone mind telling me if these are the right settings to get the most free memory. I have seen Program Memory has high as 209MB free but I can only get mine to 201MB Free.

Any help would be great.

Thanks!
[Windows Mobile Software Development] FormerPalmOS:
The settings on this page affect the flash partition sizes, not program memory. The only two ways to affect program memory are to change the pagepool size limit and to compress the XIP so it needs less RAM to load. The former can be done with a readily available pagepool changer application. I assume you have a non-Verizon Touch Pro - set/keep the pagepool limit at 24MB or 32MB. The memory you "take away" from the program memory is better used as a pagepool anyway - your device will be faster. Or you can go for zero limit on the pagepool which lets WM use as much as it wants (vs. a hard limit of 24 or 32). But going below a limit of 16 will actually make your device slower, not faster (unless you go to zero).

FYI, the pagepool changer modifies a data structure that is part of NK.EXE in the XIP. The changer app will work on the S002 file in the nk.exe module in the XIP directory (add a .nb to the S002 file, run the app, then change it back), on the xip.bin (again, add .nb then change it back) or on os.nb.payload or on the final ROM .nbh. Only catch is that you also have to patch the code section of NK.EXE (S000 file in the module directory) to make the pagepool changer changes stick. There is lots of info on how to do this - basically you hexedit the S000 file, search for a string and change it (technically you are changing a MOV assembly language instruction to the equivalent of a NOP).

Compressing the XIP size requires much more in depth knowledge (much of which is in this forum). If you have a CDMA touch pro, I've already done much of this work for a number of different XIP system versions - check out the ppcgeeks CDMA HTC Touch Pro Upgrades forum. Just note that those are all optimized for the Verizon HTC TOuch Pro which has way less memory than the Sprint device - so you will want to be sure to change the pagepool limit (I set most of those at 10MB).
[Windows Mobile Software Development] GSLEON3:
This is easily changed with a couple hex edits. one is text & one is unicode text. Similar to changing the date of the rom.
[Windows Mobile Software Development] bitserve:
Cracing never said if he'd found where the version was found for his ROM, but I suspect that he had the same problem I had recently.

For me, the ROM version wasn't being pulled from anywhere in the OS or in the XIP, instead there was some junk in the os.nb.payload data that somehow was getting read first. I actually had to hexedit the os.nb.payload to clean it up. Someone should write a guide on cleaning up the os.nb.payload file.
[Windows Mobile Software Development] CRACING:
Hi,

Sorry, I forget to tell you about how I solved this problem. I simply hex edited the nk.exe and the OS was changed.

Thats all.

Thanks and regards
[Windows Mobile Software Development] inertiax3:
Dear all... being a n00b and having read many, many pages about XIP porting .. I still cannot succesfully *FULLY* port XIP 21109 to my Samsung i780 :(

I've resorted to using XIPPorterEx and this indeed seems to build a ported XIP - however the device doesen't boot.

Thus I've dumped the XIP.bin (that was created by XIPPorterEx) using XIPPort, clicked "write maps" and.. (both txt files are attached to this post)

map.txt shows:

80061f20 - 80061fb8 L00000098 o32 region_1 rva=00006000 vsize=00000098 real=01ff1000 psize=00000098 f=c0000040 for mspart.dll

80061fb8 - 80061fe8 L00000030 NUL

80061fe8 - 80061ff8 L00000010 copyent 00000000 L00000000 -> 80370000 L00000508

80061ff8 - 80061fff L00000007 modname pm.dll

80061ff8 - 80061fff L00000007 !!!!!!!!!!!!!!!!!!

80061ff8 - 80062008 L00000010 copyent 80292848 L00001800 -> 80326000 L00048750

80062000 - 80062008 L00000008 !!!!!!!!!!!!!!!!!!

80062000 - 80069814 L00007814 o32 region_0 rva=00001000 vsize=00007814 real=03ff0000 psize=00007814 f=60000020 for cachefilt.dll

..this would be all nice, but in the same file I also get:

8031e000 - 8031e000 L00000000 Start: start of RAM

8031e000 - 80326000 L00008000 NUL

80326000 - 8036f000 L00049000 initialized data of region_2 nk.exe

8036f000 - 80370000 L00001000 NUL

80370000 - 80371000 L00001000 initialized data of region_1 giisr.dll

80370000 - 80371000 L00001000 !!!!!!!!!!!!!!!!!!

80370000 - 80376000 L00006000 uninitialized data of region_1 nk.exe

80371000 - 80376000 L00005000 !!!!!!!!!!!!!!!!!!

80371000 - 80371000 L00000000 ------ start of RAM free space

80371000 - 878e1000 L07570000 NUL

878e1000 - 878e1000 L00000000 End: end of RAM

Does this mean that I should work my way up from cachefilt.dll? What about the other !!!!!!!!!!!!!! in the "Start: start of RAM" - should these also be addressed?

Please someone clarify this for me.. I am stuck and would like to continue. THANK YOU VERY MUCH!
[Windows Mobile Software Development] Ameet:
These are the overlaps in the copyentries of those modules. I have not yet mastered the art of removing the overlaps in those sectors but have you tried with another xip? Maybe you can change the xip.bin file and try again

This is the overlap in the RAM sector. You need to reloc the nk.exe and check the ROMHDR.txt to get those Physlast, ulRamStart, ulRamEnd values to correct it

p.s. I think cmonex has mentioned somewhere on 1st page here that the giisr.dll can be safely deleted to get more space in free RAM
[Windows Mobile Software Development] Ameet:
This means the ulRamEnd is overlapping the nk.exe by L00005000. To correct this try using MReloc_nk to correct the nk.exe address or change the ulRamStart in ROMHDR.txt to 80376000

Detailed mentioned here by cmonex and DupinBJK: http://xdaforums.com/showpost.php?p=2812740&postcount=4
[Windows Mobile Software Development] Nokser:
You go tu my TUT, maybe it work.
[Windows Mobile Software Development] Ameet:
Try nokser's tutorial if it helps or upload both the xip.bin files and I'll see what I can do :)
[Windows Mobile Software Development] Nokser:
As for the porting XIP Sektion, willing to help :cool:
[Windows Mobile Software Development] inertiax3:
Thanx very much guys.. I am still trying myself (but to no avail).. I will upload the files and maybe I could make another tutorial to be posted in this thread based on your steps

edit: uploaded the files below

http://www.megaupload.com/?d=NAVDSYAB

or

http://rapidshare.com/files/201923987/XIP_help.zip
[Windows Mobile Software Development] Ameet:
Would love to add your tutorial too :) Will check the files later at home tonight