Database Info

aku 3.5 files

Can anyone tell me where i can find the files needed to cook your own aku 3.5 rom? i mean something like that, but in 3.5 version:
Device-dependent packages:
DEV:
[li]DEV_Himalaya_v1.50.rar[/li]
ROM:
[li]ROM_Himalaya_v1.50_3.00a.00.rar - 128MB RAM[/li]
[li]ROM_Himalaya_v1.50_3.00a.32.rar - 96MB RAM / 32MB RAMDisk[/li]
[li]ROM_Himalaya_v1.50_3.00a.64.rar - 64MB RAM / 64MB RAMDisk[/li]
Independent packages: !!! Both should have the same AKU !!!
OS:
[li]OS_AKU_2.0_v1.50.rar - AKU 2.0 (Build 14847)[/li]
[li]OS_AKU_2.2_v1.50.rar - AKU 2.2 (Build 14928)[/li]
[li]OS_AKU_2.3_v1.50.rar - AKU 2.3 (Build 14955)[/li]
[li]OS_AKU_3.0_v1.51.rar - AKU 3.0 (Build 15096)[/li]
LOC:
[li]LOC_AKU_2.0_v1.50_[ WWE | GER ].rar - AKU 2.0 [/li]
[li]LOC_AKU_2.3_v1.50_[ WWE ] - AKU 2.3[/li]
[li]LOC_AKU_3.0_v1.50_[ WWE ] - AKU 3.0[/li]
Thanks a lot!

dzuniga said:
Can anyone tell me where i can find the files needed to cook your own aku 3.5 rom? i mean something like that, but in 3.5 version:
Device-dependent packages:
DEV:
[li]DEV_Himalaya_v1.50.rar[/li]
ROM:
[li]ROM_Himalaya_v1.50_3.00a.00.rar - 128MB RAM[/li]
[li]ROM_Himalaya_v1.50_3.00a.32.rar - 96MB RAM / 32MB RAMDisk[/li]
[li]ROM_Himalaya_v1.50_3.00a.64.rar - 64MB RAM / 64MB RAMDisk[/li]
Independent packages: !!! Both should have the same AKU !!!
OS:
[li]OS_AKU_2.0_v1.50.rar - AKU 2.0 (Build 14847)[/li]
[li]OS_AKU_2.2_v1.50.rar - AKU 2.2 (Build 14928)[/li]
[li]OS_AKU_2.3_v1.50.rar - AKU 2.3 (Build 14955)[/li]
[li]OS_AKU_3.0_v1.51.rar - AKU 3.0 (Build 15096)[/li]
LOC:
[li]LOC_AKU_2.0_v1.50_[ WWE | GER ].rar - AKU 2.0 [/li]
[li]LOC_AKU_2.3_v1.50_[ WWE ] - AKU 2.3[/li]
[li]LOC_AKU_3.0_v1.50_[ WWE ] - AKU 3.0[/li]
Thanks a lot!
Click to expand...
Click to collapse
i think*
ftp://xda:[email protected]/Uploads/Himalaya/Helmi/Helmi_HIMA_AKU3.5_R0.rar

Here's the right one:
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_Hima_AKU3.5_Kitchen_Test1.rar
please replace the LOC & OS with this pack (to avoid problem with messaging app):
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_AKU3.5_LOC&OS_With_CrossbowTheme.rar
Note:
Almost all my work is been tricked by someone, make sure u've check for virus and make sure the file isn't modify by someone else.

Helmi AKU3.5 Kitchen
helmi_c said:
Here's the right one:
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_Hima_AKU3.5_Kitchen_Test1.rar
please replace the LOC & OS with this pack (to avoid problem with messaging app):
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_AKU3.5_LOC&OS_With_CrossbowTheme.rar
Note:
Almost all my work is been tricked by someone, make sure u've check for virus and make sure the file isn't modify by someone else.
Click to expand...
Click to collapse
Thanks a million, Helmi.
I notice, c_shekhar added ext-rom for use after hard-reset, in his latest ROM... do I any need to modify anything to have this function... It would be useful to automate other installations?

