yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] lennysh:
Can somebody please attach buildxip.exe to a post for me?

Also, there are Titan and Vogue kitchens already on PPCKitchen.org's website. Apache as well... Others soon....
[Touch GSM ROM Development] !Aman!:
here u go :)
[Touch GSM ROM Development] {SBR}_L3GION:
i do understand there is kitchens already up for these 2 devices but i would rather learn how to do this stuff myself so that i dont have to rely on others to do the work for me and also i would like to start providing a service to the community.
[Touch GSM ROM Development] Noonski:
Even though i didn't need to because of the kitchen i use.

I still set out to reallocate the modules manually.

And then i came to the initvmmap.exe

I had to change it to 00012000 from 00013000

But everytime i clicked Do it!

It went back to the 00013000 ? It didn't do this on any of the other modules (up till now).

Let me continue doing my own XIP Port ;)
[Touch GSM ROM Development] lennysh:
Thanks, but that one doesn't work for me either... Guess I'll go back to Xipport, and leave this XIP Kitchen to be completed another day...
[Touch GSM ROM Development] Noonski:
Thanks for the xip.bin.

I think i managed to glue it together. At first i was abit confused. and was getting ahead of myself. But took the time and i didn't brick my phone.

Now running new Diamond XIP.

And i can even see some damned improvements. A few items just after reboot seem faster.

But Top Start Menu Bar is showing during the First Splash screen right after Flash.

Your Tutorial has just made me an even more dangerous man.

Nice working with you.
[Touch GSM ROM Development] lennysh:
To fix the start bar showing at boot, replace services.exe with one from an older "working" build...
[Touch GSM ROM Development] Ameet:
Hey Lenny, you beat me to it. Aman told me about this and I used the services.exe from 19951 Diamond build. This worked out well :)
[Touch GSM ROM Development] lennysh:
Bad thing is, this is not a fix. Or a patch. It's a bandaid. We need to compare the two files to find out what changed that is causing this issue, so we can start patching the newer builds.
[Touch GSM ROM Development] !Aman!:
i wonder how do u plan to compare the two files :rolleyes:?

PS: all these newer builds are coming initially for VGA devices, so i believe microsoft is developing them mainly for VGA and not QVGA which is leading to small bugs like the one mentioned above. the newer dll's & exe's may be more suited to the VGA devices than our QVGA devices.
[Touch GSM ROM Development] MickyMax:
Thanks, I've the same problem. I'll test this. :cool:
[Touch GSM ROM Development] lennysh:
You'd think this yes, but, I think I also have this bug on my VGA device... I'll double check...
[Touch GSM ROM Development] !Aman!:
i see...even if this bug exists for VGA devices, how can we find the problem with the newer builds?
[Touch GSM ROM Development] lennysh:
Well... It's like this... I know a dev that fixed a contrast bug newer builds were doing on the Axim. He did this by comparing a working GWES.EXE and a non-working GWES.EXE. There was also a menu bug with overlaying that he also made some slight changes to that file to fix that. As with the contrast bug, he found a hidden call for a registry entry. Once we now set that registry entry, no more contrast problem on boot. So I think if the Axim does indeed have this bug, I'll get him to do his magic. :cool: Then we can see about designing an app or something to do this on future builds if he happens to fix. Even if this bug isn't on the Axim, I have 2 PPC phones that I know one of have this bug. So I'll still get him to do it. :cool:
[Touch GSM ROM Development] lennysh:
Also, I'm trying to start an IRC chatroom for experienced developers/rom cooks for HTC devices only. Sorta a private chatroom where we could discuss things like this, fix them, then post them to forums... Just PM me if you want the details... This will also help us I think all stay current with the newer builds... I have several friends that I'm also gonna try to get in there... You'll definitely recognize them when you see them...:D
[Touch GSM ROM Development] MickyMax:
Why private chat ? The goal is'nt to share tips about cooking ?
[Touch GSM ROM Development] lennysh:
That took a lot longer than i expected... The idea is to compile the right ideas together, then post...with better how-to's.... less posting, yet get more accomplished... with a single post...
[Touch GSM ROM Development] Nixeus:
Hello !

