Related
Hello there.
well, i'm trying to cook a new version of my ROM, but i have sawn on Fanman release that there's no RGU files...
Because he seems to have merged all of them in the default.hv.
I've tried, but many keys disappear when flashing it to phone...
Have you got any ideas ?
Thanks
Best regards
What kitchen are you using to cook the rom? I've been using the Core Pro kitchen but noticed that none of the changes I made to the .hv files were being included in the cooked rom so this would explain why none of yours are either. For now stick all the changes into 1 rgu file, will be much easier to insert into the hives once it is working again that way I'd imagine.
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
kulbut0r said:
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
Click to expand...
Click to collapse
Is that not what he already has tho? I thought the point of his post was how to get all the rgu files into the hives but since this is not currently possible (as far as I am aware, kitchen dependant of course) he may as well place them all into one rgu file.
yep, all changes are not tooked in the hv files, i wanna have only the hives to gain more spaces...
I'll try again
aje_fr said:
to gain more space...
Click to expand...
Click to collapse
kulbut0r said:
Click to expand...
Click to collapse
No more RGU = More space on ROM
This evening, i tried to copy HV after buildos and before createrom, but nothing more....
And when i looked on the temp folder of kitchen, the hv files are really small and doesn't include the hv files in sys\metadata...
Really strange, it seems that modifications in the hives of sys\metadata are not included in final rom ?!
aje_fr said:
No more RGU = More space on ROM
Click to expand...
Click to collapse
small benefit however !
why not to stay with markquinton's recommendation : place all you updates into one rgu file.
So, i finally make it work but strangely i have more memory but software couldn't start and claim an memory error...
I can't even access to program folder
Anybody don't know why ?!
Thanks
aje_fr this is file FRE mui in Faman Rom and RGU file..!
http://rapidshare.com/files/44793173/MUI_RGU_040C.exe
method :
Dump Faman Rom and Copy All file to Dump Folder.Then it.Run PKT tools make OEM and SYS.Now u have OEM and Sys.In OEM and SYS copy all file FRE lang u need..!
Cheers..!
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
aje_fr said:
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
Click to expand...
Click to collapse
u online yahoo mesenger ???
i'm online now...!
Has anyone managed to successfully edit the hive files and have the changes included in their built rom? As I've been playing around with this for a while but have as yet still not managed it. I'm getting annoyed with having to set a lot of default settings in rgu files when they could easily be included in the hives from the start.
Hi , last version of buildos+package tools....
try 4.2b3 version now.....
Last version 29.04.2008
http://rapidshare.com/files/111296473/kitchen.zip
improved real xipporting with buildxip.exe...
how it works...
dump xip.bin from same or other device; so you have xip\ folder annd romhdr.bin.
copy xip\ folder just created into my buildos by clicking on:"New Xip"
and then by pressing on: "port it" and selecting all xip->same or different device xip, you finally have new xip build ported into my kitchen, ready to be builded into "out.bin" by buildxip executed by all "CREATE_ROM_xxx.bat" files building new rom.
Code:
this last version has also load/save config, so you can preconfigure from
ultralight to full rom, load a config file and only by a click you have the
preferred rom to build, so you can publish in a bit all kind of roms you want!!!
this tool goes into kitchen or bepe's WM 6.1 one, or WM 6.1 of mine...
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
ervius said:
Hi , last version of buildos+package tools....
added:
to extract xip for non trinity roms, at dump\ analyzing... it execute a bat file...
all bat files to extract xip are stored into \TOOLS folder, and must have a name that starts with: "XIP_extract" example: XIP_extract_From_hermes.bat; XIP_extract_from_trinity.bat ecc....
try it... obviously there are a lot of devices, you can try for yours and post the bat to make bettere xip extracting of buildos , inside \tools folder, yet XIP_extract_from trinity.bat and XIP_extract_from_kaiser.bat
TODO:
extract from os.nb by other devices from executing others bat like xip extracting...
bye!
download here:
http://rapidshare.com/files/103757462/buildos_3.9b3.rar
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
Click to expand...
Click to collapse
Can you give us a description of your cooking?
cyron_at said:
Can you give us a description of your cooking?
Click to expand...
Click to collapse
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
ervius said:
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
Click to expand...
Click to collapse
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
cyron_at said:
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
Click to expand...
Click to collapse
read also this 3d...
http://forum.xda-developers.com/showthread.php?t=320504
Once XIP is extracted, what exactly gets done to port the XIP to trinity?
Thank ERVIUS
Very good tools ...
4.0b1 is borning, what about???
now:
1) it can dump os.nb from different devices (kaiser / hermes/trinity for now!) executing differents bat made just to dump them...
2) extract xip from different devices (kaiser/hermes/trinity for now!) by executing different bats made just to extract them...
3) build os (for trinity/hermews also ruu_signed.nbh) for different devices (kaiser/hermes/trinity for now)
I think tomorrow, ops today in the afternoon, I'll post it....
what I need???
that someone make some bats to dump/build os.nb for other devices, and bats to extract xip from other devices....
bye!!!
Build Packages,..
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
cyron_at said:
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
Click to expand...
Click to collapse
yes, wait the 4.0b1....
and test that one....
ervius said:
yes, wait the 4.0b1....
and test that one....
Click to expand...
Click to collapse
Sure! When do you think will the release be published?
cyron_at said:
Sure! When do you think will the release be published?
Click to expand...
Click to collapse
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
ervius said:
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
Click to expand...
Click to collapse
Thanks Ervius... Great News!!! i will test it tonight.
axl79 said:
Thanks Ervius... Great News!!! i will test it tonight.
Click to expand...
Click to collapse
yes...
if I'll able to upload it....
some connectivity problems.....
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
ervius said:
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
Click to expand...
Click to collapse
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
ervius said:
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
Click to expand...
Click to collapse
Thank you.. Really nice tool! Trying tonight!
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
GDT said:
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
Click to expand...
Click to collapse
yes, you can, I posted kitchen until this afternoon, and don't know if I'll post the 19209 rom...
version 3 in 1st post...
some improvements, soved other little bugs, added "execute CREATE_ROM_***.bat" flag by default and context menu to delete files on "search duplicete files" into rgu editor...
bye!
Can anyone tell me what is the "OS.NB" file in the ROM folder? That is created when cooking a rom?
Its the one that follows the OEM SYS folder. Is that ROM folder OS.NB a complation of SYS folder file's? or the windows mobile OS?
OS.nb is a compilation of OEM, SYS and XIP too!
Regards,
Carty..
hi
Hello, ty for replying.
XIP is that the WM OS? Reason im asking is that i see some other roms on here has a lower size XIP os file, and they usually are faster.
XIP has the core modules which are mostly loaded on memory. XIP means Xecute In Place. Exspecially the files like coredll and other important ones require quick performance and so they are from XIP.
Regards,
Carty..
kool
Oh cool tysm. your the first helpful person ive met on here so far.
This means i can change the os.nb to a different from other roms?
sorta
umm the file in the ROM folder yea, but somethings might not work, they will apply but wont close properly, im still new so mix and match, but so far it worked for me.
Maybe we have to edit the boot.rgu or something!?
Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar
Bump, no one want to look in it and help me ??
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.
How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.
Bump, bump, bump.
Must be some1 out there, there can help me find my mistake ;/
danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon
anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot
Need help porting sys folder..
I've successfully ported XIP to 20757 and now i've been trying to port the sys build folder 20757 and up, from multiple roms, such as the xperia x1 roms, the blackstone roms, and other's from the site.
But all of my attempts has fail, so was hoping someone could tell me what im doing wrong.
First sys attempt i tried was;
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
found here http://forum.xda-developers.com/showthread.php?t=389772
Second i tired, to port it from a thread on the kaiser forum, http://forum.xda-developers.com/showthread.php?t=437264
and third i tried this following guide from the elf forms, http://forum.xda-developers.com/showthread.php?t=379598
so for short
1. made 1 folder for old sys, and 1 for new system with the build number
2. copy .vm .rom WinCENLS_WWE, shell/shellresand shell/shell32 folder, with my already ported XIP
3. swap out the res folder like 800 and 640 ones for the diamond, (where ever it is needed to port the rom)
4. then ran g'reloc
so yeah finally when i tried all this, form the guide, it doesnt work
What about the easiest way?
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
ababrekar said:
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
Click to expand...
Click to collapse
I thought that to but every time i tried to port the Blacstone sys and Greloc
the rom doesnt boot, I have tried many times and allways the same result.
havent test for a wile, the xip port I get whit your exellent manual xip port but not the sys, so now I have a rom os 20757 Build 19665
have you tried replacing all except the Metadata folder ?
for your XIP which is the base used 1.93, 1.96, 1.97 ?
I have tried the xiportereex tool but some modules are missing, so I tryied to add it by myself, it boot but sometime touch screen doesn't responde at first tap, very strange, I have also a pb with default ringtone witch is not the one it should be by mxipupdate
hi
thank you for your reply everyone but several attempts trying you methods but none has worked ; ;
UPDATE; i give up trying to port sys build, thnx for you help everyone.
Same problem for me, if I try all these method in order to port the sys 20764 ( blackstone) to me ELF, the phone don't boot :-(
if the problem is running poutlook, please check if you have custsat.dll in your rom.
if removed, poutlook won't run.
This is the sam exact problem i'm running into. I can't just not port the SYS because the XIP i'm using opens the windows in a tiny little corner in the top left hand corner. Has anyone figured out how to actually port the SYS since none of the tutorials seem to work.
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Bxsteez said:
a tiny little corner in the top left hand corner
Click to expand...
Click to collapse
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Vic5870 said:
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Click to expand...
Click to collapse
In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs
omaga said:
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Click to expand...
Click to collapse
I had this problem when i was porting the Touch HD ROM to the Xperia X1 and thats wvga to wvga. I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Bxsteez said:
I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Click to expand...
Click to collapse
Ye I thought that sys is the easy part I got so many sys port that the rom doesnt boot. Now i get 2 in a row 21109 and 21014 sudden and If I remember right I have allways done the same way
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Bxsteez said:
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Click to expand...
Click to collapse
Maybe you should post in the X-Peria ROM dev. forum!?
I have but as we all know the xperia doesn't get as much attention as to the full blown htc devices. I figure that the porting method should be about the same with the exception of changing some things based on resolution. Am i wrong?
Have you deleted some folders from official HD SYS??
If yes, notice that the rom doesn't boot without SqlCeMobile and SqlCeMobile_Lang_0409 folders. I'm speaking from my experience with HD.
And I remember I've ported these official builds to Toshiba G900 without problems. Then, make attention to these things too.
And control if into your original SYS, you have some different folders in comparison to the new SYS.
Another thing, Ervius xipporterex rev-35, deletes some things from xip, but it works perfect in that way. The only thing you have to notice, is that it deletes WinCENLS_WWE from xip, then you have to add it into SYS folder.
@Bxsteez,
chek your 21109 SYS, and change mxip_system.vol(into Shell), with your original and see if mxipcold_wpc_2.provxml is into Base_DPI_192 folder, if not, copy your original one there. Change MobileCalculator.exe into baseapps folder too.
Just gave this a shot and nothing works again.... I can't even port the XIP and use the standard SYS and get it to boot. I wonder if i'm using a some corrupted build of 21109. Can someone point me in the direction of where to get OS CE 21109 and 21109 build?
Search on ppcgeeks the calkulins kitchen for diamond, then extract the xip from os.nb.payload and use that to port, worked for me with ervius xipporterex-35.
And make those changes into SYS folder, they are needed to boot properly.