Dear helmi_c,
Thanks for the post.
I couldnot download the files. Could you please check it back.
Best regards,
helmi_c said:
Here's the right one:
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_Hima_AKU3.5_Kitchen_Test1.rar
please replace the LOC & OS with this pack (to avoid problem with messaging app):
ftp://xda:[email protected]/Uploads/Himalaya/Helmi_AKU3.5_LOC&OS_With_CrossbowTheme.rar
Note:
Almost all my work is been tricked by someone, make sure u've check for virus and make sure the file isn't modify by someone else.
Click to expand...
Click to collapse

shehababdulaziz said:
Dear helmi_c,
Thanks for the post.
I couldnot download the files. Could you please check it back.
Best regards,
Click to expand...
Click to collapse
the ftp files is missed !!!!!

shehababdulaziz said:
Dear helmi_c,
Thanks for the post.
I couldnot download the files. Could you please check it back.
Best regards,
Click to expand...
Click to collapse
Here is Helmi_C
http://www.4shared.com/file/10259265/40c4647d/Helmi_AKU35_LOCOS_With_CrossbowTheme.html
http://www.4shared.com/file/10245518/3cd0e8a/Helmi_Hima_AKU35_Kitchen_Test1.html

How to change the Ver Name?

In the Version screen under Settings/About/Version
How does one change the name there.
CE OS 5.2.1620 (Build 18125.0.1.2) *****
The * is where the name is.
How Do I change that.

almulder said:
In the Version screen under Settings/About/Version
How does one change the name there.
CE OS 5.2.1620 (Build 18125.0.1.2) *****
The * is where the name is.
How Do I change that.
Click to expand...
Click to collapse
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"About"=" GM v1.7"

Thank you.