I have ported the last SYS ( 20273) issue from the Diamond to my Touch !

I have ported the DPI in 96 !

Nevertheless, the Windows Live Messenger don't function :(

When i'm trying to connect, i have a error message :

" Unable to Connect, Try to verify that then reception is good"

Anyone have a Windows Live Messenger which i can integrate on my wm6.1 ROM ?

Great thanks for all :)
[Touch GSM ROM Development] Noonski:
You have to create your own .lnk files.

These days i'm alergic for those.
[Touch GSM ROM Development] MickyMax:
I've successfully ported the 20273's windows live to my french ROM. I'm using the DPI from the 19212 build and the others files from the true 20273.

Take a look at the OEMMisc rgu which has changes... ;)
[Touch GSM ROM Development] !Aman!:
it would have been better had u mentioned that registry value alongwith its correct value rather than creating a mysterious situation :D
[Touch GSM ROM Development] MickyMax:
Here's the new value. It's only the URL which has been modified.

[HKEY_LOCAL_MACHINE\Services\Windows Live\Platform\Passport]
"Policy"="https://http.mws.mobile.live.com/2006/10/MWP2007_02/SecurityPolicy/Default.aspx"
[Touch GSM ROM Development] Nixeus:
Great thanks for all your help, i will try your advice ! Gret thanks :)
[Touch GSM ROM Development] Nixeus:
Great thanks to your file Noonski, it function !

Nevertheless it is the 10.6.34.800, do you have a more recent version ?

Great thanks :)
[Touch GSM ROM Development] Noonski:
Ha,

Right back atja Ameet.

Since you added XIP porting to my curriculum.
[Touch GSM ROM Development] Ameet:
Will update this thread shortly with updates on porting guides. Also going to add the .CPL guide for porting newer Diamond / Raphael & Xperia ROMs :)
[Touch GSM ROM Development] lennysh:
XIP Porting Guide

I found a good detailed guide to XIP porting on a Chinese site (bbs.xbeta.cn) by the user ganfan a while back.. I decided to go and translate it for us to English. It has pictures and all. So if anybody would like to see it so far, the link is:

http://wiki.htcgeeks.com/index.php5?title=HowToPortXIP

I'm still working on the wording of it, so it'll be constantly updated for a lil while. Feel free to help out on it if you wish.
[Touch GSM ROM Development] Ameet:
:) I'll test your guide and report the outcome :D Will update mine if the physical RAM addresses can be change
[Touch GSM ROM Development] !Aman!:
very nice lennysh :)
[Touch GSM ROM Development] lennysh:
I'm no where near completely re-worded it yets. Tis why I'm asking anybody that knows the process to help out if ya can. Main reason I added it to a Wiki... :D
[Touch GSM ROM Development] raykisi:
Hi,

i want to ask how to use the "XIP port" option in Ervius's Pkgtools V4.3b1, coz after i use dumperrom.exe to dump the xip.bin and put all the file in the "New XIP" folder and press "Port It", the program showed an error msg, "Error Finding OEMXIPKERNEL package, try porting all modules manually!!! Why is that? and i could i resolve it?
[Touch GSM ROM Development] Ameet:
What exactly do you mean by "put all the files"? Do you have the OEMXIPKERNEL modules and files? Dumprom creates files and not modules. To use Ervius's kitchen for porting you will need modules. I suggest you use XIPPort tool and go as guided since it also needs your original OEMXIPKERNEL
[Touch GSM ROM Development] raykisi:
After i use dumprum.exe to dump my xip.bin, i have a XIP folder which contain subfolder like busenum.dll, cachefilt.dll, cecompr.dll, ceddk.dll.........

Or can u tell me wht exactly i should put in the "New XIP" folder, like wht structure should the folder be as when i use XIPPORT.exe to dump XIP.bin the result folder structure is different from when i using dumprom.exe
[Touch GSM ROM Development] Ameet:
Can you please refer to the pdf guide on first page? Answers to all these questions are in there
[Touch GSM ROM Development] X-On:
Hello!

