With my experience, I will instruction to you.
Ex : CE OS 5.2.1620 (Build 18125.0.4.2)
Step by step :
1. CE OS 5.2.1620 related to XIP (You can do this with tools on forum).
2. Build 18125 related to cplmail module only. You only change this module that show build with your taste. (I'm sure).
3. 0.4.2 number related to AKU registry, this number to belong file *.rgu in Shell in KitChenROM.
You can compare new KitchenROM with other KitChen and replace this modules.
Do You know how to delete the ext rom from a kitchen?
Gr. bram
bram_smulders said:
Do You know how to delete the ext rom from a kitchen?
Gr. bram
Click to expand...
Click to collapse
I think you can edit it in default.hv file,
- search with autorun key.
boy_de_ghet said:
With my experience, I will instruction to you.
Ex : CE OS 5.2.1620 (Build 18125.0.4.2)
Step by step :
1. CE OS 5.2.1620 related to XIP (You can do this with tools on forum).
2. Build 18125 related to cplmail module only. You only change this module that show build with your taste. (I'm sure).
3. 0.4.2 number related to AKU registry, this number to belong file *.rgu in Shell in KitChenROM.
You can compare new KitchenROM with other KitChen and replace this modules.
Click to expand...
Click to collapse
I try as well to change the version number, but have no idea what you mean by "cplmail module". Where can i find it ?
Thanks ....
Jan
ISWEGO said:
I try as well to change the version number, but have no idea what you mean by "cplmail module". Where can i find it ?
Thanks ....
Jan
Click to expand...
Click to collapse
correct module is called cplmain.cpl be it on the way KITCHEN_TRINITY \ SYS \ 23554 \ SHARED \ COMMON \ Redist But how and what it can to correct (edit) I do not know. Apparently only the HEX editor
boy_de_ghet tell my line in the code which is responsible for the build number?
This was just put on the HTC site a day or so back. Hope someone find it useful.
http://www.mediafire.com/?0jt1cwyx61g
Hmmm... does anyone have any further information about this build? I'm interested to know how the "1.81.710.1" relates to Dutty's 5.2.1921 / 20000.7.0 WM6/CE?? According to the phone, I'm running 1.57.x.x but surely its a huge leap to 1.81.x.x ??
And I've only just got my Kaiser working well here in Australia on the Vodafone network... oh well, another flash coming up
Mirror:
http://rapidshare.com/files/7123262....1_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Enjoy,
Nadavi
I just put this on my Tytn and the ROM is more speedier than the Three ROM that came on my device.
What are the CE and WM build levels?
abubasim said:
What are the CE and WM build levels?
Click to expand...
Click to collapse
Where do I find the info ?
sorry I am fairly new to the WM devices...
Start / Settings / System tab / About (CE OS ??? and the memory)
Start / Settings / System tab / Device Information (ROM version & ROM date)
Thanks in advance!
GTRoberts said:
Start / Settings / System tab / About (CE OS ??? and the memory)
Start / Settings / System tab / Device Information (ROM version & ROM date)
Thanks in advance!
Click to expand...
Click to collapse
CE OS 5.2.1620 (Build 18125.0.4.2)
ROM version: 1.81.710.1 WWE
ROM date: 10/02/07
Radio version: 1.27.12.11
Same here:
CE OS 5.2.1620 (Build 18125.0.4.2)
ROM version: 1.81.710.1 WWE
ROM date: 10/02/07
Radio version: 1.27.12.11
Aussie stock.
Thanks ra303... so this official one is pretty close to the versions Dutty and the others are basing their rom's on. Not too bad.
Of course, one of the questions is... how well does video files play on it?
Have anyone tried this rom?
If the SMS / MMS combined or are they separate?
Thanks
JY
bjaaz said:
Same here:
CE OS 5.2.1620 (Build 18125.0.4.2)
ROM version: 1.81.710.1 WWE
ROM date: 10/02/07
Radio version: 1.27.12.11
Aussie stock.
Click to expand...
Click to collapse
Bought mine outright from 3 a couple of days ago, and my
ROM version is 1.81.861.0 WWE
ROM date: 09/12/07
Moby58 said:
Bought mine outright from 3 a couple of days ago, and my
ROM version is 1.81.861.0 WWE
ROM date: 09/12/07
Click to expand...
Click to collapse
Moby thats the version for Three only.
The One I posted is for generic optus/voda etc.
GTRoberts said:
Thanks ra303... so this official one is pretty close to the versions Dutty and the others are basing their rom's on. Not too bad.
Of course, one of the questions is... how well does video files play on it?
Click to expand...
Click to collapse
I have the same question. maybe i will flash it for a bit and test it out tonight. i doubt it will be any better. propbably just a different extended rom.
After i flashed this rom and used it for a few minutes it doesn't seem to have anything new. The graphics performance as i expected is the same which non existent.
Going back to Dutty's Rom
jyavenard said:
Have anyone tried this rom?
If the SMS / MMS combined or are they separate?
Thanks
JY
Click to expand...
Click to collapse
jyavenard... SMS/MMS are combined. I like that as I only have a few MMS a month.
GTRoberts said:
jyavenard... SMS/MMS are combined. I like that as I only have a few MMS a month.
Click to expand...
Click to collapse
The reason I want separate SMS/MMS is that way I can install the Palm Threaded SMS application and still have MMS available.
The Palm threaded stuff doesn't work for MMS.
So even though I pretty much never use MMS ; I like the idea that it still works on my phone, should I ever need it
Jean-Yves
For example i have CE OS 5.2.19212 (Build 19212.1.0.3)
(Build 19212.1.0.3) = SYS
CE OS 5.2.19212 = OEM
How and why does we change the OEM number?
I noticed ex. Garmins DK2 have CE OS 5.2.20226( BUILD 20226.1.1.1)
How can it be 'CE OS 5.2.20226' ? If latest rom for Kaiser is 19214, meaning the latest OEM for Kaiser that is.
I am NOT implying that chefs on this board fake theyre CE OS build, but if its not legit we don't know what is real anymore. Sorry if the question is a bit blur but I am lost on this one.
they should be all real. It's not an official kaiser build. You are right with the last official kaiser build. The other numbers are ports from other phone roms. Sometimes those builds can even be better than the last official kaiser build, sometimes worse since incompatability. Some people are curious the new things in a new build even if its a port so they want the newest build. Good reason why chefs cook these ported roms. My honest opinion, speed wise, the ports and the latest kaiser official are the same.
well yes we can take dll's from other devices or apps to upgrade but changing the CE OS build?
Meaning, you can't port whole OEM dir! Because device drivers are there, so why change the CE OS build?
I believe the 20226 comes from the Sony Xperia X1 (made by HTC). Laurnetius26 made a statement about this in one of his ROM threads... basically, he said he wanted to experiment with the newest ROMs (not necessarily Kaiser based) to improve the performance of the Kaiser. I believe he starts with entire new ROMs and goes from there (my guess). Dutty used to make his "hybrid" ROMs where he would use parts from different ROMs and use them together. Some chefs just clean up official Kaiser ROMs. Examples of all of these are all over this board.
Well, this i know. But if you study all of Leo`s release you will notice he doesnt use a single CE OS build that is "off".
Meaning he always uses Kaiser officials, that way ie. I have no problem following up on what he uses.
As for the experiment, he just experiments with the dll's not the CE OS number.
the CE OS number comes from MSXIPKernel in XIP. OEM in imgfs has nothing to do with it.
Intresting conversation here.
I'm a noob in this as well.
Question 2 you please, maybe you can explain?
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588).
Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed.
Thanks,
Leo
dcd1182 said:
the CE OS number comes from MSXIPKernel in XIP. OEM in imgfs has nothing to do with it.
Click to expand...
Click to collapse
Laurentius26 said:
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588)Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed
Click to expand...
Click to collapse
Hey Leo. Kaiser not my teritory but couldn't resist putting in my 2 cents This indeed is an interesting conversation
The build no is determined by the "d0b41563-b345-4444-aa15-986e7c7fff99.dsm" in OS within SYS
The version is determined by "d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm" file in XIP (MSXIPKernelTlk)
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Laurentius26 said:
Intresting conversation here.
I'm a noob in this as well.
Question 2 you please, maybe you can explain?
When I port I always use a shipped rom as source (OEM and XIP)
The SYS dir is ported and sometimes I port XIP as well.
How come when I do that the CE OS number is always the shipped source?
Only the (build....) changes, which I think is the SYS dir isn't?
Let's say for example CE OS 5.2.19212 (build 19588).
Are you telling CE OS 5.2.19212 is coming from XIP?
I ported XIP a few times but this number never changed.
Thanks,
Leo
Click to expand...
Click to collapse
Yes the CE OS number comes from the XIP and the build comes from the sys to be more acurate the buld number is in the dsm file in the os folder of sys.
I'm not shure acactly where the XIP number is stored but my guess would be one of the dsm file in the xip folder
gullum said:
Yes the CE OS number comes from the XIP and the build comes from the sys to be more acurate the buld number is in the dsm file in the os folder of sys.
I'm not shure acactly where the XIP number is stored but my guess would be one of the dsm file in the xip folder
Click to expand...
Click to collapse
Tag!! Beat you to it brother
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
ababrekar said:
Hey Leo. Kaiser not my teritory but couldn't resist putting in my 2 cents This indeed is an interesting conversation
The build no is determined by the "d0b41563-b345-4444-aa15-986e7c7fff99.dsm" in OS within SYS
The version is determined by "d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm" file in XIP (MSXIPKernelTlk)
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Click to expand...
Click to collapse
one reason I havn't moved to the never builds is that they are originaly made for VGA so we need to use (old files) in some cases to get them to work on QVGA phones... this will often cause more problems then it's worth messing with.
This actualy means that even though these 20xxx builds look like they are clean ports they are in fact hybrate builds
Laurentius26 said:
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
Click to expand...
Click to collapse
for more info, read this
http://forum.xda-developers.com/showpost.php?p=2362796&postcount=350
Yeah.. you are talking about the 192 packages to 96 isn't?
Thanks Gullum.
gullum said:
one reason I havn't moved to the never builds is that they are originaly made for VGA so we need to use (old files) in some cases to get them to work on QVGA phones... this will often cause more problems then it's worth messing with.
This actualy means that even though these 20xxx builds look like they are clean ports they are in fact hybrate builds
Click to expand...
Click to collapse
Laurentius26 said:
Nice to see you here!
So it's just a hack, that's what I was thinking as well.
Thank you for confirming this!
Grtz,
Leo
Click to expand...
Click to collapse
Well it depends on the cook, if he has chosen to hack the nos or use the correct porting method by which you get the dsm files automatically and it is a true build
htctouchp said:
for more info, read this
http://forum.xda-developers.com/showpost.php?p=2362796&postcount=350
Click to expand...
Click to collapse
Oh right. I forgot to mention your research in this part of the world
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
ryncppr said:
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
Click to expand...
Click to collapse
Thats what I mentioned that when cooks port the SYS alongwith the XIP from a different build, they automatically get both the dsm files
Cooks who dont know or dont want to spend time in porting, they would hack and hex edit the nos by way which htctouchp explained in his post
ryncppr said:
Ok so let me get this straight...... using Garmin for an example...
He has his latest ROM as CE OS 20270 and build 20270. He has more and less ported the XIP and SYS folders to achieve this but in reality it is just a hack and not really a true 20270 build???
My thought on the matter is that this number is that...exactly a number!!! I have fully ported the SYS changing the 192 files to 92...and copying over the XIP (that is allowed). Sometimes I would not get the build number to change? Even though I know the files were transfered over as I replaced them.
Click to expand...
Click to collapse
well, i do not own a kaiser and am not first hand familiar with garmin's ROM, but i would still have to assume that it is NOT a "hack and not really a true 20270 build"
i would assume that garmin has properly dumped a 20270 ROM, and replaced *DPI_192* with *DPI_96*. he then moved modules into place for kaiser and theres SYS.
a properly ported XIP gets all of MSXIPKernel and MSXIPKernelLTK from the new source (and thus gets the new build number). these packages are not specific to any DPI. the only thing kept from your kaiser original is OEMXIPKernel, which has no effect on CE OS build numbers.
true in this scenario the newer CE OS source has been modified to adjust DPI but it is what i would personally consider a "true" build. gullum said that this can cause problems- i have not seen this in my experience and this is the first i have heard that. gullum can you provide any detail here?
ryncppr, i think you misunderstood here:
ababrekar said:
Now some people hex edit these files to make the ROM look more recent, but an honest developer would use the SYS (may have altered some packs though) and XIP from the different builds and then cook
Click to expand...
Click to collapse
i think we agree that a "hack" means fake build numbers, achieved by hex editing the dsm's mentioned. i very highly doubt any of the ROMs you see in this forum with well known CE OS numbers are "hacks" of this kind. they achieved that build number by properly bringing over the parts containing it.
i should also mention that in my opinion, purposely faking a MS build by hexedit is bad for our community. it does nothing positive for anyone.
Ok I understand what your saying....And I hope Garmin takes no offense to me using his name it was just the first post I saw with both the CE OS and Build numbers newer!!!
SO I fully understand then....sorry so many questions but this is what XDA-Developers forums should be like...!!!!
WHen I properly port an XIP address I should use M'reloc the check the old folders numbers against the new folders right. A majority of them seem the same but it appears there is only a few folders with different numbers?
i would just like to say that use cooked ROMs only from people whom u trust. better yet, cook a ROM for urself by porting from a shipped ROM rather than using an uploaded kitchen.
OK I have done searching and read through pretty much all the Wiki.... but I can not find where the "Build" is that is refered to in soo many threads. Is it the OS Build? The TouchFLO version?
When I go to Device information I see ROM Version 1.95.502.5 WWE But I do not see a build. If I Look at TouchFLO in the settings I see I have Version 3.0 Build 29946. << Is that the Build that they talk about? I am most interested since I want to use the "[APP][CAB][QVGA]HTC Rhodium Menu Enhancement-Replacement [04-10-09] " But they say I need to have build 21000.
http://forum.xda-developers.com/showthread.php?t=502327
[APP][CAB][QVGA]HTC Rhodium Menu Enhancement-Replacement [04-10-09]
Thanks again and sorry for the Newwb Question. I truly did search and read... but searching for "Build" even with anything just gives too much back.
Regards,
SoBBie
Hi supersobbie,
Build refers to the version of the Operating System; you can typically find the information on your device by:
1. Tapping Settings.
2. Tapping the Settings tab.
3. Tapping About.
4. Tapping the Version tab.
For example: 5.2.21040 (Build 21042.1.6.1)
In the example above, it would mean Windows Mobile 5.2 running Build 21042, AKU 1.6.1. Note that the ".21040" portion in the example above should match the Build information ... but since this is a custom ROM, it may not.
HTH,
Ahhhh HA!... THANKS!!! I am a fool.
Found it... I have Win Mobile 6.1
CE OS 5.2.19971 (Build 19971.1.2.6)
That is why my stuff is not working...
Thanks alot.
SoBBie
Finally cooked my first ROM for my ELFIN (GSM)!! So please be kind..
thanks to ELF(in) Hybrid Kitchen v2.0.7
Windows Mobile 6.1 and next generation TouchFLO™
Windows Mobile 6.1 Professional
CE OS 5.2.1.19972 (Build 19972.1.2.7)
© 2008 Microsoft Corporation.
should I include a Screenshot? I don't think so .. you've seen Manila right? so just take the SS from there..
This is a SHIFTED ROM - (SOUTH EAST ASIA - (Philippines))
http://www.htc.com/sea/SupportDownload.aspx?p_id=88&cat=2&dl_id=421
I have a valid Serial Number
htc.com said:
Summary: Update HTC Touch (ROM 256MB, RAM 128MB version) to Windows Mobile 6.1 and next generation TouchFLO™. ROM version: 3.07.707.02 WWE; ROM date: 10/25/08; Radio version: 03.34.90 Protocol version: 4.1.13.71
Click to expand...
Click to collapse
i think this is for Vague? but I want it in my ELFIN! I keep getting a INCOMPATIBLE MODEL ID! so, after a lot of die-hard trying but so what.. here it is! a very very Clean ROM (I like clean ROMs, make me feel at ease )
This is a CustomRUU, I think that means, you should have your CID unlocked! and for all those WM6.1 fans.. here's your ROM
http://uploading.com/files/167a8da2/RUU_signed.nbh/
does anybody have a WM6.5 CLEAN!!! for QVGA? Built around 23017? I don't like the 23047 taskbar!! YUCK! I don't think Microsoft released that kind of taskbar, it's awefull and stupid.
What version of manilla is it? Thanks.