Custom rom`s CE OS build, what is real and what is not?

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.

ROM resource Windows Mobile 6.1 (96 DPI)

Iam now collecting all ROM resources i can get ;-) so i can share it.
Links will be later on.
XIP.bin => porting ROM (OS) (ROM)
SYS => OS related (coredll.dll)
Complete
5.2.19212
5.2.19214
5.2.19588 (xip.bin - os.nb.payload - SYS)
5.2.19591 (xip.bin - os.nb.payload - SYS)
5.2.20202 (xip.bin - os.nb.payload - SYS)
5.2.20273 (xip.bin - os.nb.payload - SYS)
5.2.20275 (xip.bin - os.nb.payload - SYS)
5.2.20721 (xip.bin - os.nb.payload - SYS)
5.2.20748 (xip.bin - os.nb.payload - SYS)
5.2.20749 (xip.bin - os.nb.payload - SYS)
5.2.20753 (xip.bin - os.nb.payload - SYS)
5.2.20755 (xib.bin - os.nb.payload - SYS)
5.2.20764.1.4.3
5.2.20788 (xip.bin - SYS)
5.2.21159 (xip.bin - SYS)
5.2.21169 (xip.bin - SYS)
5.2.21176 (xip.bin - SYS)
5.2.21189 (xip.bin - SYS)
5.2.21193 (xip.bin - SYS)
5.2.22222 (xip.bin - SYS)
Official
5.2.19608.1.2.60 - HTC Venus WWE (1213...)
(xip.bin - SYS)
5.2.19199.1.0.0 - HTC Kaiser WWE (3.08.161.0)
(xip.bin - SYS)
5.2.19965.1.2.3 - HTC Touch Cruise WWE (3.13.405.0)
(xip.bin - SYS)
5.2.19974 - HTC Jade WWE 1.40.721.2)
(xip.bin - SYS)
5.2.20279 - HTC Rose WWE 1.14.707.0)
(xip.bin - SYS)
5.2.xxxx - HTC WWE )
(xip.bin - SYS)
More to come...
03-10-2008: a 20788 ROM i still havent found
04-10-2008: Added 20748 SYS
07-10-2008: I am Busy to replace the 5.2.19965 for a official one for sure!
16-10-2008: added a official 5.2.19965.1.2.3 extracted SYS and XIP.Bin
18-11-2008: added a 5.2.19608.1.2.60 extracted SYS and XIP.bin (and replace 192.dpi files with 96.dpi files)
25-11-2008: HTC Jade complete
25-11-2008: HTC Rose in progress
Update as soon as possible now
>>> Collection <<<

can't wait!

can i get the sys folder for 20755

5.2.20755
{SBR}_L3GION said:
can i get the sys folder for 20755
Click to expand...
Click to collapse
SYS 5.2.20755 is placed

wow great stuff man !, and thanks for this 20755 Build, any info about it ?

Now this is a contribution that will be under appreciated by most.
But This is a great Effort.

this should be stickied.

S.V.I said:
this should be stickied.
Click to expand...
Click to collapse
This should even be stickied in Hacking and Development.

Noonski said:
This should even be stickied in Hacking and Development.
Click to expand...
Click to collapse
If it will be stickied it is not my decission i think. ;-)
But i want to make a catalog for all available and future versions of windows Mobile.
So iam just startting now and there is a lot to do.

hey sleurhut, nice job...there is a newer build out there, newer then the 20755, some thing like 20788 , could we have that too

ather90 said:
hey sleurhut, nice job...there is a newer build out there, newer then the 20755, some thing like 20788 , could we have that too
Click to expand...
Click to collapse
Yep i will collect it all ;-)

Wish i know what you said
Try the TNT's kitchen with some this, i cant understand but i will learn reading a lot... This is the things I cant understand where can get??? kind of magic, does anybody knows a link for a cooking school?

hi here is a link to cooking:
http://forum.xda-developers.com/showthread.php?t=388666
here is the link to port the files he gave us:
http://forum.xda-developers.com/showthread.php?t=389772

Thanks but...
dfeuchter said:
hi here is a link to cooking:
http://forum.xda-developers.com/showthread.php?t=388666
here is the link to port the files he gave us:
http://forum.xda-developers.com/showthread.php?t=389772
Click to expand...
Click to collapse
I cant test and learn how to cook. Somebody stole my wizard last night i was waiting for the BUS and two guys atacks me with a knife, they took my Wizard and my money.

+ Que PPC said:
I cant test and learn how to cook. Somebody stole my wizard last night i was waiting for the BUS and two guys atacks me with a knife, they took my Wizard and my money.
Click to expand...
Click to collapse
ohh **** sorry for u.
@sleurhut:
I have build the rom from your sys and xip.bin but when i load the rom to my device an start it i get this message:
"The file 'poutlook' cannot be opened. Either it is not signed with a trusted certificate? or one of its components cannot be found..." And I can't do anything. i have searched but i have nothing found related to this problem

search for a program called "unsigner" and a program called "ms signer" maybe one word.
it works the same way with dlls. first you unsign to get rid of any signatures, then you sign to make sure it works.
then you must have a package in the oem that disables the securities. the problem probably lies in the oem that you are using. do you have "OEM certs" file in the oem somewhere?

Hi thx for this fast answer yes i have a oem cert this was my first thought but it the problem isn´t the oem packages. I will try the security off package then the unsigner i hope this helps, did anybody else get this error? I had the securityoff package already in the sys folder but not in the oem package propably the package were not loaded?

You don't need the OS.nb.payload. When you cook it's only used for the XIP... SYS folder is OS related and contains in a new build new/updated files...

j.vd.spank said:
You don't need the OS.nb.payload. When you cook it's only used for the XIP... SYS folder is OS related and contains in a new build new/updated files...
Click to expand...
Click to collapse
When i try to cook without it the i get an error message that the path was not found i use the tnt kitchen with the xip.bin and sys from 5.2.20755.
@S.V.I: I have test your solutions but when i reset the poutlook.exe certificate and write it again, wm 6.1 doesnt boot. I have test all combinations of reseting the certificate for this folder in SYS\BaseApps\poutlook.exe and SecurityOff application in oem and sys folder.

j.vd.spank said:
You don't need the OS.nb.payload. When you cook it's only used for the XIP... SYS folder is OS related and contains in a new build new/updated files...
Click to expand...
Click to collapse
I know that there must be something with the SYS (coredll.dll)
I use a Bepe 0.99 related kitchen. And the only thing how te get the correct OS was to replace the 8004000-os.nb (os.nb.payload). It was strange but it worked.
I use the correct SYS but with a older related 8004000-os.nb OS file the disired version was not shown. Version is editable but is not the way to be

where is the "build"

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