Since 19665 Diamond ROM's version, I always have the taskbar (top bar), with the windows' flag in the middle, appears during the booting of the device on top of the welcome screen (third boot picture).

Have anybody met this issue before?

I'll put a picture tomorrow for whom doesn't know what i'm talking about.
[Touch GSM ROM Development] dsixda:
I've seen this with a few cooked ROMs... it happens sometimes. it's fine.
[Touch GSM ROM Development] X-On:
Okay but why am i the only one to have this issue? Is there a chance that a corrupted NBH file might give a wrong SYS folder?

Nixeus (aka CrashOver :p), did you manage to port this version without these issues?
[Touch GSM ROM Development] MickyMax:
Try replacing "services.exe" (in OS I think) by the one of your old build... (96DPI) ;)
[Touch GSM ROM Development] Ameet:
I started using the OS\services.exe from 19591 build :D It works
[Touch GSM ROM Development] nosedive:
thanks for your great guide on porting xip and sys ... i finally got it working on my trinity and upgraded my kitchen to xip 20273 and sys 20273!!!

i'm really really happy :D

i'm now on xip 20275...
[Touch GSM ROM Development] X-On:
Thank you!!!! It works like a charm!
[Touch GSM ROM Development] Nixeus:
It appear that here is a new ce issue from the diamon, not the 20275, but the 20295. For the moment i will stay on the 20273 because it appera that the 20275 build consum 2mb in addition.
[Touch GSM ROM Development] Nixeus:
The CE 20296 :) (not tested and ported for me, but if anyone could perfom benchamrk it will be great:) )

http://www.mediafire.com/?nnnlxbhfdsr
[Touch GSM ROM Development] Ameet:
Did you know there are these builds in the outside forum somewhere? :)

20276

205xx

207xx (AKU 1.4)

The newest Build is 209xx

:D
[Touch GSM ROM Development] nosedive:
so where to get these builds from??

i tried now 20275 for some hours and there seem to be performance benefit in 20275 over prev builds... (though 20275 need 2mb more ram)
[Touch GSM ROM Development] nosedive:
ported my 20296 over to 20275 but device is stuck on 2nd boot screen... any similar experiences to you??
[Touch GSM ROM Development] !Aman!:
20976 ?? :D, must be 20296, isnt it?

can u tell us what files/modules did u change while porting it?
[Touch GSM ROM Development] Ameet:
If you have downloaded the 20296 from Niki kitchen threads, then this MSXIPKERNEL in kind of incomplete. I mean this doesnt have fatutil.dll and a few others too. I'm trying to combine the missing modules from the 20275 build, but last night even with 20296 XIP and 20275 Core the ROM showed me 20273 Build SYS. Tonight I'm going to try and cook a ROM with full 20275 SYS & 20296 XIP. If this works out well, I'll upload my working XIP
[Touch GSM ROM Development] lennysh:
Just for the common knowledge, 20275 is fake. It's actually 20273 that has been hexed to be 20275. 20273 is still the newest build that I know of that is authentic. If I'm wrong, (read this on several Chinese, Russian threads) then please prove me wrong. I need something to do anyway. Seems all my devices (4 btw) are running 20273, and now I'm bored. Nothing to cook! :D
[Touch GSM ROM Development] Ameet:
Phew!! Thanks for the update brother. Looks like I just found my newer shipped ROM hookup :)

I'm going to revert back to 20273 build then :D
[Touch GSM ROM Development] Nixeus:
MMM i have perfrom benchmark with the CE 20273 and 20275 ( with the same SYS, and APPZ) and it appear that the result of the benchmark is not the same:)

20275 is better ! So i don't think that the 20275 is the 20273 !
[Touch GSM ROM Development] kokotas:
I'm with you!

For further discussing,

does anybody believe that bepe would post a build that's fake?

I don't think so!Do you?

Regards!
[Touch GSM ROM Development] Nixeus:
I would like to find the xip.bin of CE 20295, because.ht 20295 ce here appera to be missing :s
[Touch GSM ROM Development] nosedive:
did you succeed??

