I ever customized several wizard roms, but regarding porting ROM, I'm a newbie.
Let's think about two scenarios:
1. If I got an AKU 3.x ROM of other phone, i.e., a ROM of Artemis
2. If I got a WM6 ROM of other phone which version is newer than any current known ROMs, i.e., a Hermes WM6 ROM
If I want to port the ROM to run on a wizard, what are the most important files, modules, drivers or something like XIP section we need to port? are there any different steps when porting within those two scenarios? Will somebody make a brief introduction or write a tutorial here?
Bepe, mUn, Faria and other talent guys, I know you're expert on this, please show me your hands and help on this, thank you.
I am too learning this ... seems pretty tricky if not near impossible without proper XIP section. Meaning that if you want to port WM6 to a device that didn't had a WM6 it's impossible ... or very close to that.
Take this as an example http://forum.xda-developers.com/showpost.php?p=1243434&postcount=172
Not the actual files, those are device specific (xip.bin for example) but a little guide.
anichillus said:
I am too learning this ... seems pretty tricky if not near impossible without proper XIP section. Meaning that if you want to port WM6 to a device that didn't had a WM6 it's impossible ... or very close to that.
Take this as an example http://forum.xda-developers.com/showpost.php?p=1243434&postcount=172
Not the actual files, those are device specific (xip.bin for example) but a little guide.
Click to expand...
Click to collapse
thanks, that's great
Hi,
i have a little question.
Which and how many versions of OS exist and which are the differences.
The OS version 5.2.318 is come before or after the 5.2.1413?.
Thanks for your answers.
Good question and should be pinned (if i didn't miss it when i joined)
From what i gather 5.2.1413 is a newer build but had more bugs that these developers in some threads fixed for there roms.
Yep 1413 is a newer build and it also came with the new 2007 version of Office Mobile.
The OS build question has an excellent answer in the second post of this thread: http://forum.xda-developers.com/showthread.php?t=316447
Im looking for a clean os, preferably CE 5.2.19400 (Build 19199.1.0.0).
I want to have a clean base OS to start adding my fixes, applications and tools. I have tried to disect many of the "vanilla" versions from people, but even their clean versions still include a lot of garbage I dont want and is almost impossible to clean. I would rather start from a totally clean os and build up from there.
Thanks,
jay
I would also like to know this.
further, how can one be sure that a 'clean' os (or any freely downloadable rom for that matter) is free from software that snoops on you, etc?
Here is the 19400 dump
http://www.sendspace.com/file/kdincu
I wonder, is a Hermes dump usable to cook a Wizard ROM?
And you mention, "CE 5.2.19400 (Build 19199.1.0.0).". Is that newer or older than the custom ROMS that are advertised as WM 6.1 build 19209? I mean, does that mean CE 5.2.19209 build xxxxxx or CE 5.2.xxxxx build 19209?
Cheers!
CE 5.2.19400 (Build 19199.1.0.0) means OS from new build, XIP from old build.
However there are some fake ROMs that with modified OS version, this may be the case (Because official 19209 ROM is AKU 1.0.2, how come this ROM is still AKU1.0.0?)
ROMs for other devices can be used in Wizard after porting (at least OS(SYS+OEM) porting must be done). You may use XIP from other Wizard ROMs, but will show your old XIP build in the About screen.
Thanks for the explanation, it's clear now
Alex has not been releasing new cooking kits, but there are alot of new roms based on newer builds. Is anyone out there making new cooking kits? Or do we have to build from the ground up from the official roms? I'm interested in cooking a rom, but not sure where to get a new source of files (I've cooked a few based on some of Alex's cooking kits).
-Todd
first you need to know how to use whats already given to you by Alex then when you know how and what to do.. you can think of porthing other builds.
and no there is no need in a new kitchen for the new builds.
and people please read and search this forum before asking the last weeks there have been far to many cooking questions that could have been answered by looking in the sticky threads.
gullum said:
first you need to know how to use whats already given to you by Alex then when you know how and what to do.. you can think of porthing other builds.
and no there is no need in a new kitchen for the new builds.
and people please read and search this forum before asking the last weeks there have been far to many cooking questions that could have been answered by looking in the sticky threads.
Click to expand...
Click to collapse
Maybe I didn't ask the right question. I'm not looking for a new kitchen, but a new cooking kit. I've noticed there's some newer OS builds out there. Have they been ported from other devices maybe? That's what I was wondering...... I've read the tutorials and watched the videos on dumping a rom, but wanted to get good at cooking before venturing out!
yes every build newer then 5.2.19212 is ported from other devices except from 213 & 214 witch are modified version of 212
If you search in forums for other models you find newer build that are made into cooking kits you anly need to change some things froms the oem folder to get them to work on kaiser and ofcause you need to port the xip too
Ok I know what you mean about a newer kitchen. I posted this in my other thread too what think needs to be implemented is the newer programs that are used in the kitchen.
1. BuildOS+package 4.b3 instead of v. 2
2. PackageTools is also newer.
I am just not sure how to change the .bat files or I would try this myself. DOn't get me wrong ALEX's kitchen is suitable but newer software is out there.
gullum said:
yes every build newer then 5.2.19212 is ported from other devices except from 213 & 214 witch are modified version of 212
If you search in forums for other models you find newer build that are made into cooking kits you anly need to change some things froms the oem folder to get them to work on kaiser and ofcause you need to port the xip too
Click to expand...
Click to collapse
Ok, that was my misunderstanding. So I guess I need to build from the 3.03 kit, which I'm going to guess is the 212 build. I built from the 3.02 kit because I read somewhere that the 3.03 was slower than 3.02 (think it was in one of dutty's threads). Thanks again.
-Todd
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.