i did the same but in some way the xip does not work ... i got xip20273 and sys20273 running but xip 20296 does not work for me - i guess its why there are parts missing... i did not get the 20296 from niki kitchen, but if you search on google, there are some chinese threads you can get it from...
[Touch GSM ROM Development] Ameet:
Yes succeeded right :) Attached the 20296 MSXIPKERNEL on post 3 (http://xdaforums.com/showpost.php?p=2051340&postcount=3) Mix those modules with your OEMXIPKERNEL and you are ready to cook. Do the M'reloc id necessary :)
[Touch GSM ROM Development] nosedive:
finally got it up and running

thanks for help! ;)
[Touch GSM ROM Development] Ameet:
:) Happy cooking ;)
[Touch GSM ROM Development] ayyu3m:
been working on hypercore v1.01 for a while. not so good at xip porting yet. but have downloaded the tools from 1st post.

staring at the pictorial. i sure am gettin error when i run the 1st command

C:\Users\ayyu3m\Desktop\HyperCore\Tools\XIP_extract>nbsplit -elf os.nb
NBSplit 2.0 RC 2
No supported device specified.
Usage: nbsplit -hermes|acer|sp|mpx200|emu <filename.nb>
This will generate <filename.nb.payload> and <filename.nb.extra>
[Touch GSM ROM Development] Ameet:
Aah!! You need to run nbsplit -kaiser os.nb ;) There's no -elf switch in the nbsplit
[Touch GSM ROM Development] ayyu3m:
i tried that command cos -kaiser os.nb switch didnt work.

i m guessing its something to do with paths or file locations?

???
[Touch GSM ROM Development] !Aman!:
first, get the latest tools. the latest version is 2.1 RC2, then use nbsplit -kaiser os.nb
[Touch GSM ROM Development] nosedive:
new xip+sys20721

i learned a lot in this 3d and i thank you all ... and i let you know if i find something new.. its brewing out there ... new xip and sys ready for cooking

see here

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

http://xdaforums.com/showthread.php?t=402752
[Touch GSM ROM Development] ayyu3m:
thankx htctouchp. its working now.
[Touch GSM ROM Development] ayyu3m:
getting an error in M'Reloc

wrong value in o32_realaddr

??
[Touch GSM ROM Development] Ameet:
Yes. There are 2 modules which cant be reloced (dont know off hand which ones) But why manual relocing when Bepe, Ervius & Koko's kitchens can do it auto for you :rolleyes:
[Touch GSM ROM Development] ayyu3m:
keke..i was following ur picture tutorial and didnt have second thoughts abt looking elsewhere..hehehe

great pictorial...i jus made myself familiar with commands...now to look into kitchens.
[Touch GSM ROM Development] y_bother:
first really thanx :) and great done

just one simple question plz

when making the SYS folder... both folders have to be for the same device?

just to be sure

sorry if this question is asked before :)
[Touch GSM ROM Development] Ameet:
:) I got me a visitor after a long time :D

Porting SYS means the SYS to be used is from a different device. Very simply to follow as a thumb rule would be the below scenario

Old SYS

SYS\Shell\shell32.exe

SYS\Shell\shellres.dll

SYS\OS\services.exe (this is required only to get rid of title bar showing at boot if SYS used from VGA devices)

SYS\.VM

SYS\WinCeNls_WWE

New SYS

Rest of whole folder :) and run G'reloc as mentioned in the SYS porting section
[Touch GSM ROM Development] !Aman!:
i'm not sure if VGA devices are the culprits here. i've noticed this title bar even in shafez ROM which is from a QVGA device itself. and btw, we have been using 19591/19588 build's services.exe (for solving this issue) which are from VGA devices ;)
[Touch GSM ROM Development] Ameet:
Aah yes :) You right :D Since I lost my data I lost my head too :D
[Touch GSM ROM Development] pfcsabre:
Probably trying my luck in posting in this thread than in Dev and Hacking thread :o

I've managed to do manual XIP porting from ababrekar's guide, and now doing SYS porting. I'm following this guide in assumption that it's almost the same for all devices. I had this instruction from the manual XIP porting:

But here g'Reloc complains and is looking for some files in the kernel folders when I delete OEMXipKernel and MSXipKernel. So if I do manual XIP porting, do I delete the folders if not porting a SYS, or do SYS porting first, delete it and do manual XIP porting?
[Touch GSM ROM Development] Ameet:
You probably misunderstood :) The XIP porting guide mentioned here is maybe as I would put it, is for those specific devices which are supported by the buildxip.exe tool. The guide (manual) is for devices which are not supported. You need to remove the MSXIPKERNEL & OEMXIPKERNEL foders from your SYS & OEM folders and then run GReloc
[Touch GSM ROM Development] pfcsabre:
No I understood it correctly :D I like to do things manually first then think of automatic procedures later, this way I'll understand more of it :) Thanks for the tip, will try to do that now!
[Touch GSM ROM Development] lennysh:
My point exactly. This is why I luv my XIP Kitchen I made. Of course, you have to be able to do it manually first to make an XIP Kitchen. But now, anybody can do XIP. Or, will when it's releasable. It does everything automatically now. And werks perfectly 100% of the time. I just need to make some minor changes. But this is off-topic... l8tr!
[Touch GSM ROM Development] Noonski:
Even if the default.hv and user.hv get recreated in Rom, i still like keeping the original default.hv and user.hv in the Metadata folder when porting another systems SYS folder.
[Touch GSM ROM Development] Ameet:
Hey Lenny. Hope to see this soon for public release ;)
[Touch GSM ROM Development] try:
Dear AB,

its me again. I am trying to port the SYS 20924 from ELF to my Raphael. Sorry to post in ELF section but I cannot find it in Development section.

XIP porting was done with your help. Thank you.

I follow your suggestions above to port the SYS, but the device do not boot. it stuck on the red text (radio, protocol, etc)

So I re-try it from the beginning.

Use Raphael SYS as working base.

Replace all directories inside SYS with directories from SYS 20924 except:

All SYS\***DPI_96, I left the SYS\***DPI_192 since Raphael use VGA

SYS\.ROM

SYS\.VM

SYS\Base_Lang_0409

SYS\OS

SYS\ppgprov

SYS\Shell

SYS\SQM​

G'Reloc,

This time I managed to pass onto next screen (Preparing your device for first use....).

But my device stuck there.

Any "light up" on what i was doing wrong?

TIA,
[Touch GSM ROM Development] !Aman!:
use those in red color from new SYS.
[Touch GSM ROM Development] Ameet:
Also to add, ensure matching the .VM values from the original SYS through G'Reloc
[Touch GSM ROM Development] try:
Actually, when 1st i try to port.

I was trying to replace everything with new SYS, except the one mentioned by Ababrekar:

SYS\Shell\shell32.exe

SYS\Shell\shellres.dll

SYS\OS\services.exe (this is required only to get rid of title bar showing at boot if SYS used from VGA devices)

SYS\.VM

SYS\WinCeNls_WWE​

and gwes.exe (needed for VGA devices)

But it didn't boot, just stop in red R...D...G... screen

@Ababrekar

G'reloc maintain values from original SYS, as you mentioned in the guide.

I will try again tonight. In the meantime any help are really appreciated.

TIA and cheers,
[Touch GSM ROM Development] !Aman!:
don't replace those. just use the new ones and then try.
[Touch GSM ROM Development] Ameet:
Try again with what Aman mentioned. Moreover just to clarify, Greloc doesnt have values from original SYS but it determines them from the .VM module so first run the tool on your original sys and then run again on the new sys to match those values ;)
[Touch GSM ROM Development] try:
Thanks guys,

Definitely will try again as your suggestions. But now I am in business trip for 1 week. Soon as I return I will try and let you guys now the progress.

TIA,
[Touch GSM ROM Development] robertus3d:
Hi guys, great work, but a question for you!

I've ported Sys 20931 in my rom, except .Vm folder, shell32.exe and shelres.dll.

I cook it but at startup it gave me tmail error and any type of messages doesn't work also IE...

Some idea or tips!

Great work also with Xip porting!;)
[Touch GSM ROM Development] qsqa:
Maybe I'm noob but you should take from original SYS also shellres.192.dll (in QVGA it will be shellres.96.dll) and shellres.dll.0409.mui ...
[Touch GSM ROM Development] robertus3d:
Ok I've solved my porting Sys, all works correctly but I've still 1 bug, data connection by my operator don't work!:mad:

I can download data by wifi or sync pc, I've try 2 o 3 simcard, but nothing!

I've ported new Sys folders except old .Vm, .Rom, shell32.exe, shellres.dll, services.exe, ppgprov and Sqm folder from my rom!
[Touch GSM ROM Development] jeesus123:
I also have problems with porting sys to raphael, I used latest AT&T rom as base and took 20931 SYS files from ppkitchen buidOS software.

Usually it hangs on boot with radio and rom details. Can someone post short tutorial how to really port SYS on Touch pro.

thanks in advance.
[Touch GSM ROM Development] adonix:
Hello,

First, excuse me for posting in Elf's section since i own an eten x800 device. I'm trying to port wm6.1 to my device. I have succeeded to port wm6.1 from eten x900 (xip and sys) but i'm unable to port sys to my device from any HTC device.

I have followed the steps found in this thread, but no success, the device hangs on boot screen. What i have noticed is that i'm able to start the device once in replace the entire OS folder in sys from older version. But the device is so buggy and it gives lots of error messages.

what i did is:

Keep : .VM, .ROM, ppgprov, WinCENLS_WWE, SQM, shell32.exe, shellres.exe & services.exe

Replace all files (same dpi and resolution)

that didn't work unless older OS folder was kept

Any ideas please?

Thanks
[Touch GSM ROM Development] Nixeus:
Difficulties to port the new SYS 20764 (blackstone) to our ELF / ELFIN

Hi my friend,

I need a little help !

I have no difficulties to port SYS folder !

But, with the new SYS folder 20764 issue from the BLACKSTONE, i have difficulties !

If i Replace .VM, .ROM and wincelens, the romm boot, but with the BIG logo, it's normal because the blakstone is in DPI 192.

Next, i replace all the folder *192* , i build my rom, and then, after the first bootscreen ( the htc bootscreen), there is the " bip", and i can see no welcomescreen, and i cannot to continue !

Have someone any help to this probleme ?

How porting this SYS in DPI96 ?

Great thanks my friend :)

regards,

Nixeus
[Touch GSM ROM Development] !Aman!:
did u cook a protected ROM?
[Touch GSM ROM Development] Nixeus:
Hi,

Yes i cook protected rom, but i can cook non-protected rom, why ?
[Touch GSM ROM Development] !Aman!:
which kitchen did u use? Ervius' or bepe's?
[Touch GSM ROM Development] Nixeus:
It's a kitchen named "Execute", it's a french kitchen.

I used it since 10month and no problem :s
[Touch GSM ROM Development] Nixeus:
Do you think that i need to test with another kitchen, ervius ? or bepe ?

Thanks :)
[Touch GSM ROM Development] !Aman!:
yeah, try bepe's or Ervius' kitchen.
[Touch GSM ROM Development] sleurhut:
It is not the kitchen.

I had it working and now i cant do it againg.

I have now the same pronblems

beep at startscreen but i cant see the allign stuff. It must something simple.
[Touch GSM ROM Development] !Aman!:
check if all of the provxml's have +r & +s attributes. then also try after making the attributes of all the rgu's/dsm's etc as +a -r -s -h
[Touch GSM ROM Development] Garfiel:
Hello

I'm trying to carry a 21,009 SYS to Raphael. And I get an error "poutlook.exe. I tried to change the original file, but even so, it still gives me the same mistake.

That is what I am doing wrong?

Thank you
[Touch GSM ROM Development] Noonski:
Skip the 21009 SYS, Go around the forum and roms with that Sys and you will find quite some issues Popping up.
[Touch GSM ROM Development] Nokser:
Porting build 21139

Tell me how to do that in the SETTINGS options are all about and with the like ... in 21139 THX